NET/MASTER Messages Manual

NNM0305
Messages
2–64 106159 Tandem Computers Incorporated
NNM0305 FILEID fileid ALREADY ASSIGNED TO UDB filename
Cause. A UDBCTL command was issued to assign an ID to a UDB file. However, the
UDB file had an ID already.
fileid is the ID of the UDB file specified.
filename is the name of the UDB file specified.
Effect. The assignment is rejected and the original UDB ID remains operative.
Recovery. To assign a new ID to the UDB file, use the UDBCTL STOP command to
delete the existing ID, then assign the new ID.
NNM0306 UNABLE TO ALTER STATUS, UNTIL OPEN ERROR CORRECTED filename
Cause. A UDBCTL command was issued and an attempt was made to assign an ID to,
or to dissociate an ID from, a UDB. The command failed because the UDB had an
OPEN error. If the command operated on a UDB that had a pair of files, one of the
files may have caused the error.
filename is the name of the file that caused the error.
Effect. The operation is not performed.
Recovery. Use the SHOW UDB command to determine the nature of the error. The
error is identified by a Guardian file-system error number.
NNM0307 FILEID fileid STILL HAS ACTIVE USERS
Cause. A UDBCTL CLOSE or UDBCTL STOP command was issued but the specified
UDB file was in use.
fileid is the UDB ID of the file specified.
Effect. The UDB file is not affected.
Recovery. Use the SHOW UDBUSER command to list the users of the UDB file. If it is
necessary to stop system NCL procedures (for example, LOGPROC and EMSPROC)
that are using the UDB file, use the SYSPARMS command (for example, SYSPARMS
LOGPROC=FLUSH).