Article View: bit.listserv.asm370
Article #294Re: assembly language coding conventions
From: Bruce Black
Date: Sun, 04 Sep 2005 15:06
Date: Sun, 04 Sep 2005 15:06
36 lines
3167 bytes
3167 bytes
Well said, Mike. You saved me the time of typing much the same thing. Another point: a pre-assembled patch area is usually covered by an existing base register, while an EXTENDed area may not be. > Here's why: if you sell z/OS software commercially, and you don't ship > source code for your product to the licensing customer, AND they choose > to install your product without SMP/E, then without a preassembled > patch area they must apply a patch to your product in two steps: step > one invokes the BINDER to do EXTEND, and step two applies the zap with > the AMASPZAP utility. With the relatively low level of z/OS > expertise/experience available to apply product patches in many z/OS > shops today, "GOODNESS", from an ISV standpoint, lies in keeping > instructions to customers simple. Fewer steps to follow to apply patches > is "better" than having more steps to follow. It is often desireable to > help customers by simplifying maintenance and the patch application > process as much as possible. AMASPZAP is still a very easy to use and > rapid method for applying patches to correct minor bugs in commercial > software. Bug-free code would be the ideal, but... > > With SMP/E, maintenance is much easier to automate, but many shops today > still don't use SMP/E for ISV products. > > Mike Shaw > MVS/QuickRef Support Group > Chicago-Soft, Ltd. -- Bruce A. Black Senior Software Developer for FDR Innovation Data Processing 973-890-7300 personal: bblack@fdrinnovation.com sales info: sales@fdrinnovation.com tech support: support@fdrinnovation.com web: www.innovationdp.fdr.com
Technical Details
Message-ID:
<431B0D65.4030607@fdrinnovation.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!sn-xit-04!sn-xit-12!sn-xit-09!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!fdrinnovation.com!bblackReferences:
<BAY104-F39E67737EA82962FAF2588C6A20@phx.gbl> <4319EA8A.8050100@quickref.com>Show Full Headers
Complete Article Headers
X-Google-Thread: fcdcb,17e1789a2da292be
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!sn-xit-04!sn-xit-12!sn-xit-09!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!fdrinnovation.com!bblack
From: Bruce Black <bblack@fdrinnovation.com>
Newsgroups: bit.listserv.asm370
Subject: Re: assembly language coding conventions
Date: Sun, 4 Sep 2005 11:06:13 -0400
Organization: SAS Inc.
Lines: 36
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <431B0D65.4030607@fdrinnovation.com>
References: <BAY104-F39E67737EA82962FAF2588C6A20@phx.gbl>
<4319EA8A.8050100@quickref.com>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1125846712 23744 10.19.150.41 (4 Sep 2005 15:11:52 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Sun, 4 Sep 2005 15:11:52 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
Approved-By: Bruce Black <bblack@FDRINNOVATION.COM>
In-Reply-To: <4319EA8A.8050100@quickref.com>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 04 Sep 2005 15:11:50.0224 (UTC)
FILETIME=[F996AD00:01C5B162]
Originator: daemon@mozart.unx.sas.com