|
Dennis,
I think that the idea is not to "presume" that the program source comes
from
the dev LPAR but to ASSURE that is the case. That is where good Source
Management systems (Like MKS, Aldon, etc) come handy.
Regards,
Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries
--
On Wed, Jun 30, 2010 at 8:36 AM, David FOXWELL
<David.FOXWELL@xxxxxxxxx>wrote:
module
-----Message d'origine-----
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Vern Hamberg
If you DO have a separate development LPAR, put
source there - there's no reason to put it on the production
LPAR - see debugging response below.
For OPM *PGMs, DSPPGM shows the source on the first page. For
ILE *PGMs,
the source is in the *MODULE detail of DSPPGM (put a 5 on the
youlisted and see the DSPMOD output, where the source is given).
So when a program malfunctions, and you want to inspect the source,
have to <presume> it was created from the source on the dev lpar?prod
Would the development lpar contain all sources and objects but the
lpar only the objects necessary for execution which are copies of themailing list
objects on the development lpar?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
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.
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.