Thanks, Rob. I think the first thing I'll have tried (if ops will do it!) is perform a WHOHAS on the dataset. This should tell me who/what has the dataset enqueued, right?
Frank ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Jackson, Rob <[email protected]> Sent: Friday, February 15, 2019 5:30 PM To: [email protected] Subject: Re: IEC331I 042-006 occurs during GDG roll in process One more thing, is it possible for this job that runs that many times per day to contend with itself occasionally (i.e. demand-triggered with varying job name or duplicate-jobname execution allowed in JES)? First Tennessee Bank Mainframe Technical Support -----Original Message----- From: Jackson, Rob Sent: Friday, February 15, 2019 7:20 PM To: [email protected] Subject: RE: IEC331I 042-006 occurs during GDG roll in process Hah, our emails waived at each other as they were being delivered. But it would be weird if someone were always browsing the last generation when this happened. At any rate, with our AO product--and most of the others I've used--it would be pretty simple to automate the deletion of that rolled-out GDS. You'd still have to wait until it was unallocated by whatever caused it in the first place, of course. First Tennessee Bank Mainframe Technical Support -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Frank Swarbrick Sent: Friday, February 15, 2019 7:10 PM To: [email protected] Subject: Re: IEC331I 042-006 occurs during GDG roll in process [External Email] The long result code (040B0425) seems to mean "Verify DADSM SCRATCH request; enqueue on SYSDSN failed." What can cause this to occur? Someone perhaps had the dataset open for browsing, perhaps? ________________________________ instructions, send email to [email protected] with the message: INFO IBM-MAIN FIRST TENNESSEE Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
