If you want to work with a SYSLOG-FGG, you must create this before the start of the application.
Creating SYSLOG as filebase.SLOG
In the simplest case you work with the FGG filebase.SLOG, whereby the base lies outside the valid range. This FGG need only be created once before the first application start. For each subsequent application start, openUTM automatically continues with the next generation of the file generation last written, provided you do not move the base into the valid range. You can create the FGG using the following BS2000 command:
/CREATE-FILE-GROUP - / GROUP-NAME = filebase.SLOG - / ,GENERATION-PARAMETER = *GENERATION-PARAMETER( - / MAXIMUM = n - / [,VOLUME = volume - / ,DEVICE-TYPE = device - / ,OVERFLOW-OPTION = overflow ] )
Meaning of parameters:
MAXIMUM=n
Maximum number of file generations that can be cataloged simultaneously in the FGG.
VOLUME=volume, DEVICE=device
Volume identifier and device type of the disk on which the FGG is to be
created. The FGG can be created on PUBLIC or PRIVATE DISK.
OVERFLOW-OPTION=overflow
Specifies what should happen if the maximum permitted number of file generations (MAXIMUM) is exceeded. You can use this operand to control whether only the last n (MAXIMUM) file generations are to be retained from the SYSLOG-FGG of your application, or whether all file generations written by openUTM are to be retained. You can specify CYCLIC-REPLACE, REUSE-VOLUME or KEEP-GENERATION.
(See also section "Identifier overflow protection" and section "Retaining SYSLOG generations".)
KEEP-GENERATION
All file generations are retained, even if the number specified in MAXIMUM is exceeded.
CYCLIC-REPLACE and REUSE-VOLUME
Specify that the oldest file generation of the FGG is deleted before the new one is created.
If you specify CYCLIC-REPLACE or REUSE-VOLUME here, the value you select for the MAXIMUM (number of file generations) should not be too small. After switching files, the “old” file generation, which is no longer being written by openUTM, can be kept open for a longer period by some tasks (if these are using a user program unit for a very long time). If you have permitted n file generations and if a task keeps the file generation i open, it is not yet possible to switch to file generation i+n. The BS2000 system reports a DMS error for this file generation. Automatic size monitoring is suspended until the administrator of the application successfully switches the SYSLOG file using the KDCSLOG command.
With OVERFLOW-OPTION=KEEP-GENERATION, however, it is also possible to switch files in this case.
Using the command you create an FGG whose base lies at 0, i.e. outside the valid range. openUTM automatically creates all file generations. With the first application start, openUTM creates the file generation with the generation number 1 and uses this as the first SYSLOG file.
Creating SYSLOG with link names
If you want to work with the link name SYSLOG, then you can create the SYSLOG using the same command as for a SYSLOG with filebase.SLOG (see above). For GROUP-NAME, you can specify any name fgg-name. Before each application start, you must then use the following BS2000 command to assign the link name SYSLOG to the file generation which should be opened by openUTM as the first SYSLOG:
/SET-FILE-LINK LINK-NAME=SYSLOG,FILE-NAME=fgg-name(*gen)
gen is the generation number of the file generation which openUTM should open as the first SYSLOG file after the application start.