× 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.




We were purely doing the shutdown with a vary off of the *NWS on the green
screen. It was sitting there until the wait limit was reached (default of
15min) and then abending. We were able to ID the problem: one the one
problematic IXS, the three Windows services that begin with 'iSeries' were
not present. The IBM tech had a set of DOS window commands that we issued
to rebuild and reinstall these services and that fixed the issue.

He said it's a documented issue within their support help, but that it's
less common at V5R4 than V5R3. So if you run into anything similar, check
out your Windows services and look to make sure the ones beginning with
'iSeries' are present and started.




Pete Helgren
<Pete@xxxxxxxxxx>
Sent by: To
midrange-l-bounce Midrange Systems Technical
s@xxxxxxxxxxxx Discussion
<midrange-l@xxxxxxxxxxxx>
cc
07/13/2007 12:11
PM Subject
Re: IXS servers not shutting down
properly after V5R4
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






Chad,

When you say "not shutting down properly", at what point are you seeing
the abend? And what is the error message? I just upgraded a customer
about a month ago and they have both an IXS and IXA but I can't say that
we have shut down the hardware. I have warm booted after applying the
usual Microsoft updates and it has rebooted with no ill effects.

Are you issuing a shutdown in Windows and then a vrycfg at the command
line? I just want to know the sequence so I know what to look for.

Pete


ChadB@xxxxxxxxxxxxxxxxxxxx wrote:
Anyone else have trouble with their IXS servers not shutting down
properly
after upgrading to V5R4? Now that we are at V5R4 and have synched our
IXSs
to the new PTF level on the server side, they are not shutting down
properly - they reach the limit specified on their *NWSD descriptions (15
min default) and then are ended abnormally and throw an error on the
*LINXX
type hardware resource. We are at latest cume, groups, and have the
integration group installed. I'm working with IBM on the problem, but
was
wondering if anyone else has seen this...

--
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 ...

Follow-Ups:
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.