Lizette, I've see the same type of problem with a VSAM file in our scheduler as well. It can be open to people looking at job history and thus, we have problems reloading it.
We received an IEC161I message to SYSLOG - so, I wrote some automation to take the dataset name from the error message and issue a D GRS command against the dataset (d grs,res=(sysdsn,dsname.here)). Some of our applications have had similar issues with VSAM files - and this automation helped them determine who caused their abends. Robert DiBianca -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Monday, February 15, 2016 11:52 AM To: [email protected] Subject: Issues with VSAM Enqueuers and Batch job with IDCAMS I have an issue where an STC holds a VSAM Dataset. The STC is a scheduling software that writes all of the info on jobs running/completed/failed and so forth, to this file. Once per day we close and free the VSAM file from the STC, run an archive process and then re-open then file to the STC. This works nearly all of the time. However, on occasion (a couple times a year) the job will fail in the IDCAMS Step with DATASET IN USE BY ANOTHER TASK message. The enq is so fast, I do not have any indication of what was holding it. The IDCAMS Step reloads the history file with the last 3 days' worth of information about jobs. It is a very simple REPO IFILE(x) OFILE(y) I opened an SR to IBM DFSMS and asked if they could add some checks in IDCAMS for the nonzero return code from the enq and let me know what job is using it. They indicated that extra code path to do that would not help. They felt that the enq is released so soon the extra test for the enqueue would not provide the name of the task. I have looked at RMF reports - I could see nothing. I have looked at DAF reports for the 5 min time frame - I could see nothing. When the step fails with RC12, I do the D GRS,C and nothing shows up. I am tempted to start the ISG Monitor for Enqueues for the 15 minute window when this job runs. If we rerun the job it is successful. Anyone have any other ideas to try and trap this rascally rabbit? Lizette Koehler statistics: A precise and logical method for stating a half-truth inaccurately ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information in this transmission may contain proprietary and non-public information of BB&T or its affiliates and may be subject to protection under the law. The message is intended for the sole use of the individual or entity to which it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited. If you received this message in error, please delete the material from your system without reading the content and notify the sender immediately of the inadvertent transmission. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
