On Tue, 25 Jun 2024 23:32:55 -0500, Paul Gilmartin wrote:

>On Wed, 26 Jun 2024 03:15:25 +0000, kekronbekron wrote:
>
>>Are you able to share this, Paul?
>> 
>I no longer have the code.
> 
I'll suggest that as a PoC you try  allocating your SYSIN  to a data set,
RECFM=VB to see whether it meets your need.

It's absurd that the various SUBMIT commands, TSO, ISPF, Rexx,
and OMVS enforce FB,80, a convention designed to accommodate
devices that haven't been marketed in this century.

>I used ISPF Edit facilities to get LRECL, RECFM of the Edited file.
>
>BPXWDYN or ALLOCATE SYSOUT INTRDR with similar attributes.
>
>Extracted lines and wrote one-by-one with EXECIO.
>(Why doesn't silly ISPF support stem variables!?)
>
>In an earlier approach I used FTP; FILETYPE=JES, JESRECFM, JESLRECL.
>
>Both successful.
>
>
>>On Tuesday, June 25th, 2024 at 23:32, Paul Gilmartin wrote:
>>
>>> On Tue, 25 Jun 2024 13:33:59 -0400, Phil Smith III wrote:
>>> 
>>> > SWAG but have you tried a trailing semicolon? Or quotes around the value? 
>>> > I found an example on the web for another product:
>>> > ENVAR C='X Y'
>>> > ...which sorta suggests that the quotes might work. Might try both 
>>> > flavors of quote, too.
>>> 
>>> Or, RECFM=VB.
>>> 
>>> I wrote an Edit macro which allocates INTRDR with the attributes of the
>>> file being edited in order to avoid the 80-characte limit. Why didn't IBM
>>> think of that? I consider quiet truncation to be data corruption.

-- 
gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to