TheRealRaven Apr 28, 2015   1:11 PM GMT

What do you need help with? What have you done so far that we can look at? (And why would you want to do something like this in the first place? It's likely to cause future confusion.)

34,430 pointsBadges:

ToddN2000 Apr 28, 2015   2:21 PM GMT

It may be easier to do a CHGCMD. It's not recommended to change system commands as it may effect more than you plan on. Have you looked at doing a find / replace using PDM to make the change?

Splat Apr 28, 2015   4:12 PM GMT

You might be better served by making a copy of the SAVOBJ command - I have a library that sits above QSYS in the system portion of the library list just for that purpose - and use the CHGCMDDFT command to alter the DTACPR parameter on the copied version.   This would allow you to avoid changing every program using the SAVOBJ command.

12,865 pointsBadges:

TheRealRaven Apr 29, 2015   0:26 AM GMT

We don't know why this is being done, so CHGCMDDFT and making a copy might both be inappropriate. (Or either could fit very well.) So far, all we know is that new command is being created with a different name that will be used in some CL programs. There seems to be some problem with the DTACPR() parameter, but we don't know what the problem is. Hard to supply good suggestions without knowing what needs to be "fixed".

34,430 pointsBadges:

TheRealRaven Apr 29, 2015   12:30 AM GMT

Ah! Upon re-reading, I think ToddN2000 correctly guessed the purpose of creating a new command. But changing the SAVOBJ default to be DTACPR(*MEDIUM) would make the default invalid for tape devices.

That makes the question less clear. There should be only a very few CL programs that include a SAVOBJ command. Some of those will be IBM-supplied programs. Maintenance changes should be easy and fairly quick.

34,430 pointsBadges: