Messages K147 - K189

K147

Sign-on for &USRTYPE user &USER not successful.
&PTRM/&PRNM/&BCAP/&LTRM reason: U&REA7

&USRTYP contains the following values:

• CONNECTION at sign-on of the connection user ID of a connection to a UPIC client or transport system application

• CLIENT at sign-on of a genuine user ID via TS application, UPIC client or OSI TP partner.

The values in &REA7 have the following meanings:

&REA7	Meaning
U1	The specified USER does not exist.
U2	The specified USER is locked.
U3	Somebody has already signed on with this USER name.
U4	The “old” password specified is incorrect.
U5	The new password specified cannot be used.
U6	There is no card reader available.
U7	The card information is incorrect
U8	It is not possible to sign on at the moment: because of a resource bottleneck because the maximum number of users who can be signed on simultaneously has already been reached because a password could not be changed, since an inverse KDCDEF is currently running.
U10	The current LTERM partner is not authorized to continue the service.
U11	The password is no longer valid. The password must be changed by the administrator. When the user signs on using an OSI TP association, the password cannot be changed (nor can it in an application with grace sign-on).
U12	The new password does not fulfill the requirements
U13	The new password is too short.
U14	The password passed by KDCUPD does not fulfil the generated complexity requirements or is too short.
U15	A transaction restart is necessary for the specified user.
U16	The open service cannot be continued from this partner type.
U17	The administrator entered SHUT WARN; normal users can no longer sign on to the application (an administrator can still sign on).
U18	The encryption mechanism required for continuing the open service is not available on the connection
U19	The validity period of the password has expired. Because Grace Sign-On is generated, sign-on can be repeated by transferring a new password.
U22	The specified USER does not exist in the cluster user file.
U23	Someone else has already signed on to another node with this USER.
U24	It is currently not possible to sign on because the cluster user file could not be locked in the generated time (CLUSTER statement, FILE-LOCK-TIMER-SEC parameter, FILE-LOCK-RETRY parameter).
U25	It is not possible to sign on at this node application because the user has a service that is bound to another node application and may not be terminated.
U26	Sign-on rejected because the open service belonging to the user has a transaction in the PTC state but no service restart has been requested.

K149	Internal diagnostic information &DIA5 An event has occurred which is logged with diagnostic information. &DIA5 is the internal UTM diagnostic information.

K151

Run of inverse KDCDEF terminated. Return code: &IDEFRC &DMSE &FNAM

The insert &IDEFRC contains a 16-digit return code for the inverse KDCDEF. The return code comprises two 8-digit printable numbers.

The first 8 digits have the following meanings:

First 8 digits	Meaning
00000000	The inverse KDCDEF was terminated normally.
00000001	A file handling error occurred.
00000002	A memory bottleneck occurred.
00000003	No KDCDEF statements were generated.

Digits 9 - 16 are only relevant if the first 8 digits contain 00000001. In this event, digits 9 - 16 contain a more detailed description of the error which occurred.
In all other cases, digits 9 - 16 contain 00000000.

Digits 9 - 16	Meaning
00000001	Invalid name for an output file.
00000002	Output file could not be created.
00000003	Output file could not be opened.
00000004	Output file could not be written.

The insert &DMSE contains the printable DMS error code if an error occurs during file handling and digits 9 - 16 of the insert &IDEFRC contain one of the values 00000002, 00000003 or 00000004.

The insert &FNAM contains the name of the file for which the error occurred.

K152

Heuristic report: &COND &MTYPE &OSLPAP &USER &LTAC &AAIS &AAID

The inserts have the following meaning

&COND	Meaning
MIX	The server reported data inconsistency. This is not possible with an asynchronous message to a UTM application.
HAZ	Possible data inconsistency. Connection to OSI TP job receiver (subordinate) was lost after a PREPARE was sent and the OSI TP job submitter (superior) had not carried out a backup. The transaction is rolled back on the job submitter and a asynchronous message is sent again. The transaction is also rolled back in a UTM job receiver, or an asynchronous message is rejected (immediately after a restart), so that the data is consistent.

&MTYPE	Meaning
DIAL	A dialog message was sent.
ASYN	An asynchronous message was sent.

