Based my experiences with CODE, it looks like a communications failure causes the client to lose track of the server job holding the member lock. The server job doesn't know any better so it maintains the locks (which is probably good). The connection is reestablished but the client appears to "forget" which job holds the lock, so your save is rejected because it doesn't know which server job has the member locked. Client-server design is completely foreign to me. Nonetheless, this appears to be a very poor implementation of a critical system function. I don't think anybody can disagree that the communications environment (TCP/IP) is the weak link in every system; this is where we need robust, tolerant code. Working over a WAN, I face this problem a couple of times a day with both CODE and WDSCi; it drives me crazy. -reeve -----Original Message----- From: firstname.lastname@example.org [mailto:email@example.com]On Behalf Of sublime78ska Sent: Saturday, November 16, 2002 9:13 PM To: firstname.lastname@example.org Subject: [WDSCI-L] The member is locked by job QRWTSRVR "Member MYLIB/QRPGLESRC(MYPGM) can not be saved on 192.168.1.1. The member is locked by job QRWTSRVR" I am getting this error message when saving but when I look at the source member on the as400, it has been saved ! I did it a few times in a row, and each time the member was saved correctly on the as400 inspite of the message. The member is locked, that's true, but that it can not be saved is apparently not true. I think I know what happens which causes this: I connect via VPN. The VPN session drops periodically and reconnects. Once that happens, I start to get these messages. Are there any nice ways of restarting WSDc without rebooting my PC? I tried ending all the EVF* jobs but it didn't help. Something along the lines of codeedit /CM EXIT would be nice ! Phil _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l or email: WDSCI-Lemail@example.com Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.