| SAS Companion for the OS/2 Environment |
Internal errors are fatal errors that keep the SAS System from
starting. While you should not usually see these error messages, with a bit
of investigation you may be able to solve the problem that generated the message.
The following list describes the most common of these messages:
10 Host internal error: 10- CTRL BREAK was pressed during the initialization
of the SAS System. Therefore, the SAS System terminated.
11 Host internal error: 11- The SAS System needs more memory. To correct
the problem, change swapping to a disk with more free space or delete enough
files from the present swap disk to free up at least 20 megabytes of memory.
12 Host internal error: 12- The SAS System has determined that there
is an error in the specified SAS System configuration. A descriptive message
is displayed that indicates which system option is in error.
13 Host internal error: 13- Some part of the SAS System cannot be loaded.
The part in question is indicated via a descriptive message. Restore the missing
part to the appropriate directory.
24 Host internal error: 24- The SAS System was unable to initialize
display manager. A descriptive message is displayed indicating the appropriate
action.
208 Unable to open profile catalog.- The SAS System must have access to your
SASUSER.PROFILE catalog or be able to create one if one does not exist. Check
to be sure you have enough disk space, or if you are running the SAS System
on a network, that you have access to the correct files. The SASUSER.PROFILE
catalog is opened in the directory specified by the SASUSER system option,
described on SASUSER.
Also see Profile Catalog.
WORK library is undefined. SASUSER library is undefined.
SASHELP library is undefined.- Check your SAS command or SAS configuration
file to be sure that you have specified the directory path correctly for these
libraries.
302 SASMSG library is undefined.- Check your SAS command or SAS configuration
file to be sure that you have specified the directory path correctly for this
library.
Unable to initialize WORK library. Unable to initialize
SASUSER library.- Check your SAS command or SAS configuration
file to be sure that you have specified the correct directory for the WORK
and SASUSER libraries. If you are running the SAS System on a network, be
sure you have access to the necessary files.
401 Unable to initialize the message subsystem.- Check your SAS command or SAS configuration
file to be sure that you have specified the directory path correctly for all
SAS data libraries. Also check to see if your SAS configuration file is where
it should be. If you are sure you have specified the directory paths correctly,
contact your SAS Site Representative. It is possible that SAS message files
have become corrupt or have been inadvertently deleted.
601 Invalid SETINIT information.- Check your SETINIT information for errors.
For more information, see the installation instructions for Version 8 of
the SAS System for OS/2.
602 CORE catalog could not be accessed for options initialization.- The CORE catalog cannot be accessed. This
may be caused by having the date on your PC set incorrectly. Use the OS/2
DATE command to verify and set the date.
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
