Barbara,
Okay thanks was thinking the command made it sound like that.
Since I have to get the ADMIN involved with making a copy of the CRTCBLPGM
and then running the CHGCMDDFT (since my access does not allow that), was
curious if my thought was correct and seems like it is. So sounds like if
becomes to much of problem then make new PDM option to use or just get
them to switch to RDP, which ever they see as the lesser evil :).
Jeff Buening
Sr. Developer
P: 419.586.8599
| F: 419.586.6224
Celina Insurance Group
800.552.5181 | 1 Insurance Square, Celina, Ohio 45822
www.celinainsurance.com
................................................................................
...............................
The information contained in this message (including any attachments) is
confidential and may be privileged.
Unauthorized disclosure, copying, or use of this information is prohibited and
may be unlawful.
If you are not the intended recipient, please delete this message and notify
the sender.
From: Barbara Morris <bmorris@xxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Date: 07/22/2013 04:58 PM
Subject: Re: [WDSCI-L] Change the default for the Compile command
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
On 7/22/2013 8:34 AM, Jeff Buening wrote:
Reading the CHGCMDFT doesn't look like this is possible because doesn't
have default value, but does anyone know can I change the OPTION parm on
CRTCBLPGM to always be *SRCDBG in PDM? In RDP the default is *SRCDBG,
but
when other users who use PDM compile, the OPTION parm is blank, which
means I can't debug their programs in RDP, until I recompile them with
*SRCDBG.
No, as far as I know, the system doesn't support CHGCMDDFT for a
parameter, like the OPTION parameter, that takes a list of values.
Maybe you could get the PDM folks to use a PDM option, say CB, instead
of using 14 to compile COBOL programs.
CRTCBLPGM PGM(&L/&N) SRCFILE(&L/&F) OPTION(*SRCDBG)
midrange.com
