Pre-Con Ed: Best practices for setting up CA Workload Automation ESP Application Procedures
•
0 likes•883 views
Pre-Con Ed: Best practices for setting up CA Workload Automation ESP Application Procedures
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Pre-Con Ed: Best practices for setting up CA Workload Automation ESP Application Procedures
Similar to Pre-Con Ed: Best practices for setting up CA Workload Automation ESP Application Procedures (20)
More from CA Technologies
More from CA Technologies (20)
Recently uploaded
Recently uploaded (20)
Pre-Con Ed: Best practices for setting up CA Workload Automation ESP Application Procedures
- 2. 2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD © 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA. For Informational Purposes Only Terms of this Presentation
- 5. 5 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Decision To Use Your Enterprise Workload Product or Not? § Is the application business critical? § Does the application have a business impact on: – Revenue – Service – Customer § Yes. Then you need to use the Enterprise Workload solution
- 6. 6 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Once You Have a Production Workload Instance, What is The Value of a Pre-production Instance? § It is used to protect production – Minimizes potential for production failure or outage – Testing of application flows before production – Testing of Application Integrations in pre-prod enables better Enterprise Workload usage and visibility – Part of a Devops implementation strategy § Testing of CA WLA ESP server upgrades and fixes
- 7. 7 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Potential issues with multiple CA WLA ESP instances § Manual effort to migrate CA WLA ESP procedures from one instance to another – Manual effort to change values like arguments and times in the Applications and Jobs – Change Event names and scheduling frequencies § Hard to keep CA WLA ESP procedures in sync without proper naming standards
- 8. 8 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Potential issues with using a single CA WLA ESP instances § Test can inadvertently affect production – Naming standards and security profiles should prevent this from happening – Runaway REXX programs § Ensure separate Event Initiators – Try to have as much physical and logic separation
- 9. 9 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Value of creating Naming standards § Easier to categorize artifacts for searching purposes § Easier to determine ownership or responsibility § Easier to create and onboard new applications
- 10. 10 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Value of creating Naming standards § Easier to create and/or clone security rules § Easier to subscribe in Monitoring – Can subscribe to just the Applications that you want § Enable moving applications through a development life cycle as part of your Devops strategy – Minimize or eliminate manual changes between stages
- 11. 11 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Suggestions for CA WLA ESP Artifact Naming Standards § 8 character Application names (PDS Member) makes it hard to use multiple characters for the Application name – Many customers have a naming convention for a couple of characters to represent the business application – PDS member name does not have to match the Application name but makes searching easier if it does – APPLDESC was created to provide better visibility of the application purpose § APPL APPLDESC DESC('HELLO FROM CA WORLD') PQC = SUBSTR(1,3,%ESPTRMEM) SITE = SUBSTR(4,1,%ESPTRMEM) THRD = SUBSTR(5,1,%ESPTRMEM) APPLID = SUBSTR(6,2,%ESPTRMEM)
- 12. 12 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Suggestions for CA WLA ESP Artifact Naming Standards § Event prefixes are independent names and not associated with a real TSO logon userid – Example DEV.PAYOLL, TEST.PAYROLL, PROD.PAYROLL – Usually used as a test for which environment standards to load – This is usually the userid used for the execution of z/OS workload REXXON Eventname=CLANGVAR('%ESPEVENT') PARSE VAR Eventname event_prefix '.' event_name "event_prefix='"event_prefix"' " REXXOFF ENVCHAR = substr(1,1,%ESPEVENT) INVOKE CAIDEMO.PROD.ESP.PROCLIB($%event_prefix) REXXON Eventname = CLANGVAR('%ESPEVENT') parse var Eventname PAR1 "." PAR2 "_" PAR3 "_" PAR4 "SSID='"PAR1"'" "ACID='"PAR2"'" "GSID='"PAR3"'" "VSID='"PAR4"'" REXXOFF BCID = SUBSTR(7,2,%ACID) HCID = SUBSTR(1,2,%GSID)
- 13. 13 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Suggestions for CA WLA ESP Artifact Naming Standards § Another suggestion for Event names is to use a customer name or distribution center name when you are using an Application as a Template for a many to one execution – Example DC1, DC2, DC3 – Change the Application name as well DCNUM = substr(1,3,%ESPEVENT) APPL %ENV.STATS INVOKE CAIDEMO.PROD.ESP.PROCLIB($%DCNUM)
- 14. 14 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD CA WLA ESP Artifacts Where the Business Application Name Can be Used as a Prefix § Resources - prefix_D/R/T_RESOURCE_NAME – Try to be very descriptive in the name – Easier to troublehoot when jobs are in RESWAIT § Security Group profile - prefix_GR § Global Variable Table Name - prefix_GV
- 15. 15 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD CA WLA ESP Artifacts Where the Business Application Name Makes Sense as a Prefix § Calendar Special Days - prefix_SPECIAL_DAY § JCLLIB, TEMPLIB, COPYJCL, DOCLIB
- 16. 16 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Static Variables - Environment Variables Symlib at Event Level (DEFSYML command) ESP_subsys ='ESPP' ESP_env ='PROD' ESP_envchar = ‘P’ ESP_zosusr ='PRODUSR' ESP_ftpusr ='FTPUSR' ESP_rcvport ='9671' ESP_wssport ='9654' ESP_webport ='4567' ESP_hostdns ='TSO21'
- 17. 17 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Dynamic Variables – Some Common Examples Used by INVOKE statement § JCLLIB, COPYJCL, TEMPLIB, DOCLIB § Dates § Agents § Directories/paths § Fixlib § Times/SLAs/Critical jobs § Notifications § Jobname/qualifier § Notification Lists § Database servers
- 18. 18 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Sample Dynamic Variables JCLLIB 'CAIDEMO.PROD.ESP.JCLLIB' COPYJCL 'CAIDEMO.PROD.ESP.COPYJCL' JOBNAME TEMPLIB 'CAIDEMO.PROD.ESP.TEMPLIB' USEMEM DOCLIB 'CAIDEMO.PROD.ESP.DOCLIB' OPTIONS RESTARTSTEP DUEOUTPROPAGATION CRITPATH ON NOTIFY FAILURE MAILBOX(JROONEY) NOTIFY OVERDUE ALERT(LATE) root_directory='c:prodhomebin' report_directory='c:Reports' agentname = 'PROD_AGENT' gentime P0 today gentime P1 today plus 1 day gentime M1 today less 1 day P0DATEA = '%P0YEAR%P0MM%P0DD' P1DATEA = '%P1YEAR%P1MM%P1DD' M1DATEA = '%M1YEAR%M1MM%M1DD' echo %P0DATEA echo %P1DATEA echo %M1DATEA
- 19. 19 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Use as Envars in Wob Defintion REXXON Eventname=CLANGVAR('%ESPEVENT') PARSE VAR Eventname event_prefix '.' event_name "event_prefix='"event_prefix"' " REXXOFF APPL %event_prefix.SYM INVOKE CAIDEMO.PROD.ESP.PROCLIB($%EVENT_PREFIX) JOB %ESP_ENVCHAR.AACJ001 MEMBER PAACJ001 RUN DAILY TIME='30' CODE='04' ENDJOB NT_JOB Echo_test RUN now AGENT %AGENTNAME CMDNAME %root_directoryechoit.bat ARGS 'just some message' ENVAR ESP_subsys =%ESP_subsys ENVAR ESP_env =%ESP_env ENVAR ESP_envchar =%ESP_envchar ENVAR ESP_zosusr =%ESP_zosusr ENVAR ESP_ftpusr =%ESP_ftpusr ENVAR ESP_rcvport=%ESP_rcvport ENVAR ESP_wssport=%ESP_wssport ENVAR ESP_webport=%ESP_webport ENVAR ESP_hostdns=%ESP_hostdns ENDJOB
- 20. 20 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Simulation Output § Execution of Symlib § Echo used to confirm some values being passed during execution § ENVAR used to pass symbolics without the need to include in the args
- 22. 22 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Global Variable Tables Can Be Used As Well § VTDEFINE CAWORLD § VTLIST CAWORLD § VPUT GV_TEST TABLE(CAWORLD) § VGET GV_TEST TABLE(CAWORLD)
- 24. 24 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD VTRDEF – Define Global Variable Trigger § Create a Global Variable trigger § Whenever a variable is updated § Or when it is updated to a certain value VTRDEF VARIABLE(GV_TEST) TABLE(CAWORLD) EVENT(PROD.GVTRIG) WHEN(‘START’)
- 25. 25 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Ways to Minimize or Eliminate Changes While Moving Through the Lifecycle § Define an Event with a Symlib with static variables – May not need to move the Event though the lifecycle § Define dynamic variables in the INVOKE defined in the Application at Event Trigger time – Date symbolics for past, present and future dates § Embed IF/THEN/ELSE logic in the job definition – For values that need to be set just before the job is executed
- 26. 26 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Ways to Minimize or Eliminate Changes While Moving Through the Lifecycle § Try to make it so that only the Application needs to be migrated – Use links for APPLSTART and APPLEND as functions to execute CA WLA ESP commands to set-up other jobs and to keep the Application as self- sufficient as possible
- 27. 27 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Ways to Minimize or Eliminate Changes While Moving Through the Lifecycle § Create application standards for deploying applications – Standard directory names in pre-prod and prod will minimize the need for creating exception symbolics § Unix and Linux are interchangeable job types – Can test with a Unix agent but actually use Linux in production
- 28. 28 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Leveraging Agent Alias § Do not need to define the real agent name in the CA WLA ESP topology to use a particular agent § An agent alias can be set-up for any reason and for any purpose – CA pre-sales routinely uses aliases to mimic customer’s agents – Multiple aliases can be set-up on an agent § Could use production agent names for pre-prod agents § When retiring an agent, can be an easy way to switch agents without changing job definitions immediately
- 29. 29 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Executing the CA Software Change Management Solution for Life Cycle Management § Move the CA WLA ESP Procedure PDS member § Execute a Simulation of the Application – Validate the syntax of the CA WLA ESP Procedure – Can use a generic Event for the simulation – Execute for daily, Weekly, monthly, Holiday, etc… § Can move the Event – May need to execute a processor to change the definition in pre-prod
- 31. 31 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Sample CA Endevor Processor for Simulation //*------------------------------------------------------ //* GESPSIM PROCESSOR FOR ESP PROCEDURE SIMILATION //* //*------------------------------------------------------ ------------- //GESPSIM PROC AA=' ', // CPFX=&#COMMPRFX., // PFX=&#BASEPRFX// VIO=SYSDA //* --------------------------------------- //* ALLOCATE THE OUTPUT LISTING DATASETS //* --------------------------------------- //INITLIST EXEC PGM=BC1PDSIN //C1INIT01 DD DSN=&&ESPLST,DISP=(,PASS), // SPACE=(TRK,(3,5)), // DCB=(RECFM=FBA,LRECL=133,DSORG=PS) //**===================================================== //** ESPSIM - SIMULATE PROC VIA ESP //**===================================================== //ESPSIM EXEC PGM=ESP,MAXRC=0,PARM='SUBSYS(EP21)' //SYSPRINT DD DSN=&&ESPLST,DISP=(OLD,PASS) //*YSPRINT DD SYSOUT=* //SYSIN DD * SIMULATE EVENT(ROOJO02.&C1ELEMENT) SCHED('TODAY') //* //* ----------------------------------- //* PLACE THE LISTING IN LISTINGS //* ----------------------------------- //CONLIST EXEC PGM=CONLIST,PARM=STORE,MAXRC=0,COND=EVEN //C1LLIBO DD DSN=&PFX..LISTLIB, // DISP=OLD,MONITOR=COMPONENTS,FOOTPRNT=CREATE //C1BANNER DD UNIT=&VIO,SPACE=(TRK,(1,1)), // DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS) //LIST01 DD DSN=&&ESPLST,DISP=(OLD,PASS) //* ----------------------------------- //* COPY SIMULATE OUTPUT TO SYSOUT //* ----------------------------------- //COPYSRC EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=X,BLKSIZE=0 //SYSIN DD DUMMY,BLKSIZE=0 //SYSUT1 DD DSN=&&ESPLST,DISP=(OLD,PASS) //SYSUT2 DD SYSOUT=*
- 32. 32 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Can also Manage the CA WLA ESP Event //*------------------------------------------------------------------- //* GESPEVNT: Define ESP event //* //*------------------------------------------------------------------- //GESPEVNT PROC AA=' ', START OF SYMBOLIC LIST // CPFX=&#COMMPRFX., COMMON SYSTEM PREFIX // ZZZ=' ' //**=================================================================** //** ESP - Execute ESP commands ** //**=================================================================** //STEP010 EXEC PGM=ESP,PARM=('SUBSYS(JPR)') //STEPLIB DD DISP=SHR,DSN=CAIDEMO.ESP.R113.SSCPLINK //SYSPRINT DD SYSOUT=* //SYSIN DD DISP=SHR,DSN=&C1BASELIB(&C1ELEMENT) //*
- 34. 34 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Summary § Some upfront naming conventions can help out later when planning for Application life cycle management § Leverage Symlibs, Invokes and Global variables for CA WLA ESP instance related symbolics § CA Endevor can be very useful for managing and validating the movement of artifacts from pre-prod to prod
- 35. 35 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Recommended Sessions SESSION # TITLE DATE/TIME MFX129S Vision and Roadmap: CA Workload Automation ESP Edition 11/16/2016 at 12:45 pm Jasmine C MFX138S Verizon Case Study: CA WLA ESP: Best Practices, DevOps, Change Management Utilizing CA Endevor 11/16/2016 at 3:00 pm Jasmine C MFX123S Case Study: UPS Enables Organizational Efficiencies through the Use of CA Workload Automation 11/17/2016 at 12:45 pm Jasmine C MFT157P Panel Discussion- Best Practices: High Volume Transaction Processing and Analytics 11/17/2016 at 1:45 pm Mainframe Theatre