[Default] On 23 Feb 2017 06:55:00 -0800, in bit.listserv.ibm-main
[email protected] (Charles Mills) wrote:
>It will work more or less as you expect, with no C's necessary. The
>following is cut-and-pasted *exactly* from a working job, and the parm works
>as expected.
>
>/CZAAPILD EXEC PGM=CZAAPILD,
>// PARM=('INST(CAM.Test.Agent)',
>//* 'COMM(";"),MAJ(CorreLog),MIN(5),TRACE(),LEN(PREFIX)', Test
>// 'COMM(";"),MAJ(CorreLog),MIN(6),TRACE(),LEN(CZ1LEN)', VM RACF
>//* 'COMM(";"),MAJ(IMS),MIN(1),TRACE()', IMS 01&03
>// 'PURGE(N)')
That says to me that you can have comments in the records in PARMDD by
using similar syntax.
Clark Morris
>
>Charles
>
>-----Original Message-----
>From: IBM Mainframe Discussion List [mailto:[email protected]] On
>Behalf Of Clark Morris
>Sent: Thursday, February 23, 2017 6:34 AM
>To: [email protected]
>Subject: Re: Question about PARMDD
>
>[Default] On 22 Feb 2017 14:28:53 -0800, in bit.listserv.ibm-main
>[email protected] (Paul Gilmartin) wrote:
>
>
>Could someone try the following to see if it works? Assume the C for
>continuation is in column 72.
>
>//STER1 EXEC PGM=IEFBR14,PARM=(PARAM1, some comment C
>// PARAM2, another comment C
>// PARAM3) last comment
>
>After reading the entries at the Knowledge Center it has a 50/50 chance of
>working based on how I read them. The next step would be to check a program
>(say a compiler) to see if it actually feeds the right information to it.
>
>As a retiree, I don't have access to a z system.
>
>Clark Morris
>>On Wed, 22 Feb 2017 22:10:43 +0000, David W Noon wrote:
>>>
>>>> This thread began with a discussion of the PARM string. I'd like to
>>>> think of JCL as source code, not as data.
>>>
>>>You can consider JCL as whatever you wish. The point I was making was
>>>that the PARM string is data, not source code.
>>>
>>The storage object pointed to by R1 is data. The argument of the CALL
>>macro as the programmer writes it is source code. It's subject to
>>symbol substitution, joining of continuation lines, etc.
>>
>>>> And I definitely think of JCL as sorely deficient in string
>>>> manipulation operations. It was developed a half-century ago,
>>>> subject to severe resource constraints.
>>
>>But I think we're largely in agreement:
>>
>>>Ideally, JCL should have civilized syntax for string manipulation and
>>>for flow control. This would include SELECT/WHEN/OTHERWISE, DO-loops.
>>>WHILE-loops as well as IF/ELSEIF/ELSE. The string manipulation would
>>>include conditional substitution (ternary operator?) as well as
>>>concatenation, extraction and removal of substrings, scanning
>>>strings(*) for patterns and a whole lot more. We're basically talking
>>>Python here, and a bit more besides.
>>>
>>>(*) I think regular expressions would send most mainframe programmers
>>>scatty, but it would be nice to have.
>>
>>-- gil
>>
>>----------------------------------------------------------------------
>>For IBM-MAIN subscribe / signoff / archive access instructions, send
>>email to [email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions, send email
>to [email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
