LOBOPTS statement
The LOBOPTS statement controls how
Log Master
maintains the LOB VSAM files that it uses to store large object (LOB) data.
Log Master creates one set of VSAM files for each LOB column that occurs in the log records that are selected by a log scan. If a LOB column occurs in a partitioned table space, Log Master creates one set of VSAM files for each partition of each LOB column. Log Master deletes the LOB VSAM files at the end of processing unless the log scan includes an output logical log file.
The following figure shows the LOBOPTS statement syntax:
Option | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
TRACKS | CYLINDERS | Specifies the units that Log Master uses to allocate LOB VSAM files.
See also LOBALLOC=CYLINDERS. | ||||||||
SPACE (priSpace,secSpace) | Specifies how Log Master allocates disk space for LOB VSAM files. Use this keyword along with the CYLINDERS or TRACKS keyword. Log Master allocates these data sets in the same way that VSAM data sets are allocated in JCL. Log Master allocates priSpace first. If Log Master needs more space, it allocates an additional amount of secSpace (often called an extent). Log Master can allocate up to 128 extents. See also LOBSPACE=(10,10). | ||||||||
VOLUME (volser) | Specifies the volumes that Log Master uses to store LOB VSAM files. Enter a list of valid volsers. Separate multiple volsers with commas. Log Master uses the volumes that you specify in an IDCAMS DEFINE CLUSTER command. See also LOBVOLS=. | ||||||||
STORCLAS (storageClass) | Specifies the Data Facility Storage Management System (DFSMS) storage class that Log Master uses to store LOB VSAM files. See also LOBSTOR=. | ||||||||
MGMTCLAS (mgmtClass) | Specifies the DFSMS management class that Log Master uses to store LOB VSAM files. See also LOBMGMT=. | ||||||||
DATACLAS (dataClass) | Specifies the DFSMS data class that Log Master uses to store LOB VSAM files. See also LOBDATA=. | ||||||||
PREFIX (clusterPrefix) | Defines a prefix that Log Master uses in the names of LOB VSAM files. Log Master constructs the data set name by using this prefix, the database identifier (DBID) of the LOB column, the page set identifier (PSID) of the column, and a sequentially incremented data set number. To avoid duplicate data sets during repeated log scans, consider using symbolic values such as &DATE. and &TIME. in the prefix that you define. See also LOBPREF=&&SYSUID..LOB. | ||||||||
DUPLICATE DATASET | Determines how Log Master responds to a duplicate data set condition as it attempts to create a LOB VSAM file. This keyword determines the severity of the message that Log Master displays, and whether Log Master continues processing. To avoid duplicate data sets during repeated log scans, consider using symbolic values such as &DATE. and &TIME. in the prefix that you define with the PREFIX keyword.
See also LOBDUPDS=ERROR. | ||||||||
LOBLIMIT nn | Determines the maximum number of LOB VSAM files that Log Master can create to store the LOB data of one LOB column (or one partition of one LOB column). Log Master allocates a new LOB VSAM file only when it has filled the initial data set and all possible extents, but more LOB column data remains to be written. If the number of data sets (with full extents) that are required to store a LOB column’s data exceeds this limit, Log Master issues an error message, saves any temporary LOB VSAM files permanently to disk, and terminates processing. Specify a number of data sets between 1 and 26. The default value is 10. See also LOBLIMIT=10. |