Messages that Runtime Diagnostics analyzes

Parent topic: Runtime Diagnostics

BPX message analysis

This topic covers the messages Runtime Diagnostics uses for its analysis.

For more information on BPX messages for z/OS® UNIX System Services, see z/OS MVS System Messages, Vol 3 (ASB-BPX).

BPXF006I
A FILE SYSTEM WITH FILESYSTYPE type FAILED TO INITIALIZE. IT TERMINATED DURING INITIALIZATION

Explanation

If prompted for restart, fix the problem and respond. If no prompt, the system will run without the physical file system.

BPXF020I
FILE SYSTEM name MAY BE DAMAGED. RETURN CODE = return_code, REASON CODE = reason_code

Explanation

Access to files within the file system might still be possible. If an sdump was captured, provide it to IBM® support.

BPXF029E
ROOT FILE SYSTEM name WAS NOT MOUNTED. RETURN CODE = return_code, REASON CODE = reason_code

Explanation

Correct the problem in bpxprmxx or the superuser can enter correct data using TSO/E mount with "/" as the mountpoint.

BPXF076I
FILE SYSTEM INIT DELAYED BY ACTIVITY ON ANOTHER SYSTEM.

Explanation

See the subsequent BPXF041I message in OPERLOG. Issue D GRS,LATCH,C on all systems to investigate latch contention.

BPXF083I
THE INDICATED FILE SYSTEM IS UNUSABLE UNTIL IT IS UNQUIESCED <name>QUIESCING SYSTEM=<sysname> PID=<pid> JOB=<jobname> LATCH=<latchnum>

Explanation

An authorized user might be able to unquiesce the file system from the ISPF shell. See the message documentation in z/OS MVS System Messages, Vol 3 (ASB-BPX).

BPXF215E
ACCESS TO THE z/OS UNIX COUPLE DATA SET IS NOT AVAILABLE.

Explanation

Review the error codes and correct the access problem. Issue the SETXCF couple command to enable the couple data set.

BPXF216E
FILE SYSTEM PARTITION CLEANUP IS DELAYED DUE TO text

Explanation

See the subsequent BPXF041I message in OPERLOG. Issue D GRS,LATCH,C on all systems to investigate latch contention.

BPXF217E
FILE SYSTEM PARTITION CLEANUP FAILED DUE TO text

Explanation

Issue F BPXOINIT,FILESYS=D,EXCEPTION to identify impacted file systems. Unmount and remount if file system does not recover.

BPXI026I
THE ETCINIT JOB COULD NOT BE STARTED. system_call RETURN CODE return_code REASON CODE reason_code

Explanation

Creation for process failed for /etc/init or /usr/sbin/init.

Examine the return and reason codes. See the message documentation in z/OS MVS System Messages, Vol 3 (ASB-BPX).

BPXI027I
THE ETCINIT JOB ENDED IN ERROR, EXIT STATUS exit_status

Explanation

Examine the exit status code. See the message documentation in z/OS MVS System Messages, Vol 3 (ASB-BPX).

BPXI031E
BPXOINIT FAILED TO INITIALIZE. RETURN CODE return_code REASON CODE reason_code

Explanation

Examine the return and reason codes. Correct the error. A re-IPL of the system is required to start z/OS UNIX.

BPXI036E
UNIX SYSTEM SERVICES ARE NOT AVAILABLE

Explanation

Correct the conditions that caused the failure. A re-IPL of the system is required to start z/OS UNIX.

BPXI043E
MOUNT TABLE LIMIT HAS REACHED limperc% OF ITS CURRENT CAPACITY OF limtot

Explanation

See the message documentation in z/OS MVS System Messages, Vol 3 (ASB-BPX).

BPXI060I
jobname RUNNING IN ADDRESS SPACE asid IS BLOCKING SHUTDOWN OF OMVS

Explanation

Evaluate stopping the indicated job. The indicated job must be stopped to allow z/OS UNIX shutdown to complete.

