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


  1.  Home
  2. MIDRANGE-L
  3. February 2016

Re: Upgrading 3rd party products which include copysrc

Charles,

I didn't mention any ILE.

The example I gave is similar to an OPM that we've had available for 20+
years. No ILE, no signatures, etc. A straight CALL.

In this case when the parameter list (a data structure) changes, a
recompile is required. No big deal to do that. Never had anyone complain
about it (at least to my face. lol).

Brad
www.bvstools.com

On Mon, Feb 8, 2016 at 4:32 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

DOSTUFF should have been updated in such a manner as to not require
recompile.

- No existing parameters changed
- new Parms added as OPTION(*OMIT)

If you absolutely must change an existing parm, there are a couple tricks
- rename, in the service program, DOSTUFF to DOSTUFF_OLD. Add a new
DOSTUFF().

Since the procedures all called by position at run time, any existing calls
will continue to call DOSTUFF_OLD. But when they get recompiled, they'd
get the new DOSTUFF and could make changes then.

Charles

On Mon, Feb 8, 2016 at 5:23 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

Jon... here's an example where it would make a difference (but wasn't the
issue Paul is speaking about)

An application uses a parameter list that's defined as a data structure.
That parameter list is used by the program as an *ENTRY list. We'll call
our application DOSTUFF.

To call DOSTUFF from a program (MYPGM for example) it will need the same
parameter list. That parameter list is included in a /copy member when
you
install to DOSTUFF application.

If you put the new version of DOSTUFF (and subsequently a new /copy
member
where the parameter list has been updated) on and do NOT recompile
MYPGM...
pointer or parameter errors or corrupt data happens. The parameter lists
don't match up.

Recompile the program(s) that call DOSTUFF so the new /copy member is
brought into the MYPGM program and things are fine again because the
parameter list matches.

Brad
www.bvstools.com

On Mon, Feb 8, 2016 at 4:12 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

Any copy source is included by the compiler at the time that the
module/program is compiled Paul. There is absolutely no way it can
have
any impact on a system where none of the programs/service programs have
been recompiled.

If after migration the programs failed then there is another reason and
the job log should give some hints. Most likely off the top of my head
would be differences in library list (missing files and/or programs) or
missing service programs.

But missing copy source - nope - no way.


On Feb 8, 2016, at 3: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.

Jon Paris

www.partner400.com
www.SystemiDeveloper.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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.