Problem Note 68486: A SAS/CONNECT® spawner in the SAS 9.4M6 and SAS 9.4M7 releases executed on z/OS fails with a S0C4-10 abend
In the SAS® 9.4M6 (TS1M6) and SAS® 9.4M7 (TS1M7) releases on the z/OS operating system, a SAS/CONNECT spawner fails with a S0C4-10 abend. This problem occurs when the following container hot fixes are applied:
- K1P001, which contains the individual hot fixes I8E004, I8E005, and I5V005 and the dependent hot fix K1M001
- K1P002, which contains the individual hot fixes I8E004, I8E005, I5V007, and I9R050 and the dependent hot fix K1M001
Note: You also see the message below in addition to the S0C4-10 abend:
USER COMPLETION CODE=0996 REASON CODE=000C4000
When you execute the ViewRegistry Report (see SAS KB0036131, "Using the ViewRegistry Report and other methods to determine the software releases and hot fixes that are installed"), you see that the individual hot fixes are listed. However, the references to the container hot fixes are not included because the report does not list container hot fixes.
The current workaround is to specify the SAS/CONNECT spawner parameter "-NETENCRYPTALGORITHM xxxxx" in the spawner's //PARMS file.
In the parameter, xxxxx is a valid value, such as SASProprietary. SASProprietary can be used by all sites without any configuration changes.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/CONNECT | z/OS | 9.4_M6 | | 9.4 TS1M6 | |
z/OS 64-bit | 9.4_M6 | | 9.4 TS1M6 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
The spawner abends after applying the container hot fix K1P001 or the container hot fix K1P002.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2022-02-01 11:09:17 |
Date Created: | 2021-10-08 09:29:02 |