DBOC/DBIC: Monitoring Local Resources with Operational Commands › INQ=urt/INQ=limiter: Displaying URT Information › Display Example: DBOC INQ=FAIL

Display Example: DBOC INQ=FAIL

The following example illustrates a limited URT Inquiry display, where the limitation is on the URTs with a failure on the last open or close.

 DBOC INQ=FAIL                                                         DELIM &
 
      (1)  (2)     (3)    (4)            (5)             (6)      (7)      (8)
 URT 0060(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD=NO
 URT 0061(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0062(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0063(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0064(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0065(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0066(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0068(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0069(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0070(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0072(STD UNOPENED      ) CLOSE FAILED RC25 020 PRTY=07 TXNUD
 URT 0100(STD UNOPENED      ) CLOSE FAILED RC02 052 PRTY=07 TXNUD=NO
 DC00380I  TRANSACTION COMPLETED.

Field Descriptions

The URT Inquiry panel displays one row of information per URT, where URTs are listed in ascending order by URT-suffix. Information includes URT characteristics such as type, status, and when to open, pertinent messages such as the number of active tasks for an open URT, and how the URT is defined in its DBURSTR macro.

Interpreting Displayed Data

Use the following guidelines to interpret the display. URT characteristics are labeled by fields as they were on the report. See the information about online URTs in the System Reference Guide.

Œ

The range of numbers which can appear as URT suffixes is limited by the MAXURTS= value specified in the System Option Table (DBCVTPR). For details on the MAXURTS= parameter, see the System Reference Guide.



The origin of the Type characteristic is the DBUREND macro parameter DBSQL= in the URT definition. If DBSQL=YES, SQL appears. If DBSQL=NO and you defined a URT with the displayed number, STD appears. If DBSQL is NO and you have not defined a URT with a number within the range 0001-nnnn (see the System Reference Guide descriptions of the MAXURTS= and PREFIX= parameters for details about the nnnn 4-digit suffix), that URT number is eligible for use by a CA product for dynamic generation. If so used, DYN appears. If not so used, HAVE NO CSD ENTRIES appears in the Usage/Reason Not Used field.

Note: For more information about the DBSQL= parameter, see the chapter on defining a URT in the CA Datacom/DB Database and System Administration Guide.

Ž

The only Status characteristic controlled by a definition is UNOPENED. Only a URT defined with AUTO= or DEFER= can exist in UNOPENED status. Once a URT is open, it remains open until CA Datacom CICS Services is shut down unless explicitly closed through a DBOC or DBEC CLOSE= command.



Except for URTs specified for delayed opening, CA Datacom CICS Services opens all URTs at system startup. In the DBCVTPR macro, two lists of URTs may be identified for delayed opening with AUTO= and DEFER= respectively, those to open automatically when required by an application for its processing and those to defer opening until requested by a DBOC or DBEC OPEN= command.

To add to the list of URTs which open automatically, see AUTO= Setting URTs for Automatic Opening. To add to the list of URTs which only open when a DBOC OPEN= command is issued, see DEFER= Setting URTs for Deferred Opening. To return URTs to their original automatic open or deferred open state (as specified in DBCVTPR), see RESTART= Returning URTs to Initial Status.



If the table is open, its current usage can be determined by examining the ACTIVE= and RESRVD= data.

The presence of an OPEN FAILED or CLOSE FAILED entry indicates a processing failure. Take the action suggested in the CA Datacom/DB Message Reference Guide for the displayed CA Datacom/DB return code.

If INVALID, recompile the module to create a valid online URT. See the information about online URTs in the System Reference Guide.

If NOT LINK EDITED, either remove this URT name from the CICS System Definition data set (CSD) or link edit the assembled URT macros to produce a load module which resides in the searched load library.

INVALID, DISABLED, NOT LINK EDITED, or SKIPLOAD and HAVE NO CSD ENTRIES (or HAS NO CSD ENTRY) appear when the following conditions apply:

• you have disabled a CSD entry
• the load module is not in the DFHRPL
• the URT has been specified in a SKIPLOAD macro in the DBCVTPR as not to be loaded
• no entry in the CICS System Definition data set (CSD) for these or this URT within the MAXURTS= range

• This message is for information only.

  Example:

   DBOC INQ=FAIL                                                         DELIM &
   
         Œ          Ž                                  ‘       ’        “
   URT 0014(STD UNOPENED AUTO )                       PRTY=07 TXNUD=NO
   URT 0015          HAS NO CSD ENTRY   
   URT 0016(STD UNOPENED AUTO )                       PRTY=07 TXNUD=NO
   URT 0017-0019     HAVE NO CSD ENTRIES   
  

‘ ’ “

The DBURSTR macro parameters PRTY=, TXNUNDO=, and TIMEMIN= or TIMESEC= can be changed by altering values and reassembling and relinking the URT. A low priority task (PRTY=1) which has a resource under exclusive control could tie up that resource indefinitely, the avoidance of which is a good reason to specify TIMEMIN= or TIMESEC= in DBURSTR rather than accepting the default of zero. If the default is used for this URT, no entry appears for ECWAIT=. A low priority task with transaction backout specified (TXNUNDO=YES), can force checkpointing in the Log Area(s).

Note: For more information, see defining the user environment in the CA Datacom/DB Database and System Administration Guide.