RE: Member locked

["Reeve Fritchman" <reeve@xxxxxxxxxx>]

Justin, you're not alone.  

The communications manager (IMHO the least robust piece of code ever
written) has likely taken a hit and it's lost contact with the server job
(running in QUSRSWRK).  

When you tell CODE you're finished with a member, you're implicitly
releasing the member.  Since CODE has "forgotten" (or can't recover) the
server job holding the lock, you're S.O.L. and your only option is to zap
the server job.

I don't know if the server job does anything more than lock the member so
other users can't get at it.  Unfortunately, usually I'm the one that wants
to get at it.

**Supposedly** the communications manager is scheduled to be replaced in a
future release.  My experience is that it's pretty reliable on a LAN but
very unstable on a WAN (dial up or Internet).

-reeve

> -----Original Message-----
> From: code400-l-bounces@midrange.com
[mailto:code400-l-bounces@midrange.com] On Behalf Of
> Justin Houchin
> Sent: Thursday, January 23, 2003 11:34 AM
> To: code400-l@midrange.com
> Subject: Member locked
> 
> Could someone please tell me how to unlock a locked source member?
> 
> 
> 
> Thanks,
> 
> 
> 
> Justin Houchin
> 
> Programmer and Web Developer
> 
> www.reliatek.com
> 
> justin@reliatek.com
> 
> 
> 
> _______________________________________________
> This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> To post a message email: CODE400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/code400-l
> or email: CODE400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/code400-l.
> 
> NOTE: WDSc for iSeries disucssion has it's own mailing list.
> Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l