Re: [CMS-PIPELINES] Question about starsys *vmevent handling......

I think Rob hit the nail on the head. STARSYS tries a 2-way IUCV connection but *VMEVENT is 1-way. You should be using STARMSG instead as it's also 1-way. -- Mike Harding z/VM System Support mhard...@us.ibm.com mikehard...@mindless.com (925) 672-4403 (o) (925) 323-2070 (m) (925) 672-3922 (h) /sp

Re: [CMS-PIPELINES] swap two records

323-2070 (m) /sp CMSTSO Pipelines Discussion List wrote on 08/14/2019 11:22:45 AM: > From: Rob van der Heij > To: CMS-PIPELINES@VM.MARIST.EDU > Date: 08/14/2019 11:23 AM > Subject: [EXTERNAL] Re: swap two records > Sent by: CMSTSO Pipelines Discussion List > > On Wed, 14 Au

Re: [CMS-PIPELINES] swap two records

Perhaps simpler, as a rexx stage: Parse arg tag . 'CallPipe (End ?) *:', '|a:Pick anycase from 1+ == /'tag'/ count 2', '|Spec a: 1-* . set #0:=a read 1-* n write print #0 1', '|b:Faninany', '|*:', '?a:|b:' Exit Rc -- Mike Harding z/VM System Support mhard...@us.ibm.com

Re: [CMS-PIPELINES] Punch and deblock

4 you are allowed to simply |substr 2-*| > rather than starting all of SPEC. Sort of like getting on your scooter > board rather than starting up the combine harvester to go buy a pint of > milk. > > On 1/26/19 00:55, Michael Harding wrote: > > Forgive me, it's Friday.

Re: [CMS-PIPELINES] Punch and deblock

Forgive me, it's Friday. With a nod in the direction of ancient wisdom, you're mostly right. In this case though he just need to take a cue from the proffered code and ignore records without the leading x'41' (stacker select) then strip that: "reader | strfind x41 | spec 2-* n | deblock cms | >

Re: [CMS-PIPELINES] SPECS IF ... comparing strings

Easy, use a specs variable: ... '|Specs a: w -1 . . if a=="stuff" then ... else ... endif The last I knew, double-quotes were the only acceptable delineator for this construct but that may have changed. -- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List wrote on

Re: [CMS-PIPELINES] Selecting multiple record chunks

Simple case of "sipping" pipeline: 'PIPE (End ?)', '<' infile, '|pck:rexx *.1:', '|Cons', '?Literal /* */ Signal On error;', 'Do forever; "Peekto";', /* test if any input */ '"CallPipe *:||FromTarget Pick 5.2 == /99/ || take 4|| *:";', 'End; Error: Exit Rc*(Rc<>12)', '|pck:' -- Mike Harding

Re: [CMS-PIPELINES] getting the RC from third party commands

No, the command and cms stages are documented to write all command output before writing the return code to the secondary stream, which is easily verified. The stall occurs because command was stuck writing the return code before it posted eof on its primary. A simple elastic stage on the second

Re: [CMS-PIPELINES] getting the RC from third party commands

Why not just run the VMSECURE module from the COMMAND stage? It knows how to communicate with the VMSECURE machine, displays the messages and sets the return code, both of which COMMAND will capture. For example... 'pipe (stagesep ! endchar ?)', ' Var vmcmd', /* assumed to be "vmsedure"

Re: [CMS-PIPELINES] Variable field selection

Agree with Alan. Any unspecified argument is "OMITTED". Note that z/VM Rexx, OpenObject Rexx and Regina Rexx all specify Arg() as returning the number of the last EXPLICIT argument. That doesn't mean your subroutine/function can't look for more as long as it can handle their being null. Or in

Re: [CMS-PIPELINES] Variable field selection

Too sly, but inventive! I personally like to code "parse value function() with ."; safe with or without a returned value. -- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List wrote on 05/03/2017 11:39:04 AM: > From: Rob van der Heij

[CMS-PIPELINES] Variable field selection

I thought I remembered an idiom in specs for specifying field selections when the field separation character wasn't known before hand, but now can't find or seem able to reinvent it. The equivalent of the ability in Rexx to assign a value to a variable and use that variable as a separator later in

Re: [CMS-PIPELINES] Pipethink and filtering. CP QUERY PATHS 0-FFFF

Yes, for the result the OP finally stated I agree joincont would be the way to go, but that was unclear in the original post. Thus the "'||join * /;/', /* process one group here */" in my post to suggest additional logic could be applied even though yes, that too could in most cases could

