|
View previous topic :: View next topic
|
| Author |
Message |
vikas kumar jain
New User
Joined: 02 Aug 2006
Posts: 9
Location: noida
|
|
|
|
I've a very long line to pass through JCL to a proc. It's as follows :
//SUBJECT=&MAR.USERID.&LIne.PLEASE&line.VERIFY&line.MRGWSBRO
// &line.BESTANDEN&line.ABR&line.AANWEZIG&line.
I've tried to give X,* etc at 72 column for continuation.
But it's not working...it's taking only first line and neglecting second. can u suggest ? |
|
| Back to top |
|
 |
mtaylor
Active User
Joined: 20 Feb 2009
Posts: 108
Location: Kansas City
|
|
|
|
The only way a statement will continue to the next line is if the last character in the parameter list is a comma OR if it's an unclosed string literal that ends at column 71 (then continues at column 16 on the next, non comment line). IF statements continue until the THEN key word is found. A character in column 72 of an uncontinued line indicates the next line is a comment.
So to sum up: you can't do that. |
|
| Back to top |
|
|
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
As mtaylor outlined the requirements (which you may have looked up already?) :
1. enclose string in quotes
2. code line 1 thru col 71
3. 'x' in col 72
4. continue line 2 in col 16
You can do a continuation like that. |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
|
|
| Bill Dennis wrote: |
| You can do a continuation like that. |
But what will happen if those "&line"s are going to be replaced by a variable larger or smaller than five characters? |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
| Quote: |
| But what will happen if those "&line"s are going to be replaced by a variable larger or smaller than five characters? |
It shoudn't matter what the length of the variable is.
Gerry |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1248
Location: Richfield, MN, USA
|
|
|
|
| The length of the expanded value of MAR is going to have an effect as well as the length of LINE. |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi Terry,
what I should have said is as long as the total length of the PARM does not exceed 100 characters.
Having a length greater or less than the variable is not a problem, I'm assumed CICS Guy was concerned if the expanded format did not finish in col 71.
This could be an easier way to achieve the result
| Code: |
// SET V1=&MAR.USERID.&LINE.PLEASE&LINE.VERIFY&LINE.MRGWSBRO
// SET V2=&LINE.BESTANDEN&LINE.ABR&LINE.AANWEZIG&LINE.
// SET V3=&V1&V2
// SUBJECT=&V3
|
Gerry |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
|
|
| Quote: |
| This could be an easier way to achieve the result |
The very point I was aiming for....
| Quote: |
| Having a length greater or less than the variable is not a problem, I'm assumed CICS Guy was concerned if the expanded format did not finish in col 71. |
But, if the "X" is in column 71 and the five byte "&line" was actually four bytes long, would the CC71 "X" still be in CC71? |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi CICS Guy,
It's not a problem if the five byte &line is only four bytes long, it will still continue the parameter.
Acutally you can leave col 72 blank.
Gerry |
|
| Back to top |
|
|
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
| As gerry said, code the JCL with PARM symbolics to satisfy the reader/interpreter (end in 71, 'X' in 72, continue in 16, etc.). The length of the symbolics after substitution doesn't matter as long as the total PARM ends up at 100 bytes or less. |
|
| Back to top |
|
|
vikas kumar jain
New User
Joined: 02 Aug 2006
Posts: 9
Location: noida
|
|
|
|
| lots of thanks Dennis..it works...(no need of X in 72 column also) |
|
| Back to top |
|
|
|
|