&OSLPAP:	Name of the partner application.
&USER:	Name of the user who issued the job.
&LTAC:	for an asynchronous message: LTAC name of the job for a dialog massage: TAC of the transaction for which inconsistency is possible
&AAIS:	Size of the atomic action identifier in bytes.
&AAID:	contains the encoded atomic action identifier (up to 64 bytes).

K154

Network message: &PTRM/&PRNM/&BCAP/&LTRM &TCPCL &TCPRC

The inserts of the message have the following meaning:

Insert	Meaning
&TCPCL	internal socket function or internal socket event
&TCPRC	Diagnostic Word

&TCPCL is output in printable form:

&TCPCL	Meaning
ATTACH	Create a socket
CONNECTION_REQ	Request the establishment of a connection
CONNECTION_RSP	Confirm the establishment of a connection
DISCONNECT_REQ	Clear connection
DATA_REQ	Send data
DATA_IND	Receive data
GET_HOST_BY_ADDR	Determine computer name of an IP address
GET_HOST_BY_NAME	Determine IP address of a Computer

The diagnostic word is 4 bytes long and are specified in hexadecimal. The values have the following meaning:

&TCPRC	Meaning	Cause / Response
00000008	Invalid parameter
00000014	Connection letter too long
00000028	The previous send action was not yet completed when the data was sent.	Normal response
00000030	Internal error	See WAIT41 in message K060
00000038	The previous send action was not yet completed when the connection was established/cleared	Normal response
0400001C	Resource bottleneck	Check UTM generation
04000020	Application is not signed on	Check UTM generation
04000024	Connection already cleared	Normal response
08000024	Connection already established	Normal response
10000024	UTM network connection not yet active	Normal response
1C080000	End of application through KDCSHUT utility with time specification	Normal response
1C0C0000	End of application through KDCSHUT utility without time specification	Normal response
24000004	Connection already cleared	Normal response
24000018	Negative response to request to establish connection	Normal response
24000038	Request to clear connection	Normal response
30000020	Error during sign-on
FF013008	Only spaces were passed when determining a host’s IP address	Check UTM generation
FF023008	It was not possible to determine the host’s IP address	Check UTM generation

K155

Your password is expired! - please enter password and new password

K156

UTM-UPIC encryption functionality &CRYP  available: &RSLT

K158

Inconsistent value for CPU time used: &CPUTEXT

The calculation of the CPU time used by the user resulted in an inconsistent value.

The message contains the following inserts:

Insert	Meaning
PTRM	Name of the current PTERM
PRNM	Name of the current processor
BCAP	Name of the current BCAM application
LTRM	Name of the current LTERM
USER	Name of the current user
CPUTEXT	NEGATIVE: A negative value was observed OVERFLOW: Too much time used by the user
CPUBEGIN	CPU time used at the beginning of the period monitored
CPUEND	CPU time used at the end of the period monitored
CPUUSED	CPU time used calculated for the period monitored
CPUCLNT	CPU time actually used by the current user
CPUREAS	Internal diagnostic value

K159

Password for User &USER changed

The password has been changed for the specified user. The message is sent every time the password is changed independently of how the password was changed (administrator, via SIGN CP, etc.)

The message possesses the following inserts:

Insert	Meaning
USER	Name of the user whose password was changed.
ENCPW	Modified password in encrypted form.

This message can be used to transfer modified user passwords to a standby application. To this end, the message destination MSGTAC or USER-DEST must be defined for this message in the private message module. The new user password can be set in encrypted form in the standby application by defining pw_encrypted='Y' via programmed administration KC_MODIFY_OBJECT, object type USER.

Notes:

• You should note that no UTM-D communication is permitted in the MSGTAC program unit. The modified password cannot therefore be sent directly from the MSGTAC program unit via a UTM-D connection to the standby application.

• If the application terminates during productive operation and password changes are made during this period then it is possible that the corresponding messages to the MSGTAC program will not be received but will instead be lost.

• UTM generates the new message for each type of password change and in particular if the password is modified in the standby application. You should make sure that the standby application does not transfer the password back to the productive application in order to avoid any ping-pong effect.

• You should note that UTM uses different encryption algorithms on different platforms. As a result, the function cannot be used on a cross-platform basis.

• The passwords should be generated with the same level of complexity in the involved applications since UTM does not check the complexity when entering the encrypted password.

K160

The &TACNTR. transaction of service &TCVG has been rolled back by &RBCAUSER (&RCCC/&RCDC); (pid: &PID)

