× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2014

RE: Trying to start host servers on a box. Getting errors.

Here's where System I Navigator comes into play. If you have that you can
go to the TCP servers section. Find the server for the database connections
and right click on it. It should show the job logs for those jobs. You
should also be able to start them from there and then watch them as they
start.

That interface is in the new *ADMIN server if you have PTF groups from about
October or so on the box. Get to that with http://yourserver:2001.
Assuming of course you have the *ADMIN server started.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Tuesday, February 11, 2014 6:51 PM
To: Midrange Systems Technical Discussion
Subject: Re: Trying to start host servers on a box. Getting errors.

On 2/11/14 4:12 PM, Jim Oberholtzer wrote:
This is one of those where the messages for the routes do not make a
difference. When these servers start, part of the process is to be
sure all of the needed entries are there so this happens all the time.
When I just did it on my V7 box the same messages were displayed,
except for the " Error occurred starting server daemon job" that is after
route 200 and before 600.
Those two messages are most likely the salient ones.

Can you show the 2nd level text for them? Which daemons did not start?

Thanks.
Message ID . . . . . . : PWS3005
Date sent . . . . . . : 02/11/14 Time sent . . . . . . :
15:11:00

Message . . . . : Error occurred starting server daemon job.

Cause . . . . . : An error has occurred starting the *FILE server daemon
job.
Recovery . . . : See messages listed previously. Determine the cause
of
the error, correct the problem and run the command again.
and
Message ID . . . . . . : PWS3005
Date sent . . . . . . : 02/11/14 Time sent . . . . . . :
15:11:01

Message . . . . : Error occurred starting server daemon job.

Cause . . . . . : An error has occurred starting the *DATABASE server
daemon
job.
Recovery . . . : See messages listed previously. Determine the cause
of
the error, correct the problem and run the command again.

No joblogs were produced. The above certainly explains why a JDBC connection
couldn't be established, but I haven't a clue what to do about it.

The only port restrictions on the system are on ports 137-139. They couldn't
have anything to do with this, could they?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.