![]() | ![]() | ![]() | ![]() | ![]() |
During initialization when SAS is validating the license, it scans the Physical Configuration Communication Area (PCCA). However, it limits this scan to the first 16 Central Processors (CPs). If SAS does not find a General Purpose (GP) processor within the first 16 CPs, then SAS fails to initialize and terminates with RC U0999. To circumvent this issue, ensure that a GP processor is varied online within the first 16 CP slots.
In SAS® 9.4M5 (TS1M5), which is where the original issue noted above was addressed, SAS initialization might fail with RC=0998. In this scenario, a symptom dump in the JOBLOG shows System Completion Code=0C4 in module SASHOST (depending on the entry to SAS that is used, this could be SASXA1 or SASXAL).
Symptom dump output looks similar to the following:
The abend occurs due to a LOAD instruction mapping off Register 10, which has EBCDIC data (in the above dump, this is the x'F0F8F0C6'). This behavior occurs due to a storage overlay because of encountering more than 16 CPs during initialization.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | Base SAS | z/OS 64-bit | 9.4_M1 | 9.4_M8 | 9.4 TS1M1 | 9.4 TS1M8 |
z/OS | 9.4_M1 | 9.4_M8 | 9.4 TS1M1 | 9.4 TS1M8 |