KC_USLOG - Administer the user log file

The user log file is managed as the file generation directory USLOG. Using KC_USLOG, you can close the current user log file (file generation of USLOG) and simultaneously open a new user log file, which is the file generation with the next generation number. The closed log file may then be put to any use you require.

Switching with dual USLOG

If the user log file of your application is operated with dual files (see the openUTM manual “Generating Applications”), the KC_USLOG call acts on both files.

Period of validity of the change / cluster

Successful processing of the call means that UTM has successfully switched to the next file generation. UTM writes all LPUT messages generated after the switch to the new log file. After switching, UTM also writes the LPUT messages to the new USLOG file generation(s) until you again switch to the following file generation.

The following applies in UTM cluster applications (Unix, Linux and Windows systems):
The call applies globally to the cluster, i.e. the current user log file is closed and a new user log file is opened at all currently running node applications.

KDCLOG ("KDCLOG - Change the user log file")

Data to be supplied

Function of the call	Data to be entered in the
	parameter area 1	identification area	selection area	data area
Switch the user log file over to the next file generation of the FGG	subopcode1: KC_SWITCH data_lth: 0	——	——	——

¹ The operation code KC_USLOG must be specified in the parameter area.

Parameter settings
Parameter area
Field name	Content
version	KC_ADMI_VERSION_1
retcode	KC_RC_NIL
version_data	KC_VERSION_DATA_11
opcode	KC_USLOG
subopcode1	KC_SWITCH
id_lth	0
select_lth	0
data_lth	0
Identification area
—
Selection area
—
Data area
—

KDCADMI call

KDCADMI (&parameter_area, NULL, NULL, NULL)

Data returned by UTM
Parameter area
Field name	Content
retcode	Return codes

retcode 

UTM writes the return codes for the call to the retcode field. In addition to the return codes listed in section "Return codes", the following codes may also occur:

Main code = KC_MC_REJECTED_CURR

The call cannot be processed at the present time.

Subcode:

KC_SC_LWRT_IN_PROGRESS

USLOG cannot be switched to the next file generation at the present time as UTM is currently writing data to the USLOG.

KC_SC_INVDEF_RUNNING

Only in UTM cluster applications:
An inverse KDCDEF is currently running, i.e. the job cannot be processed at present.

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcode:

KC_SC_FILE_ERROR

It is not possible to switch USLOG to the next file generation due to a DMS error.

KC_SC_NO_GLOB_CHANG_POSSIBLE

Only in UTM cluster applications:
No global administration is possible since the generation of the node applications is not consistent at present.

Maincode = KC_MC_RECBUF_FULL

Subcode:

KC_SC_NO_INFO

The buffer containing the restart information is full (see openUTM manual “Generating Applications”, KDCDEF control statement MAX, parameter RECBUF).