On 1/11/2012 7:42 AM, McKown, John wrote:
HLASM symbols can include the underscore character. I looked at the IEABRCX macro and saw where it
used it as a prefix in an OPSYN. So, in my messing around, I created a macro in my source code
which I called __LA (posted in a previous message). Of course, __LA is not a valid member name,
according to normal z/OS syntax. I couldn't create an __LA source member in my maclib using ISPF.
But, in this case, I'm not doing batch compiles. I'm actually compiling from the z/OS UNIX shell
prompt, via a make file, using the "as" command. One option on the "as" command
is -I to specify an additional macro library (multiple -I options if more than one is needed).
Well, the maclib specified in the -I can be either a PDS or a UNIX subdirectory. __LA is a
perfectly valid UNIX file name. And, nicely, if I have an macro named __LA in the subdirectory
referenced by the -I switch, HLASM will gladly read and use it. Nifty.
What is the big deal? Well, I remember how everybody complains when IBM "steps on" their
macro name. But, if you name your internal macro with a _ in it, which is valid in an HLASM symbol,
but which cannot be easily used in a PDS member name, the probability of IBM "stepping
on" it is greatly reduced. And you should be able to use the subdirectory name in your batch
compiles simply by including it in the SYSLIB for the assembler. From looking, _ is the only such
character.
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
I think that's really creative. Way to go!
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-355-2752
http://www.trainersfriend.com
* To get a good Return on your Investment, first make an investment!
+ Training your people is an excellent investment
* Try our tool for calculating your Return On Investment
for training dollars at
http://www.trainersfriend.com/ROI/roi.html
