Requests for information about MUF or MSIDname resources are issued with the DBEC or the DBEX transaction followed by the INQuire operand. The options enable you to invoke a display of all MUFs or selected MUFs by criteria or generic number (MUF) or MUFNAME (MSIDname). If you issue the command with the DBEX transaction ID, you cannot update any information on the resulting scrollable display. One of the only allowable entries in the Action field is an S, which toggles to the URT-level display to show all the URTs for the MUF of the selected entry. The other allowable entries are E to display the return code summary, T to display active tasks, and U to display the task usage summary. If you issue the command with DBEC, you can alter certain fields on the panel.
The following is an example of a MUF definition appended to the DBCVTPR macro. This only needs to be coded if you need to access multiple MUFs, since the basic DBCVTPR parameters define a single MUF. A MUF definition is made with a DBCSID macro, each entry appended to the DBCVTPR macro defining a particular CA Datacom/DB MUF. The MUF (or MSIDname)-level display reflects the order of the DBCSID macros. The values for the bold-faced parameters in this example are displayed on the MUF-level inquiry.
DBCSID SIDNAME=DBSIDPR,USERS=3,CONNECT=PLT,EOJ_OK=DISCONNECT
Invoke the following transaction to display the status of CA Datacom/DB MUFs.
Note: The status of any MUF displayed in this manner is current as of the time of the last request processed by that MUF. For example, if the last request processed by a MUF was 90 seconds ago, a DBEC I,MUF (or DBEX I,MUF) or DBEC I,MSIDname (or DBEX I,MSIDname) request displays the status of that MUF as it was 90 seconds ago.
►►─┬─ DBEC ─┬┬─ INQuire,MUF(nn) ───────────┬┬──────────┬─┬────────────┬────────►◄ └─ DBEX ─┘└─ INQuire,MSIDname(xxxxxxxx) ┘└─ ,STATS ─┘ └─ ,limiter ─┘
(Required) Specify a transaction ID valid with Enhanced commands used to monitor MUFs. Select the transaction ID for which you are authorized. Leave a space between the transaction ID and the command.
(Required) Requests a scrollable display of MUFs. (INQ and I are valid abbreviations.)
(Required) Specifies the inquiry is to invoke the MUF-level display. The value within the parentheses identifies the number of the MUF relative to the order of the DBCSID macros appended to the DBCVTPR macro, if multiple MUFs are defined. MSIDname(xxxxxxxx) is ignored if it is also specified as a MUF qualifier.
Specifies that you want to display only the MUF with the specific 2-digit number nn.
Alternately, instead of using the nn number to specify only a specific MUF, you can use the wildcard symbol ? (a question mark) to accept any digit 0—9 for one (or both) of the two digits of the number.
See Command Examples.
(Required) Specifies the inquiry is to invoke the MUF-level display. The value within the parentheses identifies the MUFs identified by the SIDNAME specified in the DBCSID macros appended to the DBCVTPR macro, if multiple MUFs are defined. The MUFs that meet the qualification of your request are presented in the order that they are defined in the DBCSID macros of the DBCVTPR. If the MSIDname(xxxxxxxx) qualifier is specified with the MUF(nn) qualifier then this parameter is ignored.
Specifies that you want to display only the MUF with the SIDNAME specified as defined for the DBSIDPR module name xxxxxxxx for this MUF.
Alternately, instead of using the xxxxxxxx name to specify only a specific MUF, you can use the wildcard symbol * (asterisk) to accept SIDNAMEs that begin with a specific value. The asterisk represents any trailing characters in the SIDNAME.
See Command Examples.
Note: Choose either MUF(nn) or MSIDname(xxxxxxxx). If they are both specified, the MSIDname(xxxxxxxx) parameter is ignored and the qualification is assumed by MUF(nn). Use the one to qualify the MUF inquiry in the manner that meets your needs.
(Optional) Requests a scrollable display of MUF-level statistics for requested MUFs.
(Optional) Limits the inquiry to MUFs of the designated status, how defined for opening, or to request the MUF-level statistics display. The following are the values for designating limiters of each type:
|
Limiter Type |
Valid Values |
Description |
|
Status |
DISconnect |
MUFs explicitly disconnected through a DBEC command. (DIS is a valid abbreviation. |
|
|
DISCONNECTING |
MUFs with a disconnect in progress, where disconnect is invoked at the completion of the current read or update. |
|
|
CONnect |
MUFs that are currently connected. (CON is a valid abbreviation.) |
|
|
CONNECTING |
MUFs with a connect in progress. |
|
|
UNConnected |
MUFs defined as AUTO or DEFer that have not been connected by a program call, PLT, or a DBEC transaction. (UNC is a valid abbreviation.) |
|
When |
AUTO |
MUFs defined to be connected when required by a program or a URT open. |
|
|
DEFer |
MUFs defined to be connected only by an explicit DBEC command. (DEF is a valid abbreviation.) |
|
|
PLT |
MUFs opened at CA Datacom CICS Services startup and not defined for AUTO or DEFer. |
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|