Messages of the utmmain process

U221 U222 U223

&OBJ1 UTM application &APPL &VERS terminated ( &STRTIME ) &OBJ1 Invalid number of arguments &OBJ1 UTM application &APPL still running according to internal status, applifile: &OBJ3 An application of this name is already running. This can result from the following: The application name selected is not unique throughout the system. Response: ask the UTM administrator. The user-own application ran as a UTM test application. The initial status was not then produced by calling the kdcrem utility. Response: call the kdcrem utility. The application was not terminated before the operating system shut down. Response: call the kdcrem utility. The application was running as a productive application with the TEST option. After the application is terminated normally, the utmmain process is not terminated automatically. Response: terminate the utmmain process with kill -9.

U224 U225 U227 U228 U229 U230 U231

&OBJ1 KDCROOT terminated utmmain: Error while creating pipe &FNAM,errno: &ERRNO &OBJ1 UTM application &APPL terminated by kdcrem utmmain: Read error on pipe, errno: &ERRNO utmmain: &OBJ1 process died, pid: &PID, &SIGEXIT( &STRTIME ) utmmain: utmwork process died, pid: &PID utmwork is being restarted (&STRTIME) utmmain: utmwork process died, pid: &PID Unexpected exit code: &EXTCODE &SIGEXIT( &STRTIME ) This message is generated when a utmwork process is not terminated under the control of openUTM, for instance if terminated with kill -9. In the UTM application a work process is lost and is not restarted. The UTM application is terminated abnormally in this case in order to avoid inconsistencies. This is indicated with the message U221. The list below shows some of the reasons why work processes can terminate without being under the control of openUTM: application was started with STXIT = OFF and a signal occurred utmwork processes receive signals from a source other than openUTM a program unit overwrites signal routines the runtime environment of COBOL or C++ causes the process to terminate the database terminates the process Action: Eliminate the problem which resulted in the termination of the process and restart the UTM application.

U232

&OBJ1 Error &UERRNO during utmmain run

The values of &UERRNO and their meanings are listed in the following table. For most errors, additional information on the associated actions is available at stderr.

&UERRNO	Meaning	Action
1	Standalone application: FILEBASE parameter not present in start parameter file.	User error
	UTM cluster application: CLUSTER-FILEBASE parameter not present in start parameter file.
2	utmmain could not sign on at the shared memory areas of the application.	User error
11	First utmwork process terminated immediately after start.	See utmwork messages
12	utmwork process terminated in undefined state.	See utmwork messages
13	Invalid job received by utmwork.	Problem report + documentation
18	utmnetssl process has been terminated.	User error: For details see preceding SSL msg U306
21	Memory bottleneck while requesting lock management for cluster configuration file (only for UTM cluster applications).	Check memory requirement
22	utmmain could not set a shared lock for the cluster configuration file (only for UTM cluster applications).	User error
23	Memory bottleneck while requesting area for reading in cluster configuration file (only for UTM cluster applications).	Check memory requirement
24	Cluster configuration file has inconsistent content (only for UTM cluster applications).	User error
25	Invalid version in cluster configuration file (only in UTM cluster applications).	User error
26	Invalid operating system type in cluster configuration file (only in UTM cluster applications).	User error
27	Invalid bit mode in cluster configuration file (only in UTM cluster applications).	User error
28	Name of local host could not be evaluated (only for UTM cluster applications).	Problem report + documentation
29	Node entry for local host could not be found in cluster configuration file (only for UTM cluster applications).	User error
30	Memory bottleneck while requesting lock management for KDCFILE (only for UTM cluster applications).	Check memory requirement
31	utmmain could not set a shared lock for the KDCFILE (only for UTM cluster applications).	User error
32	File is not a cluster configuration file	User error
33	The node name specified during node recovery could not be found in the cluster configuration file.	User error
34	The local host name is longer than 64 characters.	User error
41-49	utmmain was not able to sign on to the IPC shared memory.	Problem report + documentation
51-59	utmmain was not able to send the anno for issuing message K167 to utmwork.	Problem report + documentation

U233

U234

U235

U236

U237

U238

U239

U240

U241

&OBJ1 &UREAS

&OBJ1 fork() error &ERRNO ; process type: &PRTYPE

&OBJ1 Starting error &ERRNO for file &FNAM

&OBJ1 Starting of &FNAM, pid: &PID

&OBJ1 Error while deleting a semaphore, key: &SEMKEY, error: &ERRNO

&OBJ1 Error while attaching to a shared memory, key: &SHMKEY, error: &ERRNO

&OBJ1 Error while deleting a shared memory, key: &SHMKEY, error: &ERRNO

utmmain started for test in dialog

&OBJ1 <FILEBASE> more than 29 chars or max. no. of processes

U242

&OBJ1 &FBTYPE names inconsistent, reason: &UERRNO
&FILEBAS1
&FILEBAS2

The insert &FBTYPE has the following meaning:

&FBTYPE	Meaning
FILEBASE	FILEBASE specification in start parameter file
ARGUMENT	FILEBASE specification as argument of utmmain
CLUSTER-FILEBASE	CLUSTER-FILEBASE specification in start parameter file
CONFIG-FILE	FILEBASE specification in cluster configuration file
NODE-RECOVERY-DIR	Directory for node recovery

The insert &UERRNO has the following meaning

&UERRNO	Meaning
1	File base name specification missing in the start parameter file.
2	It was not possible to switch to the directory specified in the start parameter file.
3	It was not possible to change to the directory specified in the argument in utmmain.
4	It was not possible to change to the original directory.
5	The specification of the filebase name as a utmmain argument does not correspond to the specification in the start parameter file (for standalone applications) or in the cluster configuration file (for UTM cluster applications)
6	The directory in which utmmain was started does not match the filebase directory of the node application for which a node recovery is to be performed.
7	utmmain was not started in the filebase directory.

The inserts &FILEBAS1 and &FILEBAS2 have the following meanings:

Insert	Meaning
&FILEBAS1	Specification in start parameter file
&FILEBAS2	Specified as argument

U244

utmmain: Please start &FNAM with arguments:
&VERS &APPL &FILEBASE &FNAM &PID &WID &STIND &WTYP

U245

U246

U247

&OBJ1 System file stdout will be switched from &FNAM to file &FNAM.

&OBJ1 System file stderr will be switched from &FNAM to file &FNAM.

&OBJ1 New system file &FNAM opened. Previous system file was &FNAM.