A fix is available
APAR status
Closed as program error.
Error description
An application called System SSL which called ICSF to send a secure request to a cryptographic coprocessor. This request contained data (which we will call malformed-data) that caused the cryptographic coprocessor to take a checksum error and then it went into type II recovery. Since the request could not be processed on that coprocessor, ICSF routed the request to another coprocessor and the same thing happened. That coprocessor took a checksum error and went into recovery. ICSF continued to route the request to the next coprocessor until there were no more left to attempt to process the request on. At this point ICSF failed the request and passed a return code of 12 back to System SSL. A RC of 12 to System SSL indicates that the ICSF hardware (cryptographic coprocessors) are no longer available and all subsequent calls that require the ICSF hardware will fail. The only way to have System SSL make calls to ICSF again is to recycle the applications that are using System SSL. This APAR along with a co-req MCL, when both are applied will allow ICSF to take a dump to capture the malformed data and also to prevent ICSF from redriving the request to another coprocessor. ** NOTE ***************************************************** The PTF can be applied before the MCL or the MCL can be installed before the PTF. The order the fixes are applied does not matter and no harm will occur if you run with either fix without the other. The bottom line is that both fixes are needed to be installed so a dump can be taken if you were to experience the problem reported by this APAR. ******************************************* THE FOLLOWING PTFs ARE IN ERROR: UA71386 HCR7780 UA71385 HCR7790 UA71388 HCR77A0 UA71387 HCR77A1 THE PTFS ARE FIXED BY APAR OA47157 See APAR descriptions for details *******************************************
Local fix
After the cryptograpic coprocessors have completed recovery (which take about 60 seconds) all applications that are using System SSL will need to be recycled. Please be aware that if there are multiple lpars sharing these coprocessors, applications using System SSL on all lpars will need to be recycled if System SSL has detected that the ICSF hardware has gone away.
Problem summary
**************************************************************** * USERS AFFECTED: Users of ICSF with cryptographic processor * **************************************************************** * PROBLEM DESCRIPTION: An application called ICSF and the * * request contained malformed data. The * * data in the request caused a * * cryptographic processor to fail * * and go into type II recovery. ICSF * * routed the request to another active * * processor which also went into * * recovery. All active processors end * * up in recovery which causes * * applications to fail or use alternate * * cryptographic resources. * * * * The request with the malformed data * * does not cause ICSF to ABEND and the * * request was not captured in a dump. * **************************************************************** * RECOMMENDATION: * **************************************************************** Problem Summary -------------------------------------------------------------- A request with malformed data forces a processor into recovery. ICSF request routing caused all active processors into recovery due to the bad request.
Problem conclusion
This APAR along with the changes to the cryptographic processor firmware will cause ICSF to ABEND S18F RSN447. The dump will capture the request for analysis. The application with the request causing the ABEND will get a return code 8 reason code '89B'x (2203). The following new reason codes for return code 8 will be documented in the next available version of the ICSF Application Programmers Guide (SC14-7508-00) Appendix A. ICSF and TSS Return and Reason Codes Reason Codes for Return Code 8 (8) Reason Code '89B'x (2203) A malformed request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '89C'x (2204) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '89D'x (2205) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '89E'x (2206) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '89F'x (2207) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A0'x (2208) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A1'x (2209) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A2'x (2210) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A3'x (2211) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A4'x (2212) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A5'x (2213) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A6'x (2214) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A7'x (2215) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A8'x (2216) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8A9'x (2217) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8AA'x (2218) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8AB'x (2219) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8AC'x (2220) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8AD'x (2221) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8AE'x (2222) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. Reason Code '8AF'x (2223) A request caused processor recovery and ICSF takes a dump to capture the data for analysis. User action: Contact the system programmer to save the dump and contact the ICSF administrator to contact IBM. The following new reason code for ABEND18F will be documented in the next available version of the ICSF System Programmers Guide (SC14-7507-00) and z/OS MVS System Codes (SA38-0665-00) 18F Code Explanation 447 Malformed request caused processor recovery
Temporary fix
********* * HIPER * *********
Comments
×**** PE15/03/14 FIX IN ERROR. SEE APAR OA47157 FOR DESCRIPTION
APAR Information
APAR number
OA43012
Reported component name
ICSF/MVS
Reported component ID
568505101
Reported release
780
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-08-08
Closed date
2013-11-07
Last modified date
2015-03-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA71385 UA71386 UA71387 UA71388 OA44869
Modules/Macros
CSFENCPN CSFENSND CSFINIT CSFINPVT
| SA38066500 | SC14750800 | SC14750700 |
Fix information
Fixed component name
ICSF/MVS
Fixed component ID
568505101
Applicable component levels
R7A0 PSY UA71388
UP13/11/08 P F311 Ž
R7A1 PSY UA71387
UP13/11/08 P F311 Ž
R780 PSY UA71386
UP13/11/08 P F311 Ž
R790 PSY UA71385
UP13/11/08 P F311 Ž
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"780"}]
Document Information
Modified date:
09 January 2021