|
|
|
|
This section lists the exit codes used by SNAP-IX RJE programs. When a SNAP-IX RJE program operates normally and finishes successfully, it returns an exit code value of 0 (zero). If the program ends because of an error, it returns a nonzero exit code. If you run any of these programs from a shell script, the script can test the exit code to determine the cause of the error and take appropriate action.
Some of the errors in the following list are marked 'Internal error.' This indicates an internal error in SNAP-IX that should not occur during normal operation. If one of these errors occurs, report it to your SNAP-IX support personnel.
Memory allocation failure-a malloc operating system call failed.
A putmsg operating system call failed.
A fork operating system call failed.
Could not create a pipe to another process-a pipe operating system call failed. Internal error.
An exec operating system call failed.
SNAP-IX could not open a file-an fopen operating system call failed.
An access operating system call failed.
A write operating system call failed.
No parameters or options were specified on the command line.
An invalid option was specified on the command line.
An option specified on the command line was not followed by the appropriate parameter.
An option specified on the command line was followed by an invalid parameter.
Too many parameters or options were specified on the command line.
An invalid program name was specified when starting or stopping a service from the command line. This implies a problem with one of the SNAP-IX executable files; contact support services.
A parameter specified on the command line was not followed by the appropriate option.
An invalid combination of options was specified on the command line.
An error was detected in the configuration file. Check the error log file for more information.
The control daemon has not been started, so other components cannot be started.
The component you were attempting to start has already been started.
The component you were attempting to stop has not been started.
The requested action cannot be performed because the SNA software is about to terminate.
The requested action cannot be performed because the control daemon has been stopped.
SNAP-IX timed out waiting for a message when attempting to start or stop a service.
SNAP-IX received an unexpected message when attempting to start or stop a service.
SNAP-IX failed to contact the control daemon when attempting to start or stop a service.
The primary user name or group name configured for an RJE workstation was not a valid name on the Solaris system computer.
SNAP-IX could not build the directory structure for an RJE workstation.
RJE internal error.
RJE internal error.
The output directory configured for an RJE printer or punch was not a valid directory on the Solaris system computer.
SNAP-IX could not access the spool directory for the RJE workstation.
SNAP-IX could not access the spool status file for the RJE workstation.
SNAP-IX could not open the RJE code conversion table file.
The RJE workstation has been stopped, either because the snarjestop command was issued or because a time-out was specified when starting the workstation.
The RJE console program received a
The screen size in terminfo is too small to run the RJE console program; it must be at least 80 columns wide.
SNAP-IX could not open the RJE console directory for an RJE workstation. This is probably because the RJE workstation (or the snajobsub command) has not yet been run, and so the workstation's directory structure has not yet been built.
The job specified on the command could not be canceled because it was not in WAITING state.
The job specified on the command could not be canceled because it was not submitted by this user.
The job specified on the command could not be canceled because the RJE workstation was in the process of updating its status. Retry the command.
The job specified on the command did not exist.
The RJE workstation name specified was invalid.
No RJE workstation name was specified.
The RJE job could not be submitted because the spool for this workstation is already full.
The RJE workstation cannot start because either the user name bin or the group name sna is not defined on the Solaris system computer.
The RJE workstation failed to create the data file for a submitted job. Retry the submission; if it continues to fail, contact support services.
The RJE workstation failed to create the job file for a submitted job. Retry the submission; if it continues to fail, contact support services.
The RJE workstation could not write to the data file for a submitted job. This may be because the disk is full, or because a disk error has occurred.
An invalid embedded command was found in the submitted RJE job file.
The submitted RJE job file contained more than five levels of included files.
An invalid option was specified to the snarjestat program.
The supplied RJE host command was too long. Check the command syntax and retry.
An error occurred in reading the RJE console log file.
There are no active LUs available for use by the RJE workstation.
A specified directory path was too long.
SNAP-IX could not access the directory used to hold temporary files for an RJE workstation. Check that the directory defined in the workstation style file exists, and that the primary user and group of the workstation have read and write access to it.
The path of the temporary directory, specified in the RJE workstation style file, is too long.
An RJE program could not establish contact with the node. Check that the node is running.
SNAP-IX attempted to restart the workstation after a node failure (or after the SNA software was stopped and restarted), but the attempt failed. Check the log files for more information.
An RJE command was issued on the wrong computer. It must be issued on the computer where the RJE workstation is defined.
SNAP-IX could not create a temporary file for submitting an RJE job. Check that the directory defined in the workstation style file exists, and that the primary user and group of the workstation have read and write access to it.
RJE internal error.
RJE internal error.
RJE internal error.
RJE internal error.
|
|
|
 |
|