Commands › LOAD, LOADH Command › LOAD Usage Notes

LOAD Usage Notes

The LOAD command and its process do not support internal cross-platform jobs because these jobs do not refer to data sets and are executed on other platforms than where the job ID defined.

• The LOAD process builds the database profile for a new job or rebuilds the profile for a job whose JCL was changed. This profile can also be built by a DEMAND/DEMANDH (for a new job that is not defined to CA WA CA 7 Edition) or by any other run of the job if the DB.1 panel RELOAD indicator is on. However, when DEMANDed or RELOADed, the job proceeds to normal execution after the load step is executed.
• When using LOAD/LOADH, if the job was not previously defined to CA WA CA 7 Edition, the job name value for JOB must be the same as the JCL member name that contains the job's JCL. In addition, the JCLID parameter must be specified to point CA WA CA 7 Edition to the proper JCL data set.
• The corresponding DB.1 panel option RELOAD=Y performs the LOAD process as the first step of the job whenever it is run the next time. This field is automatically set to Y when a REPL is done through the CA WA CA 7 Edition JCL facility. The indicator is set back to RELOAD=N when load processing successfully completes.
• Each LOAD command results in the execution of a batch job with the same job name as the production job, or if specified in the initialization file DBASE statement, a job name derived from the LDJOBNM parameter. If using the LDJOBNM parameter, the JCL JOB statement must provide room for an eight-character job name.
• Normal data set availability checking is performed by the operating system based on DISP parameters on DD statements in the JCL. This could be a problem when LOAD is requested for a job that references a data set currently in use, such as online database files. It may be more convenient to set RELOAD to Y on the DB.1 panel for this type of job.
• In a JES3 environment, jobs that are submitted by the LOAD command have the same data set, device, and volume setup characteristics as the subject job whose profile data is being created or updated. It may be more desirable, in the JES3 environment, to use the DB.1 panel RELOAD option to avoid unnecessary mount requests for data sets not required for just the LOAD process.
• If there are any scheduled JCL overrides in the JCL, the resulting profile in the database reflects the net effect of these overrides based on the current date, time of day, and SCHID values.
• If workload balancing is being used, the job being loaded is scheduled using the default WLB job class for LOAD if the CLASS= keyword is not specified.

  Note: For more information about the LOADCLASS parameter of the OPTIONS statement in the initialization file, see the Systems Programming Guide.

• The LOAD command cannot be used for a job that has been marked as nonexecutable (for example, EXEC=N) on the DB.1 panel.
• If the LOADDSNS keyword is used on the DBASE statement in the initialization file, then the LOAD process does not build any DD or data set information for jobs that are marked MAINT=Y on the DB.1 (JOB) panel.
• If the JOB statement of a job being loaded has the RESTART keyword specifying a step for the job to begin execution, the LOAD step does not execute. To LOAD this job, omit the RESTART keyword.
• If VRMDD=DEF or VRMDD=YES is coded on the OPTIONS statement in the CA WA CA 7 Edition initialization file, then VRM resource definitions for this job are dynamically modified when the job is LOADed.

  Note: For more information about VRM Device Control, see the Database Maintenance Guide.