NET/MASTER Messages Manual

NNM1516
Messages
106159 Tandem Computers Incorporated 2–281
NNM1510 LOG FILE logfilename REJECTED - WRONG FILE PARAMETERS
Cause. A LOGSWAP command was issued, and the log subsystem attempted to use
the log file but the file has the wrong parameters. This can only happen if the log
subsystem was forced to use a file created in advance by the user. The user-provided
log file must include:
Enscribe key sequenced file
Block record 4096
Record length 4060
Primary key length 44
Primary key offset 0
Effect. The LOG subsystem rejects the log file, and either continues to use the current
log file or tries to find another log file to swap to.
Recovery. You can use the SHOW LOGS command to list the logical names of the log
files in the NonStop NET/MASTER MS system. You can use the SHOW
SYSPARMS=LOGFILE* to list the physical names of the log files. To add a log file, use
the SYSPARMS LOGFILEn=filename command.
NNM1515 ENTER LOG FILE LOGICAL NAME
Cause. A Log Browse SWAP command was issued, but you did not enter a UDB ID for
the log file.
Effect. The command is ignored.
Recovery. Use the SHOW UDB command to find out if the log file is known to the UDB
subsystem (if you issue the command from Log Browse, precede the command with a
slash (/)). Specify the correct UDB ID for the log file, and retry the SWAP command.
NNM1516 NO LOG RECORDS ON FILE fileid
Cause. A Log Browse SWAP command was issued but there are no records in the log
file that is to be browsed.
fileid is the UDB ID of the file.
Effect. The command is ignored.
Recovery. This message is informational only; no recovery action is necessary.