Re: [CMS-PIPELINES] Pipethink and filtering. CP QUERY PATHS 0-FFFF

Perfect for a sipping stage I thought when I read the initial post, before seeing the "pure pipes" preference; then I wondered if an equivalent could be accomplished with pipcmd. Attempting - Address Command 'PIPE (end ?) cp Q PATHS E1D8-E1DB', '|a:Take last', /* legend line? */

Re: [CMS-PIPELINES] SPEC IF String equality comparison and output including Field identifiers.

Also... older pipes didn't like the use of a named range as the argument to print. Changing "print a" to "id a" would work. -- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List wrote on 12/14/2016 01:59:42 PM: > From: Rob van der Heij

Re: [CMS-PIPELINES] Not-always-directly-sequential record references in PIPEs

You could code some complicated conditionals and use counters in Specs, but much simpler: look into JUXTAPOSE. -- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List wrote on 09/22/2016 07:47:03 AM: > From: "Stanislawski, Shawn (National VM

Re: [CMS-PIPELINES] Incorrect Handling of Negative Numbers With PICK?

Wrong, that should be doing a numeric compare. Look it up. A comparison operator of <<= would be for a string compare. "<=" asks for numeric comparison. -- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List wrote on 08/23/2016 01:58:27 PM: >

Re: [CMS-PIPELINES] the STACK stage

Too complicated if he only wants the first stacked item. The VAR stage, without the TRACKING option assigns its first input to the variable then shorts. So the take 1 is unnecessary, and one possible solution is simply: PIPE Stack', '|Var expdt', '|Hole' would fit the bill. Or to build on

Re: [CMS-PIPELINES] Split a file into multiple files based on a string in the data

If your totarget immediately follows the fromtarget, they're triggering on the same record. You need to bypass feeding the first record to the totarget. Simplest case, you don't want keep the separator records: ... '|fromtarget locate /file/', '|drop 1', '|totarget locate /file/", ... If you

[CMS-PIPELINES]

CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU wrote on 07/31/2015 03:21:22 AM: From: John Hartmann pi...@vm.marist.edu To: CMS-PIPELINES@VM.MARIST.EDU Date: 07/31/2015 02:21 AM Subject: Re: Sent by: CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU pipe pipeline

Re: [CMS-PIPELINES] 1.1.12/000C is available for download.

CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU wrote on 07/30/2015 08:33:51 AM: From: John Hartmann pi...@vm.marist.edu To: CMS-PIPELINES@VM.MARIST.EDU Date: 07/30/2015 07:34 AM Subject: 1.1.12/000C is available for download. Sent by: CMSTSO Pipelines Discussion List

Re: [CMS-PIPELINES] Capturing output from a pipe

CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU wrote on 07/20/2015 11:14:32 AM: From: Paul Gilmartin paulgboul...@aim.com To: CMS-PIPELINES@VM.MARIST.EDU Date: 07/20/2015 11:14 AM Subject: Re: Capturing output from a pipe Sent by: CMSTSO Pipelines Discussion List

[CMS-PIPELINES] Assertion failure?

Any ideas? With latest plastic pipes, PIPINX409E Assert failure 01C4 at 01EF7632. PIPINX411I ... In FPLSPSRL; offset 08DA in FPLSPS 11/08/14 13.17. PIPINX412I ... GPR0: 000A 01F5738C 07C0 . PIPINX412I ... GPR4: 01F5A7C0 000C 01F5738C. PIPINX412I ... GPR8:

Re: [CMS-PIPELINES] Assertion failure?

. -- Dean Koontz, The Face Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU wrote on 07/16/2015 10:18:05 AM: From: Michael Harding/Oakland/IBM@IBMUS To: CMS-PIPELINES@VM.MARIST.EDU Date: 07/16/2015 10:18 AM Subject: Assertion failure? Sent

