NET/MASTER Messages Manual

NNM2365
Messages
2–412 106159 Tandem Computers Incorporated
NNM2365 INVALID SUBVOLUME NAME
Cause. The subvolume entered was not valid. It must be $volume.subvolume or
\system.$volume.subvolume.
Effect. The definition cannot be updated or added.
Recovery. The name is most likely mistyped; correct the spelling and try again. If the
name is as you intended, check your source to find the correct name.
NNM2366 INVALID SWAP VOLUME NAME
Cause. The volume name entered for the swap volume was not valid.
Effect. The definition cannot be updated or added.
Recovery. The name is most likely mistyped; correct the spelling and try again. If the
name is as you intended, check your source to find the correct name.
NNM2367 INVALID SESSION NAME
Cause. A session name specified in an OPSYS SEND command must be 1 through 20
letters, digits, or underscores; beginning with a letter.
Effect. The command is not performed.
Recovery. Specify a proper session name.
NNM2368 SESSION sessname IS UNKNOWN
Cause. An OPSYS ANSWER, OPSYS EOF, OPSYS BREAK, or OPSYS KILL command
was entered that referred to a session that has not been set up.
sessname is the name of the session. This could be either an explicit reference:
OPSYS dsnm-command - keyword session = utility text
or an implicit reference:
OPSYS dsnm-command-keyword utility text
A session with a utility must be established by OPSYS SEND (or its various shorthand
versions) before the session can be referenced by the other OPSYS commands.
Effect. The command is not performed.
Recovery. If the session or utility name was mistyped, correct it and enter the
command again. Else set up the session.