RE: Change service program info for program

With PDM/SEU it's far better IMO to have your own PDM options
file...that way options I never use can be changed without affecting
others.  Even if there are shop standards in place I've found there are
always exceptions that have to be handled differently....

Even if you copy the commands into another library you still have to be
aware that the command may change (i.e. add keywords, etc..) that can
bite you on upgrades... 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx] On
Behalf Of Jerry Adams
Sent: Wednesday, October 12, 2005 3:10 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Change service program info for program

Tommy is correct on these cautions. 

However, if you have shop standards that the default should be changed
for everyone, the best way to do that is to copy the command (probably
from QSYS) into another library and, then, change the default there.  
For this to actually work, the library with the changed default must be
ahead of the original command library (probably QSYS).  For shop
standards it beats making PDM or WDSc changes everywhere.  Being a
one-man shop, shop standards are generally whatever I want them to be so
that's usually what I do.  In a larger organization it might go over
like a lead balloon.


        * Jerry C. Adams
*iSeries/i5 Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.893.8633x152
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Holden Tommy wrote:

>Careful with this one...Changing command defaults *could* hit someone 
>else in the backside...not to mention should the OS be upgraded your 
>back to the shipped default.  I generally handle this via PDM option 
>(for SEU..copy the QAUOOPT file into my dev lib..) or by creating 
>"custom" compile options in WDSC much safer plus it only affects me.
>
>
>Thanks,
>Tommy Holden
>
>
>-----Original Message-----
>From: rpg400-l-bounces@xxxxxxxxxxxx
>[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Giusto
>Sent: Wednesday, October 12, 2005 1:53 PM
>To: RPG programming on the AS400 / iSeries
>Subject: Re: Change service program info for program
>
>you could try CHGCMDDFT on the CRTPGM command to ALWLIBUPD(*YES) 
>assuming the CRTBNDRPG is using the CRTPGM after creating the temp 
>module object.
>
>----- Original Message -----
>From: "Mel Rothman" <mel@xxxxxxxxxxxxxx>
>To: <rpg400-l@xxxxxxxxxxxx>
>Sent: Wednesday, October 05, 2005 1:46 PM
>Subject: Re: Change service program info for program
>
>
><SNIP>
>
>Unfortunately, CRTBNDRPG, which I use, does not have either of these 
>parameters and apparently uses the defaults. DSPPGM for my programs 
>created with CRTBNDRPG show this:
>
>Allow update . . . . . . . . . . . . . . . . . :   *YES
>Allow bound *SRVPGM library name update  . . . :   *NO
>
>So, if you use CRTPGM, you can specify ALWLIBUPD(*YES) and use UPDPGM's

>SRVPGMLIB to change the bound service program's library.
>
>If you use CRTBNDRPG, you need to run CRTBNDRPG again with the desired 
>service program name and library.
>
>  
>

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.