Peter, BLSR is a critter (a good one!). I do not think that you can override a PROC's DD statements to disable BLSR. You need to change and rip it out, go back to a non-BLSR JCL.
I'm not sure, if you're familiar with BLSR, but this thing uses some trickery. For example, here's some JCL I've been playing with ... I have a test program that tests the effect of BLSR on a VSAM file's I/O performance. The program uses DDname VSAMFILE to access the VSAM dataset. //* USE THE FOLLOWING TO RUN WITHOUT BLSR: //VSAMFILE DD DSN=CUKRSC.VSAM.TEST,DISP=OLD //* USE THE FOLLOWING TO RUN WITH BLSR: //VSAM DD DSN=CUKRSC.VSAM.TEST,DISP=OLD //VSAMFILE DD DSN=CUKRSC.VSAM.TEST, // SUBSYS=(BLSR,'DDNAME=VSAM','MSG=I','DEFERW=YES', // 'HBUFND=1000','HBUFNI=500') So, to take BLSR out of the picture, you'll have to change the proc. But then, why would you want to take BLSR away? If it works properly, it should improve your job's performance more or less dramatically. Look for an IBM manual "MVS Batch Local Shared Resources" for more details. Regards, Ulrich Krueger Mainframe Systems Services National Semiconductor Corp. Santa Clara, CA 95051 Tel:(408)721-8071 Fax:(408)721-6526 Email: [EMAIL PROTECTED] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
