Operator Messages Manual
Chapter 58 NETBATCH Messages
The messages in this chapter are sent by the NetBatch subsystem.
The subsystem ID displayed by these messages includes NETBATCH as
the subsystem name. | | | |  | NOTE: Negative-numbered messages are common to most subsystems. If
you receive a negative-numbered message, see Chapter 15. | | | | |
| 100 SCHEDULER \node.$process-name STARTED | | \node.$process-name | specifies the node and process name of the scheduler.
|
Cause A START SCHEDULER command started the scheduler. Effect The scheduler is now running as a NonStop process-pair server. Recovery Informational message only; no corrective action is needed.
|
| 101 SCHEDULER \node.$process-name was stopped by command, log log-file-name, database schd-database-subvol | | \node.$process-name | specifies the node and process name of the scheduler.
| | command | specifies which of the commands ABORT SCHEDULER and
SHUTDOWN SCHEDULER shut down the scheduler. | | log-file-name | specifies the name of the scheduler’s log file.
| | schd-database-subvol | specifies the location of the scheduler’s database.
|
Cause An ABORT SCHEDULER or SHUTDOWN SCHEDULER command shut down the
scheduler. Effect The scheduler is no longer running. Recovery Informational message only; no corrective action is needed.
|
| 102 JOB job-name (job-number) started, program program-file-name, user ID group-ID user-ID | | job-name | specifies the name of the job. | | job-number | specifies the number of the job. | | program-file-name | specifies the program file name of the job’s
executor-program process. | | group-ID user-ID | specifies the user ID of the job owner. |
Cause The scheduler started the initial process (the executor program)
of the job. Effect The job’s executor program started successfully. Recovery Informational message only; no corrective action is needed.
|
| 200 EXECUTOR executor-name is down | | executor-name | specifies the name of the executor. |
Cause The executor’s processor went down. Effect The executor is no longer available for use by jobs. A job that
abended because the executor’s processor went down will make
the scheduler generate operator message 203. For recovery action,
see event message 203. Recovery Alter the executor’s CPU attribute to specify an available
CPU when both these conditions exist: The executor’s classes are unique to the executor.
You want the scheduler to continue selecting jobs
from the executor’s classes.
You can reassign the executor to its original CPU when the CPU
becomes available. |
| 201 EXECUTOR executor-name is now up | | executor-name | specifies the name of the executor. |
Cause The executor’s processor became available after being
down. Effect The executor is now available for use by jobs. Recovery Reassign the executor to its original CPU if you altered the
executor’s CPU attribute when the CPU went down. |
| 202 JOB job-name (job-number) has stopped with completion-text. Job started at time, CPU usage number microsecs, program program-file-name, user ID group-ID user-ID. | | job-name | specifies the name of the job. | | job-number | specifies the number of the job. | | completion-text | indicates how the job terminated. completion-text has one of these values: | | time | specifies when the scheduler started the job’s
executor-program process. | | number | specifies the total processor time taken by all processes
of the job. | | program-file-name | specifies the program file name of the job’s
executor-program process. | | group-ID user-ID | specifies the user ID of the job owner. |
Cause The job stopped without error. Effect None. Recovery Informational message only; no corrective action is needed.
|
| 203 JOB job-name (job-number) has ABORTED with completion-text. Job started at time, CPU usage number microsecs, program program-file-name, user ID group-ID user-ID. | | job-name | specifies the name of the job. | | job-number | specifies the number of the job. | | completion-text | indicates how the job terminated. completion-text
has one of these values: Table 58-1 completion-text Values for NETBATCH
Message 203 | completion-text Value | Description |
|---|
| -1 TRAP detected | Trap detected. Completion
code -1. | | Job requests restart | The process sent a
restart request to the scheduler. Completion code 7. | | Normal termination | Normal, voluntary termination
with no errors. Completion code 0. | | Premature termination with fatal errors | Abnormal, voluntary, but premature termination with fatal errors
or diagnostics. Completion code 3. | | Process calls abend | The process called ABEND
or PROCESS_STOP_. Completion code 5. | | Process never started | The process did not
start. Completion code 4. | | Process terminated; Guardian unable to pass CC | The process terminated itself, but the operating system could
not pass completion code and termination information to that process
because of a resource problem. Completion code -2. | | Process terminated; Invalid params in STOP/ABEND | The process terminated itself, but passed invalid parameters
to ABEND, STOP, or PROCESS_DELETE_. Completion code -3. | | STOP/ABEND issued by an external process | An external, authorized process issued an ABEND, STOP, or PROCESS_STOP_
to delete the process. Completion code 6. | | Terminated with fatal errors | Abnormal, voluntary
termination with fatal errors or diagnostics. Completion code 2.
| | Terminated with warning | Normal, voluntary
termination with warning diagnostics. Completion code 1. |
| | time | specifies when the scheduler started the job’s
executor-program process. | | number | specifies the total processor time taken by all processes
of the job. | | program-file-name | specifies the program file name of the job’s
executor-program process. | | group-ID user-ID | specifies the user ID of the job owner. |
Cause One of these errors occurred: The job’s executor-program process did one of: Abended by calling the system procedure PROCESS_STOP_
(with the ABEND option specified) or ABEND. Stopped with completion code -3, -2, -1, 2, 3, 4,
5, 6, or 7.
The scheduler stopped the job and all its processes
because the job had the attribute STOP-ON-ABEND ON and did one of: Terminated because of processor failure. Abended with any completion code. Stopped with completion code -3, -2, -1, 1, 2, 3,
4, 5, 6, or 7.
A process external to the scheduler stopped the job’s
executor-program process.
Effect The job terminated. Recovery Perform whatever action the job owner requests. |
| 204 JOB job-name (job-number) ran longer than limit minutes Program program-file-name, user
ID group-ID user-ID | | job-name | specifies the name of the job. | | job-number | specifies the number of the job. | | limit | specifies the job’s execution-time limit as
specified by the LIMIT attribute. | | program-file-name | specifies the program file name of the job’s
executor-program process. | | group-ID user-ID | specifies the user ID of the job owner. |
Cause The job exceeded its execution-time limit as specified by the
LIMIT attribute, but continued to run. Effect The job ran longer than expected. Recovery Perform whatever action the job owner requests. |
| 301 JOB job-name (job-number) failed because of error-condition. Program program-file-name, user ID group-ID user-ID. | | job-name | specifies the name of the job. | | job-number | specifies the number of the job. | | error-condition | indicates why the scheduler could not start the job’s
executor-program process. error-condition has one of these values: | | program-file-name | specifies the program file name of the job’s
executor-program process. | | group-ID user-ID | specifies the user ID of the job owner. |
Cause The scheduler failed to start the job’s executor-program
process. Effect The job failed. Recovery Correct the cause of the error, then perform whatever actions
the job owner requests. |
| 500 SCHEDULER \node.$process-name has abended because of error-condition. Log log-file-name, database schd-database-subvol. Consult your system manager
or Tandem representative. | | \node.$process-name | specifies the node and process name of the scheduler.
| | error-condition | indicates why the scheduler abended. | | log-file-name | specifies the name of the scheduler’s log file.
| | schd-database-subvol | specifies the location of the scheduler’s database.
|
Cause The scheduler called the ABEND or PROCESS_STOP_ (with ABEND
option) system procedure because of a system resource or scheduler
problem. Effect The scheduler process terminated. Recovery When the error indicates a system resource problem (for example,
disk full), correct the cause of the problem, then warm start the
scheduler. If the error indicates a scheduler problem: Check the scheduler’s log file for diagnostic messages.
Save the scheduler’s saveabend, database, and program
files. Warm start the scheduler. Contact your service provider and ask the representative
to file a Genesis case. Provide the representative with a copy of
the scheduler’s log, and the saveabend, database, and program
files.
|
| 501 Logon failure occurred with status = status-number. | | status-number | specifies the status number returned by USER_AUTHENTICATE_. |
Cause The scheduler could not log on to the log file owner's user
ID. Effect The logon status returned and the scheduler process ultimately
abends. Recovery The status indicates the type of error occurred. For details
about the error, see USER_AUTHENTICATE_ in the Guardian
Procedure Calls Reference Manual and take corrective action
accordingly. |
| 502 Logfile log-file-name could not be created due to file system error err-num | | log-file-name | is the name of the scheduler’s log file. | | err-num | is the file system error that occurred while creating
the scheduler log file. |
Cause The scheduler could not create the scheduler log file. Effect A file system error is returned and the scheduler process ultimately
abends. Recovery The file system error indicates why the log file could not
be created. For details, see the Guardian Procedure Calls
Reference Manual and take corrective action accordingly. |
|