Re: changing field descriptions

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

I had tried that exact thing not but a day ago, with failure.  I'm on
V3R7M0 and wanted to add DDS to a "flat" S/36 file that had
been overlooked.

So I created the DDS in a test library, copied a few of the records
into it with FMTOPT(*NOCHK) and tested the integrity of my DDS
file, which was fine.  Then I copied the DDS source into the production
library, and did a ALCOBJ *EXCL on the file I wanted to change.

Then I issued the CHGPF, prompted it, and gave it the source code
file and member, and hit enter.  And received an error.  Unfortunately,
I don't remember what the error was, but I seem to recall it had something
to do with not being able to map from a string field to a numeric field.

So I then copied from my production file to my test file with *NOCHK,
did a DLTF on my production file, and did a CPYF from my test
file to my production file.

What a pain.

Regards,

Jim Langston

"Bale, Dan" wrote:

> The newest (V3R7 and higher???) incarnations of CHGPF (that's _Change_
> Physical File) allow you to "recompile" the file object and keep the data
> and handle the logical files.  It's no longer a pipe dream!
>
> Look for the Source file (SRCFILE) and Delete dependent logical file
> (DLTDEPLF) parameters on the command and prompt for the help text on them.
>
> - Dan Bale

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---