LOG
- Purpose
-
The LOG option specifies the location of the member-level log files to be additionally generated.
- Default
-
By default, if you do not specify the LOG option, ABO will not generate member-level log files. Note that regardless of the LOG option the output from the entire ABO invocation will always be generated in the location according to OPTLOG DD.
- Parameters
-
- dsn:
A data set name that must include the high-level qualifier.
- DD:ddname:
Specifies a ddname.
- path:
A full HFS path that starts with a slash(/).
- dsn:
- Usage
-
The target of the LOG option can be one of the following items:
- A PDS or PDSE. When a member is optimized, the log output particular to that member is placed in a member of the PDS or PDSE where the member name is based on the optimized member name (upper-cased and truncated to 8 characters). The contents of the member, if any, are overwritten even if the former contents were produced by ABO in previous invocations.
- An HFS path pointing to a directory. When a member is optimized, the log output particular to that member is placed in a file in the specified HFS directory where the file name is based on the optimized member name appended with .log. The contents of the member, if any, are overwritten even if the former contents were produced by ABO in previous invocations.
Notes:- The target of the LOG option must be either a PDS or PDSE with no member specified, or an HFS path that points to a directory. If the target of the LOG option is specified as a PDS or PDSE with a member specified, a sequential data set, or an HFS file, an error message will be issued.
- The target data set of the LOG option should follow the recommended allocation parameters of the OPTLOG in Table 1.
Example 1
BOPT IN=DD:SYSBIN(*) OUT=DD:SYSBOUT LOG=HLQ.LOG.OUT
Example 2
BOPT IN=DD:SYSBIN(*) OUT=DD:SYSBOUT LOG=DD:LOG
Example
3
BOPT IN=DD:SYSBIN(*) OUT=DD:SYSBOUT LOG=/home/user1/logdir
For more information, see Log files.