BPXI062I
jobname RUNNING IN ADDRESS SPACE asid IS PREVENTING THE SHUTDOWN OF OMVS FROM COMPLETING

Explanation

The indicated job is blocking z/OS UNIX shutdown. Evaluate stopping the indicated job. The indicated job must be stopped to allow z/OS UNIX shutdown to complete.

BPXI068I
jobname RUNNING IN ADDRESS SPACE asid IS USING text

Explanation

Evaluate stopping the indicated job. The indicated job must be stopped to allow z/OS UNIX shutdown to complete

BPXI076E
LATCH CONTENTION EXISTS THAT MUST BE RESOLVED PRIOR TO SHUTDOWN

Explanation

Issue D GRS,C to determine the nature of the contention. Evaluate canceling or forcing the address space that is causing contention.

BPXI084E
OMVS SHUTDOWN IS STALLED IN FILE SYSTEM TERMINATION

Explanation

z/OS UNIX shutdown delayed while terminating file systems. Get an SVC dump of z/OS UNIX and its associated data spaces.

BPXM048I
BPXOINIT FILESYSTEM SHUTDOWN INCOMPLETE. notshutdown FILESYSTEM(S) ARE STILL OWNED BY THIS SYSTEM. mounted FILESYSTEM(S) WERE MOUNTED DURING THE SHUTDOWN PROCESS

Explanation

Issue D OMVS,F to identify file systems that did not move or unmount. See the message documentation in z/OS MVS System Messages, Vol 3 (ASB-BPX).

BPXP007E
STARTING PHYSICAL FILE SYSTEM pfsname IN ADDRESS SPACE spacename

Explanation

Get an SVC dump of the indicated address space, z/OS UNIX and its associated data spaces. Provide the dump to IBM support.

IEA message analysis

For more information on IEA messages for the communication and console services, see z/OS MVS System Messages, Vol 6 (GOS-IEA).

IEA230E
WTOR BUFFER SHORTAGE. 80% FULL

Explanation

Enter D R,R to display outstanding WTOR messages. Reply to them. Enter K M,RLIM=nnnn to increase the RLIM buffer limit.

IEA231A
SEVERE WTOR BUFFER SHORTAGE. 100% FULL

Explanation

Enter D R,R to display outstanding WTOR messages. Reply to them. Enter K M,RLIM=nnnn to increase the RLIM buffer limit.

IEA359E
BUFFER SHORTAGE FOR RETAINED ACTION MESSAGES - 80% FULL

Explanation

Enter D R,L to display action messages, respond to them, or delete them using K C,X,ID-ID (X = A,E OR CE) where ID is the message numbers.

IEA360A
SEVERE BUFFER SHORTAGE FOR RETAINED ACTION MESSAGES - 100% FULL

Explanation

Enter D R,L to display action messages, respond to them, or delete them using K C,X,ID-ID (X = A,E OR CE) where ID is the message numbers.

IEA404A
SEVERE WTO BUFFER SHORTAGE - 100% FULL

Explanation

Enter D C,B to display WTO backlog; enter K Q to clear message queue; enter K M,MLIM=nnnn to increase the buffer limit for MLIM (maximum number of WTO messages allowed in the system).

IEA405E
WTO BUFFER SHORTAGE - 80% FULL

Explanation

Enter D C,B to display WTO backlog. Enter K Q to clear message queue. Enter K M,MLIM=nnnn to increase the buffer limit for MLIM (maximum number of WTO messages allowed in the system).

IEA406I
WTO BUFFER SHORTAGE RELIEVED
IEA611I
{COMPLETE|PARTIAL} DUMP ON dsname

Explanation

Use IPCS to diagnose the problem and determine the action for a partial dump, see the message documentation.

IEA793A
NO SVC DUMP DATA SETS AVAILABLE FOR DUMPID=dumpid FOR JOB (*MASTER*). USE THE DUMPDS COMMAND OR REPLY D TO DELETE THE CAPTURED DUMP

