Tags
abend, application, automation, batch, COND, JCL, job, kedb, mainframe, MAINFRAMES, only, RESTART, restartable, self, self-restartable
In my previous article, we have gone through about KEDB (Known Error Database) and how much it helps to resolve repeating issues/abends and saves time. To amend to that, I have found an article that discusses on how a mainframe application can be made self-restartable. The approach seems to be promising and can be used for various applications but will need a thorough thought process, time and quite an effort to build it. But it has lot of benefits once it is built.
Whenever a job fails, below are the manual steps that we would do
- Find the type of problem (Data issue, Code Issue, System Issue)
- Identify where to restart the job. Sometimes we need to restart from prior steps. (KEDB helps here)
- Data/File fix might be needed before restart
- Restarting the job from correct step
Noe for making the mainframe application self-restartable, all the above manual steps needs to be automated. And to automate, we would require few components
- A KSDS File to hold list of all job names/step names
- Additional JCL step in each job that needs to log the step of the job when it fails (using COND = ONLY)
- Program to determine the failure step and do the housekeeping activities for the restart (KEDB helps here)
- Program to restart the Job as desired based on restart instructions
Go through this Referenced Article to get an detailed overview
——————————————————————————————————–
In United States, If you would like to Earn Free Stocks, Credit card Points and Bank account Bonuses, Please visit My Finance Blog
——————————————————————————————————–
You may also like to look at:
F1 for Mainframe 