Re: V4R4 Upgrade Problem/Question

[pytel@xxxxxxxxxx]

There are two major scenarios for A900 2000.
1) After hardware or software upgrade system may reassign resource names.
In this case existing controller descriptions will point to wrong cards or just
point nowhere.
To fix this, resource names in controller descriptions should be checked and
corrected.

(It may happen, that you do not have any access to system and only have A900
2000 on a panel.
This situation is covered in documentation. You need to do what is called
"attended IPL, console in debug mode".
Temporary service controller description will be generated for such IPL and you
will be able to edit controller descriptions.)

2) More general case is when system does not recognize primary console card in
the place where it expects to find one.
It happens sometimes with systems which can have more than one console card -
for example, some RISC boxes can have both PC console and twinax consoles. If
primary console card is unaccessible, hence A900 2000.
This may require physical reshuffle of cards.
In many cases SRC on the panel is only nuissance, without any influence on
system availability.

Fixing this problem may require an IPL at worst. I have never seen that reload
had to be done to fix this.

Best regards
    Alexei Pytel


Larry Bolhuis <lbolhui@ibm.net> on 09/13/99 06:24:24 AM

Please respond to MIDRANGE-L@midrange.com

To:   Midrange Systems Mailing List <MIDRANGE-L@midrange.com>
cc:
Subject:  V4R4 Upgrade Problem/Question




Greetings,

 Over the weekend one of my customers made the move to V4R4 on their
Model 500.  After the PTF CUM apply the system came up with A900 2000
on the panel (Can't find the console).   The console device and all
devices on CTL01 were not functioning.  They called support (starting
with hardware ending up with $upportline) and over a lot of hours IBM
decided to replace CTL01 but this did not help.  Their final
suggestion: Repload the system starting with SLIC. (Thanks
'microsoft')

 Finally yesterday afternoon the customer called me (shame on them for
waiting so ong!) and I observed the following: There was no QCTL
controller or QCONSOLE device, but all other local and remote
controllers were up and working normally.  CTL01 was varried off and a
message in QSYSOPR said it could not be varied on because QCTL (which
does not exist) was varied on.  So I varied it on manually and the
workstations came up. (Still A900 2000 on the panel) Printers were not
working on CTL01, they would vary on and start writers but spooled
files were all held by the writer immediately.  My somewhat simpler
solution was to RTVCFGSRC on CTL01, copy all the spooled files from
*OUTQs associated with printers on CTL01, delete CTL01 and all
associated devices, rebuild it from the retrieved source, IPL.  All
better now. (Even QCTL and QCONSOLE now exist!)

 Is is too much to ask that $upportline and IBM-SERVE would have tried
this simple solution before recommending a scratch reload???

 I will wait for some learned opinions before I call some people and
give them MY opinion on the matter.

 Thanks - Larry

--
Larry Bolhuis         | What do You want to Reload today?
Arbor Solutions, Inc  |  (Hint: It's NOT MY AS/400!!!)
(616) 451-2500        |
(616) 451-2571 -fax   | Two rules to success in life:
lbolhui@ibm.net       | 1. Never tell people everything you know.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---