13. 13 @CAWORLD #CAWORLD
Best Practices
Mainframe Proclib Naming Standard
Mainframe Proclibs contain Application names are limited to 8 characters and are defined with the following format:
IPSNESP.AAA.PROCLIB.VISL
Where:
IPSNESP – Does not change
AAA - Characters are defined as the 3 alpha character code
PROCLIB – Does not change
VIS – Does not change
L – Mainframe Location Code
Example:
IPSNESP.CMD.PROCLIB.VISN
| |
Application North
Application/Event/Proclib Standardized Names Example
16. 16 @CAWORLD #CAWORLD
Dev-Ops
Step 2: Create Stop File Trigger Application
APPL OTAECFT
/* This appl contains all OTA EAST CFT jobs*/
FILE_TRIGGER OTAE_STOP_FT
/* Triggers OTA EAST Stop Event $VZWXOTA.OTAESTOP
RUN DAILY
AGENT OTAEAST
FILENAME '/ota/data/adm_ota/otaStopEastESP' CREATE NOCHANGE(1) CONTINUOUS($VZWXOTA.OTAESTOP)
DUEOUT EXEC 23:59 EASTERN
NOTIFY OVERDUE ALERT(GLB5)
Stop and Start Setup
17. 17 @CAWORLD #CAWORLD
Dev-Ops
Step 3: Create Stop Application
APPL OTAESTOP
/* This appl will set OTA_EASTBATCH to 0*/
JOB STOP.EASTOTA_BATCH TASK SELFCOMPLETING
/* This link job will stop the OTA East batch jobs.*/
RUN DAILY
RELEASE ADD(Cleanup_Stop_Start_Files.OTAEAST_STOP)
ESP RESDEF OTA_PRD_DATA_OTA_EASTBATCH SET AVAIL(0)
NOTIFY PNODE(COMPLETE) ALERT(SHTR)
ENDJOB
UNIX_JOB Cleanup_Stop_Start_Files.OTAEAST_STOP
/* This script will cleanup the ESP Stop/Start dummy files created to stop/start OTA batch
RUN DAILY
AGENT OTAEAST
USER adm_ota
SCRIPTNAME /ota/data/adm_ota/cleanupESP.sh
ENDJOB
Stop and Start Setup
18. 18 @CAWORLD #CAWORLD
Dev-Ops
Step 4: Create Start Continuous File Trigger Application
APPL OTAECFT
/* This appl contains all OTA EAST CFT jobs*/
FILE_TRIGGER OTAE_STRT_FT
/* Triggers OTA EAST Start Event $VZWXOTA.OTAESTRT
RUN DAILY
AGENT OTAEAST
FILENAME '/ota/data/adm_ota/otaStartEastESP' CREATE NOCHANGE(1) CONTINUOUS($VZWXOTA.OTAESTRT)
DUEOUT EXEC 23:59 EASTERN
NOTIFY OVERDUE ALERT(GLB5)
ENDJOB
Stop and Start Setup
21. 21 @CAWORLD #CAWORLD
CA WA ESP Edition and CA Endevor®
Step 1: Creation of the CA Endevor® Environment
The CA Endevor® Administrator in coordination with our Scheduling team defined the CA Endevor® environment. The CA Endevor® environment
contains the following: 1 Environment, 1 System, 27 Subsystems, 2 stages and 2 types (APL) for application and (SYM) for Global Variables/Symlib
members.
CA Endevor® Setup
Environment
EPSWLS
System
EPS
Subsystem
AAA00 (AAA = 3 Character
Application code)
Stage
Stage 1: PSTG
Stage 2: PROD
Type
Type 1: APL
Type 2: SYM
Step 2: Creation of the Package Shipment Rules
Since the CA Endevor® software is required to be installed on our development mainframe, we needed a process to send the updated applications to
the production mainframe proclibs. The CA Endevor® Administrator created Package Shipment rules to allow this to occur. Once the CA Endevor®
package is executed, the CA Endevor® with CA WA ESP elements are then ‘shipped’ to our production proclibs.