The CONS_ENTRIES table

The table CONS_ENTRIES shows the history of the KDCFILE. It contains a maximum of 10 entries. The entries are sorted in descending order of the generation time, i.e. the most recent entry comes first. If 10 entries have not yet been created for the KDCFILE, the first entries in the table are blank.

Entries are written in the table when the following events occur:

• when a KDCDEF generation is executed

• when KDCUPD is called

• each time the UTM application is started

A table entry has the following format:

type	r1	r2	f1	i1	i2	i3	f2	yymmdd	hhmmss	tttt
4	1	1	2	1	1	1	1	6	6	4	Byte

type	’DEF ’ for KDCDEF run ’UPD ’ for KDCUPD run ’STRT’ for application start.
r1 and r2 designate the correction status of KDCDEF, KDCUPD and UTM system code (e.g. ’23’ for V7.0A23).
r1,r2	’nm’ two digits for the source correction character ’00’ space for the first release of a version.
f1, f2	Filler.
For type ’STRT’ and ’DEF’: i1,i2, i3 and ttt contain additional information.
For type = STRT:
i1	’C’ for UTM cold start, ’W’ for UTM warm start
i2	’P’ for production for type = STRT
i3	’B’ for batch process, ’D’ for dialog process
tttt	PID of the UTM process for type = STRT.
For type = DEF:
i2	’-’ when the KDCFILE was created successfully for type e= DEF ’W’ when the KDCFILE was created with errors.
yymmdd	Date (year, month, day)
hhmmss	Time (hours, minutes, seconds).