I felt that the SPEC doesn't and much complication to the pipeline:
"PIPE (endchar ?)",
"| STEM SYS.",
"|0:PICK 6.3 \== /54B/",
"|2:PICK W-1 == /1/",
"|s:PICK 9.1 \== /S/",
"|p:PICK 9.1 \== /P/",
"| SPEC /VM1/ 1.8 1-* NW RECNO FROM" X2D(2000) "D2X NW.4 RIGHT
/C/ NW",
"|i:FANINANY",
"| SPEC W2 X2C 1.2 W1 N.8 W2 NW.4 W3 NW.6 W4 NW.8 W5 NW.4 W6 NW.7
W7 NW.8 RIGHT W10-* NW",
"| SORT 3.8 1.2",
"| SPEC 3-* 1",
"| PREFACE STRLITERAL '*Phase rCCUU VolSer User Id. vCCUU
DevType Cyls New How'",
"| PREFACE STRLITERAL
'*---------------------------------------------------------------'",
"| PREFACE STRLITERAL '* How: (C)opy, (R)eassign & (F)ormat
for VM usage'",
"| PREFACE STRLITERAL '* VM0 - Prior to any migration
(testing)'",
"| PREFACE STRLITERAL '* VM1 - z/VM system'",
"| PREFACE STRLITERAL '* VM2 - Misc. VM volumes'",
"| PREFACE STRLITERAL '* UAGLOBE - UA/Globe migration'",
"| PREFACE STRLITERAL '* AIL2 - AIL test volumes
(reassigned)'",
"| PREFACE STRLITERAL '* AIL1 - AIL production volumes and
flashcopy'",
"| > MIGDASD TABLE A",
"?s:",
"| SPEC /VM1/ 1.8 1-* NW RECNO FROM" X2D(200C) "D2X NW.4 RIGHT W7
NW",
"|i:",
"?p:",
"| SPEC /VM1/ 1.8 1-* NW RECNO FROM" X2D(2010) "D2X NW.4 RIGHT W7
NW",
"|i:",
"?2:",
"| SPEC /VM2/ 1.8 1-* NW RECNO FROM" X2D(2040) "D2X NW.4 RIGHT W7
NW",
"|q:FANINANY",
"|i:",
"?0:",
"| SPEC /VM0/ 1.8 1-* NW RECNO FROM" X2D(2020) "D2X NW.4 RIGHT W7
NW",
"|q:",
"? STEM AIL.",
"|t:PICK W3 \== /AILTEST/",
"|f:PICK 1.1 \== /9/",
"| SPEC /AIL1/ 1.8 1-* NW RECNO FROM" X2D(2100) "D2X NW.4 RIGHT
W7 NW",
"|i:",
"?f:",
"| SPEC /AIL1/ 1.8 1-* NW RECNO FROM" X2D(F100) "D2X NW.4 RIGHT
a: 6.3 .",
'IF a=="MOD" THEN',
"/C/ NW",
'ELSEIF a=="MVS" THEN',
"/C/ NW",
"ELSE",
"/R/ NW",
"ENDIF",
"|i:",
"?t:",
"| SPEC /AIL2/ 1.8 1-* NW RECNO FROM" X2D(2500) "D2X NW.4 RIGHT
/R/ NW",
"|i:",
"? STEM UA.",
"|j:PICK 1.1 \== /7/",
"|k:PICK 1.1 \== /8/",
"|b:PICK W6 == /10017/",
"| SPEC /UAGLOBE/ 1.8 1-* NW RECNO FROM" X2D(2800) "D2X NW.4
RIGHT W7 NW",
"|i:",
"?j:",
"| SPEC /UAGLOBE/ 1.8 1-* NW RECNO FROM" X2D(FA00) "D2X NW.4
RIGHT a: 6.3 .",
'IF a=="MOD" THEN',
"/C/ NW",
'ELSEIF a=="MVS" THEN',
"/C/ NW",
"ELSE",
"/R/ NW",
"ENDIF",
"|i:",
"?k:",
"| SPEC /UAGLOBE/ 1.8 1-* NW RECNO FROM" X2D(F800) "D2X NW.4
RIGHT a: 6.3 .",
'IF a=="MOD" THEN',
"/C/ NW",
'ELSEIF a=="MVS" THEN',
"/C/ NW",
"ELSE",
"/R/ NW",
"ENDIF",
"|i:",
"?b:",
"| SPEC /UAGLOBE/ 1.8 1-* NW RECNO FROM" X2D(2A00) "D2X NW.4
RIGHT W7 NW",
"|i:"
Translation: I have three STEM variables that represent categories of
DASD. (We are migrating from DS8100 to a DS8870.) This further
categories the DASD into "production", "flashcopy" (Fxxx), etc. and
assigns an address (using an address converted to a decimal for RECNO).
These MOD & MVS prefixed volume serial number need to be (C)opied
(rather than just (R)edefined in the VM directory).
I know TMI!
Since this is a conversion, I don't expect any more usage of this PIPE
(EXEC) after the conversion is complete.
Okay, I've opened myself up now...completely exposed....let the games
(criticisms) begin!
Frank M. Ramaekers Jr.
> -----Original Message-----
> From: CMSTSO Pipelines Discussion List [mailto:CMS-
> [email protected]] On Behalf Of Rob van der Heij
> Sent: Friday, April 25, 2014 8:22 AM
> To: [email protected]
> Subject: Re: [CMS-PIPELINES] SPEC with multiple IFs.
>
> I would be tempted to call this abuse of the spec stage ... I'd
suggest
>
> | a: if locate 6.3 /MVS/
> | spec ...
> | a:
> | b: if locate 6.3 /MON/
> | spec ...
> | b:
> | a:
>
>
> Actually, I'm pretty sure I would code a 'lookup' that matches the
3-char key in
> the table and picks up the snippet to append to the record...
>
> Rob
>
>
> On 25 April 2014 15:12, Hobart Spitz <[email protected]
<mailto:[email protected]> > wrote:
>
> > Mike said:
> > > I think this is one of those cases where specs requires that a
> > > string
> > be
> > > delimited specifically with double quotes.
> >
> > I'm tempted to say that there is no such thing, but I've learned
that
> > such statements are risky. If there is, I'd like to know for sure;
if
> > not, we owe it to the list to get the correct answer.
> >
> > That said, I would go back to the original, and run it with TRACE I,
> > and repost the results with a mono-spaced font. Perhaps there is
are
> > two single quotes that look like a double quote, or vice versa,
e.g..
> >
> >
> >
> >
> > On Thu, Apr 24, 2014 at 9:24 PM, Frank M. Ramaekers
> > <[email protected] <mailto:[email protected]> >wrote:
> >
> > > Yes, double-quotes did the trick. Never would have guessed.
> > >
> > > Frank M. Ramaekers Jr.
> > >
> > > > -----Original Message-----
> > > > From: CMSTSO Pipelines Discussion List [mailto:CMS-
> > > > [email protected] <mailto:[email protected]> ] On
Behalf Of Michael Harding
> > > > Sent: Thursday, April 24, 2014 4:29 PM
> > > > To: [email protected]
<mailto:[email protected]>
> > > > Subject: Re: [CMS-PIPELINES] SPEC with multiple IFs.
> > > >
> > > > I think this is one of those cases where specs requires that a
> > > > string
> > > be
> > > > delimited specifically with double quotes.
> > > >
> > > > --
> > > > Mike Harding
> > > > z/VM System Support
> > > >
> > > > [email protected] <mailto:[email protected]>
> > > > [email protected] <mailto:[email protected]>
> > > > (925) 926-3179 (w)
> > > > (925) 323-2070 (c)
> > > > /sp
> > > >
> > > >
> > > > CMSTSO Pipelines Discussion List <[email protected]
<mailto:[email protected]> >
> > > > wrote
> > > on
> > > > 04/24/2014 01:40:29 PM:
> > > >
> > > > > From: "Frank M. Ramaekers" <[email protected]
<mailto:[email protected]> >
> > > > > To: [email protected]
<mailto:[email protected]>
> > > > > Date: 04/24/2014 01:41 PM
> > > > > Subject: Re: SPEC with multiple IFs.
> > > > > Sent by: CMSTSO Pipelines Discussion List
> > > > > <[email protected]
<mailto:[email protected]> >
> > > > >
> > > > > After correcting the missing comma and using ELSEIF, it ends
> > > > > with a
> > > > cryptic:
> > > > >
> > > > >
> > > > >
> > > > > "| SPEC /UAGLOBE/ 1.8 1-* NW RECNO FROM" X2D(F800) "D2X
> > > > > NW.4 RIGHT a: 6.3 .",
> > > > >
> > > > > "IF a==/MOD/ THEN",
> > > >
> > > > >
> > > > > "/C/ NW",
> > > >
> > > > >
> > > > > "ELSEIF a==/MVS/ THEN",
> > > >
> > > > >
> > > > > "/C/ NW",
> > > >
> > > > >
> > > > > "ELSE",
> > > >
> > > > >
> > > > > "/R/ NW",
> > > >
> > > > >
> > > > > "ENDIF",
> > > >
> > > > >
> > > > > PIPYAC1434E Parse error in state 137, unexpected O_MULT at
offset
> 3:
> > > > > "/MOD/ THEN /C/ NW ELSEIF a==/MVS/ THEN /C/ NW ELSE /R/ NW
> ENDI
> > > > >
> > > > > F".
> > > >
> > > > >
> > > > > PIPMSG003I ... Issued from stage 2 of pipeline 11.
> > > >
> > > > >
> > > > > PIPMSG001I ... Running "SPEC /UAGLOBE/ 1.8 1-* NW RECNO FROM
> > > > > 63488
> > > > D2X
> > > > > NW.".
> > > > >
> > > > > PIPYAC1435I Expecting T_IDLETTER T_NUMBER T_QSTRING T_IDENT
> > > > T_ID_CHAR
> > > > > T_CTR T_DOT T_DOTDOT T_CTRARRAY S_LP O_PLUS O_NOT F_FIRST
> F_EO
> > > > >
> > > > > F F_BREAK F_C2D F_C2F F_X2D F_X2F F_STRING F_AVERAGE
> F_VARIANCE
> > > > > F_NUMBER F_EXACT F_SQRT F_STDDEV F_STDERRMEA
> > > > >
> > > > > PIPSPE192I ... Scan at position 69; previous data "OM 63488
D2X
> > > > > NW.4 RIGHT a: 6.3 . IF a==/".
> > > > >
> > > > >
> > > > >
> > > > > Frank M. Ramaekers Jr.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > >
> > > > > > From: CMSTSO Pipelines Discussion List [mailto:CMS-
> > > > >
> > > > > > [email protected] <mailto:[email protected]> ]
On Behalf Of Kris Buelens
> > > > >
> > > > > > Sent: Thursday, April 24, 2014 3:24 PM
> > > > >
> > > > > > To: [email protected]
<mailto:[email protected]>
> > > > >
> > > > > > Subject: Re: [CMS-PIPELINES] SPEC with multiple IFs.
> > > > >
> > > > > >
> > > > >
> > > > > > I don't know if that will help: PIPE alos has ean ELSEIF
> > > > >
> > > > > >
> > > > >
> > > > > > "ELSEIF a==/MVS/ THEN",
> > > > >
> > > > > > "/C/ NW",
> > > > >
> > > > > >
> > > > >
> > > > > >
> > > > >
> > > > > > Kris Buelens,
> > > > >
> > > > > > --- freelance z/VM consultant, Belgium ---
> > > > >
> > > > > >
> > >
--------------------------------------------------------------------
> > > > > > ---
> > > > >
> > > > > >
> > > > >
> > > > > >
> > > > >
> > > > > > 2014-04-24 22:19 GMT+02:00 Joe Parker <[email protected] <
> > > > > mailto:[email protected] <mailto:[email protected]> > >:
> > > > >
> > > > > >
> > > > >
> > > > > > > Well, it's been quite a few years since I wrote any pipe
> > > > > > > code,
> > > > but....
> > > > >
> > > > > > > could it be there's a comma missing in the first line?
> > > > >
> > > > > > >
> > > > >
> > > > > > > > Date: Thu, 24 Apr 2014 15:13:22 -0500
> > > > >
> > > > > > > > From: [email protected]
<mailto:[email protected]>
> <mailto:[email protected] <mailto:[email protected]> >
> > > > >
> > > > > > > > Subject: SPEC with multiple IFs.
> > > > >
> > > > > > > > To: [email protected]
<mailto:[email protected]>
> > > > <mailto:[email protected]
<mailto:[email protected]> >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > I can't seem to find information on what could be wrong
> > > > > > > > with
> > > this:
> > > > >
> > > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "| SPEC /xxxx/ 1.8 1-* NW RECNO FROM" X2D(F800) "D2X
NW.4
> > > > RIGHT a:
> > > > >
> > > > > > > > 6.3 ."
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "IF a==/MOD/ THEN",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "/C/ NW",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "ELSE",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "IF a==/MVS/ THEN",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "/C/ NW",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "ELSE",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "/R/ NW",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "ENDIF",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > "ENDIF",
> > > > >
> > > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > I'm not getting the output I expect (I don't see PIPE
> > > > > > > > flagging
> > > > >
> > > > > > > > anything). I've only had single IF's in the past.
> > > > >
> > > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > Frank M. Ramaekers Jr. | Systems Programmer |
Information
> > > > Technology
> > > > >
> > > > > > > > | American Income Life Insurance Company | 254-761-6649
> > > > >
> > > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > >
> > > > >
> > > > > > >
> > > > >
> > >
> >
> >
> >
> > --
> > OREXXMan
> >
