On Dec 20, 2011, at 08:29, McKown, John wrote:
> Just for learning, and fun (FSVO "fun"), I'm doing some programming in HLASM
> for z/OS UNIX. In the spirit of things, I'm keeping the source in UNIX
> subdirectories and using the "make" UNIX command, in an interactive UNIX
> shell, to control the assembly (using the "as" UNIX command) and linking
> (using the "ld" UNIX command). I've run into an irritation. I like to keep my
> UNIX file names in __lower__ case. The source code in my assembler invokes
> one of my macros. The source is in lower case. I get a "macro not found"
> error because the assembler UPPER CASES the macro name before looking for the
> macro. I guess I understand why HLASM does this. But is there __any__ way to
> have HLASM r6.0 (PTF UK54260) use lower case? Or am I stuck with making my
> UNIX resident macro names UPPER CASE? I know that I have the -I to search my
> UNIX subdirectory set correctly because if I make the UNIX file name UPPER
> CASE, then it assembles cleanly.
>
Right. If HLASM can do it for EXTRNs, why not for macros.
If Binder supports a Mixed/UPPER switch, why not HLASM?
In the interim, a short awk or sed script (I don't know perl)
could create symlinks with HLASM-friendly names.
We've experimented with bilingual C/HLASM copybooks. Some
in production, in fact. In C:
#define MACRO
#include "FOO"
Then in FOO:
MACRO /* assembler code; ignored by C
&L FOO args
*/ C declaration /*
HLASM declaration
*/ C declaration 2 /*
HLASM declaration 2
...
-- gil
