Re: Down system????? -- MIDRANGE-L

Boss just stopped by. No IBM as yet. System is up. My workstation
did not get varied on. He varied it on.

Just signed on. Printer devices are varied on and running. Most
displays are not..

Still nothing from IBM. Boss is going to run end of day jobs that
were not completed.

John McKee

On Mon, Mar 18, 2013 at 9:46 AM, <rob@xxxxxxxxx> wrote:

Ok, my next step is not what I recommend. Caution. But, depending on the
urgency of your situation you may want to try the following:
RMTCMD CHGIPLA STRPRTWTR(*YES) STRRSTD(*NO)
RMTCMD PWRDWNSYS DELAY(120) RESTART(*YES)

And I would consider this a "Sev 1, System Down" issue. Being put on call
back in such a situation is fishy. Over an hour is downright rank.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 03/18/2013 10:22 AM
Subject: Re: Down system?????
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Tried starting the controlling subsystem: rmtcmd strsbs bsyobj1/bctl
Already running.

Tried the interactive subsystems, BINTER and BINTER2. Neither was
running.

Make me think the startup program hung or didn't start. Still no
interactive sessions. Maybe some part of tcp is still down?

John McKee

On Mon, Mar 18, 2013 at 9:06 AM, <rob@xxxxxxxxx> wrote:

RMTCMD with a CHGUSRPRF to change them to a printer that is working.
RMTCMD WRKACTJOB OUTPUT(*PRINT)
RMTCMD STRPRTWTR ...
RMTCMD STRSBS QINTER
If it's already started you'll just get that error. If you don't use
QINTER (we don't on our Domino lpars) then you just started an extra
subsystem. No big deal, just deal with it after the emergency.
Now, if you do not allow 5250 to autocreate, and all the workstation
controllers are varied off, that could be interesting. And may affect
printing also.

Again, any chance a qinter killing backup or something may be running?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 03/18/2013 09:56 AM
Subject: Re: Down system?????
Sent by: midrange-l-bounces@xxxxxxxxxxxx

One LPAR.

Can't use FTP as former sa locked down FTP inbound.

Tried rmtcmd dsplib. Connected. But, last thing in the command prompt

is

CPF4252

A very old error as there is no PRT01 and maybe never was.

So, something is working.

On Mon, Mar 18, 2013 at 8:33 AM, <rob@xxxxxxxxx> wrote:

Does index builds NOT display any reference codes on the front? So

that's

all post IPL? Could be. It's been a long time since I did a system
restore from a tape with no save of the access paths. I remember some
files taking a week to complete.
However, we were able to do some work, as long as we avoided files

needing

the access path rebuilt.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxx>,

Date: 03/18/2013 09:29 AM
Subject: Re: Down system?????
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Rob,

If the partition is not activated, then how would the NICs respond to a
ping?

I suspect an earlier suggestion of index rebuilds may be accurate.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 3/18/13 8:25 AM, rob@xxxxxxxxx wrote:

If, this is a single lpar system
and if the display is only showing you 01 B N
and if you are unable to connect to it via telnet, ftp, etc (and

normally

can)
then I suspect that someone typed in RESTART(*NO) on the last

pwrdwnsys.

Try hitting the white button.

If it's only displaying 01 B N then it is not going through any long

IPL

process such as PTF apply or anything because it would be displaying

that

code where the 01 B N displays.

Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept
1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108
6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Jack
Kingsley <iseriesflorida@xxxxxxxxx> To: Midrange Systems Technical
Discussion <midrange-l@xxxxxxxxxxxx>, Date: 03/18/2013 09:19 AM
Subject: Re: Down system????? Sent by: midrange-l-bounces@xxxxxxxxxxxx
Maybe it is going through an access path rebuild, I would try and gain
access to the lan console and see if you can get signed on. On Mon,
Mar 18, 2013 at 9:17 AM, John McKee <jmmckee@xxxxxxxxxxxxxx> wrote:

We have maintenance. But, nobody called it in. Just wanted to get
that up front.

System panel shows B 01 N

System (v5r4 520 (maybe) was unresponsive following weekly IPL. Boss
IPLed this morning. He has been watching it for an hour. He says
that periodically the lights blink on the disks.

I can ping both NICs.

Tried OpsNav. It could not connect. I believe we are using lan

console.

Boss said he tried calling IBM, but had difficulty. Probably dump

it

on

me.

The former sa isn't anymore.

This is not mission critical, but the phones will be ringing.

Just wanted to know if anybody had any info/ideas.

John McKee
--

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

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