In that case
parse value diagrc(8,' SPOOL CONS CLOSE OPERATOR ') with cprc
cpcc cpmsg
if he wants to see both the the return code and the message or
parse value diag(8, 'SPOOL CONS OPERATOR CLOSE') with cpmsg
if he doesn't care about the rc or cc from CP but does want to see the
message. Yet another way would be
y = diag(8,'SPOOL CONSOLE OPERATOR CLOSE)
and then process the variable Y. If all that us wanted is to keep the
response from showing up on the console, then a simple
call diag 8, 'SPOOL CONS OPERATOR CLOSE
will do the trick.
Maybe many start with that type of simple Pipe, but they need to learn
that Pipes is not the correct tool for every job. There are many places
where a Pipe is the best tool, but for something like processing a
simple command that only returns a small amount of data in its response
or if the desire is simply to suppress the display of the response,
there are better ways. I have known many people who learned to use
Pipelines as a replacement for EXECIO (and, as Phil Smith III likes to
point out, there are places where EXECIO is superior to Pipelines) and
who have written many complex REXX programs who still, after several
years, have never progressed beyond code that looks like this:
'pipe cp cmd1'
'pipe cp cmd2'
. . .
'pipe cp cmdn'
(Yes, Alan, most who code like this commit that other sin of not
including an "address command" statement in their programs.)
Regards,
Richard Schuh
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Hughes, Jim
Sent: Thursday, July 17, 2008 5:56 AM
To: [email protected]
Subject: Re: Some REXX exec help needed.
Pretty harsh comment there Richard.
It seems he'd like to eat up the response to the Close command
and perhaps process the result. The CP command as you wrote it
displays it on the console. The DIAG command as you wrote it also
displays the output on the console.
How about cutting me some slack? Many people start using
PIPE's with a simple one like mine.
____________________________
Jim Hughes
603-271-5586
"Its kind of fun to do the impossible." (Walt Disney)
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard
Sent: Wednesday, July 16, 2008 5:36 PM
To: [email protected]
Subject: Re: Some REXX exec help needed.
Even cheaper,
say diag(8, 'SPOOL CONS CLOSE OPERATOR')
or
'CP SPOOL CONS CLOSE OPERATOR'
Why invoke Pipelines when there are both an internal function
and a simple command that will do the job with much less overhead (no
scanner, scheduler, etc.). This is a case of blatant misuse of
Pipelines.
Regards,
Richard Schuh
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Hughes, Jim
Sent: Wednesday, July 16, 2008 2:25 PM
To: [email protected]
Subject: Re: Some REXX exec help needed.
It works for me.
On the other hand why not make life easier on yourself
and PIPE it:
PIPE LITERAL CLOSE CONS OPERATOR | CP | Stem ans. "
____________________________
Jim Hughes
603-271-5586
"Its kind of fun to do the impossible." (Walt Disney)
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Howard Rifkind
Sent: Wednesday, July 16, 2008 5:19 PM
To: [email protected]
Subject: Re: Some REXX exec help needed.
Yes it did as indicated below, but shouldn't this have
appeared in the reader stack as shown by keying in the following at the
console?
CLOSE CONS OPERATOR
CON FILE 0227 SENT TO OPERATOR RDR AS 0063 RECS 0017
CPY 001 T NOHOLD NOKEEP
Ready;
CP Q RDR OPERATOR
ORIGINID FILE CLASS RECORDS CPY HOLD USERFORM OPERFORM
DEST KEEP MSG
E18823 0063 T CON 00000017 001 NONE STANDARD STANDARD
OFF OFF OFF
Ready;
>>> "Hughes, Jim" <[EMAIL PROTECTED]> 7/16/2008 5:14
PM >>>
If the console was spooled, it went to operator.
CP Q RDR OPERATOR and see if a console spool file is
there.
____________________________
Jim Hughes
603-271-5586
"Its kind of fun to do the impossible." (Walt Disney)
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Howard Rifkind
Sent: Wednesday, July 16, 2008 5:13 PM
To: [email protected]
Subject: Re: Some REXX exec help needed.
This is what shows up during execution:
204 *-* 'EXECIO * CP (STRING CLOSE CONS OPERATOR'
>>> "EXECIO * CP (STRING CLOSE CONS OPERATOR"
205 *-* MAXLINES = QUEUED()
>>> "0"
>>> "Hughes, Jim" <[EMAIL PROTECTED]> 7/16/2008 5:09
PM >>>
Yes.
____________________________
Jim Hughes
603-271-5586
"Its kind of fun to do the impossible." (Walt Disney)
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Howard Rifkind
Sent: Wednesday, July 16, 2008 5:06 PM
To: [email protected]
Subject: Re: Some REXX exec help needed.
Thanks...
Is my EXECIO statement valid?
>>> "Hughes, Jim" <[EMAIL PROTECTED]> 7/16/2008 5:03
PM >>>
MAKEBUF not MAKBUF hence the -3.
____________________________
Jim Hughes
603-271-5586
"Its kind of fun to do the impossible." (Walt Disney)
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Howard Rifkind
Sent: Wednesday, July 16, 2008 5:00 PM
To: [email protected]
Subject: Some REXX exec help needed.
I have the following code in a REXX exec which if I
recall worked without any issues in a prior life.
'MAKBUF'
BUFFNUM = RC
'EXECIO * CP (STRING CLOSE CONS OPERATOR'
The MAKBUF is returning an RC of -3
and the EXECIO statement isn't working but did in the
past.
I know this is crazy but all this started after I logged
off and then back on.
Any ideas as how to solve this will be appreciated.
Thanks.
_____________
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.
_____________
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.
_____________
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.
_____________
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.
