Generally you can get away with not closing DCBs and the system will close them. The problem occurs when the DCB is either in GETMAINed storage, or in a secondary load module brought in by the jobstep program with a LOAD (which is pretty much the same thing) - AND the storage gets freed before end of jobstep. MVS goes to close the DCB and - ta-da! - it's not there. SC03 will also happen if a DCB gets overlaid or "clobbered" in some way before the system can close it.
I think that a job's behavior in this regard can be a little unpredictable because things may depend on whether the storage gets reused or not. That's probably why he is seeing different results depending on whether or not DB2 is in the picture. It's not DB2 per se, but the fact that DB2 coincidentally changes the storage allocation picture in some way. He might get different results, for example, with a different region size. Shmuel is 100% correct though - it's like your mom said: if you open the DCB, you close it. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Lizette Koehler Sent: Wednesday, June 22, 2005 3:55 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Help on SC03 abend If my old addled brain is thinking correctly, I believe over 10 years ago IBM decided to no longer be nice to programs and require that all programs close any files they open. And if they did not close them, the system would then issue a SC03 abend. Or am I getting too forgetful??? ---------------------------------------------------------------------- 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
