|
|
|
When a program establishes a connection with the MUF for the first time through a User Requirements Table, the MUF issues the following job-started message in the program's message log:
The DB00101I message can be followed by either of the following messages if the job referenced in the DB00101I is executing from another environment using XCF or CCI as its communication protocol.
Contained in the message is additional information such as the following:
A similar message is issued when the first online User Requirements Table is opened. In CICS, the RUN-UNIT is in effect until all online User Requirements Tables associated with the CICS are closed (usually the whole session). For this reason, all CICS tasks also include a SUB RUN-UNIT number that uniquely identifies each CICS transaction within a CICS session.
When a program completely drops connectivity with the MUF, the following job-ended message is posted in the MUF region. You receive this message only if you have installed CA Datacom CICS Services. CA Datacom/AD Version 14.0 does not deliver CA Datacom CICS Services. It was delivered in CA Datacom/AD Version 12.0.
The message shows the job name, RUN-UNIT number, and other items. You can use the RUN-UNIT number on the DB00101I and DB00102I to determine when a job started and stopped.
Once the MUF is up, you can begin to run jobs that request CA Datacom CICS Services.
At any time, you can run a batch job or enter a console command to request the current status of the MUF. This status provides specific information on all jobs currently accessing the MUF. We recommend that two to three STATUS commands be issued to see progress over time. For more information about this function, see the description of the DBUTLTY COMM OPTION=STATUS or the COMM STATUS command in the CA Datacom/DB DBUTLTY Reference Guide. AD14COMM is a sample JOB that is provided. CA SYSVIEW can optionally be used to monitor the activity within the MUF.
Sample Report
Following is a sample report page. For an example report header, see Sample Report Headers.
MULTI-USER DBDVM02 AVAILABLE TASKS - ATTACHED-----1, AVAILABLE----24 JOBNAME R-UNIT TASK STATUS CMD DBID TBL SEQ TIME I/O ID TSN OWNR/Y TSN-TM DBDVL132 14160 1 READY TO RUN ADDIT 997 C02 95727 DBDBBBDA :01 JOBNAME R-UNIT TASK VALUE/RID STATJOB2 33654 1 1 PAY
The main purpose of the DBUTLTY AUTOINFO function is to allow you to choose a given MUF and quickly generate information about that environment. This information can be helpful for you and for your communications to Technical Support about a MUF problem.
AUTOINFO should be executed while the MUF is experiencing the problem. However, AUTOINFO can be executed after the MUF has come down or has been cycled. While it will not furnish as much information about a particular situation that occurred in the previous MUF execution, it still provides valuable environmental information.
Sample Report
Following is a sample report page. For an example report header, see Sample Report Headers.
MUF IS AVAILABLE, INFORMATION IS PROVIDED BY THE MUF. MUFNAME: MUF4 RELEASE: 14.0 JOB/STC NAME: QA12MUF4 CXXNAME: QAMUF4 JOBID: JOB11528 SYSTEM: CA31 ENABLED TIME: 2008/11/11 13:12:17 CURRENT MUF TIME: 2008/11/11 13:14:59 MUF IS SHADOW: N MUF HAS SHADOW: N DB SUBSYS PRESENT: Y SQL: Y EXTERNAL SECURITY: N ACCOUNTING ON: N
DBIDS: DST: 1000 HISTORY: 1007 CBS TEMP: 0006 CBS HEUR: 1006 TASKS: TOTAL: 00250_ XCF: 00250_ CCI: 00050_ SIZE: 46080_
If AUTOINFO is executed after a MUF has ended but has not been restarted, the function ends with a U0004 condition code. This notifies you that while the report has executed, certain data was not available.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |