I've never seen nor heard of an IHADCB
macro, as of z/OS 2.4. Did you mean one should just create it?
Well, that's embarrassing. Bad assumption on my part. There is such a
macro, but it's apparently not shipped externally.
The assembler part consists of
MACRO
IHADCB &DSORG=,&DEVD=
DCBD
I posted that purely for amusement. I've never seen nor heard of an IHADCB
macro, as of z/OS 2.4. Did you mean one should just create it?
I have no real issue with any of the mapping macros; their various styles
and conventions are understandable given the decades of history.
sas
On Sat, Aug
Anyone ever notice that macro DCBD produces a DSECT named IHADCB, and that
macro IHADCBE produces a DSECT named DCBE? Go figure.
Did you "figure" that you might be doing something wrong that led you to
think that that is strange?
You should probably be using IHADCB which internally invokes DC
f
Of Steve Smith
Sent: Friday, August 16, 2019 4:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TGIF
Anyone ever notice that macro DCBD produces a DSECT named IHADCB, and that
macro IHADCBE produces a DSECT named DCBE? Go figure. Reminds me of
parkway vs. driveway.
How about the DCBE version 1 (n
Anyone ever notice that macro DCBD produces a DSECT named IHADCB, and that
macro IHADCBE produces a DSECT named DCBE? Go figure. Reminds me of
parkway vs. driveway.
How about the DCBE version 1 (not to be confused with the *first*
version... sheesh), which expands the original by 24 bytes to add
