Problem Note 3065: Phase 3 Kernel Initialization message if ERRORFLG is part of SETINIT
In Release 8.1 TS1M0, if ERRORFLG is part of the SETINIT, SAS
abends with the following error on MVS:
+(SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
+UNABLE TO INITIALIZE THE SAS KERNEL
IEF450I SASINSTA COPYINIT - ABEND=S000 U0999 REASON=00000000
and the following error on CMS:
ERROR: Initialization of SETINIT information from SASHELP failed.
FATAL: Unable to initialize the options subsystem.
(SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
UNABLE TO INITIALIZE THE SAS KERNEL
This abend occurs any time the SETINIT contains ERRORFLG, even if
the site is running on a properly licensed CPU.
During the MVS installation of Release 8.1 TS1M0, if ERRORFLG is
part of the RENEWPRM member of the control data set, the SASINSTA job
abends with the above message.
During the CMS installation of Release 8.1 TS1M0, if ERRORFLG is
part of the SETNAME SAS file loaded from tape, the GETSAS exec will
abend with the above message during application of the SETINIT.
Circumvention on CMS:
Apply the zap Z8013065. There is no need to reapply the SETINIT or
rerun GETSAS. If abend occurred while executing GETSAS, rebuild the SAS
Registry file following the instructions in the install guide under the
Chapter "Maintaining the SAS System Under CMS".
Circumvention on MVS:
Apply the zap Z8013065. During the installation process the zap can be
applied with 2 different scenarios:
1. In the SASINSTA job, insert a job step that applies the zap
between the SASINIT step and the COPYINIT step.
2. Apply the zap to the &prefix.LIBRARY that aleady exists at the
time of the abend, then edit the SASEDITP member of the control
data set by uncommenting the line below, and re-run the
SASINEW and SASINSTA jobs.
*NO* START-W/LICENSE=ON <<=== Blank '*NO*' to begin at License
This is fixed in Release 8.2 TS2M0.
Operating System and Release Information
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
A zap for this issue for SAS 8.1(TS1M0) on MVS is available at: