XMLOPTS statement
The XMLOPTS statement controls how
BMC AMI Log Master
maintains the XML VSAM files that it uses to store data from XML columns.
BMC AMI Log Mastercreates one set of VSAM files for each XML column that occurs in the log records that are selected by a log scan. If an XML column occurs in a partitioned table space, BMC AMI Log Master creates one set of VSAM files for each partition of each XML column. BMC AMI Log Master deletes the XML VSAM files at the end of processing unless the log scan includes an output logical log file.
The following figure shows the XMLOPTS statement syntax diagram:
Option | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
TRACKS | CYLINDERS | Specifies the units that BMC AMI Log Master uses to allocate XML VSAM files.
See also LOBALLOC=CYLINDERS. | ||||||||
SPACE (priSpace, secSpace) | Specifies how BMC AMI Log Master allocates disk space for XML VSAM files. Use this keyword along with the CYLINDERS or TRACKS keyword. BMC AMI Log Master allocates these data sets in the same way that VSAM data sets are allocated in JCL. BMC AMI Log Master allocates priSpace first. If BMC AMI Log Master needs more space, it allocates an additional amount of secSpace (often called an extent). BMC AMI Log Master can allocate up to 128 extents. See also LOBSPACE=(10,10). | ||||||||
VOLUME (volser) | Specifies the volumes that BMC AMI Log Master uses to store XML VSAM files. Enter a list of valid volsers. Separate multiple volsers with commas. BMC AMI 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 BMC AMI Log Master uses to store XML VSAM files. See also LOBSTOR=. | ||||||||
MGMTCLAS (mgmtClass) | Specifies the DFSMS management class that BMC AMI Log Master uses to store XML VSAM files. See also LOBMGMT=. | ||||||||
DATACLAS (dataClass) | Specifies the DFSMS data class that BMC AMI Log Master uses to store XML VSAM files. See also LOBDATA=. | ||||||||
PREFIX (clusterPrefix) | Defines a prefix that BMC AMI Log Master uses in the names of XML VSAM files. BMC AMI Log Master constructs the data set name by using this prefix, the database identifier (DBID) of the XML 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 XMLPREF=&&SYSUID..XML. | ||||||||
DUPLICATE DATASET | Determines how BMC AMI Log Master responds to a duplicate data set condition as it attempts to create an XML VSAM file. This keyword determines the severity of the message that BMC AMI Log Master displays, and whether BMC AMI 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. | ||||||||
XMLLIMIT nn | Determines the maximum number of XML VSAM files that BMC AMI Log Master can create to store the data of one XML column (or one partition of one XML column). BMC AMI Log Master allocates a new XML VSAM file only when it has filled the initial data set and all possible extents, but more XML column data remains to be written. If the number of data sets (with full extents) that are required to store an XML column’s data exceeds this limit, BMC AMI Log Master issues an error message, saves any temporary XML VSAM files permanently to disk, and terminates the processing. Specify the number of data sets between 1 and 26. The default value is 10. See also LOBLIMIT=10. |