KO2Z - OMEGAMON® PE Subsystem messages
KO2Z abend codes
KO2Z messages
might be accompanied by the following abend codes:
- Abend code
- U2008
- The current OMPE Subsystem function terminated abnormally. Locate message KO2Z999E in the SYSLOG or OMPE server job log to identify the reason code associated with this failure.
KO2Z return codes
KO2Z
messages might be accompanied by the following return codes:
- Return code
- 0000
- Request successful.
- 0004
- OMEGAMON for Db2 PE return code.
- 0008
- Subsystem function failed.
- 0012
- Request terminated abnormally.
- 0016
- Unexpected ABEND occurred
- 0020
- Internal failure occurred
- 0028
- OMPE Collector request failed.
- 0256
- OMPE/XCF failure occurred
KO2Z reason codes
KO2Z
messages might be accompanied by the following reason codes:
- Reason code
- 0000
- Successfully completed.
- 0004
- Invalid subsystem name specified.
- 0008
- OMPECT structure not found in system-level name/token pair.
- 0011
- OMPECT validity check error.
- 0016
- OMPE Subsystem failed.
- 0020
- OMPE Subsystem is inactive.
- 0024
- Mutually exclusive INITPARM parameters specified.
- 0028
- One or more INITPARM parameters are not valid.
- 0032
- Module OMPELIB cannot open the TKANMOD library.
- 0036
- ECSA storage obtain error.
- 0040
- Dynamic allocation error trying to allocate data set specified in INITPARM parameter DSN=name.
- 0044
- Incorrect input parameter string specified with the VARY OMPE,REFRESH command request.
- 0048
- OMPEMGS/LINKAGE=PC must be called within the OMPE Collector address space.
- 0052
- JCL parameter data not specified with the utility PARM= JCL keyword.
- 0056
- Invalid F/MODIFY command input specified.
- 0060
- GXL/GXE global structure update failed.
- 0064
- OMPECT control structure ECSA virtual storage obtain error.
- 0068
- Refresh processing architecture error detected.
- 0072
- Utility command not allowed from TSO/E session.
- 0076
- The XCF main task abnormally terminated. Check the OMPE server job log for error messages in support of this failure.
- 0080
- RKD2PAR parameter data set RDJFCB error detected.
- 0084
- RKD2PAR parameter data set Open error detected.
- 0088
- The I/O read routine could not find the specified member.
- 0092
- The I/O routine could not obtain virtual storage for a READ request.
- 0096
- Could not find enough virtual storage to read member data.
- 0100
- Member data record insert overflow error detected.
- 0104
- Ddname/DSName function error detected by initialization routine.
- 0108
- No input records found in the specified set member.
- 0112
- Could not identify the XCF component main XCFCT control structure. Structure has been overlaid.
- 0116
- XCF main task could not create, delete, or retrieve the home-level name/token pair.
- 0120
- XCF resource manager abnormally terminated.
- 0124
- XCF member query function abnormally terminated.
- 0128
- XCF member Receive request abnormally terminated.
- 0132
- Parse routine found no record data to process.
- 0136
- Parse routine detected an unrecognized record.
- 0140
- Parse routine detected an unrecognized subrecord.
- 0144
- The specified input member was not found in the specified data set.
- 0148
- Read routine SYNAD error was detected.
- 0152
- Unsupported member was specified as input member name.
- 0156
- DDN or DSN INITPARM parameter not specified.
- 0160
- Parse entry structure error has been detected.
- 0164
- SVC call caused an abend because ALLOW(NO) was specified.
- 0168
- INITPARM LIB=DSName DYNALLOC allocation error.
- 0172
- INITPARM LIB=DSName data set Open error.
- 0176
- INITPARM LIB=DSName load module LOAD error.
- 0180
- INITPARM LIB=DSName E/CSA storage obtain error.
- 0184
- OMPE/XCF status routine abnormally terminated.
- 0188
- OMPE/XCF failed to successfully create a required data space.
- 0192
- OMPE/XCF XSRE failed validity checks.
- 0196
- UCM function detected an invalid input request.
- 0200
- The subsystem initialization routine could not obtain ECSA storage for the diagnostic work area buffers.
- 0204
- The global virtual storage list (GSL) is not currently initialized.
- 0208
- Incorrect global virtual store list element was specified with a storage release request.
- 0212
- Incorrect SSCT control block was processed by the global virtual storage list (GSL) component.
- 0216
- Invalid common subpool number was received by the global virtual storage (GSL) component.
- 0220
- Loop detected while executing a subsystem interface (SSI) subsystem routine.
- 0224
- An operator command interface storage obtain error was detected.
- 0228
- Loop detected while executing an EOT broadcast function request.
- 0232
- Loop detected while executing an EOM broadcast function request.
- 0236
- Loop detected while executing a WTO broadcast function request.
- 0240
- OMPECT control structure ESQA storage obtain error.
- 0244
- Loop detected by the subsystem initialization routine running in the MSAS address space.
- 0248
- Invalid parameter list supplied to the common message WTO processing routine.
- 0252
- Undefined message ID was passed as input to the WTO macro.
- 0256
- Internal error while processing the subsystem WTO message table repository.
- 0260
- Undefined segment error processing a subsystem WTO message request.
- 0264
- Invalid global virtual storage structure (GSL) detected.
- 0268
- Invalid ASCB(FREE=EOM) global virtual storage request was specified.
- 0272
- Invalid TCB (FREE=EOT) global virtual storage request was specified.
- 0276
- The global virtual storage list component detected that the GSL structure is not initialized.
- 0280
- A utility request was made against a subsystem that is not currently initialized.
- 0284
- No data was found to display for the specified command.
- 0288
- A subsystem request was issued against a subsystem release that does not match the current environment.
- 0292
- The OMPE Subsystem could not initialize the ESVT control structure.
- 0296
- The OMPE Subsystem module loader routine abnormally terminated.
- 0300
- The OMPE cross-memory initialization routine abnormally terminated.
- 0304
- The OMPE Subsystem loader routine could not obtain ECSA virtual storage required for commonly loaded load modules.
- 0308
- The OMPE Subsystem could not locate the OMVT vector table.
- 0312
- The OMPE Subsystem loader routine could not obtain ESQA virtual storage for the CDE/XTLST control blocks.
- 0316
- IRB timer service error. The common IRB routine abnormally terminated.
- 0320
- IRB ABTERM post error. The common IRB routine was abnormally terminated while waiting for a request to complete.
- 0324
- Subsystem module OMPECIU abnormally terminated.
- 0328
- Subsystem module OMPERFC abnormally terminated.
- 0332
- Subsystem module OMPERFR abnormally terminated.
- 0336
- Subsystem module OMPERFS abnormally terminated.
- 0340
- Invalid PARM= JCL initialization values specified.
- 0344
- Subsystem module OMPESVS abnormally terminated.
- 0348
- Subsystem module OMPESVS abnormally terminated.
- 0352
- Subsystem module OMPEIVT abnormally terminated.
- 0356
- Message processing routine loop detected error.
- 0360
- A subsystem Refresh request did not complete.
- 0364
- An invalid OMPE Subsystem name was specified by a utility function.
- 0368
- The requested task to be attached by the Attach service request failed while processing in IRB mode.
- 0372
- Lock manager routine abnormally terminated.
- 0376
- IXCQUERY failed to obtain a buffer large enough to hold group member data.
- 0380
- IXCQUERY group NO_MEMBER service request call failed.
- 0384
- IXCQUERY group NO_MEMBER service request found no member records in QUAH#REC field.
- 0388
- Group user SRB exit routine abnormally terminated.
- 0392
- Member XMEM entry dequeue routine abnormally terminated.
- 0396
- Module OMPEXDQ XMEM loop detected. The service request abnormally terminated.
- 0400
- Module OMPEXDB XMEM loop detected. Service request abnormally terminated.
- 0408
- Module OMPEXRB Receive request failed to validate the input parameters supplied by the OMPEXRE request SRB routine.
- 0412
- Module OMPEXRB could not load the module specified in the CALL= operand of the Send service request
- 0416
- The routine specified on the CALL= operand of the Send service request returned a non-zero return code.
- 0420
- The routine specified on the CALL= operand of the Send service request abnormally terminated.
- 0424
- Routine OMPEXRE failed to add the XCF data space to the DU-AL access list.
- 0428
- Routine OMPEXRE failed to receive the XCF response data via the IXCMSGI XCF service request.
- 0432
- The main XCF OMPEXCF Receive routine abnormally terminated. XCF Receive services are no longer available.
- 0436
- The main OMPEXCF task failed to load the driver function load modules.
- 0440
- The OMPEXRM resource termination manager terminated abnormally.
- 0444
- OMPETOP job step task abended referencing the OMPECT control table.
- 0448
- OMPE/XCB function failed while validity checking control structures.
- 0452
- OMPE/XCF IRB routine abnormally teminated.
- 0456
- OMPE/XCF dispatcher abnormally terminated.
- 0460
- OMPE/XCF dispatcher was entered without the LOCAL lock held.
- 0464
- OMPE/XCF dispatcher failed to locate a dispatchable TCB.
- 0468
- The Attach driver routine detected an invalid task ATTACH count.
- 0472
- The Attach driver failed to obtain the required virtual storage buffers.
- 0476
- OMPE/XCF dispatcher failed to locate a valid XRRD dispatcher entry.
- 0480
- OMPETOP job step task failed to locate the subsystem control table.
- 0484
- OMPE/XCF receive routine could not locate sending XMEM status entry.
- 0488
- OMPE/XCF receive routine detected a XMEM queue loop condition.
- 0492
- OMPE/XCF receive routine could not identify the correct Receive request.
- 0496
- OMPE/XCF receive routine failed validity checking XSRE and XRDE structures.
- 0500
- OMPE/XCF dispatcher could not retrieve a dispatcher token.
- 0504
- OMPE/XCF dispatcher failed control structures validity checks.
- 0508
- OMPETOP initialization failed server verification checks.
- 0512
- OMPETOP APF-authorization check error detected.
- 0516
- OMPE/XCF resource manager failed due to unknown function code.
- 0520
- OMPETOP failed to create/retrieve home type name token pair.
- 0524
- OMPEOPT detected an invalid user option address.
- 0528
- OMPEOPT detected an invalid user options table.
- 0532
- OMPEOPT failed while validity checking user options table.
- 0536
- OMPEOPT found zero user option table entries defined.
- 0540
- OMPEOPT specified user option not found in user options table.
- 0544
- OMPETOP could not match a subsystem name to server name.
- 0548
- Virtual storage test protection service abnormally terminated.
- 0552
- IRB service schedule failed to respond with completion indicator.
- 0556
- Event notification cell pool build request failed.
- 0560
- General I/O manager detected that the output buffer is too small to handle the request.
- 0564
- General I/O manager falied to validity check the supplied buffer address.
- 0568
- General I/O manager failed the reuest due to PSW storage key mismatch.
- 0572
- General I/O manager could not return any records to requestor.
- 0576
- Initialization failed to locate the system-level subsystem name/token pair
- 0588
- Common PC routine received invalid input parameters
- 0700
- Linkage stack storage key authorization error.
- 0704
- Linkage stack storage subpool authorization error.
- 0708
- Linkage stack request specified a zero stack size.
- 0712
- Linkage stack request size requested exceeds maximum allowed.
- 0716
- Linkage stack requested segment size exceeds stack size.
- 0720
- OMPE/XCF invalid XSRE structure ID detected in input request data buffer.
- 0724
- OMPE/XCF receive routine could not locate the target receive load module.
- 0728
- OMPE/XCF receive routine could not locate the specified receive TCB.
- 0732
- OMPE/XCF receive routine detected an invalid input request data buffer address.
- 0736
- OMPE/XCF receive routine detected an invalid input request data buffer length.
- 0740
- OMPE/XCF receive routine detected that the input request data buffer length is too small to handle the data request.
- 0744
- OMPE/XCF receive routine detected that the target data space STOKEN is not initialized.
- 0748
- Linkage stack build service routine terminated abnormally.
- 0752
- Collector Initialization routine failed to dynamically allocate the load module library.
- 0756
- Collector initialization routine failed while closing the STEPLIB load module library.
- 0760
- Initialization routine failed to build the cell pool callable services cell pool.
- 0764
- Initialization resource manager failed to build the OMPE/XCF receive cell pool.
- 0768
- Initialization resource manager failed to build the OMPE/XCF request cell pool.
- 0772
- Collector Initialization routine failed to build the required recovery cell pool.
- 0776
- Initialization resource manager failed to build the control block access cell pool.
- 0780
- OMPE/XCF detected that an invalid SEND request load module was specified.
- 0784
- Initialization resource manager failed validity checking a subsystem control structure.
- 0792
- The IRB scheduler failed to schedule the requested service routine.
- 0796
- OMPE/XCF failed while validty checking the ZXCF collector structure.
- 0800
- Linkage stack manager failed validity checking STKE stack element.
- 0804
- Linkage stack manager failed validity checking TSTK top element structure.
- 0808
- Linkage stack manager failed validity checking BSTK bottom element structure.
- 0812
- Linkage stack manager received an invalid service request length.
- 0816
- Linkage stack manager detected a linkage stack overflow exception.
- 0820
- Linkage stack manager received an invalid stack service request.
- 0824
- Linkage stack manager failed validity checking the LSCT control table.
- 0828
- Linkage stack manager detected LSCT control table overflow.
- 0832
- Initialization resource manager failed to build the control block access key=7 cell pool.
- 0836
- Initialization resource manager failed to build the control block access key=8 cell pool.
- 0840
- The resource manager driver routine detected that an invalid request was specified.
- 0844
- Entry convention processing detected a save area stack overflow exception.
- 0848
- Subentry convention processing detected a save area stack overflow exception.
- 0852
- Entry stack processing detected a save area stack overflow exception.
- 0856
- Initialization resource manager failed to initialize the required cell pool environment.
- 0876
- OMPE/XCF receive routine detected that the receive buffer size is too small to process the incoming XCF data request.
- 0880
- OMPE/XCF receive routine detected that the receive data space is too small to process the incoming XCF data request.
- 0884
- OMPE/XCF response routine received an invalid data space ALET.
- 0888
- OMPE/XCF IRB function failed during ALESERV add request processing.
- 0892
- OMPE/XCF receive routine failed during ALESERV add request processing.
- 0896
- Initialization resource manager failed to build the required SRB cell pool.
- 0900
- Common PC routine driver failed validity checking the OMVT vector table.
- 0904
- Common PC routine driver failed validity checking the PCPL parameter list.
- 0908
- Common PC routine driver failed validity checking the SSCT control table.
- 0912
- OMPE/XCF failed to load the required control block access load module.
- 0916
- Common PC routine driver failed while processing the save area stack.
- 0920
- OMPE/XCF failed due to no OMPEXMT table entries specified.
- 0924
- Common PC routine driver received an invalid PC function entry code.
- 0928
- OMPE/XCF response routine failed validity checking the XRDE structure.
- 0932
- OMPE/XCF response routine failed validity checking the XSRE structure.
- 0936
- OMPE/XCF response routine failed validity checking the response data buffer.
- 0940
- OMPE/XCF response routine failed validity checking the response buffer size.
- 0944
- OMPE/XCF response routine failed validity checking the input buffer size.
- 0948
- OMPE/XCF response routine failed validity checking the XMEM structure.
- 0960
- OMPE/XCF receive routine failed validity checking the XMEM structure.
- 0964
- OMPE/XCF receive routine failed validity checking the XCF status entry.
- 0968
- OMPE/XCF detected an output buffer overflow condition.
- 0972
- OMPE/XCF detected that the output buffer size specified is zero.
- 0984
- Collector initialization driver failed to retrieve the OMPE/XCF connect token.
- 0988
- OMPE/XCF component failed validity checking XMEM structure.
- 0992
- Common PC routine driver failed validity checking SSCTSUSE pointer.
- 0996
- Common PC routine driver failed validity checking OMPECT structure.
- 1000
- Common SRB scheduler failed to locate target requested address space.
- 1004
- Common SRB scheduler failed to locate the address space STOKEN.
- 1008
- Common SRB scheduler failed to locate the subsystem control table.
- 1012
- Common SRB scheduler failed to validity check subsystem structures.
- 1016
- Common SRB scheduler received an invalid SRB input routine.
- 1020
- Common SRB scheduler failed to schedule the specified SRB routine.
- 1024
- Common SRB scheduler abnormally terminated.
- 1028
- Subsystem initialization routine failed validity checking the SSVT control block.
- 1032
- Subsystem initializatrion routine failed validity checking the SSCT control block.
- 1036
- Subsystem initialization routine failed validity checking SSI entry point.
- 1040
- OMPE/XCF query module detected a locked loop condition.
- 1044
- OMPE/XCF group service routine detected a locked loop condition.
- 1048
- Subsystem initialization routine failed validity checking SSI function codes.
- 1052
- Subsystem initialization routine failed validity checking SSVT address pointer.
- 1056
- Subsystem initialization routine failed to swap SSVT control blocks.
- 1060
- Subsystem initialization routine failed during SSVT compare and swap processing.
- 1064
- Subsystem initialization routine detected invalid SSVT function matrix.
- 1068
- Subsystem initialization routine failed during swap SSVT processing.
- 1072
- VTAM® resource manager failed validity checking XRDE structure.
- 1076
- VTAM resource manager failed validity checking XRDE environment.
- 1080
- VTAM resource manager detected an invalid processing environment.
- 1084
- OMPE/XCF control block access response routine not specified error.
- 1088
- OMPE/XCF notifiy routine received the requested input buffers.
- 1092
- OMPE/XCF notify routine abnormally terminated.
- 1096
- VTAM resource manager failed validity checking OMPE/XCF structures.
- 1100
- VTAM resource manager detected an invalid OMPE/XCF initialization request.
- 1104
- VTAM routse manager could not locate the Db2 routing table.
- 1120
- Memory object manager received an invalid service request.
- 1124
- Memory object manager failed validity checking the SGT segment table.
- 1128
- Memory object manager failed releasing the SGT segment table.
- 1132
- Memory object manager failed validity checking requested segment length.
- 1136
- Memory object manager request exceeds maximum size allowed.
- 1140
- Memory object manager received a zero or negative segment request length.
- 1144
- Memory object manager computed a segment length that exceeds maximum allowed.
- 1148
- Memory object manager could not locate key-related segment table.
- 1152
- Memory object manager failed validity checking segment table index.
- 1156
- Memory object manager failed validity checking segment table entry.
- 1160
- Memory object manager could not locate a segment table entry.
- 1164
- Memory object manager failed validity checking the SGTE free queue.
- 1168
- Memory object manager detected an invalid SGT slot pointer.
- 1172
- Memory object manager maximum SGT/SGTE slots exceeded.
- 1176
- Memory object manager received an invalid free segment request.
- 1180
- Memory object manager failed validity checking SGTE element.
- 1184
- Memory object manager failed validity checking SGTE segment length.
- 1188
- Memory object manager failed due to incorrect storage release size.
- 1192
- Memory object manager could not locate specified storage address.
- 1196
- Memory object manager detected that the current TCB exceeded the allowed memory limit.
- 1200
- Memory object manager detected that the current address space exceeded the allowed memory limit.
- 1204
- Memory object manager abnormally terminated.
- 1300
- OMPE/XCF Send service routine failed validity checking XRDE structure.
- 1304
- OMPE/XCF Send service routine failed XRDE fetch/store access.
- 1308
- OMPE/XCF Send service routine failed validity checking TOKEN parameter.
- 1312
- OMPE/XCF Send service routine failed TOKEN fetch/store access.
- 1316
- OMPE/XCF Send service routine detected the output data buffer address is not initialized.
- 1320
- OMPE/XCF Send service routine detected the output data buffer size is not initialized.
- 1324
- OMPE/XCF Send service routine detected the output data buffer exceeds 128 MB.
- 1328
- OMPE/XCF Send service routine failed output data buffer fetch/store access.
- 1332
- OMPE/XCF Send service routine detected the input data buffer address is not initialized.
- 1336
- OMPE/XCF Send service routine detected the input data buffer length is not initialized.
- 1340
- OMPE/XCF Send service routine detected the input data buffer exceeds 60K.
- 1344
- OMPE/XCF Send service routine failed input data buffer fetch/store access.
- 1348
- OMPE/XCF Send service routine abnormally terminated due to fetch/store failure.
- 1352
- OMPE/XCF Send service routine failed to retrieve connection token.
- 1356
- OMPE/XCF Send service routine failed validity checking XMEM structure.
- 1360
- OMPE/XCF Send service routine detected that the OMPE/XCF environment is inactive.
- 1364
- OMPE/XCF Send service routine could not locate the OMPEXMT control table.
- 1368
- OMPE/XCF Send service routine failed during timer supervision processing.
- 1372
- OMPE/XCF Send service routine detected that the input buffer length exceeds data space size.
- 1376
- OMPE/XCF Send service routine did not receive a response in the specified time limit.
- 1380
- OMPE/XCF Send service routine failed establishing a timer environment.
- 1384
- OMPE/XCF Send service routine detected a locked XMEM structure loop.
- 1388
- OMPE/XCF Send service routine found an empty XMEM queue.
- 1392
- OMPE/XCF Send service routine failed to validity check XMEM structure.
- 1396
- OMPE/XCF Send service routine could not locate the target XMEM structure.
- 1400
- OMPE/XCF Send service routine timed out waiting for response data.
- 1404
- OMPE/XCF Send service routine failed validity checking token TCB address.
- 1408
- OMPE/XCF Send service routine failed validity checking token ASCB address.
- 1412
- OMPE/XCF Send service routine failed validity checking input buffer ALET.
- 1416
- OMPE/XCF Send service routine failed validity checking output buffer ALET.
- 1420
- OMPE/XCF Send service routine detected that the target XCF member is not active.
- 1424
- OMPE/XCF Send service routine abnormally terminated.
- 2000
- OMPEZ64 For the $ZSTOR64 service request, an invalid function code is specified.
- 2004
- OMPEZ64 An error occurred. The 64-bit memory object manager stopped abnormally.
- 2008
- OMPEZ64 For the $ZSTOR64 service request, an invalid CELLS= macro operand is specified.
- 2012
- OMPEZ64 For the $ZSTOR64 service request, an invalid CSIZE= macro operand is specified.
- 2016
- OMPEZ64 The CSIZE= value that is specified for the $ZSTOR64 service request exceeds the maximum value.
- 2020
- OMPEZ64 For the $ZSTOR64 service request, the FPROT= macro operand is specified. This operand is not supported.
- 2024
- OMPEZ64 For the $ZSTOR64 service request, an invalid TCB= macro operand is specified.
- 2028
- OMPEZ64 For the $ZSTOR64 service request, an invalid MODE= macro operand is specified.
- 2032
- OMPEZ64 For the $ZSTOR64 service request, an invalid cell pool HDR= macro operand is specified.
- 2036
- OMPEZ64 For the $ZSTOR64 service request, an invalid object segment OWNER= macro operand is specified.
- 2040
- OMPEZ64 The 64-bit memory object storage manager request stopped abnormally.
- 2048
- OMPEZ64 A shortage of memory object segments is detected.
- 2052
- OMPEZ64 The memory object segment request failed.
- 2056
- OMPEZ64 An error occurred while checking the validity of the requestor parameter list.
- 2060
- OMPEZ64 An error occurred while checking the validity of the FREE ID control field.
- 2064
- OMPEZ64 An error occurred while checking the validity of the FREE segment request.
- 2068
- OMPEZ64 An error occurred while checking the validity of the CP64 task control segment.
- 2072
- OMPEZ64 The memory segment to be freed cannot be found.
- 2076
- OMPEZ64 An internal loop is detected while scanning the CP64 control structure.
- 2084
- OMPEZ64 The 64-bit memory object storage manager CPCT control table cannot be obtained.
- 2088
- OMPEZ64 An overflow condition is detected while processing the CPCT control table.
- 2092
- OMPEZ64 An internal error occurred while processing a free extent.
- 2096
- OMPEZ64 The requested memory object cannot be built.
- 2100
- OMPEZSL The virtual storage cell pool manager received an invalid function code request.
- 2104
- OMPEZSL The virtual storage cell pool manager stopped abnormally.
- 2108
- OMPEZSL For the $ZPOOL service request, an invalid CELLS= macro operand is specified.
- 2112
- OMPEZSL For the $ZPOOL service request, an invalid CSIZE= macro operand is specified.
- 2116
- OMPEZSL For the $ZPOOL service request, an invalid CSIZE= macro operand is specified.
- 2120
- OMPEZSL For the $ZPOOL service request, an unauthorized virtual storage subpool is specified.
- 2124
- OMPEZSL For the $ZPOOL service request, an invalid BUILD macro operand is specified.
- 2128
- OMPEZSL For the $ZPOOL service request, an invalid MODE= macro operand is specified.
- 2132
- OMPEZSL For the $ZPOOL service request, an invalid HDR= macro operand is specified.
- 2140
- OMPEZSL The $ZPOOL service request is stopped abnormally.
- 2144
- OMPEZSL For the $ZPOOL service request, an invalid GET= was specified while a cell pool deletion was in progress.
- 2148
- OMPEZSL A shortage of cell pool elements is detected.
- 2152
- OMPEZSL The cell pool cannot be extended because the limit for maximum extents is exceeded.
- 2156
- OMPEZSL An invalid cell pool GET service request is detected.
- 2160
- OMPEZSL An error occurred while checking the structure of the FREE ID data field.
- 2164
- OMPEZSL An error occurred while checking a FREE service request cell.
- 2168
- OMPEZSL The CP31 structure validity check failed.
- 2172
- OMPEZSL A previously freed cell element cannot be freed again.
- 2176
- OMPEZSL A CP31 infinite structure loop is detected.
- 2180
- OMPEZSL A CP31 infinite extent structure loop is detected.
- 2184
- OMPEZSL The validity check of the CPXT control table failed.
- 2188
- OMPEZSL A CPXT table overflow error occurred.
- 2192
- OMPEZSL A CP31 extent free internal error occurred.
- 2196
- OMPEZSL The DELETE cell pool request is not valid.
- 88000
- Classic session OMPE/XCF driver detected an invalid input buffer address.
- 88004
- Classic session OMPE/XCF driver detected an invalid collection routine name.
- 88008
- Classic session OMPE/XCF driver detected that the XCF gateway is not active.
- 88012
- Classic session OMPE/XCF driver detected that the specified collection routine is undefined.
- 88016
- Classic session OMPE/XCF driver failed to locate the Db2 routing table.
- 88020
- Classic session OMPE/XCF driver detected an invalid Db2 routing table.
- 88024
- Classic session OMPE/XCF driver failed to locate the specified Db2 subsystem.
- 88028
- Classic session OMPE/XCF driver detected an invalid routing table pointer.
- 88032
- Classic session OMPE/XCF driver detected an invalid routing table header.
- 88036
- Classic session OMPE/XCF driver detected an invalid routing table Db2 ID.
- 88040
- Classic session OMPE/XCF driver could not locate the XCF token.
- 88044
- OMPE/XCF Send service routine failed validity checking XRDE structure.
- 88048
- OMPE/XCF Send service routine failed to locate the XCF connection token.
- 88052
- OMPE/XCF Send service routine failed validity checking token TCB pointer.
- 88056
- OMPE/XCF Send service routine failed validity checking token ASCB pointer.
- 88060
- OMPE/XCF Send service routine failed to locate target XMEM structure.
- 88064
- OMPE/XCF Send service routine failed to validity check XMEM structure.
- 88068
- OMPE/XCF Send service routine failed to validity check ALLTHOUT thread entry.
- 88072
- OMPE/XCF Send service routine detected that the buffer size exceeds data space size.
- 88076
- Classic session OMPE/XCF driver failed validity checking $ZDB2 control block.
- 88080
- Classic sesson OMPE/XCF driver failed validity checking VPI9800 block.
- 88084
- OMPE/XCF remote Db2 thread CPU driver failed sorting ALLTHOUT thread entries.
- 88088
- OMPE/XCF remote Db2 thread CPU driver stopped abnormally.
- 88092
- OMPE/XCF remote Db2 thread CPU driver found zero threads to process.
- 88096
- OMPE/XCF remote Db2 thread CPU driver failed validity checking ZCPU structure.
- 88100
- OMPE/XCF remote Db2 thread CPU response routine failed to validity check XSRE structure.
- 88104
- OMPE/XCF remote Db2 thread CPU response routine failed to validity check XRDE structure.
- 88108
- OMPE/XCF remote Db2 thread CPU response routine failed to validity check IRDA block.
- 88112
- OMPE/XCF remote Db2 thread CPU response routine failed to validity check IRDL length.
- 88116
- OMPE/XCF remote Db2 thread CPU response routine failed to validity check ZCPU block.
- 88120
- OMPE/XCF remote Db2 thread CPU response routine found zero ZCPE entries to process.
- 88124
- OMPE/XCF remote Db2 thread CPU response routine failed during ALESERV ADD request.
- 88128
- OMPE/XCF remote Db2 thread CPU response routine failed to validity check ZCPE block count.
- 88132
- OMPE/XCF remote Db2 thread CPU response routine found an unsupported Db2 subsystem version.
- 88136
- OMPE/XCF environment initialization failed to validity check the Db2 ERLY block.
- 88140
- OMPE/XCF environment initialization failed to validity check the Db2 subsystem ID.
- 88144
- OMPE/XCF environment initialization found an invalid Db2 subsystem ID as input.
- 88148
- OMPE/XCF environment initialization failed to validity check the Db2 SCOM block.
- 88152
- OMPE/XCF environment initialization failed to validity check the Db2 SSCT control block.
- 88156
- OMPE/XCF environment initialization failed to validity check the Db2 ACOM control block.
- 88160
- OMPE/XCF environment initialization failed to validity check the Db2 RMVT control block.
- 88164
- OMPE/XCF environment initialization failed to validity check the Db2 RMFT control block.
- 88168
- OMPE/XCF environment initialization failed to validity check the Db2 AMGS control block.
- 88172
- OMPE/XCF environment initialization failed to locate the Db2 routing table.
- 88176
- OMPE/XCF remote Db2 thread CPU collection routine failed to validity check Agent ASCB pointer.
- 88180
- OMPE/XCF remote Db2 thread CPU collection routine failed to validity check Agent ASSB pointer.
- 88184
- OMPE/XCF remote Db2 thread CPU collection routine failed to validity check Agent ASCB address.
- 88188
- OMPE/XCF remote Db2 thread CPU collection routine failed during ALESERV ADD request processing.
- 88192
- OMPE/XCF remote Db2 thread CPU collection routine failed during ALESERV DELETE processing.
- 88196
- OMPE/XCF remote Db2 thread CPU collection routine could not locate the Db2 AGNT control block.
- 88200
- OMPE/XCF control block access PC routine driver received an invalid input parameter list.
- 88204
- OMPE/XCF control block access PC routine driver specified an invalid processing environment.
- 88208
- OMPE/XCF control block access PC routine driver detected an invalid OMPE Collector environment.
- 88212
- OMPE/XCF control block access PC routine driver does not support the COMMCOLL collector environment.
- 88216
- OMPE/XCF control block access PC routine driver failed validity checking the specified Db2 version.
- 88220
- OMPE/XCF control block access PC routine driver detected an unsupported Db2 subsystem version.
- 88224
- OMPE/XCF control block access PC routine driver eas unable to locate the XRDE structure.
- 88228
- OMPE/XCF control block access PC routine driver failed to validity check XRDE structure.
- 88232
- OMPE/XCF control block access PC routine driver could not locate the Db2 vector table.
- 88236
- OMPE/XCF control block access PC routine driver received a zero DBPL block address.
- 88240
- OMPE/XCF control block access PC routine driver failed to validity check DBPL block.
- 88244
- OMPE/XCF control block access PC routine driver found an invalid collection routine entry address.
- 88248
- OMPE/XCF control block access PC routine driver failed to locate the specified Db2 subsystem.
- 88252
- OMPE/XCF control block access PC routine driver failed to locate the Db2 subsystem SSCT control table.
- 88256
- OMPE/XCF control block access PC routine driver received a null DBPL block address.
- 88260
- OMPE/XCF control block access PC routine driver failed to validity check DBPL block.
- 88264
- OMPE/XCF control block access PC routine driver detected a zero work area address.
- 88268
- OMPE/XCF control block access PC routine driver detected a zero input buffer address.
- 88272
- OMPE/XCF control block access PC routine driver detected a zero output buffer address.
- 88276
- OMPE/XCF control block access PC routine driver detected a zero work area length.
- 88280
- OMPE/XCF remote Db2 thread CPU collection routine failed to validity check the Db2 AGNT control block pointer.
- 88284
- OMPE/XCF remote Db2 thread CPU collection routine failed to validity check the Db2 AGNT control block address.
- 88288
- OMPE/XCF remote Db2 thread CPU collection routine failed to validity check the Agent ASCB address.
- 88292
- OMPE/XCF remote Db2 thread CPU collection routine failed to validity check the Agent TCB address.
- 88296
- OMPE/XCF remote Db2 thread CPU collection routine abnormally stopped.
- 88300
- OMPE/XCF Db2 environment initialization routine detected an invalid environment request.
- 90004
- OMPE/XCF ACE to AGNT collection routine failed to validity check the AMGS Db2 control block.
- 90008
- OMPE/XCF ACE to AGNT collection routine failed to validity check the Db2 ACE control block.
- 99000
- OMPE Collector subsystem token service routine retrieve request failed.
- 99004
- OMPE Collector subsystem token service routine failed token type validity checks.
- 90008
- OMPE Collector subsystem token service routine token name failed validity checks.
- 90012
- OMPE Collector subsystem token service routine token address failed validity checks.
- 90016
- OMPE Collector subsystem token service routine token retrieve failed validity checks.
- 90020
- OMPE Collector subsystem token service routine token delete failed validity checks.
- 90024
- OMPE Collector subsystem token service routine token create failed validity checks.
- 90028
- OMPE Collector subsystem token service routine token type retrieve failed validity checks.
- 90032
- OMPE Collector subsystem token service routine token delete function failed.
- 91000
- OMPEZIP The validity check of the OMPECT control structure failed.
- 91004
- OMPEZIP A duplicate $ZIIP ENABLE service request call is detected.
- 91008
- OMPEZIP The PC service request function code is not valid.
- 91012
- OMPEZIP A duplicate $ZIIP ENABLE instance service request is detected.
- 91016
- OMPEZIP $ZIIP ENABLE cannot be issued in SRB-mode.
- 91020
- OMPEZIP ZIIP support is not available (CVTZIIP).
- 91024
- OMPEZIP $ZIIP DISABLE cannot be issued in TCB-mode.
- 91028
- OMPEZIP The SVZ control storage block cannot be obtained.
- 91032
- OMPEZIP The $ZOMCT control structure is not initialized.
- 91036
- OMPEZIP The validity checks of the &ZOMCT control structure failed.
- 91040
- OMPEZIP The $ZMSTATE state entry block address is not initialized.
- 91044
- OMPEZIP The validity check of the $ZMSTATE entry block failed.
- 91048
- OMPEZIP The $ZIIP service request cannot be issued in XM-mode.
- 91052
- OMPEZIP The scheduling of the target enclave SRB routine failed.
- 91056
- OMPEZIP The DISABLE service request cannot locate the $ZMSTATE state entry block.
- 91060
- OMPEZPP The $ZMSTATE state entry block is not valid.
- 91064
- 91064 There are no zIIPs processors defined for the z/OS® image.
- 91076
- OMPEZIP The Disable post-processor EPA is not initialized.
- 91096
- OMPEZIP The zIIP jobstep TCB environment is not valid.
- 92000
- OMPEHVS The return code of the $ZTOKEN CREATE service request is nonzero.
- 92004
- OMPEHVS The issued service request is incorrect.
- 92008
- OMPEHVS The service request stopped abnormally.
- 92012
- OMPEHVS The DELETE service request is not supported in SRB-mode.
- 92016
- OMPEHVS The virtual storage is insufficient.
- 92020
- OMPEHVS The specified storage heap structure cannot be found.
- 92024
- OMPEHVS In the pool, no extents are available.
- 92028
- OMPEHVS The heap virtual storage segment to be freed cannot be found.
- 92032
- OMPEHVS The BUILD service request cannot to be issued in SRB-mode.
- 92036
- OMPEHVS The MODE= service request macro operand is not valid.
- 92040
- OMPEHVS The specified heap virtual storage subpool is not valid.
- 92044
- OMPEHVS The LOC= service request macro operand is not valid.
- 92048
- OMPEHVS The USAGE= service request macro operand is not valid.
- 92052
- OMPEHVS The TOKEN= macro operand contains a value of zero.
- 92056
- OMPEHVS The TOKEN= macro operand points to an invalid SH31 block.
- 92060
- OMPEHVS The validity check of the $ZSHCT control structure failed.
- 92064
- OMPEHVS The validity check of the $ZSHCT control structure identifier failed.
- 92068
- OMPEHVS No $ZSHCT control table slots are available.
- 92200
- OMPEHVS The zIIP TCB address cannot be found.
- 92204
- OMPEHVS The validity checks of the $ZMSTATE service failed.
- 92208
- OMPEHVS The value of the TCB address is null.
- 92212
- OMPEHVS The specified TOKEN= macro operand is not valid.
- 92216
- OMPEHVS The validity check of the $ZSH31 data structure failed.
- 92220
- OMPEHVS In SRB-mode, the $ZHEAP FREE service request cannot be issued with the macro operand USAGE=ANY.
- 92224
- OMPEHVS The owner TCB address of the heap virtual storage manager $ZHEAP FREE service request does not match.
- 92228
- OMPEHVS The TCB address owner is not valid.
- 92232
- OMPEHVS A zero length value is supplied.
- 92236
- OMPEHVS The length exceeds the maximum size.
- 92240
- OMPEHVS The heap virtual storage manager $ZHEAP FREE service request is issued in an incorrect state.
- 92244
- OMPEHVS The specified ADDR= macro operand is not valid.
- 92248
- OMPEHVS The specified LENGTH= macro operand is not valid.
- 92252
- OMPEHVS The specified cell pool ID is not valid.
- 92256
- OMPEHVS The specified MODE= macro operand is not valid.
- 92260
- OMPEHVS The TCB token cannot be found.
- 92264
- OMPEHVS The OMCT control table cannot be found.
- 92268
- OMPEHVS The specified TOKEN=TCB macro operand is not valid.