Has Colesoft been using VSTRCZFS?
No, I noticed it while developing SIMD support. In my disassembly
displays, the 8th character was being truncated.
It's no big deal really, I just need to change an EQU and reassemble.
But it does make me wonder if they might eventually go to 9 or longer...
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: [email protected]
Home page: www.colesoft.com
User's Group: www.xdc.com (on LinkedIn)
Facebook: www.facebook.com/colesoftware
Videos: www.youtube.com/user/colesoftware
At 1/21/2015 11:10 AM, Paul Gilmartin wrote:
On 2015-01-21, at 08:37, David Cole wrote:
> Correct me if I'm wrong (John Ehrman),
> but I thought that IBM once upon a time,
> way back when they started to create mnemonics longer than 5 characters...
>
> I thought they said
> their new limit was going to be seven characters.
> Well... "VSTRCZFS".
>
> [sigh]
>
How many collisions are there between z13 mnemonics and z/OS library
macro names and HLASM instructions.
I think it was said here that if hardware design tried to name
instructions such as POP, PUSH, WAIT, POST, ... HLASM would prevail
with possible intercession of Marketing. But are new mnemonics
vetted against all member names in all maclibs of all IBM
products? (Do significant ISVs count?)
Has Colesoft been using VSTRCZFS?
If seven characters is enough for TSO user IDs, it ought to be
enough for instruction mnemonics.
What about 9? Would that require a redesign of HLASM? UNIX file
names can easily be 9 and more, but BPAM wouldn't support them.
-- gil
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: <mailto:[email protected]>[email protected]
Home page: www.colesoft.com
User's Group: www.xdc.com (on LinkedIn)
Facebook: www.facebook.com/colesoftware
Videos: www.youtube.com/user/colesoftware
