Re: CHGCMDDFT for TGTRLS from *CURRENT to V7R1M0

[Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>]

I also change the command defaults right in QSYS.  I have a job scheduler
job that run 7 days a week at 11pm which consists of the following commands:

DFLTAPLUS - changes Abstract print files to the page size I want
DFLTCMDP - changes command defaults in QSYS
DFLTGN#  - Changes ProGen Plus print files to the page size I want
DFLTOTH -  Changes misc stuff, like authority to some objects
DFLTPRTF - Changes all system print files to the page size I want
DFLTTAA  - Changes all TAA Tools print files to the page size I want

I too have been doing it this way for 15+ years with no issues.  Takes 3-4
minutes to run.



On Thu, Jan 18, 2018 at 1:10 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

> Yep, IPL startup programs are the cats meow.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   Denis Robitaille <denis_robitaille@xxxxxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Date:   01/18/2018 11:55 AM
> Subject:        RE: CHGCMDDFT for TGTRLS from *CURRENT to V7R1M0
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> Here are a few others that you might consider:
> CRTCLMOD
> CRTPGM
> CRTS36RPT
> CRTSRVPGM
> CRTSQLRPG
>
> Here is how we implement this on pour site:
> The TGTRLS that we want to use is in a data area
> All the CHGCMDDFT are in a CL program that uses the data area
> This CL program is called by the start up program.
>
> This way, after an IPL (for version update, PTF ...) all the default that
> we want changed are always applied. When we decide to change the target
> release, we just change the data area and call the CL program.
>
> We do change the IBM commands. We do not create a copy. In 15+ years, this
> never gave us any problem.
>
> Hope this help
>
>
> Denis Robitaille
> Chef de service TI - Solution d'entreprise
> Infrastructure et opérations
>
> CASCADES CENTRE DES TECHNOLOGIES
> 412 Marie Victorin
> Kingsey falls(Québec) Canada J0A 1B0
> Tél :  819 363 6100  Poste :52130
> Cell : 819 352 9362
>
>
> -----Message d'origine-----
> De : MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de
> Steinmetz, Paul
> Envoyé : 18 janvier 2018 11:34
> À : 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
> Objet : CHGCMDDFT for TGTRLS from *CURRENT to V7R1M0
>
> We will be upgrading R&D LPAR from V7R1 to V7R3 this weekend.
> Production LPAR will remain at V7R1, will be done at a future date.
>
> During the period that the two LPARS are at different releases, I need to
> CHGCMDDFT for TGTRLS on the R&D LPAR from *CURRENT to V7R1MO, so objects
> created on V7R3 will run on V7R1.
> Below are the common ones that I know need changing, there are others.
> Any thoughts from the group on any I'm am missing?
>
> CHGCMDDFT  CMD(QSYS/CRTBNDCL) NEWDFT('TGTRLS(V7R1M0)')
> CHGCMDDFT CMD(QSYS/CRTBNDRPG) NEWDFT('TGTRLS(V7R1M0)')
> CHGCMDDFT CMD(QSYS/CRTCLPGM) NEWDFT('TGTRLS(V7R1M0)')
> CHGCMDDFT CMD(QSYS/CRTRPGMOD) NEWDFT('TGTRLS(V7R1M0)')
> CHGCMDDFT CMD(QSYS/CRTRPGPGM) NEWDFT('TGTRLS(V7R1M0)')
> CHGCMDDFT CMD(QSYS/CRTRPTPGM) NEWDFT('TGTRLS(V7R1M0)')
> CHGCMDDFT  CMD(QSYS/CRTSQLRPGI) NEWDFT('TGTRLS(V7R1M0)')
> CHGCMDDFT CMD(QSYS/SAVRSTLIB) NEWDFT('TGTRLS(V7R1M0)')
> CHGCMDDFT CMD(QSYS/SAVRSTOBJ) NEWDFT('TGTRLS(V7R1M0)')
>
> 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
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> moment to review the archives at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
>
>
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD