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.
U9	Sign-on not possible due to lack of Kerberos support.
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  of the generated complexity level
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.

K150

RSO error &RSORC &RSO2RC &RSOMSG when calling subsystem RSO with action &RSOOPC

The insert &RSOOPC describes the RSO call in which the error occurred and has the following meaning:

RSOOPC	Meaning
X‘01‘	Reserve Printer
X‘02‘	Print Message
X‘03‘	Release Printer
X‘04‘	Invalidate Bourse
X‘05‘	Receive Info: Information on the printer or printer jobs
X‘06‘	Receive OLTP interfaces version number

The inserts &RSORC, &RSO2RC and &RSOMSG describe the synchronous and
asynchronous return code and the RSO error message. The RSO error message
can be obtained from the RSO manual.

If the asynchronous return code is not X'00000000', then the error occurred during
the execution of the preceding job. In this case, the operation code of the preceding
call can be found in byte 4 and the return code in bytes 5 to 8 of the insert
RSOANNO:

X'56'

undef

undef

Opcode

R e t u r n c o d e

If the synchronous return code is not X'00000000' then the error occurred in the
current &RSOACT call. The content of the insert &RSOANNO is then irrelevant.

If both the synchronous and the asynchronous return codes are X'00000000' then
the RSO error message indicates a problem.

The return code (SC2 SC1 MC) consists of the components subcode 2 (SC2,
always X‘00‘), subcode 1 (SC1) and main code (MC).

SC1	MC	Meaning
X‘00‘	X‘0000‘	The function was executed without error.
X‘01‘	X‘0003‘	Function call with invalid action.
	X‘0004‘	Length of the RSO macro OLTPRQX passed in the FPUT/DPUT RP by the UTM program unit is incorrect.
	X‘0005‘	Version of the RSO macro OLTPRQX passed in the FPUT/DPUT RP by the UTM program unit is incorrect.
	X‘0006‘	Function/unit of the RSO macro OLTPRQX passed in the FPUT/DPUT RP by the UTM program unit is incorrect.
	X‘0011‘	Character set name (CCSNAME) incorrect
	X‘000A‘	RSO buffer size too small (see RSO command MODIFY-SPOOL-PARAMETER).
	X‘FFFF‘	Unit or function not supported.
X‘02‘	X‘0006‘	Printer in release process. It will soon be available.
	X‘FFFF‘	Function not available.
X‘03‘	X‘FFFF‘	Version not supported.
X‘20‘	X‘0001‘	An error was reported during a memory request.
	X‘0003‘	Printer is already reserved by another application (as of RSO V3.2A).
	X‘0004‘	This printer is already reserved.
	X‘0005‘	An error occurred when creating the OLTP controller.
	X‘0009‘	An error occurred when using the bourse interface.
	X‘000F‘	An error occurred when using the memory pool.
	X‘0010‘	An inconsistency in the internal tables was detected.
X‘40‘	X‘0007‘	The printer is currently being used.
	X‘0012‘	Character set name (CCSNAME) unknown
	X‘0013‘	XHCS error in RSO
	X‘000B‘	An error occurred on accessing the printer.
	X‘000D‘	UTM does not have any access rights for the device (see the MODIFY-PRINTER-OUTPUT command).
X‘41‘	X‘0002‘	Printer not reserved by UTM or not started (see RSO command START-PRINTER-OUTPUT).
	X‘0006‘	The printer is currently being released because the STOP-PRINTER-OUTPUT command was issued.
	X‘0008‘	Printer released internally as a result of an internal error (recovery).
	X‘000C‘	Printer cannot be reserved due to recovery.
	X‘FFFF‘	RSO subsystem not loaded.
X‘42‘	X‘FFFF‘	RSO subsystem not connected.
X‘80‘	X‘000E‘	An error occurred on accessing the printer.
X‘81‘	X‘FFFF‘	RSO subsystem temporarily unavailable.
X‘82‘	X‘FFFF‘	RSO subsystem halted or stopped.

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.
00000005	Output file already exists and is not of the type SAM.

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).

