When the SYSLOG file is maintained as an FGG, then openUTM opens a file generation of the SYSLOG-FGG as the SYSLOG file when the application starts. All tasks of the application write UTM messages with the destination SYSLOG to this file generation first.
If the SYSLOG is created as a file generation group, you need only create the file generation group (FGG) before the start. You do not have to create the individual file generations because openUTM does not open a SYSLOG file generation before checking that it already exists. If the file generation exists, it is simply opened. If the file generation does not yet exist, openUTM creates the file generation automatically with the properties of the file generation group.
If you want to assign particular values for primary and secondary allocation to the file generations, then you must create a file generation of the FGG with the desired values. openUTM then creates the next file generations with the same values.
Making the SYSLOG-FGG known
You have the following opportunities to make the SYSLOG-FGG known to openUTM:
Using the link name “SYSLOG”
At the start of the application, you create an FGG with any name for the SYSLOG. Then assign the link name SYSLOG to one of the FGG file generations using /SET-FILE-LINK. The link name must be assigned before each application start.
In this case, the file generation group containing the file generation with the link name SYSLOG is taken as the SYSLOG-FGG. openUTM first logs data in the file generation with the link name SYSLOG (first SYSLOG file generation).
If you generated automatic size monitoring for your application, openUTM switches to the next file generation of this FGG as soon as the size of the first SYSLOG file generation has reached the threshold value for size monitoring. If this file generation does not yet exist, openUTM creates it automatically.
If the application was generated without automatic size monitoring, openUTM continues logging data in the file generation with the link name SYSLOG until you switch to another file generation of the FGG using the administration command KDCSLOG, or until you activate automatic size monitoring (e.g. with the administration command KDCSLOG). This file generation is likewise created automatically by openUTM when switching files.
Creating an FGG with the name filebase.SLOG before the first start of the application
This file generation group must have the same base name (including CATID and USERID) as the KDCFILE (KDCA file) and must be set up under the BS2000 user ID under which the UTM processes run.
openUTM only uses the FGG with the name filebase.SLOG as the SYSLOG-FGG if no file or file generation assigned to the link name SYSLOG exists under the user ID of the application when the application starts. If a file or file generation with the link name SYSLOG exists, openUTM always logs the SYSLOG UTM messages in this file.
If filebase.SLOG is a file generation group, then the defined base of the FGG determines which file generation is taken as the first SYSLOG file.
Basis outside of the valid range
If the base lies outside the valid range (e.g. BASE-NUM=0), then openUTM creates the file generation with the generation number LAST-GEN+1 at the start of the application. This file generation is then the first SYSLOG file.
The next generation of the file generation last written in the previous application run is used by openUTM as the first SYSLOG file the next time the application starts. In other words, if data is written in the generations up to the n-th file generation in the last application run, then logging starts with the (n+1)-th file generation with the next application start.
Basis within the valid range
If the base lies within the valid range between the first and last file generation (the output of the SHOW-FILE-ATTRIBUTES command on the FGG shows FIRST-GEN <= BASE-NUM <= LAST-GEN), then the base generation is taken as the first SYSLOG file.
openUTM does not modify the base number set by you. In other words, if the base lies outside the valid range, at the next application start openUTM begins logging again in the same file generation as with the previous start unless you modify the base setting beforehand.