ujobdump - Dump Upgraded Job Definitions

ujobdump [-vclx?] [-d AltDir] DataArea Outfile [-u User [Jobs]] [-t Tokens]

ujobdump is a utility that dumps job definitions based on the selection criteria specified. The ujobdump utility, in conjunction with the ujobload 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.


Program Option	Description
`v`	Verbose. This option lists the jobs as they are being processed and any jobs that are not dumped.
`c`	Count. The count option displays the number of jobs that will be processed. This option does not process any jobs.
`l`	List. The list option lists, across the page, all jobs that are counted with the `-c` option.
`x`	Include upgrade job.
`?`	Print usage and syntax.
`d AltDir`	Alternate Source Directory. The alternate source directory is used mainly when applying MSPs or CTPs. This option specifies where alternate source directories (acsrc, amsrc, apsrc, and so on) are located. Typically , this would be the backup source directory that holds the original source for any programs that have changed after applying an MSP or CTP and will cause ujobdump to only dump jobs associated with changed programs.
`DataArea`	You must specify a data area. Only jobs with all their steps run in the specified data area will be dumped, regardless of any other parameter entered. If you do not specify any other options, all jobs for that data area will be dumped.
`OutFile`	You must specify an output file. This is the file to which the job definitions will be dumped. If you specify a dash (-), job definitions will be dumped to standard out.
`u User [Jobs]`	User. The user option causes only jobs for the designated user to be dumped. If job names are listed after the user name, only those jobs for the given user will be dumped. Multiple jobs may be specified. The user name is the "NT..." user name, not the domain\user name.
`t Tokens`	Tokens. The tokens option causes only jobs containing the specified form IDs to be dumped. If this option is specified, specific jobs cannot be specified with the `-u` option.

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.