K153

Info for FHS message: &PTRM/&PRNM/&BCAP/&LTRM/&USER This message is generated if FHS requests openUTM to output a message to SYSOUT. The message allows you to assign the user and LTERM partner to the FHS message. This information can be required in the event of problems with OMNIS (with and without MUX connections) in order to identify where the problem originated.

K154

SOCKET 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
OPEN_EVENTGROUP	Open the event group
ATTACH IPv4	Create a socket for the address family AF_INET
ATTACH IPv6	Create a socket for the address family AF_INET6
ATTACH AMBIGUOUS	A socket with the same port number has already been generated.
EVENT	Pick up an event
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 IPv4 address
GET_IPNODE_BY_ADDR	Determine host name corresponding to an IPv6 address
GET_HOST_BY_NAME	Determine IPv4 address of a computer
GET_IPNODE_BY_NAME	Determine IPv6 address corresponding to a host Name

The values of the diagnostic word are 4 byte long and are specified in hexadecimal notation. They correspond to the return codes of the “YDBSOC” interface.

General return codes

The following return codes can occur at every call of the TCP/IP functions:

Return code				Meaning
Subcode		Main code
2	1	2	1
00	01	FF	FF	Invalid unit or function in the standard header
00	02	FF	FF	Requested function not available
00	03	FF	FF	Invalid version number in standard header
00	41	FF	FF	Subsystem not present or not started
00	20	00	30	Internal BCAM error
00	82	00	04	BCAM is not active
0C	40	02	1C	BCAM shutdown running
14	40	02	20	SOCKET of BCAM administrator closed
00	04	00	44	Parameter list not accessible

&TCPCL = OPEN_EVENTGROUP

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	OPEN-EVENTGROUP executed successfully
04	80	06	1C	No memory available for SUB-TCB
04	80	0C	1C	No memory available for layer 4 CB
04	80	10	1C	No memory available for local event group control block
04	80	11	1C	No memory available for global event group control block
04	80	14	1C	No memory available for event group name
08	40	01	1C	BCAM shutdown announced
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND processing
00	01	02	51	Event group already opened by this task
00	01	10	51	USERID of the owner of the event group could not be determined
00	01	11	51	Specification of EVENTGROUP_NAME is not permitted for a TU user

&TCPCL = CLOSE_EVENTGROUP

Return code				Meaning
Subcode		Main code
2	1	2	1
00	01	00	00	CLOSE_EVENTGROUP executed successfully
04	80	0C	1C	No memory available for layer 4 CB
08	40	01	1C	BCAM shutdown announced
00	80	00	28	Event group cannot be closed at the moment (call can be repeated later)
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND processing
00	01	04	51	Task not connected to the event group
00	01	07	51	Invalid EVENTGROUP_ID
00	01	13	51	Event group cannot be closed at the moment because it is still being used

&TCPCL = ATTACH IPv4 or ATTACH IPv6

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	SOCKET executed successfully
00	01	33	08	Specified port number already being used
04	80	04	1C	No memory available for APPCB
04	80	06	1C	No memory available for SUB-TCB
04	80	09	1C	No memory available for ENACB
04	80	0C	1C	No memory available for layer 4 CB
04	80	0D	1C	No free ABID available
04	80	0E	1C	No free port number available
04	80	13	1C	No name server entry available
08	40	01	1C	BCAM shutdown announced
10	82	00	1C	Global limit value for the number of open SOCKETs reached
10	01	00	20	SOCKET already opened by this task
18	40	01	20	SOCKET is currently being forcibly closed by the BCAM administrator
28	82	00	20	Local task limit value for the number of open SOCKETs
00	80	00	28	SOCKET currently not possible (call can be repeated later)
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND processing
00	01	01	50	Unknown host
00	01	02	50	Host not active
00	01	04	51	Task not connected to the event group
00	01	07	51	Invalid EVENTGROUP_ID
00	01	10	53	USER_ID could not be determined

