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 (not to be confused with the *first* version... sheesh), which expands the original by 24 bytes to add one new bit? I guess DCBEFLG4 was miffed at being skipped and negotiated a big payoff. -- sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TGIF
That's an especially good one, but the inconsistency is rampant: MACRO IHADSAB, DSECT DSAB MACRO IEFJFCBN, DSECT JFCB MACRO IHAPSA, DSECT PSA but MACRO and DSECT both IEZJSCB Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 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 (not to be confused with the *first* version... sheesh), which expands the original by 24 bytes to add one new bit? I guess DCBEFLG4 was miffed at being skipped and negotiated a big payoff. -- sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TGIF
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 DCBD. Then we have "macro IHADCB produces a DSECT named IHADCB". Then you can choose to think about why some produce a DSECT without the component prefix and some with, as Charles observed. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TGIF
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 17, 2019 at 9:06 AM Peter Relson wrote: > > 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 DCBD. Then we > have "macro IHADCB produces a DSECT named IHADCB". > > Then you can choose to think about why some produce a DSECT without the > component prefix and some with, as Charles observed. > > Peter Relson > z/OS Core Technology Design > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TGIF
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 DSORG=&DSORG,DEVD=&DEVD MEND , No, I wouldn't suggest there's any reason for you to create one, since you've obviously done just fine without it. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
