Messages K049 - K070

K049

Error &RCCC2 during application startup

UTM issues message K049 whenever the start of a UTM task is aborted due to an error, and the error code &RCCC2 shows the cause of the error.
The table below lists the possible error codes together with error causes and possible error recovery actions.

Start error codes

Code	Error cause	Response
2	There is not enough space available for the ROOTDATA area.	Check UTM generation and system configuration
3	The ROOTDATA area is not allocated or the string ‚ROOTDATA‘ is not available.	Reconcile openUTM versions
4	KDCROOT and the UTM system modules are of different versions.	Reconcile openUTM versions
5	Application cannot be signed on to Name Manager.	System error; please write PR and notify Software Support
6	The start of a follow-up task is aborted due to abortion of the start of the first task.	See error code of 1st task
7	The user‘s message module is not consistent with the message module of the UTM system code (e.g. incorrect number of inserts).	Correct message module and link UTM application again
8 *)	An attempt has been made to start UTM tasks both in dialog and in batch mode.	Start follow-up tasks in the same mode as the 1st task
9 *)	Insufficient space for the fixed section of KAA or for the KDCA-FCB.	System error; please write PR and notify Software Support
10	The request of a UTM task for 4K of class 6 memory has been rejected.	Check   BS2000 generation and memory requirements of the UTM application
11	Error at first OPEN call for the KDCA file of KDCFILE, possibly due to incorrect FILEBASE name specification in start parameters. Possible cause in UTM cluster applications: An online import is running for the node that is to be started.	See DMS error code
12	DMS error when reading first KAA page from the KDCA file.	See DMS error code
13	DMS error when reading first or last check page of KDCA file; the file cannot be used.	Make copy or regenerate with KDCDEF
14	The openUTM version in the KAA (KDC Application Area) which is read from the KDCFILE does not match the version of the UTM system code. The error can occur if you attempt to run two UTM applications having the same name in different openUTM versions in parallel.	Change name of an application (MAX APPLINAME=...)
15	KDCDEF and UTM code inconsistent with respect to KAA structure.	Regenerate with correct KDCDEF
16	KDCDEF and UTM system modules are of different versions.	Reconcile versions
17	Before the start KDCFILE was processed by KDCUPD, which terminated abnormally	Make KDCFILE consistent by means of either KDCUPD or KDCDEF
18	The KDCFILE in a follow-up task does not have the same generation time as the first task.	Start follow-up task with same KDCFILE file as first task
20	The memory pool for KAA cannot be reserved in class 5 memory  by the first task of the UTM application due to insufficient address space.	Check attributes of the BS2000 user name, e.g. ADDRESS-SPACE-LIMIT, and the MPOOL statement
21	A follow-up task of a UTM application is unable to link up with the KAA memory pool due to insufficient address space.	As for 20
22	DMS error when reading an NSR page in KAA.	See DMS error code
23	A KAA NSR page has been destroyed, the KDCA file can no longer be used.	Regenerate with KDCDEF
24	DMS error when reading an SR page in KAA.	See DMS error code
25	A KAA SR page has been destroyed, the KDCA file can no longer be used.	Regenerate with KDCDEF
26	At least one program for a generated event function is missing or an event-driven service is missing; i.e. the program is neither linked nor can it be loaded	Transfer program to the library specified at UTM generation and relink if necessary
27	KCSBKAA returned a bad return code. Error during initialization of the SYSLOG data in the KAA	Write problem report
28	During a (follow-up) start of the UTM application an inconsistency in the database generation between KDCFILE and ROOT was detected. The error occurs when KDCFILE and ROOT source are incompatible. UTM rejects this in order to avoid consequent errors.	Generate KDCFILE and ROOT with the same start parameters
29	The administration program unit (KDCADM) is missing or TAC KDCSHUT is not generated.	Add the KDCADM program to the UTM generation and add to the UTM application Generate TAC KDCSHUT
30	The request from a UTM task for a contiguous  area for the task-specific UTM tables (= KTA)  in class 5 memory has been rejected	Check attributes of the BS2000 user name, e.g. ADDRESS-SPACE-LIMIT, and memory requirements; reduce KTA by changing KDCDEF operands (e.g. check MAX TRACEREC=)
31	An attempt has been made to start more tasks than have been generated or set via administration..	User error
32	Bad return code from KCSBKTA (KCSSLOG may not have been able to initialize the SYSLOG data in the KTA).	Write problem report
33	UTM refuses to start more tasks for the UTM application because the latter has already terminated (normal or abnormal termination).	Usual action
34	The KDCFILE in a follow-up task does not have the same KAA size as the first task.	Start follow-up task with same KDCFILE file as first task
35	While dynamically loading the application program, UTM detects that the UTM application is being aborted.	Usual action
36	Error in Name Manager call for a follow-up task of an UTM application.	System error; please notify Software Support
37	Number of tasks to be started insufficient for PGWT processing or for a UTM cluster application	Start at least 2 tasks
38 *)	The task has already signed on to the Name Manager but with invalid KAA or KTA address.  This error occurs if the application start terminated with errors (xx) and the application program is subsequently restarted with the same task.  UTM terminates the task abnormally due to a suspected loop in the start procedure.	Check start procedure
39	When dynamically loading the application program, UTM detected that the UTM generation has been illegally changed.	Check start procedure and UTM generation
40	Number of entries in the program, load module or message module tables in ROOT and in the KDCFILE do not match (see K072 message)	Generate KDCFILE and ROOT with the same start parameters
41	A program or load module attribute in ROOT and in the KDCFILE do not match (see K073 message).	Generate KDCFILE and ROOT with the same start parameters
42 *)	The task has failed to create a slot for the taskservice table due to insufficient address space.  The slot should be created in a memory pool in the class 5 memory.	Check attributes of the BS2000 user name, e.g. ADDRESS-SPACE-LIMIT, and memory requirements of the UTM application
43 *)	ROOT and KDCFILE do not match with regard to the sequence of the user message modules.	Generate KDCFILE and ROOT with the same start parameters
44	The generations of KDCFILE and ROOT do not match with regard to the maximum length of the messages to/from clients. (KDCDEF statement MAX TRMSGLTH)	Generate KDCFILE and ROOT with the same start parameters
45	Error in KCSLKLC when setting a TAC class lock	Increase parameter MAX RESWAIT= (...,time2)
46 **)	UTM cluster application: A follow-up task was started with different cluster filebase specifications from the first task.	Start first task and follow-up task with same start parameters
47	The generations of KDCFILE and ROOT do not match with respect to the use of BLS.	Generate KDCFILE and ROOT with the same start parameters
48	Error while initializing buffer management in start case 1 or 2.	Increase the virtual address space. If this does not help, write problem report.
49 *)	The version number of the phase started in a follow-up task is different to that of the phase of the first task.	Supply phase of first task.
50	The first UTM task is trying to set up the cache memory pool, or a follow-up task is trying to link up to it. This is not possible due to insufficient address space. The memory pool should be created in the class 5 memory.	Check attributes of the BS2000 user name, e.g. ADDRESS-SPACE-LIMIT, and memory requirements of the UTM application
51	The file is not a KDCDEF file; for file name see K082 message (possible cause: KDCDEF from older version)	Supply or generate correct file
52	The file has been inadvertently replaced by another KDCFILE file, e.g. pool file instead of KDCB file; for file name see K082 message.	As for 51
53	The file does not match the KDCA file (e.g. different KDCDEF time); for file name see K082 message; for details on the error cause see the log in SYSOUT	As for 51
54	The consistency check shows that the file has been destroyed. Possibly a version mix. For file name see K083 message	As for 51 Check versions
55	DMS error with KDCA/KDCB file	See DMS error code
56	DMS error with page pool file
57	DMS error with restart file
58	Error in conjunction with the SYSLOG file to be made available by the user. Possible causes: Neither the link name SYSLOG nor a file generation group with the name basename.SLOG exists. Message K043 is additionally output. Size monitoring was generated (MAX SYSLOG-SIZE), but the SYSLOG made available is not a file generation group.	Check start procedure, SYSLOG file and UTM generation
59	Error when opening SYSLOG file	See DMS error code
60	Error during sign-on of the UTM application or follow-up task to BCAM or socket. For exact error cases see BCAM info word in message K065 (default destination SYSLOG) or message K154 (default destination SYSLOG) for application name with T-PROT=SOCKET. User error or system error.	Evaluate K065 or K154 in the SYSLOG file; for contents of the BCAM word info, consult Systems Support
61 *)	When signing on to BCAM or socket, a continuation application task is informed that it is the first task; this error may occur if the UTM application was previously terminated by a BCAM command (e.g. BCLOSE) and a task of that UTM application was not able to terminate, e.g. because it was processing a long transaction or was waiting for the database to be loaded (1st task of the UTM application).	Check if application tasks are still present in the system; load database  if necessary; then restart
62	As for 70.	As for 70.
63 *)	The number of TCB entries in the KAA is not the same as in ROOT.	Regenerate KDCFILE and/or ROOT
64	A request from the first task of the UTM application for a work area of 8K of memory made during warm start is rejected	Check system generation and UTM generation
65	As for 64 (length = task no. * 2K)	As for 64
69**)	KDCFILE and ROOT do not match regarding the OSI-TP generation. Possible causes: a new KDCFILE was created (new: with OSI-TP, old: without OSI-TP), the UTM application could not be relinked or the ROOT source could not be recompiled.	Regenerate, compile ROOT and link.
70	The first task of the UTM application has detected inconsistent data in KDCFILE during warm start.	System error; please write PR and notify Software Support, regenerate KDCFILE with KDCDEF
71**)	As for 70.	As for 70.
72	As for 70.	As for 70.
73 *)	As for 70.	As for 70.
74	Database problem with DB status check during restart; error cause KU. is output, see KCRCDC error codes	Correct database, restart the UTM application
75	As for 70.	As for 70.
76	As for 70.	As for 70.
77	A user ID for an open asynchronous service could not be found	Write PR.
79	A UTM task requests, but is not allocated class 6 memory.	Check attributes of the BS2000 user name, e.g. ADDRESS-SPACE-LIMIT,and memory requirements of the UTM application.
80	The first task of the UTM application has detected inconsistent data in KDCFILE when setting up the page pool map.	System error; please write PR and notify Software Support, regenerate KDCFILE with KDCDEF
81	As for 80.	As for 80.
82	Database problem when erasing DB status information; error cause KUxx is output, see KCRCDC codes.	Correct database, restart the UTM application
83	Database problem when rolling back a DB transaction; error cause KUxx is output, see KCRCDC codes.	Correct database, restart the UTM application
84	The task attempts to create a slot for an OSI service table. This attempt is unsuccessful due to a lack of memory space. The slot should be located in a memory pool in class 5 memory.	Check attributes of the BS2000 user name, e.g. ADDRESS-SPACE-LIMIT, and memory requirements of the UTM application.
85	The task has failed to create a slot for an open service due to insufficient address space. The slot should be located in a memory pool in class 5 memory.	Check attributes of the BS2000 user name, e.g. ADDRESS-SPACE-LIMIT, and memory requirements of the UTM application.
86	The 1st task of the UTM application has detected unallocated page pool pages in the cache (during warm start)	System error; please write PR and notify Software Support
89 *)	Error during name manager call for the UTM application’s first task	System error; please write PR and notify Software Support
90	Error when starting an open distributed asynchronous service	System error; please write PR and notify Software Support
91	Error when starting XAP-TP. A full description of the error can be found under message K124.	System error; please write PR and notify Software Support
92	No free NODE table was found during a restart for OSI-TP with XAP-TP.	System error; please write PR and notify Software Support
93	A user ID for a transaction which has not yet terminated was found during a restart for OSI-TP with XAP-TP.	System error; please write PR and notify Software Support
94	An inconsistent NODE table was found during a restart for OSI-TP with XAP-TP.	System error; please write PR and notify Software Support
95 **)	DMS error while writing a UTM cluster file (start case 1)	See DMS error code
96 **)	A UTM cluster file does not correspond to the cluster configuration file, e.g. different generation time. File name, see K082 message. For details on the cause of the error see the log message in stdout .	Use the correct UTM cluster file or regenerate the UTM cluster application.
97 **)	DMS error while writing a cluster file (operation code CL_FIRST_NODE)	See DMS error code
98 **)	The KDCFILE does not correspond to the cluster configuration file, e.g. different generation time. File name, see K082 message. For details on the cause of the error see the log message in stdout .	Use the correct KDCFILE or regenerate the KDCFILE.
99	Database problem  when starting via IUTMDB: Database system not available.	Check generated database systems
100	An inconsistency was detected between KDCFILE and ROOT while starting the UTM application in the KB length.	Create KDCFILE and ROOT with the same generation parameters
101	An inconsistency was detected between KDCFILE and ROOT while starting a follow-up task in the KB length.	Create KDCFILE and ROOT with the same generation parameters
102 *)	An inconsistency was detected between KDCFILE and ROOT while restarting the application program in the KB length.	Create KDCFILE and ROOT with the same generation parameters
103	An inconsistency was detected between KDCFILE and ROOT while starting the UTM application in the NB length.	Create KDCFILE and ROOT with the same generation parameters.
104	An inconsistency was detected between KDCFILE and ROOT while starting a follow-up task in the NB length.	Create KDCFILE and ROOT with the same generation parameters.
105  *)	An inconsistency was detected between KDCFILE and ROOT while reloading the application program in the NB length.	Create KDCFILE and ROOT with the same generation parameters.
106  *)	An inconsistency was detected between KDCFILE and ROOT while starting the UTM application regarding the use of the SQL features.	Create KDCFILE and ROOT with the same generation parameters.
107  *)	An inconsistency was detected between KDCFILE and ROOT while starting a follow-up task regarding the use of the SQL features.	Create KDCFILE and ROOT with the same generation parameters.
108  *)	An inconsistency was detected between KDCFILE and ROOT while reloading the application program regarding the use of the SQL features.	Create KDCFILE and ROOT with the same generation parameters.
109	An inconsistency was detected between KDCFILE and ROOT while starting the UTM application in the number of databases.	Create KDCFILE and ROOT with the same generation parameters.
110	An inconsistency was detected between KDCFILE and ROOT while starting a follow-up task in the number of databases.	Create KDCFILE and ROOT with the same generation parameters.
111  *)	An inconsistency was detected between KDCFILE and ROOT while reloading the application program in the number of databases.	Create KDCFILE and ROOT with the same generation parameters.
112	The first task in the UTM application (start case 1) detected an inconsistency with respect to the database types (only possible in the case of UTM-S applications and a subsequent start).	Create KDCFILE and ROOT with the same generation parameters.
113  **)	When a follow-up task was started, an inconsistency with respect to the database types was detected (only possible in the case of UTM-S applications and a subsequent start).	Create KDCFILE and ROOT with the same generation parameters.
115	An inconsistency was detected between KDCFILE and ROOT in the type of database or the database entries while starting the UTM application .	Create KDCFILE and ROOT with the same generation parameters.
116	An inconsistency was detected between KDCFILE and ROOT in the type of database or the database entries while starting a follow-up task .	Create KDCFILE and ROOT with the same generation parameters.
117  *)	An inconsistency was detected between KDCFILE and ROOT in the type of database or the database entries while reloading the application program.	Create KDCFILE and ROOT with the same generation parameters.
118 **)	UTM cluster application: Error reading filebase name of KDCFILE from the cluster configuration file Possible causes: memory bottleneck error accessing cluster file invalid cluster file own node not found For more details, see message K043 and K190	See message K043 or K190; correct start parameters or UTM generation if necessary
119 **)	UTM cluster application: The KDCFILE was generated as a UTM cluster application but no CLUSTER-FILEBASE start parameter was specified.	Correct start parameters
120 **)	UTM cluster application: The KDCFILE was not generated as a UTM cluster application but a CLUSTER-FILEBASE start parameter was specified.	Correct start parameters
122 **)	UTM cluster application: Error editing the cluster configuration file for initialization of the KAA	See message K043 and/or K190
123 **)	UTM cluster application: Error registering node	See message K043 and/or K190
125 **)	UTM cluster application: The sequence of node names in the KDCFILE is different from that in the cluster configuration file.	Correct the UTM generation; Regenerate the KDCFILE and, if necessary, the UTM cluster files
127 **)	UTM cluster application: Error opening cluster user file on start of first process in application (start case 1)	See message K043 and/or K190
128 **)	UTM cluster application: Error opening cluster user file on start of a follow-up process in application (start case 2)	See message K043 and/or K190
130 **)	UTM cluster application: Error requesting start lock for serialization by KCSCONS (start case 1)	See message K043 and K190
131 **)	UTM cluster application: Error opening administration journal files on start of a follow-up process in application (start case 2)	See message K043 and K190
132 **)	UTM cluster application: Error opening cluster administration journal files when reloading the application program after a program replacement (start case 3)	See message K043/K190
133 **)	UTM cluster application: Error creating administration journal files on start of first process in application (start case 1)	See message K043/K190
134 **)	UTM cluster application: Error writing online copy on start of first process in application (start case 1)	See message K043 and/or K190
135 **)	UTM cluster application: Error processing online copy on start of first process in application (start case 1)	See message K043/K190 and/or K174
136 **)	UTM cluster application: Error editing cluster user file on start of first process in application (start case 1)	See message K043 and/or K190
137 **)	UTM cluster application: Calling KCCCTRL with operation code REGISTER_NODE returns an unknown return code.	System error, please write problem report and inform Software Support.
138 **)	UTM cluster application: Calling KCCJCTL with operation code WRITE_JOURNAL_PI returns an incorrect return code.	System error, please write problem report and inform Software Support.
139 **)	UTM cluster application: No lock was requested for start serialization.	System error, please write problem report and inform Software Support.
140 **)	UTM cluster application: Error concluding registration of node at cluster	See message K043 or K190
141 **)	UTM cluster application: Calling KCCJCTL with operation code JFCT_SET_KAA_INFO returned an incorrect return code.	System error, please write problem report and inform Software Support.
142 **)	UTM cluster application: Calling KCCJCTL with operation code JFCT_GET_KAA_INFO returned an incorrect return code.	System error, please write problem report and inform Software Support.
143 **)	UTM cluster application: Error opening administration journal files on start of first process in application (start case 1)	See message K043 and K190
144 **)	UTM cluster application: Error processing administration journal	System error, please write problem report and inform Software Support.
145 **)	UTM cluster application: Calling KCCJCTL with operation code JFCT_SET_KAA_INFO returned an incorrect return code.	System error, please write problem report and inform Software Support.
146 **)	UTM cluster application: The runtime configuration of the node application that is to be started does not match the runtime configuration of the running node applications.	See message K174
147 **)	UTM cluster application: Global administration actions should be processed in the warm start. However, the administration journal files cannot be opened.	Check whether the administration journal files exist, see message K043/K190
148 **)	UTM cluster application: Global administration actions should be processed in the warm start. Internal error when reading journal files.	System error, please write problem report and inform Software Support.
149 **)	UTM cluster application: Internal error when cleaning up node-specific information in the journal files.	System error, please write problem report and inform Software Support.
150 **)	UTM cluster application: Error opening administration journal files on start of first process in application (start case 1)	See message K043 and K190
151 **)	UTM cluster application: Error requesting lock for start serialization of nodes (during warm start).	See message K043 or K190
152 **)	UTM cluster application: Error requesting lock for start serialization of nodes	See message K043 or K190
153 **)	UTM cluster application: Cluster page pool control file defective.	See message K190
154 **)	UTM cluster application: Error opening the LOCK file on the start of a follow-up process in application (start case 2)	See message K043
155 **)	UTM cluster application: Error opening the LOCK file on the start of the first process in application (start case 1)	See message K043
156 **)	UTM cluster application: Error opening the LOCK file on the start of a follow-up process in application (start case 2)	See message K043
157 **)	UTM cluster application: Error while checking the cluster GSSB file	See message K043 or K190
158 **)	UTM cluster application: Error while checking the cluster ULS file	See message K043 or K190
161 **)	UTM cluster application: Error while releasing the ULS locks in the cluster ULS file	See message K190
162 **)	UTM cluster application: Error while releasing the GSSB locks in the cluster GSSB file	See message K190
164 **)	UTM cluster application: Error while opening the LOCK file on warm start	See message K043
165 **)	UTM cluster application: On the warm start of a node application, it was not possible to lock the cluster lock file in the generated time.	Repeat the UTM application start operation
166 **)	UTM cluster application: Internal error when rolling back a transaction in PTC state during node recovery.	System error, please write problem report and inform Software Support.
167 **)	UTM cluster application: Internal error when outputting existing transactions in PTC state during node recovery.	System error, please write problem report and inform Software Support.
168 **)	As for 167.	As for 167.
169 **)	UTM cluster application: An attempt was made to perform a node recovery for a node application that terminated normally.	Check whether the incorrect node was specified in the start parameter.
170 **)	UTM cluster application: Cluster page pool and KDCFILE generated with different BLKSIZE.	Regenerate all the UTM cluster files.
171 **)	UTM cluster application: A node recovery was started in a dialog.	Start node recovery in batch operation.
172 **)	UTM cluster application: Error while locking a cluster user file when starting the first process in application (start case 1)	See messages K043 and K190
173 *)	The UTM application is generated with BCAMAPPL with T‑PROT=(SOCKET,...,SECURE), but no job-variable with the filebase name is catalogued.	Catalogue the job-variable or change the configuration of the UTM application

The codes marked with *) only appear on BS2000 systems and the codes marked with **) only appear on Unix, Linux and Windows systems.

K050

Successful warm start for application &APPL under UTM &VERS / &OST1

K051

Successful cold start for application &APPL under UTM &VERS / &OST1

The messages K050 and K051 are output after the successful startup of the application. The insert &VERS contains the openUTM version, &OST1 the type of operating system and &BMD1 the bit mode (32/64).

Both messages have the additional inserts &AMOD, &TERM, &ATYP and &FNOD which are not contained in the default message text; these have the following meanings:

&AMOD contains the application mode of the application:
"S" in the case of UTM-S
"F" in the case of UTM-F

&TERM contains the termination type entered in the KDCFILE at application startup; the following values are possible:
"C": The KDCFILE was created anew with KDCDEF.
"U": The KDCFILE was updated with KDCUPD.
"N": The last application run was terminated normally.
"A": The last application run was terminated abnormally.

&ATYP contains:
"C" in the case of a UTM cluster application
"S" in the case of a standalone application

&FNOD contains:
" " (blank) in the case of a standalone application
"Y" on the startup of the first node application in a UTM cluster application
"N" on the startup of each subsequent node application in a UTM cluster application

K052

Startup completed - task &TASK activated for application &APPL,  System-Task: &STSK

