Setting up a Datacom MUF with Automation Operations routines
Article ID: 375983
Updated On:
Products
Issue/Introduction
As more and more data centers are automating their processing, having the correct settings in an application can make the creation and use of automated operations (called AO) routines much easier. This article points out a few key topics to consider as you create or maintain your Datacom/DB or Datacom/AD MUF.
Resolution
Every company has its own requirements and standards for creating automated operations (AO) routines. Below are a few general points that will help your AO team be more effective in managing the Datacom environment.
Knowing that the MUF is up and active
To determine when the MUF is up and ready for work, you will look for the DB00201I message (see Formatting Messages topic below):
DB00201I - MULTI-USER ENABLED, CXX=MY15MUF MUFNAME=MY15MUF AD
Shutting down the Datacom MUF
To shut down the MUF, you can use the recommended /F MY15MUF,EOJ command, or you can use the more generic /P MY15MUF command. If you use the Stop (P) command, Datacom will turn it into the EOJ command internally and perform all the normal termination processing. Note that the order is important here, and you should not stop the MUF until all other tasks that use it are also terminated. So if your application has some job or STC running to use the MUF, it needs to stop first, then the MUF. Likewise, any TSO users that are connected to the MUF need to drop those connections before the MUF is shut down.
To help with this process, your AO team can build a routine to help you with shutdowns. They could issue a command /F MY15MUF,STATUS when it is time to shut down, and then they can parse the output. Here is a simple output:
DB01311I - STATUS
DB01327I - MULTI-USER AVAILABLE, TASKS - ATTACHED----10, AVAILABLE----90 08/26/24
DB01328I - TIME I/O JOBNAME R-UNIT TASK CMD-DBID-TBL SEQ STATUS ID
DB01330I - DLV1C530 41772 1 NOT ACTIVE 10
If you see any DB01330I messages, the Jobname (which is for STC and TSU also) will show who is connected to the MUF. In this sample, we need to stop DLV1C530 before we can shutdown the MUF. At one customer, the AO system had a hierarchy of Parent/Child relationships. Then, if you shutdown the Parent, the AO routines would also go through its database and shut down any Children tasks first (and of course, Children of Children, and so on). This makes it easier to start up and shutdown the tasks, like for an IPL for example.
Formatting Message IDs for MUF Messages
One thing that will make your AO routines easier is to format the messages differently. Currently, your MUF log may show messages like this:
10.04.08 STC19774 MY15MUF:DB00254I - message text goes here....
In order to use AO routines, you would have to specify the message ID as MY15MUF:DB00254I to find it. Since AO routines already know which job issues the message, you don't need the jobname attached to the message ID. In addition, by leaving off the jobname from the message ID, you can then create only a single routine member (here called DB00254I) that will handle every MUF. Of course, you can create specific instructions for specific MUFs in that routine if needed.
To be able to take advantage of this, change your MUF Startup Options for MUFMSG:
From MUFMSG YES,NO,NO
To MUFMSG NO,NO,NO
This is what will change. The current MUF log messages look like this (I have highlighted the Message ID that your AO routine would use):
10.04.08 STC19774 MY15MUF:DB00271I - AREAEV -YES, DATAFS -YES, DATAHU -YES, SU - NO
10.04.08 STC19774 MY15MUF:DB00270W - ACCESS TO DATACOM TABLES NOT PROTECTED BY EXTERNAL SECURITY
10.04.08 STC19774 MY15MUF:DB00226I - MULTI-USER ACTIVATED XCF SUPPORT (MY15MUFG,MY15MUF)
10.04.08 STC19774 MY15MUF:DB00201I - MULTI-USER ENABLED, CXX=MY15MUF MUFNAME=MY15MUF AD
10.04.08 STC19774 MY15MUF:DB00903I - OPENED, BASE - 2
10.04.08 STC19774 MY15MUF:DB00915I - CXX DBID 2 DATA-DICT DEFINITION VERSION 15.0 CHANGE LEVEL 0
10.04.09 STC19774 MY15MUF:DB00903I - OPENED, BASE - 15
10.04.09 STC19774 MY15MUF:DB00915I - CXX DBID 15 DDD-DATABASE DEFINITION VERSION 15.0 CHANGE LEVEL 0
And after recycling the MUF with the change, they will look like this:
10.04.08 STC19774 DB00271I - AREAEV -YES, DATAFS -YES, DATAHU -YES, SU - NO
10.04.08 STC19774 DB00270W - ACCESS TO DATACOM TABLES NOT PROTECTED BY EXTERNAL SECURITY
10.04.08 STC19774 DB00226I - MULTI-USER ACTIVATED XCF SUPPORT (MY15MUFG,MY15MUF)
10.04.08 STC19774 DB00201I - MULTI-USER ENABLED, CXX=MY15MUF MUFNAME=MY15MUF AD
10.04.08 STC19774 DB00903I - OPENED, BASE - 2
10.04.08 STC19774 DB00915I - CXX DBID 2 DATA-DICT DEFINITION VERSION 15.0 CHANGE LEVEL 0
10.04.09 STC19774 DB00903I - OPENED, BASE - 15
10.04.09 STC19774 DB00915I - CXX DBID 15 DDD-DATABASE DEFINITION VERSION 15.0 CHANGE LEVEL 0
I hope this short article is helpful for you and the AO team!
Feedback
