Re: Anybody have any ideas why the WSERVICE server won't start?

James

I'd expect to see at east one job initiating when I started the server
so my first port of call would be to check for jobs starting (and
ending I guess) at the time I was trying to start the server. I'd get
the job details and go hunting for a job log. On occasion in these
situations I've had to change the IBM supplied JOBD to ensure a job
log is generated but thats where I'd start.

If you can't see any jobs then the next place to start would be any
internal logs for the server itself - I'd probably expect to find
these in the IFS somewhere probably under a QIBM directory somewhere.

Just guessing but that's what I'd do if I was in your shoes.

On Mon, Sep 20, 2010 at 6:30 AM, <jamesl@xxxxxxxxxxxxxxxxx> wrote:

To summarize:

After installing ....JV1 option 6 (but neither re-IPLing, nor re-applying
that massive PTF group), the IWS server tutorial let me go past the point
where it had complained before, all the way to the end of the tutorial.

After going through the IWS tutorial, seemingly successfully, I had a new
web service (ConvertTemp2, I think it is) on the WSERVICE server. But
neither the WSERVICE application server (port 10000, I think) nor the
WSERVICE HTTP server (10010, unless I have the two mixed up) will come up.

And "Manage All Servers" seems to be very unreliable about recognizing
whether ADMIN (2001) is up, even though I couldn't be looking at it if it
weren't.

Suggestions?  H E L P ! !