Martin,
Man, you are crazy.
That said, from the manual:
"If an option was specified on the DELETE operand of the ASMAOPT macro
during installation, you cannot change the option when you invoke the
assembler."
Looks like VSE supplies a default that forces an override for COMPAT.
You might want to generate your own ASMAOPT and see what happens.
FYI, VSE supplies their own modified assembler default option macro.
Look at SKASMOPT in library 59. I don't know if it affects COMPAT.
Tony Thigpen
-----Original Message -----
From: Martin Truebner
Sent: 08/02/2013 06:25 AM
I try to get a handle on how the HLASM handles mixed case coding after
eons of uppercase only (or NOCOMPAT).
Apparently my HLASM (PTF UK80713 HLASM R6.0)
does ignore me- here is the first page:
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='LINECOUNT(00),CPAT(NOCASE)'
1S54I PHASE ASMA90 IS TO BE FETCHED FROM PRD1.BASE
High Level Assembler Option
Overriding ASMAOPT Parameters - EX(INX(FLOWASM),LBX(FLOWASM),PRX(F
)
Overriding Parameters- LINECOUNT(00),CPAT(NOCASE)
No Process Statements
Options for this Assembly
NOADATA
4 ALIGN
BATCH
CODEPAGE(047C)
3 NOCOMPAT
NODBCS
Question: Is it me or VSE or HLASM
Underlying question - what do I have to specify to make it handle
label "HANS" as different from "Hans" or am I totally off target and it
will never do that.
--
Martin
Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE
more at http://www.picapcpu.de
