This topic describes the Allocation parameters syntax used in various elements of the LOGSCAN statement.
These parameters determine the keywords and values that Log Master uses when it allocates space for an output data set.
The following is the Allocation parameters syntax diagram:
The following table describes the Allocation parameters options:
Indicates whether Log Master instructs the operating system to compress the data in an output data set.
|CYLINDERS | TRACKS|
Specifies how Log Master allocates space for an output data set. CYLINDERS indicates that Log Master uses DASD cylinders. TRACKS indicates that Log Master uses DASD tracks.
Specifies the data class of an output data set. Use this keyword only with DFSMS. A data class defines allocation attributes of a data set (such as organization or record length).
Specifies the expiration date of an output data set. In the initial request for space, Log Master includes the date specified by expDate. On or after that date, the data set can be deleted or written over by another data set. You cannot specify both an expiration date and a retention period for the same data set.
Enter an expiration date using the format yyyy/ ddd, where yyyy represents a four-digit year and ddd represents the number of days from the beginning of the year (the julian date). For example, you would enter January 30, 2010 as 2010/030.
Do not enter any two-digit year values, except for the dates 99365, 99366, 98000, and 99000 (these dates have special meanings for the operating system and certain tape management systems).
Specifies the retention period of an output data set. Enter a retention period using a number from 0 to 9999. In the initial request for space, Log Master includes the retention period. After the specified number of days have passed, the data set can be deleted or written over by another data set. You cannot specify both a retention period and an expiration date for the same data set.
Specifies the allocation attributes of an output data set by copying the attributes of the model data set defined by modelDscb. Use an existing cataloged data set on a direct access volume as the model data set. This keyword is required if you are cataloging generation data group (GDG) data sets.
Specifies the logical record length (in bytes) of records in an output data set. When Log Master writes
The required LRECL value depends on the output type. For reports that you generate using a template, you must define the LRECL of your output to be large enough to accommodate the longest line length defined by your template.
shows the required and default values of this keyword, depending on the type of output that Log Master writes to the output data set.
Directs Log Master to limit the number of volumes that it uses to store output data sets. Enter a maximum number of volumes as volumeCount.
Specifies the management class of an output data set. Use this keyword only with DFSMS. A management class defines how DFSMS manages a data set (when DFSMS migrates the data set, when it archives the data set, and so on).
Directs Log Master to request that the operating system releases any unused space when it closes a given output data set.
Determines how Log Master requests space for an output data set on a direct access volume.
Specifies the storage class of an output data set. Use this keyword only with DFSMS. A storage class defines storage attributes of a data set (similar to those defined with the UNIT or MAXVOL keywords).
Specifies the storage device (or group of devices) where Log Master requests space for an output data set. Enter the unit name of a device or group of devices. Do not use this keyword with DFSMS.
Specifies the volume or volumes where Log Master stores output data sets. You can specify up to six VOLSERs (regardless of the value of the MAXVOL keyword). Separate multiple VOLSERs with commas. If you specify a magnetic tape volume, Log Master overwrites any existing information on the tape.