Or possibly when the precursor to the binder was developed that long ago, 
whoever wrote this section figured with a 44 character DSN being the longest 
available, they padded it with 20 bytes to make sure it was plenty long.  Then 
when Unix-style path names came along later, whoever added the path capability 
decided to not increase the length in order to not take a chance at breaking 
anything?

Rex

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Peter Relson
Sent: Saturday, November 22, 2014 6:44 PM
To: [email protected]
Subject: Re: Binder SYSPRINT wrap?

Gil mentioned the "DATA SET SUMMARY" section.

I presume his use involved the file system. For a data set, the lines in 
that section would not come close to reaching column 84.

For example,
DDNAME    CONCAT   FILE IDENTIFICATION 
 
LPALIB      01     SYS1.LPALIB 
SYSOBJS     02     TESTUSER.OBJS 

I would guess that many who read the append did not realize that the 
original post related to presentation of a "long" path name. I know that I 
did not.

Regardless, for whatever reason, when the binder was developed going on 25 
years ago someone implemented "put 64 columns of path name info per line". 
Maybe they thought that was a reasonable amount, maybe they wanted a power 
of two; I have no idea.

This has apparently not been an issue to anyone.

Peter Relson
z/OS Core Technology Design

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to