Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!USCMVSA.BITNET!LDW
From: LDW@USCMVSA.BITNET (Leonard D Woren)
Newsgroups: comp.lang.asm370
Subject: Re: Offset 608, part two..
Message-ID: <8912090132.AA04438@brazos.rice.edu>
Date: 8 Dec 89 21:47:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.BITNET@ricevm1.rice.edu>
Distribution: inet
Organization: The Internet
Lines: 13

> Argh..  I looked at the data areas book at *decimal* 608 and found
> the SYSNAME.  *hexadecimal* offset 608 is a V-con pointing at DEVTAB.
>
> Moral of the story ...

No, the moral of the story is as you stated in your original posting
-- *never* use hard-coded offsets. If there's a supplied macro for the
area, use it.  Otherwise, make one.  Another example of why:  Ever try
to modify the output format when all references to the output line are
coded as things like   MVC  LINE+34(5),DATA  ?  It's much much simpler
when there's a layout with field names for the output line.

/Leonard