Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!helios.ee.lbl.gov!ncis.tis.llnl.gov!lll-winken!uwm.edu!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!CERNVM.BITNET!TNT
From: TNT@CERNVM.BITNET (Tony Cass)
Newsgroups: comp.lang.asm370
Subject: NUCON Macro - was Re: CTCAs
Message-ID: <9001190049.AA21839@lilac.berkeley.edu>
Date: 19 Jan 90 00:49:48 GMT
References: <PERSHNG@YKTVMH3>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.bitnet@lilac.berkeley.edu>
Distribution: inet
Organization: The Internet
Lines: 15
X-Unparsable-Date: Thu, 18 Jan 90 11:56:55 SET

>If you look at the NUCON mapping macro, you will notice that it provides
>symbolic names for all of the low-storage locations.  It is considered
>preferable to use these symbolic names, rather than absolute addresses.
>Just remember to provide an appropriate USING pseudo-op in your assembler
>routine:
>

Beware!! I recently received TNLs for the CMS Application Program Development
Reference (SN31-1587) and the CMS App. Prog Development Guide (SN31-1586) for
VM/XA SP 2.1.
The NUCON macro is now documented, but the only fields listed as being
supported as programming interfaces are ADEVTAB and AEXEC. All the rest
are there at the moment - but for how long?

Tony Cass