RE: Physical file Modification

Simple but brilliant, thanks !

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de CRPence
Envoyé : lundi 30 juin 2008 17:21
À : midrange-l@xxxxxxxxxxxx
Objet : Re: Physical file Modification

A methodology:

<code>
crtmsgf qtemp/ovrcpf
mrgmsgf *libl/qcpfmsg qtemp/ovrcpf select(cpa32b2)
chgmsgd cpa32b2 dft(i) msgf(qtemp/ovrcpf)
/* */
rtvjoba inqmsgrpy(&prvinq)
chgjob inqmsgrpy(*dft)
ovrmsgf qcpfmsg qtemp/ovrcpf
chgpf srcfile()
chgjob inqmsgrpy(&prvinq)
dltovr qcpfmsg
/* */
dltmsgf qtemp/ovrcpf
</code>

If the overridden-to message file is created & maintained as part of the utility, in a permanent library, then the *MSGF need not be created & deleted for each customized utilization.

http://groups.google.com/groups/search?hl=en&ie=UTF-8&num=50&q=crpence+alter+drop+column+chgjob
http://groups.google.com/group/it.comp.as400/browse_frm/thread/369263a2c0bf6684/24f62ee6eb9d5b38?hl=en&lnk=st&q=crpence+alter+drop+column#24f62ee6eb9d5b38

Regards, Chuck

David FOXWELL wrote:

We have a tool used for file modifications that basically saves the
file to change, creates a new file with the new DDS and copies the
data from the old file to the new.

I would like to replace this mechanism with CHGPF.

How can I manage the message that is sent when a field is dropped?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.