Re: CHGPF Ignore question

Thanks, Chuck! It's too late for that this time -- I went ahead and deleted and recreated the file, but I was just curious. It was an empty file, so there wasn't actually any data that could have been lost, and this has always worked for me in the past
....


Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> writes:

On 03-Feb-2012 12:24 , Michael Naughton wrote:

I just tried to use CHGPF on a file in a system I'm developing. I
want to remove a field and add a field. When I tried it, I got
"Change of file MYFILE may cause data to be lost", which I expected
because of dropping the field. In the past, I've always just replied
"I" and the command has proceeded, but this time I got another
message telling me that doing this may cause data to be lost and
informing that the reason is that I'm dropping a field. There
doesn't seem to be any way to reply to this message, and the command
doesn't run.

The file was compiled from DDS, and we're on V7R1. Is this something
new, or is there some setting that got switched? I googled around
and searched the archives, but I didn't find anything .....

Collect an unfiltered LOG(4 0 *SECLVL) spooled joblog after the
inquiries\messages, and a SysRqs-3 OPTION(*PRINT) [or WRKJOB
OUTPUT(*PRINT) taken of the CHGPF requester from another job] for each
time the inquiry [or whatever message type; unstated; and presumably a
CPA32B2] is given. That should be give a better representation of what
transpired, and very possibly also /why/ that outcome.

Other information like reply list entries, DSPMSGD of the message(s)
given, and WRKREGINF may also be of interest, if the review of the
DSPJOB and DSPJOBLOG information might /hint/ to look further.

Regards, Chuck

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA 01376
413-676-3144
Internal: x 444
mnaughton@xxxxxxxxxxxx
****************************************
NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.