The message has the following inserts:

Insert	Meaning
PTRM	Name of the current PTERM
PRNM	Name of the current processor
BCAP	Name of the current application
LTRM	Name of the current LTERM
USER	Name of the current user
TCVG	Name of the service TAC in which the transaction was rolled back
TAC	Name of the TAC in which the transaction was rolled back
TACNTR	Number of the rolled back transaction within the service
RBCAUSER	Initiator of the rollback. There are the following values for the initiator, User PEND RS: Rollback was triggered by a PEND RS in the program unit. System PEND RS: Rollback was triggered by a PEND RS initiated by UTM. User PGWT RB: Rollback by triggered by a PGWT RB in the program unit. System PGWT RB: Rollback was triggered by a PGWT RB initiated by UTM. User PEND ER: Rollback was triggered by a PEND ER/FR in the program unit. System PEND ER: Rollback was triggered by a PEND ER initiated by UTM. DBSTATUS OPEN: The rollback was triggered during the warm start due to an unsuccessful database status query. DBSTATUS ERROR: Error when querying the database status during node recovery. DB CONFIRM PTC: Error on XA database call CONFIRM PREPARE TO COMMIT STATE during node recovery. DB CATA VTV: Error on database call CANCEL TRANSACTION during node recovery. JOURNAL: The rollback was triggered during the warm start due to an incompletely written journal record.
RCCC	Value of the compatible KCRCCC return code
RCDC	Valid of the incompatible KCRCDC return code
PID	pid of the process

K161	Synchronous Periodic Write started for task&PID
K162	Long IO for task&PID: &IOPG pages, &IOMS milliseconds
K163	Long Periodic Write for task&PID: &IOPG pages, &IOMS milliseconds
K167	System files stdout and stderr successfully switched.

K169

action: &ACTION; node: &NNM1/&HST1/&STATE; node monitoring this node: &NNM2/&HST2; node monitored by this node: &NNM3/&HST3

The message is output when a node signs on or off at a cluster or when a node fails. It provides information during the monitoring relationships in the UTM cluster application.

The message possesses the following inserts:

Insert	Meaning
&ACTION	Describes the situation in which the message is output. It contains one of the following values: ADD REMOVE CHANGE FAIL
&NNM1, &NNM2, &NNM3	Contain the node names.
&HST1, &HST2, &HST3	Contain the computer names.
&STATE	Contains the status of the node application that has been added or removed. If the node application has been added then the old status of this node application is output; if it has been removed then its new status is output. The insert &STATE can have the following values:
	G: generated	Node application has not yet been started
	R: registered	Node application is active
	T: terminated	Node application was terminated normally
	A: abterm	Node application was terminated abnormally
	F: failure	Node is marked as failed

K170

Cluster: new KDCFILE detected; generation time: &DTTM, state: &STATE

The message is output if the generation time reveals a newly generated KDCFILE which is defined as the basis for future starts of application instances.

The message possesses the following inserts:

Insert	Meaning
&DTTM	Generation time of the new KDCFILE
&STATE	Start type of the local application. The insert &STATE can have the following values:
	G: generated	Node application has not yet been started
	R: registered	Node application is active
	T: terminated	Node application was terminated normally
	A: abterm	Node application was terminated abnormally
	F: failure	Node application is marked as failed

K174

Configuration mismatch: &DIA1

The configuration of the starting node application does not match the configuration of the running UTM cluster application.

The insert &DIA1 describes the cause of the error:

• Values <= 10: Runtime configuration error

• Values > 10: KDCDEF configuration error

Values of the insert &DIA1 and their meanings:

