RE: Compiler Directives for printer files

Buck & Henrik,

I am guessing that was developed on an older release. On V4R5+ you can

use a command processor exit. The advantage is that you can compile in

any subsystem, see what was specified during prompting, and then return

the changes back to the command prompt.

David Morris

>>> Buck.Calabro@commsoft.net 05/02/02 07:07AM >>>
Henrik Krebs http://hkrebs.dk/index.html has posted an example of
using
routing entries to invoke a user-written pre-processor.  I can't locate
the
code in the archives but the salient thread is here
http://archive.midrange.com/midrange-l/199806/msg00530.html  Email
Henrik
and he might post his code in his shareware section...

His idea revolves around creating a batch subsystem entry that doesn't
use
QCMD as the command request processing program.  He has written his own
that
reads the request message, parses out the source file/member names and
then
reads the source to find embedded 'commands' and overrides.  He then
injects
those commands as new request messages and calls QCMD which processes
them,
thus overriding the original CRTxxx command into a job stream built
based on
parameters read from the source file.

Very slick.
  --buck