On Wed, 17 Sep 2014 06:53:36 -0400, Shmuel Metz (Seymour J.) wrote:
>
>>Can anyone supply a rationale for these behaviors?
>
>C2H5OH?
>
The second most plausible rationale is, as I conjectured earlier, a desperate
and misdesigned attempt to suss out the attributes of the source file.
With encouragement from Tony H. (largely, he discouraged my doing it the
hard way), I have several empirical data points. The SYSIN data sets, as
appearing in the JCL:
//SYSUT2 DD * xxx
This is SYSUT2.
short
//SYSUTV DD *
This is SYSUTV.
//SYSUTW DD *
This is SYSUTW.
Same length.
//SYSUTX DD *
This is SYSUTX.
long
//* Empty SYSIN. ..|....+....|....+....|....+....|....+....|....+....|....+....|
//SYSUTZ DD * 2....+....3....+....4
//REXXIN DD *,DLM='..'
show DCB attributes:
%SHOWDCB
DCB: SYSUT2 0000DB18 DCBLRECL: 21 DCBBLKSI: 25 DCBRECFM: 40 V
DCB: SYSUTV 0000D8E0 DCBLRECL: 60 DCBBLKSI: 60 DCBRECFM: 90 FB
DCB: SYSUTW 0000D6A8 DCBLRECL: 50 DCBBLKSI: 50 DCBRECFM: 90 FB
DCB: SYSUTX 0000D470 DCBLRECL: 37 DCBBLKSI: 41 DCBRECFM: 40 V
DCB: SYSUTZ 0000D238 DCBLRECL: 40 DCBBLKSI: 40 DCBRECFM: 90 FB
READY
JES2 makes the choice; the programmer has little control over it.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
