HP 3000 Manuals HP 3000 Manuals
SNA NRJE Error Messages (continued)
---------------------------------------------------------------------------------------
613 MESSAGE UNABLE TO OPEN $STDIN. (SEV=613)
CAUSE
ACTION
---------------------------------------------------------------------------------------
614 MESSAGE UNABLE TO OPEN $STDLIST. (SEV=614)
CAUSE
ACTION
---------------------------------------------------------------------------------------
615 MESSAGE SPOOL FILE CLOSE ERROR. DEV=!, SP STATUS=!.
(SEV=615)
CAUSE
ACTION
---------------------------------------------------------------------------------------
616 MESSAGE SPOOL FILE PURGE ERROR. DEV=!, SP STATUS=!.
(SEV=616)
CAUSE
ACTION
---------------------------------------------------------------------------------------
617 MESSAGE SPOOL FILE READ ERROR. DEV=!, SP STATUS=!.
(SEV=617)
CAUSE
ACTION
---------------------------------------------------------------------------------------
618 MESSAGE MAXIMUM ALLOWABLE CLASSES, 100, EXCEEDED.
(NRJEOUT=618)
CAUSE Too many device classes have been indicated in the
Info parameter of a RUN NRJEOUT command.
ACTION Reduce the number of device classes indicated in
the Info parameter of the RUN NRJEOUT command.
Separate jobs or sessions may be suitable.
---------------------------------------------------------------------------------------
619 MESSAGE MAXIMUM ALLOWABLE LDEVS, 100, EXCEEDED.
(NRJEOUT=619)
CAUSE Too many logical device numbers have been indicated
in the Info parameter of a RUN NRJEOUT command.
ACTION Reduce the number of logical device numbers
indicated in the Info parameter of the RUN NRJEOUT
command. Separate jobs or sessions may be
suitable.
---------------------------------------------------------------------------------------
620 MESSAGE WARNING: MAXIMUM CHAIN, 100, REACHED. (NRJEOUT=620)
CAUSE There are too many spool files in one chain.
ACTION Alter the host job so that fewer data sets are
generated.
---------------------------------------------------------------------------------------
622 MESSAGE NRJEOUT STACK DESTROYED BY USER PROCEDURE.
(NRJEOUT=622)
CAUSE NRJEOutData, supplied by a user, destroyed the
integrity of data, DB through Q, in the NRJEOUT
routine.
ACTION Check the indexing range of operations that do
storage.
---------------------------------------------------------------------------------------
623 MESSAGE FAILED TO FIND PROGRAM FILE NAME. (NRJEOUT=623)
CAUSE
ACTION
---------------------------------------------------------------------------------------
624 MESSAGE FAILED TO FIND PROGRAM FILE NAME. (NRJEOUT=624)
CAUSE
ACTION
---------------------------------------------------------------------------------------
625 MESSAGE NRJEOUT NOT RUN FROM THE GROUP NRJE.SYS.
(NRJEOUT=625)
CAUSE
ACTION
---------------------------------------------------------------------------------------
701 MESSAGE COMMA IS EXPECTED. (CI=701)
CAUSE Parsing error.
ACTION Re-enter data.
---------------------------------------------------------------------------------------
702 MESSAGE COMMA OR CARRIAGE RETURN IS EXPECTED. (CI=702)
CAUSE Parsing error.
ACTION Re-enter data.
---------------------------------------------------------------------------------------
703 MESSAGE KEYWORD CAN BE SPECIFIED ONLY IN THE DISPLAY
COMMAND. (CI=703)
CAUSE A keyword was used out of context.
ACTION Re-enter data without the keyword.
---------------------------------------------------------------------------------------
704 MESSAGE DUPLICATE KEYWORDS DETECTED. (CI=704)
CAUSE A keyword was used more than once where prohibited.
ACTION Re-enter data and do not repeat the keyword.
---------------------------------------------------------------------------------------
705 MESSAGE ENTER WELCOME MESSAGE ( HIT CARRIAGE RETURN TO
TERMINATE ). (CI=705)
CAUSE This is an information message for an NRJE manager
entering a welcome message.
ACTION Enter welcome message data lines followed by a
[RETURN]. Enter a [RETURN] immediately after a
prompt to terminate the welcome message.
---------------------------------------------------------------------------------------
706 MESSAGE EQUAL SIGN EXPECTED AFTER A KEYWORD. (CI=706)
CAUSE A data entry error has occurred. An equal sign
following a keyword has been omitted.
ACTION Scan the data for a keyword that requires an equal
sign and a parameter. Re-enter the information.
---------------------------------------------------------------------------------------
707 MESSAGE INPUT ERROR. (CI=707)
CAUSE An error has occurred in reading from $STDIN.
ACTION Re-enter the NRJE subsystem and then re-enter the
data. If this occurs again, contact your HP
representative for assistance.
---------------------------------------------------------------------------------------
708 MESSAGE INVALID CHAIN SIZE. (CI=708)
CAUSE The chain size parameter value is out of range.
ACTION Correct the chain size parameter value and re-
enter data.
---------------------------------------------------------------------------------------
709 MESSAGE INVALID PRIORITY. (CI=709)
CAUSE The priority value is out of range.
ACTION Correct the priority value and re-enter data.
---------------------------------------------------------------------------------------
710 MESSAGE INVALID JOB NAME, JOB NUMBER OR USER.ACCOUNT.
(CI=710)
CAUSE An incorrect job name, job number or
UserName.AcctName was entered.
ACTION Job names must begin with a letter and be eight or
fewer alphanumeric characters long. Job numbers
are five digit numeric strings. A UserName and
AcctName each must begin with a letter and be eight
or fewer alphanumeric characters long; a period
must separate the two.
---------------------------------------------------------------------------------------
711 MESSAGE INVALID JOB NAME. (CI=711)
CAUSE An incorrect job name was entered.
ACTION A job name must begin with a letter and be eight or
fewer alphanumeric characters long. Correct the
information and re- enter the data.
---------------------------------------------------------------------------------------
712 MESSAGE INVALID JOB NUMBER. (CI=712)
CAUSE An incorrect job number was entered.
ACTION A job number is a string of five or fewer numbers.
Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
713 MESSAGE NO SUCH KEYWORD. (CI=713)
CAUSE An unknown keyword was entered.
ACTION Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
714 MESSAGE LENGTH OF THE LU NAME IS OUT OF RANGE. (CI=714)
CAUSE An invalid LU name was entered.
ACTION An LU name must begin with a letter and may be
eight or fewer alphanumeric characters long.
Correct the information and re- enter the data.
---------------------------------------------------------------------------------------
715 MESSAGE NEW PRIORITY MUST BE BETWEEN 0 AND 14. (CI=715)
CAUSE An invalid new priority value was entered.
ACTION A priority must be between 0 and 14. Correct the
information and re-enter the data.
---------------------------------------------------------------------------------------
716 MESSAGE INVALID USER.ACCOUNT. (CI=716)
CAUSE An incorrect UserName.AcctName was entered.
ACTION Verify that the UserName and AcctName exist. A
UserName and AcctName must each begin with a letter
and may be eight or fewer alphanumeric characters
long. One must be separated from the other by a
period.
---------------------------------------------------------------------------------------
717 MESSAGE INVALID WORKSTATION ID. (CI=717)
CAUSE An invalid workstation identification was entered.
ACTION Verify that the workstation identification exists.
A workstation must begin with a letter and may be
eight or fewer alphanumeric characters long.
Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
718 MESSAGE LENGTH OF THE WORKSTATION ID IS OUT OF RANGE.
(CI=718)
CAUSE The workstation identification contains too many,
or too few characters.
ACTION A workstation identification must begin with a
letter and may be eight or fewer alphanumeric
characters long. Correct the information and
re-enter the data.
---------------------------------------------------------------------------------------
719 MESSAGE NEW PRIORITY IS EXPECTED. (CI=719)
CAUSE The new priority value was omitted.
ACTION Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
720 MESSAGE NO PARAMETER IS EXPECTED. (CI=720)
CAUSE A superfluous parameter was entered.
ACTION Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
721 MESSAGE NO SUCH COMMAND. (CI=721)
CAUSE An unknown command was entered.
ACTION Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
722 MESSAGE NO SUCH COMMAND OR PARAMETER. (CI=722)
CAUSE An unknown command or parameter was entered.
ACTION Correct the command or parameter and re-enter the
data.
---------------------------------------------------------------------------------------
723 MESSAGE KEYWORD VALID ONLY IN SOME OF THE OPERATOR
COMMANDS. (CI=723)
CAUSE A keyword has been entered and is not valid for the
current command.
ACTION Refer to NRJE manual for command syntax and
reenter.
---------------------------------------------------------------------------------------
724 MESSAGE UNABLE TO PARSE THE PARAMETER LIST. (CI=724)
CAUSE A syntax error has occurred in the paramter list.
ACTION Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
725 MESSAGE SEMICOLON IS EXPECTED. (CI=725)
CAUSE A semicolon was omitted.
ACTION Correct the information and re-enter.
---------------------------------------------------------------------------------------
726 MESSAGE KEYWORD CAN BE SPECIFIED ONLY IN THE STARTWS
COMMAND. (CI=726)
CAUSE A keyword was used incorrectly.
ACTION Omit the keyword from the command and re-enter the
data.
---------------------------------------------------------------------------------------
727 MESSAGE UNABLE TO OPEN $STDINX. (CI=727)
CAUSE The $STDINX input file could not be opened.
ACTION Another routine may be using $STDINX. Wait and then
try to open again.
---------------------------------------------------------------------------------------
728 MESSAGE UNABLE TO OPEN $STDLIST. (CI=728)
CAUSE The $STDLIST output file could not be opened.
ACTION Another routine may be using $STDLIST. Wait and
then try to open again.
---------------------------------------------------------------------------------------
729 MESSAGE KEYWORD CAN BE SPECIFIED ONLY IN THE SUBMIT
COMMAND. (CI=729)
CAUSE The keyword use is limited to the SUBMIT command.
ACTION Delete the keyword from this command and re-enter
the data.
---------------------------------------------------------------------------------------
730 MESSAGE WARNING: ATTEMPT TO SWITCH TO THE CURRENT
WORKSTATION. (CI=730)
CAUSE The current workstation and the new workstation are
identical.
ACTION Switching workstation is superfluous.
---------------------------------------------------------------------------------------
731 MESSAGE MORE PARAMETERS ARE EXPECTED. (CI=731)
CAUSE There are too few parameters.
ACTION Check the paramter list, add to it, and re-enter
the data.
---------------------------------------------------------------------------------------
732 MESSAGE WARNING: EXTRA PARAMETERS ARE DETECTED AND IGNORED.
(CI=732)
CAUSE There are too many parameters.
ACTION No action is required. If this error message was
printed because of prestored input, delete the
extra parameters to prevent this message from being
printed again.
---------------------------------------------------------------------------------------
733 MESSAGE UNABLE TO PARSE THE COMMAND. (CI=733)
CAUSE
ACTION
---------------------------------------------------------------------------------------
734 MESSAGE THE CONSOLE MUST BE OPENED PRIOR TO USING THIS
COMMAND. (CI=734)
CAUSE An attempt was made to RELEASE the console when it
was not open.
ACTION Issue a CONSOLE command, or call NRJEConsole, then
enter a host console command or call NRJESendCmd.
---------------------------------------------------------------------------------------
735 MESSAGE WORKSTATION ID IS EXPECTED. (CI=735)
CAUSE A workstation identification was omitted from this
command and there is no default workstation. The
NRJE subsystem was entered without specifying a
workstation identification.
ACTION Re-enter this command including a workstation
identification parameter. Or enter an NRJE command
with a workstation identification parameter to
establish a default workstation, and then enter
this command.
---------------------------------------------------------------------------------------
736 MESSAGE UNABLE TO READ WELCOME MESSAGE INPUT. (CI=736)
CAUSE NRJE command interpreter unable to read input
welcome messages from the user. A file system
error should follow to clarify the situation.
ACTION Investigate the file system error message and if
possible reenter.
---------------------------------------------------------------------------------------
737 MESSAGE END OF INPUT FILE DETECTED, SUBSYSTEM IS
TERMINATING... (CI=737)
CAUSE NRJE command interpreter received an end of file
condition from MPE file system when attempting to
read user input.
ACTION
---------------------------------------------------------------------------------------
738 MESSAGE UNDEFINED MPE COMMAND. (CI=738)
CAUSE An undefined MPE command was entered from the NRJE
subsystem.
ACTION Correct the MPE command and re-enter the data.
---------------------------------------------------------------------------------------
739 MESSAGE UNABLE TO EXECUTE MPE COMMAND. MPE ERROR # !.
(CI=739)
CAUSE An MPE command that was entered from the NRJE
subsystem could not be executed. The meaning of
MPE error number ! can be found in System
Operation and Resource Management Reference Manual.
The command to be executed may be limited to
non-break mode.
ACTION In order to execute the MPE command, EXIT from
NRJE, execute the MPE command, and then re-enter
NRJE.
---------------------------------------------------------------------------------------
740 MESSAGE MAXIMUM OF 5 LU NAMES CAN BE ENTERED. (CI=740)
CAUSE There are more than five LU name parameters in the
command.
ACTION Reduce the number of LU names to five, or less, and
re- enter the command.
---------------------------------------------------------------------------------------
741 MESSAGE LENGTH OF THE INFILE NAME IS OUT OF RANGE. (CI=741)
CAUSE An InFile reference is too long.
ACTION An InFile reference can be a fully qualified file
name, or * followed by a formal designator
reference to a FILE command. All parts of a fully
qualified file name, and a formal designator, must
begin with a letter and are eight or fewer
alphanumeric characters long.
---------------------------------------------------------------------------------------
742 MESSAGE DUPLICATE INFILE OPTION IS DETECTED. (CI=742)
CAUSE An InFile reference was followed by a (C,C) or
(T,T).
ACTION Correct the command and re-enter it.
---------------------------------------------------------------------------------------
743 MESSAGE EXPECTED A RIGHT PARENTHESIS AFTER THE INFILE
OPTIONS. (CI=743)
CAUSE A right parenthesis was omitted.
ACTION Correct the command and re-enter it.
---------------------------------------------------------------------------------------
744 MESSAGE EXTRANEOUS TOKEN AFTER THE INFILE OPTION IS
DETECTED. (CI=744)
CAUSE A token that is not a comma, semicolon, or carriage
return is detected after an infile option.
ACTION Refer to NRJE manual and re-enter.
---------------------------------------------------------------------------------------
745 MESSAGE MAXIMUM OF 5 INFILES CAN BE ENTERED. (CI=745)
CAUSE Too many infiles have been specified.
ACTION If the SUBMIT command is for more than one job,
divide the task into several SUBMIT commands. If
the SUBMIT command is for one job, consolidate the
files as follows: (1) append several files
together and SUBMIT again, and (2) write a routine
using the NRJESubmit intrinsic.
---------------------------------------------------------------------------------------
746 MESSAGE SEMICOLON OR CARRIAGE RETURN IS EXPECTED. (CI=746)
CAUSE A semicolon or carriage return was omitted.
ACTION Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
747 MESSAGE INFILE OPTION IS INVALID. (CI=747)
CAUSE An invalid infile option was specified.
ACTION Correct the information and re-enter the data.
---------------------------------------------------------------------------------------
748 MESSAGE NO WORKSTATION IS SELECTED. (CI=748)
CAUSE No workstation identification has been specified.
ACTION Enter an NRJE command with a workstation
identification to specify a default workstation, or
use a workstation identification with the commands
that require it.
---------------------------------------------------------------------------------------
751 MESSAGE UNABLE TO EXECUTE RUN COMMAND. CREATEPROCESS ERROR
# !. (CI=751)
CAUSE A RUN command has been issued within the CI but
failed.
ACTION Check and make sure the program does exist.
---------------------------------------------------------------------------------------
752 MESSAGE KEYWORD VALID ONLY IN THE SUBMIT OR DISPLAY
COMMAND. (CI=752)
CAUSE A keyword has been entered out of context.
ACTION Correct and re-enter the command.
---------------------------------------------------------------------------------------
753 MESSAGE REDO INPUT EXCEEDS THE MAXIMUM COMMAND LENGTH.
(CI=753)
CAUSE The input to correct a command is too long.
ACTION Correct the command in stages.
---------------------------------------------------------------------------------------
754 MESSAGE REDO INPUT CONTAINS GARBAGE DELETION. (CI=754)
CAUSE Garbage characters detected after delete characters
(D).
ACTION Re-enter.
---------------------------------------------------------------------------------------
755 MESSAGE UNABLE TO OPEN THE HOST CONSOLE. (CI=755)
CAUSE The workstation is not active, or the host console
is already in use.
ACTION Use the DISPLAY command, or its intrinsic
equivalent, to determine whether the workstation is
active, or the host console is already in use.
Wait until the workstation is active, or the host
console is available, and re-enter the command.
---------------------------------------------------------------------------------------
756 MESSAGE WORKSTATION ID LENGTH IS NOT BETWEEN 1 AND 8
CHARACTERS. (CI=756)
CAUSE A workstation identification length is out of
range.
ACTION A workstation identification must begin with a
letter and be eight or fewer alphanumeric
characters long. Correct the information and
re-enter the data.
---------------------------------------------------------------------------------------