Charles, Yes, that works as well for both Subsystems listed. QSAM with the member name specified just like you have it
Also in the SYSLIB you can concatenate "real" IBM PDSs with the "other" library types, but must specify SUBSYS=???? On all those DDs as well in the SYSLIB concat. Good Luck! Jeff Bruner L2 Support for CA Librarian & CA Panvalet -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Charles Mills Sent: Wednesday, January 13, 2010 11:35 AM To: IBM-MAIN@bama.ua.edu Subject: SUBSYS=LAM and PANV supported for QSAM access? I'm working on a product that will have to support SUBSYS=LAM and SUBSYS=PANV datasets. I don't have access to the CA products or documentation, and it's awfully tough to get customers to help with problems that are not directly on their radar. I have only seen SUBSYS=LAM and SUBSYS=PANV coded on DD statements that defined an entire "PDS-like" dataset that the program would access with BPAM macros: BLDL, FIND, READ, etc.: //SYSLIB DD DSN=OUR.PANVALET.LIBRARY,DISP=SHR,SUBSYS=PANV Does anyone know *for sure* whether the LAM and PANV access methods support coding SUBSYS=LAM on a DD statement that references a single member for QSAM access? In other words something like //SYSIN DD DSN=OUR.PANVALET.LIBRARY(MAINPROG),DISP=SHR,SUBSYS=PANV Thanks in advance. Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
