Re: Invoking a pre-processor EXEC

2009-07-17 Thread Schuh, Richard
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:ib...@listserv.uark.edu] On Beha

Re: Invoking a pre-processor EXEC

2009-07-17 Thread Frank M. Ramaekers
HI'm getting the following, but it looks like it worked: iocp a1 DMSEXD418W Drop pending for IOCPREAL EXEC IOCP: TOTAL MESSAGES FOR SYNTAX CHECKING: 0INFORMATIONAL: 0 CAUTION: 00 000WARNING: 0ERROR: 0 TOTAL IOCP MESSAGES: 0INFORMATIONAL: 0CAU

Re: Invoking a pre-processor EXEC

2009-07-17 Thread Frank M. Ramaekers
Yepdidn't get that fardarn, looked promising. 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 M

Re: Invoking a pre-processor EXEC

2009-07-17 Thread Bruce Hayden
Are you sure it worked as you expected? See usage note 1 of the help for the RUN command: "The RUN command passes only the file name (fn) of an exec to the EXEC processor. Therefore, you cannot use "fm" to select a particular exec." You have to execload it, as Richard posted. On Fri, Jul 17, 200

Re: Invoking a pre-processor EXEC

2009-07-17 Thread Romanowski, John (OFT)
does it work? The HELP for RUN command says " The RUN command passes only the file name (fn) of an exec to the EXEC processor. Therefore, you cannot use "fm" to select a particular exec." Is the HELP mistaken? > -Original Message- > From: The IBM z/VM Operating System [mailto:ib...@lists

Re: Invoking a pre-processor EXEC

2009-07-17 Thread Schuh, Richard
Look at Note 1 of the HELP. 1. If you are executing a CMS EXEC or EXEC 2 file, the arguments you enter on the RUN command line are assigned to the variable symbols &1, &2, and so on. If you are executing a REXX program, the arguments you enter on the RUN command line are

Re: Invoking a pre-processor EXEC

2009-07-17 Thread Wakser, David
Use file mode. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, July 17, 2009 2:36 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Invoking a pre-processor EXEC I'd like to write a pre-processor EXEC of an exist

Re: Invoking a pre-processor EXEC

2009-07-17 Thread Frank M. Ramaekers
Found the RUN command...works like a charm. 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

Re: Invoking a pre-processor EXEC

2009-07-17 Thread Schuh, Richard
'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:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers > Sent: Friday, July 17, 2009 11:36 AM > To: IBMVM@LISTSE

Invoking a pre-processor EXEC

2009-07-17 Thread Frank M. Ramaekers
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

Re: SYSPROF.EXEC

2009-07-17 Thread Schuh, Richard
You do always have to check. Just because something has not changed in a long time does not mean that it will never change. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Michael Donovan Sent: Friday

Re: SYSPROF.EXEC

2009-07-17 Thread Rob van der Heij
On Fri, Jul 17, 2009 at 1:39 PM, Michael Donovan wrote: > Fair enough! It seemed to me as though the discussion had turned to more of > a concern over the amount of time needed to rework exits each time service > or a new release came out. Since there have not been changes made since > VM/ESA 2.2.

Re: SYSPROF.EXEC

2009-07-17 Thread Michael Donovan
Fair enough! It seemed to me as though the discussion had turned to more of a concern over the amount of time needed to rework exits each time service or a new release came out. Since there have not been changes made since VM/ESA 2.2.0, I was curious as to why the perception existed that there