&DIA1	Meaning
1	Mixed system log file SYSLOG as single file and file generation group (FGG)
2	The encryption capability of the starting node application is different from that of the running node applications.
3	The application program version of the starting node application is different from the application program version of the running node applications.
11	Mixture of UTM-F and UTM-S applications (MAX APPLIMODE)
12	Mixture of single and duplicate file maintenance (second parameter in MAX KDCFILE, MAX USLOG)
13	Mixture of applications with and without users
14	Mixture of applications with and without multiple sign-on permission (SIGNON MULTI-SIGNON)
16	The number of database systems has been modified. (DATABASE, RMXA)
17	The sequence of database statements (DATABASE) has been modified.
18	The password history has been modified (SIGNON PW-HISTORY)
19	The number of LSSBs has been changed (MAX LSSB)
20	The number of GSSBs has been changed (MAX GSSB)
21	The number of ULS has been changed (ULS)
22	A ULS from the old KDCFILE no longer exists in the new KDCFILE.
23	The maximum number of services that a user is permitted to stack has been reduced (MAX NRCONV)
24	The maximum number of asynchronous services that may be open simultaneously has been reduced (2nd value in MAX ASYNTASKS)
25	The maximum length of the card information has been reduced (MAX CARDLTH)
26	The maximum length of the Kerberos principal has been reduced (MAX PRINCIPAL-LTH)
27	The size of the page pool has been reduced (1st parameter value in MAX PGPOOL)
28	The size of the process-specific buffer for the restart data has been reduced (2nd parameter value in MAX RECBUF)
29	The length of the communication area has been changed (MAX KB)
30	The length of the default primary work area has been reduced (MAX SPAB)
31	The length of the message area has been reduced (MAX KB)
32	The maximum length of physical output messages has been changed (MAX TRMSGLTH)
33	The maximum length of the user data in LPUT records has been reduced (MAX LPUTLTH)
34	The value of the parameter ABORT-BOUND-SERVICE in the CLUSTER statement has been changed.

K175	File &FNAM created

K176

Procedure &PRCN started. &MSG2 RC = &RCHX

The configured procedure was started on the recognition of a node application failure.

The insert &PRCN contains the started procedure including the passed parameters.

The insert &MSG2 contains additional return information.

Values of the insert &RCHX1 and their meanings:

&RCHX1	Meaning
0	The procedure could not be started successfully
-1	The procedure could not be started. &MSG2 contains additional information.

K178

Cluster journal files: action &ACTION; states (&STATE,&STA2); used pages (&PGS1,&PGS2); number switches &SWNR

Diagnostic information is output for the two files in the administration journal.

The message possesses the following inserts:

Insert	Meaning
&ACTION	Action of the administration journal:
	CHANGE	The administration journal file to which data is not currently written has been fully processed by all running node applications and an online copy of the administration data has been created; the entries in the file are no longer needed.
	CREATE	The administration journal files have been (re)generated. This is performed on the start of the first node application if the node application was previously regenerated.
	EXTEND	The administration journal file to which data is currently written has been extended because the other administration journal file has not yet been processed by all running node applications or the online copy of the administration data has not yet been completed.
	OPEN	The administration journal files have been opened. Output on the start of every UTM process.
	SWITCH	The administration journal file to which data is currently written has been switched.
&STATE / &STA2	Status of an administration journal file: At any time, only one file may have the status C; the other file must have the status O or R .
	C (Current)	This is the file to which data is currently written.
	O (Old)	This file is still being processed by running node applications or the online copy of the administration data is not yet terminated.
	R (Reusable)	The data in this file is no longer required and can be overwritten after the administration journal files have been switched.
&PGS1 / &PGS2	Valid pages of an administration journal file: Outputs the number of logically valid pages of an administration journal file: When the file to which data is currently written is switched, it contains only one valid page: the first page containing the control information. Other pages containing old, invalid journal records are not physically released but continue to be occupied.
&SWNR	Number of times the administration journal is switched (ACTION SWITCH)

K179

Data to import completely imported by Online Import

K180

Data to import partially imported by Online Import

K181

No data to import existing for Online Import in file &FNAM.

K182

Abnormal termination of Online Import from file &FNAM.

K183

Normal termination of Online Import from file &FNAM.

K184	There is already an Online Import or a run of KDCUPD active for the old KDCFILE.

K185

The Online Import states that the generation times of the KDCFILEs are not equal

K186

The source application is not part of the cluster application.

K187

Start of Online Import from file &FNAM.

K188

Journal creation time is different. In &OBJ1: &DTTM; in &OBJ2: &DTM2

In the case of UTM cluster applications, this warning is output for diagnostic purposes if different administration journal generation times have been found in files.

The message possesses the following inserts:

Insert	Meaning
&OBJ1 / &OBJ2	File ID	Meaning
	jkaa	JKAA file
	journal	JRN1/JRN2 file
	kdcfile	KDCFILE
&DTTM / &DTM2	Journal generation time found in file 1 or file 2.

K189

Signon rejected - service restart in node application on host &HST1 required