PowerExchange for CDC and Mainframe
- PowerExchange for CDC and Mainframe 10.5.2
- All Products
ASK INFAPreview
Please log in to access Bolo.
ASK INFAPreview
Reason Code
| Explanation
|
|---|---|
00F7FF01
| The chainer module could not obtain a work area.
|
00F7FF02
| An attempt to initialize the common services environment failed.
|
00F7FF03
| An attempt to connect to common services failed.
|
00F7FF04
| An attempt to initialize the XCF interface failed.
|
00F7FF05
| An attempt to open the XCF interface failed.
|
00F7FF06
| An attempt to create the XCF interface failed.
|
00F7FF07
| $XCF GET failed for message.
|
00F7FF08
| $XCF GET failed for group event (Logger group).
|
00F7FF09
| $XCF GET failed for group event (Post‑Log Merge group).
|
00F7FF17
| Failed adding log reader control block (OUQQ).
|
00F7FF18
| Unable to start log reader subtask.
|
00F7FF19
| ECCR is already connected to Logger.
|
00F7FF1A
| Unable to add PKT queue entry.
|
00F7FF1B
| Failed to add ECCR control block (INQQ).
|
00F7FF1C
| Invalid signon type (neither read nor write).
|
00F7FF1D
| Attempt to perform resume operation failed.
|
00F7FF1E
| Unable to locate log reader (OUQQ) control block.
|
00F7FF1F
| Could not write to global circular queue.
|
00F7FF20
| Logger name in restart request does not match logger ID.
|
00F7FF21
| End location in transfer request before start location.
|
00F7FF22
| Terminate request did not complete successfully.
|
00F7FF23
| Delete of log reader (OUQQ) control block fail.
|
00F8FF01
| The chainer module could not obtain a work area.
|
00F8FF02
| The chainer module is unable to delete the old ECB list.
|
00F8FF03
| The chainer module is unable to obtain a new ECB list.
|
00F8FF04
| The checkpoint processor received an unexpected termination of the QSAM I/O subtask.
|
00F8FF05
| The checkpoint processor received an unexpected termination of the TIMER subtask.
|
00F8FF06
| The checkpoint processor received an unexpected termination of the JOURNAL subtask.
|
00F8FF07
| The checkpoint processor received an unexpected termination of the PROCESS subtask.
|
00F8FF08
| The checkpoint processor received an unexpected termination of the RESTART subtask.
|
00F8FF09
| The checkpoint processor received an unexpected termination of the LOGICAL subtask.
|
00F8FF0A
| The checkpoint processor received an unexpected termination of the PHYSICAL subtask.
|
00F8FF0B
| The checkpoint processor received an unexpected termination of the Checkpoint subtask.
|
00F8FF0C
| The checkpoint processor received an unexpected termination of the XCF subtask.
|
00F8FF0D
| The checkpoint processor received an unexpected termination of the VTAM I/O subtask.
|
00F8FF0E
| The checkpoint processor received an unexpected request for a checkpoint.
|
00F8FF0F
| The checkpoint processor received an unexpected request for a shutdown.
|
00F8FF10
| The checkpoint processor received an unexpected operator reply.
|
00F8FF11
| The checkpoint processor received an unexpected reload of EDMZPARM.
|
00F8FF12
| The checkpoint processor received an unexpected termination of an MVS command.
|
00F8FF13
| The chainer module was unable to delete a work area.
|
00F8FF14
| The PowerExchange Logger found an invalid code. A WRITE to a restart data set (ERDS) failed.
|
00F9F701
| The routine that determines the number of blocks available in the active LOG2 was unable to obtain a LOGQ latch.
|
00F9F702
| The routine that determines the number of blocks available in active LOG2 was unable to release the LOGQ latch.
|
00F9F801
| The routine that determines the number of blocks available in active LOG2 was unable to obtain the LOGQ latch.
|
00F9F802
| The routine that determines the number of blocks available in active LOG2 was unable to release the LOGQ latch.
|
00F9F803
| The chainer module could not obtain a read buffer.
|
00F9F804
| The chainer module was unable to add an entry to the BLKQ COPY1 queue.
|
00F9F805
| The chainer module was unable to add an entry to the active LOGQ COPY1 queue.
|
00F9F806
| The chainer module was unable to add an entry to the archive BLKQ COPY1 queue.
|
00F9F807
| The chainer module was unable to add an entry to the archive LOGQ COPY1 queue.
|
00F9F808
| The chainer module was unable to find an entry in the GBLBLKQ11 queue.
|
00F9F809
| The chainer module was unable to find an entry in the GBLBLKQ12 queue.
|
00F9F80A
| The chainer module was unable to find an entry in the GBLBLKQ21 queue.
|
00F9F80B
| The chainer module was unable to find an entry in the GBLBLKQ22 queue.
|
00F9F901
| The routine that determines the number of blocks available in active LOG1 was unable to obtain the LOGQ latch.
|
00F9F902
| The routine that determines the number of blocks available in active LOG1 was unable to release the LOGQ latch.
|
00F9F903
| The chainer module could not obtain a read buffer.
|
00F9F904
| The chainer module was unable to add an entry to the BLKQ COPY1 queue.
|
00F9F905
| The chainer module was unable to add an entry to the active LOGQ COPY1 queue.
|
00F9F906
| The chainer module was unable to add an entry to the archive BLKQ COPY1 queue.
|
00F9F907
| The chainer module was unable to add an entry to the archive LOGQ COPY1 queue.
|
00F9F908
| The chainer module was unable to find an entry in the GBLBLKQ11 queue.
|
00F9F909
| The chainer module was unable to find an entry in the GBLBLKQ12 queue.
|
00F9F90A
| The chainer module was unable to find an entry in the GBLBLKQ21 queue.
|
00F9F90B
| The chainer module was unable to find an entry in the GBLBLKQ22 queue.
|
00F9FA01
| The chainer module was unable to find an entry in the GBLBLKQ11 queue.
|
00F9FA02
| The chainer module was unable to find an entry in the GBLBLKQ12 queue.
|
00F9FA03
| The chainer module was unable to find an entry in the GBLBLKQ21 queue.
|
00F9FA04
| The chainer module was unable to find an entry in the GBLBLKQ22 queue.
|
00F9FA05
| A save error occurred in the physical logger processor (EDMLPLG0). The other log was already stopped.
|
00F9FA06
| A save error occurred in the physical logger processor (EDMLPLG0). There is no secondary log.
|
00F9FA07
| The secondary active log subtask (EDMLPLG2) has abended.
|
00F9FB01
| The routine to terminate processing of active log could not obtain the LOGQ latch.
|
00F9FB02
| The routine to terminate processing of active log could not release the LOGQ latch.
|
00F9FB03
| The DIV UNACCESS macro could not stop accessing the LOG1 data set.
|
00F9FB04
| The DIV UNIDENTIFY macro could not unidentify the LOG1 data set.
|
00F9FB05
| The ALESERV DELETE macro could not delete the LOG1 data set.
|
00F9FB06
| The DSPSERV DELETE macro could not delete the LOG1 data set.
|
00F9FB07
| The DIV SAVE macro could not save the LOG2 data set.
|
00F9FB08
| The DIV UNMAP macro could not unmap the LOG2 data set.
|
00F9FB09
| The DIV UNACCESS macro could not stop accessing the LOG2 data set.
|
00F9FB0A
| The DIV UNIDENTIFY macro could not unidentify the LOG2 data set.
|
00F9FB0B
| The ALESERV DELETE macro could not delete the LOG2 data set.
|
00F9FB0C
| The DSPSERV DELETE macro could not delete the LOG2 data set.
|
00F9FB0D
| The chainer module was unable to find an entry in the GBLBLKQ11 queue.
|
00F9FB0E
| The chainer module was unable to find an entry in the GBLBLKQ12 queue.
|
00F9FB0F
| The chainer module was unable to find an entry in the GBLBLKQ21 queue.
|
00F9FB10
| The chainer module was unable to find an entry in the GBLBLKQ22 queue.
|
00F9FC01
| The routine to initialize processing of active log could not obtain the LOGQ latch.
|
00F9FC02
| The routine to initialize processing of the active log could not release the LOGQ latch.
|
00F9FC03
| Dynamic allocation for the active LOG1 data set failed.
|
00F9FC04
| The routine to initialize processing of the active log could not release the LOGQ latch.
|
00F9FC05
| Dynamic allocation for the active LOG2 data set failed.
|
00F9FC06
| The routine to initialize processing of the active log could not release the LOGQ latch.
|
00F9FC07
| The DSPSERV CREATE macro could not create a hyperspace for HSP LOG1 data set.
|
00F9FC08
| The ALESERV OBTAIN macro could not obtain the access-list entry token (ALET) LOG1 data set.
|
00F9FC09
| The DSPSERV CREATE macro could not create a hyperspace for HSP LOG2 data set.
|
00F9FC0A
| The ALESERV OBTAIN macro could not obtain the access-list entry token (ALET) LOG2 data set.
|
00F9FC0B
| The DIV IDENTIFY macro could not identify the LOG1 data set.
|
00F9FC0C
| The DIV ACCESS macro could not access the LOG1 data set.
|
00F9FC0D
| The DIV MAP macro could not map the LOG1 data set.
|
00F9FC0E
| The DIV IDENTIFY macro could not identify the LOG2 data set.
|
00F9FC0F
| The DIV ACCESS macro could not access the LOG2 data set.
|
00F9FC10
| The DIV MAP macro could not map the LOG1 data set.
|
00F9FC11
| The chainer module was unable to find an entry in the GBLBLKQ11 queue.
|
00F9FC12
| The chainer module was unable to find an entry in the GBLBLKQ12 queue.
|
00F9FC13
| The chainer module was unable to find an entry in the GBLBLKQ21 queue.
|
00F9FC14
| The chainer module was unable to find an entry in the GBLBLKQ22 queue.
|
00F9FC15
| The physical logger found that both the primary and secondary active logs are in a stopped state.
|
00F9FD01
| The routine to obtain new active log could not obtain the LOGQ latch.
|
00F9FD02
| The routine to obtain new active log could not release the LOGQ latch.
|
00F9FE01
| The chainer module could not obtain a command buffer.
|
00F9FF01
| The chainer module could not obtain a work area.
|
00F9FF02
| The GETSTOC routine was unable to determine the number of available blocks for logging to the LOG1 data set.
|
00F9FF03
| The GETSTOC routine was unable to determine the number of available blocks for logging to the LOG2 data set.
|
00F9FF04
| A GETNEWL error occurred while attempting to get a new log during initialization.
|
00F9FF05
| The PowerExchange physical logger was unable to determine if a new active LOG2 exists.
|
00F9FF06
| The PowerExchange physical logger was unable to determine if a new active LOG1 exists.
|
00F9FF07
| The INIACTL routine could not initialize a new log.
|
00F9FF08
| The chainer module was unable to find an entry in the GBLBLKQ11 queue.
|
00F9FF09
| The chainer module was unable to find an entry in the GBLBLKQ12 queue.
|
00F9FF0A
| The chainer module was unable to find an entry in the GBLBLKQ21 queue.
|
00F9FF0B
| The chainer module was unable to find an entry in the GBLBLKQ22 queue.
|
00F9FF0C
| The chainer module was unable to add a LOCAL control block.
|
00F9FF0D
| The chainer module could not initialize the OPQ queue.
|
00F9FF0E
| An attempt to obtain a LOGQ latch failed.
|
00F9FF0F
| An attempt to release the LOGQ latch failed.
|
00F9FF10
| No space is available in the active log.
|
00F9FF11
| The physical logger processor (EDMLPLG0) was unable to build a UOW queue.
|
00F9FF12
| The physical logger processor (EDMLPLG0) could not obtain the LOGS log queue.
|
00F9FF13
| The physical logger processor (EDMLPLG0) entered an ESTAE routine.
|
00F9FF14
| The physical logger processor (EDMLPLG0) encountered an invalid log RBA.
|
00F9FF15
| The physical logger processor (EDMLPLG0) could not obtain a log queue latch.
|
00F9FF16
| The physical logger processor (EDMLPLG0) could not release a log queue latch.
|
00F9FF17
| The physical logger processor (EDMLPLG0) was unable to connect to PowerExchange common services.
|
00F9FF18
| A write error occurred. There is no secondary log.
|
00F9FF19
| A write error occurred. The other log was already stopped.
|
00F9FF1A
| Failure in attaching active log 2 subtask (EDMLPLG2).
|
00F9FF1B
| No available active log dataset.
|
00F9FF1C
| Number of secondary active log datasets does not match number of primary active log datasets.
|
00F9FF1D
| Archive log operation failed at initialization.
|
00F9FF1E
| Attempt to log data while logger is quiesced
|
