50-year-old memory so take this with a grain of salt: The first 16 bytes of the DTF is a CCB. One of the 16-bit fields in the CCB is the residual count. So if the DTF is expecting 128 bytes and reading 80, the field will contain 48 = x'0030'.
But I would think that scanning for binary zeroes or translating them to blanks would be a perfectly acceptable approach. Charles -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of David Clark Sent: Monday, December 15, 2025 7:16 AM To: [email protected] Subject: Re: Reading Past /* on SYSRDR/SYSIPT OK, I now have DTFCD working just fine--no need to resort to custom CCB/CCW/EXCP coding. I'm also accepting a user-specified alternate delimiter for EOD from the EXEC PARM. One problem remains... I've coded the DTF with BLKSIZE=128 to accommodate greater than 80-column input. This is working, too. However, when reading only 80-column input, I'm getting nulls for the remaining length. How do I tell what length data has been read? Or do I just translate the nulls to spaces and move on? I see nothing in the description of the DTFCD or GET macros about a record length being returned. Sincerely, Dave Clark -- int.ext: 91078 direct: (937) 531-6378 home: (937) 751-3300 Winsupply Group Services 3110 Kettering Boulevard Dayton, Ohio 45439 USA (937) 294-5331