Re: [CMS-PIPELINES] Assertion failure?

wrote on 07/16/2015 12:33:07 PM: From: Michael Harding/Oakland/IBM@IBMUS To: CMS-PIPELINES@VM.MARIST.EDU Date: 07/16/2015 12:33 PM Subject: Re: Assertion failure? Sent by: CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU Poking around in the dump a bit, I figured out I was probably

Re: [CMS-PIPELINES] Pipe Hostid issue

CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU wrote on 07/13/2015 12:57:26 PM: From: Alan Altmark/Endicott/IBM@IBMUS To: CMS-PIPELINES@VM.MARIST.EDU Date: 07/13/2015 12:57 PM Subject: Re: Pipe Hostid issue Sent by: CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU

Re: [CMS-PIPELINES] Pipe Hostid issue

On Monday, 07/13/2015 at 04:30 EDT, Michael Harding/Oakland/IBM@IBMUS wrote: Interestingly, on one of our internal jumbo systems where the host returned by IDENTIFY will vary depending on one's cpuid as set up in the directory, the output from the socket(getname) call agrees with identify

Re: [CMS-PIPELINES] Output to the bit bucket

Don't even need to do that. 'pipe (endchar ?)', 'stem BST.', '| l: lookup', '?', 'stem VSE.', '| l:', '?', 'l:', '| specs /T:/ 1 1-* next', '| console' -- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List

[CMS-PIPELINES] Spec abend

Coming out of starmsg, originally I had ... '|Spec 17-* strip n', ... Fine, until I decided I wanted to retain leading blanks. Trying to be clever, I coded ... '|Spec a: 17-* . set #0:=Strip(a,T, ) print #0 n', ... Well that produced a surprise: PIPINX410E ABEND 00C5 at 01EF7024; PSW 03EC1000

Re: [CMS-PIPELINES] Gate behavior

In your original (iirc) the stage between starmsg and gate was keeping starmsg from seeing its output severed, so it would have waited forever (or until a pipestop). -- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU wrote on 11/03/2014

Re: [CMS-PIPELINES] Assert failure?

doesn't. -- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU wrote on 09/08/2014 12:36:18 PM: From: Michael Harding/Oakland/IBM@IBMUS To: CMS-PIPELINES@VM.MARIST.EDU Date: 09/08/2014 12:36 PM Subject: Re: Assert failure? Sent by: CMSTSO Pipelines

Re: [CMS-PIPELINES] Trying to use the Locate

I think you're expecting the results to flow out of the bottom of the pipe. If you moved the stage after the faninany (dropping the : a2 connection) you'd probably have what you want. That after all is where you're feeding the records selected by the locates. -- Mike Harding z/VM System

Re: [CMS-PIPELINES] saving the last section I skipped

or an elastic before DAM. On 07/01/2014 09:37 PM, Michael Harding wrote: Duh! Need more sleep I reckon. Should have seen the first, misunderstood DAM's behavior (and a trailing hole stage took care of that). Thanks again -- Mike Harding z/VM System Support /sp CMSTSO Pipelines

Re: [CMS-PIPELINES] saving the last section I skipped

CMSTSO Pipelines Discussion List CMS-PIPELINES@vm.marist.edu wrote on 07/01/2014 09:47:49 AM: From: Glenn Knickerbocker n...@bestweb.net To: CMS-PIPELINES@vm.marist.edu Date: 07/01/2014 09:48 AM Subject: Re: saving the last section I skipped Sent by: CMSTSO Pipelines Discussion List

Re: [CMS-PIPELINES] abend in z/CMS

IMO there's an incompatibility between something in the LE support and plastic pipes. I suffered similar abends a couple of years ago calling LDAPSRCH (GLDSRCH module) from a pipe until I reverted to the product (ESA) version of pipelines. I beat on it a while, and discussed it with John, but

Re: [CMS-PIPELINES] I'm stumped

