Testing CICS connection to CA Datacom/DB MUF

book

Article ID: 196856

calendar_today

Updated On:

Products

CA Datacom CA Datacom/DB CA Datacom/AD

Issue/Introduction

This article discusses two methods of testing CICS connectivity to a CA Datacom MUF when the MUF is running before CICS starts, and when the MUF is not running.

 

Environment

Component : CA DATACOM CICS SERVICES

 

Resolution

This process assumes that the proper PLTPI (CICS startup Program Initation) configuration has been used.

Test #1 - Starting the CICS region when the MUF is already running:

  1. Start the MUF as usual
  2. Start the CICS region
  3. Look in the CICS log for this message:
    DC00118I - CA Datacom CICS Services 15.0 STARTED BY         PLT
    showing that the PLT initialization has completed for CA Datacom CICS Services. You should also see messages like this
    DB00135I - CONNECT TO ...
    DB00101I - STARTED JOB-...
    to show that the region is connected to the MUF
  4. In the CICS region, issue DBOC INQ=GENOPTS and see if the values are correct.

Test #2 - Starting the CICS region before the MUF is started:

  1. DO NOT Start the MUF yet
  2. Start the CICS region
  3. Look in the CICS log for this message:
    DC00118I - CA Datacom CICS Services 15.0 STARTED BY         PLT
    showing that the PLT initialization has completed for CA Datacom CICS Services. You should also see messages like this
    DB00121I - UNAVAILABLE - ...
    DB00122I - ACCESS TYPE - LOCAL ...
  4. Now, start the CA Datacom MUF
  5. In the CICS region, issue the command
    DBEC P,CONNECT,MUF(??)
    and you should get a list of MUFs connected to this region
  6. Look in the CICS log to see the connected messages:
    DB00135I - CONNECT TO ...
    DB00101I - STARTED JOB-...
  7. In the CICS region, issue DBOC INQ=GENOPTS and see if the values are now correct.

 

 

Additional Information

As always, please contact Broadcom support for CA Datacom if you have further questions.