control-m jcl verify - die atics · pdf filecontrol-m workload automation control-m/jcl...
TRANSCRIPT
Why does JCL need to be verified?
Why JCL Verification?- Job failures in production have a potential business impact
- The creation & modification of JCLs can be an error-prone process
- The dynamic nature or the IT environment requires constant verification of JCLs validity
- Enforcing naming standard of the organization when promoting JCL’s across environments is a common requirement
JCL verification solutions commonly offer:
© Copyright 6/9/2013 BMC Software, Inc 2
JCL verification solutions commonly offer:- JCL checking ability
- Site Standard & Policy verification automation
Control-M JCL Verify – JCL verification
New Control-M JCL Verify product
- Ensure JCLs are error-free by checking:
� Syntax
� File existence
� Security
� JES2 & JES3 statements
� Checking that all the PGMs invoked can be located
© Copyright 6/9/2013 BMC Software, Inc 3
� Checking that all the PGMs invoked can be located
- Tight integration with Control-M
� From the definition and monitoring panels
� Resolve auto edit variables
� Ability to check jobs that are ordered for specific date before submitting
- General abilities
� Ability to bypass check
� Ability to decide on check level (Error\ Warning\ Information)
Control-M JCL Verify – Concept
Main Engine
- Set of routines that are responsible for checking the JCL cards of job(s)
- Accessible using API
User Interfaces
- Stand alone (ISPF) using edit macro
- Control-M based
Only if Control-M is installed and Control-M JCL verify is licensed
© Copyright 6/9/2013 BMC Software, Inc 4
� Only if Control-M is installed and Control-M JCL verify is licensed
- Batch utility
Administrator Interfaces (via ICE)
- Install
- Maintenance
JCL basic syntax (not optional)- //MYDD DD BSN=XX.YY.ZZ,DISP=SHR
JES2 and JES3 cards syntax (optional) - /*ROUTE XEQ
Dataset existence (optional)- //MYDD DD DSN=XX.YY.ZZ,DISP=SHR (XX.YY.ZZ – does not exist)- Only Catalog will be checked
Security check (optional)
Control-M JCL Verify – Main Engine Abilities
© Copyright 6/9/2013 BMC Software, Inc 5
Security check (optional)- //MYDD DD DSN=XX.YY.ZZ,DISP=SHR (user cannot access XX.YY.ZZ)- Checks userid (default)
Modules existence (optional)- //STEP1 EXEC PGM=MYPROG (MYPROG cannot be found in the search
path of STEPLIB, JOBLIB, LINKLST…)
Control-M JCL Verify – Utilities
CTJINIT- The CTJINIT utility boosts the performance of the JCL verifications by
loading basic site related information into shared objects.
- Shared objects are used by each verification
- Data in shared objects is static
- Planned data refresh periodically (no automatic refresh)
CTJVER- Verify single job or work in mass mode
© Copyright 6/9/2013 BMC Software, Inc 6
- Verify single job or work in mass mode
- Verify many jobs together (from one or different libraries)
CTJPLAN- Verify jobs for specific scheduling date (ODATE)
Control-M JCL Verify – Next Releases
Site Standards
- User interface for standards specification
- Enforce specified standards
- Bypass/Trigger errors and warnings
- Job’s visual reformatting
EM interface
© Copyright 6/9/2013 BMC Software, Inc 7
EM interface
Major utilities support (e.g. IEBCOPY)
- SYSIN statements
- DD cards allocation
Remote verification
- Verify a job as if it would run on a different lpar
CTM job flows
- Do not warn on a missing dataset in JOB X if a preceding job in its flow
creates it
Control-M JCL Verify – Site Standards - Selection
General Selection parameters:- ENVIRONMENT
- Priority
- SCHEDLIB - schedule library
- SCHEDTAB - schedule table
- SCHEDJOB - schedule job
- JCLLIB - JCL library
- JCLMEM - JCL member
© Copyright 6/9/2013 BMC Software, Inc 8
- JCLMEM - JCL member
- JOBNAME - JOBNAME of the JCL
Control-M JCL Verify – Site Standards - Processing
The site standards rule will cover the following ONs:- JOBINIT - once you start verifying the job
- JOB - Job statement
- PROC - on a PROC statement
- JCLLIB - on record of JCLLIB
- INCLUDE - on record of INCLUDE
- JOBEND - once Control-M/JCL Verify end the verification for relevant job
© Copyright 6/9/2013 BMC Software, Inc 9
relevant job
- EXEC - at EXEC statement with the same name of PGM or PROC
- DD - SYSIN, SYSOUT, DDNAMEs
For each of these rules the customer can define DO statements:- DO MSG - to issue user messages
- DO SET - Assign value to variable or JCL statement
- DO IF-ELSE-END - for several variables and user defined variables.
- DO RETURN - to return with RC and RS that the user define
Control-M JCL Verify – Rule Definition Screen
© Copyright 6/9/2013 BMC Software, Inc 10
Control-M JCL Verify – Rule Definition Screen
© Copyright 6/9/2013 BMC Software, Inc 11
Control-M JCL Verify – Rule Definition Screen
© Copyright 6/9/2013 BMC Software, Inc 12
To learn more, go ocial
© Copyright 6/9/2013 BMC Software, Inc1313 © Copyright 6/9/2013 BMC Software, Inc
Thank You
© Copyright 6/9/2013 BMC Software, Inc14 © Copyright 6/9/2013 BMC Software, Inc14
Thank You