I cheat horribly. I put my personal HLASM macros in a UNIX directory. HLASM accepts the _ character as a valid alphanumeric. ISPF doesn't for member names in a PDS, but will for a UNIX file name. So I name my personal macros such that they are all 8 or fewer characters; upper case alphabetic, numeric, and have a _ somewhere in them. Given my luck, the hardware people will see this message and go "hey! great idea! Let's co-opt it!"
On Mon, Mar 18, 2013 at 10:18 AM, Andreas F. Geissbuehler < [email protected]> wrote: > Paul Gilmartinäs response to Binyamin Dissen: >> >>> Wasn't there an IBM warning that user macros should be greater than five >>> characters since all opcodes were to be five characters or less, and thus >>> this >>> problem would be avoided? >>> >>> Right. >> > > Thusfar I often inclued a $ # @ in my 'cute' (=short) macro names. > I wrote 'often'... From now on it will be 'always' and consistently ! > All other potential 'collisions' are masked by SYSLIB concatenation. > > My 2 bits: > - IBM opcodes will remain [A-Z] > - IBM might at some point introduce/add characters at present illegal for > opcodes and macro names > - one such extension *should be* for 'qualifiers' like J-NE BR-O > > Andreas F. Geissbuehler > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown
