Simplify operations

• Automate archiving of the IMS MTO log

Using the BBI-SS PAS Journal log, automate the archiving of a machine-readable IMS MTO log. Daily, a time-initiated EXEC can switch and dump the Journal log at midnight. The dumped copy is then archived on some offline media. This eliminates the need for a hardcopy log.

• Document a shift turnover

Document a shift turnover with a time-initiated EXEC that issues a message to the BBI-SS PAS Journal, such as

SHIFT2 CHANGE AT 1600

The operator can send additional comments to the Journal by entering messages on the COMMAND line. By including the word SHIFT2 in each message, FIND (and REPEAT FIND) commands can be used by the next shift operator to find all related messages.

• Application programmers control IMS test system

Let application programmers use the MainView AutoOPERATOR application line commands, such as starting or stopping databases or transactions, to control the IMS test systems.

• Control DBR process

Ensure the deallocation of DBR databases occurs successfully. Issue the /DBR command from an EXEC and wait to receive the completion message within a specified time interval. If the completion message is not received, send an ALERT to the STATUS/EXCEPTION display. A sample EXEC that performs this function is included in the BBUSER library and it is named IMAGE1.

You will need a second EXEC to process the DFS0488I message. This EXEC can be scheduled from a Rule and can set a variable to indicate the deallocation is successful. The first EXEC will check the value of the variable after the waiting interval expires. A sample for the second EXEC is named DFS0488I EXEC and included in the BBUSER library. Setting the value of the variable can be done in the DFS0488I Rule itself, so if the EXEC does not perform any other complex automation, it can be eliminated.

• Establish additional recovery points

Establish additional recovery points when necessary by forcing an OLDS switch with a /DBR command against a dummy database such as the sample database DI21PART.

• Automate stopping regions

Save message region numbers at region startup (by using EXEC DFS551I) so that the region can be stopped automatically at the proper time. Issue the /STOP REGION command with the region number (jobname not allowed).

As an alternative, you can use a DFS551I message-initiated Rule to set a variable value to the message region number and eliminate the need for an EXEC.

Note: Refer to the OSPI Application in the MainView AutoOPERATOR Advanced Automation Guide for alternative methods of stopping regions.

• More meaningful messages

Change the text of the messages sent to the STATUS/EXCEPTION display so that they will be more meaningful to the operator. For example, if an MSC link goes down, provide the name of the system or location of the link partner, rather than only the internal number.

• Automate an on-call list

Automate the tracking of people who are on call. Set up an EXEC to run at BBI-SS PAS startup and at shift change to set global variables identifying the on-call personnel responsible for that time period.

For example, global variables for the payroll-dba or the IMS-SYSPROG can define the name, TSO ID, work extension and home phone number. All other EXECs then refer to these global identifiers instead of to specific information that continually changes. This single list is easily updated. It can be flexible enough to differentiate between workdays and weekends, holidays, or other special conditions.