&STSK specifies whether (Y) or not (N) the task is a system task.

K053

New user log file created; old user log file contains &CNTR records.

K054

Copies of the user log files are not identical.

K055

Asynchronous service &ATAC1 terminated by UTM; KCRCCC=&RCCC; KCRCDC=&RCDC; USER=&USER; LTERM=&LTRM

K056

Task &TASK terminated

K057

Application run terminated

K058

Abnormal termination of task &TASK

K059

Abnormal termination of application run

K060

Application run aborted; reason = &TRMA

UTM creates a memory dump whenever a UTM application is aborted or a dump requested. Such a dump is produced for eachtaskof the application (see chapter "The UTM dump").

The insert &TRMA describes the reason (TRMA reason) for the termination. You will find this six-character code in the file name of the dump file (see chapter "The UTM dump").

The TRMA reasons of the individual tasks in a UTM application are generally not identical. The TRMA reason of the task which is the first to initiate the application termination identifies the reason for the termination of the application. The TRMA reasons of the follow-up tasks, so-called continuation dumps, are of subsidiary importance.

A list of the termination codes, an explanation, and, if required, recommendations for changing the application's configuration can be found in section "UTM dump error codes".

For a more detailed diagnosis, please also see the most recent K190 messages.

K061

Dump file &FNAM created

