Re: Can't keep QEJBADMIN running -- JAVA400-L


Joe,
The for the more general case of the MCH74A0, you should look at the
contents of any QPRINT spooled files associated with the QEJBADMIN job, and
more importantly (if it exists) the contents of file
/QIBM/UserData/WebASAdv/default/logs/tracefile. If you see
'UnknownhostException' or 'Unable to register with location service
daemon', then you most likely have a TCP/IP configuration problem (really
doesn't look like it based on the info you posted - but you never know).
With the latter message, a couple of customers have recently run into
problems when they have configured client socks and mistakenly added a
first entry that makes all requests into the box be routed to a different
IP address to be handled.

If you have not installed any group PTF for 3.5, that is most likely your
problem.  When 3.5 shipped there were a set of individual PTFs that were
required (and listed on the PTFs page of our web site). Unfortunately, once
we came out with our first group PTF we overlaid that list (not to say we
don't have it, but the product really required the 3.5.1 level to be fully
functional so we did not want to encourage running just 3.5.0 with the
minimum PTFs). At any rate, you would still be missing PTFs.

I am pretty sure you cannot get the group PTF via iPTF since it is so large
(includes three other group PTFs, the WebSphere PTFs, and a handful of
additional PTFs not in any other group).

I think it would be great if when someone ordered the product, they were
also shipped the latest group PTF.  Have you tried asking when you order
the product if you can also put in an order for the group PTF? I am pretty
sure I have asked in the past why the latest group can't just be shipped
when someone orders the product, and was told that it couldn't be - but I
will check again. Not something I have alot of clout on though.

Our new install and initial configuration guide for 3.5 (see first page of
the on-line documentation off our web site) does document (both in the
Planning section and the detailed steps) that you should/must get the
latest group PTF for the product when installing (and if no group PTF is
available get the PTFs listed on the PTFs page). So if new users read the
documentation maybe they can be helped.
See the What's New page on our Web Site for more information and links to
the doc and PDF.

So to recap:
   Option 10 and 12 of CFGTCP look file, check the QPRINT spooled files and
   the tracefile file in /qibm/userdata/webasadv/default/logs. Make sure
   you put the latest group PTF on.
   Don't use iPTF to get the Group PTF. The group is too large. We can't
   help that, and it is generally to our customers benefit that we ship
   what we know they need. We could require that you get several PTFs
   individually (i.e. breakup our group), but I don't think that will
   benefit the majority of our customers and will create more room for
   mistakes.
   Try using the new install/initial config doc. and see what you think.
   There is a Feedback link you can use to provide feedback on it. I
   believe this link is available thoughout our web site, and can be used
   for constructive criticism/comments and, of course, outrageous flattery.
   I am posting a separate note which will contain a warning that the 3.5.3
   group PTF for Standard Edition contains the wrong workstation FixPaks
   for the admin console (they are for 3.5.2 not 3.5.3), so , for now, you
   must get the FixPak3 for the admin console from the web site listed in
   the 3.5.3 release notes. The Advanced Edition group PTF contains the
   correct FixPak3 files.  We will be putting out a PTF for Standard
   Edition Monday or Tuesday with the correct FixPaks and updating the
   3.5.3 release notes with appropriate information about the problem.

Thanks,
Frances Stewart
WebSphere Application Server for iSeries 400
IBM Rochester


"Joe Pluta" <joepluta@PlutaBrothers.com>@midrange.com on 04/18/2001
11:33:14 PM

Please respond to JAVA400-L@midrange.com

Sent by:  owner-java400-l@midrange.com


To:   <JAVA400-L@midrange.com>
cc:
Subject:  Can't keep QEJBADMIN running



Thought I'd crosspost this tidbit.
----

Hey folks!  I'm close to getting WAS3.5 running, but QEJBADMIN won't stay
up.  I'm getting an error, MCH74A0 in QJVAJNI.  (I'm re-IPLing as we speak,
just to make sure there's nothing flaky because I just installed WebSphere,
but let me move forward despite that).

I looked on the IBM website, and lo and behold, got exactly the problem:

----------
If these jobs do not stay active, check in the QEJBADMIN job log for a
message MCH74A0 T/QJVAJNI.

This is usually caused by either the Domain information not being entered
or
the Fully Qualified Domain name not existing in the Host Table on OS/400.

Make sure OS/400 has information filled in on CFGTCP, option 12, for the
Host and Domain Names. Assure that OS/400 has this Fully Qualified Domain
Name (host.domain) associated with an address on CFGTCP, option 10.
---------

Well, this looks like EXACTLY the problem!  I'm saved!

Or maybe not.  Because my option 10 and option 12 seem to be just fine.
They look like this:

                      Work with TCP/IP Host Table Entries
                                                             System:
S105GPCM
 Type options, press Enter.
   1=Add   2=Change   4=Remove   5=Display   7=Rename

      Internet         Host
 Opt  Address          Name

      10.1.1.65        PBD270.PLUTABROTHERS.COM
                       PBD270
      127.0.0.1        LOOPBACK
                       LOCALHOST



Bottom
 F3=Exit   F5=Refresh   F6=Print list   F12=Cancel   F17=Position to

                        Change TCP/IP Domain (CHGTCPDMN)

 Type choices, press Enter.

 Host name  . . . . . . . . . . .   'PBD270'

 Domain name  . . . . . . . . . .   'PLUTABROTHERS.COM'



 Host name search priority  . . .   *LOCAL        *REMOTE, *LOCAL, *SAME
 Domain name server:
   Internet address . . . . . . .   *NONE



Bottom
 F3=Exit   F4=Prompt   F5=Refresh   F10=Additional parameters   F12=Cancel
 F13=How to use this display        F24=More keys


According to this, I have a name, PBD270.PLUTABROTHERS.COM, that is linked
to my TCP/IP address of 10.1.1.65 (which points to my ethernet card).  So,
I
look for more information and find that I probably need a group PTF (which
for some unknown reason was NOT shipped when I ordered WebSphere).  I tried
logging into the iPTF system (even though I have a feeling I can't get the
Group PTF via iPTF).  No matter, it didn't recognize my password.  I tried
re-registering, but the US Registration isn't working.  So I've
re-registered via the non-US registration (although I was able to enter my
country as United States), and now I'm waiting for the registration to go
through.  No luck so far.

And of course, there's no darned iPTF capability for the group PTF.

If IBM were TRYING to make it difficult to get going with WebSphere, they
couldn't do a much better job than this.

Sheesh

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---



+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---