|
Trust me, Charles.
I wish we all could use time machines and best case scenarios... The life
of an ISV is quite interesting to say the least. We have OPM, ILE and
everything in between that is supported.
How would you feel if a vendor said "sorry, you need to now change ALL of
your applications to use ILE" instead of a simple recompile for a parameter
list? Now that is a *SHUDDER*. At least in the world I see. :)
Brad
www.bvstools.com
On Mon, Feb 8, 2016 at 5:19 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
<shudder> OPM <shudder>don't
Oh well I can kind of see it then.
But I'm still of the option that vendors should provide updates that
require a recompile. ;)20+
Take a page from IBM's book and include a "data format" parm or
DS-subfield.
Granted, probably a bit difficult to change after 20 years...
Personally, I'd have considered leaving the OPM calls alone. If the
customers wanted the new functionality they'd need to use ILE interface.
Having come from an environment where even a recompile meant the program
had to be re-tested...I very much frown on having a vendor tell me "you
just have to recompile."
Charles
On Mon, Feb 8, 2016 at 5:41 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:
Charles,
I didn't mention any ILE.
The example I gave is similar to an OPM that we've had available for
wasn'tyears. No ILE, no signatures, etc. A straight CALL.complain
In this case when the parameter list (a data structure) changes, a
recompile is required. No big deal to do that. Never had anyone
about it (at least to my face. lol).tricks
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
they'd- rename, in the service program, DOSTUFF to DOSTUFF_OLD. Add a newcalls
DOSTUFF().
Since the procedures all called by position at run time, any existing
will continue to call DOSTUFF_OLD. But when they get recompiled,
wrote:get the new DOSTUFF and could make changes then.
Charles
On Mon, Feb 8, 2016 at 5:23 PM, Bradley Stone <bvstone@xxxxxxxxx>
Jon... here's an example where it would make a difference (but
We'llthe
structure.issue Paul is speaking about)
An application uses a parameter list that's defined as a data
That parameter list is used by the program as an *ENTRY list.
iscallwhen
sameour application DOSTUFF.
To call DOSTUFF from a program (MYPGM for example) it will need the
parameter list. That parameter list is included in a /copy member
youlists
install to DOSTUFF application.member
If you put the new version of DOSTUFF (and subsequently a new /copy
where the parameter list has been updated) on and do NOT recompileMYPGM...
pointer or parameter errors or corrupt data happens. The parameter
don't match up.
Recompile the program(s) that call DOSTUFF so the new /copy member
thebrought into the MYPGM program and things are fine again because
jon.paris@xxxxxxxxxxxxxx>parameter list matches.
Brad
www.bvstools.com
On Mon, Feb 8, 2016 at 4:12 PM, Jon Paris <
canwrote:
Any copy source is included by the compiler at the time that the
module/program is compiled Paul. There is absolutely no way it
programshave
any impact on a system where none of the programs/service
reasonhave
been recompiled.
If after migration the programs failed then there is another
isandprograms)
headthe job log should give some hints. Most likely off the top of my
would be differences in library list (missing files and/or
orPSteinmetz@xxxxxxxxxx
missing service programs.
But missing copy source - nope - no way.
On Feb 8, 2016, at 3:40 PM, Steinmetz, Paul <
XXX/QRPGLECPY,XXXYZ
wrote:
Rob,
Our RPGLE source, which includes 3rd party /copy
BehalfThe 3rd party product is integrated into our code.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On
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
itused
indoing a
RPGLE with /copy and/or /include statements?
If so, then how would one know you had an issue unless you WERE
recompile?
Trying to think how such a migration might work, and I can see
layouts.somebeing
really different based on the vendor's mind set.
For example, if I was migrating from version x to version y of
libraryvendor's package they may first migrate all the data to a new
in
a
new format. Like add new columns, change column attributes, etc.
Then they would recompile all programs to get these new
bothversionSome
may ask why they would recompile versus just sending you end
assume ayourobjects and the answer would be because they may allow you to add
haveown
modifications to the new tables.
As far as testing /copy or /include one may have to see if they
a
hardcoded library on the statement, or if their instructions
copysrc1600certain order in your library list.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept
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
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
On an R&D LPAR, I upgraded two 3rd party products last week,
recompilationsof
which
use copysrc.
Both products stated no re-compilation needed.
Both products had failures related to the copysrc,
testwere
needed.
How does one include the new copy src for the recompiles and
relatedthe
newmailing
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)
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
relatedmailingquestions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
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
relatedmailingquestions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
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
mailingmailingmailingquestions.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
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)
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)
listlistlist
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
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
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 mailing list archive is Copyright 1997-2025 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.