Looks like ORG's alignment is unconditional so it may generate different
offsets from CNOP when the location counter is already correct.
D-Loc Object Code Addr1 Addr2 Stmt Source Statement
00000000 00000000 00000010 1 TEST1 DSECT
00000000 2 BEFORE1 DS XL10
0000000A 3 CNOP 2,8
0000000A 4 RNAME1 DS 0CL6
0000000A 5 ASID1 DS H
0000000C 6 ADDR1 DS F
7 *--------------------
00000000 00000000 00000018 8 TEST2 DSECT
00000000 9 BEFORE2 DS XL10
0000000A 0000000A 00000012 10 ORG *,8,2
00000012 11 RNAME2 DS 0CL6
00000012 12 ASID2 DS H
00000014 13 ADDR2 DS F
14 *--------------------
00000000 00000000 00000010 15 TEST3 DSECT
00000000 16 BEFORE3 DS XL10
0000000A 0000000A 0000000A 17 ORG *,8,-6
0000000A 18 RNAME3 DS 0CL6
0000000A 19 ASID3 DS H
0000000C 20 ADDR3 DS F
21 *--------------------
00000000 00000000 00000010 22 TEST4 DSECT
00000000 23 BEFORE4 DS XL11
0000000B 0000000B 0000000A 24 ORG *,8,-6
0000000A 25 RNAME4 DS 0CL6
0000000A 26 ASID4 DS H
0000000C 27 ADDR4 DS F
28 END
Robert Ngan
CSC Financial Services Group
From: John Ehrman <ehr...@us.ibm.com>
To: ASSEMBLER-LIST@listserv.uga.edu
Date: 2012/06/14 13:01
Subject: Re: DS 0H
Sent by: IBM Mainframe Assembler List <ASSEMBLER-LIST@listserv.uga.edu>
Tom Marchant included this code fragment:
CNOP 2,8
RNAME DS 0CL6
ASID DS H
ADDR DS F
Since this is defining data fields, ORG may be more appropriate than CNOP
(which is intended for instruction streams):
ORG *,8,2
RNAME DS 0CL6
ASID DS H
ADDR DS F
John Ehrman
