ujobload - Load Upgraded Job Definitions

ujobload [-oudl?] [-x OldJobName:NewJobName...] DataArea InFile

The ujobload utility, in conjunction with the ujobdump utility, enables you to update job definitions more easily when a batch update or report parameter form has a new form definition file (.scr) as a result of CTP or MSP installation or an application upgrade. To determine if a new or updated .scr file has been added, examine the install.log file (in the case of a CTP or MSP) or the readme file (in the case of an application upgrade). Because ujobdump and ujobload update the job definitions, you do not have to manually change the job definitions when new or modified .scr files are installed.

The purpose of ujobdump and ujobload is to provide the capability to map the parameter fields when loading job definitions. These two scripts use the standard Lawson jobdump and jobload utilities, but enhance the process by parsing the job parameters fields and mapping their values during the load process. Default values to new fields will also be loaded.

ujobload is a utility that creates and optionally processes a standard Lawson jobload file for each job found in the input file. For each job, the LAWDIR, PROJECT, PRODUCTLINE, JOBNAME, and PARAMS lines are altered to match the current Environment, data area specified and parameter fields of the form.

Program Option Description
o Overwrite. The overwrite option causes any existing job definitions to be overwritten. If you do not specify this option, only jobs that do not exist will be created.
u Update. If you do not specify an update option, no jobs will be overwritten or created. List only is then assumed.
d List "deleted" fields. This option causes ujobload to list, with the other mapped fields, parameter fields which exist in the job definition and have values, but are not mapped to any field in the new job definition. Regardless of whether this option is specified or not, all "deleted" fields will be listed in the summary report at the end of the output log
l Display the job log from the last ujobload run by the designated user. You must specify the DataArea when using the -l option. No other parameters are required when using this option.
? Print usage and syntax.
x OldJobName: NewJobName

Translate. The translate option renames specified job names from OldJobName to NewJobName. You can specify as many translate options as necessary.

For example:

ujobload -x JOB-1:JOB-1a -x JOB2:JOB-2a

DataArea You must specify a data area. All job steps will be created to run in this data area.
InFile You must specify an input file. This is the file from which the job definitions will be read. If you specify a dash (-), job definitions will be read from standard in.

At the command line, specify the information above.

For more information about jobs and reports, see Lawson Administration: Jobs and Reports.

Considerations

  • It takes about 5 seconds to dump and load an average job. That’s about 720 jobs an hour, or 17,280 per day. Clients with a lot of jobs may want to break down the upgrade by user. Also, the average time depends on the parameter list. If the parameter list of the dump matches the parameter list of the job being loaded, the job only takes a second or two. If they do not match, the job will take several seconds to run. CTPs and MSPs should run faster than the 5 second average and will be limited to the number of jobs attempted to dump and load if the -d option is used.

  • When upgrading from product line A to product line B within the same environment, if you do not rename the jobs, they will overwrite product line A’s jobs.

  • Parameter field values are mapped between fields with the same name. If a field was renamed, the value will not be mapped.

  • Clients should check carefully the "deleted fields" summary for possible problems (see the previous consideration).

  • Program names that are recycled will get unpredictable results. The job will be loaded and parameter fields will be mapped if any of the field names match.