The ATMCOMM log file is stored on the A disk of the user on which ATMCOMM is running. The file stores records in variable record length, or V, format. Each line in the file represents a single message or command recorded by ATMCOMM. The first field on each line is an eight-character time stamp in the format hh:mm:ss.
One blank follows the time stamp, and then a number representing the message type is shown. The numbers are assigned as follows:
Messages appearing in the log file with the letter I are ATMCOMM internal messages. These messages are as follows:
ATM9103I ATMCOMM terminating - returning to CMS ATM9111I ATMCOMM loaded: mm/dd/yy hh:mm:ss Started: mm/dd/yy hh:mm:ss ATM9129I No disk space for log file; logging suspended ATM9130I Logging resumed Atmcomm; (Ready message, including time stamp and RC) ATMCOMM (Null input message) Unknown CP/CMS command (Error response to invalid command)
In the log file, the user ID where the message originated is displayed following the message type. For SCIF traffic received from user RSCS, RSCS is displayed. However, the user ID for the user on which ATMCOMM is running is shown as an asterisk (*) rather than the actual user ID.
Messages containing the letters C or I will always display an asterisk in this field. It is important to note that sending the command MSG * HELLO from the user where ATMCOMM is running will also result in an asterisk in this field.
The informational fields are followed by the message text, beginning in position 21 on each line. Message text is unformatted. Messages do not include any indication where the message originated since that information is contained in the previous field. For the same reason, SCIF traffic does not include a user ID prefix.
|
Copyright © 2014 CA.
All rights reserved.
|
|