away. Wouldn't you say that EOF is a break? On 09/05/2013 09:05 PM, Michael Harding wrote: This: '|Spec printonly EOF a: w3 . set #0+=1', 'if a#1 then', 'b: substr 1.8 of w2 . c: substr 9.6 of w2 .', 'set (#1:=a;#2:=b;#3:=c) fi', 'eof print #0 strip 5 /samples, max

Re: [CMS-PIPELINES] Help with DIRECTORY pipe

something: '| Spec w1-7 n a: w8 . b: w9 . c: w10 . if a^== then // nw if b^== then /xxx/ nw if c^== then /xxx/ nw fi fi fi' -- Mike Harding z/VM System Support mhard...@us.ibm.com mikehard...@mindless.com (925) 926-3179 (w) (925) 323-2070 (c) /sp CMSTSO Pipelines Discussion

[CMS-PIPELINES] Trick needed

How do you specify the size of an output object in specs at run time? I want to expand directory POOL statements myself. I have: '|gpa:Lookup w1 master detail', /* pull in any POOL records */ '|Spec a: w4 . b: w6 . Set (#0:=a;#1:=b) read', /* userid POOL LOW x HIGH y ... */ 'a: w1 . set

Re: [CMS-PIPELINES] Trick needed

:48:12 PM: From: Michael Harding/Oakland/IBM@IBMUS To: CMS-PIPELINES@vm.marist.edu, Date: 07/22/2013 03:50 PM Subject: Trick needed Sent by: CMSTSO Pipelines Discussion List CMS-PIPELINES@vm.marist.edu How do you specify the size of an output object in specs at run time? I want to expand

[CMS-PIPELINES] Pick input range inconsistency

pipe literal abcdef 123456|pick 1+ == /abc/|cons abcdef 123456 Ready; T=0.01/0.01 09:29:34 pipe literal abcdef 123456|pick 8+ == /123/|cons abcdef 123456 Ready; T=0.01/0.01 09:29:57 pipe literal abcdef 123456|pick 8+ == /1234/|cons abcdef 123456 Ready; T=0.01/0.01 09:30:25 pipe literal abcdef

Re: [CMS-PIPELINES] Pick input range inconsistency

, Michael Harding mhard...@us.ibm.com wrote: pipe literal abcdef 123456|pick 1+ == /abc/|cons abcdef 123456 Ready; T=0.01/0.01 09:29:34 pipe literal abcdef 123456|pick 8+ == /123/|cons abcdef 123456 Ready; T=0.01/0.01 09:29:57 pipe literal abcdef 123456|pick 8+ == /1234/|cons abcdef

Re: [CMS-PIPELINES] Pick input range inconsistency

to offend, but it would appear that you don't understand what 1+ means and when it is appropriate. Nor the finer points of substr. On 28 December 2012 19:28, Michael Harding mhard...@us.ibm.com wrote: I recognize 1+ isn't a valid input range, I was just surprised that pick didn't support

[CMS-PIPELINES] Starmon suppress?

Either I'm missing something or the SUPPRESS option on the STARMON stage isn't working. Being only interested in user domain records (domain 4), I have starmon samples suppress F7FF, yet coming out of the stage I'm seeing: Total Records 11739 Domain 4 Recs 486 Domain 0339

Re: [CMS-PIPELINES] Starmon suppress?

On Mon, Jan 9, 2012 at 9:19 PM, Michael Harding mhard...@us.ibm.com wrote: Either I'm missing something or the SUPPRESS option on the STARMON stage isn't working. Being only interested in user domain records (domain 4), I have starmon samples suppress F7FF, yet coming out of the stage

Re: [CMS-PIPELINES] Move files and preserve timestamps

I years ago set up a process to mirror the Marist pipelines site, which might be easily adaptable to your situation. It uses ftp as transport, and sets the timestamp of the local files to match the source. Send me a note off-list if you're interested. -- Mike Harding z/VM System Support

Re: [CMS-PIPELINES] reversing *parts* of a record

While all-pipes solutions are usually elegant and always inherently cool, either Bob's or the Piper's could be a challenge to build dynamically. I'd probably use one or the other - or something similar - for a fixed case, but I think Shimon's search for a generalized solution would be more easily