Re: What goes where?

No presumption necessary....

The object on production will tell you the system created on, ie. DEV,
and the source file and source member date and times. You can easily
check that the object on production matches the object on development.

In fact, by not allowing source or object creation on production,
you've pretty much guaranteed that production matches development.

Lastly, most change management systems will put a version number on
the object and while have the capability to compare production vs.
development to tell you if there's any mismatches.

Display Object Description - Service

Object . . . . . . . . . . . . . . . : FV011R
Library . . . . . . . . . . . . . : HLTHPRDPGM
Library ASP device . . . . . . . . . : *SYSBAS
Library ASP group . . . . . . . . . : *SYSBAS
Type . . . . . . . . . . . . . . . . : *PGM

Object control level . . . . . . . . : 00R00016

Object Control level is the version number assigned by our change
management system.

HTH,
Charles

On Wed, Jun 30, 2010 at 9:06 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx> wrote:

-----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 module
listed and see the DSPMOD output, where the source is given).

So when a program malfunctions, and you want to inspect the source, you have to <presume> it was created from the source on the dev lpar?
Would the development lpar contain all sources and objects but the prod lpar only the objects necessary for execution which are copies of the objects on the development lpar?
--
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.