Candidate subsystem messages for monitoring

Certain messages that are issued by IMS and its component subsystems can be critical to detecting problems early and identifying their root cause.

The following sections contain example lists of subsystem messages that are candidates for monitoring in the IMS environment.

Important: Use the lists only as an example when determining which messages to monitor in your own IMS environment. The lists contain only a small subset of all of the messages your installation might need to monitor. The lists also might contain messages that your installation does not need to monitor.

The lists are organized into the following sections:

Messages that are issued in all IMS environments. These are typically messages that are issued by the IMS control region or system components.
Messages that are issued by IMS DB components. These messages can be issued only in DB/TM and DBCTL environments.
Messages that are issued by IMS TM components. These messages can be issued only in DB/TM and DCCTL environments.

Some sections contain separate lists for optional components that run in a given environment.

Messages to monitor in all IMS environments

The following messages are related to IMS system components and processing, so can be issued in all IMS environments.

DFS0414I CONTINUING WITH ALTERNATE LOG
DFS629I IMS ttt TCB <action> IMS|SYS sss|uuuuvvvvIMS ttt TCB <action> IMS|SYS sss|uuuuvvvv or IMS BATCH REGION ABEND - IMS|SYS uuuu or PSW AT ERROR = hhhhhhhh hhhhhhhh or MODID = cccccccc EPA = aaaaaaaa or IMS DBC REGION ABEND
DFS0738X ERROR TERMINATING OLDS RC=xx dddddddd nnnnnnn
DFS2867A EXTERNAL TRACE NOT USABLE, REPLY "Y" TO USE OLDS, "N" TO TRACE INCORE
DFS3258A LAST ONLINE LOG DATA SET IS BEING USED - NEED ARCHIVE or SYSTEM WAITING FOR AN ONLINE LOG DATA SET - NEED ARCHIVE
DFS3262E NO DATA SET AVAILABLE FOR LOG WRITE AHEAD
DFS3306A CTL REGION WAITING FOR csltype
DFS3785E DIAGNOSE AWE INITIALIZATION FAILED – reason_text
DFS3786E DIAGNOSE AWE PROCESSING ERROR – reason_text
DFS3787E DIAGNOSE SYSOUT PROCESSING ERROR – reason_text
DFS555I RAN tttttttt ABEND (SYSID sss); REASON=reason; MSG IN PROCESS: xxxx (up to 78 bytes of data) time-stamp
DSP0014I DYNAMIC ALLOCATION FAILED FOR RECONn RETURN CODE=xx REASON CODE=xxxx
DSP0027I ddname DATA SET IS FULL
DSP0256I NO SPARE RECON DATA SET AVAILABLE
DSP1135A SCI REGISTRATION FAILED, IMSPLEX NAME=nnnnn, RC=xxxxxxxx, RSN=yyyyyyyy, JOB=jjjjjjjj
DSP1141I RECON LOSS NOTIFICATION RECEIVED, JOB=jjjjjjjj
DSP1145I RECON LOSS NOTIFICATION NOT SENT, JOB=jjjjjjjj
DSP1147I DBRC REGION WAITING FOR SCI, IMSPLEX NAME=ppppp
DSP2002E DBRC INITIALIZATION ERROR IN modulename servicename RC=rc detail

IMSRSC repository messages:

DFS4409A REPOSITORY CHANGE LIST IS NOT ACCESSIBLE - IMS RESOURCES MAY BE OUT OF SYNC
DFS4411E REPOSITORY CHANGE LIST PROCESSING FAILED RC=rc RSN=rsn
DFS4413E REPOSITORY CHANGE LIST PROCESSING FAILED FOR RSCNAME=rscname RSCTYPE=rsctype CC=cc

Messages to monitor in DB/TM and DBCTL environments

The following messages are related to IMS DB components and processing, so can be issued only in DB/TM and DBCTL environments.

