It helps to look at this from a historical perspective. When VSAM was introduced in the early 1970s, the DCB equivalents to the ACB and RPL we’re hopelessly convoluted, and the theory was to provide an API to mask the complexity.
As it turns out, the cure of MODCB and SHOWCB was worse than the problem, as the ACB and RPL (and EXLST) were just not that complicated. The IBM code I saw for VTAM never used MODCB either. And these control blocks have been static for decades with a few minor extensions. Happy coding! Tom Harper Phoenix Software International Sent from my iPhone > On Feb 24, 2022, at 12:49 PM, Dave Clark <dlcl...@winsupplyinc.com> wrote: > > "IBM Mainframe Assembler List" <ASSEMBLER-LIST@LISTSERV.UGA.EDU> wrote on > 02/24/2022 12:35:27 PM: >> You may use whichever DSECT you want. I just use IFGRPL but that’s >> just my preference. > > > Thanks. I have confirmed that both of the following generate the > same mapping for a VSAM RPL. The second one just also overlays the > mapping for a VTAM RPL. > > > IKQRPL DSECT=YES > > IFGRPL DSECT=YES,AM=VSAM > > > Sincerely, > > Dave Clark > -- > int.ext: 91078 > direct: (937) 531-6378 > home: (937) 751-3300 > > Winsupply Group Services > 3110 Kettering Boulevard > Dayton, Ohio 45439 USA > (937) 294-5331 > > > > > ********************************************************************************************* > This email message and any attachments is for use only by the named > addressee(s) and may contain confidential, privileged and/or proprietary > information. If you have received this message in error, please > immediately notify the sender and delete and destroy the message and all > copies. All unauthorized direct or indirect use or disclosure of this > message is strictly prohibited. No right to confidentiality or privilege > is waived or lost by any error in transmission. > ********************************************************************************************* -------------------------------------------------------------------------------- This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use.
