On Thu, 17 Jul 2008 08:55:44 -0400 Hughes, Jim said: >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.
I'm willing to cut you some slack as well as cut Richard some slack. His point is that there are some significant overhead associated with Pipelines (Richard's point) and there are some alternatives ( Rexx diag, which with minor changes from his examplle ... variable = diag(8, 'SPOOL CONS CLOSE OPERATOR') allows processing the response to the CLOSE command or SPOOL command) Is the overhead of Pipelines always bad? No. Do you need to be aware of it and understand it? Yes. It believe it was Kent Fiala at SAS that did some of the first looking at the issues that I remember. Pipelines is not a simple replacement for EXECIO or Rexx Diag function. Changing do i = 1 to r.0 .... 'EXECIO 1 DISKW .... (VAR VARIABLE' end to do i = 1 to r.0 .... 'PIPE var variable | >>' file end could be a make things significantly slower. Conceptualy, changing that to do i = 1 to r.0 .... 'EXECIO 1 CP .... (STR' command end to do i = 1 to r.0 .... 'PIPE CP' command '| var xyz' end is not much different. The second will run slower. Move the PIPE outside the loop, and it exists in an EXEC that runs for 10 minutes anyway, and you might not notice it. In a 15,000 line EXEC with no other EXECIOs, would I choose PIPE CP over EXECIO, probably. Forcing whoever has to support the EXEC to switch mental gears between EXECIO and PIPE is probably not worth the 0.2 ms of extra CPU time when it is run, unless it is run thousands of times per day. What was MY first pipe? Don't remember, probably the Hello World, or some other sample from Melinda's paper. Or probably that other faux pas 'PIPE <' file '| stem recs.' (One test I ran a couple years ago showed that I could read most files 3 or 4 times in the time of 1 loading it into a stem. Even for large files.) Richard's point is that every tool has a proper place, and be careful to choose the proper tool. /ahw >____________________________ >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: IBMVM@LISTSERV.UARK.EDU >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: IBMVM@LISTSERV.UARK.EDU > 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: IBMVM@LISTSERV.UARK.EDU > 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: IBMVM@LISTSERV.UARK.EDU > 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: IBMVM@LISTSERV.UARK.EDU > 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: IBMVM@LISTSERV.UARK.EDU > 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. >
