CA Scheduler Job Management r11 and CA Common Services for z/OS r12 and above compatibility requirements.
Article ID: 19312
Updated On:
Products
Issue/Introduction
List of the requirements, changes, and recommendations for CA Scheduler JM r11 when upgrading to CA Common Services for z/OS r12 and above.
Environment
Component: SCHDMS
Resolution
The following CA Scheduler JM r11.0 apars are required when using CA Common Services CAIENF r12 and above:
APAR#: RO06408
Title: SUPPORT FOR CAIENF R12
Description: CAENF r12 requires an update to the DCMs used by CA Scheduler.
APAR #: RO12887
Title: PROVIDE SAMPLE JCL TO USE WITH CAIENF R12
Description: CAIENF r12 requires different setup instructions and sample query JCL.
Additional requirements:
-The CA Datacom MUF may NOT be shared with CA Scheduler JM and CAIENF r12 and above. CA Scheduler JM and other Workload Automation products such as CA Workload Automation Restart Option for z/OS Schedulers (CA 11) and CA Jobtrac JM may share the same CA Datacom MUF.
-Installation of CA Scheduler JM DCMs (Data Control Module) procedure also changed in Common Services r12 and above. DCMs are now installed in the startup of CAIENF. The DCM configuration statements are placed in the ENFPARMS DD data set that is allocated to the CAIENF started task job. The CA Scheduler JM CAILOAD containing the DCM modules must be in the CAIDCM DD in the CAIENF started task. CA Scheduler JM APAR RO06408 delivers JCL member ACHENF12 containing the DCM, EVENT and SELECT statements used by CA Scheduler JM. Below are the contents of ACHENF12.
***************************************************************** *** COPYRIGHT (C) 2009 CA. *** ALL RIGHTS RESERVED. ***************************************************************** * * USE CARE IN SETTING YOUR CAIENF OPTIONS. CA SCHEDULER MAY NOT * BE THE ONLY CA PRODUCT ON THIS SYSTEM USING CAIENF. * * THE FOLLOWING STATEMENTS FOR CA SCHEDULER MAY BE SPECIFIED IN * THE CAIENF R12 OPTIONS: * *---------------------------------------------------------------- * * TURN RECORDING ON * RECORD(YES) * *---------------------------------------------------------------- * * CA SCHEDULER NJE EVENT * NOTE--THE CA SCHEDULER EVENT IS ONLY REQUIRED IF YOU WILL BE * USING THE CA SCHEDULER NJE FEATURE (SUBMITTING JOBS ON * ONE JES NODE FOR EXECUTION ON ANOTHER JES NODE) * * DCM(CACHDCM0) * EVENT(SCHDNJE,ACT) * EVENT(SCHDNJE,REC) * EVENT(SCHDNJE,RP=1) * EVENT(SCHENJE,PURGE=Y) * *---------------------------------------------------------------- * * THE FOLLOWING STATEMENTS MAKE THE LISTED EVENTS ACTIVE IN * CAIENF. THESE EVENTS ARE REQUIRED BY CA SCHEDULER. * EVENT(JOBINIT,ACT) EVENT(JOBINIT,REC) EVENT(JOBINIT,RP=1) EVENT(JOBINIT,PURGE=Y) EVENT(STEPTERM,ACT) EVENT(STEPTERM,REC) EVENT(STEPTERM,RP=1) EVENT(STEPTERM,PURGE=Y) EVENT(JOBTERM,ACT) EVENT(JOBTERM,REC) EVENT(JOBTERM,RP=1) EVENT(JOBTERM,PURGE=Y) EVENT(JOBFAIL,ACT) EVENT(JOBFAIL,REC) EVENT(JOBFAIL,RP=1) EVENT(JOBFAIL,PURGE=Y) * * THE FOLLOWING SELECT STATEMENTS MAY BE USED TO LIMIT THE * NUMBER OF EVENTS RECORDED TO THE ENF DATABASE. CA SCHEDULER * USES RECORDED EVENTS DURING STARTUP TO UPDATE THE ACTIVE * WORKLOAD TO THE CURRENT SYSTEM STATE (IE, MARK JOBS THAT RAN * WHILE CA SCHEDULER WAS DOWN AS STARTED, COMPLETED, ETC.). * CA SCHEDULER USES EVENTS FOR JOBS AND STARTED TASKS, BUT NOT * FOR TSO SESSIONS, SO TSO SESSION EVENTS DO NOT NEED TO BE * RECORDED. * SELECT(JOBINIT,JOBNUM,NE,TS*) SELECT(STEPTERM,JOBNUM,NE,TS*) SELECT(JOBTERM,JOBNUM,NE,TS*) SELECT(JOBFAIL,JOBNUM,NE,TS*) * *---------------------------------------------------------------- * * DSCLOSE EVENTS ARE OPTIONAL FOR CA SCHEDULER AND ARE NOT * RECOMMENDED DUE TO THE VOLUME OF EVENTS. * * USE THESE STATEMENTS TO MAKE DSCLOSE ACTIVE. NOTE THAT ONLY * DATASET CLOSE FOR OUTPUT AND UPDATE ARE USED, NEVER DATASET * CLOSE FOR INPUT, SO DATASET CLOSE FOR INPUT DOES NOT NEED TO * BE RECORDED. * * EVENT(DSCLOSE,ACT) * EVENT(DSCLOSE,REC) * EVENT(DSCLOSE,RP=1) * EVENT(DSCLOSE,PURGE=Y) * SELECT(DSCLOSE,ACCESS,NE,IN*) * * USE THESE STATEMENTS TO MAKE DSCLOSE INACTIVE: * * EVENT(DSCLOSE,INACT) * EVENT(DSCLOSE,NOREC) * * NOTE THAT YOU MAY HAVE DSCLOSE EVENTS ACTIVE BUT HAVE * CA SCHEDULER IGNORE THEM THROUGH USE OF THE CA SCHEDULER * DSCLOSE=NO OPTION. * *---------------------------------------------------------------- * * JOBPRINT AND JOBPURGE EVENTS ARE OPTIONAL TO CA SCHEDULER. * MOST SITES DO NOT NEED THE EVENTS. THEY ARE ONLY USED FOR * STATION 60 JOBS AND TO CHANGE THE STATUS OF "COMPLETED" JOBS * TO "PURGED." * * USE THESE STATEMENTS TO MAKE JOBPRINT AND JOBPURGE ACTIVE: * * EVENT(JOBPRINT,ACT) * EVENT(JOBPRINT,REC) * EVENT(JOBPRINT,RP=1) * EVENT(JOBPRINT,PURGE=Y) * SELECT(JOBPRINT,JOBNUM,NE,TS*) * EVENT(JOBPURGE,ACT) * EVENT(JOBPURGE,REC) * EVENT(JOBPURGE,RP=1) * EVENT(JOBPURGE,PURGE=Y) * SELECT(JOBPURGE,JOBNUM,NE,TS*) * * USE THESE STATEMENTS TO MAKE JOBPRINT AND JOBPURGE INACTIVE: * * EVENT(JOBPRINT,INACT) * EVENT(DSCPRINT,NOREC) * EVENT(JOBPURGE,INACT) * EVENT(DSCPURGE,NOREC) * * NOTE THAT YOU MAY HAVE JOBPRINT AND JOBPURGE EVENTS ACTIVE BUT * HAVE CA SCHEDULER IGNORE THEM THROUGH USE OF THE CA SCHEDULER * JOBPRINT=NO AND JOBPURGE=NO OPTIONS. * *---------------------------------------------------------------- * * IN CERTAIN VERY RARE SITUATIONS A JOB CAN ABEND IN SUCH A WAY * THAT THE ENTIRE INITIATOR ADDRESS SPACE FAILS. IN THIS CASE A * JOBTERM EVENT IS NOT ISSUED FOR THE JOB. A MEMTERM EVENT IS * ISSUED INSTEAD. CA RECOMMENDS THAT THE MEMTERM EVENT BE ACTIVE. * EVENT(MEMTERM,ACT) EVENT(MEMTERM,REC) EVENT(MEMTERM,RP=1) EVENT(MEMTERM,PURGE=Y) * *---------------------------------------------------------------- . If you are using Critical Path Monitoring (CPM), CPM APAR RO06862: ENF R12 DCM COMPATIBILITY - SUPPORT ADDED INDEX must be applied. The DCM and EVENT must be added to CAIENF started task ENFPARMS dataset. The CPM CAILOAD containing the DCM modules must be in the CAIDCM DD in the CAIENF started task. Below are the statements required: * DCM for CPM DCM(CADBODCM) * EVENTS for CPM EVENT(CABMSSTA,ACT) EVENT(CABMSSTA,REC) EVENT(CABMSSTA,PURGE=Y) EVENT(CABMSSTA,RP=1) . If you are using Cross Platform Scheduling products such as Unicenter JMO or CA Workload Autosys Edition to submit a job to CA Scheduler JM, the DCM and EVENT statements must be added to the CAIENF started task ENFPARMS DD dataset. The CA Scheduler JM CAILOAD containing the DCM modules must be in the CAIDCM DD in the CAIENF started task. *---------------------------------------------------------------- * * CROSS-PLATFORM SCHEDULING (UNICENTER JMO OR CA AUTOSYS TO * CA SCHEDULER) * NOTE: MODULE CAL2DCM2 IS PROVIDED BY CA-XPS (ON THE CA COMMON * SERVICES TAPE) * NOTE: THIS DCM IS NOT REQUIRED FOR CROSS-PLATFORM SCHEDULING * WHEN JOBS ARE SUBMITTED FROM CA SCHEDULER TO OTHER CA * SCHEDULING PRODUCTS OR AGENTS. IT IS ONLY REQUIRED IF * JOBS WILL BE SUBMITED FROM ANOTHER CA SCHEDULING PRODUCT * TO CA SCHEDULER. * DCM(CAL2DCM2) EVENT(CAXPSFBK,ACT) EVENT(CAXPSFBK,REC) EVENT(CAXPSFBK,RP=1) EVENT(CAXPSFBK,PURGE=Y) *
Additional Information
For additional information, see the Common Services Reference Guide , section CAIENF Control Options.
Feedback
