Richard,

You must be pretty ill;  your recent posts have been atypical.  My 
suggestion that SFS responses *might* be somehow handled by CP was only 
because SFS has exhibited some unintuitive behavior (those with high a 
"astonishment factor") in the past.

I tried (using more modern plumbing) from z/VM 5.1 and Pipes works fine 
here.
BTW, thanks for the examples to help retry the problem, they were just 
what was needed even if I cannot recreate the problem.

---<snip>---
enroll user test gen01: (blo 10 
M2WALTER HALINVA1; T=0.01/0.01 13:22:03 
type richards file a 
 
DELETE USER TEST GEN01: (TYPE NOCONF 
 
M2WALTER HALINVA1; T=0.01/0.01 13:22:10 
PIPE < RICHARDS FILE A | COMMAND | CONSOLE 
Deleted USERs: 
TEST 
M2WALTER HALINVA1; T=0.01/0.01 13:22:31 
enroll user test gen01: (blo 10 
M2WALTER HALINVA1; T=0.01/0.01 13:22:34 
PIPE < RICHARDS FILE A | COMMAND CMDCALL | CONSOLE 
Deleted USERs: 
TEST 
M2WALTER HALINVA1; T=0.01/0.01 13:22:39 
q cmslevel 
CMS Level 21, Service Level 501 
M2WALTER HALINVA1; T=0.01/0.01 13:22:44  
---<snip>---

Going back to the "sanctioned", vanilla Pipes distributed with z/VM 510 
did not yield any difference:
---<snip>---
pickpipe esa  
FPLINX086I CMS/TSO Pipelines, 5741-A05/5655-A17 1.0110 
(Version.Release/Mod) - G
enerated 22 Jul 2004 at 09:53:44  
Source:  z/VM 5.1.0  
M2WALTER HALINVA1; T=0.03/0.04 13:28:24  
enroll user test gen01: (blo 10  
M2WALTER HALINVA1; T=0.01/0.01 13:28:44  
PIPE < RICHARDS FILE A | COMMAND CMDCALL | CONSOLE  
Deleted USERs:  
TEST  
M2WALTER HALINVA1; T=0.01/0.01 13:28:50  
---<snip>---

So... a question that has not been asked directly before even though the 
answer has been indirectly implied: has this ever worked before?  If so, 
what changed?  If not, perhaps it is time to open a PMR since it works at 
other sites.

Good Hunting!

Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.



"Schuh, Richard" <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
12/15/2006 12:07 PM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: COMMAND vs. CMS






Try too sick to want to do it at the time. I didn't know that you had
become a Unix bigot.


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Friday, December 15, 2006 12:33 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: COMMAND vs. CMS

On Fri, 15 Dec 2006 00:13:43 -0500, Rick Troth <[EMAIL PROTECTED]> wrote:

>Do you have a COMMAND REXX in the mix intercepting the built-in?
>
>-- R;
Sorry Rick, but when you code 'xxx' as stage PIPE first looks for a
built= -in stage, only if not found, it looks for "xxx REXX".

As Richard was too lazy/didn't understand/didn't dare/ ... I ran a
series=  of commands to show the use of CMDCALL with SFS.  It also
proves that DELETE=

USER works perfectly well from under the COMMAND stage.  You truly NEED
t= he CMDCALL prefix to find out what goes wrong with SFS commands.

 ENRoll user TEST
 Ready KRIS at VMKBBR01 ; T=0.01/0.01 08:25:09  ENRoll user TEST
DMSJEN1166E Userid TEST is already enrolled  Ready KRIS at VMKBBR01
(00040); T=0.01/0.01 08:25:41  PIPE COMMAND ENROLL USER TEST!CONS  Ready
KRIS at VMKBBR01 (00040); T=0.01/0.01 08:25:49  PIPE COMMAND CMDCALL
ENROLL USER TEST!CONS  DMSJEN1166E Userid TEST is already enrolled
Ready KRIS at VMKBBR01 (00040); T=0.01/0.01 08:25:56

 delete user TEST2 (Noconf
 Deleted USERs:
 TEST2
 DMSJDE1224W One or more userids were not enrolled as USERs  Ready KRIS
at VMKBBR01 (00004); T=0.01/0.01 08:27:15  PIPE COMMAND DELETE USER
TEST2 (NOCONF!CONS  Deleted USERs:
 TEST2
 Ready KRIS at VMKBBR01 (00004); T=0.01/0.01 08:27:29  PIPE COMMAND
CMDCALL DELETE USER TEST2 (NOCONF!CONS  Deleted USERs:
 TEST2
 DMSJDE1224W One or more userids were not enrolled as USERs  Ready KRIS
at VMKBBR01 (00004); T=0.01/0.01 08:27:46  PIPE COMMAND CMDCALL DELETE
USER TEST (NOCONF!CONS  Deleted USERs:
 TEST
 Ready KRIS at VMKBBR01 ; T=0.01/0.01 08:28:26

In EXECs I often use constructs like this when dealing with SFS
commands:=

    'PIPE COMMAND CMDCALL LISTDIR' JobDirid '(NOSUB', 
       '!VAR EMSG!DROP!CHOP 1!Var fm'            =
 
    select                     =
 
     when rc=28 then jobmode='-'             =
 
     when rc<>0 then call ErrExit rc,emsg           =
 
     otherwise /* Job found.  Access dirid */          =

      if fm='-' then do                =
 
         Call CSL 'DMSGETFM RC REAS jobmode'          =
 
Key points are CMDCALL and VAR EMSG!DROP.  Because with CMDCALL you not
o= nly get error messages but also headers appear.  In general -with
CMDCALL- th= e first line is either an error message, either a
headerline.

CMDCALL can also help the lazy ones.  Everyone should know that decent
ex= ecs run with ADDRESS COMMAND.  As a result, STAE for example doesn't
produce error messages.  Sometimes though STATE's error message is
usefull for la= zy
programmers:
  Not so lazy
    'STATE' inputfile
    if rc<>0 then do
        say 'Input file "'inputfile'" not found'; exit rc; end
  Lazy, but more, extact, error information is displayed
    'CMDCALL STATE' inputfile
    if rc<>0 then exit rc

All this is explained in great detail in both "telecourses" Guy De
Ceulae= r and I produced. 
Advanced REXX:
  http://www.vm.ibm.com/download/packages/descript.cgi?TCVM1
  (look for Lesson1, Chapter 3)
Pipelines:
  http://www.vm.ibm.com/download/packages/descript.cgi?TCVM
  (look for Lesson2, Chapter 3)

Yours Knigth of VM,
Kris Buelens



 
The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient 
is strictly prohibited.


Reply via email to