You can use PIPE, to start whatever you like:
  PIPE REXX (fn ft fm)
Beware though, the default "address" will point to PIPE, what is no problem
if your code starts with ADDRESS COMMMAND. Without an ADDRESS COMMAND (or
address CMS if you like to life unsafe), all CMS commands will result in
RC-7

2009/7/17 Schuh, Richard <[email protected]>

> If all of the messages are from an asynchronous CP command, it might be
> possible that the messages from it come after or between the ones from the
> EXECDROP
>
> Regards,
> Richard Schuh
>
>
>
> > -----Original Message-----
> > From: The IBM z/VM Operating System
> > [mailto:[email protected]] On Behalf Of Frank M. Ramaekers
> > Sent: Friday, July 17, 2009 1:08 PM
> > To: [email protected]
> > Subject: Re: Invoking a pre-processor EXEC
> >
> > Hmmmm....I'm getting the following, but it looks like it worked:
> >
> > iocp a1
> >
> > DMSEXD418W Drop pending for IOCPREAL EXEC
> >
> > IOCP:
> >
> > TOTAL MESSAGES FOR SYNTAX CHECKING: 00000    INFORMATIONAL: 00000
> > CAUTION: 00
> > 000    WARNING: 00000    ERROR: 00000
> >
> > TOTAL IOCP MESSAGES: 00000    INFORMATIONAL: 00000    CAUTION: 00000
> > WARNING:
> >  00000    ERROR: 00000
> >
> > DMSEXD416W There are no IOCPREAL * SYSTEM or USER EXECs
> > storage resident
> >
> >
> > Here's what I coded:
> >
> > "EXECLOAD IOCP EXEC S IOCPREAL EXEC (PUSH USER"
> > "EXEC IOCPREAL" args
> > "EXECDROP IOCPREAL"
> >
> > Not sure why the EXECDROP would execute before the EXEC
> > completed and why it wasn't there when it tried to drop it?
> >
> > Frank M. Ramaekers Jr.
> > Systems Programmer                   MCP, MCP+I, MCSE & RHCE
> > American Income Life Insurance Co.   Phone: (254)761-6649
> > 1200 Wooded Acres Dr.                Fax:   (254)741-5777
> > Waco, Texas  76710
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: The IBM z/VM Operating System
> > [mailto:[email protected]] On Behalf Of Schuh, Richard
> > Sent: Friday, July 17, 2009 1:48 PM
> > To: [email protected]
> > Subject: Re: Invoking a pre-processor EXEC
> >
> > 'EXECLOAD EXECA EXEC Z EXECX EXEC (PUSH USER'
> > 'EXEC EXECX'
> > 'EXECDROP EXECX'
> >
> > Regards,
> > Richard Schuh
> >
> >
> >
> > > -----Original Message-----
> > > From: The IBM z/VM Operating System
> > > [mailto:[email protected]] On Behalf Of Frank M. Ramaekers
> > > Sent: Friday, July 17, 2009 11:36 AM
> > > To: [email protected]
> > > Subject: Invoking a pre-processor EXEC
> > >
> > > I'd like to write a pre-processor EXEC of an existing EXEC with the
> > > same name.  How do you make sure that the pre-processor
> > EXEC doesn't
> > > invoke
> > > itself and invokes the original EXEC.   (It finds the pre-processor
> > > first because of disk access order.)
> > >
> > > Frank M. Ramaekers Jr.
> > > Systems Programmer                   MCP, MCP+I, MCSE & RHCE
> > > American Income Life Insurance Co.   Phone: (254)761-6649
> > > 1200 Wooded Acres Dr.                Fax:   (254)741-5777
> > > Waco, Texas  76710
> > >
> > > _____________________________________________________ This message
> > > contains information which is privileged and confidential and is
> > > solely for the use of the intended recipient. If you are not the
> > > intended recipient, be aware that any review, disclosure, copying,
> > > distribution, or use of the contents of this message is strictly
> > > prohibited. If you have received this in error, please destroy it
> > > immediately and notify us at [email protected].
> > >
> >
> > _____________________________________________________ This
> > message contains information which is privileged and
> > confidential and is solely for the use of the intended
> > recipient. If you are not the intended recipient, be aware
> > that any review, disclosure, copying, distribution, or use of
> > the contents of this message is strictly prohibited. If you
> > have received this in error, please destroy it immediately
> > and notify us at [email protected].
> >
>



-- 
Kris Buelens,
IBM Belgium, VM customer support

Reply via email to