System Generation Manual for G-Series RVUs

SYSGENR Messages
System Generation Manual for G-Series RVUs—523407-001
A-25
SYSGENR Message Descriptions
Effect. If SYSGENR cannot start the version of the program listed in the table above,
SYSGENR terminates. Exception for SWID: If SYSGENR encounters errors trying to
create a SWID process, SYSGENR continues to normal completion (if there are no
other errors); but object-file fingerprints are not obtained or recorded in the OSCONFIG
file.
Recovery. Refer to the Guardian Procedure Errors and Messages Manual for
corrective action for the NEWPROCESS error.
Cause. SYSGENR is unable to create a temporary file because the system ran out of
process names.
Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates.
Recovery. Gather the items listed on page A-1, then call your service provider.
Cause. After code was accelerated, SYSGENR has found an invalid virtual address in
an object file.
Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates.
Recovery. Gather the items listed on page A-1
, then call your service provider.
Cause. The system process code object file filename was compiled with the
NOFIXUP compile option and was not bound later using BIND. This type of file is not
permitted by SYSGENR as a system process file. 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. Inform your service provider about filename.
SYSGEN^BINDER
The version of BINDER in $SYSTEM.SYSTEM
SYSGEN^DISKGEN
The version of DISKGEN at the SYSGENR
default volume and subvolume
SYSGEN^SWID
The version of SWID in $SYSTEM.SYSTEM
NO NAME WAS AVAILABLE TO BE CREATED FOR THE SYSTEM FILE
OBJECT FILE ACCELERATED AT WRONG VIRTUAL ADDRESS:
OBJECT FILE COMPILED WITH NOFIXUP OPTION: filename
OBJECT FILE FIXUP ERROR nnn1, nnn2 FILE: filename
ASSIGN Command SYSGENR Uses Instead