Management Central Problem
Frank
PTF package C3007510, and installed the client access express service pack
SI06804. Client access V5R1 is installed on the PC, and we are able to
control and gain access to the system the system via the definition under
"my connections".
When expanding the management central branch in the ops navigator, the ops
navigator does not respond for some time, then a failure to connect message
is displayed on the PC. Additionally, when the management central branch of
the ops navigator is expanded, two jobs start on the AS/400- QYPSJSVR and
QYPSSVR. The QYPSSVR job finishes quite quickly, however, the QYPSJSVR job
runs for about 15 minutes, and consumes vast amounts of system resources
before ending abnormally. The same problem occurs when commands STRTCP or
STRTCPSVR(*MGTC) are issued. The joblog (see below) implies that we need to
define our system as an endpoint, however, we are unable to do this because
we can't expand the management central branch in the ops navigator.
5722SS1 V5R1M0 010525 Job Log
CENTRAL 26/02/03 11:24:27 Page 1
Job name . . . . . . . . . . : QYPSJSVR User . . . . . . :
QYPSJSVR Number . . . . . . . . . . . : 525576
Job description . . . . . . : QYPSJOBD Library . . . . . :
QSYS
MSGID TYPE SEV DATE TIME FROM PGM
LIBRARY INST TO PGM LIBRARY INST
CPF1124 Information 00 26/02/03 11:06:36 QWTPIIPP
QSYS 067E *EXT *N
Message . . . . : Job
525576/QYPSJSVR/QYPSJSVR started on 26/02/03 at
11:06:36 in subsystem QSYSWRK in
QSYS. Job entered system on 26/02/03 at
11:06:35.
CPI1125 Information 00 26/02/03 11:06:36 QWTPIIPP
QSYS 02DC *EXT *N
Message . . . . : Job
525576/QYPSJSVR/QYPSJSVR submitted.
Cause . . . . . : Job
525576/QYPSJSVR/QYPSJSVR submitted to job queue
QSYSNOMAX in QSYS from job
525573/QUSER/QZRCSRVS. Job
525576/QYPSJSVR/QYPSJSVR was started
using the Submit Job (SBMJOB) command
with the following job attributes:
JOBPTY(5) OUTPTY(5) PRTTXT()
RTGDTA(RUNPTY10) SYSLIBL(QSYS
QSYS2 QHLPSYS QUSRSYS DIVGPL
DIVPGM TAATOOL)
CURLIB(*CRTDFT) INLLIBL(QTEMP RSLIB
CSTSTLIB UTLGENLIB QGPL QRPG
TOTC21) LOG(4 00 *NOLIST)
LOGCLPGM(*NO) INQMSGRPY(*RQD)
OUTQ(RSLIB/RSOUTQ) PRTDEV(PRT01) HOLD(*NO)
DATE(*SYSVAL) SWS(00000000)
MSGQ(/*NONE) CCSID(37) SRTSEQ(*N/*HEX)
LANGID(ENU) CNTRYID(US)
ALWMLTTHD(*YES).
*NONE Request 26/02/03 11:06:36 QWTSCSBJ
*N QCMD QSYS 0173
Message . . . . : -QSYS/CALL
PGM(QSYSDIR/QYPSJSVR)
CPC1129 Completion 00 26/02/03 11:07:27 QWTCHGJB
QSYS 05CE *EXT *N
Message . . . . : Job
525576/QYPSJSVR/QYPSJSVR changed by QSECOFR.
CPFB9BC Diagnostic 40 26/02/03 11:23:30 QYJSPART
QSYS *STMT QYJSPART QSYS *STMT
From module . . . . . . . . :
QYJSPPGM
From procedure . . . . . . :
callProgram
Statement . . . . . . . . . : 93
To module . . . . . . . . . :
QYJSPPGM
To procedure . . . . . . . :
callProgram
Statement . . . . . . . . . : 93
Message . . . . : Initialization
failed.
Cause . . . . . : Static
initialization of class
com.ibm.mc.client.McEnvironment
failed. Recovery . . . : If the problem
persists, contact service.
CPFB96C Diagnostic 40 26/02/03 11:23:36 QYJSPART
QSYS *STMT QYJSPART QSYS *STMT
From module . . . . . . . . :
QYJSPPGM
From procedure . . . . . . :
callProgram
Statement . . . . . . . . . : 93
To module . . . . . . . . . :
QYJSPPGM
To procedure . . . . . . . :
callProgram
Statement . . . . . . . . . : 93
Message . . . . : Value not valid.
Cause . . . . . : Value *N is not
valid for variable getHostName. Recovery
. . . : If the problem persists,
contact service.
CPFB9B6 Diagnostic 40 26/02/03 11:23:36 QYJSPART
QSYS *STMT QYJSPART QSYS *STMT
From module . . . . . . . . :
QYJSPPGM
From procedure . . . . . . :
callProgram
Statement . . . . . . . . . : 93
To module . . . . . . . . . :
QYJSPPGM
To procedure . . . . . . . :
callProgram
Statement . . . . . . . . . : 93
Message . . . . : Management Central
server not started.
Cause . . . . . : Management Central
server *N on port *N 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,
5722SS1 V5R1M0 010525 Job Log
CENTRAL 26/02/03 11:24:27 Page 2
Job name . . . . . . . . . . : QYPSJSVR User . . . . . . :
QYPSJSVR Number . . . . . . . . . . . : 525576
Job description . . . . . . : QYPSJOBD Library . . . . . :
QSYS
MSGID TYPE SEV DATE TIME FROM PGM
LIBRARY INST TO PGM LIBRARY INST
contact service.
MCH74A5 Escape 40 26/02/03 11:24:18 realcftrap2
0014E8 QYPSJSVR QSYSDIR *STMT
To module . . . . . . . . . :
QYPSSMJSVR
To procedure . . . . . . . :
sys_CallStaticVoidMethod__FiT1e
Statement . . . . . . . . . : 852
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.
CEE0200 Information 10 26/02/03 11:24:19 QLEAWI
QSYS *STMT QCMD QSYS 01A1
From module . . . . . . . . : QLEDEH
From procedure . . . . . . : Q LE
leDefaultEh
Statement . . . . . . . . . : 176
Message . . . . : This job is about
to end.
Cause . . . . . : The job is being
terminated because the job is capable of
having multiple threads and the
application has issued an exit(), abort() or
their equivalent APIs, an exception
has occurred and is not being handled,
or a return from main() has occurred
in a program that runs in a *NEW
Activation Group.
CEE0200 Information 10 26/02/03 11:24:19 QLEAWI
QSYS *STMT QYPSJSVR QSYSDIR *STMT
From module . . . . . . . . : QLEPM
From procedure . . . . . . : Q LE
leBdyEpilog
Statement . . . . . . . . . : 1061
To module . . . . . . . . . :
QYPSSMJSVR
To procedure . . . . . . . :
_CXX_PEP
Statement . . . . . . . . . : 1628
Message . . . . : This job is about
to end.
Cause . . . . . : The job is being
terminated because the job is capable of
having multiple threads and the
application has issued an exit(), abort() or
their equivalent APIs, an exception
has occurred and is not being handled,
or a return from main() has occurred
in a program that runs in a *NEW
Activation Group.
CPC1219 Completion 50 26/02/03 11:24:20 QWTPITPP
QSYS 0695 *EXT *N
Message . . . . : This job ended
abnormally.
Cause . . . . . : An error occurred
that caused this job to end abnormally.
Recovery . . . : See the
previously listed messages in the job log for
this job. Correct the errors and try
the request again.
CPF1164 Completion 00 26/02/03 11:24:25 QWTMCEOJ
QSYS 00BC *EXT *N
Message . . . . : Job
525576/QYPSJSVR/QYPSJSVR ended on 26/02/03 at
11:24:25; 526 seconds used; end code
30 .
Cause . . . . . : Job
525576/QYPSJSVR/QYPSJSVR completed on 26/02/03 at
11:24:25 after it used 526 seconds
processing unit time. The job had ending
code 30. 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
5722SS1 V5R1M0 010525 Job Log
CENTRAL 26/02/03 11:24:27 Page 3
Job name . . . . . . . . . . : QYPSJSVR User . . . . . . :
QYPSJSVR Number . . . . . . . . . . . : 525576
Job description . . . . . . : QYPSJOBD Library . . . . . :
QSYS
MSGID TYPE SEV DATE TIME FROM PGM
LIBRARY INST TO PGM LIBRARY INST
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 book,
http://www.as400.ibm.com/infocenter.
Any help would be gratefully received.
Thanks in advance,
Frank
Bengt Persson
have you put a hostname and domain name for the AS/400 in CFGTCP, 12?
A name that also exists in CFGTCP, 10 or in a DNS?
--
Bengt
"Frank" <nos...@nowhere.com> skrev i meddelandet
news:b3ibfg$eqk$1...@helle.btinternet.com...
Bill
is a domain name in CFGTCP 12.
Thnx
Bill
"Bengt Persson" <be...@home.se> wrote in message
news:b3icaa$1m73cv$1...@ID-3221.news.dfncis.de...
RPGeezus
work at my office. The Management Central server job, QYPSSRV, listens on
port 5555. The Management Central java server job, QYPSJSVR, listens on port
5544.
Open up both ports and then try and start MC again. It worked for me.
"Bill cogeco.net>" <bwragg@<NOSPAM> wrote in message
news:Bb47a.80701$L47.11...@read2.cgocable.net...
Frank
I checked the hostname and host table entries as you suggested- and they
contain values that appear to match. The hostname was in lower case- so we
changed that to upper case to match the host table entry. Unfortunately
this did not fix the problem.
Regards,
Frank
"Bengt Persson" <be...@home.se> wrote in message
news:b3icaa$1m73cv$1...@ID-3221.news.dfncis.de...
Bill
Thmx
Bill
"RPGeezus" <RPGe...@nospam.com> wrote in message
news:WD57a.3156$OD6.3...@ursa-nb00s0.nbnet.nb.ca...
newbie2002
I had these exact messages in my job logs also. I was able to start
the management central server on my central system but it failed to
start on an endpoint system. I needed it running on the endpoint to
use the monitoring feature. To fix it I had to change the domain
information on the endpoint system to match the central system. Not
sure if this helps you or not.
Shane
"Frank" <nos...@nowhere.com> wrote in message news:<b3ibfg$eqk$1...@helle.btinternet.com>...
Frank
user QYPSJSVR. Management central now functions.
Thanks to those who responded to the original post.
"Frank" <nos...@nowhere.com> wrote in message
news:b3ibfg$eqk$1...@helle.btinternet.com...