RE: What to do with QRCL objects after RCLSTG

I *have* checked out a few of these objects via DSPOBJD DETAIL(*BASIC) &
DETAIL(*FULL) & DETAIL(*SERVICE) - there's nothing, nyet, nada.

If, as Andy suggests, that the absence of a library name (showing *N) means
that these objects have not been "in a library" (whatever that means), it
would be interesting to know how that happened.

But it appears that, no matter what, I should just recompile the objects
from the source we have.

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Al Barsa
Sent: Thursday, May 30, 2002 10:00 AM
To: midrange-l@midrange.com
Subject: Re: What to do with QRCL objects after RCLSTG



What I usually do with objects in QRCL is to go back to the original
object, and check it out.  The point of putting stuff into QRCL is to give
you the ability to reassemble things that and out of kilter.

Theoretically, of OS/400 was perfect, RCLSTG would never be needed, but
there are bugs in OS/400, and systems do go down.

Once your done with QRCL, save it, and delete it.

Al