Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Record logging 1
- Thread starter 149149149
- Start date
If you want to log commands then yes... IOELI Input Output I/O Log Initiate.
IOELI[:[PRINT=][,RESULT=]];
PRINT= YES or NO
Will log print commands or not.
RESULT= YES, NO, SEP
Will log the results of commands or not, you can use sep if you want results in a separate file from the commands.
The I/O log function consists of the following logs:
Command log
The command log enables the analysis of terminal activities. It can also be edited and used to regenerate the data that were changed since the last dump, or to synchronize data between the system and an external data base. A command log stores records of the entered commands and related data.
The command log logs the following events:
MML commands and their execution result
Data reload
Periodic system dump
Logon log
The logon log is activated automatically when the system is put into service.
The logon log enables the analysis of system access. A logon log stores records of logon events, both successful and unsuccessful, and logoff events. Logging of logon/logoff events is automatically initiated; it does not have to be initiated via MML command.
The relevant data are written into the log files on the storage device and the files are stored under the directory /SYSN/USER1/SES/IC. There are 12 logon log files, one for each month, which stores the logon/logoff events. They are named LOGONyy.DAT where yy ranges from 01 to 12.
The data in the command log file are in ACSII format.
For each logon event the following data are logged:
The date and time of the event
The identification of the MML port that was used to logon
The name of the user account that was used to logon via NIU or a dash (-) if logged on via IPU
The authority level associated with the account (logon via NIU) or the password (logon via IPU)
The logon indicator (LOGIN)
The logon result (OK or NOK)
The remote IP address if logged on via TELNET
For each logoff event the following data are logged:
The date and time of the event
The identification of the MML port that was used to logon
The name of the user account that was used to logon via NIU or a dash (-) if logged on via IPU
The authority level associated with the account (logon via NIU) or the password (logon via IPU)
The logon indicator (LOGOUT)
The existing logon log files can be printed and erased by using file system commands like FIFCP, FIDAP and FIDIE.
IOELI[:[PRINT=][,RESULT=]];
PRINT= YES or NO
Will log print commands or not.
RESULT= YES, NO, SEP
Will log the results of commands or not, you can use sep if you want results in a separate file from the commands.
The I/O log function consists of the following logs:
Command log
The command log enables the analysis of terminal activities. It can also be edited and used to regenerate the data that were changed since the last dump, or to synchronize data between the system and an external data base. A command log stores records of the entered commands and related data.
The command log logs the following events:
MML commands and their execution result
Data reload
Periodic system dump
Logon log
The logon log is activated automatically when the system is put into service.
The logon log enables the analysis of system access. A logon log stores records of logon events, both successful and unsuccessful, and logoff events. Logging of logon/logoff events is automatically initiated; it does not have to be initiated via MML command.
The relevant data are written into the log files on the storage device and the files are stored under the directory /SYSN/USER1/SES/IC. There are 12 logon log files, one for each month, which stores the logon/logoff events. They are named LOGONyy.DAT where yy ranges from 01 to 12.
The data in the command log file are in ACSII format.
For each logon event the following data are logged:
The date and time of the event
The identification of the MML port that was used to logon
The name of the user account that was used to logon via NIU or a dash (-) if logged on via IPU
The authority level associated with the account (logon via NIU) or the password (logon via IPU)
The logon indicator (LOGIN)
The logon result (OK or NOK)
The remote IP address if logged on via TELNET
For each logoff event the following data are logged:
The date and time of the event
The identification of the MML port that was used to logon
The name of the user account that was used to logon via NIU or a dash (-) if logged on via IPU
The authority level associated with the account (logon via NIU) or the password (logon via IPU)
The logon indicator (LOGOUT)
The existing logon log files can be printed and erased by using file system commands like FIFCP, FIDAP and FIDIE.
-
1
- Thread starter
- #4
- Status
