Re: Binder SYSPRINT wrap?
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Saturday, November 22, 2014 6:44 PM To: IBM-MAIN@LISTSERV.UA.EDU 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, DDNAMECONCAT 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 lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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, DDNAMECONCAT 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
In caajsdjifcetyukih8nywc22e9r5epqlvwdy1tm3uaiujsmk...@mail.gmail.com, on 11/21/2014 at 02:37 PM, John McKown john.archie.mck...@gmail.com said: I think gil has more of a UNIX background. When you are used to truly long lines, the z/OS use of 121 or 132 byte print lines can be a real PITA. Yeah, the 1443 is too new to consider 145[1], much less 205. [1] cc included. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
So it WASN'T done just to annoy Gil? Darn! Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Saturday, November 22, 2014 4:44 PM To: IBM-MAIN@LISTSERV.UA.EDU 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, DDNAMECONCAT 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. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
On 2014-11-20, at 13:25, Charles Mills wrote: Just to annoy you. I hadn't known they cared. I suppose I should be flattered. Original message From: Paul Gilmartin Date:11/20/2014 9:57 AM (GMT-08:00) Browsing a Binder SYSPRINT, I notice that lines in *** DATA SET SUMMARY *** are wrapped after 84 columns (including carriage control), then padded with blanks to 121 characters. Why? What's the rationale for this behavior? Other sections of the same SYSPRINT use all 121 characters. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
That would be too easy. Many things seems to annoy the OP. Maybe there's a platform out there with fewer nits to pick. On Thu, Nov 20, 2014 at 3:25 PM, Charles Mills charl...@mcn.org wrote: Just to annoy you. Charles Sent from a mobile; please excuse the brevity Original message From: Paul Gilmartin 000433f07816-dmarc-requ...@listserv.ua.edu Date:11/20/2014 9:57 AM (GMT-08:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Binder SYSPRINT wrap? Browsing a Binder SYSPRINT, I notice that lines in *** DATA SET SUMMARY *** are wrapped after 84 columns (including carriage control), then padded with blanks to 121 characters. Why? What's the rationale for this behavior? Other sections of the same SYSPRINT use all 121 characters. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
On Fri, Nov 21, 2014 at 1:52 PM, Don Imbriale don.imbri...@gmail.com wrote: That would be too easy. Many things seems to annoy the OP. Maybe there's a platform out there with fewer nits to pick. I think gil has more of a UNIX background. When you are used to truly long lines, the z/OS use of 121 or 132 byte print lines can be a real PITA. UNIX people are used to longer lines so that a logical entity is normally on just one line. This type of output is much easier to parse with normal UNIX utilities. I guess it's what you're used to. I, personally, have not actually printed _anything_ on paper for _years_. I keep my output in either sequential data sets or UNIX files. I prefer UNIX files, but I put stuff in data sets to be kind to others who view UNIX as something arcane and impossible to learn. -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
On Fri, 21 Nov 2014 14:37:40 -0600, John McKown wrote: On Fri, Nov 21, 2014 at 1:52 PM, Don Imbriale wrote: That would be too easy. Many things seems to annoy the OP. Maybe there's a platform out there with fewer nits to pick. I think gil has more of a UNIX background. When you are used to truly long lines, the z/OS use of 121 or 132 byte print lines can be a real PITA. I understand that, but given that they've settled on 121, and use all 121 productively elsewhere in the SYSPRINT, wrapping at 84 in one section is plain stupidity. mit der Dummheit kämpfen Götter selbst vergebens -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
For the record let me say I was not dinging the OP for being a nitpicker. No such implication was intended. It just seemed that the question itself was unanswerable. I have a friend who used to be the systems programming manager for a large retailer. When his people would come to him with questions like why does the Binder wrap certain lines at 84 columns? he would say Let's split that question into two parts to make it simpler. Why? That's a question that philosophers have struggled with for years and have never come up with an answer. And does the Binder wrap certain lines at 84 columns? The answer to that question is Yes. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Don Imbriale Sent: Friday, November 21, 2014 11:52 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Binder SYSPRINT wrap? That would be too easy. Many things seems to annoy the OP. Maybe there's a platform out there with fewer nits to pick. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
On Fri, 21 Nov 2014 13:51:14 -0800, Charles Mills wrote: For the record let me say I was not dinging the OP for being a nitpicker. No such implication was intended. It just seemed that the question itself was unanswerable. I have a friend who used to be the systems programming manager for a large retailer. When his people would come to him with questions like why does the Binder wrap certain lines at 84 columns? he would say Let's split that question into two parts to make it simpler. Why? That's a question that philosophers have struggled with for years and have never come up with an answer. And does the Binder wrap certain lines at 84 columns? The answer to that question is Yes. I think he was imitating Prof. Irwin Corey, the World's Foremost Authority. https://www.youtube.com/watch?v=RHlLmYVCzKY Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Binder SYSPRINT wrap?
Browsing a Binder SYSPRINT, I notice that lines in *** DATA SET SUMMARY *** are wrapped after 84 columns (including carriage control), then padded with blanks to 121 characters. Why? What's the rationale for this behavior? Other sections of the same SYSPRINT use all 121 characters. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Binder SYSPRINT wrap?
Just to annoy you. Charles Sent from a mobile; please excuse the brevity Original message From: Paul Gilmartin 000433f07816-dmarc-requ...@listserv.ua.edu Date:11/20/2014 9:57 AM (GMT-08:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Binder SYSPRINT wrap? Browsing a Binder SYSPRINT, I notice that lines in *** DATA SET SUMMARY *** are wrapped after 84 columns (including carriage control), then padded with blanks to 121 characters. Why? What's the rationale for this behavior? Other sections of the same SYSPRINT use all 121 characters. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
