MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2014

RE: Identifying all references to a currently active program



fixed

Alan

The RXS upgrade was sort of unique.
A simple RSTOBJ from a savf into the existing RXS library, omitting any configuration objects.
Some old objects were replaced, new objects added.
I've never done a restore with intentional omits, but it was very useful for the config objects.

Message . . . . : -RSTOBJ OBJ(*ALL) SAVLIB(RXS) DEV(*SAVF) SAVF(QGPL/RXS311)
MBROPT(*ALL) ALWOBJDIF(*FILELVL *OWNER) RSTLIB(RXS) OUTPUT(*PRINT)
OMITOBJ((RXSUNQ) (RXSCFG) (LICP) (RXSRTRCTL) (RXSRTRLOG))

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Tuesday, August 12, 2014 3:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: Identifying all references to a currently active program

What did they do with the old library? Did they rename it. If yes, anything still active will be pointing to the programs in the old library. If they deleted it, then the next time one of programs gets tried to use it should blow up although that is not guaranteed. I have had service programs pointing to an old version that held on even when the service program was deleted.


On Tue, Aug 12, 2014 at 1:39 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

RXS 2.71 to 3.11 upgrade complete.
All is working.
No objects were moved to the QRPLOBJ library, what does this infer?
RXS license key LICP had to be moved from old license key library
KTLIC to RXS.
Object LICP in KTLIC type *FILE moved to library RXS

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Paul Nelson
Sent: Tuesday, August 12, 2014 2:24 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Identifying all references to a currently active program

If a program is active, and a newer version is installed, the older
version is automatically stuffed into QRPLOBJ under a different name.
The user won't know what happened. The next time the program is
called, the user will get the new version.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Tuesday, August 12, 2014 1:15 PM
To: 'Midrange Systems Technical Discussion'
Subject: Identifying all references to a currently active program

I'm upgrading a 3rd party tool later today, RXS 2.71 to 3.11.
The upgrade is simple, RSTOBJ from a savf to the RXS library, about 70
objects.
Takes about 10 seconds.
The issue is we have no easy way of knowing what programs of ours
should be stopped/started The main RXS object is RXSSV *SRVPGM, which
is part of BNDDIR RXSBND
1) Is there a command or tool that would show any reference or call to
this program?
2) If an RPGLE program is in memory, but not currently used, if this
object if replaced by the upgrade, the reference to this program will
probably result is failure, correct?

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


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






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact