DSM/SCM Messages Manual

DSM/SCM EMS Messages
DSM/SCM Messages Manual—529845-006
5-18
2035
DSC SPI command CONFIG Safeguard access check
DSC SPI command LISTDEV Safeguard command ADD FILE
EDITREAD Safeguard command DELETE FILE
EDITREADINIT SETMODE
FILEINFO STOP
FILEINQUIRE TAPEMOUNT
FUP Dup UNLOCK
NEWPROCESS WRITE
NEXTFILENAME WRITEREAD
filename
is the file name in the internal format of the file where the error occurred.
Cause. A warning or restartable file error occurred during the specified procedure or
action.
Effect. If the error is a warning, the activity continues processing. If the error is
restartable, the activity stops in a restartable state.
Recovery. Check the file-system error code in the message. For a definition of the
specified error, see Section 7, File-System Errors. For more detailed information,
including recovery actions, see the Guardian Procedure Errors and Messages Manual .
If the error is a warning, the operator or planner might need to decide if corrective
action is needed. If the error is restartable, correct the error and restart the activity.
If the file name was $EMSLOGF.ILEERROR, the server process could not send an
EMS message out to the DSM/SCM EMS collector. Instead, this error was reported
back to the Schedule Manager on behalf of the server that could not send out the
message. This is most likely caused by an internal code error where an EMS message
routine was not called. Performing a trace will help identify the faulty code to
development.
2035
remote-node-num
is the name of the remote system that was not available.
Cause. A user request to a remote system could not be finished because the remote
system was not available.
Effect. The activity stops in a restartable state.
Recovery. Determine why the Expand line is down or unavailable. If possible, correct
the problem that is causing the line to be down. Restart the activity when the remote
system is available.
Remote system remote-node-num not available. RESTART the
activity when the remote system is available.