Link to home
Start Free TrialLog in
Avatar of istate
istate

asked on

Cannot start Management Central server

I was trying to access Management Central in iSeries Navigator and received the following error:  failed to connect to central system 'Iseries.istate.com'.

After clicking on Verify Connection, i received two failed messages:
   - the Management Central server is not running. Open Management Central in iSeries Navigator to start the server.
   - could not verify Java setup. Failed to create a Java Virtual Machine.

After following the instructions under 'Details' for those two errors, as well as following the troubleshooting guide on IBM's website <http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzaih/rzaihtblshtmcconnect.htm>, the Management Central server just won't start. To start it, I am simply going to My Connections; Iseries.istate.com; Network; Servers; TCP/IP, right click Management Central and select Start.

We are running V5R3M0 on a 520. If any other information is needed to help solve my dilemma, I will gladly supply it.

Thanks.
-Adam

Avatar of Member_2_276102
Member_2_276102

Adam:

First, after clicking <Start>, what happened? If you right-click and select <Server jobs>, does the joblog show anything? After clicking <Start>, note that you should (1) select 'Management Central' to get focus in the right-hand pane and then do View-> Refresh.

IIRC, a common problem has been a faulty TCP/IP configuration. Please show your hosts table entry for Iseries.istate.com.

Tom
Avatar of Barry Harper
Adam,
Use WRKACTJOB SBS(QSYSWRK) to see if the management central job QYPSJSVR is running. If it is, check its job log; if not, find the job log and post it here.
From a command prompt, use CWBPING <ip-address> to run a client access ping. Please post the results.
Barry
Avatar of istate

ASKER

I will post the joblog in a seperate post.

- tliotta
when i click start, it just sits there for about a minute with an hour glass. If I do a refresh, it still shows a status of 'Stopped'.
here is the TCP/IP host table entry:

-----
                       Display TCP/IP Host Table Entries                        
                                                             System:   ISERIES  
 Internet Address . . . . . . . . . . . :   10.100.91.10                        
 Host names:                                                                    
   Name . . . . . . . . . . . . . . . . :   ISERIES                            
   Name . . . . . . . . . . . . . . . . :   ISERIES.ISTATE.COM                  
   Name . . . . . . . . . . . . . . . . :   QS10A2569                          
 Text description . . . . . . . . . . . :                                      
                                                                         Bottom
-----

- _b_h
job QYPSJSVR is not running. here are the results of the cwbping:

-----  
   C:\Documents and Settings\aray>cwbping 10.100.91.10

   IBM iSeries Access for Windows
   Version 5  Release 3  Level 0
   Connection Verification Program
   (C) Copyright IBM Corporation and Others 1984, 2003.  All rights reserved.
   U.S. Government Users Restricted Rights - Use, duplication or disclosure
     restricted by GSA ADP Schedule Contract with IBM Corp.
   Licensed Materials - Property of IBM

   To cancel the CWBPING request, press CTRL-C or CTRL-BREAK
   I - Verifying connection to system 10.100.91.10...
   I - Successfully connected to server application: Central Client
   I - Successfully connected to server application: Network File
   I - Successfully connected to server application: Network Print
   I - Successfully connected to server application: Data Access
   I - Successfully connected to server application: Data Queues
   I - Successfully connected to server application: Remote Command
   I - Successfully connected to server application: Security
   I - Successfully connected to server application: DDM
   I - Successfully connected to server application: Telnet
   I - Connection verified to system 10.100.91.10
   
-----

-Adam
Avatar of istate

ASKER

guys:

here is the joblog from my most recent attempt at starting Management Central server.

-----

5722SS1 V5R3M0 040528                           Job Log                             ISERIES  01/15/07 08:40:31          Page    1
 Job name . . . . . . . . . . :   QYPSJSVR        User  . . . . . . :   QYPSJSVR     Number . . . . . . . . . . . :   871975      
 Job description  . . . . . . :   QYPSJOBD        Library . . . . . :   QSYS                                                      
SGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST  
PF1124    Information             00   01/15/07  08:40:21.794600  QWTPIIPP     QSYS        061C     *EXT                    *N    
                                    Message . . . . :   Job 871975/QYPSJSVR/QYPSJSVR started on 01/15/07 at                      
                                      08:40:21 in subsystem QSYSWRK in QSYS. Job entered system on 01/15/07 at                    
                                      08:40:21.                                                                                  
