SmartJCLwww.horizont-it.com
SmartJCL
Program found / not found
SmartJCL has many additional functions like
Reformat
Standards Check, Change Facility, REXX interface
Scheduler interface (Control-M, TWS for z/OS)
SmartJCL can be used as Edit Macro, in Batch, from ISPF or eclipse
Integrated in ProcMan, it offers full JCL Change Management
Moves JCL through all stages, e.g. from Test to Integration to Production
Full history, e.g. a JCL containing all versions
It’s more then a simple JCL Checker. It offers many additional features that makes it a complete JCL management tool:
HORIZONT
3. Error message
JCL Validation – DSN Catalog
Error fixed: The inserted IDCAMS step deletes the DSN before its new creation.
But IDCAMS requires SYSPRINT...
HORIZONT
JCL Validation – PGM not found
Program names are not only taken from PGM= but also DB2 (and IMS) calls are recognized
HORIZONT
HORIZONT
Administrator specifies positions of keyword, value and continuation line individually for each JCL parameter according to your company needs
User invokes the function out of the ISPF editor with a simple line command
JCL is reformatted automatically according to your specifications
Use the reformat function to change the JCL format quickly and easily to conform readable standards
HORIZONT
HORIZONT
HORIZONT
SRI - SmartJCL REXX Interface
SRI provides access to all JCL statements for verification and modification by writing simple REXX code
SRI has functions to access JCL constructs easily, e.g.
if qualifier(“dataset name",FIRST)=“TEST“ then ...
SRI contains functions to delete, insert or modify all statements, even complete steps can be inserted automatically!
SRI is a powerful tool to simplify JCL handling, e.g. to
implement your own checks and setup a “JCL quality insurance system”
to change JCL automatically
SRI allows to access all JCL parameters out of your REXX programs
HORIZONT
REXX Interface
There are a lot of well documented examples which explain how the SRI functions are working
Here we go through all statements, if it’s a DD we go through all parameters, if it is DSN= we check the name and do something
HORIZONT
Every site has individual rules, e.g.
„the first qualifier of new datasets in production must be PROD“
„UNIT WORK not allowed if program is SORT“
…
It is possible to use SmartJCL‘s REXX interface and code such checks
The ISPF rule dialog simplifies that. No coding is needed to setup your own standard checks.
An ISPF dialog supports an “JCL Administrator” to specify rules according to site specific standards easily:
HORIZONT
Rule Dialog - Standards Check
An ISPF “wizard” guides you step by step to generate the conditions and actions of the rule
Here we verify the DSN of new cataloged datasets, if the job run in class “P”.
If it’s not okay, a message will be written and an appropriate RC will be set (that’s defined in the messages member)
HORIZONT
Rule Dialog - Standards Check
The result of the new standards rule (DSN starts with P390K which is not allowed in prod)
HORIZONT
DELETE PARM=UNIT
DELETE JOB=ABC%,PGM=IDCAMS,PARM=UNIT,VALUE=TAPE4
In addition to the REXX Interface, SmartJCL has an integrated change facility. It enables you to implement automatic and/or mass changes easily. Examples:
In case of more complex demands, use the REXX Interface
HORIZONT
Remote Check
The Remote Check enables you to perform the JCL check on another system. Advantages are:
Simplifies checking JCL from the test or development system against the production libraries on the production system.
It avoids to transfer the JCL manually to the other (remote) system, logon to that system and check it locally at this system.
SmartJCL remote check uses standard TCP/IP architecture
Simple TCP/IP protocol
It works like this:
The user create or modify JCL on the development system
The user calls JCK macro with parameter SRV=“target system”
SmartJCL transfer the JCL, run the check remotely on the “target system” and send back the resulting messages
HORIZONT
TWS Interface
One of the major benefits of SmartJCL is the integrated interface to TWS:
SmartJCL will simulate variable substitution
(important if you use TWS variable in e.g. DSN etc.)
Optional display TWS info in JCL
(e.g. Application id, Predecessors, Successors, and Special Resources)
Select jobs to be checked from AD or CP by Application Id, Owner Id, Input Arrival etc.
Check JCL in production sequence and simulate catalog actions
Several simulation modes allow to check the complete production in advance (and fix errors in advance)
HORIZONT
TWS Interface - Edit Macro
If you use TWS variable e.g. in a DSN, it result in an error message
Use macro OSJ and JCK to first resolve the variable and then call the check
HORIZONT
TWS Interface - Edit Macro
SmartJCL searches in the CP and AD for the job. You can choose which one should be the input and if it is AD you can enter a simulation date in the future
HORIZONT
HORIZONT
TWS Interface – ISPF + Batch
The ISPF dialog is mainly used to generate batch jobs and consists of three parts:
Selection, Simulation, JCL Check
e.g. select from AD
Additional selection criteria
The result will be a list of job names in a file
HORIZONT
TWS Interface – Select from CP
The result will be a list of job names in a file
Additional selection criteria
Job creates a file
Without checking the jobs in the correct sequence, a JCL checker displays a message like „dataset not found“.
SmartJCL TWS Interface sort the jobs by planned start times and therefore they are checked in correct run sequence.
Job reads previously created files and creates other files
HORIZONT
TWS Interface – Forecast
The forecast creates a trial plan for any date in the future.
As always, the result will be a list of job names in a file
HORIZONT
Input is the list of jobs
If the select job did run and the joblist file has been created, the simulation can be started
The output file contains JCL of all jobs, sorted by planned start, all variable are resolved
HORIZONT
TWS Interface – JCL Check in Batch
Now you can start the JCL check of all previously selected and simulated jobs
HORIZONT
TWS Interface – JCL Check in Batch
The result is (optional) a detailed list of the JCL and it’s errors and a summary which contain all messages (including the standards check)
You may use the “migrated info” to recall required datasets automatically in advance
HORIZONT
Simulate Control-M variable substitution (AUTO-Edit Funktion)
Select the jobs to be checked by Table, Group, Application etc.
Besides TWS SmartJCL also supports Control-M.
It enables you to:
1 JOBLIST - Select jobs for simulation
2 SIMULATE - Start JCL simulation based on previous selection
3 CHECK - Start JCL check based on previous simulation
4 CHECK - Start JCL check without simulation
5 REFORMAT - Start JCL reformat (pre release)
Note: Options 3, 4, 5 are only available, if a JCL checker
is installed, for example SmartJCL
Control-M ISPF Dialog
Control-M Interface Mainpanel
Selection
Table ===> ____________________
Application ===> ____________________
Group ===> ____________________
Jobname ===> ________
Owner ===> ______________________________
Control-M ISPF Dialog
HORIZONT
JCL LIBRARY MODE
For simulation of private members enter Y: N (Y or N)
SCHEDULING LIBRARY MODE
For simulation of the jobs unloaded from the SCHEDULE LIBRARY.
Files
Control-M ISPF Dialog
Specify desired date
-----------------------------------------------------------
000002 //*%OPC SCAN
000005 //DD1 DD DSN=P390A.%%GROUP..%%NO,DISP=SHR
000006 //**************************************************
000008 //DD1 DD DSN=P390A.%%JOBNAME..LIST%%NO,
000009 // DISP=(,CATLG),SPACE=(CYL,(2,5),RLSE),
000012 //OUT1 DD DISP=SHR,DSN=P390A.%%JOBNAME..LIST%%NO
000013 //IN1 DD DISP=SHR,DSN=P390A.%%JOBNAME
****** ******************** Bottom of Data ****************
-----------------------------------------------------------
000002 //*%OPC SCAN
000005 //DD1 DD DSN=P390A.%%GROUP..%%NO,DISP=SHR
000006 //**************************************************
000008 //DD1 DD DSN=P390A.%%JOBNAME..LIST%%NO,
.HAAA // DISP=(,CATLG),SPACE=(CYL,(2,5),RLSE)
000009 //**************************************************
.HAAI //OUT1 DD DISP=SHR,DSN=P390A.%%JOBNAME
…must be substituted before Simulation.
Control-M Variables
-----------------------------------------------------------
000002 //*%OPC SCAN
000005 //DD1 DD DSN=P390A.TEST.LIST10,DISP=SHR
000006 //**************************************************
000008 //DD1 DD DSN=P390A.SIMJCL01.LIST10,
000009 // DISP=(,CATLG),SPACE=(CYL,(2,5),RLSE),
…in order to perform a correct validation
Control-M Variables
Define and select a joblib to select the job member
There is an extra ISPF dialog to run JCL checks for a set of jobs in batch or foreground
HORIZONT
Select the member and their sequence by entering a number
HORIZONT
JCL Validation – ISPF
Command BAT would generate a job to run the check in batch, command FORE run it in foreground
HORIZONT
JCL Validation – ISPF
The check is done, choose one of the reports, e.g. the summary
HORIZONT
JCL Validation – ISPF
The summary shows all messages, including your own standards check messages
HORIZONT
SmartJCL
ProcMan
ProcMan is a very flexible handover system, specifically for JCL and TWS objects
The workflow, verification and generation rules and the system environment configuration can be customized to your needs
The user are guided by a modern, easy to use web dialog
All objects and handover process data are stored in an archive. This helps auditors to verify the changes.
See extra “ProcMan - Product Presentation.pps”
HORIZONT
HORIZONT
www.horizont-it.com