System Generation Manual for G-Series RVUs

SYSGENR Messages
System Generation Manual for G-Series RVUs—523407-001
A-34
SYSGENR Message Descriptions
Cause. The file specified as system code has not been bound starting at segment 5.
This error can occur if you create system code by using BIND outside of SYSGENR.
Effect. SYSGENR terminates.
Recovery. Ensure that you are using the correct version of BIND when running
SYSGENR.
Cause. The sum of the optional control block specifications and the allocation for I/O
system data structures has exceeded the available system data space. Or, a table in
the system data segment is larger than 64K words. This message appears in the body
of the listing, at the point where the error was detected.
Effect. SYSGENR terminates.
Recovery. Gather the items listed on page A-1, then call your service provider.
Cause. SYSGENR has created a system image. The NSR-X variable is that specified
by the SYSTEM_PROCESSOR_TYPE entry in the CONFTEXT file. This message is
displayed on the home terminal and appears at the end of the listing to indicate
termination status.
Effect. SYSGENR continues.
Recovery. Informational message only; no corrective action is needed.
Cause. The system library code file filename, which is referenced in the
SYSTEM_LIBRARY_CODE_FILES entry, is a multiple segment file that also contains
one or more interrupt procedures. This message appears in the body of the listing, at
the point where the error was detected.
Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates.
Recovery. Gather the items listed on page A-1, then call your service provider.
SYSTEM CODE MUST START AT SEGMENT 5
SYSTEM DATA SPACE OVERFLOW
SYSTEM IMAGE IS FOR AN NSR-X SYSTEM
SYSTEM LIBRARY CODE FILE filename is MULTI-SEGMENT, BUT
CONTAINS INTERRUPT PROCEDURES