SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 60730: Initialization of SAS® results in system abend 0C4 when there are no General Processors configured within the first 16 Central Processors

DetailsHotfixAboutRate It

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:

  IEA995I SYMPTOM DUMP OUTPUT  707
             SYSTEM COMPLETION CODE=0C4  REASON CODE=00000010
              TIME=01.41.44  SEQ=00362  CPU=0000  ASID=02CB
              PSW AT TIME OF ERROR  078D3000   AA391330  ILC 4  INTC 10
                ACTIVE MODULE           ADDRESS=00000000_2A3696F8  OFFSET=00027C38
                NAME=SASHOST
                DATA AT PSW  2A39132A - FFE758A0  60AC58B0  A0305820
                AR/GR 0: 0000005B/00080000   1: 00000000/00012BF0
                      2: 00000000/00000000   3: 00000000/8000A000
                      4: 00000000/2A3964F8   5: 00000000/2A3911B4
                      6: 00000000/0000B108   7: 00000000/00012418
                      8: 00000000/2A3C2918   9: 00000000/00080000
                      A: 00000000/F0F8F0C6   B: 00000000/8000A000
                      C: 00000000/8000A000   D: 00000000/00012C10
                      E: 00000000/2A36DB48   F: 00000000/2A3911B4
              END OF SYMPTOM DUMP

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.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemBase SASz/OS 64-bit9.4_M19.4_M89.4 TS1M19.4 TS1M8
z/OS9.4_M19.4_M89.4 TS1M19.4 TS1M8
* 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.