RE: Upgrading 3rd party products which include copysrc

Thanks Brad.
No you are not the only guilty party, there our others.

I still need to figure out how to get your new cpysrc on R&D, so programmers can compile and test.
But problem is that R&D is used for other testing, which cannot break (current version).

So I actually need parts of both versions running simultaneously.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bradley Stone
Sent: Monday, February 08, 2016 3:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: Upgrading 3rd party products which include copysrc

I am one of the guilty parties here (maybe the only one) that caused Paul issues.

We did forget to include in our install/upgrade instructions for one of our products that if you're using any subprocedures from our service programs/modules that you should recompile not only to get the new /copy or /include members imported, but also to bind to the new versions of the modules/service programs.

This has since been updated in the documentation for our product.

It was an oversight on my part and I do apologize for the problems/confusion it may have caused Paul or anyone else.

Brad
www.bvstools.com

On Mon, Feb 8, 2016 at 2:40 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

Rob,

Our RPGLE source, which includes 3rd party /copy XXX/QRPGLECPY,XXXYZ
The 3rd party product is integrated into our code.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, February 08, 2016 3:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: Upgrading 3rd party products which include copysrc

I'm a little confused.

Just to get started, what do you mean by copysrc? Stuff that is used
in RPGLE with /copy and/or /include statements?

If so, then how would one know you had an issue unless you WERE doing
a recompile?

Trying to think how such a migration might work, and I can see it
being really different based on the vendor's mind set.

For example, if I was migrating from version x to version y of some
vendor's package they may first migrate all the data to a new library
in a new format. Like add new columns, change column attributes, etc.
Then they would recompile all programs to get these new layouts. Some
may ask why they would recompile versus just sending you end version
objects and the answer would be because they may allow you to add your
own modifications to the new tables.

As far as testing /copy or /include one may have to see if they have a
hardcoded library on the statement, or if their instructions assume a
certain order in your library list.



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: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 02/08/2016 03:12 PM
Subject: Upgrading 3rd party products which include copysrc
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



On an R&D LPAR, I upgraded two 3rd party products last week, both of
which use copysrc.
Both products stated no re-compilation needed.

Both products had failures related to the copysrc, recompilations were
needed.

How does one include the new copy src for the recompiles and test the
new objects, prior to doing the upgrade?


Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related questions.