On Dec 20, 2011, at 08:56, Thomas David Rivers wrote:
>
> <shameful plug>
> Well - I don't know of a way in HLASM - but the Dignus assembler
> in that environment has a pretty powerful search mechanism that
> lets you do precisely that...
>
> You can cause it to use lower or upper-case letters, append
> a suffix (e.g. ".mac") or just about anything you'd like.
>
> This works under z/OS UNIX and all the other UNIXes/Linuxes we support.
>
> You can also do cool things like put your maclib members in a ZIP file
> and have it look there.
> </shameful plug>
>
I think Tachyon does about the same. And Tachyon may be trailing
Dignus in support of z196 opcodes.
Don't know about z390. But the source is available. Haven't
even tried z390 with a concatenation/searchpath of directories.
>From the earlier cited:
http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.asma500%2Fasmi102072.htm
CASE
Instructs the assembler to maintain uppercase alphabetic character set
compatibility with earlier assemblers. It restricts language elements
to uppercase alphabetic characters A through Z if they were so restricted
in earlier assemblers.
It becomes a question of whether macro names are "language elements".
I'd say, "No." HLASM disagrees with me. The criterion is that
opcodes are enumerated in a Reference Manual; user-defined macro
names are not.
HLASM provides exits for I/O processing. We've used them, exactly
for source/macros in UNIX directories, prior to the availability
of NFS. I had no cause to investigate whether the exit can
perform the OPEN and defer all further processing to HLASM.
-- gil
