Rob,

Thanks for all the pointers. What upgrade were you doing to Quickr?
I'm currently at 8.0.1. I'm assuming that you are going 8.0.1?

We are actually running two instances on two different LPAR's. 6.5.5.
(QP) and 8.0.1. We are looking at our options for the 6.5.5 legacy
stuff. We may migrate places (depending on how much link trouble we
have) vs. actually upgrading the server.....I'm not sure but I know I'm
not excited about upgrading the server....as you can tell by my 6.5.5
release level.....

Michael Crump

Manager, Computing Services
Saint-Gobain Containers, Inc.
1509 S. Macedonia Ave.
Muncie, IN 47302

765.741.7696
765.741.7012 f



Motivation
If a pretty poster and a cute saying are all it takes to motivate you,
you probably have a very easy job. The kind robots will be doing soon.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, September 04, 2008 4:38 PM
To: Midrange Systems Technical Discussion
Subject: RE: 5799PTL - more details on what it does and where it is
required?

v6r1-si31970
But if you don't have the issue with NETSTAT and trying option 3, then I

wouldn't worry about this ptf.

If it's any consolation, I just opened another pmr because my quickr
upgrade failed during the RSTLICPGM. Love those call back queues. They

always seem to wait until after closing time...
CPF0C4D - Error occurred while processing object QPIN0050 in library
QQPLACE.
Cause . . . . . : While processing object QPIN0050 type *PRDLOD in
library QPLACE an error occurred which prevented the operation from
completing successfully. The return code is 0024-DIRLIST.
No previous messages look promising...

Rob Berendt

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