Rob,
Maybe I should look at this from a different angle, as you suggested.
We have had more instances lately where someone needs to access something from another application.
When this happens, an addlible XXX is inserted, code executed, rmvlible xxx is inserted.
This is fine, as long as no dups.
So maybe I should dspobjd for XXX, then query that against the rest of the objects in QUSRSYS/QAEZDISK.
This would only give the dups for the library in question.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, February 09, 2015 3:31 PM
To: Midrange Systems Technical Discussion
Subject: Re: identify/list any duplicate objects from any two libraries.
Well, if it is just QSYS2 you're concerned about, you could always just DSPOBJD the items in QSYS2 and then query that against the rest of the objects in QUSRSYS/QAEZDISK.
That also might be easier for you to understand instead of joining the same table to itself.
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: Gqcy <gmufasa01@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 02/09/2015 03:15 PM
Subject: Re: identify/list any duplicate objects from any two
libraries.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
in the case of this object (QSYS2/LIBLIST)
the "creation" date as seen in DSPOBJD is the date the PTF came active
(upon IPL, 02/01/2015).
On 2/9/2015 1:33 PM, rob@xxxxxxxxx wrote:
There is no create date.
Would that be accurate? For example, if you put on a PTF from IBM do
they
'create' LIBLIST or 'restore' it?
Well, maybe they do 'create' it...
Creation information:
Creation date/time . . . . . . . . . : 12/12/14 21:32:06
Created by user . . . . . . . . . . : QSYS
System created on . . . . . . . . . : GDISYS
Which happens to match the date we last ran a RCLSTG.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.