Creating the user log file

The file generation group for the user log file must have the file name filebase.USLA. Here, filebase is the base name of the KDCFILE as generated in MAX..., KDCFILE=filebase.

The file generation group must be created before the first application start. The following BS2000 commands must thus be issued:

• CREATE-FILE-GROUP command to create the catalog entry. You must specify:

  • the name of the file generation group

  • the maximum permitted number of generations

  • the procedure when the maximum number of generations is reached (OVER-FLOW-OPTION=CYCLIC-REPLACE is the default)

  • the access authorization, if necessary

• CREATE-FILE-GENERATION command to create at least one generation.

• MODIFY-FILE-GROUP-ATTRIBUTES command to define the reference generation for relative numbering.

Example: Creating a file generation group for a user log file

/CREATE-FILE-GROUP GROUP-NAME=filebase.USLA                      -
/                 ,GENERATION-PARAMETER=GENERATION-PARAMETER(    -
/                  MAXIMUM=3,OVERFLOW-OPTION=REUSE-VOLUME)
/CREATE-FILE-GENERATION GENERATION-NAME=filebase.USLA(+1)
/MODIFY-FILE-GROUP-ATTRIBUTES GROUP-NAME=filebase.USLA           -
/                 ,GENERATION-PARAMETER=GENERATION-PARAMETER(    -
/                  BASE-NUMBER=RELATIVE-TO-LAST-GEN(NUMBER=0))

If the OVERFLOW-OPTION=REUSE-VOLUME parameter is set, a new generation is created on the same volume as the deleted generation.

If the user log records (LPUT calls) can be > 6 KB, you must specify the SPACE operand in the CREATE-FILE-GENERATION commands for the primary and secondary allocation. The values of the SPACE operand must be large enough that at least one LPUT record fits in the disk area for the secondary allocation. The primary allocation must be at least twice as big as the secondary allocation.

If the file generation group is to be created on a private disk, you must also note the following:

• Each individual file generation of the group must be created on the private disk using a CREATE-FILE-GENERATION command before the start of the application.

• You must specify OVERFLOW=REUSE-VOLUME when creating the file generation.

• If the base of the file generations is set to the last member of the file generation group following creation, openUTM begins with the last file generation and then switches to the next generation. If the first generation is specified as the base, openUTM switches to the last generation when the first KDCLOG command is issued (see  Switching to the next file generation).

These restrictions do not apply to file generations on PUBLIC DISK.

 

Example: Creating a file generation group on private disk

/CREATE-FILE-GROUP GROUP-NAME=filebase.USLA                      -
/                  ,GENERATION-PARAMETER=GENERATION-PARAMETER(   -
/                   MAXIMUM=3,OVERFLOW-OPTION=REUSE-VOLUME       -
/                  ,VOLUME=B004H,DEVICE-TYPE=D3465)
/CREATE-FILE-GENERATION GENERATION-NAME=filebase.USLA(*1)        -
/                  ,SUPPORT=PRIVATE-DISK(VOLUME=B004H,DEVICE-TYPE=D3435)
/CREATE-FILE-GENERATION GENERATION-NAME=filebase.USLA(*2)        -
/                  ,SUPPORT=PRIVATE-DISK(VOLUME=B004H,DEVICE-TYPE=D3435)
/CREATE-FILE-GENERATION GENERATION-NAME=filebase.USLA(*3)        -
/                  ,SUPPORT=PRIVATE-DISK(VOLUME=B004H,DEVICE-TYPE=D3435)
/MODIFY-FILE-GROUP-ATTRIBUTES GROUP-NAME=filebase.USLA           -
/                  ,GENERATION-PARAMETER=GENERATION-PARAMETER(   -
/                   BASE-NUMBER=RELATIVE-TO-LAST-GEN(NUMBER=0))