DFS047A UNABLE TO OBTAIN AUTHORIZATION FOR DATA BASE xxxxxxxx. REASON CODE = zz. PSB= psbname.
DFS0565I cccc COMMAND NOT PROCESSED DB=xxxxxxxx IN USE BY PSB=psbname, REG=region-number
DFS691I WAITING FOR CTL xxxx - yyyyyyyy
DFS0730I UNABLE TO OPEN OR CLOSE DATASET WITH DDNAME ddname FOR REASON x, yy, z DATABASE dbdname programid
DFS0811A UNABLE TO OBTAIN GGG GIGABYTES OF 64-BIT STORAGE FOR THE ACB POOL. REASON=xxxx
DFS0844I modulename dbname DATASET FULL, DDNAME=ddname
DFS0845I dbname DATASET LIMIT REACHED, DDNAME=ddname
DFS981I DBD=dbdname WITHIN PSB=psbname STOPPED DUE TO (BACKOUT FAILURE|ERE NOBMP START|COLDBASE START|REMOTE TAKEOVER)
DFS2011I IRLM FAILURE - IMS QUIESCING
DFS2012I GLOBALLY SHARED DATA BASE|AREA - dbdname|areaname STOPPED or SHARING DATA BASE(S) STOPPED BECAUSE DATA SHARING DISCONTINUED
DFS2503W DYNAMIC ALLOCATION|DEALLOCATION| CREATION| DELETION FAILED FOR DATA SET NAME xxxxxxxx.xxxxxxxx.xxxxxxxx DATABASE NAME dbdname REASON CODE yyyyy
DFS3867A NOTIFY REQUEST TO SET AN ADS TO AVAILABLE STATUS FAILED FOR AREA=xxxxxxxx DD=yyyyyyyy
DFS4164W FDR FOR (imsid) TIMEOUT DETECTED DURING LOG AND XCF SURVEILLANCE

Messages to monitor in DB/TM and DCCTL environments

The following messages are related to IMS TM components and processing, so can be issued only in DB/TM and DCCTL environments.

DFS271 UNABLE TO LOAD ERROR MESSAGE OUTPUT DESCRIPTION
DFS2013 NUMBER OF RECORDS IN QBLKS DATA SET HAS EXCEEDED UPPER THRESHOLD
DFS2014 NUMBER OF RECORDS IN SMSGQ DATA SET HAS EXCEEDED UPPER THRESHOLD
DFS2015 NUMBER OF RECORDS IN LMSGQ DATA SET HAS EXCEEDED UPPER THRESHOLD
DFS2088I APPC/OTMA SMQ ENABLEMENT INACTIVE. REASON = xxx.
DFS3492W APPC/IMS TIMEOUT LIMIT REACHED FOR LU luname, TP-ID tp-id, variable text
DFS554A TRAN tttttttt ABEND (SYSID sss); REASON=reason; MSG IN PROCESS: xxxx (up to 78 bytes of data) time-stamp

OTMA messages:

DFS1988W OTMA input messages from member yyyyyyyy have reached xx% of the maximum active input message limit zzzz
DFS1989E OTMA input messages from member yyyyyyyy have reached the maximum active input message limit zzzz
DFS2088I APPC/OTMA SMQ ENABLEMENT INACTIVE. REASON = xxx.
DFS3428W THE TOTAL OTMA INPUT MESSAGES(TIB) HAVE REACHED xx% OF THE GLOBAL LIMIT zzzz
DFS3429E THE TOTAL OTMA INPUT MESSAGES(TIB) HAVE REACHED THE GLOBAL LIMIT zzzz
DFS3492W APPC/IMS TIMEOUT LIMIT REACHED FOR LU luname, TP-ID tp-id, variable text
DFS3494E OTMA HAS TIMED OUT FOR TMEMBER/TPIPE xxxx/yyyy variable text
DFS3495W OTMA HAS BEEN WAITING FOR AN ACK FROM TMEMBER/TPIPE xxxx/yyyy FOR OVER zzzz SECONDS.
DFS4382W THE TOTAL OTMA TPIPE COUNT nnnnn HAS REACHED 80% OF mmmmm for MEMBER name
DFS4383E THE TOTAL OTMA TPIPE COUNT nnnnn HAS REACHED 100% OF mmmmm for MEMBER name
DFS4385E THE GLOBAL OTMA TPIPE COUNNT nnnnn HAS REACHED 100% OF kkkkk
DFS4515W THE GLOBAL OTMA TPIPE COUNT HAS REACHED THE 80% OF THE GLOBAL LIMIT OF nnnnnn
DFS4516E THE GLOBAL OTMA TPIPE COUNT HAS REACHED THE GLOBAL LIMIT OF nnnnnn