Operator Messages Manual
Chapter 100 Spooler and Spooler Plus Messages
The messages in this chapter are generated by the Spooler and
Spooler Plus subsystems. The subsystem ID displayed by these messages
includes SPOOLER as the subsystem name. | 1 Spooler Collector $process_name State Change, Event: Collector State Change, Cause: cause, Previous
state: prev_state, Current state: cur_state | | process_name | identifies the spooler collector process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-1 describes each text string displayed in the
cause field. Table 100-1 Spooler Message 1 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Cold Initialization Started | The spooler
collector is establishing a new spooling environment. No spooler objects
are defined. No jobs are present. | | Crash Recovery Started | During warmstart
initialization, the collector found the data file in the open state
and attempted a recovery. | | Dormant | The spooler is unavailable and is
either in the early stages of startup or the last stages of shutdown. | | Drain Started | The spooler collector is draining. | | No More Opens Allowed | The spooler collector
will not allow any more opens. | | Started | The initialization is complete and
the start command has been issued. | | Takeover Started | The primary process has
failed and the backup is taking over. | | Warm Initialization Started | The spooler
collector is in the process of a warm initialization. |
| | prev_state | identifies the previous state of the spooler collector
process that generated the event. Table 100-2 describes all the spooler collector states.
Not all states may be returned to this field. Table 100-2 Spooler Collector Process States | State | Meaning |
|---|
| Active | The spooler is active and ready to
accept jobs. | | Cold | The spooler collector is in the process
of a cold initialization. | | Dormant | The spooler collector is not running. | | Drain | The spooler collector is draining. | | No More Opens | The spooler collector will
not accept any new opens. | | Recovery | The collector data file was found
open when initialization started, and is now in the recovery state. | | Takeover | The primary process has failed
and the backup is taking over. | | Warm | The spooler collector is in the process
of a warm initialization. |
| | cur_state | identifies the current state of the spooler collector
process that generated the event. Process states are described in Table 100-2. Not all states may be returned
to this field. |
Cause This event occurs when the state of spooler collector is changing. Effect None Recovery Informational message only; no corrective action is needed. |
| 3 Spooler Collector $process_name Unavailable, Event: File cannot be accessed, Cause: cause, Previous state: prev_state, Current state: cur_state, FS Error: error_code, File: filename, Base object: object, Detail: detail_text, Symptom: symptom | | process_name | identifies the spooler collector process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-3 describes each text string displayed in the
cause field. Table 100-3 Spooler Message 3 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| I/O error | A read, write, or position operation
failed for the specified file. |
| | prev_state | identifies the previous state of the spooler collector
process that generated the event. Table 100-2 describes all the spooler collector states.
Not all states may be returned to this field. | | cur_state | identifies the current state of the spooler collector
process that generated the event. Process states are described in Table 100-2. Not all states may be returned
to this field. | | error_code | identifies a file-system error code. | | filename | may contain the spooler supervisor process name, the
spooler control file name, or a question mark (?) if no file name
is applicable. | | object | identifies the object containing the error or the
object associated with the error. | | detail_text | provides additional explanatory information. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of this text string. |
Cause During spooler operation, the collector could not read, or write,
or position within the spooler collector’s data file. The detail field describes detailed cause information. Table 100-4 describes the cause of each
text string displayed in the symptom field. Table 100-4 Spooler Message 3 Causes | Symptom Field Text String | Cause |
|---|
| {3_1 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX.
This condition occurred during drain while the spooler collector was
writing out the bit map block to the spooler collector data file. | | {3_2 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call POSITION.
This condition occurred during drain while the spooler collector was
writing out the bit map block to the spooler collector data file. | | {3_3 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX.
This condition occurred during drain while the spooler collector was
writing out the bit map block to the spooler collector data file. | | {3_4 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call WRITEX.
This condition occurred during drain while the spooler collector was
writing out the bit map block to the spooler collector data file. | | {3_5 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call FILE_GETINFOLIST_.
This condition occurred during coldstart initialization while the
spooler collector was receiving file information about its data file. | | {3_6 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call FILENAME_DECOMPOSE_.
This condition occurred during coldstart initialization while the
spooler collector was receiving file information about the spooler
collector data file. | | {3_7 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call READUPDATE.
This condition occurred during a takeover when the spooler collector
was attempting to read the $RECEIVE file. | | {3_8 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call WRITEREAD.
This condition occurred during takeover and while the spooler collector
was attempting to reestablish communication with the supervisor. | | {3_9 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call POSITION
or WRITEX. This condition occurred during a takeover by the backup
process and while the spooler collector was attempting to rewrite
the last I/O to its data file. | | {3_10 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call GET_LIB_FNAME_.
This condition occurred when the spooler collector was attempting
to create its own backup process and while attempting to go to the
library file name. | | {3_11 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call GET_SWAP_FNAME_.
This condition occurred while the spooler collector was attempting
to create its own backup process. | | {3_12 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call FILENAME_DECOMPOSE_.
This condition occurred while the spooler collector was attempting
to create its own backup process. | | {3_13 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call GET_PROG_FNAME_.
This condition occurred while the spooler collector was attempting
to create its own backup process. | | {3_14 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call PROCESS_GETINFO_.
This condition occurred while the spooler collector was attempting
to create its own backup process. | | {3_15 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call GET_MYNAME_.
This condition occurred during spooler collector initialization. | | {3_16 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred during initialization and while the spooler
collector was attempting to read the $RECEIVE file. | | {3_17 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call FILENAME_SCAN_.
This condition occurred during initialization and while attempting
to establish communication with the spooler supervisor. | | {3_18 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred during initialization and while the spooler
collector was attempting to establish communication with the spooler
supervisor. | | {3_19 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred during initialization and while the spooler
collector was attempting to open its data file. | | {3_20 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred during initialization and while the spooler
collector was attempting to open its data file. | | {3_21 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call SETMODE.
This condition occurred during initialization and while the spooler
collector was attempting to read its data file. | | {3_22 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call POSITION.
This condition occurred during initialization and while the spooler
collector was attempting to read its data file. | | {3_23 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX. | | {3_24 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call READX.
This condition occurred during initialization and while the spooler
collector was attempting to read its data file. | | {3_25 TCOLMAIN} | The collector received the
indicated file-system error after the system procedure call SETMODE.
This condition occurred during initialization and while the spooler
collector was attempting to read its data file. | | {3_26 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred during initialization and while the spooler
collector was attempting to read its data file. | | {3_27 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call REPLY.
This condition occurred during normal processing and while the spooler
collector was attempting to reply to a message received in its $RECEIVE
file. | | {3_28 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call READUPDATE.
This condition occurred during normal processing and while the spooler
collector was attempting to read its $RECEIVE file. | | {3_29 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call READDATA.
This condition occurred during normal processing and while the spooler
collector was attempting to read a data block off its data file. | | {3_30 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call READDATAX.
This condition occurred during normal processing and while the spooler
collector was attempting to read a data block off its data file. | | {3_31 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call POSITION.
This condition occurred while the spooler collector was attempting
to do big-block I/O on its data file using SETMODE 141. | | {3_32 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call READX.
This condition occurred while the spooler collector was attempting
to do big-block I/O on its data file using SETMODE 141. | | {3_33 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call READX.
This condition occurred while the spooler collector was attempting
to do big-block I/O on its data file using SETMODE 141. | | {3_34 TCOLMAIN} | The spooler collector’s
data file received an I/O error after a nowait I/O on a data block. | | {3_35 TCOLMAIN} | The spooler collector received
an I/O error while checking a nowait I/O for its $RECEIVE file. | | {3_36 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred while the spooler collector was attempting
to open its data file during recovery. | | {3_37 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call SETMODE.
This condition occurred while the spooler collector was attempting
to enable big-block I/O using SETMODE 141 during recovery. | | {3_38 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call SETMODE.
This condition occurred while the spooler collector was attempting
to enable big-block I/O using SETMODE 141 during recovery. | | {3_39 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred while the spooler collector was enabling big-block
processing during recovery. | | {3_40 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call POSITION.
This condition occurred while the spooler collector was enabling big-block
processing during recovery. | | {3_41 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX.
This condition occurred while the spooler collector was enabling big-block
processing during recovery. | | {3_42 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call WRITEX.
This condition occurred while the spooler collector was enabling big-block
processing during recovery. | | {3_43 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred while the spooler collector was enabling big-block
processing during recovery. | | {3_44 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call SETMODE.
This condition occurred while the spooler collector was enabling big-block
processing during recovery. | | {3_45 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call SETMODE.
This condition occurred while the spooler collector was enabling big-block
processing during recovery. | | {3_46 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call OPEN_FILE_.
This condition occurred while the spooler collector was enabling big-block
processing during recovery. | | {3_47 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_48 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call POSITION.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_49 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_50 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call WRITE.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_51 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_52 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call POSITION.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_53 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_54 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call WRITEX.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_55 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call AWAITIOX.
This condition occurred while the spooler collector was attempting
to do a waited I/O on its data file. | | {3_56 TCOLMAIN} | The spooler collector received
the indicated file-system error after the system procedure call POSITION
or WRITEX. This condition occurred while the spooler collector was
attempting to do a nowait I/O on its data file. |
Effect The spooler collector stops. Recovery Examine the file-system displayed in error_code. Make changes
as required to permit the file (filename) to be read from, written
to, or positioned. |
| 4 Spooler Collector $process_name Unavailable, Event: Internal error, Cause: cause, Previous state: prev_state, current
state: cur_state Detail: detail
text, Symptom: symptom | | process_name | identifies the spooler collector process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-5 describes each text string displayed in the
cause field. Table 100-5 Spooler Message 10 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Diagnostic | A programmed internal error check
has failed. |
| | prev_state | identifies the previous state of the spooler collector
process that generated the event. Table 100-2 describes all the spooler collector states.
Not all states may be returned to this field. | | cur_state | identifies the current state of the spooler collector
process that generated the event. Process states are describes in Table 100-2. Not all states may be returned
to this field. | | detail_text | provides additional explanatory information. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of this text string. |
Cause The NonStop Kernel operating system detected an unmanaged calculation
error or a serious system environmental condition. During spooler
collector operation, the detail field describes
detailed cause information. Table 100-6 describes the cause of each text string displayed in the symptom field. Table 100-6 Spooler Message 4 Causes | Symptom Field Text String | Cause |
|---|
| {4_1 TCOLMAIN} | During initialization, the
spooler collector detected an incorrect process type while making
system procedure call PROCESS_GETPAIR_. The error returned is shown
in the detail text. | | {4_2 TCOLMAIN} | During initialization, the
spooler collector received an unexpected error while decomposing its
process handle. The error received is shown in the detail text. | | {4_3 TCOLMAIN} | The spooler collector’s
backup process began a takeover before the primary process had finished
initialization. | | {4_4 TCOLMAIN} | The DP2 buffersize for the
spooler collector’s data file is not compatible with the spooler
collector’s configured unit size.See installation documentation
for specifying the correct unit size and/or the DP2 buffer size for
the data file. | | {4_5 TCOLMAIN} | The DP2 buffersize for the
spooler collector’s data file is not compatible with the spooler
collector’s configured unit size.See installation documentation
for specifying the correct unit size and/or the DP2 buffer size for
the data file. | | {4_6 TCOLMAIN} | The DP2 buffersize for the
spooler collector’s data file is not compatible with the spooler
collector’s configured unit size.See installation documentation
for specifying the correct unit size and/or the DP2 buffer size for
the data file. | | {4_7 TCOLMAIN} | The DP2 buffersize for the
spooler collector’s data file is not compatible with the spooler
collector’s configured unit size.See installation documentation
for specifying the correct unit size and/or the DP2 buffer size for
the data file. | | {4_8 TCOLMAIN} | During coldstart initialization,
the spooler collector could not allocate the needed extended memory
segment. | | {4_9 TCOLMAIN} | During initialization, a
system error occurred while the spooler collector was attempting to
use its allocated extended memory segment. The error from the call
to USESEGMENT is shown in the detail text. | | {4_10 TCOLMAIN} | During warmstart initialization,
a nonrecoverable error occurred while the spooler collector was attempting
to complete a recovery of its data file. | | {4_11 TCOLMAIN} | During initialization, the
spooler collector could not read the startup message from the spooler
supervisor. | | {4_12 TCOLMAIN} | During initialization, the
spooler collector could not read the startup message from the spooler
supervisor. | | {4_13 TCOLMAIN} | During spooler collector
warmstart initialization, the spooler collector read the master record
from its data file. The only valid states for the master record are
OPEN or CLOSED. Any other state indicates a corrupted or invalid data
file. | | {4_14 TCOLMAIN} | During warmstart initialization,
the spooler collector checked to verify that the unit size, indicated
on the master record, is the same as the one given in the start message
from the spooler supervisor. If they are not the same, the data file
is different than the one the spooler collector was processing prior
to drain. | | {4_15 TCOLMAIN} | The error indicates that
an incorrect system version was used for running this version of the
spooler collector. | | {4_16 TCOLMAIN} | During initialization, the
spooler collector detected that it was using an incorrect version
of the spooler collector. | | {4_17 TCOLMAIN} | The spooler collector received
the indicated file-system error while attempting to create heap space.
The error returned from the call to POOL_DEFINE_ is shown in the detail
text. | | {4_18 TCOLMAIN} | The spooler collector received
the indicated file-system error while attempting to free pool space.
The error returned from the call to POOL_GETSPACE_ is shown in the
detail text. | | {4_19 TCOLMAIN} | The spooler collector received
the indicated file-system error while attempting to free pool space.
The error returned from the call to POOL_PUTSPACE_ is shown in the
detail text. | | {4_20 TCOLMAIN} | The spooler collector received
the indicated file-system error while attempting to create heap space.
The error returned from the call to SEGMENT_ALLOCATE_ is shown in
the detail text. | | {4-TRAP} | During spooler collector operation,
the NonStop Kernal has detailed an unmanaged calculation error or
a serious system environmental condition. |
Effect The spooler collector stops. Recovery For the 4-TRAP cause, examine the trap information in the event
message to find out what type of trap occurred. For the following
trap types, attempt to clear the environmental block and warmstart
the spooler collector: For all other message 4 types, consult with your service provider
to help resolve the problem. Warmstart the spooler collector. If the
failure reoccurs following warmstart, determine if a specific object
is implicated and try to remove this object from the spooler and reintroduce
it after the problem has been solved. If these steps fail, coldstart
the spooler collector. |
| 7 Spooler Collector $process_name Maximum exceeded, Event: NO available openers, Cause: cause | | process_name | identifies the spooler collector process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. |
Cause This event occurs when the spooler collector has reached the
maximum number of openers. Effect None Recovery Take action to reduce the number of opens to the spooler collector. |
| 8 Spooler Collector $process_name Maximum exceeded, Event: No available space in data file, Cause: cause | | process_name | identifies the spooler collector process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. |
Cause This event occurs when the spooler collector data file has reached
the maximum allocated units. Effect None Recovery Take action to reduce the number of jobs using space in the
spooler collector’s data file. |
| 9 Spooler Collector $process_name, Event: Transient event, Cause: cause, Detail: detail_text, Symptom:
symptom | | process_name | identifies the spooler collector process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-7 describes each text string displayed in the
cause field. Table 100-7 Spooler Message 9 Cause Field Text Strings | Cause Field Test String | Meaning |
|---|
| Diagnostic | A programmed internal error check
has failed. See detail text for additional information. |
| | detail_text | provides additional explanatory information. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of this text string. |
Cause During spooler collector operation, the NonStop Kernel operating
system detected a transient error. The detail field describes detailed
cause information. Table 100-8 describes
the cause of each text string displayed in the symptom field. Table 100-8 Spooler Message 9 Causes | Symptom Field Text String | Cause |
|---|
| {9_1 TCOLMAIN} | The blocking buffer space
exceeded its maximum allowable space. All available extended memory
for blocking job data has been exhausted. This condition occurs when
the spooler collector exceeds the maximum number of openers. | | {9_2 TCOLMAIN} | The spooler collector was
configured with an odd-sized unit specification. This condition is
inefficient since the spooler collector always uses a 1024-byte buffer.
In this case, it is possible for the best configuration to have a
4096-byte buffer. Configuring the unit size so that it is module 4
causes a 4096-byte large buffer. | | {9_3 TCOLMAIN} | For the job process indicated
in the message, the maximum allowable pages or lines was exceeded.
The processing of that job ends. | | {9_4 TCOLMAIN} | When the spooler collector
called the Spooler library routine SPOOLSTART2 on behalf of a non-level
3 user, it received an unexpected error. This is a nonrecoverable
internal error that causes the spooler collector to abend and produce
a SAVEABEND file. | | {9_5 TCOLMAIN} | When the spooler collector
called the spooler-library routine SPOOLCONTROL on behalf of a non-level
3 user, it received an unexpected error. This is a nonrecoverable
internal error that causes the spooler collector to abend and produce
a SAVEABEND file. | | {9_6 TCOLMAIN} | When the spooler collector
called the spooler library routine SPOOLSETMODE on behalf of a non-level
3 user, it received an unexpected error. This is a nonrecoverable
internal error that causes the spooler collector to abend and produce
a SAVEABEND file. | | {9_7 TCOLMAIN} | When the spooler collector
called the spooler library routine SPOOLWRITE on behalf of a non-level
3 user, it received an unexpected error. This is a nonrecoverable
internal error that causes the spooler collector to abend and produce
a SAVEABEND file. | | {9_8 TCOLMAIN} | When the spooler collector
does a nowait I/O on its data file, it follows a certain protocol.
When this is not followed, an internal error occurs causing the spooler
collector to abend and produce a SAVEABEND file. | | {9_9 TCOLMAIN} | When the spooler collector
does a nowait I/O on its $RECEIVE file, it follows a certain protocol.
When this is not followed, an internal error occurs causing the spooler
collector to abend and produce a SAVEABEND file. | | {9_10 TCOLMAIN} | The messaging protocol between
the supervisor and the spooler collector was not followed. This is
an internal error that causes the spooler collector to abend and produce
a SAVEABEND file. | | {9_11 TCOLMAIN} | When the spooler collector
calls to AWAITIOX for a nowait I/O, it expects the data type to be
one of a few types. If it is not, an internal error occurs causing
the spooler collector to abend and produce a SAVEABEND file. | | {9_12 TCOLMAIN} | The last time the spooler
collector did a checkpoint, it received an invalid-parameter status
message from the file system. The error returned is shown in the detail
text. This is an internal error that causes the spooler collector
to abend and produce a SAVEABEND file. | | {9_13 TCOLMAIN} | When the spooler collector
called the spooler library routine SPOOLCONTROLBUF on behalf of a
non-level 3 user, it received an unexpected error. This is a nonrecoverable
internal error that causes the spooler collector to abend and produce
a SAVEABEND file. | | {9_15 TCOLMAIN} | The spooler collector bitmap
filemarker or block type is invalid causing an internal error. This
is a nonrecoverable error that causes the spooler collector to abend
and produce a SAVEABEND file. | | {9_16 TCOLMAIN} | The spooler collector bitmap
filemarker or block type is invalid causing an internal error. This
is a nonrecoverable error that causes the spooler collector to abend
and produce a SAVEABEND file. | | {9_17 TCOLMAIN} | The spooler collector bitmap
filemarker or block type is invalid causing an internal error. This
is a nonrecoverable error that causes the spooler collector to abend
and produce a SAVEABEND file. | | {9_18 TCOLMAIN} | When deallocating a unit
for a job, the spooler collector detected that the corresponding bit
in its bitmap was already cleared. This is an internal error that
causes the spooler collector to abend and produce a SAVEABEND file. | | {9_19 TCOLMAIN} | When checking to see if
the current caller of the spooler collector was a valid user, it encountered
a user number out of the range of the user table. This is an internal
error that causes the spooler collector to abend and produce a SAVEABEND
file. | | {9_20 TCOLMAIN} | During recovery, the spooler
collector detected the data file is corrupt and cannot continue. This
is an internal error that causes the spooler collector to abend and
produce a SAVEABEND file. | | {9_21 TCOLMAIN} | During recovery, the spooler
collector detected the data file is corrupt and cannot continue. This
is an internal error that causes the spooler collector to abend and
produce a SAVEABEND file. | | {9_22 TCOLMAIN} | While servicing a request
to delete a job, the spooler collector detected an inconsistency in
the bitmap and in the data it expected to release. This is an internal
error that causes the spooler collector to abend and produce a SAVEABEND
file. | | {9_23 TCOLMAIN} | While servicing a request
to delete a job, the spooler collector detected an inconsistency in
the bitmap and in the data it expected to release. This is an internal
error that causes the spooler collector to abend and produce a SAVEABEND
file. | | {9_24 TCOLMAIN} | While servicing a request
to delete a job, the spooler collector detected an inconsistency in
the bitmap and in the data it expected to release. This is an internal
error that causes the spooler collector to abend and produce a SAVEABEND
file. | | {9_26 TCOLMAIN} | While it was about to write
a job’s data to the spooler collector’s data file, the
spooler collector detected an invalid data buffer length. This is
an internal error that causes the spooler collector to abend and produce
a SAVEABEND file. | | {9_27 TCOLMAIN} | When the spooler collector
does a checkpoint to its backup process, sometimes the size of the
message is too large to process in one call and it is broken up into
two or more calls. If a process failure occurs during this multiphase
checkpoint, then the backup process cannot continue. This is a nonrecoverable
error that causes the spooler collector to abend and produce a SAVEABEND
file. | | {9_28 TCOLMAIN} | A file-system error occurred
when the spooler collector was in the process of starting a new job,
and an attempt was made to decompose the file name of the user’s
process handle. | | {9_29 TCOLMAIN} | A file-system error occurred
when the spooler collector was in the process of starting a new job,
and an attempt was made to decompose the file name of the user’s
process handle. | | {9_30 TCOLMAIN} | The spooler collector’s
backup process is down because of a processor failure. | | {9_31 TCOLMAIN} | The spooler collector could
not create a backup process because the processor failed. | | {9_32 TCOLMAIN} | This is a notification that
the spooler collector’s backup process processor went down and
a system message was received by the collector’s primary process. | | {9_33 TCOLMAIN} | The processor for the primary
process of the spooler collector is down, and the backup process is
taking over. | | {9_34 TCOLMAIN} | When the spooler collector
tried to reestablish communication with the supervisor, a file-system
error occurred in its system procedure call to WRITEREAD. The error
returned is shown in the detail text. | | {9_35 TCOLMAIN} | The spooler collector received
an unexpected message from the supervisor. This is an internal error
that causes the spooler collector to abend and produce a SAVEABEND
file. | | {9_36 TCOLMAIN} | An inconsistency occurred
in the messaging protocol between the spooler collector and the spooler
supervisor. This is an internal error that causes the spooler collector
to abend and produce a savebend file. | | {9_37 TCOLMAIN} | While the spooler supervisor
was giving the spooler collector LISTOPENS information, the communications
protocol between the supervisor and the spooler collector failed.
The file-system error, returned from the spooler collector’s
attempt to write to the supervisor, is included in the message. This
error causes the spooler collector to enter into the drain state. | | {9_38 TCOLMAIN} | During the processing of
a request from the spooler supervisor to get information from the
spooler collector, the communications protocol failed. The file-system
error, returned from the spooler collector’s attempt to write
to the supervisor, is included in the message. This error causes the
spooler collector to enter into the drain state. | | {9_39 TCOLMAIN} | The spooler collector’s
backup process is down. The message shows the error returned from
the last attempt to checkpoint. | | {9_40 TCOLMAIN} | The spooler collector has
detected that its backup process is down for an unknown reason. | | {9_41 TCOLMAIN} | When the spooler collector
tried to create its backup process, it received an error in its system
procedure call to PROCESS_CREATE_. The error returned is included
in the detail text. | | {9_42 TCOLMAIN} | When the spooler collector
tried to create its backup process, it received an error in its system
procedure call to PROCESS_CREATE_. The error returned is included
in the detail text. | | {9_43 TCOLMAIN} | After creating its backup
process, the spooler collector could not run CheckAllocate on the
extended segment. The error returned from the system procedure call
to SEGMENT_ALLOCATE_CHKPT_ is included in the detail text. | | {9_44 TCOLMAIN} | During warmstart initialization,
the spooler collector detected that the DP2 BUFFERSIZE of its data
file had been modified between the last drain and the beginning of
the warmstart. This may affect the internal buffering of the spooler
collector by making it more efficient or less efficient. See the Spooler
Utilities Reference Manual and the Spooler Plus Utilities Reference
Manual for a description of the relationship between the spooler collector’s
unit size and the DP2 BUFFERSIZE and how it affects the spooler collector’s
internal buffering. The old and new DP2 BUFFERSIZE are shown in the
detail text. |
Effect The spooler collector continues. Recovery Analyze the error and perform corrective action where possible. | | | |  | NOTE: Some of the calls to this procedure are followed by a TFDS SAVEABEND:
the transient nature is only till the SAVEABEND occurs. This method
uses the collector to continue to the SAVEABEND. | | | | |
|
| 10 Spooler Collector $process_name Usage Threshold, Event: Data file capacity, Current usage level: level, Usage unit: unit,
timestamp LCT (current): time, Configured
high value: high_value, Configured low
value: low_value, Configured maximum value: max_value | | process_name | identifies the spooler collector process generating
the event. | | level | indicates the amount of disk space utilized by the
spooler collector process as a percentage of the total disk space
allocated to the data file. | | unit | identifies the type of unit used to measure the event.
Type 1 is a percentage unit and type 19 is a count. This event message
always returns type 1 (percentage). | | time | indicates the time that the event occurred. | | high_value | identifies the configured high-threshold value for
the type of event that has occurred. | | low_value | identifies the configured low-threshold value for
the type of event that has occurred. | | max_value | identifies the configured maximum value of units the
spooler collector can allocate. |
Cause This event occurs when the amount of disk space used exceeds
the configured high-threshold value (high_value), or when the amount of disk space used falls below the configured
low-threshold value (low_value) after the
high‑threshold value has been exceeded. Effect None Recovery Delete unneeded jobs or move them to another collector using
SPOOLCOM. |
| 11 Spooler Collector $process_name Usage Threshold, Event: Opener capacity, Current usage level: level, Usage unit: unit,
timestamp LCT (current): time, Configured
high value: high_value, Configured low
value: low_value, Configured maximum value: max_value | | process_name | identifies the spooler collector process generating
the event. | | level | indicates the number of openers against the spooler
collector. | | unit | identifies the type of unit used to measure the event.
Type 1 is a percentage unit and type 19 is a count. This event message
always returns type 2 (count). | | time | indicates the time that the event occurred. | | high_value | identifies the configured high-threshold value for
the type of event that has occurred. | | low_value | identifies the configured low-threshold value for
the type of event that has occurred. | | max_value | identifies the configured maximum value of units the
spooler collector can allocate. |
Cause This event occurs when the number of openers against the identified
spooler collector exceeds the configured high-threshold value (high_value), or when the number of openers against
the identified spooler collector falls below the configured low-threshold
value (low_value) after the high-threshold
value has been exceeded. Effect None Recovery An application may be in a loop opening the collector. Use LISTOPENS
to determine if the number of opens is indicative of an application
problem. |
| 301 Spooler Print Process $process_name Unavailable, Event: Internal error, Cause: cause,Previous state: prev_state, Current state: cur_state, Detail: detail_text, Symptom: symptom | | process_name | identifies the spooler print process generating the
event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-9 describes each text string displayed in the cause field. Table 100-9 SPOOLER Message 301 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Diagnostic | A programmed internal error check
has failed. |
| | prev_state | identifies the previous state of the spooler print
process that generated the event. Table 100-10 describes the spooler supervisor process states.
Not all states may be returned to this field. Table 100-10 Spooler Print Process States | State | Meaning |
|---|
| Active | The print process is active and ready
to accept jobs. | | Dormant | The print process is not running. |
| | cur_state | identifies the current state of the spooler print
process that generated the event. Process states are described in Table 100-10. Not all states may be returned
to this field. | | detail_text | provides additional explanatory information. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of this text string. |
Cause During spooler print operation, the NonStop Kernel operating
system has detected an error that it will not recover from. The symptom
field describes detailed cause information. Table 100-20 “SPOOLER Message 403 Causes”Table 100-11 describes the cause of each text string displayed
in the symptom field. Table 100-11 Spooler Message 301 Causes | Symptom Field Text String | Cause |
|---|
| {301_1 TFSTMISC} | A timeout error occurred
while the print process was waiting for an I/O completion. | | {301_2 TFSTMISC} | A file-system error occurred
while the print process was waiting for an I/O completion. | | {301_3 TFSTMISC} | A file-system error occurred
while the print process was waiting for an I/O completion. | | {301_4 TFSTMISC} | An internal error has occurred.
An OPEN call completed without a process control block (PCB). | | {301_5 TFSTMISC} | An internal error has occurred.
An OPEN call completed without a process control block (PCB) with
none pending. | | {301_6 TFSTMISC} | An unknown device completion
occurred for the device and for the file. | | {301_7 TFSTMISC} | An unknown buffer completion
occurred for the device and index indicated. | | {301_8 TFSTMISC} | An error occurred while
the print process was attempting to use an extended memory segment. | | {301_9 TFSTMISC} | An error occurred in the
buffer management. The error that was returned from a call to a system
procedure call DEFINEPOOL is shown. | | {301_10 TFSTMISC} | An error occurred while
the print process was attempting to use an extended memory segment. | | {301_11 TFSTMISC} | An error occurred while
the print process was attempting to use an extended memory segment. | | {301_12 TFSTMISC} | An internal error occurred
while the print process was attempting to make an insertion into a
linked list. The head pointer and block pointer are shown. | | {301_13 TFSTMISC} | An internal error has
occurred. An OPEN call completed without a process control block (PCB). | | {301_14 TFSTMISC} | An unexpected error was
returned upon the completion of reading a $RECEIVE file. | | {301_15 TFSTMISC} | An error occurred while
the print process was reading a $RECEIVE file. | | {301_16 TFSTMISC} | An error occurred in the
buffer management while the print process was attempting to return
a buffer to a pool. The call to USESEGMENT failed. | | {301_17 TFSTMISC} | An error occurred in the
buffer management while the print process was attempting to return
a buffer to a pool. The call to PUTPOOL failed. | | {301_18 TFSTMISC} | An internal error occurred
when the stack indicated grew too large for the device indicated. | | {301_21 TFSTMISC} | This is not a named process. | | {301_22 TFSTMISC} | A file-system error occurred. | | {301_23 TFSTMISC} | The print process could
not open the $RECEIVE file. | | {301_24 TFSTMISC} | The print process could
not open the $RECEIVE file. | | {301_25 TFSTDO} | An error occurred while
the print process was attempting to use an extended memory segment.
The segment number is shown in the error message. This error causes
the print process to abend and produce a SAVEABEND file. | | {301_26 TFSTDO} | An error occurred while
the print process was attempting to use an extended memory segment.
The segment number is shown in the error message. This error causes
the print process to abend and produce a SAVEABEND file. | | {301_27 TFSTDO} | An error occurred while
the print process was attempting to use an extended memory segment. | | {301_28 TFSTDO} | An error occurred while
the print process was attempting to use an extended memory segment. | | {301_29 TFSTDO} | An error occurred while
the print process was attempting to use an extended memory segment. | | {301_30 TFSTSUPR} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTSTATUS2, but received an error return instead. This
is an internal error and causes the print process to abend and produce
a SAVEABEND file. | | {301_31 TFSTMISC} | The print process received
an error while doing a system procedure call to CONTROL for the named
device. | | {301_32 TFSTMISC} | The print process received
an error while doing a system procedure call to CONTROL for the named
device. | | {301_35 TFSTMISC} | An error occurred because
the spooler print process was not a named process. | | {301_36 TFSTMISC} | An error occurred because
the spooler print process was not a named process. | | {301_37 TFSTMISC} | The print process could
not do an open on the spooler supervisor. | | {301_38 TFSTMISC} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTINIT, but received an error return instead. | | {301_39 TFSTDO} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTSTART2, but received an error return instead. | | {301_40 TFSTDO} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTINFO, but received an error return instead. | | {301_41 TFSTDO} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTINFO, but received an error return instead. | | {301_42 TFSTDO} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTSTART2, but received an error return instead. | | {301_43 TFSTSUPR} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTCOMPLETE, but received an error return instead. | | {301_44 TFSTMISC} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTINIT, but received an error return instead. | | {301_45 TFSTSUPR} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTREADCOMMAND, but received an error return instead. | | {301_46 TFSTSUPR} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTREADCOMMAND, but received an error return instead. | | {301_47 TFSTSUPR} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTSTAT, but received an error return instead. |
Effect The spooler print process stops. Recovery Analyze the error and perform corrective action where possible. |
| 304 Spooler Print Process $process_name Transient, Event: Transient event, Cause: cause, Detail: detail_text, Error: error_code, Symptom: symptom | | process_name | identifies the spooler print process generating the
event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-12 describes each text string displayed in the cause field. Table 100-12 SPOOLER Message 304 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Diagnostic | A programmed internal error check
has failed. |
| | detail_text | provides additional explanatory information. | | error_code | identifies a file-system error code. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of this text string. |
Cause During spooler print process operation, the NonStop Kernel operating
system detected a transient error. The detail field describes detailed cause information. Table 100-13 describes the cause of each text string displayed
in the symptom field. Table 100-13 Spooler Message 304 Causes | Symptom Field Text String | Cause |
|---|
| {304_1 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_2 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_3 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_4 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_5 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_6 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_7 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_8 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_9 TFSTMISC} | The print process detected
that the device had a Multibyte Character Set Translation Value (MBCS)
conflict. It will use a SETMODE 144 value instead of CHARMAP. | | {304_10 TFSTMISC} | The print process could
not obtain a buffer for the Multibyte Character Set Translation (MBCS). | | {304_11 TFSTMISC} | After a communications
error, there is a possible duplicate of pages printed on the device
for the job. | | {304_12 TFSTMISC} | A SNAX-connected device
had an error indicated in the error text. | | {304_13 TFSTMISC} | An error was returned
from the call to the spooler library procedure PRINTREAD. | | {304_14 TFSTMISC} | The print process failed
to increase the size of a buffer for the device. An error returned
from the system procedure call RESIZESEGMENT. | | {304_15 TFSTMISC} | The print process could
not find CONTYPE in the configuration file for the device. | | {304_16 TFSTMISC} | The print process detected
an illegal CONTYPE in the configuration file for the device. | | {304_17 TFSTMISC} | The print process detected
an illegal TIMEOUT in the configuration file for the device. | | {304_18 TFSTMISC} | The print process detected
an illegal BUFFERSIZE in the configuration file for the device. | | {304_19 TFSTMISC} | The print process detected
an illegal ERRORRECOVERY in the configuration file for the device. | | {304_20 TFSTMISC} | The print process detected
an illegal EOLWRITE in the configuration file for the device. | | {304_21 TFSTMISC} | The print process could
not allocate a user conversation buffer for the device. The error
that returned from call to the system procedure call SEGMENT_ALLOCATE_
is included in the error text. | | {304_22 TFSTMISC} | The print process could
not allocate a user conversion buffer for the device. | | {304_23 TFSTMISC} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTREAD, but received an error return instead. | | {304_24 TFSTMISC} | The print process attempted
to communicate with the spooler supervisor using the spooler library
procedure PRINTREAD, but received an error return instead. | | {304_25 TFSTMISC} | The print process could
not find a SHADOW entry in the FASTCNFG configuration file. | | {304_26 TFSTMISC} | The print process could
not find a SHADOW entry in the FASTCNFG configuration file. | | {304_27 TFSTMISC} | The print process could
not open the SHADOW file at the location for the device. | | {304_28 TFSTMISC} | The print process could
not open the SHADOW file at the location for the device. | | {304_30 TFSTMISC} | The print process detected
a Multibyte Character Set Translation (MBCS) error for the device. | | {304_31 TFSTMISC} | An error occurred while
the print process was attempting to write to the SHADOW file. The
error, indicated in the error text, is from the system procedure call
FILE_OPEN_. | | {304_32 TFSTMISC} | An error occurred while
the print process was attempting to write to the SHADOW file. The
error, indicated in the error text, is from the system procedure call
WRITEX. | | {304_33 TFSTMISC} | An error occurred while
the print process was attempting to do a system procedure call WRITEX. | | {304_34 TFSTMISC} | An error occurred while
the print process was attempting to call WRITEX. | | {304_35 TFSTMISC} | An error occurred while
the print process was attempting to call WRITEX. | | {304_36 TFSTMISC} | An error occurred while
the print process was attempting to call WRITEX. | | {304_37 TFSTMISC} | An error occurred while
the print process was attempting to call WRITEX. | | {304_38 TFSTMISC} | An error occurred while
the print process was attempting to call WRITEX. | | {304_39 TFSTDO} | When the print process attempted
to start the printing of a job on the device, it could not open the
data file receiving the error indicated in the error text. | | {304_40 TFSTDO} | When the print process attempted
to call the PRINTSTART2 procedure on behalf of the device, it received
the error indicated in the error text. | | {304_41 TFSTDO} | When the print process attempted
to call the PRINTSTART2 procedure on behalf of the device, it received
the error indicated in the error text. | | {304_42 TFSTDO} | When the print process attempted
to call the PRINTINFO procedure on behalf of the device, it received
the error indicated in the error text. | | {304_43 TFSTDO} | When the print process attempted
to reinstate a font job for the device specified, it could not open
the data file and received the file-system error indicated in the
error text. | | {304_44 TFSTDO} | When the print process attempted
to reinstate a font job for the device, it called the PRINTSTART2
procedure and received the error indicated in the error text. | | {304_45 TFSTDO} | When the print process attempted
to reinstate a font job for the device, it called the PRINTSTART2
procedure and received the error indicated in the error text. | | {304_46 TFSTSEND} | When the print process
attempted to send a CONTROLBUF to the device, it detected that the
Top of Form Substitution limit (2048) was exceeded in the job indicated
in the detail text. | | {304_47 TFSTSEND} | When the print process
attempted to send a CONTROLBUF to the device, it detected that the
Multibyte Character Set Translation Value (MBCS) Substitute Shift
to DBCS string was too long for the job indicated in the detail text. | | {304_48 TFSTSEND} | When the print process
attempted to send a CONTROLBUF to the device, it detected that the
Multibyte Character Set Translation Value (MBCS) Substitute Shift
to SBCS string was too long for the job indicated in the detail text. | | {304_49 TFSTSUPR} | The print process could
not open the spooler supervisor for the purpose of receiving status
information on behalf of the device specified in the detail text. | | {304_50 TFSTSUPR} | The print process could
not open the spooler supervisor for the purpose of receiving status
information on behalf of the device specified in the detail text. | | {304_51 TFSTSUPR} | The print process could
not open the spooler supervisor for the purpose of receiving status
information on behalf of the device specified in the detail text. | | {304_52 TFSTSUPR} | The print process could
not open the spooler supervisor for the purpose of receiving status
information on behalf of the device specified in the detail text. | | {304_53 TFSTCNFG} | The device could not open
the FASTCNFG configuration define file because of the file-system
error indicated in the error text. | | {304_54 TFSTCNFG} | The device could not open
the FASTCNFG configuration define file because of the file-system
error indicated in the error text. | | {304_55 TFSTCNFG} | The device could not open
the FASTCNFG configuration define file because of the file-system
error indicated in the error text. | | {304_56 TFSTCNFG} | The indicated configuration
file did an illegal indirection to another configuration file. | | {304_57 TFSTCNFG} | The device specified detected
an error when opening the print process configuration file. |
Effect The spooler print process continues. Recovery Analyze the error and make corrective action where possible. | | | | | NOTE: Some of the calls to this procedure are followed by a TFDS SAVEABEND:
the transient nature is only until the SAVEABEND occurs. This method
allows the spooler collector to continue to the point of the SAVEABEND. | | | | |
|
| 400 Spooler Supervisor $process_name State Change, Event: Spooler State Change, Cause: cause, Previous state: prev_state, current
state: cur_state | | process_name | identifies the spooler supervisor process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-14 describes each text string displayed in the cause field. Table 100-14 SPOOLER Message 400 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Cold Initialization Started | The spooler
supervisor is establishing a new spooling environment. No spooler
objects are defined. No jobs are present. | | Crash Recovery Started | During warmstart
initialization, the supervisor found the routed file in the open state
and will attempt to do a recovery. | | Dormant | The spooler is unavailable and in
either the early stages of startup or the last stages of shutdown. | | Drain Started | The spooler supervisor is
draining. | | Initialization Completed | Initialization
of the spooler is complete. | | Rebuild Started | A warmstart with new configuration
parameters has started. | | Started | The initialization is complete and
the start command has been issued. | | Takeover Completed | The backup process has
finished taking over from the primary process. | | Takeover Started | The primary process has
failed and backup is taking over. | | Warm Initialization Started | The spooler
supervisor is in the process of a warm initialization. |
| | prev_state | identifies the previous state of the spooler supervisor
process that generated the event. Table 100-15 describes all the spooler supervisor process
states. Not all states may be returned to this field. Table 100-15 Spooler Supervisor Process States | State | Meaning |
|---|
| Active | The spooler is active and ready to
accept jobs. | | Cold | The spooler supervisor is in the process
of a cold initialization. | | Dormant | The spooler supervisor is not running. | | Drain | The spooler supervisor is draining. | | No More Opens | The spooler supervisor will
not accept any new opens. | | Recovery | The supervisor data file was found
open when initialization started, and is now in the recovery state. | | Takeover | The primary process has failed
and the backup is taking over. | | Warm | The spooler supervisor is in the process
of a warm initialization. |
| | cur_state | identifies the current state of the spooler supervisor
process that generated the event. Process states are described in Table 100-15. Not all states may be returned
to this field. |
Cause This event occurs when the state of the spooler supervisor is
changing. Effect None Recovery Not applicable. |
| 402 Spooler Supervisor $process_name Unavailable, Event: Invalid Configuration specified, Cause: cause, Previous state: prev_state, Current state: cur_state, FS Error: error_code, File: filename, Base object: object, Symptom: symptom | | process_name | identifies the spooler supervisor process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-16 describes each text string displayed in the cause field. Table 100-16 SPOOLER Message 402 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Incorrect installation | Certain spooler components
must be installed together and must match in version. Startup parameters
must be correct in quantity and value. Validity checks are performed
to assure consistency and compatibility. |
| | prev_state | identifies the previous state of the spooler supervisor
process that generated the event. Table 100-15 describes all the spooler supervisor process
states. Not all states may be returned to this field. | | cur_state | identifies the current state of the spooler supervisor
process that generated the event. The process states are described
in Table 100-15. Not all states
may be returned to this field. | | error_code | identifies a file-system error code. | | filename | may contain the spooler supervisor process name, the
spooler control file name, or a question mark (?) if no file name
is applicable. | | object | identifies the object containing the error or the
object associated with the error. | | detail_text | provides additional explanatory information. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of this text string. |
Cause The cause of this event message depends on the text string displayed
in the symptom field. Table 100-17 describes the cause of each text string displayed in the symptom
field. Table 100-17 SPOOLER Message 402 Causes | Symptom Field Text String | Cause |
|---|
| {402_1 TSUPINIT} | During spooler initialization,
the spooler supervisor detected an invalid status (from PROCESS_GETPAIRINFO_)
for the process that created the supervisor (its caller). The only
valid status values are as follows: | | {402_2 TSUPINIT} | During spooler initialization,
the spooler supervisor could not obtain information (from PROCESSHANDLE_DECOMPOSE_)
about the process that created the supervisor (its caller). | | {402_3 TSUPINIT} | During spooler initialization,
the spooler supervisor detected that its own process identity was
not valid. | | {402_4 TSUPINIT} | During spooler startup,
the spooler supervisor detected an invalid file code for the specified
control file. The spooler can warmstart from only control files with
filecodes of 124 (C00), 125 (C20), 126 (C20ABA), 127 (D00, D10), OR
128 (current file code). | | {402_5 TSUPINIT} | During spooler startup,
the spooler supervisor detected an invalid control file version. This
code is retained inside file code 128 control files. Valid versions
for D41 spooler warmstart are 1 (C31), 3 (D20 to D21), and 5 (D41). | | {402_6 TSUPINIT} | During spooler startup,
the spooler supervisor detected an invalid message or status on $RECEIVE.
The supervisor was expecting a startup message from the caller. | | {402_7 TSUPINIT} | During spooler startup,
the spooler supervisor failed to receive a valid startup message from
its caller. | | {402_8 TSUPINIT} | During spooler startup,
the startup message received by the spooler supervisor contained an
invalid IN parameter. | | {402_9 TSUPINIT} | During spooler startup,
the IN parameter of the startup message received by the spooler supervisor
contained an invalid file name prefix for control file number 3. | | {402_10 TSUPINIT} | During spooler startup,
the IN parameter of the startup message received by the spooler supervisor
contained an invalid file name prefix for control file number 4. | | {402_11 TSUPINIT} | During spooler startup,
the coldstart parameters received by the spooler supervisor contained
an invalid value where the REBUILD directive is normally specified. | | {402_12 TSUPINIT} | During spooler startup,
the spooler supervisor received a REBUILD directive but no coldstart
parameters were provided. | | {402_13 TSUPINIT} | During spooler startup,
the spooler supervisor detected an incomplete quantity of coldstart
parameters. | | {402_14 TSUPINIT} | During spooler startup,
the spooler supervisor detected that one of the required coldstart
parameters was missing. | | {402_15 TSUPINIT} | During spooler startup,
the spooler supervisor detected extraneous coldstart parameters. | | {402_16 TSUPLOG} | An attempt was made to
start the spooler with an illegal startup parameter. Check the configuration
file and start again. | | {402_17 TSUPLOG} | An attempt was made to
start the spooler with an illegal startup parameter. Check the configuration
file and start again. |
Effect The spooler supervisor stops. Recovery Recovery from this event depends on the text string displayed
in the symptom field. Table 100-18 describes the recovery for
each text string displayed in the symptom field. Table 100-18 SPOOLER Message 402 Recovery Procedures | Symptom Field Text String | Recovery |
|---|
| {402_1 TSUPINIT} | Examine the invalid status.
Make changes as required in the calling process to permit the startup
to complete. Repeat the startup operation. | | {402_2 TSUPINIT} | Examine the file-system
error. Make changes as required in the calling process or its environment.
Repeat the startup operation. | | {402_3 TSUPINIT} | Examine the process (file)
name. Make sure the spooler supervisor is started as a named process.
Examine the error code (from PROCESS_GETINFO_ or FILENAME_DECOMPOSE_)
and make sure the process environment is valid. Repeat the startup
operation. | | {402_4 TSUPINIT} | Coldstart the spooler or
choose a spooler version that is able to use these version control
files and repeat the warmstart operation. | | {402_5 TSUPINIT} | Coldstart the spooler or
choose a spooler version that is able to use these version control
files and repeat the warmstart operation. | | {402_6 TSUPINIT} | Examine the file-system
error (from AWAITIO). See Appendix B for file-system error descriptions. Correct
the calling process or environment. Repeat the startup operation. | | {402_8 TSUPINIT} | Correct the startup message
IN parameter. Repeat the startup operation. | | {402_9 TSUPINIT} | Examine the file-system
error (from OLDFILENAME_TO_FILENAME_). See Appendix B for file-system error descriptions. Correct
any file name conflicts. Correct any errors in the startup IN parameter.
Repeat the startup operation. | | {402_10 TSUPINIT} | Check the file-system
error (from OLDFILENAME_TO_FILENAME_). See Appendix B for file-system error descriptions. Correct
any file name conflicts. Correct any errors in the startup IN parameter.
Repeat the startup operation. | | {402_11 TSUPINIT} | Correct the SPOOL startup
parameters. Repeat the startup operation. | | {402_12 TSUPINIT} | Provide the correct startup
parameters. These startup parameters are as follows and must be provided
in the following order:Maximum number of locations Maximum number of devices Maximum number of collectors Maximum number of print processes
Maximum number of batches Maximum number of device queue nodes
| | {402_13 TSUPINIT} {402_14 TSUPINIT} {402_15 TSUPINIT} | Provide the correct startup parameters. The startup parameters
are as follows and must be provided in the following order:Maximum number of locations Maximum number of devices Maximum number of collectors Maximum number of print processes
Maximum number of batches Maximum number of device queue nodes
| | {402_16 TSUPINIT} {402_17 TSUPINIT} | Examine
the file-system error. See Appendix B for file-system error descriptions. Correct
the file name, attributes, or the environment. Repeat the warmstart
operation. |
|
| 403 Spooler Supervisor $process_name Unavailable, Event: File cannot be accessed, Cause: cause, Previous state: prev_state, Current state: cur_state, S Error: error_code, File: filename, Base object: object, Symptom: symptom | | process_name | identifies the spooler supervisor process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-19 describes each text string displayed in the cause field. Table 100-19 SPOOLER Message 403 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Incorrect file code | The filecode for the
specified file was not expected. Only specific filecodes (representing
versions of spooler control files) are supported. | | FILE_CREATE_ error | The specified file could
not be created. There may be inadequate resources or an input error
to the create process. | | FILE_OPEN_ error | The specified file cannot
be opened. It may not exist or there may be a permission limitation. | | FILE_RENAME_ error | The file that has been
newly created could not be renamed to the specified name. The previous
file may not have been purged or the name may be invalid. | | I/O error | A read, write, or position operation
failed for the specified file. |
| | prev_state | identifies the previous state of the spooler supervisor
process that generated the event. Spooler supervisor process states
are described in Table 100-15. Not
all states may be returned to this field. | | cur_state | identifies the current state of the spooler supervisor
process that generated the event. Spooler supervisor process states
are described in Table 100-15. Not
all states may be returned to this field. | | error_code | identifies a file-system error code. | | filename | may contain the spooler supervisor process name, the
spooler control file name, or $RECEIVE. | | object | identifies the object containing the error or the
object associated with the error. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of these codes. |
Cause The cause of this event message depends on the text string returned
to the symptom field. Table 100-20 describes the cause of each
text string displayed in the symptom field. Table 100-20 SPOOLER Message 403 Causes | Symptom Field Text String | Cause |
|---|
| {403_1 TSUPMEM} | The spooler supervisor detected
an error while attempting to update an object on the control file.
The error returned from the call to POSITION is shown in the detail
text. | | {403_2 TSUPMEM} | The spooler supervisor detected
an error while attempting to update an object on the control file.
The error returned from the call to WRITEX is shown in the detail
text. | | {403_3 TSUPINIT} | During spooler initialization,
the spooler supervisor could not open its $RECEIVE file. | | {403_4 TSUPINIT} | During spooler startup,
the spooler supervisor could not open the specified control file. | | {403_5 TSUPRECV} | The spooler supervisor
received an error while attempting to read the $RECEIVE file. | | {403_6 TSUPJOB} | During spooler initialization,
an error occurred while converting a file name. | | {403_7 TSUPCACH} | The system procedure call
WRITEX failed while trying to delete a record from the spooler control
file. | | {403_8 TSUPCACH} | The system procedure call
WRITEX failed while trying to delete a record from the spooler control
file. | | {403_9 TSUPBKUP} | During spooler takeover,
the process could not read the $RECEIVE file. | | {403_10 TSUPBKUP} | During spooler takeover,
a RESETSYNC error occurred. | | {403_11 TSUPINIT} | During spooler initialization,
a FILE_PURGE_ failed. | | {403_12 TSUPINIT} | During spooler initialization,
the spooler supervisor attempted to get information about the control
file through the system procedure call FILE_GETINFOLISTBYNAME_, but
the call failed. | | {403_13 TSUPINIT} | During spooler initialization,
the spooler supervisor attempted to get information about the control
file through the system procedure call FILENAME_DECOMPOSE_, but the
call failed. | | {403_14 TSUPINIT} | During spooler initialization,
the spooler supervisor attempted to get information about the control
file through the system procedure call FILENAME_DECOMPOSE_, but the
call failed. | | {403_15 TSUPINIT} | During spooler initialization,
the spooler supervisor attempted to get information about the control
file through the system procedure call FILE_OPEN_, but the call failed. | | {403_16 TSUPINIT} | During spooler warmstart,
the spooler supervisor could not open the specified control file. | | {403_17 TSUPINIT} | During spooler coldstart
operation, the spooler supervisor could not write to the specified
control file. | | {403_18 TSUPINIT} | During spooler warmstart
operation, the spooler supervisor could not rename the new control
file to replace the purged version of the specified control file.
The purge of the old file may have failed. | | {403_19 TSUPINIT} | During spooler warmstart
operation, the spooler supervisor could not open the specified control
file. | | {403_20 TSUPINIT} | During spooler warmstart
operation, the spooler supervisor determined that the specified control
file was inaccessible or unusable. | | {403_21 TSUPINIT} | During spooler startup,
the spooler supervisor detected an invalid file code for the specified
control file. The spooler can warmstart from only control files with
file codes of 124 (C00), 125 (C20), 126 (C20ABA), 127 (D00 and D10),
or 128 (current file code). | | {403_22 TSUPINIT} | During spooler warmstart
operation, the spooler supervisor could not read from or position
within the specified control file. | | {403_23 TSUPINIT} | During spooler warmstart
operation, the spooler supervisor could not write to or position within
the specified control file. |
Effect The spooler supervisor stops. Recovery The recovery for this event message depends on the text string
displayed in the symptom field. Table 100-21 describes the recovery for
each text string displayed in the symptom field. Table 100-21 SPOOLER Message 403 Recovery Procedures | Symptom Field Text String | Recovery |
|---|
| {403_1 TSUPINIT} | Examine the file-system
error. Make changes as required to permit the control file to be written
and positioned. Repeat the coldstart operation. | | {403_2 TSUPINIT} | Examine the file-system
error. Make changes as required to permit the control file to be created.
Repeat the coldstart operation. | | {403_3 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Correct the process environment.
Repeat the startup operation. | | {403_4 TSUPINIT} {403_5 TSUPINIT} | Examine
the file-system error. See Appendix B for file-system error descriptions. Correct
the file attributes or environment. Repeat the startup operation. | | {403_6 TSUPINIT} | Coldstart the spooler or
choose a spooler version that is able to use these version control
files and repeat the warmstart operation. | | {403_7 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Correct the file attributes
or environment. Repeat the startup operation. | | {403_8 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be created. Repeat the coldstart operation. | | {403_9 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be opened. Repeat the coldstart operation. | | {403_10 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be read. Repeat the coldstart operation. | | {403_11 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be written. Repeat the coldstart operation. | | {403_12 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be written and positioned. Repeat the coldstart
operation. | | {403_13 TSUPINIT} | Examine the file-system
error (from FILE_RENAME_). See Appendix B for file-system error descriptions. Determine
if the old control file is still present. If so, clear the condition
affecting the purge operation. If the old control file has been purged,
restore it from a copy. Once the old control file has been verified
to be present, repeat the warmstart operation. If the old control
file cannot be restored, do a coldstart. | | {403_14 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be opened. Repeat the coldstart operation. | | {403_15 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Correct the file name, attributes,
or the environment. Repeat the warmstart operation. | | {403_16 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Correct the file name, attributes,
or the environment. Repeat the warmstart operation. | | {403_17 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be written. Repeat the coldstart operation. | | {403_18 TSUPINIT} | Examine the file-system
error (from FILE_RENAME_). See Appendix B for file-system error descriptions. Determine
if the old control file is still present. If so, clear the condition
affecting the purge operation. If the old control file has been purged,
restore it from a copy. Once the old control file has been verified
to be present, repeat the warmstart operation. If the old control
file cannot be restored, do a coldstart. | | {403_19 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Correct the file name, attributes,
or the environment. Repeat the warmstart operation. | | {403_20 TSUPINIT} | Examine the file-system
error (from FILE_GETINFOBYNAME_). See Appendix B for file-system error descriptions. Clear
the condition restricting access to the control file. Repeat the warmstart
operation. If the condition persists, coldstart the spooler. | | {403_21 TSUPINIT} | Coldstart the spooler
or choose a spooler version that is able to use these version control
files and repeat the warmstart operation. | | {403_22 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be read and positioned. Repeat the warmstart
operation. If the failure persists, coldstart the spooler. | | {403_23 TSUPINIT} | Examine the file-system
error. See Appendix B for file-system error descriptions. Make changes as required to
permit the control file to be written and positioned. If the failure
persists, coldstart the spooler. |
|
| 404 Spooler Supervisor $process_name Unavailable, Event: Internal Error, Cause: cause, Previous state: prev_state, Current
state: cur_state, FS Error: error_code, Base object: object, detail: detail_text, Symptom: symptom | | process_name | identifies the spooler supervisor process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-22 describes each text string displayed in the cause field. | | prev_state | identifies the previous state of the spooler supervisor
process that generated the event. Spooler supervisor process states
are described in Table 100-15. Not
all states may be returned to this field. | | cur_state | identifies the current state of the spooler supervisor
process that generated the event. Spooler supervisor process states
are described in Table 100-15. Not
all states may be returned to this field. | | error_code | identifies a file-system error code. | | object | identifies the object containing the error or the
object associated with the error. | | detail_text | provides additional explanatory information. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of these codes. |
Cause The cause of this event message depends on the text string returned
to the detail field. Table 100-22 describes the cause of each text string displayed
in the symptom field. Table 100-22 SPOOLER Message 404 Causes | Symptom Field Text String | Cause |
|---|
| {404_1 TSUPINIT} | The backup process for
the spooler supervisor failed. | | {404_2 TSUPBKUP} | A system problem occurred
causing takeover to fail. | | {404_3 TSUPBKUP} | A call to PROCESSHANDLE_DECOMPOSE_
failed during an attempt to create the backup process for the spooler
supervisor. | | {404_4 TSUPBKUP} | The spooler supervisor
detected an error in its backup process. | | {404_8 TSUPBKUP} | An incorrect library was
detected during an attempt to create backup. | | {404_12 TSUPJOB} | During new job initialization,
an error occurred while converting a file name. | | {404_13 TSUPPROC} | When the spooler supervisor
attempted to start the indicated collector, it received a file system
error while doing a system procedure call GET_MYNAME_. | | {404_15 TSUPPROC} | When the spooler supervisor
attempted to start the indicated print process, it received a file
system error while doing a system procedure call GET_MYNAME_. | | {404_16 TSUPRECV} | When the spooler supervisor
attempted to add a new user to its user table, it detected an error
while decomposing the user’s process handle. The error from
call to PROCESSHANDLE_DECOMPOSE_ is shown in the error message. | | {404_20 TSUPMEM} | The spooler supervisor
could not allocate an extended memory segment. The error returned
from the call to ALLOCATE_SEGMENT_ is shown in the error message. | | {404_21 TSUPMEM} | The spooler supervisor
could not allocate an extended memory segment. The error returned
from the call to RESIZESEGMENT is shown in the error message. | | {404_22 TSUPPROC} | An illegal message was
sent from a collector to the spooler supervisor. | | {404_23 TSUPRECV} | The spooler supervisor
detected an error while attempting to read the $RECEIVE file. | | {404_24 TSUPLOG} | An attempt was made to
start the spooler with an illegal startup parameter, causing an error
to occur. | | {404_26 TSUPMEM} | The spooler supervisor
could not allocate heap space. The error returned from the call to
SEGMENT_ALLOCATE_ is shown in the error message. | | {404_27 TSUPMEM} | The spooler supervisor
could not define pool space when allocating heap space. The error
returned from the call to POOL_DEFINE_ is shown in the error message. | | {404_28 TSUPMEM} | The spooler supervisor
could not get temporary pool space when calling a MALLOC routine.
The error returned from the call to POOL_GETSPACE_ is shown in the
error message. | | {404_29 TSUPMEM} | The spooler supervisor
detected an error when returning heap space. The error returned from
the call to POOL_PUTSPACE_ is shown in the error message. | | {404-TRAP} | During spooler supervisor operation,
the NonStop Kernal has detailed an unmanaged calculation error or
a serious system environmental condition. |
Effect The spooler supervisor stops and a Tandem Failure Data System
(TFDS) event is generated. Recovery For the 404-TRAP cause, examine the trap information in the
event message to find out what type of trap occurred. For the following
trap types, attempt to clear the environmental block and warmstart
the spooler supervisor: For the 404_assert error error_number, during spooler operation the supervisor detected an internal assert
error from which it could not recover; the spooler supervisor stopped.
To recover, restart the spooler. For all other message 404 types, consult with your service provider
to help resolve the problem. Warmstart the spooler supervisor. If
the failure reoccurs following warmstart, determine if a specific
object is implicated and try to remove this object from the spooler
and reintroduce it after the problem has been solved. If these steps
fail, coldstart the spooler supervisor. |
| 405 Spooler Supervisor $process_name Unvailable, Event: Not using correct spooler library, Cause: cause, Previous state: prev_state, Current state: cur_state, FS Error: error_code, Base object: object, Symptom: symptom | | process_name | identifies the spooler supervisor process generating
the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-23 describes each text string displayed in the cause field. Table 100-23 SPOOLER Message 405 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Incorrect installation | Certain spooler components
must be installed together and must match in version. Startup parameters
must be correct in quantity and value. Validity checks are performed
to assure consistency and compatibility. |
| | prev_state | identifies the previous state of the spooler supervisor
process that generated the event. Spooler supervisor process states
are described in Table 100-15. Not
all states may be returned to this field. | | cur_state | identifies the current state of the spooler supervisor
process that generated the event. Spooler supervisor process states
are described in Table 100-15. Not
all states may be returned to this field. | | error_code | identifies a file-system error code. | | object | identifies the object containing the error or the
object associated with the error. | | symptom | contains a text string that provides a code and a
module name. The code indicates the point in the module where the
error was detected and the module name identifies the module. See
cause and recovery information for the meaning of these codes. |
Cause The cause of this event message depends on the text string returned
to the symptom field. Table 100-24 describes the cause of each
text string displayed in the symptom field. Table 100-24 SPOOLER Message 405 Causes | Symptom Field Text String | Cause |
|---|
| {405_1 TSUPINIT} | During spooler coldstart
operation, the supervisor detected an invalid version identification
for the spooler library. |
Effect The spooler supervisor stops. Recovery The recovery for this event message depends on the text string
displayed in the symptom field. Table 100-25 describes the recovery for
each text string displayed in the symptom field. Table 100-25 SPOOLER Message 405 Recovery Procedures | Symptom Field Text String | Recovery |
|---|
| {405_1 TSUPINIT} | Examine the library versions.
Regenerate the proper library or, in special cases, locally bind to
the proper library. Repeat the coldstart operation. |
|
| 406 Spooler Supervisor $process_name, Event: No available openers, Cause: cause | | process_name | identifies the supervisor process generating the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-26 describes each text string displayed in the cause field. Table 100-26 SPOOLER Message 406 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Spooler limit has been reached | No more openers
are available. |
|
Cause The spooler supervisor reached the maximum number of openers. Effect None Recovery Take action to reduce the number of openers to the spooler supervisor. |
| 407 Spooler Supervisor $process_name, Event: Maximum batch job limit reached, Cause: cause | | process_name | identifies the supervisor process generating the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-27 describes each text string displayed in the cause field. Table 100-27 SPOOLER Message 407 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Maximum batch job limit has been reached | The maximum batch jobs in the spooler has been reached. |
|
Cause The spooler supervisor reached the maximum opens. Effect None Recovery Take action to reduce the number of openers to the spooler supervisor. |
| 408 Spooler Supervisor $process_name Transient Fault, Event: Internal Error, Fault: fault, Error: error | | process_name | identifies the supervisor process generating the event. | | fault | contains a text string that provides information about
the fault that has occurred. Table 100-28 describes each text string displayed in the fault field. Table 100-28 SPOOLER Message 408 Fault Field Text Strings | Fault Field Text String | Meaning |
|---|
| Diagnostic | A programmed internal-error check
has failed. |
| | error | contains a code that indicates the cause of the error.
See cause and recovery information for the meaning of these codes. |
Cause The cause of this event message depends on the code displayed
in the error field. Table 100-29 describes the cause of each code displayed in
the error field. Table 100-29 SPOOLER Message 408 Causes | Error Field Code | Cause |
|---|
| {408_1 TSUPJOB} | While trying to schedule
a job into a device queue, the Spooler Supervisor failed to allocate
a device queue node (system limit). The job is placed on hold. | | {408_2 TSUPBKUP} | A call to GET_SWAP_FNAME_
failed during an attempt to create a backup process. | | {408_3 TSUPBKUP} | A call to FILENAME_DECOMPOSE_
failed during an attempt to create a backup process. | | {408_4 TSUPBKUP} | A call to GET_PROG_FNAME_
failed during an attempt to create a backup process. | | {408_5 TSUPBKUP} | A call to PROCESS_GETINFO_
failed during an attempt to create a backup process. | | {408_6 TSUPBKUP} | A call to FILENAME_DECOMPOSE_
failed during an attempt to create a backup process. | | {408_7 TSUPPROC} | When the spooler supervisor
attempted to start a new job, a file-system error occurred while decomposing
the collector process name. | | {408_8 TSUPPROC} | When the spooler supervisor
attempted to close a new job, a file-system error occurred while decomposing
the collector process name. | | {408_9 TSUPBAT} | The job attempted to add
its location to the location table while it was about to close, but
the table was full. As a result, the job was placed on hold. | | {408_10 TSUPMEM} | The spooler supervisor
detected an invalid segment number for the extended memory, and it
resulted in an internal error. | | {408_11 TSUPBKUP} | The spooler supervisor
backup processor is down. | | {408_12 TSUPBKUP} | A takeover from the primary
process occurred because of processor failure. | | {408_13 TSUPBKUP} | A backup down, CPU failure
occurred when an attempt to create the supervisor backup process failed. | | {408_14 TSUPBKUP} | An error on extended segment
swap file occurred when an attempt to create the supervisor backup
process failed. | | {408_15 TSUPBKUP} | During a call to SEGMENT_ALLOCATE_CHKPT_,
an error occurred while attempting to create the spooler supervisor
backup process. | | {408_16 TSUPBKUP} | During a call to SEGMENT_ALLOCATE_CHKPT_,
an error occurred while attempting to create the spooler supervisor
backup process. | | {408_17 TSUPBKUP} | The spooler supervisor
detected an error in its backup process, backup down, checkpoint error. | | {408_18 TSUPBKUP} | The spooler supervisor
detected an error in its backup process, spooler stopped, primary
process will not stay up. | | {408_19 TSUPBKUP} | The spooler supervisor
detected an error in its backup process, backup Down, new process
error. | | {408_20 TSUPBKUP} | The spooler supervisor
detected an error in its backup process, backup down, checkpoint error. | | {408_21 TSUPBKUP} | The spooler supervisor
detected an error in its backup process, supervisor backup process
does not exist. | | {408_22 TSUPBKUP} | The spooler supervisor
detected an error in its backup process, unable to allocate extended
segment. | | {408_23 TSUPMEM} | The spooler supervisor
detected an invalid internal table number resulting in an internal
error. | | {408_24 TSUPLIB} | A user requested the spooler
supervisor to create a SAVEABEND file which indicates where the file
is located. | | {408_25 TSUPCNFG} | The spooler supervisor
attempted to configure the spooler with a higher job limit than the
current spooler would allow. To receive higher maximum limits, install
Spooler Plus. | | {408_26 TSUPJOB} | The spooler supervisor
could not RESIZE the extended segment. | | {408_27 TSUPJOB} | A supervisor backup process
does not exist occurred while a call to checkpoint a resized segment
was made. | | {408_28 TSUPJOB} | When the spooler supervisor
attempted to send a device control message to a print process, it
found that the device was off line. | | {408_29 TSUPJOB} | While the spooler supervisor
attempted to add a virtual location for a new job to the location
table, it detected that the location table had reached its maximum
configurable number of locations and the job was placed on hold. | | {408_30 TSUPJOB} | The spooler supervisor
attempted to delete a job while the collector was not running. | | {408_31 TSUPCNFG} | The spooler supervisor
attempted to configure the spooler with a higher location limit than
the current spooler would allow. To receive higher maximum limits,
install Spooler Plus. | | {408_32 TSUPCNFG} | The spooler supervisor
attempted to configure the spooler with a higher location limit than
the current spooler would allow. To receive higher maximum limits,
install Spooler Plus. | | {408_33 TSUPCNFG} | The spooler supervisor
attempted to configure the spooler with a higher location limit than
the current spooler would allow. To receive higher maximum limits,
install Spooler Plus. | | {408_34 TSUPLOG} | An illegal Job 0 was detected
at READFE, resulting in an internal error. | | {408_35 TSUPLOG} | An illegal Job 0 was detected
at UPDATEFE, resulting in an internal error. | | {408_36 TSUPLOG} | An illegal Job 0 was detected
at FORMATEFE, resulting in an internal error. | | {408_37 TSUPLOG} | An illegal Job 0 was detected
at DELETEEFE, resulting in an internal error. | | {408_38 TSUPPROC} | The job attempted to add
its location to the location table while it was about to close, but
the table was full. As a result, the job was placed on hold. | | {408_39 TSUPPROC} | The spooler supervisor
killed the collector because of a collector process error. | | {408_40 TSUPPROC} | The spooler collector
stopped. | | {408_41 TSUPPROC} | The spooler supervisor
killed the print process because of a print process error. | | {408_42 TSUPPROC} | The print process stopped. | | {408_43 TSUPPROC} | When the print process
tried to connect to the indicated device, the device was not ready.
This message was passed from the print process to the spooler supervisor. | | {408_44 TSUPPROC} | When the print process
tried to connect to the indicated device, the device was already in
use. This message was passed from the print process to the spooler
supervisor. | | {408_45 TSUPPROC} | When the print process
tried to connect to the indicated device, the device had an interrupt
timeout. This message was passed from the print process to the spooler
supervisor. | | {408_46 TSUPPROC} | When the print process
tried to connect to the indicated device, the device modem had disconnected.
this message was passed from the print process to the spooler supervisor. | | {408_47 TSUPPROC} | When the print process
tried to connect to the indicated device, the device had timed out.
This message was passed from the print process to the spooler supervisor. | | {408_48 TSUPPROC} | When the print process
tried to connect to the indicated device, the device had timed out.
This message was passed from the print process to the spooler supervisor. | | {408_49 TSUPPROC} | The print process detected
the error shown on the device indicated in the error text. | | {408_50 TSUPPROC} | When the print process
tried to connect to the device indicated in the error text, the device
was off line. This message was passed from the print process to the
spooler supervisor. | | {408_51 TSUPPROC} | The spooler supervisor
received a print process message from a process that was know to the
supervisor. | | {408_52 TSUPPROC} | The print process sent
a message to the supervisor regarding a device that was not known
to the supervisor. | | {408_53 TSUPPROC} | The print process sent
a message to the supervisor regarding a device that was not known
to the supervisor. | | {408_54 TSUPPROC} | The print process indicated
reported that the job number ended printing abnormally. | | {408_55 TSUPPROC} | The print process indicated
reported that the job number ended printing abnormally. | | {408_56 TSUPPROC} | The print process indicated
reported that the job number ended printing abnormally. | | {408_57 TSUPPROC} | While attempting to start
the collector, the spooler supervisor received an error when it tried
to do the call to PROCESS_CREATE_. The error returned is shown in
the error text. | | {408_58 TSUPPROC} | While attempting to start
the print process, the spooler supervisor detected an error when it
did a call to CREATE_PROCESS_. The error returned is shown in the
error text. | | {408_59 TSUPPROC} | During the process of
sending a request to a print process, the spooler supervisor detected
that the number of entries in its receive queue (unanswered messages
obtained from the $RECEIVE file) had exceeded the maximum. | | {408_60 TSUPPROC} | During the process of
sending a request to a print process or a collector, the spooler supervisor
detected that the number of entries in its receive queue (unanswered
messages obtained from the $RECEIVE file) had exceeded the maximum. | | {408_61 TSUPPROC} | During the process of
retrieving listopens information from a collector, the spooler supervisor
detected that the number of entries in its receive queue (unanswered
messages obtained from the $RECEIVE file) had exceeded the maximum. | | {408_62 TSUPPROC} | During the process of
retrieving listopens information from a collector, the spooler supervisor
detected that the number of entries in its receive queue (unanswered
messages obtained from the $RECEIVE file) had exceeded the maximum. | | {408_63 TSUPRECV} | After reading a new request
from the $RECEIVE file, the spooler supervisor attempted to add it
to its own receive table but found that the maximum number of entries
had been exceeded. | | {408_64 TSUPRECV} | A system message that
the backup processor went down was received by the spooler supervisor. | | {408_65 TSUPLIB} | Warning: Dev entry already
in time list means a check to see if a device was on line failed.
An attempt was made to put the request to check it again into a time
list, but an entry for that device was already in the list. | | {408_66 TSUPPROC} | Warning: Dev entry already
in time list means a check to see if a device was on line failed.
An attempt was made to put the request to check it again into a time
list, but an entry for that device was already in the list. | | {408_67 TSUPPROC} | Warning: Dev entry already
in time list means a check to see if a device was on line failed.
An attempt was made to put the request to check it again into a time
list, but an entry for that device was already in the list. | | {408_68 TSUPPROC} | Warning: Dev entry already
in time list means a check to see if a device was on line failed.
An attempt was made to put the request to check it again into a time
list, but an entry for that device was already in the list. | | {408_69 TSUPCNFG} | An attempt was made to
configure the spooler with a higher font limit than the current spooler
would allow. To get higher maximum limits, install Spooler Plus. | | {408_70 TSUPCNFG} | An attempt was made to
configure the spooler with a higher font limit than the current spooler
would allow. To get higher maximum limits, install Spooler Plus. | | {408_71 TSUPCNFG} | An attempt was made to
configure the spooler with a higher font limit than the current spooler
would allow. To get higher maximum limits, install Spooler Plus. | | {408_72 TSUPCNFG} | An attempt was made to
configure the spooler with a higher font limit than the current spooler
would allow. To get higher maximum limits, install Spooler Plus. | | {408_73 TSUPBKUP} | During checkpointing,
an invalid parameter passed and the process abended, causing an internal
error. | | {408_74 TSUPINIT} | This event is displayed
whenever the Spooler is started with different primary and backup
CPUs. | | {408_75 TSUPINIT} | This event is displayed
whenever the Spooler is started with the same primary and backup CPUs. | | {408_76 TSUPPROC} | Write to the collector
process is not possible as the collector is in error state. | | {408_77 TSUPPROC} | Collector process cannot
be started. | | {408_78 TSUPPROC} | Write to print process
is not possible as the print process is in error state. | | {408_79 TSUPPROC} | Print process cannot be
started. | | {408_80 TSUPPROC} | The Spooler supervisor
attempted to stop the print process as the operation on the supervisor
timed out. | | {408_81 TSUPPROC} | The Spooler supervisor
attempted to stop the print process as a file-system 26 error is encountered. | | {408_82 TSUPPROC} | The Spooler supervisor
attempted to stop the collector process as the operation on the supervisor
timed out. | | {408_83 TSUPPROC} | The Spooler supervisor
attempted to stop the collector process as a file-system 26 error
is encountered. | | {408_84 TSUPPROC} | The Spooler supervisor
attempted to stop the collector process as the collector process timed
out. | | (408_85 TSUPPROC} | The Spooler supervisor
attempted to stop the print process as the print process timed out. | | {408_86 TSUPRECV} | Collector process is stopped. | | {408_87 TSUPRECV} | The print process stopped. | | {408_88 TSUPPROC} | An attempt made to stop
the collector process returned an error. | | {408_89 TSUPPROC} | An attempt made to stop
the print process returned an error. |
Effect The spooler supervisor stops. Recovery Consult your service provider to help resolve the problem. Warmstart
the spooler. If the failure reoccurs following the warmstart, determine
if a specified object (for example, a particular job) is implicated
and attempt to remove this object from the spooler and possibly reintroduce
it after the problem has been avoided. If these steps fail, coldstart
the spooler. |
| 409 Spooler Supervisor $process_name Maximum exceeded, Event: Maximum job limit reached, Cause: cause | | process_name | identifies the supervisor process generating the event. | | cause | contains a text string that provides information about
why the event was generated. Table 100-30 describes each text string displayed in the cause field. Table 100-30 SPOOLER Message 407 Cause Field Text Strings | Cause Field Text String | Meaning |
|---|
| Spooler limit has been reached | The maximum
job limit has been reached. |
|
Cause The maximum jobs allowed in the spooler has been reached. Effect None Recovery Take action to reduce the number of jobs in the spooler. |
| 412 Spooler Supervisor $process_name Usage Threshold, Event: Spooler batch job capacity, Current usage
level: level, Usage unit: unit, Current time (UTC): time, Configured high value: high_value,
Configured low value: low_value | | process_name | identifies the spooler supervisor process generating
the event. | | level | indicates the number of batch jobs in the system. | | unit | identifies the type of unit used to measure the event.
Type 1 is a percentage unit and type 19 is a count. This event message
always returns type 2 (count). | | time | indicates the time that the event occurred. | | high_value | identifies the configured high-threshold value for
the type of event that has occurred. | | low_value | identifies the configured low-threshold value for
the type of event that has occurred. |
Cause This event occurs when the number of batch jobs exceeds the
configured high-threshold value (high_value), or when the number of batch jobs falls below the configured low-threshold
value (low_value) after the high-threshold
value has been exceeded. Effect None Recovery Delete unneeded batch jobs or temporarily remove them from the
spooler as spooler job files, if necessary. |
| 413 Spooler Supervisor $process_name Usage Threshold, Event: Spooler job capacity, Current usage level: level, Usage unit: unit,
Current time (UTC): time, Configured high
value: high_value, Configured low value: low_value | | process_name | identifies the spooler supervisor process generating
the event. | | level | indicates the current number of jobs in the system. | | unit | identifies the type of unit used to measure the event.
Type 1 is a percentage unit and type 19 is a count. This event message
always returns type 2 (count). | | time | indicates the time that the event occurred. | | high_value | identifies the configured high-threshold value for
the type of event that has occurred. | | low_value | identifies the configured low-threshold value for
the type of event that has occurred. |
Cause This event occurs when the number of jobs exceeds the configured
high-threshold value (high_value), or when
the number of jobs falls below the configured low-threshold value
(low_value) after the high-threshold value
has been exceeded. Effect None Recovery Delete unneeded jobs or temporarily remove them from the spooler
as spooler job files, if necessary. |
| 414 Spooler Supervisor $process_name Usage Threshold, Event: Spooler location capacity, Current usage
level: level, Usage unit: unit, Current time (UTC): time, Configured high value: high_value, Configured
low value: low_value | | process_name | identifies the spooler supervisor process generating
the event. | | level | indicates the number of locations in the system. | | unit | identifies the type of unit used to measure the event.
Type 1 is a percentage unit and type 19 is a count. This event message
always returns type 2 (count). | | time | indicates the time that the event occurred. | | high_value | identifies the configured high-threshold value for
the type of event that has occurred. | | low_value | identifies the configured low-threshold value for
the type of event that has occurred. |
Cause This event occurs when the number of locations in the system
exceeds the configured high-threshold value (high_value), or when the number of locations in the system falls below the
configured low-threshold value (low_value) after the high‑threshold value has been exceeded. Effect None Recovery Delete unneeded jobs occupying unique virtual locations, if
necessary. |
| 415 Spooler supervisor $process_name Threshold, Event: Spooler queue node threshold, Current usage level:level Usage unit: unit,
Current time (UTC): time, Configured high
value: high_value, Configured low value: low_value, Configured maximum value: max_value | | process_name | identifies the spooler supervisor process generating
the event. | | level | indicates the current number of queue nodes in the
system. | | unit | identifies the type of unit used to measure the event.
Type 1 is a percentage unit and type 19 is a count. This event message
always returns type 2 (count). | | time | indicates the time when the event occurred. | | high_value | identifies the configured high-threshold value for
the type of event that has occurred. | | low_value | identifies the configured low-threshold value for
the type of event that has occurred. | | max_value | identifies the maximum threshold value for the type
of even that has occurred. |
Cause This event occurs when the number of queue nodes exceeds the
configured high-threshold value (high-value), or when the number of queue nodes falls below the configured low-threshold
value (low-value) after the high-threshold
value has been exceeded. Effect None Recovery If necessary, delete the unneeded jobs, or temporarily remove
them, from the spooler as spooler job files. |
| 416 Spooler Supervisor $process_name Usage Threshold, Event: Spooler opener capacity, Current usage
level: level, Usage unit: unit, Current time (UTC): time, Configured high value: high_value, Configured
low value: low_value | | process_name | identifies the spooler supervisor process generating
the event. | | level | indicates the number of opens to the identified spooler
supervisor (process_name). | | unit | identifies the type of unit used to measure the event.
Type 1 is a percentage unit and type 19 is a count. This event message
always returns type 2 (count). | | time | indicates the time that the event occurred. | | high_value | identifies the configured high-threshold value for
the type of event that has occurred. | | low_value | identifies the configured low-threshold value for
the type of event that has occurred. |
Cause This event occurs when the number of openers to the identified
spooler supervisor exceeds the configured high-threshold value (high_value), or when the number of openers to the identified
spooler supervisor falls below the configured low‑threshold value
(low_value) after the high-threshold value
has been exceeded. Effect None Recovery Determine the number of PERUSE or SPOOLCOM users and stop those
that are idle or are not being used. If applications (including TACL
macros) are using the spooler application program interfaces (APIs),
check these processes and stop those that are idle or are not operating
correctly. |
|