Explanation

Enter DD ADD,SMS=class to add SMS classes, enter DD ADD,VOL=VOLSER to add DASD volumes, or reply D to delete the captured dump.

IEA799I
AUTOMATIC ALLOCATION OF SVC DUMP DATA SET FAILED DUMPID=dumpid REQUESTED BY JOB (jobname) reason-text reason text2

Explanation

Enter D D to view allocation status. Enter DD ADD,VOL=VOLSER to add dump resources.

IEA911E
{COMPLETE|PARTIAL} DUMP ON SYS1.DUMPnn JOB (jobname) FOR ASIDS(id,id,...) [REMOTE DUMPS REQUESTED | REMOTE DUMP FOR SYSNAME: sysname] INCIDENT TOKEN:incident-token [SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz] [reason-text] [ERRORID = SEQyyyyyy CPUzz ASIDasid TIMEhh.mm.ss.f] [TSOID = tsoid] [ID = uuuuuuuuuuDUMPid=dumpid REQUESTED BY

Explanation

Use IPCS to diagnose the problem and determine the action. For a partial dump, see the message documentation.

IEE message analysis

For more information about IEE messages for MVS™, see z/OS MVS System Messages, Vol 7 (IEB-IEE).

IEE012A
NO LONGER SAVING MESSAGES FOR HARDCOPY, LOGLIM REACHED.

Explanation

Issue V SYSLOG,HARDCPY to activate SYSLOG. K M,LOGLIM=nnnnn to increase the LOGLIM value.

IEE601E
PROCESSOR (y) IS IN AN EXCESSIVE DISABLED SPIN LOOP WAITING FOR event HELD BY PROCESSOR (x). ACR IS ALREADY ACTIVE. SPIN WILL CONTINUE.

Explanation

Reply U, ABEND or TERM to message IEE331A.

IEE711I
[SYSTEM UNABLE TO DUMP|SYSTEM DUMP NOT TAKEN. reason]

Explanation

The system did not write the requested SVC dump. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IEE766E
BUFFER SHORTAGE FOR SYSTEM LOG - 60% FULL

Explanation

K M,LOGLIM=nnnnnn to increase the WTL buffers.

IEE767A
SEVERE BUFFER SHORTAGE FOR SYSTEM LOG - 100% FULL

Explanation

K M,LOGLIM=nnnnnn to increase the WTL buffers.

IEE786I
THE PAGEADD COMMAND ENCOUNTERED A FAILURE

Explanation

Issue R nn,U to message IEE787A to continue PAGEADD processing. Issue R nn,END to message IEE787A to end PAGEADD processing.

IEE986E
SMF HAS USED nn% OF AVAILABLE BUFFER SPACE

Explanation

Issue D SMF to check the status of the SMF data sets. Use the SMF dump program (IFASMFDP) to make a data set available for use.

IOS message analysis

For more information about IOS messages, see z/OS MVS System Messages, Vol 9 (IGF-IWM).

IOS078I
I/O REQUEST HAS TIMED OUT

Explanation

Run EREP to dump data from SYS1.LOGREC and provide it to IBM Support.

IOS078I
I/O REQUEST HAS TIMED OUT

Explanation

Run EREP to dump data from SYS1.LOGREC and provide it to IBM Support.

IOS431I
THE INDICATED SYSTEM HOLDS THE RESERVE ON THE DASD DEVICE.

Explanation

Issue D GRS,DEV=dev to investigate and resolve the contention. See the message documentation in z/OS MVS System Messages, Vol 9 (IGF-IWM).

IOS1078I
I/O REQUEST HAS TIMED OUT

Explanation

Run EREP to dump data from SYS1.LOGREC and provide it to IBM support.

IOS1079I
I/O REQUEST HAS TIMED OUT

Explanation

Run EREP to dump data from SYS1.LOGREC and provide it to IBM support.

IRA message analysis

For more information about IRA messages for System Resource Manager, see z/OS MVS System Messages, Vol 9 (IGF-IWM).

IRA100E
SQA SHORTAGE

Explanation

Determine largest users of sqa/csa storage. Get an SVC dump of those users for analysis. Include SQA/CSA/RGN in the dump.

IRA101E
CRITICAL SQA SHORTAGE

Explanation

Get an SVC dump of common storage to analyze its growth and determine if SQA/CSA allocation is adequate.

IRA103I
SQA/ESQA HAS EXPANDED INTO CSA/ECSA BY xxxxx PAGES

Explanation

Evaluate the system requirement for sqa storage. Increase the size of the SQA parameter in the IEASYSXX parmlib member.

IRA200E
AUXILIARY STORAGE SHORTAGE

Explanation

Issue PA PAGE=DSNAME to add auxiliary storage. Evaluate canceling jobs indicated by messages IRA206I and IRA210E.

IRA201E
CRITICAL AUXILIARY STORAGE SHORTAGE

Explanation

Issue PA PAGE=DSNAME to add auxiliary storage. Evaluate canceling any jobs indicated by messages ira206i and ira210e.

IRA206I
uuuuuuuu ASID aaaa FRAMES ffffffffff SLOTS ssssssssss % OF AUX nn.n

Explanation

Get an SVC dump of the indicated ASIDs for analysis. Evaluate canceling one or more of the indicated ASIDs.

IRA210E
uuuuuuuu ASID aaaa SET NON DISPATCHABLE Frames+Slots vvvvvvvvvv RATE rrrrrr

Explanation

Issue PA PAGE=DSNAME to add auxiliary storage. Evaluate canceling the indicated job.

IRA211I
uuuuuuuu ASID aaaa SET NON DISPATCHABLE Frames+Slots vvvvvvvvvv RATE rrrrrr

Explanation

Issue PA PAGE=DSNAME to add auxiliary storage. Evaluate canceling the indicated job.

IRA220I
CRITICAL AUXILIARY SHORTAGEtext

Explanation

The text is:
! ## ! USER     ! ASID ! PAGES      ! SLOTS      ! 
+----+----------+------+------------+------------+
! ii ! uuuuuuuu ! aaaa ! xxxxxxxxxx ! zzzzzzzzzz ! 
! ii ! uuuuuuuu ! aaaaS! xxxxxxxxxx ! zzzzzzzzzz !
! ii ! uuuuuuuu ! aaaaN! xxxxxxxxxx ! zzzzzzzzzz !
Issue PA PAGE=DSNAME to add auxiliary storage. Evaluate canceling a specific consumer by replying to message IRA221D.
IRA400E
return-code, PAGEABLE STORAGE SHORTAGE

Explanation

Evaluate canceling jobs identified by messages IRA403E and IRA404I.

IRA401E
return-code, CRITICAL PAGEABLE STORAGE SHORTAGE

Explanation

Evaluate canceling jobs identified by messages IRA403E and IRA404I.

IXC message analysis

For more information on IXC messages for Cross System Coupling Facility (XCF) , see z/OS MVS System Messages, Vol 10 (IXC-IZP).

IXC101I
SYSPLEX PARTITIONING IN PROGRESS FOR sysname REQUESTED BY jobname REASON: reason

Explanation

See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC105I
A SYSTEM HAS BEEN REMOVED FROM THE SYSPLEX.

Explanation

See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC244E
XCF CANNOT USE {PRIMARY | ALTERNATE} SYSPLEX COUPLE DATA SET dsname, {ON VOLSER volser, | VOLSER N/A,} text

Explanation

Check data set name and VOLSER to ensure they are correct.

IXC246E
typename COUPLE DATA SET dsname ON VOLSER volser, DEVNdevnum, HAS BEEN EXPERIENCING I/O DELAYS FOR delaysec SECONDS.

Explanation

See messages IOS078I and IOS1078I for the same device number and see the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC255I
UNABLE TO USE DATA SET dsname AS THE {PRIMARY|ALTERNATE} FOR typename: text [RELEVANTtypename COUPLE DATA SET FORMAT INFORMATIONPRIMARY FORMAT LEVEL: fmtlevel FORMAT KEYWORDS: fmtinfo ALTERNATE FORMAT LEVEL: fmtlevel FORMAT KEYWORDS: fmtinfo]

Explanation

See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC256A
REMOVAL OF {PRIMARY|ALTERNATE} COUPLE DATA SET dsname FOR typename CANNOT FINISH THE {ACTION|COMPLETE} PHASE UNTIL THE FOLLOWING SYSTEM(S) ACKNOWLEDGE THE REMOVAL: syslist

Explanation

Missing response delaying the removal of a couple data set. If the condition persists, see the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC259I
I/O ERROR ON DATA SET dsname FOR typename, VOLSER volser, modname,post-code,text

Explanation

Reply COUPLE=xx to message IXC207A. (xx = the suffix of the COUPLExx parmlib member to be used by XCF initialization.)

IXC267E
PROCESSING WITHOUT AN ALTERNATE COUPLE DATA SET FOR typename. ISSUE SETXCF COMMAND TO ACTIVATE A NEW ALTERNATE.

Explanation

No alternate couple data set defined for indicated function. Issue SETXCF COUPLE,TYPE=typename,ACOUPLE=DSNAME to activate a new alternate couple data set.

IXC406I
THIS SYSTEM IS CONNECTED TO ETR NET ID=xx. THE OTHER ACTIVE SYSTEMS IN THE SYSPLEX ARE USING ETR NET ID=yy. EFFECTIVE CLOCK VALUES ARE NOT CONSISTENT.

Explanation

Correct any ETR problem and retry with COUPLExx parmlib member or correct any improperly defined ETR time offsets.

IXC427A
SYSTEM sysname HAS NOT UPDATED STATUS SINCE hh:mm:ss BUT IS SENDING XCF SIGNALS. XCF SYSPLEX FAILURE MANAGEMENT WILL REMOVE sysname IF NO SIGNALS ARE RECEIVED WITHIN A interval SECOND INTERVAL

Explanation

Determine and resolve any contention issues with the sysplex couple data set. Reply to message IXC426D.

IXC430E
SYSTEM sysname HAS STALLED XCF GROUP MEMBERS

Explanation

Issue D XCF,G to see groups with stalled members. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC431I
text

Explanation

Issue D XCF,G,grpname,membername for more information. For the complete message text, see the IXC431I messages in z/OS MVS System Messages, Vol 10 (IXC-IZP)

IXC432I
text

Explanation

The indicated XCF group member is no longer stalled. No action needed.

IXC440E
SYSTEM hurtsys IMPACTED BY STALLED XCF GROUP MEMBERS ON SYSTEM stallsys

Explanation

Issue D XCF,G to see groups with stalled members. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC446I
SYSTEM sysname IS IN MONITOR-DETECTED STOP STATUS BUT IS SENDING XCF SIGNALS. SFM WILL TAKE SSUM ACTION AT actiontime IF SYSTEM REMAINS IN THIS STATE.

Explanation

The indicated system has not updated its system status. Investigate the XCF couple data sets for contention or poor performance.

IXC467I
command dir pathname RSN: text

Explanation

XCF IS TRYING TO RESTORE THE INDICATED PATH TO SERVICE. SEE THE MESSASGE DOCUMENTATION.

Explanation

The indicated system is waiting for system reset. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC512I
POLICY CHANGE IN PROGRESS FOR CFRM TO MAKE polname POLICY ACTIVE. numpend POLICY CHANGE(S) PENDING.

Explanation

Issue D XCF,STR to show structures pending actions. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC518I
SYSTEM sysname NOT USING COUPLING FACILITY type.mfg.plant.sequence PARTITION: partition side CPCID: cpcid NAMED cfname REASON: text

Explanation

The indicated coupling facility is unusable. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC519E
COUPLING FACILITY DAMAGE RECOGNIZED FOR COUPLING FACILITY type.mfg.plant.sequence PARTITION: partition side CPCID: cpcid NAMED cfname

Explanation

Run EREP to dump data from SYS1.LOGREC and gather XCF/XES CTRACE records and provide them to IBM support.

IXC522I
rebuildtype FOR STRUCTURE strname IS BEING STOPPED action DUE TO reason [codetype stopcode]

Explanation

See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC538I
DUPLEXING REBUILD OF STRUCTURE strname WAS NOT INITIATED BY MVS. REASON: reason

Explanation

Duplexing rebuild start request of structure not performed. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC552I
DUPLEX REBUILD NEW STRUCTURE strname WAS ALLOCATED IN A COUPLING FACILITY THAT IS NOT FAILURE ISOLATED FROM THE OLD STRUCTURE.

Explanation

Review your coupling facility configuration. When possible duplex failure isolation is strongly encouraged.

IXC553E
DUPLEXING REBUILD NEW STRUCTURE strname IS NOT FAILURE ISOLATED FROM THE DUPLEXING REBUILD OLD STRUCTURE.

Explanation

Review your coupling facility configuration. When possible duplex failure isolation is strongly encouraged.

IXC573I
phase PROCESSING DURING A SYSTEM-MANAGED process FOR STRUCTURE strname ENCOUNTERED AN ERROR. ERROR DATA: reason [reldata1 reldata2 reldata3 reldata4] AUTO VERSION: procid1 procid2

Explanation

Error encountered during rebuild or duplex rebuild process. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC585E
STRUCTURE strname IN COUPLING FACILITY cfname, PHYSICAL STRUCTURE VERSION physver1 physver2, IS AT OR ABOVE STRUCTURE FULL MONITORING THRESHOLD OF thresh%. ENTRIES: IN-USE: nnnnnnnn, TOTAL: pppppppp, pct% FULL [ELEMENTS: IN-USE: nnnnnnnn, TOTAL: pppppppp, pct% FULL] [EMCS: IN-USE: nnnnnnnn, TOTAL: pppppppp, pct% FULL]

Explanation

Issue D XCF,STR,STRNAME=strname to get structure information. Iincrease structure size or take action against application.

IXC615I
GROUP grpname MEMBER membername JOB jobname ASID asidtext

Explanation

XCF terminated the group member to resolve critical problem. Restart the affected application, subsystem, or system. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC631I
GROUP grpname MEMBER membername JOB jobname ASID asidSTALLED, IMPACTING SYSTEM sysname {WHICH IS IN PARTITIONING }

Explanation

Issue D XCF,G,grpname,membername to get more information. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC633I
text GROUP gnme MEMBER mnme JOB jnme ASID asid{DEEMED | CONFIRMED} IMPAIRED AT ipdate iptime ID: s#.r#LAST MSGX: sgdate sgtime sgexit STALLED sgwork PENDINGQLAST GRPX: grdate grtime grexit STALLED grwork PENDINGQLAST STAX: stdate sttime stexit STALLED

Explanation

Indicated XCF group member is not operating normally. See message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC635E
SYSTEM sysname HAS IMPAIRED XCF GROUP MEMBERS

Explanation

The indicated system has impaired group members. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC700E
SYSPLEX COUPLE DATA SET LIMIT REACHED, FUTURE REQUESTS MAY BE REJECTED. text

Explanation

Issue D XCF,COUPLE to review maximum values in the sysplex couple data set. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXC800I
ELEMENTS FROM TERMINATED SYSTEM sysname NOT RESTARTED. text

Explanation

Indicated system had jobs that could not be restarted. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL message analysis

For more information on IXL messages for Cross System Extended Services (XES), see z/OS MVS System Messages, Vol 10 (IXC-IZP).

IXL010E
NOTIFICATION RECEIVED FROM COUPLING FACILITY type.mfg.plant.sequence PARTITION: partition side CPCID: cpcid NAMED cfname cfservrecord

Explanation

Run EREP to dump data from SYS1.LOGREC and provide it to IBM support.

IXL013I
requesttype REQUEST FOR STRUCTURE structure-name FAILED. JOBNAME: jobname ASID: asid CONNECTOR NAME: connector-name IXLCONN RETURN CODE: return-code, REASON CODE: reason-code errortype CONADIAGdiagn: diagvalue

Explanation

See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).
Note: Only the last occurrence of message IXL013I is displayed when structure name, jobname, ASID, and connector name match.
IXL015I
strtype ALLOCATION INFORMATION FOR STRUCTURE structure-name CONNECTOR NAME: connector-name CFNAME ALLOCATION STATUS/FAILURE REASON------ --------------------------------cfname text [diag]

