On Fri, 24 Jun 2011 12:24:13 +0530, sourabh khandelwal <[email protected]> wrote:
>Hello, > I was applying RSU on one of our z/OS system but during apply >process I received D37-04 abend for below datasets. > >1) DIT.V1R3M0.SDITMOD1 >2) SYS1.NUCLEUS >3) SYS1.SIOALMOD > . . . >2) I had bring down current z/OS system on which I was applying RSU and I >had one more z/OS system . So I tried renaming SYS1.NUCLEUS for the older >system by specifing the dataset name with volume. But as this system also >contain SYS1.NUCLEUS, which matches with old system . So its has not allowed >me to rename the dataset. > > I can't think of any work entity (job, STC or anything else) allocating SYS1.NUCLEUS in a way resulting in ENQing on its name. You, most likely, have a never-endind job that does nothing except JCL- allocating SYS1.NUCLEUS together and some other critical datasets alike, just to prevent accidental deletion of them. Try GRS displays to find out who is doing this. ---------------------------------------------------------------------- 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
