iSeries Navigator : Problems starting Management central.
Daniel Benzimra-Ceuppens
starts 2 jobs.
Job ../QYPSJSVR/QYPSJSVR always ends abnormally after some 3 minutes.
The joblog indicates that "Object of type McScheduler could not be created."
and "Object of type com.ibm.mc.server.McPrivateServer could not be
created.".
I have no idea of where to start looking for a solution.
Has anyone had this problem ? Any solutions out there ?
Regards, Daniel.
QYPSJSVR JOBLOG
================
5722SS1 V5R2M0 020719
Job Log
Job name . . . . . . . . . . : QYPSJSVR
User . . . . . . : QYPSJSVR Number . . . . . . . . .
. . : 022086
Job description . . . . . . : QYPSJOBD
Library . . . . . : QSYS
MSGID TYPE SEV DATE TIME FROM PGM
LIBRARY INST TO PGM LIBRARY INST
CPF1124 Information 00 22/07/03 13:07:28,305072 QWTPIIPP
QSYS 05D4 *EXT *N
Thread . . . . : 00000001
Message . . . . : Job
022303/QYPSJSVR/QYPSJSVR started on 22/07/03 at
13:07:28 in subsystem QSYSWRK in
QSYS. Job entered system on 22/07/03 at
13:07:27.
CPI1125 Information 00 22/07/03 13:07:28,308824 QWTPCRJA
QSYS 0108 *EXT *N
Thread . . . . : 00000001
Message . . . . : Job
022303/QYPSJSVR/QYPSJSVR submitted.
Cause . . . . . : Job
022303/QYPSJSVR/QYPSJSVR submitted to job queue
QSYSNOMAX in QSYS from job
022226/QPGMR/QWZASTRTCP. Job
022303/QYPSJSVR/QYPSJSVR was started
using the Submit Job (SBMJOB) command
with the following job attributes:
JOBPTY(5) OUTPTY(5) PRTTXT(EU-Count)
RTGDTA(RUNPTY10) SYSLIBL(QSYS
QSYS2 QHLPSYS QUSRSYS
UTL_OPR) CURLIB(*CRTDFT) INLLIBL(QGPL
QTEMP) LOG(4 00 *NOLIST)
LOGCLPGM(*NO) INQMSGRPY(*RQD)
OUTQ(/*DEV) PRTDEV(PRT01) HOLD(*NO)
DATE(*SYSVAL) SWS(00000000)
MSGQ(/*NONE) CCSID(37) SRTSEQ(*N/*LANGIDSHR)
LANGID(ENG) CNTRYID(IL) JOBMSGQMX(30)
JOBMSGQFL(*WRAP) ALWMLTTHD(*YES)
INLASPGRP(*NONE) SPLFACN(*KEEP).
*NONE Request 22/07/03 13:07:28,313464 QWTSCSBJ
*N QCMD QSYS 0178
Thread . . . . : 00000001
Message . . . . : -QSYS/CALL
PGM(QSYSDIR/QYPSJSVR)
CPFB93B Diagnostic 40 22/07/03 13:10:47,111840 QYJSPART
QSYS *STMT QYJSPART QSYS *STMT
From module . . . . . . . . :
QYJSPPGM
From procedure . . . . . . :
callProgram
Statement . . . . . . . . . : 93
To module . . . . . . . . . :
QYJSPPGM
To procedure . . . . . . . :
callProgram
Statement . . . . . . . . . : 93
Thread . . . . : 00000001
Message . . . . : Object not created.
Cause . . . . . : Object of type
McScheduler could not be created. Recovery
. . . : If the problem persists,
contact service.
CPFB93B Diagnostic 40 22/07/03 13:10:48,108632 QYJSPART
QSYS *STMT QYJSPART QSYS *STMT
From module . . . . . . . . :
QYJSPPGM
From procedure . . . . . . :
callProgram
Statement . . . . . . . . . : 93
To module . . . . . . . . . :
QYJSPPGM
To procedure . . . . . . . :
callProgram
Statement . . . . . . . . . : 93
Thread . . . . : 00000001
Message . . . . : Object not created.
Cause . . . . . : Object of type
com.ibm.mc.server.McPrivateServer could not
be created. Recovery . . . : If
the problem persists, contact service.
CPFB9B6 Diagnostic 40 22/07/03 13:10:48,548024 QYJSPART
QSYS *STMT QYJSPART QSYS *STMT
From module . . . . . . . . :
QYJSPPGM
From procedure . . . . . . :
callProgram
Statement . . . . . . . . . : 93
To module . . . . . . . . . :
QYJSPPGM
To procedure . . . . . . . :
callProgram
Statement . . . . . . . . . : 93
Thread . . . . : 00000001
Message . . . . : Management Central
server not started.
Cause . . . . . : Management Central
server *N on port 10.4.0.30 could not
connect with server on system *N.
Recovery . . . : Verify the server on
the target system is started and
configured correctly. If the problem
persists, contact service.
MCH74A5 Escape 40 22/07/03 13:10:50,785384
realcftrap2 001394 QYPSJSVR QSYSDIR *STMT
To module . . . . . . . . . :
QYPSJHELPR
To procedure . . . . . . . :
sys_CallStaticVoidMethod__FiT1e
Statement . . . . . . . . . : 878
Thread . . . . : 00000001
Message . . . . : The Java Virtual
Machine has ended.
Cause . . . . . : Java Virtual
Machine 1 has ended because of reason 1. The
reason codes are defined as follows:
01- A Java program called the
java.lang.System.exit method with a
zero status code. 02- A Java program
called the java.lang.System.exit
method with a non zero status code of 0.
03- An unexpected system error was
detected. 04- A critical Java Virtual
Machine thread has ended and
processing cannot continue. Recovery . . . :
If the Java Virtual Machine ended
because of reason code 03, an internal
error has occurred. Contact you
service representative. Information about
the error was saved in the Licensed
Internal Code log.
CEE9901 Escape 30 22/07/03 13:10:51,531176 QLEAWI
QSYS *STMT QCMD QSYS 01A6
From module . . . . . . . . : QLEDEH
From procedure . . . . . . : Q LE
leDefaultEh
Statement . . . . . . . . . : 231
Thread . . . . : 00000001
Message . . . . : Application error.
MCH74A5 unmonitored by QYPSJSVR at
statement 0000000878, instruction
X'0000'.
Cause . . . . . : The application
ended abnormally because an exception
occurred and was not handled. The
name of the program to which the
unhandled exception is sent is
QYPSJSVR QYPSJHELPR
sys_CallStaticVoidMethod__FiT1e. The
program was stopped at the high-level
language statement number(s)
0000000878 at the time the message was sent.
If more than one statement number is
shown, the program is an optimized ILE
program. Optimization does not allow
a single statement number to be
determined. If *N is shown as a
value, it means the real value was not
available. Recovery . . . : See
the low level messages previously listed
to locate the cause of the exception.
Correct any errors, and then try the
request again.
CPC2402 Completion 50 22/07/03 13:10:52,333304 QCMD
QSYS 05D8 *EXT *N
Thread . . . . : 00000001
Message . . . . : Job ended. Cancel
message received at command processor.
Cause . . . . . : A message with a
severity equal to or exceeding the end
severity was received at the command
processor. Recovery . . . : See the
messages previously listed to
determine the message that caused the job to
be ended. Correct the errors, and
then try the request again.
CPF1164 Completion 00 22/07/03 13:10:54,982152 QWTMCEOJ
QSYS 00BD *EXT *N
Thread . . . . : 00000001
Message . . . . : Job
022303/QYPSJSVR/QYPSJSVR ended on 22/07/03 at
13:10:54; 14 seconds used; end code
20 .
Cause . . . . . : Job
022303/QYPSJSVR/QYPSJSVR completed on 22/07/03 at
13:10:54 after it used 14 seconds
processing unit time. The job had ending
code 20. The job ended after 1
routing steps with a secondary ending code of
0. The job ending codes and their
meanings are as follows: 0 - The job
completed normally. 10 - The job
completed normally during controlled ending
or controlled subsystem ending. 20 -
The job exceeded end severity (ENDSEV
job attribute). 30 - The job ended
abnormally. 40 - The job ended before
becoming active. 50 - The job ended
while the job was active. 60 - The
subsystem ended abnormally while the
job was active. 70 - The system ended
abnormally while the job was active.
80 - The job ended (ENDJOBABN command).
90 - The job was forced to end after
the time limit ended (ENDJOBABN
command). Recovery . . . : For
more information, see the Work Management
topic in the Information Center,
http://www.iseries.ibm.com/infocenter.
Daniel Benzimra-Ceuppens
WRKAUT OBJ('/QIBM/ProdData/OS400/MGTC/McPrivServer.jar') showed
__ *PUBLIC(*EXCLUDE)
__ QSYS(*RWX)
after changing authority to :
WRKAUT OBJ('/QIBM/ProdData/OS400/MGTC/McPrivServer.jar') ==>
__ *PUBLIC(*RX)
__ QSYS(*RWX)
To be sure, I also changed some other objects in the same directory that had
*PUBLIC(*EXCLUDE) to *PUBLIC(*RX).
the MC serverjob QYPSJSVR started correctly.
Sometimes you have to put a problem to others to find the solution.
Daniel.
"Daniel Benzimra-Ceuppens" <dceuppens@xxxxxxx> wrote in message
news:bfj910$202a$1...@news.boulder.ibm.com...