
Procedure
1. When you start using ISPF, delete the ISPF log information from the ISPF log dataset.
2. When you perform an operation in the Smart Manager for Mainframe panel, enter LOG in the
Command line.
The Specify Disposition of Log Data Set panel appears.
3. Select 3 (Keep existing data set and continue with new data set ).
The ISPF log dataset is switched to another dataset.
You must periodically switch the ISPF log dataset to another dataset to prevent the ISPF log dataset
from becoming full.
TIP:
If the CLI command terminated abnormally because the ISPF log dataset was full, in the ISPF end menu
( Specify Disposition of Log Data Set panel), select 4 (Keep data set - New (allocate new data set in
next session)) to save the current ISPF log dataset, and then allocate another dataset.
Collecting the CLI command-execution log
If you specify the SYSLOG environment variable to output CLI command-execution logs to SYSLOG,
the KTC310I or KTC311I message containing the command-execution log (that is, the command
name, parameters, and execution results) for the following CLI commands will be output to SYSLOG:
KTACTTPG, KTCONMSG, KTDCTDEV, KTDCTTPG, KTGETHDA, KTIMPORT, KTLOAD, KTQRYDEV,
KTQRYRLC, KTQRYTPG, KTQSTATS, KTSCAN, KTSTORE
The log for the KTCONMSG command will be output only when OPEN or CLOSE is specified in the OP
parameter.
There are two methods for extracting output CLI command-execution logs from SYSLOG:
• Use an ISPF editor.
• Use an output script.
Related topics
• Setting the operating environment by using environment variables, page 41
• Setting the operating environment by using system symbols, page 43
Extracting CLI command-execution logs by using an ISPF editor
To use an ISPF editor to extract CLI command-execution logs from SYSLOG to a sequential dataset:
Procedure
1. Create a dataset to which log data will be extracted from SYSLOG.
YUKON.KTLOG is assumed as the name of the allocated sequential dataset.
2. Display SYSLOG in the SDSF panel.
User Guide 219
Komentarze do niniejszej Instrukcji