Previous Topic: PARM KeywordsNext Topic: Data Sets Used/Created


Specifying Jobs to Move

The input to the BTI run is in the form of CA WA CA 7 Edition LJOB and/or LSYS commands. They may be used in any combination to define the jobs to be moved. If any workstation networks are to also be moved, the programs automatically include those with a predecessor or successor relationship with any of the jobs specified. If others are not connected to a job, they must be moved manually by the user.

Requirements for /LOGON and /LOGOFF commands are the same here as for any BTI data set and must be supplied in addition to any LJOB or LSYS commands.

If the LSYS command is used, every job in the database with the same system name as that indicated has commands generated to define the jobs into another database. This assumes that the optional system name was entered for each of the desired jobs when they were defined in the database. It may be safer to use the LJOB command with a generic job name because job names are required in the database. Job naming conventions usually make generic specification of the desired names relatively easy. Multiple commands can be used as necessary to define all of the desired jobs.

Jobs that have any type of predecessor or trigger relationship with any of the jobs being moved are also included in the final output command data sets produced by this process. That is made possible by the look-aside process that enables automatic inclusion of workstation networks. This look-aside process only looks one level in each direction from a job that was requested to be moved.

More information:

Workstation Networks