NET/MASTER Messages Manual

NNM1507
Messages
2–280 106159 Tandem Computers Incorporated
NNM1507 NNM LOG SUBSYSTEM DOES NOT HAVE ANY AVAILABLE LOG FILES. error
Cause. The LOG subsystem was unable to log event messages. Possible causes are:
LOGWRAP system parameter has a value of NO and all declared log files were
used once already
Log files are secured from access by the LOG subsystem, in which case the reason
for the error is returned
error contains a Guardian file-system error number and the name of the file
that is in error.
Effect. A warning message is sent to the EMS collector ($0).
Recovery. Use the error number to determine the appropriate action to take. Use the
SHOW SYSPARMS=LOG* command to determine the number of log files in the
NonStop NET/MASTER MS system. If there are less than nine, you can declare more
files through the SYSPARMS LOGFILEn=filename command. If LOGWRAP is set to
NO, you can issue SYSPARMS LOGWRAP=YES to allow the log files to be reused.
NNM1508 LOGSWAP COMPLETED, NEW LOG= filename
Cause. The LOGSWAP command was successful.
filename is the name of the new log file.
Effect. The current log file is closed, and the next available log file is opened. Any old
data in the opened log file is purged.
Recovery. This message is informational only; no recovery action is necessary.
NNM1509 SYSPARMS logfilename CAN NOT BE CHANGED - IN USE
Cause. The SYSPARMS LOGFILEn=filename command failed because the log file
LOGn is currently in use.
Effect. The LOG subsystem continues normally, and ignores the command.
Recovery. Execute the LOGSWAP command to swap to another log file and then retry
the SYSPARMS LOGFILEn=filename command.