Explanation

Connector statistical information for indicated connector. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL0130
CONNECTOR STATISTICS FOR LOCK STRUCTURE structure-name, CONNECTOR connector-name: n

Explanation

Connector statistical information for indicated connector. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL040E
CONNECTOR NAME: connector-name, JOBNAME: jobname, ASID: asid HAS text. process FOR STRUCTURE structure-name CANNOT CONTINUE. MONITORING FOR RESPONSE STARTED: mm/dd/yyyy hh:mm:ss. DIAG: x

Explanation

Evaluate job and gather XES CTRACE for specific connector terminate non-responsive job. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL041E
CONNECTOR NAME: connector-name, JOBNAME: jobname, ASID: asid HAS NOT RESPONDED TO THE event FOR SUBJECT CONNECTION: subject-connector-name. process FOR STRUCTURE structure-name CANNOT CONTINUE. MONITORING FOR RESPONSE STARTED: mm/dd/yyyy hh:ss:mm. DIAG: x

Explanation

Evaluate job and gather XES CTRACE for specific connector; terminate non-responsive job. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL044I
COUPLING FACILITY cfname HAS EXPERIENCED IfccCount INTERFACE CONTROL CHECKS ON CHPID chpid DURING THE LAST interval SECONDS.

Explanation

Run EREP to dump data from SYS1.LOGREC and provide it to IBM support.

