z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


18F

z/OS MVS System Codes
SA38-0665-00

18F

Explanation

An abend occurred during the processing of the Integrated Cryptographic Service Facility/MVS (ICSF/MVS) main task.

Reason codes are as follows:
Code
Explanation:
02
No response was received from a card.
03
Error in the ICSF mainline cross memory environment.
04
Error loading or calling installation exits.
05
The entry code in the component trace environment is not valid.
09
Error in the interface to the event notification facility.
0A
Error from the component trace routine.
0B
ICSF could not load a required exit.
0C
Exit number is not valid.
0D
ICSF could not obtain a cross memory linkage index.
0E
ICSF could not set a cross memory authorization index.
0F
ICSF could not create an entry table for space-switching PC routines.
10
ICSF could not connect its entry table to the system tables.
12
ICSF could not establish an ENF listen exit.
13
ICSF could not issue a broadcast ENF signal.
14
ICSF could not establish an ESTAE during initialization.
1B
ICSF could not interpret the options data set.
1C
Serious error encountered during processing of the CICS® Wait List data set.
1E
Start of changeEntry code to CSFKSTRE routine not valid.End of change
1F
Error from DSPSERV CREATE in the data space create routine.
20
Error from ALESERV ADD in the data space create routine.
21
Error from ALESERV EXTRACT in the data space create routine.
22
Error from ALESERV DELETE in the data space create routine.
23
Error from DSPSERV DELETE in the data space create routine.
24
An unexpected branch was taken in a utility program.
2C
The refresh code in the component trace routine is not valid.
Start of change2DEnd of change
Start of changeA cryptographic coprocessor returned a bad condition code. The coprocessor has been fenced off.End of change
33
ICSF could not load a required installation service.
37
Error loading an application service.
38
ICSF could not install the compatibility cryptographic SVC.
3C
Invalid domain index specified in ICSF parameters.
3F
Error from ATTACH in the I/O subtask control routine.
41
Error in initialization.
42
Error in initialization - ATTACH.
48
Cryptographic public key operation disabled.
49
Cryptographic public key operation not initialized.
4A
Cryptographic public key operation not available.
4C
Error in CSFENICP module.
4D
Error from ATTACH in CSFENICP.
4F
Erroneous result from PCI device.
50
Error in messaging interface for PCI devices.
5A
Incorrect entry code passed to dataspace controller.
62
Unexpected output data from CSVDYLPA.
63
Unexpected return code from CSVDYLPA.
6D
Error from ATTACH of CSFINQKP.
6F
Error from ATTACH of the CSFPLMWT task.
70
Error in termination manager, tasks holding ENQs.
71
Error in termination manager, tasks waiting for ENQs.
73
Invalid CCP index in an internal call.
74
Serial number and CCP index mismatch.
75
Error from ATTACH of CSFMISDT.
76
Start of changeError from ATTACH in sysplex subtask control routine.End of change
77
Error from ATTACH of CSFKSRCK.
78
Error from ATTACH of CSFPLPST.
79
Error from ATTACH of CSFKSRPK.
7A
Error from ATTACH of CSFPLTST.
7B
Error from ATTACH of CSFKSRTK.
7C
FIPS known answer tests failed.
7D
Installation option FIPSMODE(YES,FAIL(YES)) or FIPSMODE(COMPAT,FAIL(YES)) is specified, but the IBM® System z® model type or the release of z/OS® does not support FIPS.
80
Parameter block for the compatibility services is not valid.
8C
The master key version number is not valid.
8D
The status word from the hardware contained a response code that is not valid.
8E
The status word from the hardware contained a response code that is not valid.
90
The status word from the hardware contained a response code that is not valid.
92
The key encrypting key (KEK) was the wrong type or was not a no control vector (NOCV) KEK.
94
The variant passed to the twist processing routine is not valid.
98
ICSF ended abnormally. An exit installed with the FAIL=ICSF option has ended abnormally.
A1
Requested system key was not found in the in-storage and/or the DASD CKDS.
A2
Error in the CKDS retrieval routine. The requested system key has a MAC that is not valid.
A3
Error in the CKDS retrieval routine. The requested dummy key was not found.
A4
Output type not valid.
A5
Error in parameters for internal ICSF service call.
A6
Cryptographic public key request not valid.
A7
Public key token type not valid.
A8
Hardware configuration is not enabled.
A9
Hardware configuration contains wrong key size.
AA
Arithmetic operand is not valid.
AC
Error in public key processing.
AD
Error in public key processing.
AE
Value for the FUNCTION parameter is unrecognized on call to CSFKSIPE.
AF
Error occurred in module CSFKSPSC.
B0
Error occurred in ATTACH macro issued in CSFKSPSC.
B3
Domain in CPRB does not match CCVE.
B4
Length of CPRB in SPB is wrong.
B5
Return code 16 from Cryptographic Coprocessor.
B6
Too much data for the CPRB/parameter block.
B7
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
B8
Reencipher of the CKDS failed due to an error in processing on the Cryptographic Coprocessor.
BA
Error in Pause processing.
C5
Error from an attempt to create or access a PKCS #11 data space.
D4
Failed latch create from ISGLCRT.
D5
Attempted storage overlay in hash table manager.
D6
Error in PAUSE processing.
D7
Error allocating PAUSE element.
D8
Error in PAUSE while waiting for I/O to complete.
D9
Program error detected on IXCQUERY invocation.
DA
Error in PAUSE while waiting for cross-system services to complete.
DB
Start of changeError in ISGENQ during KDS sysplex serialization.End of change
DC
Start of changeError in IXCMSGO during KDS sysplex serialization.End of change
DD
Start of changeError in IEAVPSE2 during KDS sysplex serialization.End of change
DE
Error in ISGENQ during PKDS sysplex serialization.
DF
Error in IXCMSGO during PKDS sysplex serialization.
E0
Error in IEAVPSE2 during PKDS sysplex serialization.
E1
Error in ISGENQ during TKDS sysplex serialization.
E2
Error in IXCMSGO during TKDS sysplex serialization.
E3
Error in IEAVPSE2 during TKDS sysplex serialization.
E5
Attempted to free a serialization block that was already freed.
E6
Error in IEAVPSE2 while waiting for KDS rename.
E7
Error in ISGLCRT processing of the CKDS latch set.
E8
Error in ISGLCRT processing of the PKDS latch set.
EA
Start of changeError establishing ESTAE for KDS sysplex subtask.End of change
EB
Error establishing ESTAE for PKDS cross-system services task.
EC
Error establishing ESTAE for TKDS cross-system services task.
ED
Start of changeError initializing KDS sysplex subtask.End of change
EE
Error initializing PKDS cross-systems task.
EF
Error initializing TKDS cross-systems task.
F0
Start of changeError in IXCJOIN for ICSF KDS sysplex group.End of change
F1
Error in IXCJOIN for ICSF PKDS sysplex group.
F2
Error in IXCJOIN for ICSF TKDS sysplex group.
Start of changeF3End of change
Start of changeError from IXCQUERY request in CSFPLCMD module.End of change
Start of changeF4End of change
Start of changeError from IXCMSGO request in CSFPLMSR module.End of change
Start of changeF5End of change
Start of changeError from IEAVPSE2 request in CSFPLMSR module.End of change
Start of changeFAEnd of change
Start of changeError determining sysplex KDS cluster member list in CSFPLCMD.End of change
100
The return code from an installation exit is not valid.
101
Compatibility mode services are not available. ICSF is running in PCF non-compatibility mode (COMPAT(NO)).
102
Condition code from an ICSF (instruction) macro is not valid.
103
The return code from the RCFSTAT macro is not valid.
104
The return code from the RCFCONF macro is not valid.
105
A master key version change occurred during the reencipher, conversion or dynamic CKDS update process.
107
Error in public key processing.
108
Error in interprocessor communication.
109
Bad response code for PKSC/PKA request.
10A
Bad PKSC/PKA request block.
10B
PCI device queue full error.
10C
Unknown response code from PCI device instructions.
110
Invalid return code from security exit.
111
Invalid return code from CSFEXIT1.
112
Invalid return code from CSFEXIT2.
113
Invalid return code from CSFEXIT3.
114
Invalid return code from CSFEXIT4.
115
Invalid return code from CSFEXIT5.
116
Invalid return code from security termination exit.
117
Error in RESMGR processing.
118
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
119
Rewrap of CKDS failed due to an error on coprocessor.
181
The exit list in the common I/O routine is not valid.
182
The access control block in the common I/O routine is not valid.
183
The request parameter list in the common I/O routine is not valid.
184
MAC Generate or MAC Verify failed with RC=12 during dynamic CKDS update processing.
185
An incorrect function request was passed to common I/O routines for dynamic CKDS update processing.
186
An unexpected return or reason code was returned from common I/O routines during dynamic CKDS update processing.
187
Incorrect CKDS record created during dynamic CKDS update processing.
191
A blank message skeleton was retrieved.
192
A matching message table was not found.
193
The message was not found.
194
The substitution tag is not valid.
195
The message buffer size was exceeded.
197
CAMQ reply PSMID does not match.
198
CCP reply PSMID does not match.
199
Unknown response code after dequeue CAM.
Start of change19AEnd of change
Start of changeXCF message is too big for internal ICSF buffer.End of change
Start of change19BEnd of change
Start of changeAn IXCMSGI request failure occurred receiving an XCF message.End of change
205
The control vector (CV) in the cryptographic key data set (CKDS) record is not valid.
206
The conversion service received a CKDS that is not valid.
207
WLM encountered a bad data area.
300
A function that was passed to the dialog service routine is not valid.
301
Improper key specified for clear key input dialog.
380
A message ID that was used in the component trace routine is not valid.
381
The control block in the component trace routine is not valid.
400
Condition code from an ICSF (instruction) macro is not valid.
401
Condition code from an ICSF (instruction) macro is not valid.
402
Condition code from an ICSF (instruction) macro is not valid.
403
Condition code from an ICSF (instruction) macro is not valid.
404
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
407
Unexpected condition code during PCI device initialization.
408
Condition code from an ICSF (instruction) macro is not valid.
409
Condition code from an ICSF (instruction) macro is not valid.
40A
Error in parameters for internal ICSF service call.
40B
Unknown response code from PCI device instructions.
40C
Condition code from an ICSF (instruction) macro is not valid.
40D
Error in parameters for internal ICSF service call.
40E
Condition code from an ICSF (instruction) macro is not valid.
40F
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
410
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
414
Unexpected condition code while sending a request to a PCI device.
415
Unexpected condition code while sending a request to a PCI device.
416
Unexpected condition code while receiving a reply from a PCI device.
417
Unexpected condition code while receiving a reply from a PCI device.
418
Error accessing PKCS#11 tokens.
419
Error accessing PKCS#11 objects.
41B
Error in parameters for internal ICSF service call.
41C
Reencipher of the CKDS failed due to an error in processing on the Cryptographic Coprocessor.
41D
Reencipher of the CKDS failed due to an error in processing on the Cryptographic Coprocessor.
41E
Error in parameters for internal ICSF service call.
41F
Error in parameters for internal ICSF service call.
420
Error in parameters for internal ICSF service call.
421
Error in parameters for internal ICSF service call.
423
Error in parameters for internal ICSF service call.
424
Error in parameters for internal ICSF service call.
426
Erroneous result from PCI device.
427
Error in parameters for internal ICSF service call.
428
Error in parameters for internal ICSF service call.
429
Unexpected condition code while receiving a reply from a PCI device.
42A
Unexpected condition code while receiving a reply from a PCI device.
42B
Unexpected condition code while sending a request to a PCI device.
42C
Unexpected condition code while receiving a reply from a PCI device.
42D
Unexpected condition code while receiving a reply from a PCI device.
42F
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
430
Compatibility mode service EMK is not available. ICSF is running in PCF non-compatibility mode (COMPAT(NO)).
432
Condition code from an ICSF (instruction) macro is not valid.
433
Condition code from an ICSF (instruction) macro is not valid.
434
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
435
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
436
Compatibility mode service EDC is not available. ICSF is running in PCF non-compatibility mode (COMPAT(NO)).    
43A
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
43C
The reply CPRB or parameter block cannot be processed because of invalid format or invalid data.
43F
Too much data for the CPRB/parameter block.
444
Storage for structure insufficient in PKCS #11 attribute processing.
445
Storage for structure insufficient in PKCS #11 attribute processing.
446
Storage for structure insufficient in PKCS #11 attribute processing.
447
Storage for structure insufficient in PKCS #11 attribute processing.
448
Storage for structure insufficient in PKCS #11 attribute processing.
449
Condition code from an ICSF (instruction) macro is not valid.
44A
Condition code from an ICSF (instruction) macro is not valid.
44B
Condition code from an ICSF (instruction) macro is not valid.
44D
Error in parameters for internal ICSF service call.
44E
Error in parameters for internal ICSF service call.
44F
Error while loading signed module CSFINPV2.
450
Error from PAUSE in CSFENDQT.
451
Error Allocating a PET in CSFENDQT.
452
Error from ATTACH in CSFINCPM.
453
Internal error - improper call to CSFV2KW2.
454
Internal error - unrecognized token.
455
Internal error - unexpected reencipher result.
456
Internal error - PKT full (CSFKSIPE)
457
Internal error - PKT full (CSFPLPST
458
Incorrect key record.
Start of change45AEnd of change
Start of changeThe CSFPLMWT task received a bad RC from IEAVPSE2.End of change
Start of change45BEnd of change
Start of changeThe CSFPLMRT task received inconsistent internal control information.End of change
Start of change45CEnd of change
Start of changeThe CSFSMBTM module received inconsistent internal control information.End of change
Start of change45DEnd of change
Start of changeCSFPLCMD/CSFPLMRT pause failure (XCF notify exit).End of change
Start of change45EEnd of change
Start of changeAn IXCMSGO request failure occurred sending an XCF message.End of change
Start of change45FEnd of change
Start of changeAn XCF message exit error occurred during ICSF sysplex processing.End of change
Start of change460End of change
Start of changeA sequence number error occurred during ICSF sysplex processing.End of change
Start of change461End of change
Start of changeA cache update failure occurred during ICSF sysplex processing.End of change
Start of change462End of change
Start of changeThe CSFKSIDC module was called with an incorrect function code.End of change
Start of change463End of change
Start of changeThe CSFKSIIO module was called with an invalid IO function request.End of change
Start of change464End of change
Start of changeThe CSFKSIIO module ran out of dynamic storage.End of change
Start of change465End of change
Start of changeICSF forced termination.End of change
Start of change466End of change
Start of changeAn error occurred during ATTACH of the CSFMISTP task.End of change
Start of change467End of change
Start of changeCSFENXCP detected a bad XCP message payload length.End of change
Start of change468End of change
Start of changeCSFENXCP detected a bad XCP message encoding length.End of change
Start of change469End of change
Start of changeCSFENXCP detected a bad XCP responses length.End of change
Start of change46AEnd of change
Start of changeCSFSMBTI inconsistent internal control information.End of change
Start of change46BEnd of change
Start of changeTerminate stuck I/O subtask.End of change
Start of change46DEnd of change
Start of changeCSFENXCP message response too large.End of change
Start of change46EEnd of change
Start of changeReencipher of TKDS failed due to an error on coprocessor.End of change
Start of change46FEnd of change
Start of changeCSFNCGKP data returned from XCP invalid BER format.End of change
Start of change470End of change
Start of changeCSFNCCMK error in internal ICSF service call parms.End of change
Start of change471End of change
Start of changeCSFNCRNC error in internal ICSF service call parms.End of change
Start of change472End of change
Start of changeCSFKSCS2 detects unusable KDS.End of change
Start of change473End of change
Start of changeCSFNCUWK data returned from XCP invalid BER format.End of change
Start of change474End of change
Start of changeCSFNCUWK data returned from XCP has unexpected attrs.End of change
Start of change475End of change
Start of changeCSFPLXNU XCF problems in the sysplex.End of change

System action

If the abend occurred during ICSF initialization, ICSF ends abnormally.

In general, if the abend occurred after ICSF is available and running, your application or unit of work ends. ICSF is still available. However, if the error occurred when trying to set the cryptographic domain index or if an exit that is installed with the FAIL=ICSF option abends, ICSF ends abnormally.

Programmer response

Review the reason codes on the dump title to see if the abend was an installation or user error. Also check to see if the reason code was an installation-generated reason code. If you cannot resolve the problem, search problem reporting databases for a fix for the problem. If no fix exists, save the dump, gather the dump header record, and contact the IBM Support Center.

Debugging aids and recovery-related information are discussed in ICSF System Programmer's Guide.

Source

Integrated Cryptographic Service Facility (ICSF)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014