System i Navigator connection error to Central Management System.

85 pts.
Tags:
AS/400
i5
iNavigator
iSeries Navigator
iSeries Navigator Application Administration
I am getting an error message in System i Navigator when I try to connect to Central Management System. "Unable to complete the connection to central system `system name`". I am trying to retreive the System Operator Messages. Also under Basic Operations - Messages click on the bottom panel on View System Operator Messages, nothing comes up. New window opes up, but it is blank. I have QSECOFR access, but half of the stuff gives me error message, ie trying to verify TCP/IP server properties, no go. Keep saying unable to connect.I have seen some Java related errors as well.  Iam running V6R1M0. Anyone has any experience with iNavigator? I was never able to get this right. I even tried to start the TCPIP server on the i5, no luck it says STRTCPSRV command not found in *LIBL. I really need to be able to get these System Opeator Messages, because it is very painful to scroll over hunders of messaged on the i5. Thank you for you r help in advance. Csaba

Software/Hardware used:
AS400, i5, iSeries Navigator
ASKED: May 28, 2010  4:44 PM
UPDATED: June 16, 2010  10:58 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    ...it says STRTCPSRV command not found in *LIBL. Try STRTCPSVR. And what does the QYPSJSVR joblog show for the MgtC problems? i 6.1 brought a couple changes to how MgtC interacts with some host servers, particularly the Remote Command server. (I haven't heard from IBM why MgtC needs to run its commands through the Remote Command server when they are on the same system. I'd expect MgtC simply to execute commands directly.) The MgtC joblog might show hints. Tom
    125,585 pointsBadges:
    report
  • Chabsta
    Yes that is the impression I got from IBM. They said I had errors with JavaToolBox as well. They are sending R1 PTF's out to install, supposed to fix all this. Also they implemented a build in delay for TCPSRV when IPL is preformed. I tried to do FULL SAVE of course it wont do it cause TCPSRV got locked up. This is the result of IMMED option when issue restart command even after ENDSBS *ALL was done. Will see, I just wanted get to the System Operator messages. I misspelled STRTCPSVR, that is STRTCP command anyway just found out. That works just fine. QYPSJSVR joblog looks good no error messages. I tried STRTCPSVR SERVER(*MGTC) so I got the message "MGTC server not started." Here is the joblog: QSYS/CALL PGM(QSYSDIR/QYPSJSVR) PARM('1') JVM properties were loaded from a properties file. Java Virtual Machine is Classic. JVM properties were loaded from a properties file. Start Job 212083/QUSER/QSQSRVR used for SQL server mode processing. Job 212390/QUSER/QSQSRVR used for SQL server mode processing. Job 212389/QUSER/QSQSRVR used for SQL server mode processing. Job 212402/QUSER/QSQSRVR used for SQL server mode processing. Job 212401/QUSER/QSQSRVR used for SQL server mode processing. Job 212408/QUSER/QSQSRVR used for SQL server mode processing. Job 212407/QUSER/QSQSRVR used for SQL server mode processing. Job 212412/QUSER/QSQSRVR used for SQL server mode processing. Job 212411/QUSER/QSQSRVR used for SQL server mode processing. Management Central is enabled as a provider of protocol 1024. Management Central is enabled as a verifier of protocol 1024. Object QYPSJDTAQ type *DTAQ created in library QMGTC2. Management Central server McServer on port 5544,5555 started as Central. Job 212526/QUSER/QSQSRVR used for SQL server mode processing. Job 212525/QUSER/QSQSRVR used for SQL server mode processing. Job 212594/QUSER/QSQSRVR used for SQL server mode processing. Maybe i have to forward these ports as well, but MGTC not starting anyway. See what these new PTF's will do. Keep you posted, still any idea, please share it with me. Thank you very much. Csaba
    85 pointsBadges:
    report
  • TomLiotta
    ...but MGTC not starting anyway. It looks to me as if it is starting. So, it shouldn't be that it isn't starting -- the problem should be that you can't connect to it. From the same PC, can you start the iSeries Access emulator? If you can, do you connect by name or by IP address? If by name, is it the same name that you use for the 'central system'? Is it located from your PC by DNS or by an entry in the PC hosts table? (Do you have an entry in the PC hosts table?) Since this is i 6.1, is it a new system? It should be fairly new, but you might have had it for quite a few months. How do the other servers look? Do all host servers report okay? Does CWBPING from the PC report clean connections to the servers? Try ENDTCPSVR *MGTC followed by STRTCPSVR *MGTC after a few seconds to be sure it had time to end cleanly. Does the connection still fail? I've seen failures from having different servers start in a different order -- MgtC can be very sensitive to how the *DATABASE server is handled for example. The first thing that I would do is ensure that my 'central system' TCP/IP configuration was completely correct. That means a strict conformance to the basic RFCs. Three CFGTCP options should be in agreement:
    1. Option 1 should show an ACTIVE interface in addition to the *LOOPBACK interface.
    2. Option 10 should show that that ACTIVE interface has a corresponding entry in the iSeries hosts table.
    3. Option 12 should show a Host name and a Domain name. The Domain name should be a valid domain name.
    The combination host.domain should be the first name listed on the hosts table entry for the IP address of that ACTIVE interface. The option 12 Host name search priority should be *LOCAL to ensure that the entry in the iSeries hosts table is the one that is in effect. Those might all be changed later, but that's how they should be in order to do some testing. Once you can get things working with that configuration, you have a good chance of determining if changes will cause problems. I've seen failures because the host.domain combination isn't the first name listed. And I've seen failures because a Domain name wasn't valid. And I've seen failures because *REMOTE DNS lookups returned incorrect addresses. Do you have any exit programs registered against the *DATABASE, *RMTCMD or *SIGNON servers? I've seen failures in i 6.1 from the Management Central CCSID changes. Lots of possibilities. It's probably best to start with TCP/IP fundamentals and then narrow the problem area down. That's especially true when there are no error messages that you can locate. The problem might be in any of the other servers that MgtC connects to. Tom
    125,585 pointsBadges:
    report
  • Chabsta
    This is what I got so far. All PTFs installed, after 8 hours and 3 IPLs. Java error still exists. QSH Command Entry $ > cd /qibm/proddata/http/public/jt400/lib $ > export -s CLASSPATH=.jt400.jar $ > java utilities.AboutToolBox java.lang.NoClassDefFoundError: utilities/AboutToolBox at java.lang.Throwable.<init>(Throwable.java:195) at java.lang.Error.<init>(Error.java:49) at java.lang.LinkageError.<init>(LinkageError.java:36) at java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:40 ) $ Content of the jdk14: $ ls -al /QIBM/ProdData/Java400/jdk14/lib/ext total: 76 kilobytes drwxr-sr-x 2 QSYS 0 8192 Jun 27 2009 . drwxr-sr-x 6 QSYS 0 53248 Jun 6 12:30 .. lrwxrwxrwx 1 QSYS 0 42 Jun 27 2009 dnsns.jar -> /QIBM/P rodData/Java400/jdk14/lib/dnsns.jar lrwxrwxrwx 1 QSYS 0 51 Jun 27 2009 ibmjceprovider.jar - > /QIBM/ProdData/Java400/jdk14/lib/ibmjceprovider.jar lrwxrwxrwx 1 QSYS 0 44 Jun 27 2009 ldapsec.jar -> /QIBM /ProdData/Java400/jdk14/lib/ldapsec.jar lrwxrwxrwx 1 QSYS 0 47 Jun 27 2009 localedata.jar -> /Q IBM/ProdData/Java400/jdk14/lib/localedata.jar $ I deleted and restored, recreated files in the /OS400/MGTC folder, still no love. They gave me an update for Accessi for Windows, iNavigator. Sending more PTFs. CPFB972 Diagnostic 40 06/13/10 20:28:04.270223 QYJSPART QSYS *STMT QYJSPART QSYS *STMT From module . . . . . . . . : QYJSPNTV From procedure . . . . . . : Java_com_ibm_as400_access_NativeMethods_runPro gram Statement . . . . . . . . . : 81 To module . . . . . . . . . : QYJSPNTV To procedure . . . . . . . : Java_com_ibm_as400_access_NativeMethods_runPro gram Statement . . . . . . . . . : 81 Thread . . . . : 00005589 Message . . . . : Management Central object not found on server. Cause . . . . . : A Management Central object of type com.ibm.mc.client.definition.McEndpointSystem, name xxx.xxx.dyndns.org, and owner QSECOFR could not be found. An object with name xxx.xxx.dyndns.org possibly does not exist on the server. Recovery . . . : If the problem persists, contact service. CPFB972 Diagnostic 40 06/13/10 20:28:23.768825 QYJSPART QSYS *STMT QYJSPART QSYS *STMT From user . . . . . . . . . : QSECOFR From module . . . . . . . . : QYJSPNTV From procedure . . . . . . : Java_com_ibm_as400_access_NativeMethods_runPro gram Statement . . . . . . . . . : 81 To module . . . . . . . . . : QYJSPNTV To procedure . . . . . . . : Java_com_ibm_as400_access_NativeMethods_runPro gram Statement . . . . . . . . . : 81 Thread . . . . : 0000007F Message . . . . : Management Central object not found on server. Cause . . . . . : A Management Central object of type com.ibm.mc.client.definition.McEndpointSystem, name xxx.xxx.dyndns.org, and owner QSECOFR could not be found. An object with name xxx.xxx.dyndns.org possibly does not exist on the server. Recovery . . . : If the problem persists, contact service. CPFB945 Diagnostic 40 06/13/10 20:28:24.096712 QYJSPART QSYS *STMT QYJSPART QSYS *STMT From user . . . . . . . . . : QSECOFR From module . . . . . . . . : QYJSPNTV From procedure . . . . . . : Java_com_ibm_as400_access_NativeMethods_runPro gram Statement . . . . . . . . . : 81 To module . . . . . . . . . : QYJSPNTV To procedure . . . . . . . : Java_com_ibm_as400_access_NativeMethods_runPro gram Statement . . . . . . . . . : 81 Thread . . . . : 0000007F Message . . . . : Method not successful. Cause . . . . . : Method isManageableUnique on class com.ibm.mc.client.definition.McDefinitionView could not be completed successfully. Recovery . . . : If the problem persists, contact service. CPFB972 Diagnostic 40 06/14/10 20:28:12.158673 QYJSPART QSYS *STMT QYJSPART QSYS *STMT From module . . . . . . . . : QYJSPNTV From procedure . . . . . . : Java_com_ibm_as400_access_NativeMethods_runPro gram Statement . . . . . . . . . : 81 To module . . . . . . . . . : QYJSPNTV To procedure . . . . . . . : Java_com_ibm_as400_access_NativeMethods_runPro gram Statement . . . . . . . . . : 81 Thread . . . . : 0000629C Message . . . . : Management Central object not found on server. Cause . . . . . : A Management Central object of type com.ibm.mc.client.definition.McEndpointSystem, name xxx.xxx.dyndns.org, and owner QSECOFR could not be found. An object with name xxx.xxx.dyndns.org possibly does not exist on the server. SQ99999 Diagnostic 30 06/14/10 20:28:11.540379 QSQCLI QSYS *STMT QSQCLI QSYS *STMT From module . . . . . . . . : SQLCC From procedure . . . . . . : EXCM0843 Statement . . . . . . . . . : 4637 To module . . . . . . . . . : SQLCC To procedure . . . . . . . : SQLCloseCursor Statement . . . . . . . . . : 10143 Thread . . . . : 0000629C Message . . . . : Error occurred in SQL Call Level Interface Cause . . . . . : A procedure call encountered an error. The error code is 17. Error codes are: 3 -- Program type out of range. 4 -- SQL data type out of range. 9 -- Argument value not valid. 10 -- Function sequence error. 12 -- Transaction operation state not valid. 13 -- Memory management problem. 14 -- Maximum number of handles allocated. 15 -- No cursor name available. 16 -- Handle type for operation not valid. 17 -- Connection no longer available. 21 -- Descriptor or descriptor information not valid. Recovery . . . : Refer to the DB2 for i5/OS SQL Call Level Interface (ODBC) topic collection in the Database category in the i5/OS Information Center book for a complete description of the error. Specifically, look at the procedure that sent the error. This is it for now. Standby. This is only 1 server with 1 LPAR. using DYNDNS with TCP settings. Don't think makes any difference. Csaba
    85 pointsBadges:
    report
  • TomLiotta
    17 — Connection no longer available. Minor note -- that can often mean that the *DATABASE host server was ended or ended and restarted. MgtC gets a connection through SQL CLI when MgtC starts. It later tries to get data again, but the connection has been severed. Not much help for you, I realize. But maybe it's a useful bit for some future time. When you see it in MgtC, it's usually necessary to ENDHOSTSVR/STRHOSTSVR for *MGTC to have it get a new connection to the database. (I'd like MgtC to attempt a reconnection on its own first.) Tom
    125,585 pointsBadges:
    report
  • TomLiotta
    Bug in my code -- ENDHOSTSVR/STRHOSTSVR -- s.b. ENDTCPSVR/STRTCPSVR. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following