IXL045E
[REBUILD] CONNECTOR NAME: connector-name, JOBNAME: jobname, ASID: asid FOR STRUCTURE structure-name MAY BE ENCOUNTERING DELAYS DUE TO LIMITED XES SRB SCHEDULING.

Explanation

Run EREP to dump data from SYS1.LOGREC and gather XES CTRACE and system log and provide it to IBM support. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL049E
HANG RESOLUTION ACTION FOR CONNECTOR NAME: conname TO STRUCTURE strname, JOBNAME: jobname, ASID: asid: actiontext

Explanation

See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL158I
PATH chpid IS NOW NOT-OPERATIONAL TO CUID: cuid COUPLING FACILITY type.mfg.plant.sequence PARTITION: partition side CPCID: cpcid

Explanation

Indicated channel not operational. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL159E
COUPLING SUPPORT FACILITY HARDWARE ERROR DETECTED.

Explanation

Run EREP to dump data from SYS1.LOGREC and provide it to IBM Support.

IXL160E
CF REQUEST TIME ORDERING: REQUIRED AND NOT-ENABLED text reason

Explanation

Coupling facility hardware configuration problem. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).

IXL162E
CF REQUEST TIME ORDERING: REQUIRED AND WILL NOT BE ENABLED text reason

Explanation

Coupling facility hardware configuration problem. See the message documentation in z/OS MVS System Messages, Vol 6 (GOS-IEA).