Re: Next IPL Abnormal

As I stated on Friday (below) the Next IPL=Abnormal is apparently related
to the QJVACMDSRV job ending abnormally. This job, in this instance, is
directly related to QIBMHELP server in the QSYSWRK subsystem:

Subsystem/Job User Type CPU % Function
Status
QIBMHELP QIBMHELP BCH .0 PGM-STRECLIPSE TIMW
QJVACMDSRV QIBMHELP BCI .0 JVM-org.eclips JVAW

Neither process is running on our backup system which has a Next IPL=Normal
status. I even re-IPLed that server this morning and still nothing related
to these services.

Thanks to a message by Jim Franz in the archives I found an IBM Technical
document (http://preview.tinyurl.com/qibmhelp) about the QIBMHELP server.

Using the QShell command mentioned in the document did *not* start QIBMHELP
on the backup system. Neither did the command STRTCPSVR *IBMHELP.
Apparently that server is immune to any help. .-) Oh, and I checked the
QUSRSYS/QATOCSTART file and QIBMHELP has a status of *Yes for AutoStart on
that server. Admittedly I'm confused as the only thing I found about
QIBMHELP itself as " Is an Eclipse-based Information Center that is used to
deliver Help documentation." In the 5.4 InfoCenter. What kind of help is
beyond me since Help works in both CL and WDSc on the backup server, which
is not running QIBMHELP.

Since my goal is to try to prevent an abnormal IPL by determining why this
one went abnormal on the production system, it seems that changing the
QATOCSTART autostart option to *No would be the route to go - unless someone
has a reasoned, strenuous objection to that course of action.

Jerry C. Adams
IBM System i Programmer/Analyst
There will be a procession next Sunday afternoon in the grounds of the
Monastery; but if it rains in the afternoon, the procession will take place
in the morning. - Announcement read to a church congregation
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Friday, August 13, 2010 3:55 PM
To: Midrange Systems Technical Discussion
Subject: RE: Next IPL Abnormal

Pete,

Thanks. No one can ENDJOBABN, but I have been going over the History
reports from both machines and doing some compares.

There were several jobs on both that ended with code 30 (The job ended
abnormally). But since one machine is still at Normal and these are the
same jobs, I doubt they caused the production server to go into Abnormal.

I did find job 417382/QIBMHELP/QJVACMDSRV that ended with code 80 (The job
ended (ENDJOBABN command)), which is probably the culprit. Why it went
abnormal is a mystery.

I've got more research to do when I get back Monday.

Jerry C. Adams
IBM System i Programmer/Analyst
I don't see, Mr. Speaker, why we should put ourselves out of the way to
serve posterity. What has posterity ever done for us? - Sir Boyle Roche
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Friday, August 13, 2010 3:12 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Next IPL Abnormal

Is anyone using the ENDJOBABN command? That will trip the next IPL to be
abnormal. You might want to audit that command and see if anyone is using
it.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn:
http://www.linkedin.com/groups?gid=2206093



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Friday, August 13, 2010 12:33 PM
To: Midrange Systems Technical Discussion
Subject: Re: Next IPL Abnormal

I am going to guess, look through your history logs and see how many IPL's
took place. I believe until you get a normal IPL this flag value will be
tripped abnormal.

On Fri, Aug 13, 2010 at 11:54 AM, Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
wrote:

I have a program that checks the QABNORMSW system value ("Next IPL will

be

Normal or Abnormal"). This runs every evening at about 1600. Since 3

July,

when I applied the latest cume (5.4), it has been Normal. Last night it
reported back as Abnormal.

The only "incident" between Wednesday night and last night was a power
failure. I wasn't here, but my boss used PWRDWNSYS *Immed. We actually
have two [2] 520's that are mirror images (although no twinax devices are
plugged into the second/backup system). The second system was, also,
powered down at the same time, but its next IPL will be Normal. Turns

out

that the local utility decided to give us some juice before he left do he
powered them back up using the little white button. Everything looked

fine

when I came in yesterday morning about 0530; all overnight jobs had run
successfully and the order entry lines were up and functioning.

I'm printing the History for the period using *PRTSECLVL, but I don't

know

what I should be looking for. Any clues/suggestions would be

appreciated,

Jerry C. Adams
IBM System i Programmer/Analyst
We are in favor of a law which absolutely prohibits the sale of liquor on
Sunday, but we are against its enforcement. 1920's Democratic platform

in

Syracuse, NY
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

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

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



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

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

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