home-JST    JST-mf
AutoJob    StdJob    DTASup    top bottom

JST JCL Mainframe


Jaap working

JCL script Structuring

In the old days everything was on Hollerith cards. After migration eliminating these physical artifacts mostly nothing has changed very much. Just in some rare cases some modern approach has been implemented.

The change in this is a structured JCL approach I designed with others. Split up the old Job´s into basic building blocks and reuse them in every job.
The cost saving in time is obvious. Doing something once instead by different people the same thing over and over again. Still it is difficult to get it accepted. Remember: You are (I´m) automating the daily work of some more persons.

Subjects

Words of thank to colleagues

We had a lot fun in stressfull times working out this on the mainframe in the nineties.
J.Pak codesigner of the common job approach.
D.Roekel inventing more proc-bodies faster than me.
J.Hofman P.Grobbee working it out smoothly to testers and many more people te mention.




Structure Automated JOB Processing

JCL (Job Control Language) is the script tool in a classic IBM Mainframe used to run processes for the business. It can also be used for a lot of other code to run. Before you can do anything to optimize the JCL process running business processes you must structure the way of how JCL is coded. An approach with Bodies-Frames, procedure bodies, input- output definitions is described.

There are many types leading to some work, Al list of types is:
Design JST The common Job script is the one that can be used in production environments
For support in D,T,A you need a lot of tools and other processes top be defined like

JST generating JCL

At the moment you have structured JCL, you can define a generated process to build JCL (D,T,A,P). This is where JST is used for.
The design looks at little bit complex, the basics are (red arrow optional selections)

JST running test plans

At the moment you have structured JCL and have a generated process you can work with an automated test process (D,T A). This is where JST is used for.
The solution is as simple as can be, submit the job within you test plan.


AutoJob    StdJob    DTASup    top bottom

Standard JCL JOB procedures

Structured scripting

Related to all scripts

header trailer Header
This defines all settings to run a job. All
header trailer Trailer



Structured scripting

Common Job script

This is the one you can reuse the most. It is describing the steps that defines the steps processes the business wants.
It consists of: >

body frame Bodies-Frames
This is a set of basic steps using the bodies and data definitions. It will make up the resulting JOB.
To define its contents is a business layer responsibility
procedure body procedures Bodies
To be used by Business development. Support by functional owner of infra level component.
These are the basic JCL procedure steps, like: Within the sample picture just 5 steps are used. The number of steps can vary between one (1) and many(*)
ddio1 ddio2 ddio3 Data Definitions

You need somehow to define the datasets output/print/mail databases transfers to be used. These definition may not be present hard coded in business logic code In that case no develop testing acceptance would be possible. Making some definition variable in JCL variables defined by the DTAP header solves this issue.


AutoJob    StdJob    DTASup    top bottom

DTA support procedures

Structured scripting backup restore

Backup Restore script D, T, A,

This feature is essential to D,T,A Test environments.
To allow many testers to work parallel testing should be possible (D,T)

body frame Infra-Process
The responsibility to functional support is an infrastructure task. It is used like a production tool in these environments.

Also within A the business data can be different to it´s usage goal, as there are:



Structured scripting dedicated dbms

Dedicated DBMS script D, T, A,

This feature essential to D,T,A Test environments.
To allow many testers to work parallel testing should be possible

body frame Infra-Process-procedure special
The responsibility to functional support is an infrastructure task. It is used like a production tool in these environments.

The difference to backup restore support is: This implementation can be much more challenging is the complexity of startup DBMS support requires to do so.




AutoJob    StdJob    DTASup    top bottom
home-JST    JST-mf

© 2012 J.A.Karman (16 feb 2012)