PI1125    Information             00   01/15/07  08:40:21.794920  QWTPCRJA     QSYS        0108     *EXT                    *N    
                                    Message . . . . :   Job 871975/QYPSJSVR/QYPSJSVR submitted.                                  
                                    Cause . . . . . :   Job 871975/QYPSJSVR/QYPSJSVR submitted to job queue                      
                                      QSYSNOMAX in QSYS from job 871970/QUSER/QZRCSRVS. Job                                      
                                      871975/QYPSJSVR/QYPSJSVR was started using the Submit Job (SBMJOB) command                  
                                      with the following job attributes: JOBPTY(5) OUTPTY(5) PRTTXT()                            
                                      RTGDTA(RUNPTY10) SYSLIBL(RBTSYSLIB  QSYS       QSYS2      QHLPSYS                          
                                      QUSRSYS) CURLIB(*CRTDFT) INLLIBL(QGPL       QTEMP      ICIOBJ     ICIDB                    
                                      ICIQRY     LAWDBF7    LAWSON7    VSTAX.D    VSTAX.O    ICISRC     VSTAX.S                  
                                      IBTMOD     IBTCOM     IBTDTA     JDFOBJ     IBTSEC     ICITOOLS   EDI4XXDTA)                
                                      LOG(4 00 *NOLIST) LOGCLPGM(*NO) INQMSGRPY(*RQD) OUTQ(/*DEV)                                
                                      PRTDEV(PD9909106) HOLD(*NO) DATE(*SYSVAL) SWS(00000000) MSGQ(/*NONE)                        
                                      CCSID(37) SRTSEQ(*N/*HEX) LANGID(ENU) CNTRYID(US) JOBMSGQMX(16)                            
                                      JOBMSGQFL(*WRAP) ALWMLTTHD(*YES) INLASPGRP(*NONE) SPLFACN(*KEEP).                          
NONE      Request                      01/15/07  08:40:21.827016  QWTSCSBJ                 *N       QCMD        QSYS        0189  
                                    From user . . . . . . . . . :   ARAY                                                          
                                    Message . . . . :  -QSYS/CALL PGM(QSYSDIR/QYPSJSVR) PARM('1')                                
CH3203    Escape                  60   01/15/07  08:40:31.229800  < aCreateJVM             000928   QJVAJNI     QSYS        *STMT
                                    From Program  . . . . . . . :   JavaCreateJVM                                                
                                    To module . . . . . . . . . :   QJVAJNI                                                      
                                    To procedure  . . . . . . . :   JNI_CreateJavaVM                                              
                                    Statement . . . . . . . . . :   831                                                          
                                    Message . . . . :   Function error X'1716' in machine instruction. Internal                  
                                      dump identifier (ID) 01005841.                                                              
                                    Cause . . . . . :   The machine instruction that was running failed. Time                    
                                      stamp is 01/15/07 08:40:31, error code is X'1716', error class is 0, device                
                                      number is X'0000'. The error class indicates how the damage was detected:                  
                                      0000-unspecified abnormal condition; 0002-logically invalid device sector;                  
                                      0003-device failure. For error class 0003, the device number identifies the                
                                      failing device, or contains zero if main storage failed. Recovery  . . . :                  
                                      Start problem analysis (ANZPRB command).                                                    
VAB544    Diagnostic              40   01/15/07  08:40:31.274096  QJVAUTLJVM   QSYS        *STMT    QJVASYS     QSYS        *STMT
                                    From module . . . . . . . . :   QJVAUTLJVM                                                    
                                    From procedure  . . . . . . :   JvaSendMsg                                                    
                                    Statement . . . . . . . . . :   16                                                            
                                    To module . . . . . . . . . :   QJVAIBMJNI                                                    
                                    To procedure  . . . . . . . :   IBM_CreateJavaVM                                              
                                    Statement . . . . . . . . . :   90                                                            
                                    Message . . . . :   Unmonitored exception received.                                          
                                    Cause . . . . . :   Received an unmonitored exception. Recovery  . . . :   See                
                                      the messages listed on this display or in the job log (use the DSPJOBLOG                    
                                      command to display the job log).  Correct any errors and try the command                    
                                      again.                                                                                      
PF3CF2    Escape                  30   01/15/07  08:40:31.285280  QYPSJSVR     QSYSDIR     *STMT    QYPSJSVR    QSYSDIR     *STMT
                                    From module . . . . . . . . :   QYPSJHELPR                                                    
                                    From procedure  . . . . . . :   sendEscapeMessage__12ypsJvmHelperFRC10ypsJStri                
                                      ngT1                                                                                        
                                    Statement . . . . . . . . . :   16                                                            
5722SS1 V5R3M0 040528                           Job Log                             ISERIES  01/15/07 08:40:31          Page    2
 Job name . . . . . . . . . . :   QYPSJSVR        User  . . . . . . :   QYPSJSVR     Number . . . . . . . . . . . :   871975      
 Job description  . . . . . . :   QYPSJOBD        Library . . . . . :   QSYS                                                      
SGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST  
                                    To module . . . . . . . . . :   QYPSJHELPR                                                    
                                    To procedure  . . . . . . . :   sendEscapeMessage__12ypsJvmHelperFRC10ypsJStri                
                                      ngT1                                                                                        
                                    Statement . . . . . . . . . :   16                                                            
                                    Message . . . . :   Error(s) occurred during running of IBM_CreateJavaVM  API.                
                                    Cause . . . . . :   Call your service organization and report the problem.                    
                                      Materials to accompany the problem are: -- Job log of the failing API. --                  
                                      Actual parameters specified on the API.                                                    
EE9901    Escape                  30   01/15/07  08:40:31.287136  QLEAWI       QSYS        *STMT    QCMD        QSYS        01B7  
                                    From module . . . . . . . . :   QLEDEH                                                        
                                    From procedure  . . . . . . :   Q LE leDefaultEh                                              
                                    Statement . . . . . . . . . :   168                                                          
                                    Message . . . . :   Application error.  CPF3CF2 unmonitored by QYPSJSVR at                    
                                      statement 0000000016, 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                                          
                                      sendEscapeMessage__12ypsJvmHelperFRC10ypsJStringT1. The program was stopped                
                                      at the high-level language statement number(s) 0000000016 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.                                                                      
PC2402    Completion              50   01/15/07  08:40:31.293016  QCMD         QSYS        0605     *EXT                    *N    
                                    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.                              
PF1164    Completion              00   01/15/07  08:40:31.294000  QWTMCEOJ     QSYS        00C9     *EXT                    *N    
                                    Message . . . . :   Job 871975/QYPSJSVR/QYPSJSVR ended on 01/15/07 at                        
                                      08:40:31; 1 seconds used; end code 20 .                                                    
                                    Cause . . . . . :   Job 871975/QYPSJSVR/QYPSJSVR completed on 01/15/07 at                    
                                      08:40:31 after it used 1 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.ibm.com/eserver/iseries/infocenter.                                              
                                                                                                                                 

-----

-Adam
Adam:

First glance at the joblog says that this is for IBM support, but it's not certain since it involves the JVM.

Besides the joblog, it appears that your host entry is incorrect for your system. It _probably_ should look this way:

Internet Address . . . . . . . . . . . :   10.100.91.10
 Host names:
   Name . . . . . . . . . . . . . . . . :   ISERIES.ISTATE.COM
   Name . . . . . . . . . . . . . . . . :   ISERIES

Note that the alias has been switched with the host name. Assuming that your CFGTCP option 12 shows 'Host name' as ISERIES and 'Domain name' as ISTATE.COM, then this is correct. It _might_ not make any difference for two reasons.

1. IBM has been relaxing requirements over the past couple releases. Technically, your fully qualified host name is "ISERIES.ISTATE.COM" and "ISERIES" is simply an alias. In the past, some of the TCP/IP servers would pull the fully-qualified host name and look for it in the hosts table to determine the appropriate IP address. However, the server code wouldn't look at aliases. Therefore, in your case, it would look for ISERIES.ISTATE.COM but only see ISERIES. Although that's a precise adherence to TCP/IP standards, it's not very forgiving. Servers have become more forgiving recently. (I'd still set my hosts table to meet precise standards as far as I understood them.)

2. The joblog refers to "damage". Although you can possibly locate the object that suffered the damage, IBM support should be contacted to verify the best way to do so as well as to ensure that damage is properly corrected (if it actually exists.) It's possible that this is simply a PTF issue.

Tom
Tom, do you think it would be worthwhile to re-install JV1 + cume + Java group?
Barry
Barry:

I'd wonder first about the history of related group PTFs. I.e., have any been applied at all? Was one applied recently? (...which makes me wonder "Has Management Central ever been successfully run on this system?") Then I'd wonder about cumes.

But I wouldn't be surprised if IBM suggested exactly the course you described.

Java is closely tied to ASCII. Lots of streamfile objects, etc. That makes the historical meaning of "damage" get cloudy. Maybe it isn't "damage" in the traditional sense, but procedures higher up the stack are falling back on messages that don't account for recent changes in lower level procs. Maybe it's just a streamfile that got 'touch'd by an errant QSH command and has an incorrect CCSID. Maybe...?

And maybe there was a true "damage" hit somewhere.

I'd _hope_ that uninstall/reinstall/cume/groups would fix it. But I'd also want to ensure that any cause of object damage was properly tracked down and resolved.

Tom

p.s. You musta been on vacation a few days. Welcome back if so.
Avatar of istate

ASKER

Okay, let me give you guys a little more background. I am relatively new to the company (2 years), and the system administrator duties basically fell in my lap when all the other analysts above me left the company.

Now, since I've had these responsibilities, no PTF's have been installed. I'm not sure how up to date we stayed on these previously, but I'm guessing whatever was necessary was installed when we upgraded to the 520, which was in September of 2005.

To my knowledge, Management Central has never worked. We do have IBM support, so I will give them a call as per your advice. In the mean time, which PTF's should I be looking for?

-Adam
Hi Adam,

Your Java problem may well be fixed by PTFs.

You can order fixes through Fix Central:
http://www-304.ibm.com/jct01004c/systems/support/i/fixes/orderfix.html

You need to order the current cumulative package, which will trigger the Database and Hiper groups as well. You should also order the Java group, and any other PTF groups that apply to your system.

Tom, no vacation but I have been busier than a one legged man at a butt kicking contest, so many systems, so little time....
Barry
Avatar of istate

ASKER

I'm downloading the current cumulative PTF right now. We are currently on level 5207, and the current one is 6255. Hopefully this does the trick, I'll keep you informed.

-Adam
Adam:

Extra background on PTFs... They can be ordered/applied in multiple ways.

A PTF involves a "fix" for particular problem. Often they're simple restores of individual operating system programs. A "cumulative (cume) PTF package" is a rollup of general PTFs that pretty much apply to every system. A "group PTF package" is a set of PTFs that affect particular product areas such as Java or DB2/SQL.

Because every system is different, with different workloads and different products installed, there can be hundreds of individual PTFs that are only meaningful for systems with certain combinations.

A system running Websphere Application Server with high transaction rates might apply appropriate performance PTFs for WAS. But if those PTFs work by shifting internal resources away from other system functions, they won't usually be appropriate for general systems. As such, those PTFs would probably never get included in any cume PTF package. IBM wouldn't want sites complaining about interactive performance problems that don't run WAS heavily. If included in a cume, they'd tend to get applied on every system that loaded the most recent cume.

Or a PTF that directly supports how the RPG compiler optimizes embedded SQL...? Sites that don't need the SQL Developer Kit product probably don't want the PTF. So, it gets put in the DB2 group PTF but possibly never put in a general cume package.

In your case, the relevant "group PTF" might be the Java group. For V5R3, the group PTF number is SF99269. For V5R4, it's SF99291. To see what your current "group" levels are, run the WRKPTFGRP command.

In short, the cume that you're applying might have nothing to do with your problem. (But it's generally good to get it applied because it will 'fix' any underlying issues anyway.)

Tom
Avatar of istate

ASKER

After looking through the list of available PTF's and comparing it to the PTF Groups I have currently, I noticed I do not have PTF group SF99314 - TCP/IP Group PTF installed.  Do you think this one might be necessary to fix my problem?

I was planning to order the following PTF groups:

   Cumulative PTF Package C5207530 (SF99530) - Current level 5207
   Group Hiper (SF99529) - Current level 59
   Java (SF99269) - Current level 6
   Performance Tools (SF99099) - Current level 2

I wasn't sure on the Group Hiper, as Barry mentioned that the Cume will trigger the Database and Hiper groups. Are you referring to groups SF99529 and SF99503?
Avatar of istate

ASKER

I seem to be having problems with Fix Central. I get all the way to where I enter my address information and it doesn't seem to be doing anything (it's java based so it's hard to tell.  Is there a better/easier way to order PTF's?  Again, I'm new at this.

-Adam
ASKER CERTIFIED SOLUTION
Avatar of Member_2_276102
Member_2_276102

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of istate

ASKER

here's an update:

i just received the PTF's i ordered. it looks like a got duplicates of some of them (maybe the online ordering was working, i just couldn't tell).  i will be setting up a time with our support people to get these installed.

-adam
Forced accept.

Computer101
EE Admin