K062

Dump file could not be created.

K063	Formatting error &RCF1A/&RCF2A for format &FMTN, asynchronous message for LTERM = &LTRM

K064

Message with length &IMSLTH discarded: &PTRM/&PRNM/&BCAP/&LTRM &DEVC &FIL1A &FIL2A &FIL3 &VTRC &CBRC &IMSG2 &REA1

Meaning:

1. An invalid or unexpected announcement was received at the work bourse. In this event, insert &REA1 has a value of X‘05‘ and insert &IMSG2 contains the announcement received.

2. A message from an LTERM partner has been received which is logically inconsistent for UTM. One of the following reasons apply:
   The message does not comply with the strict dialog, or

    VTSU-B reports an error when processing a physical message from a terminal or a printer. The message contains as inserts a 4-bytes return code which VTSU passed to UTM and the return code which VTSU passed in the VTSUCB.

   Or

   a message with an invalid protocol was received from a UPIC or socket client.

3. A message which does not contain a valid transmission header was received from an LU6.1 partner.

For diagnostic purposes, the first 32 characters of the message are output. For an invalid USP protocol the first 12 bytes of the USP protocol are output filled with binary zero. 

Note: If the message length is less than 32, parts of an earlier message may also be output. These characters can partly be remnants of an earlier message, with length < 32 or K-key.

