Solution to S0C4 at CLOSE SVC found: Always code STRNO=(# I/O subtasks)+1 in your JCL and you'll avoid the problem. Dynamically acquired strings (default is STRNO=2) get freed at subtask termination, leading to S0C4 at CLOSE.
Thanks to all for help on SUBSYS override. Peter -----Original Message----- From: IBM Mainframe Discussion List Sent: Wednesday, January 18, 2006 10:34 AM To: [email protected] Subject: Re: Does DDNAME=? override SUBSYS=? I agree, BLSR is a useful critter. I am, in fact, pretty familiar with it, having introduced its use into production jobs in my group to help performance. As to why I need to remove it, there may be a storage overlay issue in my massively multitasking assembler application code, OR there may be a CLOSE SVC code issue when NOT using BLSR for this application, and I need to figure out which (symptom is S0C4 in system code at CLOSE of VSAM file in MAIN application task; VSAM file was opened in MAIN task, read/write in subtasks). Peter _ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