&TCPCL = DETACH

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	CLOSE_SOCKET executed successfully
00	01	03	08	SOCKET_ID not specified
04	08	0C	1C	No memory available for layer 4 CB
04	01	00	20	SOCKET not opened by this task
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND processing

&TCPCL = EVENT

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	GET-EVENT executed successfully
00	80	00	28	GET-EVENT currently cannot be executed (call can be repeated later)
00	01	04	51	Task not connected to the event group
00	01	07	51	Invalid EVENTGROUP_ID
00	80	09	51	No event occurred

&TCPCL = CONNECTION_REQ

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	CONNECT executed successfully
00	01	03	08	SOCKET_ID not specified
04	80	02	1C	No free transport reference available
04	80	03	1C	No memory available for ACONCB
04	80	0A	1C	No memory available for ADDRCB-P
04	80	0B	1C	No free CONNECTION_ID available
04	80	0C	1C	No memory available for layer 4 CB
04	80	0E	1C	No free port number available
04	80	15	1C	No memory available for EVOL
08	40	01	1C	BCAM shutdown announced
04	01	00	20	SOCKET not opened by this task
18	40	01	20	SOCKET currently being closed forcibly by the BCAM administrator
20	01	00	20	CONNECT not permitted for SOCKET
24	82	00	20	No further connections permitted for this SOCKET
08	01	00	24	Connection already established
0C	01	00	24	Connection is already being established
18	01	00	24	Partner not known
1C	82	00	24	Partner processor not known
1C	82	01	24	Partner processor not active
1C	82	04	24	Partner IP address not known
1C	82	06	24	Request to establish connection to broadcast address
30	01	00	24	SOCKET not authorized for connection establishment
40	01	05	24	Required interface functionality not supported
40	01	07	24	Interface functionality of partners does not match
40	01	08	24	Level 4 address not available
60	40	00	24	Port number already being used
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND processing
00	01	04	51	Task not connected to the event group
00	01	07	51	Invalid EVENTGROUP_ID

&TCPCL = CONNECTION_RSP

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	ACCEPT executed successfully
00	01	07	08	CONNECTION_ID not specified
04	80	0C	1C	No memory available for layer 4 CB
08	40	01	1C	BCAM shutdown announced
04	01	00	20	SOCKET not opened by this task
18	40	01	20	SOCKET currently being closed forcibly by the BCAM administrator
04	01	00	24	Invalid CONNECTION_ID
14	01	00	24	No CONNECTION request pending
40	01	05	24	Required interface functionality not supported
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND process.
00	01	04	51	Task not connected to the event group
00	01	07	51	Invalid EVENTGROUP_ID

&TCPCL = DISCONNECT_REQ

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	CLOSE-CONNECTION executed successfully
00	01	07	08	CONNECTION_ID not specified
04	80	0C	1C	No memory available for layer 4 CB
04	01	00	20	SOCKET not opened by this task
18	40	01	20	SOCKET currently being closed forcibly by the BCAM administrator
04	01	00	24	Invalid CONNECTION_ID
64	40	00	24	Connection already being cleared down
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND process.

&TCPCL = DATA_REQ

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	SEND executed successfully
14	00	00	00	SEND executed successfully, but further sending prevented by interface flow control
00	01	07	08	CONNECTION_ID not specified
00	01	26	08	LENGTH_OF_DATA invalid
00	01	13	08	User buffer length = 0
00	01	31	08	User buffer not accessible
00	01	00	14	User data facility too large
04	80	01	1C	No memory available for data buffer
04	80	07	1C	Sending prevented by interface flow control
14	40	00	1C	Waiting for DATA_GO_INDICATION
04	01	00	20	SOCKET not opened by this task
04	01	00	24	Invalid CONNECTION_ID
48	01	00	24	Connection is not in the data transfer phase (not yet fully established)
00	80	00	28	SEND currently cannot be executed (call can be repeated later)

