- In a non-CICS environment, when z/OS Debugger starts in batch mode or full-screen mode, and you allocate the INSPLOG DD name, z/OS Debugger runs the command SET LOG ON FILE INSPLOG OLD and starts writing the log to INSPLOG.
- In a CICS® environment, when z/OS Debugger starts in full-screen mode, it runs the command SET LOG OFF. If you want a log file, you run the command SET LONG ON FILE fileid OLD and z/OS Debugger starts writing the log to fileid.
LOGDSN allows a site or a user to specify the default data set name for the log file. If you specify the LOGDSN command, z/OS Debugger handles the log file in the following way:
- In a non-CICS environment, when z/OS Debugger starts in batch mode or full-screen mode, and you allocate the INSPLOG DD name, z/OS Debugger runs the command SET LOG ON FILE INSPLOG OLD and starts writing the log to INSPLOG . This behavior remains the same.
- In a non-CICS environment, when z/OS Debugger starts in full-screen mode, if you do not allocate the INSPLOG DD name, z/OS Debugger runs the command SET LOG ON FILE fileid OLD and starts writing the log to the data set specified in the LOGDSN command.
- In CICS, when z/OS Debugger starts
in full-screen mode, it runs the command SET LOG ON FILE fileid OLD and
starts writing the log to the data set specified in the LOGDSN command.
This allows a user to always write the log file to a data set, whether in CICS or not, and without having to pre-allocate the log file data set.
For instructions on how to specify the allocation parameters for automatically creating the data set, see LOGDSNALLOC. Use the EQAOPTS LOGDSN and LOGDSNALLOC commands to help a new z/OS Debugger user automatically create and write to the log file.
If you are an existing z/OS Debugger user that uses a SAVESETS data set, and you or your site specify the EQAOPTS commands LOGDSN and LOGDSNALLOC, then the SAVESETS data set contains a SET LOG command that overrides the EQAOPTS command LOGDSN.
The following diagram describes the syntax of the LOGDSN command:
>>-EQAXOPT--LOGDSN--,--'--file_name_pattern--'--+---------+---->< '-,--LOUD-'
- file_name_pattern
- Specifies a naming pattern that determines the name of the data
set that contains the log file. Follow these guidelines when you create
the naming pattern:
- Create a data set name that includes &&USERID. as one of the qualifiers. z/OS Debugger substitutes the user ID of the current user for this qualifier when it determines the name of the data set.
- Specify NULLFILE to indicate you do not want z/OS Debugger to write to a log file.
- LOUD
- Specifies that z/OS Debugger display WTO messages, which helps you debug processing done by this command. z/OS Debugger normally does not display any messages if it does not find the data set. If you are trying to determine why z/OS Debugger is not writing to this log file, specify LOUD to see if it displays any messages.
- Instruct z/OS Debugger to create the log file by specifying the EQAOPTS LOGDSNALLOC command, as described in LOGDSNALLOC.
- Create the log file manually with the allocation parameters that are described in "Data sets used by z/OS Debugger" in the IBM z/OS Debugger User's Guide .
Example
EQAXOPT LOGDSN,'&&USERID.DBGTOOL.LOG'If you log in with user ID jsmith, z/OS Debugger determines the name of the data set to be JSMITH.DBGTOOL.COMMMANDS.