Re: V4R4 Upgrade Problem/Question -- MIDRANGE-L

Rich,

  Done tons of CISC to RISCs and seen A900 2000 on every one of 'em,
heck it's been in my checklist since the very first one.  This was a
V4R1 to V4R4 upgrade (shoulda said that in my orginal post).  

  When the customer called me and I knew A900 2000 off the top of my
head she immediately asked howcum IBM had to find it in a book.  Now I
don't expect IBM to know every code from memory (like I know about
three of em this just happens to be one) but where did the advice to
reload come from? Can ANYONE ANYWHERE point me to where it is
documented that clearing A900 2000 requires a SYSTEM RELOAD!?! What
kind of LAME ADVICE IS THIS?

  Don't mis-understand me in that I am a consultant who makes money
fixing these problems for customers, but frankly I would have rather
watched the Detroit Lions sans Barry Sanders than have to do this on
Sunday afternoon, even FOR money!

 - Larry

"Garcia Rich (SYS1RXG)" wrote:
> 
> Performing over ten CISC to RISC Migrations I can tell you that you
> run into this problem all of the time and you need to change the
> Hardware Resources Settings in order to clear this. Under no Means
> should a scratch be done. This is a normal SRC code.
> 
> -----Original Message-----
> From: Larry Bolhuis [mailto:lbolhui@ibm.net]
> Sent: Monday, September 13, 1999 7:24 AM
> To: Midrange Systems Mailing List
> 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  |
(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
+---