The standard record output to SYSLOG has the following structure:

Inserts	Meaning
&IMSLTH	Total length of input message
&DEVC	Terminal or printer type; the codes can be taken from the macro DCSTA with TYPE=TCHAR.
&FIL1A	Status of the application; possible values X'02' = start phase X'03' = normal run X'04' = shut warn X‘05‘ = shut grace X'07' = fast shut X‘08‘ = term application
&FIL2A	Status of the client or printer: X'00' = Connection clearing down X'01' = Connection not established X'02' = UTM waiting for the completion of the a connection set up X'03' = Connection established, user not yet signed on X'04' = UTM waiting for a password to be entered X'05' = UTM waiting for a password to be entered X'06' = UTM waiting for a new password to be entered X'07' = UTM waiting for an ID card to be inserted X'08' = User accepted X'09' = 2nd part of the sign-on service X'0A' = for LTERM with USAGE=O: Printer connected, otherwise user logged on
&FIL3	Status of the physical terminal or printer (2 bytes), serves as a diagnostic aid in the event of errors. The meaning of the individual bits may be found below.
&VTRC	VTSU return code
&CBRC	Return code in the VTSUCB
&IMSG2	The first 32 characters of the message (in the case of stations the first 8 characters contain the header of the station log)
&REA1	Reason for K064 message:X'01' = Bad VTSU return code X'02' = invalid function key X'03' = no positive print acknowledgment X'04' = bad return code from ISLP X'05' = inconsistent input message X'06' = LU6.1: The announcement length is shorter than the DCF in the transmission Header X'07' = Input message for disconnected MUX connection X'08' = inconsistent message from an LU6.1 partner X'09' = UPIC input message with invalid protocol X'0A' = inconsistent physical or logical acknowledgment X'0B' = input message from a socket USP application generated as an output partner X'0C' = unexpected GO signal received for a UPIC or socket connection X'0D' = inconsistent message from the SSL proxy X‘0E‘ = message with invalid HTTP protocol received X‘0F‘ = message with invalid USP protocol received

