Can CA 7 control SCHENV keyword insertion in jobs which it submits, in order to change JOB card keywords before submission?
CA 7 provides features which can facilitate the use of IBM WLM (Workload Management System) scheduling environments to manage your batch workload. A scheduling environment is a list of WLM resource names and their required states (ON, OFF, or RESET). Through CA 7 Virtual Resource Management (VRM) definitions, you can assign IBM WLM scheduling environments to individual jobs and have CA 7 automatically add the appropriate SCHENV= keyword at job submission time. These VRM definitions use the variable (VAR) resource type and can be associated based on schedule ID. When CA 7 prepares to submit a job, it scans VRM variable definitions for the SCHID of the job. If an appropriate VRM variable definition is found, it is used to set the value of the SCHENV keyword to be inserted.
CA 7 supports definition of VRM variables using RM panels which are stored in the VRM database. The sole purpose of a VRM variable definition is to control SCHENV keyword insertion. SCHENV keyword insertion can be tailored to a specific run of a job by defining a VRM variable in the job's resource profile.
A VRM WLM variable is indicated when VAR is specified as the resource type in the definition on the RM.1 panel. When VAR is specified, the FREE value is not used and will always be set to N. The resource name in the definition must begin with 'SCHENV.'. This signifies that the variable will be used for SCHENV insertion. The second node of the resource name designates the WLM scheduling environment that must be available for the job to run. This value must conform to IBM naming conventions for scheduling environments.
The setting of the WLMSE keyword on the OPTIONS statement in the CA 7 initialization file governs SCHENV keyword insertion. IF N or NO is coded, CA 7 will not attempt SCHENV keyword insertion. WLMSE=Y or WLMSE=YES indicates that CA 7 is to insert the SCHENV keyword. If a value other than these is coded, CA 7 assumes that it is a global default. The global default will be inserted when CA 7 is unable to determine a more specific value for the job. Examples can be found in the Database Maintenance Guide - under Resource Types.
First, CA 7 will scan for an entry with a SCHID value matching that of the job being submitted. If a match occurs, the value from the resource name is inserted on the JOB statement. If no match occurs, CA 7 scans for an entry with a SCHID value of 0. If found, CA 7 uses this as the SCHENV value on the JOB statement. If neither is present, CA 7 attempts to use the global value defined in the initialization file, if one is available. If no global value has been defined on the WLMSE keyword of the OPTIONS statement, the job is submitted without any SCHENV keyword insertion.
NOTES: All scheduling environments must be defined to the IBM WLM.
If the JCL for a job already has a SCHENV= keyword on the JOB statement, CA 7 will not override it. If a job is submitted with a SCHENV= keyword that specifies a scheduling environment that is not part of the current policy, the job terminates with a pre-execution JCL error.
If the JCL for a job already has a SCHENV= keyword on the JOB statement, CA 7 WA does not attempt to validate it prior to submission.
As always, please contact CA Technologies support for CA 7 if you have further questions.