Keith E. Moe wrote:

There are a fair number of IBM Macros (and ISV Macros as well) that generate message ASMA309W when you use the FLAG(PAGE0) option (mostly by specifying the register in the "index" position instead of the "base" position). RACF has taken an APAR to fix their Macros.

They are addressing only the FLAG(PAGE0) problems? What about the problems they have with FLAG(SUBSTR)??! Every RACROUTE macro invocation I've got currently looks like:

|     PUSH  ACONTROL
|     ACONTROL FLAG(NOPAGE0,NOSUBSTR)
|     RACROUTE REQUEST=...
|     POP   ACONTROL

It seems silly to update the macros to fix one issue without fixing the other. What is the APAR number? Is it FIN for release 8?

Do you think it's worth APARing any Macros that have similar problems?

Precedent is important. One component's cooperation often helps solicit another's.

Having said that, I consider the FLAG(PAGE0) support in HLASM to be flawed. If it was fixed, these other IBM macros would most-likely not need changing.

Currently, FLAG(PAGE0) flags all explicit references in which the base register is zero -- including those cases in which the index register for an RX-type instruction is non-zero e.g., 'B 4(R14)'. Such coding is fairly common practice. (Many years ago instructions coded this way actually ran slower, but that hasn't been true for a long, long time.) Furthermore, many instructions in AR-mode programs *must* be deliberately coded in this manner. Whether optional or required, such instructions should *not* be flagged as PSA references!

I have suggested improving HLASM to provide two different flavors of FLAG(PAGE0). One would perform the existing zero-base checking while the other would perform zero-base _and_ zero-index checking. This new option would flag explicit references to PSA without also flagging RX-type instructions that specify a non-zero index. Programmers using this option would get the benefit of FLAG(PAGE0) without the ugly side effects. The APARs you seek would *not* be needed!

Perhaps advocating a functional improvement to HLASM would be a more effective use of time than attempting to get all of IBM's macros changed. Even if you succeed with getting the macros changed, the flawed HLASM functionality will persist.

--
.-----------------------------------------------------------------.
| Edward E. Jaffe                |                                |
| Mgr, Research & Development    | [EMAIL PROTECTED]    |
| Phoenix Software International | Tel: (310) 338-0400 x318       |
| 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801            |
| Los Angeles, CA 90045          | http://www.phoenixsoftware.com |
'-----------------------------------------------------------------'

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to