RE: CHGCMDDFT for TGTRLS from *CURRENT to V7R1M0

Some items I've found over the years.

1) From WRKOUTQ listing of spoolfiles, 1=Send, which results in SNDNETSPLF is hardcoded by IBM to use QSYS. SNDNETSPLF placed in another library would not be called.

2) IBM products that use a product library, such as BRMS, will always call the command from the product library QBRM, command in QSYS never used.

3) PTFs can/will set commands back to IBM defaults, so if have you have defaults changed, they can be lost.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, January 18, 2018 1:22 PM
To: Midrange Systems Technical Discussion
Subject: Re: CHGCMDDFT for TGTRLS from *CURRENT to V7R1M0

... after all, even IBM has changed some of their defaults on occasion.


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: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/18/2018 01:16 PM
Subject: Re: CHGCMDDFT for TGTRLS from *CURRENT to V7R1M0
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Then perhaps one shouldn't code expecting IBM supplied defaults?
If you need CRTCLPGM to say TGTRLS(*CURRENT) then use CRTCLPGM
TGTRLS(*CURRENT), and so on.
I wouldn't go so far as to supply EVERY parameter. That way if the
customer does do a CHGCMDDFT, and it has no adverse effects on your
software, then let the customer's change percolate through. If, however,
that parameter just has to be a particular value, then supply that value.



Rob Berendt