Description:
Is there a way to verify that the connection between CICS and Datacom MUF is active? Is there a CICS transaction and/or MUF transaction that displays the connection? Where is the connection defined to both CICS and MUF?
Solution:
Here are some things you can use to see if there is a connection between the Multi-User Facility (called MUF) and the CICS region.
In the JESMSGLG for the CICS region, you might see a message like this:
DC00118I - Advantage CA-Datacom CICS Services STARTED BY xxx
This indicates that either a user (with OPID xxx) or the PLT processing loaded the programs to establish a connection to a CA Datacom/DB MUF.
Along with this message, you might see a message like this:
DB00135I - CONNECT TO mufname mufname JOB36442 sysid R12 SP0
This indicates that this CICS region connected to the MUF called mufname running with the JOBID/STCID on LPAR sysid. This MUF is at version R12 SP0.
Then you might also see this message:
DB00101I - STARTED JOB-cicsregn NUMBER-89440 CXX=cxxname MUFNAME=mufname SVC=239
This shows that the connection was opened by the CICS region cicsregn with the Run Unit number 89440 to the MUF called mufname which is running with a CXX named cxxname.
Now, in the JESMSGLG for the MUF, you might see a message like this:
DB00133I - JOB OPEN cicsregn 89440 userid JOB36449
This shows that the cicsregn job/STC opened a User Requirements Table using Run Unit 89440 under the security id userid with the JOBID/STCID JOB36449.
These above messages show the various "startup" connection messages. To know what is currently connected to the MUF, you can issue this z/OS console command:
/F mufname,STATUS
You will get the status of everything connected to the MUF, including CICS regions. The output of this command is usually placed on the console, and is also in the JESMSGLG of the MUF. It might look like this:
DB01311I - STATUS DB01327I - MULTI-USER AVAILABLE, TASKS - ATTACHED----12, AVAILABLE----24 DB01328I - TIME I/O JOBNAME R-UNIT TASK CMD-DBID-TBL SEQ STATUS DB01330I - cicsregn 89440 1 NOT ACTIVE 12
This shows that only cicsregn is connected to the MUF, and has 12 concurrent tasks available in that CICS region.
In z/VSE you run this STATUS console command via :
MSG partition-id where the MUF runs
You get a reply-id back and then enter that reply-id number STATUS .
It might look like this :
MSG F2 AR 0015 1I40I READY F2-0453 DB01300A - ENTER MULTI-USER COMMAND 453 status F2 0453 DBMUF11:246:1:DB01327I - MULTI-USER AVAILABLE, TASKS - ATTACHED-----8, AVAILABLE-----4 02/24/14 15:30:34 F2 0453 DBMUF11:246:1:DB01328I - TIME I/O JOBNAME R-UNIT TASK CMD-DBID-TBL SEQ STATUS ID TSN F2 0453 DBMUF11:246:1:DB01330I - CICSDB11 67257 1 NOT ACTIVE 8
Now, if you are in the CICS region, you can issue the command:
DBOC INQ=GENOPTS
The transaction-id could be DBOC or DBIC, or you might have changed this to another transaction in your site.
The return to the screen will look like this:
DBOC INQ=GENOPTS DELIM & Advantage CA-Datacom CICS Services r11 Service Pack(SP01) (C) 2004 Computer Associates International, Inc. 07/10/06 OPSYS=Z/OS 1.13 CICS LEVEL=TS 4.1 DB RELS=12 SP0 DB SVCID=239 SUB ID=255 MUF JOBNM=mufname MAXURTS=0500 PREFIX=DBURT DYNPPT=NO USERS=012 SKIPURT=NO LOG=(YES,NO ) SYSVIEW=NO PLANSWI=NO USERID=NO TRACE=(ON ,01000) AUXTRACE=OFF AUXTRACE LOG=DCAX DELIM=& MSGLOG=DBOC SCROLL=(AUTO SEC 10) DBEC=DBEC DBEX DBRC DBOC=DBOC DBIC DBUG=DBUG DBFS DBTS=DBTS DBTX REQTHD=00000 EXEMPT TRANS=DBOC OPERID=*** DC00380I TRANSACTION COMPLETED.
In this display, the right column shows that this CICS region is connected to a version 12.0 MUF called mufname. You can also see half way down the first column USERS=012, to coincide with what we saw on the MUF STATUS command.
The connection is made from the CICS region to the MUF through the product CA Datacom CICS Services, and a customized module called DBCVTPR, that specifies all system generation options for CA Datacom CICS Services. This module identifies how many connections can be open, what users can make changes, etc. It is linked into the CA Datacom CICS Services CUSLIB, which is added to the CICS DFHRPL along with the CA Datacom/DB CUSLIB. It is through a call to the DBSIDPR module in the CA Datacom/DB CUSLIB that connection is made to the proper MUF.
In summary, the CICS region runs CA Datacom CICS Services programs to build connections to the MUF identified through the CA Datacom/DB DBSIDPR module, and through a handshake between the CA Datacom CICS Services and CA Datacom/DB products, allows the CICS region to open and access the databases in the MUF.