Switching to the next file generation

The KDCLOG command and the KC_USLOG opcode on the KDCADMI program interface can be used by the administrator to switch to the next file generation. Each time the KDCLOG command or a corresponding KDCADMI call is issued, openUTM switches to the next file generation.

At the first start of the UTM application, openUTM writes the user log records in the generation of the group that was specified as the base at the time of creation. openUTM issues a MODIFY-FILE-GROUP-ATTRIBUTES command to the next file generation and sets the base to the next most recent file generation with each additional switch initiated by the administrator.

You can also switch to the next generation as follows after a UTM application terminates normally:

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

These commands for switching to the next file generation can also be transferred to the start procedure of your UTM application.

If the administrator, for example, wants to switch to another user log file with KDCLOG, the file generation group must be created under the same BS2000 user ID under which the UTM processes are running.