Re: pre process command

Hi Chuck and Karl -

On Mon, 30 Mar 2015 14:23:24 -0500, CRPence <CRPbottle@xxxxxxxxx>
wrote:

However my recommendation instead was to create both a custom command
and CPP, *not* to use the Exits; notably, that a custom command should
probably drop the OBJTYPE parameter and narrow the scope of the FROMOBJ
parameter possibly to a Physical File name such that perhaps also
renaming that parameter to FROMPF so as to reflect that limitation [and
possibly even making the parameter a qualified name so as to eliminate
the separate FROMLIB parameter].

That's the kind of thing I did with my CRTDUPFSET (CReaTe DUPlicate
File SET) command.

The first parameter is a qualified file name (which has to be a
physical file).

The second parameter is the target library and defaults to QTEMP.

The third parameter indicates what should be done if the physical file
already exists in the target library (defaults to *TOLIB which means
to delete-and-replace if the target library is QTEMP or issue an
escape message if the target library is not QTEMP).

The fourth parameter indicates whether the data should be copied
(defaults to *NO).

The fifth and sixth parameters provide the capability to select or
omit specific logical files from being duplicated (defaults to select
*ALL logicals and omit *NONE).

An escape message is issued if any of the logical files over the
specified physical file are in a different library.

Copying the data (if requested) is done using CPYF, not as part of the
underlying CRTDUPOBJ.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.