Note: The LOAD process is not used with cross-platform jobs, because that job type does not reference any data sets and has no steps. Thus, there should be no data set dependencies for cross-platform jobs. Data set requirements can be used when a cross-platform job must wait for a data set before being submitted for execution.
The LOAD process addresses the requirements that are associated with data set availability. Based on JCL, the LOAD process determines if the job being LOADed uses or creates a particular data set and updates the database accordingly. Data set dependencies are established for the job for each data set that is input to the job. Unless the dependent job is marked as a MAINT job on the DB.1 panel, it does not run before any required data set is created.
Whenever a permanent change is made to the JCL, the job must go back through the LOAD process that redefines the data set requirements for the job. LOAD is automatic if the JCL is changed through the DB.7 panel.
The LOAD process neither determines nor changes requirements except those associated with data set availability. If the job has requirements other than those associated with data set availability that change, they must be specified through the various DB.3 panel functions. The LOAD process does not delete any requirements that were manually updated or added through a DB.3 panel. This means that data set name changes require DB.3 updates to delete outdated references unless RENAME was used on the DB.6 panel before LOAD occurred.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|