&TCPCL = DATA_IND

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	READ executed successfully
00	01	07	08	CONNECTION_ID not specified
00	01	26	08	length_of_data invalid
00	01	2D	08	No data available
00	01	31	08	User buffer cannot be accessed
00	40	00	10	No data received
04	01	00	20	SOCKET not opened by this task
04	01	00	24	Invalid CONNECTION_ID
48	01	00	24	Connection is not in the data transfer phase (not yet fully established)
00	80	00	28	READ currently cannot be executed (call can be repeated later)
00	40	00	2C	User data lost

&TCPCL = GET_HOST_BY_ADDR

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	GET_HOST_BY_ADDR executed successfully
04	80	0C	1C	No memory available for layer 4 CB
08	40	01	1C	BCAM shutdown announced
00	80	00	28	GET_HOST_BY_ADDR currently not possible (call can be repeated later)
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND processing
00	01	01	53	Invalid IP address

&TCPCL = GET_HOST_BY_NAME

Return code				Meaning
Subcode		Main code
2	1	2	1
00	00	00	00	GET_HOST_BY_NAME executed successfully
00	01	30	08	Invalid socket host name
04	80	0C	1C	No memory available for layer 4 CB
08	40	01	1C	BCAM shutdown announced
00	80	00	28	GET_HOST_BY_NAME currently not possible (call can be repeated later)
00	20	01	30	System error at startup of CONHAND processing
00	20	02	30	System error waiting for the termination of CONHAND processing

&TCPCL = GET_IPNODE_BY_ADDR

Return code				Meaning
Subcode		Maincode
2	1	2	1
00	00	00	00	GET_IPNODE_BY_ADDR performed successfully
04	80	0C	1C	No memory available for Layer 4 CB
08	40	01	1C	BCAM shutdown announced
00	80	00	28	GET_IPNODE_BY_ADDR not currently possible (repeat call later)
00	20	01	30	System error on starting CONHAND processing
00	20	02	30	System error on waiting for termination of CONHAND processing
00	01	01	53	Invalid IPv6 address

&TCPCL = GET_IPNODE_BY_NAME

Return code				Meaning
Subcode		Maincode
2	1	2	1
00	00	00	00	GET_IPNODE_BY_NAME performed successfully
00	01	30	08	Invalid socket host name
04	80	0C	1C	No memory available for Layer 4 CB
08	40	01	1C	BCAM shutdown announced
00	80	00	28	GET_IPNODE_BY_NAME not currently possible (repeat call later)
00	20	01	30	System error on starting CONHAND processing
00	20	02	30	System error on waiting for termination of CONHAND processing

K155

Your password is expired!
Please enter expired password
> &PAS1 <
Please enter new password
> &PAS2 <
and repeat new password
> &PAS3 <

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.

• In UTM(BS2000), the same host code should be used on the participating hosts so that special characters in passwords always have the same EBCDIC code.

K160

The &TACNTR. transaction of service &TCVG has been rolled back by &RBCAUSER (&RCCC/&RCDC)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.
RCCC	Value of the compatible KCRCCC return code
RCDC	Valid of the incompatible KCRCDC return code

K161	Synchronous Periodic Write started for task &TASK
K162	Long IO for task &TASK: &IOPG pages, &IOMS milliseconds
K163	Long Periodic Write for task &TASK: &IOPG pages, &IOMS milliseconds
K164	System file SYSOUT will be switched to file &FNAM.
K165	System file SYSLST will be switched to file &FNAM.
K166	Error &RCHX when switching system file &SYSFILE to file &FNAM.
K167	System files SYSOUT und SYSLST successfully switched. If the UTM application was started in a dialog then message K167 confirms the successful switching of the SYSLST files for all the application’s tasks. SYSOUT continues to be assigned to the terminals unchanged.

K175	File &FNAM created

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