× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Make sure when you do the WRKOBJLCK that you press F6=Work with member
locks. You don't see the locks at the file object level - you need to
look at the member level. 

> -------- Original Message --------
> Subject: RE: Determining Lock on Specific PF Record
> From: "Brian Piotrowski" <bpiotrowski@xxxxxxxxxxxxxxx>
> Date: Wed, January 11, 2006 9:00 am
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> 
> Thanks, Jerry.
> 
> I did check the physical locks on the file, but there's nothing showing
> up - according to the system, no users have the record locked.  But this
> still persists to be a problem - we can't even print the record without
> the "cannot allocate" error message showing up.
> 
> It would be really nice if I could run a command that would show me a
> specific lock on a record in our table.
> 
> I went into Navigator and looked at the Database Transactions, but it
> didn't provide any useful information.
> 
> Thanks,
> 
> Brian.
> 
> -----Original Message-----
> From: Jerry Adams [mailto:jerry@xxxxxxxxxxxxxxx] 
> Sent: Wednesday, January 11, 2006 8:52 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: Determining Lock on Specific PF Record
> 
> WRKOBJLCK or WRKACTJOB option 5, option 12 should do it.  Anyway, that's
> 
> what I use.
> 
> 
> 
>       * Jerry C. Adams
> *iSeries Programmer/Analyst
> B&W Wholesale Distributors, Inc.* *
> voice
>       615.893.8633x152
> fax
>       615.995.1201
> email
>       jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>
> 
> 
> 
> Brian Piotrowski wrote:
> 
> >Hi All,
> >
> > 
> >
> >Is there an easy way to determine who has a lock on a specific record
> >(or set of records) in a Physical File?  We have a problem in one of
> our
> >records where when we try to update it the system tells me that it is
> >unable to allocate a record in the PF.  However, there are other users
> >who are currently updating other records in the same PF without issues.
> >
> > 
> >
> >Thanks,
> >
> >
> >Brian.
> >
> > 
> >
> >-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> >Brian Piotrowski
> >
> >Specialist - I.T.
> >
> >Simcoe Parts Service, Inc.
> >
> >PH: 705-435-7814
> >
> >FX: 705-435-6746
> >
> >-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> > 
> >
> >  
> >
> 
> -- 
> 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.
> 
> 
> 
> -- 
> 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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.