On Fri, 28 Oct 2016 20:18:46 +0000, Robert Prins wrote:
>On 2016-10-27 15:46, Itschak Mugzach wrote:
>>
>> As the information is in machine readable ([binary] data) it can't be rapped
>> with
>> an apostrophe because the data may include apostrophe. ...
>>
Yes, what he said.
>
>Have been doing this for two+ decades:
>
But not with arbitrary data.
>...
>filtz:
> signal tab_data
>
>/*Date | TZ | Trip | Ride | Ride | From | To |
>| 1983-08-01 | +1.00 | 4 | 28 | 29 | GR | YU |
>- - - - - - - - - - - - - - - - 95 Line(s) not Displayed
>| 2016-09-26 | +1.00 | 178 | 5 | | LT | PL |
>*/
>
>tab_data:
...
>return
>
>Key is that SIGNAL will set SIGL to the line-number of the SIGNAL statement.
>
CALL does this as well as SIGNAL and I avoid SIGNAL because it may cause
serious collateral damage.
And this still suffers the hazard of a data pattern's premature termination
of the comment.
An alternative is to place the data at the very end of the EXEC where
it will never be interpreted. But to be safe you must surround every
CALLed library function name with apostrophes. Otherwise the
interpreter looks ahead for a user-defined function and may fail on
an apparent syntax error in the data.
In CMS, but not in z'OS, quoted function names are case-sensitive.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
