|
Vern I ve read this long back in IBM books . But when the lock is *SHRRD why iam getting the following errors: (i)file YPOSF1 in is in use,cant be shared --- Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > Murali > > This is one topic that you will really need to read > up on. It is not > apparent that you have from your question. So take a > look, first, at this site > > http://www-1.ibm.com/support/docview.wss?uid=nas1b21a47c8dae2f8ed86256c4700571cf7&rs=110 > > There is a chart of what lock can be obtained in > different circumstances. > > These are held by DataMirror, the high availability > product. You might need > to talk to them or look at their documentation, to > see how to handle these > conflicts, since it is with their product. > > HTH > Vern > > At 07:52 PM 11/26/2003 -0800, you wrote: > >Hi > > > > > >Iam getting the following error very frequently > >CALL PGM(YCTC1) > > > > File YPOSF1 in QS36F in use, cannot be shared. > > > > Function check. QRY1765 unmonitored by YCTC1 > at > >statement instruction X'0016'. > > > > QRY1765 received by YCTC1 at 1100. (C D I R) > > > > > >When i went onto check object locks on this file > >YPOSF1 i found the following... > >Job User Lock Status > >Scope Thread > >RBT_GDBPOS D_MIRROR *SHRRD HELD > >*JOB > > > > > >when i went to check member locks i found the > >following..... > > > > Lock > > > > Job User Type Lock > Status > >Share > > RBT_GDBPOS D_MIRROR MBR *SHRRD HELD > > > > DATA *SHRRD HELD > > > > > >Iam nt finding any locks like *SHRUPD(shared > update) > >but still wondering why this error coming so > >frequently.Iam nt seeing ant locks like SHRUPD.Iam > >seeing only *SHRRD. > >In the above scenario i check locks and take Retry > >from the response codes. > >Can someone suggest me why Iam getting this error > even > >though there are no locks like *SHRUPD ?? > >and how do I avoid this error coming again? > >This is really making us to wait for some time to > >check locks n come back then take Retry.I would > like > >to avoid this error !!! > > > >Thank you so much for your help in advance > > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/midrange-l. > __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.