|
Sent privately. Also placed into http://www.lovelady.com/misc as
rplobj.zip
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"If I were running the world I would have it rain only between 2 and 5
A.M. Anyone who was out then ought to get wet."
-- William Lyon Phelps
Thanks Dennis .... if convenient, I'd love to see your RPLOBJ--
process.
Rich Loeber - @richloeber
Kisco Information Systems
[1]http://www.kisco.com
------------------------------------------------------------------
------locks
Dennis Lovelady wrote:
One needs to be cautious about locks that are in place (I think
arewas
held on ILE programs that are in use), but otherwise, yes.
I have a command and CPP I could share this evening, called RPLOBJ,
whose
purpose is exactly that which you describe. So that it may be run
repeatedly with success, it also renames the object when moving to
QRPLOBJ.
Not quite as slick as IBM since that (move/rename) cannot be done in
one
step, but it was workable for the time.
Dennis Lovelady
[2]http://www.linkedin.com/in/dennislovelady
--
"When I was a boy of fourteen, my father was so ignorant I could
hardly
stand to have the old man around. But when I got to twenty-one, I
astonished at how much he had learned in seven years."to
-- Mark Twain
I have a situation where I have a program that was compiled on a
different
system that I want to move into place. The program may be in use
when I
want to install the new version. Obviously, just deleting the
program and
moving the new one in would not be a great idea. Would it work
movemailing
the old version of the program into the QRPLOBJ library and then
install
the new version?
Does anyone have any experience with doing this kind of program
update? I
know the compiler will do this for me, but the program is already
compiled
when I'm moving it into production.
Rich Loeber - @richloeber
Kisco Information Systems
[1][3]http://www.kisco.com
References
Visible links
1. [4]http://www.kisco.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listmailing
To post a message email: [5]MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [6]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [7]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [8]http://archive.midrange.com/midrange-l.
References
Visible links
1. http://www.kisco.com/
2. http://www.linkedin.com/in/dennislovelady
3. http://www.kisco.com/
4. http://www.kisco.com/
5. mailto:MIDRANGE-L@xxxxxxxxxxxx
6. http://lists.midrange.com/mailman/listinfo/midrange-l
7. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
8. http://archive.midrange.com/midrange-l
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.