Meaning of the insert &FIL3:

byte A

byte B

A1

A2

A3

..

..

..

..

..

B1

B2

..

..

..

..

..

..

The individual bits have the following meaning:

Bit	Value	Meaning
A1	1	Last output was unformatted
	0	Last output was formatted
A2	1	Waiting for transport or logical print acknowledgement
A3	1	Last output was in extended line mod
B1	1	Partner is a station (terminal)
	0	Partner is an application
B2	1	Partner is a dialog partner (client)
	0	Partner is a Printer

K065

Net message: &PTRM/&PRNM/&BCAP/&LTRM &FIL1B &FIL2B

The inserts &FIL1B and &FIL2B have the following meaning:

Inserts	Meaning
&FIL1B	BCAM call or BCAM, UTM or RSO announcement type
&FIL2B	BCAM info word, (see table "Values of the BCAM info word"), UTM announcement code or RSO return codecode

&FIL1B is output in printable form. The values X’E0’, X’E2’and X’F0’ to X’FF’ indicate a UTM (timer) announcement. The values are explained in the following table.

The values marked with *) only appear on BS2000 systems and the values marked with **) only on Unix, Linux and Windows systems.

&FIL1B	Meaning	Meaning of &FIL2B
X’01’ - X’4C’	BCAM call or BCAM announcement 1	BCAM, infoword (printable)
X’56’ *)	RSO announcement	Asynchronous RSO return code (printable, see K150), the value and meaning can be found in the description of message K150 or obtained from System Support.
X’E0’	Idle timeout for an LU6.1 session (see KDCDEF statement SESCHA, parameter IDLETIME)	no meaning
X’E2’	Timeout on reception of message fragments at a socket connection since the message was not fully received within the permitted period of 10 minutes (internal value)	no meaning
X’F0’	UTM anno	If the first byte of &FIL2B is X’FD’, then a shutdown announcement from MSCF was received and the application terminates.
X’F1’ - X’FA’	UTM anno	no meaning
X’FB’	UTM anno: Timeout waiting for an acknowledgment from a printer or TS application after sending a queued message (see KDCDEF statement MAX, parameter LOGACKWAIT)	no meaning
X’FC’ - X’FE’	UTM anno	no meaning
X’FF’	UTM anno: timeout	The first byte in &FIL2B specifies the cause of the timeout:
		X’21’	Expiry of the timer which monitors the establishment of an LU6.1 session. See KDCDEF statement UTMD, parameter CONCTIME=(time1,....).
		X’22’	Expiry of the timer which monitors the reception of the acknowledgment for a queued message sent via an LU6.1 session. See KDCDEF statement UTMD, parameter CONCTIME=(....,time2).
		X’30’	Expiry of the PEND-KP timer. See KDCDEF statement MAX, parameter TERMWAIT or PGWTTIME.
		X’40’ to X’43’	Expiry of the PTERM idle timer. See KDCDEF statement PTERM or TPOOL, parameter IDLETIME or KDCDEF statement MAX, parameter PGWTTIME.

¹The value and meaning of the BCAM call and announcement can be obtained from the BCAM diagnostic documentation or System Support

Values of the BCAM info word

The table below the codes of the BCAM info word, their meaning and possible actions to recover errors.

There are two variants of BCAM info word. In the first column of the table, you find the values of the BCAM info word (arranged in ascending order in byte 4) that are returned as the return code with a BCAM call (&FIL1B < X'40'). In the second column you find the values of the BCAM info word (arranged in ascending order in byte 1) that are returned in a BCAM anno (&FIL1B >= X'40').

