Allocation parameters

This topic describes the Allocation parameters syntax used in various elements of the LOGSCAN statement.

These parameters determine the keywords and values that BMC AMI Log Master uses when it allocates space for an output data set.

The following is the Allocation parameters syntax diagram:

Related topic

LOGSCAN-output-definition

The following table describes the Allocation parameters options:

Option

Description

COMPRESS

Indicates whether BMC AMI Log Master instructs the operating system to compress the data in an output data set.

CYLINDERS | TRACKS

Specifies how BMC AMI Log Master allocates space for an output data set. CYLINDERS indicates that BMC AMI Log Master uses DASD cylinders. TRACKS indicates that BMC AMI Log Master uses DASD tracks.

DATACLAS (dataClass)

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).

EXPDT (expDate)

Specifies the expiration date of an output data set. In the initial request for space, BMC AMI 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, 2022, as 2022/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).

RETPD (retPeriod)

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, BMC AMI 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.

LIKE (modelDscb)

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.

LRECL (nnnn)

Specifies the logical record length (in bytes) of records in an output data set. When BMC AMI Log Master writes

SQL output files or DDL output files to a fixed blocked (FB) file, it forces the LRECL value of the output data set to be 80 bytes
load control files, it forces the LRECL value of the output data set to be 80 bytes (and the RECFM value to be FB)
printed output reports to a fixed blocked (FB) file, it forces the LRECL value of the output data set to be a minimum of 81 bytes.

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.

The following table shows the required and default values of this keyword, depending on the type of output that BMC AMI Log Master writes to the output data set.

Type of output	Required RECFM value	Default LRECL value	Required LRECL value
Reports (standard default reports)	FBA	81	81 to 32760 (Catalog Activity report requires a value greater than 132)
Reports (standard default in CSV or SDF format)	VB	270	81 to 32760 (Catalog Activity report requires a value greater than 132)
Reports (generated from report template)	FBA	81	81 to 32760 (Define the LRECL of your output to be large enough to accommodate the longest line length defined by your template.)
SQL files	FB or VB	FB 80 VB System Determined Block size (SDB) minus 4 bytes	FB 80 VB a value greater than or equal to the maximum length of the SQL statement plus 4
SQL template files	same as SQL file	same as a corresponding SQL file	same as a corresponding SQL file
DDL files	FB or VB	FB 80 VB SDB minus 4 bytes	FB 80 VB a value greater than or equal to the maximum length of the DDL statement plus 4
Logical log data files	VB	SDB minus 4 bytes	Required: a value greater than or equal to the length of the logical log header Recommended: a value equal to the length of the logical log header plus the length of the table rows included in the output
Logical log control files	VB	SDB minus 4 bytes	Required: a value greater than or equal to the length of the longest logical log control record (see Logical-log-files)
Load data files	VB or VBS	SDB minus 4 bytes	Required: a value greater than or equal to the length of the informational columns added to the output records Recommended: a value equal to the length of the informational columns added to the output records plus the length of the table rows included in the output
Load control files	FB	80	80

MAXVOL (volumeCount)

Directs BMC AMI Log Master to limit the number of volumes that it uses to store output data sets. Enter a maximum number of volumes as volumeCount.

MGMTCLAS (mgmtClass)

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).

RELEASE

Directs BMC AMI Log Master to request that the operating system releases any unused space when it closes a given output data set.

SPACE

Determines how BMC AMI Log Master requests space for an output data set on a direct access volume.

Value	Description
*priSpace*	Specifies the number of units of storage (either cylinders or tracks) that BMC AMI Log Master requests when it creates the output data set.
*, secSpace*	Specifies the number of units of storage that BMC AMI Log Master requests when it finds that either the primary allocation is full or a previous secondary allocation is full. If you specify secSpace , separate it from priSpace with a comma.

STORCLAS (storClass)

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).

UNIT (unitName)

Specifies the storage device (or group of devices) where BMC AMI 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.

VOLUME

Specifies the volume or volumes where BMC AMI 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, BMC AMI Log Master overwrites any existing information on the tape.

Allocation parameters

On this page