Article View: bit.listserv.asm370
Article #287Re: assembly language coding conventions
From: john gilmore
Date: Sat, 03 Sep 2005 19:43
Date: Sat, 03 Sep 2005 19:43
68 lines
3721 bytes
3721 bytes
I provided the SA22-7643-03 page reference in my first post. Here is the text: A message indicates the number of bytes added to the control section and the offset, relative to the start of the control section, where the expansion begins. The effective length of the expansion is given in hexadecimal and can be greater than the specified length if, after the specified expansion, padding bytes must be added for alignment of the next control section or named common area. I also think we can reasonably leave this topic now. Those who wish to assemble patch areas into executables are of course free to do so, as they have been since 1965. I prefer the EXTEND mechanism because it extends the patch unit, a program object, not one of its components, and for the other reasons I have mentioned. John Gilmore Ashland, MA 01721 USA >From: Binyamin Dissen <bdissen@dissensoftware.com> >Reply-To: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> >To: ASSEMBLER-LIST@LISTSERV.UGA.EDU >Subject: Re: assembly language coding conventions >Date: Sat, 3 Sep 2005 22:19:26 +0300 > >On Sat, 3 Sep 2005 18:43:53 +0000 john gilmore <john_w_gilmore@msn.com> >wrote: > >:>Still, even in those circxumstances in which an initial, >:>contingency-planning patch area is judged appropriate I should prefer to >use >:>the binder's EXTEND statement at install time, not least because the >:>documentation it generates is much superior to that provided by an >:>assembled-in patch area. > >What superior documentation? > >-- >Binyamin Dissen <bdissen@dissensoftware.com> >http://www.dissensoftware.com > >Director, Dissen Software, Bar & Grill - Israel > > >Should you use the mailblocks package and expect a response from me, >you should preauthorize the dissensoftware.com domain. > >I very rarely bother responding to challenge/response systems, >especially those from irresponsible companies. _________________________________________________________________ DonΒt just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/
Technical Details
Message-ID:
<BAY104-F386347BF5D703122469AB3C6A20@phx.gbl>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed.news2me.com!sn-xit-04!sn-xit-10!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!msn.com!john_w_gilmoreShow Full Headers
Complete Article Headers
X-Google-Thread: fcdcb,17e1789a2da292be
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed.news2me.com!sn-xit-04!sn-xit-10!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!msn.com!john_w_gilmore
From: john gilmore <john_w_gilmore@msn.com>
Newsgroups: bit.listserv.asm370
Subject: Re: assembly language coding conventions
Date: Sat, 3 Sep 2005 19:43:16 +0000
Organization: SAS Inc.
Lines: 68
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <BAY104-F386347BF5D703122469AB3C6A20@phx.gbl>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Trace: foggy.unx.sas.com 1125776811 17735 10.19.150.41 (3 Sep 2005 19:46:51 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Sat, 3 Sep 2005 19:46:51 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
X-Originating-IP: [65.54.175.209]
X-Originating-Email: [john_w_gilmore@msn.com]
X-Sender: john_w_gilmore@msn.com
X-OriginalArrivalTime: 03 Sep 2005 19:43:17.0139 (UTC)
FILETIME=[BAEEEE30:01C5B0BF]
Approved-By: john gilmore <john_w_gilmore@MSN.COM>
In-Reply-To: <uotjh1l5mdq47qv7fnns4o2htop6ni1ccd@4ax.com>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-Mime-Autoconverted: from 8bit to quoted-printable by mime827
Originator: daemon@mozart.unx.sas.com