Every way of looking at this is a cr*p shoot...
Based on last use date - the object may only be called based on certain
Based on some reference (like a call statement in a used program) - maybe
the call program name is itself a value in a file, or a call in a .net app,
or a ftp app.
If the objects are not coverted, and not elsewhere in the library list as a
usable pgm, then
move the object to a "obsolete" library, and put that at bottom of the
library list - you want an error msg of "can't execute" instead of "not
If in a 3rd party product lib - leave it alone. The miniscule space savings
not worth your time.
----- Original Message -----
From: "Jerry Draper" <midrangel@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, September 25, 2013 7:04 PM
Subject: obsolete objects
How can you identify obsolete objects that exist on a V6R1 or V7R1 system?
These would be objects that were identified in ANZOBJCVN that would not
convert but were moved over to the later OS anyway.
Of course they are unusable.
Jerome Draper, Trilobyte Software Systems, since 1976
iSeries, Network, and Connectivity Specialists -- iSeries, LAN/WAN/VPN
Representing WinTronix, Synapse, Netopia, HiT, and others .....
(415) 457-3431; www.trilosoft.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives