Re: Change service program info for program -- RPG400-L

Another thing you may want to consider doing is to create a cl sourcefile containing the following code for each command that has itsdefaults changed. This not only will serve as documentation of thechanges, but it also can be compiled when a new release is installed andit will replicate the changes to the new release. Our modified commandsare in library SOSQSYS which is ahead of QSYS in the system portion ofthe library list.


   DLTCMD     CMD(SOSQSYS/CRTLIB)
   MONMSG     MSGID(CPF2105) /* Ignore if not found */

CRTDUPOBJ OBJ(CRTLIB) FROMLIB(QSYS) OBJTYPE(*CMD) TOLIB(SOSQSYS)

   CHGCMDDFT  CMD(SOSQSYS/CRTLIB) NEWDFT('AUT(*EXCLUDE)')

You can also include in this source file any other changes to permanentsystem objects or authorities so that they can also be restored when anew release is installed.



Jerry Adams wrote:

Tommy is correct on these cautions.

However, if you have shop standards that the default should be changedfor everyone, the best way to do that is to copy the command (probablyfrom QSYS) into another library and, then, change the default there.For this to actually work, the library with the changed default must beahead of the original command library (probably QSYS). For shopstandards it beats making PDM or WDSc changes everywhere. Being aone-man shop, shop standards are generally whatever I want them to be sothat's usually what I do. In a larger organization it might go overlike 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] OnBehalf 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.