Offer, et al:
If some of your users can tolerate some changes, and the CP command of CMS
is already used in many of the other places, consider something like the
following:
CP EXEC:
/* REXX- Trap CP output for CMS stage. */
"pipe cp" arg(1) "| cons"
return RC
In addition to simplicity, this al
Thank you all for your help.
At the end STARMSG *MSGALL did the trick without the CPCONIO or VMCONIO
parameters...
Everything works perfectly now.
Thanks again!
Offer Baruch
On Tue, Nov 29, 2016 at 2:48 PM, Rod Furey wrote:
>
> But you would be better off to modify your tools to make it m
But you would be better off to modify your tools to make it more suitable
for usage in a pipe (and not prompt for input or things like that).
Rob
To emphasise what Rob says: we discovered long ago that a rewrite paid
dividends and very quickly paid back the development investment.
I ha
This time of year on the Northern hemisphere, you will likely catch a cold.
Otherwise, try it; you'll learn much better from correcting your
mistakes on your own steam.
On 11/29/2016 12:21 PM, Offer Baruch wrote:
well, this worked just perfectly...
i do have one more question...
will the STARMS
well, this worked just perfectly...
i do have one more question...
will the STARMSG *MSGALL only trap messages that comes out of my rexx or
might it also catch anything else?
am i risking catching anything?
thanks!!!
On Tue, Nov 29, 2016 at 1:04 PM, Rob van der Heij wrote:
> On 29 November 201
On 29 November 2016 at 11:36, Offer Baruch wrote:
> Thank you all for the info... but at what phase do i execute the rexx i am
> trying to trap his output?
> How does the cms or cp stages trap the output? Can't i do the same in one
> new pipe?
>
The program in my example was OFFER EXEC that con
Thank you all for the info... but at what phase do i execute the rexx i am
trying to trap his output?
How does the cms or cp stages trap the output? Can't i do the same in one
new pipe?
Thanks again
On Nov 29, 2016 10:34, "Rob van der Heij" wrote:
> > I think that if you use *MSGALL, no need to
> I think that if you use *MSGALL, no need to use SET VMCONIO IUCV and SET
> CPCONIO IUCV first. *MSGALL traps anything that would have been sent to
> the console, regardless of what you SET to IUCV.
When the pipes blow up in your face and get you trapped under the floor
boards in your basement,
I think that if you use *MSGALL, no need to use SET VMCONIO IUCV and SET
CPCONIO IUCV first. *MSGALL traps anything that would have been sent to
the console, regardless of what you SET to IUCV.
Stronger: if you'd have an active path to *MSG (e.g. WAKEUP (IUCVMSG is
active), the message classes se
On Monday, 11/28/2016 at 08:33 GMT, "John P. Hartmann"
wrote:
> Alan, CMS does not trap commands that are forwarded to CP by the default
> setting IMPCP on; nor explicitly by the CP command of CMS.
Yah, I know. :-) Believe me, I KNOW. :-) :-) I realized that all of
my recent use was with G
This might supply a good starting point:
/*
**
*/
Address Command
Parse value Diag(8,'QUERY SET') with 1 . 'VMCONIO' vms . ',' 1 . 'CPCONIO'
pms . ','
nl = '15'x
Parse value Diag(8,'SET VMCONIO IUCV'nl'SET CPCONIO IUCV') with .
Parse arg stuffs
'PIPE var stuffs|starmsg *MSGALL|spec 17-* n|stem dum
That sounds interesting Rob... i will give it a try...
Thanks!
Offer
On Nov 28, 2016 21:31, "Rob van der Heij" wrote:
> > I am trying to capture the output of a Rexx exec. the Rexx contains both
> > CMS and CP commands...
> > I would like to capture this output into a stem variable...
>
> If th
Alan, CMS does not trap commands that are forwarded to CP by the default
setting IMPCP on; nor explicitly by the CP command of CMS.
I'd say SPOOL the console. Or perhaps read the manual.
It is true that
PIPE literal | starmsg | ...
will do as requested, but I'm sure something will go
On Monday, 11/28/2016 at 07:06 GMT, Offer Baruch
wrote:
> Hello everyone,
>
> I am new to the list and need some assistance...
>
> I am trying to capture the output of a Rexx exec. the Rexx contains both
> CMS and CP commands...
> I would like to capture this output into a stem variable...
>
> so
Sounds a bit painful. Should there be a builtin stage to do this?
On Mon, Nov 28, 2016 at 2:16 PM, Rob van der Heij
wrote:
> > I am trying to capture the output of a Rexx exec. the Rexx contains both
> > CMS and CP commands...
> > I would like to capture this output into a stem variable...
>
>
> I am trying to capture the output of a Rexx exec. the Rexx contains both
> CMS and CP commands...
> I would like to capture this output into a stem variable...
If the program is asking CP to write the response directly to the terminal, then
the only option I see is routing all console output thr
Hello everyone,
I am new to the list and need some assistance...
I am trying to capture the output of a Rexx exec. the Rexx contains both
CMS and CP commands...
I would like to capture this output into a stem variable...
something like:
PIPE | STEM output.
At the moment i feel like i am in a d
17 matches
Mail list logo
