Checklist Tool

Español

Date and time:

Purpose

This tool was created to work on a z/OS system. The main purpose of this tool is to shorten the time spent every day checking our machines and all the environments we monitor before finishing each shift.

In my client's system, there are 7 environments in which we manage. Four of which are multiplex, the production SYSPLEX is formed by 9 LPARs. There are 7 IMS subsystems and 15 DB2 subsystems, due to huge amounts of data and jobs that are managed every day.

By using this checklist tool, BBVA is saving at least 45 minutes per shift avoiding having to check that everything is in order manually. Now that this is being done in 15 minutes, this allows for the operators to attend other tasks, which adds up to more than 10 hours per week of extra productive time.

How It Works

As you can see in the gif below, we execute the tool by typing from any command line ''TSO CHECK''. There are different options that can be displayed by typing its number in the field, here we are using the last option that checks all at once. This is the option that we use the most to check everything before finishing our shift. Watch the gif to see how the tool shows the results, and how it changes to the next results each time you push F3 (Exit key).

Below, you can see more details about how each option accomplishes its function. Please, don't hesitate to contact me if you have any questions.

Some Code

The utility is mainly coded in REXX language, apart from two ISPF panels and a couple of JCLs used to get information from our Workload Scheduler. The tool can easily be implemented in other z/OS environments by simply modifying a few filters for the appropriate task names and, in addition, it can be modified as any client desires.

In the gif below you can see is how I have the REXX EXECs and panels organized. There are adequately different actions performed by each of these members (for example executing IMS or System commands, reading the SYSLOGs or the IMS Jeslog, checking active jobs, and more).

List of Options
CHECK STOPPED TASKS
This option executes the AUTOOPERATOR commands to check if there are any stopped tasks, then reads the SYSLOG to get the messages.
CHECK JOBS ON THE READY LIST, OPTION 4.1
This option executes a JCL that gets the jobs from the scheduler that need to be released manually.
CHECK ENDED-IN-ERROR JOBS TO COMMENT
By using this option we can see the failed jobs that need to be commented to the next shift for their knowledge. Accomplished by executing a JCL to get the info from the scheduler.
CHECK PENDING SYSTEM REQUESTS
This option gets the Pending System Requests and compares them with the ones that are always on the system, which have been prepared manually in a list, and just shows the unusual ones.
CHECK GRS CONTENTIONS
This option executes the system command and shows us the Global Resource System Contentions.
CHECK JES2 RESOURCES USAGE
This option is used to see the usage of the spools, command pool, and other resources, just showing us the ones that are over their 50% of their capacity. This is done by reading the info from the option in SDSF.
CHECK JOBS ON THE INPUT QUEUE
This option will allow us to see quickly just the anomalous jobs on the Input queue. Achieved by reading the jobs in the Input queue and checking their status and WLM classes.
CHECK RUNNING SHIPPING JOBS, K AS ITS FITH CHARACTER
Because of this option, we can see if any file transmission is taking more than 10 minutes to be executed.
CHECK DB2 TABLES IN A RESTRICTIVE STATUS
This option filters a file that AUTOOPERATOR prepares each hour and gets just see the DB2 and their tables if they are in a restrictive status.
CHECK IMS ONLINE LOG DATASETS
This option just shows the Online Log Datasets that are “In Use” to see the percentage and others if they are in an irregular state. This is done by executing an IMS command and reading the log of the task.
CHECK IMS STOPPED DATABASES
As the option above, this one executes an IMS command and read the log of the task to show as the stopped IMS databases.
CHECK IMS STOPPED REGIONS OF THE SYSPLEX
This option shows us if there is any IMS region inactive, by comparing the regions launched during the start of IMS with the ones that are active in the system.
CHECK STOPPED TRANSACTIONS, AVOIDING LOCK ONES
As the options before, here we see the transactions that are stopped after executing a IMS command and getting the result from the IMS log.
CHECK EVERYTHING AT ONCE, PRESS F3 TO LEAVE EACH PANEL
The option that is most used, executes everything in batch mode showing a result each time.