On Dec 20, 2011, at 09:24, McKown, John wrote: >> >> The binder actually supports UNIX files. HLASM uses BPAM. >> This mess is a >> result of z/OS's BPAM support of UNIX files. > > So, hopefully, some future version of HLASM will directly support UNIX files. > The BPAM support for UNIX seems to be a bit "lacking". I say this because > BPAM does support using all possible hex values as a member name, excluding > 8x'FF'. SMP/E uses really weird member names successfully. And you can even > browse or edit them from ISPF. Hum, since the name in the message is UPPER > CASED, perhaps this particular "problem" is due to HLASM after all. > I'm astonished about 8x'FF'. Won't BLDL see that as end-of-directory and report Member not Found?
Does SMP/E still do that? I thought it was historical behavior and SMP/E now uses VSAM. Can the programmer use weird names in SMP/E MCS/Commands, or are they only used when generated by SMP/E? I know that the CSECT option on the ++MOD MCS allows anything except ' ', ',', and ')'. (IIRC) Itself restrictive because I believe Binder allows the latter two. -- gil
