Re: WDSC CHGPF / CRTPF on existing file not replacing object

Michael Quigley wrote:

Paul, Bryce, Mark, et al,

It's not a matter of WDSC. If you submit the CHGPF to batch on the green
screen, the message is not displayed nor handled. We opened a PMR about
it years ago, but it never really got anywhere. If I recall correctly the
response was basically "Working as designed." I've always thought
"working as designed" is a pretty lame answer, but I understand the
challenge--how do you ask whether to continue the CHGPF from a batch
environment? or more generically, a non-interactive environment such as
WDSC. Sending a message to QSYSOPR would wreak havoc on automated build
tools. Anyway, the problem arises because you're either changing a field
to an incompatible type, deleting a field, etc. As pointed out, the
initial CRTPF in QTEMP succeeds, but the command fails.

Michael Quigley
Computer Services
The Way International
www.TheWay.org
419 753-1222

I've also been pretty annoyed by IBM's answer (after confronting this year's
ago).

However, within SEU, one is offered the chance to "replace object" which
allows the bypass of the confirm prompt via the session default settings.
This is our shop standard; we assume that if you're at a point to make a
file change that impacts the record format, you don't give a rip about the
existing data.

I just wish there was a way within WDSC/RDP preferences to effect the same
sort of behavior. Wishful thinking I guess...

Buzz