Value (Call)	Value (Anno)	Meaning	Actions
00820004	04000000	BCAM not active	BCEND-DCSTART
0001xx08	08000000	Illegal structure of parameter list:	Inform software maintenance staff
00010014		Letter too long
00010108		CONNB not specified
00010208		NAME incorrect
00010308		APID not specified
00010408		DID not specified
00010508		NAME not specified
00010608		PNAME not specified
00010708		CID not specified
00010808		LETAR not specified
00010908		TELAR not specified
00010A08		NBUFS exceeds maximum
00010B08		distribution code length=0
00010C08		distribution code length exceeds maximum
00010D08		NGBS not specified
00010E08		GROB not specified
00010F08		distribution code not specified
00011008		distribution bourse ID not specified
00011108		APREF not specified
00011208		BLTH not specified
00011308		user buffer length = 0
00011408		TAKAR not specified
00011508		RTACK incorrect
00011608		telegram length = 0
00011708		LANNO incorrect
00011808		NBUFS not specified
00011908		EVENT incorrect
00011A08		RCCOD incorrect
00011B08		Number of routes outside permitted limit
00011C08		OWNPN incorrect
0080000C	0C00000	Timeout	Check partner
00400010	10000000	No message received	Create UTM BCAM trace
00010014	14000000	Connection message too long (letter too long)	Check structure of the connection message
00010018	18000000	DISTAB error	Inform software maintenance staff
0480xx1C	1C040000	Resource bottleneck memory for BCAM:
0480011C		Data buffer	Repeat call/enlarge memory with BCMOD ask software maintenance staff to examine data flow problems
0480021C		Reference	If error recurs, inform software maintenance staff
0480031C		ACONCB or REQCB
0480041C		APPCB
0480051C		DISTAB
0480061C		Name Manager
0480071C		Interface flow control
0480081C		Bourse
0480091C		ENACB
04800A1C		ADDRCB-P
04800B1C		CID
0840011C	1C080000	Warning: BCAM will be terminated
0C40021C	1C0C0000	BCAM will be terminated
1082001C	1C100000	Maximum number of predefined applications has been reached	/BCMOD-MAXNPA=
1440001C	1C140000	Waiting for GO signal
04010020	20000400	Application not yet known to BCAM	Open application with BCAM
08010020	20000800	Application known to BCAM under another task	Repeat call with "correct" task
0C010020	20000C00	Application signed on to BCAM exclusively through another task
10010020	20001000	Application already signed on with BCAM under this task
14400220	20001400	Forced closure of the application	Reopen application
18400120	20001800	Forced closure of the application with warning	Reopen application
1C010020	20001C00	Application is not active	/BCACT application name
20010010	20002000	Application may not actively set up connection
24820020	20002400	No further connections are allowed for this application	Increase number of connections with the BCMOD command
28820020	20002800	No non-predefined application allowed for this task	Increase with BCMOD MAXNPT
2C010020	20002C00	Application - password error	Correct password
30010020	20003000	Call already issued by another task
34010020	20003400	Application may not work with high priority	Repeat call with lower priority
04010024	24000004	Partner has no connection	Set up connection
08010024	24000008	Partner already has a connection
0C010024	2400000C	The application has issued another connection setup request to a partner, but the partner has not yet responded
10400024	24000010	Partner is already attempting to set up connection	Forget own connection request and accept partner‘s connection request
14010024	24000014	Connection request did not exist or time elapsed	Accept connection request within the allotted time
18010024	24000018	Partner not known	Generate partner correctly
1C820024	2400001C	Partner processor not known	Check generation of BCIN partner processor
1C820124	2400001C	Partner processor not active	/BCACT
1C820224	2400001C	ROUTE not known	Check generation
1C820324	2400001C	ROUTE not active	/BCACT
	2400002C	Partner does not accept the connection request	Generate DCM.BCAM.CON trace
30010024	24000030	Application may not actively set up a connection
	24000034	The partner has lost the connection and will set it up again immediately	Wait for connection setup
	24000038	Connection cleared down by the partner
	2400003C	Forced closure of the application by the operator
4001xx24	24000040	Inconsistent connection parameters:	Correct connection parameters
40010124		TELAR requested
40010224		telegrams not permitted
40010324		predefined connection: call requires GROS=F or THRU=N
40010424		user data not permitted
00800028	28000000	Attempt input/output later	No acknowledgment for connection log: Look for cause in destination processor, Modify UTM parameters BRETRYNR in KDCDEF
0040002C	2C000000	Message rejected after timeout	User problem / use more tasks with UTM
0020xx30	30000000	BCAM error	Take DUMP, create ASTRID TOTAL dump
	34000000	Inconsistent network address	Re-establish connection
00800038	38000000	Another input/output is currently running	Repeat call/ if error recurs again turn on DCM.BCAM.CON trace and make copy
0001003C	3C000000	Illegal call	Inform software maintenance staff
0001FFFF	3C000000	Illegal unit/function
0002FFFF	3C000000	Function not available
0003FFFF	3C000000	Illegal version
0004FFFF	3C000000	Incorrect parameter list

K066

Mandatory parameter FILEBASE not specified

K067

Error in interoperation with language connection module &MOD: error code = &ERCD1 &ERCD2; opcode = &OPCD2

The inserts of the message have the following meaning:

&MOD	Meaning
KDCCC	Connection module for C
KDCCCOB	Connection module for COBOL
KDCCASS	Connection module for ASSEMBLER
KDCCFOR1	Connection module for FORTRAN
KDCCILC	Connection module for ILCS
KDCCSPL	Connection module for SPL
UTMPLI1	Connection module for PL/I
UTMPAS	Connection module for Pascal

&OPCD2	Meaning
INITIALISE	Initialize the language environment
DEACTIVATE	Release the language environment
STXIT-HANDLING	STXIT handling via the language
S; XXXXXXXX	Start the program unit ' XXXXXXXX'
E; XXXXXXXX	Execute the end handling routine for the program unit ' XXXXXXXX'

The ERRORCODE is made up of 2 x 4 characters.

&ERCD1	Meaning and possible response
0000	Job has already been executed
0004	Job was not executed correctly Provide error documentation and send to Software Support
0008	Error in application program
00FF	The language connection module for a generated language is not linked when the application is started

The inserts in &ERCD2 supply additional information on errors that have occurred and are used for diagnostic purposes.The meaning can be found in the manuals for the relevant programming languages.

K068

Database connection module &DBCON version &DBV1 cannot interoperate with KDCDB macro version &DBV2

K069

Disconnection : &PTRM/&PRNM/&BCAP/&LTRM/&REA4/&REA6/&COTM

The insert &REA4 indicates who initiated the connection cleardown. The insert &REA6 contains the cause of the connection cleardown.

&REA4	Meaning
B	Transport system reports connection cleardown
L	Connection lost for socket connection
other	Connection was cleared down by UTM, for reason see &REA6

&REA6	Meaning
X'00'	Reason not specified
X'08'	Resource bottleneck
X'09'	Connection cleared down
X'0A'	Application SHUTDOWN
X'0D'	Negative return code from transport system, see associated K065 message.
X'1A' *)	Too many invalid sign-on attempts
X’2A’ *)	Connection interrupted after an unencrypted message was received from the terminal on an encrypted connection.
X'2F' *)	Closure of MUX session after the MUX transport connection had already been cleared down.
X'30' *)	Connection cleardown by KCSMUX
X'31'	Connection cleardown after KDCOFF
X'32'	Connection cleardown after SIGN OF
X'33'	Connection cleardown by the print administration
X'34'	Connection cleardown by the administration
X'35'	No messages for printer with PLEV > 0
X'36'	Page pool warning level 2 exceeded on receipt of an asynchronous DTP message.
X'37' *)	Connection cleardown after receipt of an incorrect status message from the terminal
X'38' *)	Bad return code from VTSU-B or unencrypted message received although permanent encryption was defined for the connection
X'39'	Invalid function key
X'3A'	Connection cleardown by DTP with session not yet established
X'3B'	Connection cleardown by UPIC
X'3C'	Connection cleardown after unsuccessful sign-on attempt
X'3D'	Connection cleardown after unsuccessful sign-on service
X'3E'	Connection cleardown after timeout
X'3F'	Message fragment received
X'40'	Negative transport or print acknowledgment
X'41'	Unexpected protocol element
X'42'	Inconsistent input message
X'43'	Connection cleardown through new connection setup request
X'44' *)	Connection cleared down after a negative acknowledgment from RSO.
X'47'	Connection cleared down because IDLE timer timed out.
X'49'	Socket - Connection cleared down because of invalid length of incoming message (negative or >32000)
X'4A'	Socket - Connection cleared down because of invalid version in the protocol header
X'4B'	Socket - Connection cleared down because of invalid type in the protocol header
X’4C'	Socket - Connection cleared down after an error occurred while writing the message in the message queue
X'4D'	Socket - Connection cleared down after timeout
X'4E'	Socket - Connection cleared down because of a length problem: The message generated is larger than the generated maximum length (see the MAX TRMSGLTH operand in the KDCDEF statement).
X’4F'	Socket - Connection cleared down because of unknown identifier in the protocol header
X'50'	Socket - Connection cleared down because of invalid version minor in the protocol header
X'51'	Socket - Connection cleared down because of invalid flag in the protocol header
X'52'	Socket - Connection cleared down because the maximum possible number of fragments was exceeded
X'53'	Socket - Connection cleared down because of an invalid message type FRAGMENT at the beginning of a message
X'54'	Socket - Connection cleared down because the last part of a fragment was missing.
X’56’ *)	Connection to RSO printer is shut down as the KDCS call FPUT/DPUT RP is not supported by the current RSO version.
X'57'	Cleardown of the connection to the client because insufficient processes are active to continue the service normally after timeout at the PGWT bourse.
X'59'	Connection cleared down by DTP while session established.
X’5A’	The socket connection was closed due to no longer supported USP protocol version 1.0 (minor version X'00') in the protocol header.
X'5C'	Inconsistency between the data length announced at the socket interface and the data length actually received.
X’5D’	A message fragment of size zero was received as the first fragment on a socket connection
X’5E’	HTTP protocol error
X’5F’	As the HTTP request did not contain the header field CONNECTION: KEEP-ALIVE,  the socket connection to the HTTP client was closed by the server
X’60’ *)	A connection to the SSL proxy was closed during connection setup
X’61’ *)	The connection request for an SSL connection is rejected because no further SSL connections can be managed.

The valus marked with *) only appear on BS2000 systems.

K070

USER / LSES inactive : &USER, &GLOBALSG

A value is only entered for the insert &GLOBALSG 'Cluster Global Sign' in UTM cluster applications. The insert can have the following values:

&GLOBALSG	Meaning
Y	Global sign-off at the cluster
N	Local sign-off at the node
T	The global sign-off at the cluster was not successful because the cluster user file could not be locked in the generated time.
F	The global sign-off at the cluster was not successful because the user was not found in the cluster user file.
S	The global sign-off at the cluster was not successful because the user was not signed on globally at the cluster.
O	The global sign-off at the cluster was not successful because the user was not signed on globally at the cluster at this node.
' '	Sign-off for an LU6.1 session user or a connection user.

The message is output when a user signs off. The message also possesses the following inserts:

Insert	Meaning
&COTM	Number of seconds since &USER signed on at this connection
&CPTM	Elapsed CPU time in msec in the user ID &USER if only one user was currently signed on under the user ID &USER. If multiple users have previously signed on under &USER at different connections then the value also contains their elapsed CPU time. The value is then reset to 0. If further users are still signed on under the user ID &USER then the value is 0.