On Wed, 28 Aug 2013 08:28:31 +0000, Chokalingam Thangavelu wrote: > >Is there a way to find out which jobs & userids was Holding/Locking the >dataset? > >One of our FTP job failed in July and need to find out the root cause of the >failure. We have not seen any network failure, so need to find out anyone was >holding the dataset during that time. > Most suggestions here so far apply only at the time of the failure, not "in July". You can hope to avoid or diagnose the problem next time.
Were you trying to GET or PUT the data set? Did the contention failure occur at a z/OS client or a z/OS server? Was this in a batch job? Is it practical to statically allocate the data set in JCL? This may wait until it's available, and GRS console messages may explain the problem. Would you have more flexibility if you used the API to FTP? Have you considered using a UNIX file instead of a Classic data set? Serialization rules for those are different (you can control your own locking), and might be more suited to your purpose. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
