× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We've recently migrated from a 550 at V5R4 to a 720 at 7.1 and STROBJCVN
OPTION(*CHECK) did the job for us. The output (in the job log) isn't as
workable as ANZOBJCVN but it runs very quickly if there isn't much that
needs conversion.


On 26 September 2013 13:06, <rob@xxxxxxxxx> wrote:

<snip>
While you can't run ANZOBJCVN after you upgrade to 6.1. or 7.1, you can
run STROBJCVN *CHECK and it will tell you what objects in that library
can't be converted.
</snip>
Well, that sounds like the easiest way to find them.


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: Pete Massiello - ML <pmassiello-ml@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 09/26/2013 07:51 AM
Subject: RE: obsolete objects
Sent by: midrange-l-bounces@xxxxxxxxxxxx



You need either Observability or Creation Data to re-encapsulate a
program. You can't remove Creation Data, hence your statement about V5R1
created programs below. Creation Data is a subset of Observability, which
is the min that the OS needs to re-encapsulate the program (Re-create the
*PGM from itself in the new format).

While you can't run ANZOBJCVN after you upgrade to 6.1. or 7.1, you can
run STROBJCVN *CHECK and it will tell you what objects in that library
can't be converted.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, September 26, 2013 7:46 AM
To: Midrange Systems Technical Discussion
Subject: Re: obsolete objects

I once tried running ANZOBJCVN again but that won't work again if you
you've already upgraded to 6.1 or 7.1. I suspect it will be pretty much
dormant until when IBM needs it again, if ever.

You may want to check out a homegrown version of ANZOBJCVN available at
http://www.think400.dk/downloads.htm

It may not be flawless, but it's a start.
I'm not sure on the logic that insists the target release be greater than
V5R1. IBM tells me that the target release is not so important as the
compiler level. Somewhere I read that anything compiled under V5R1 or
above, irregardless of target release, or whether or not it had
observability will be ok. The real culprits were items compiled by a
compiler prior to V5R1 with observability removed. Apparently there's
enough 'stuff' in there, even with observability removed, at V5R1 and
above that conversion processes ok.


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: Jerry Draper <midrangel@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 09/25/2013 07:05 PM
Subject: obsolete objects
Sent by: midrange-l-bounces@xxxxxxxxxxxx



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.

Jerry

--
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
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.