× 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.



Gene, 
I have had this issue several (seemingly random) times.  

I had written to this list a month or two ago with the only one
suggestion of PMR time.  Since Violaine has replied perhaps I can give
some details of how I use WDSC that might help with figuring out what's
causing QRWTSRVR to have a lock.

While I was actively trying to figure this out I changed my work library
authority such that someone would need to sign on as me or QSECOFR to
even view my source member(s).  I still got the error after that was set
so I'm confident that no one else was in the member.

I thought maybe it would be because of the number of members I had open
in LPEX, but the times I got the error didn't seem to matter 10 or just
1 member open.  Next I tried only editing members in one connection at
any one time, but again I go the error both when I was only connected to
one iSeries connection and when I was connected to multiple (which is my
usual setup).

I am using WDSc 6.0.1.1 with the Turnover plugin.  I had other plugins
installed, however because of a previous PMR I recently had to uninstall
WDSc, clean the directories and then re-install.  Now that I think of it
I haven't seen this problem since then.  It's certainly not a quick fix,
but if your interested in trying this here's the link that the IBM
support rep gave me to clean the directories after uninstalling WDSc.

http://www-912.ibm.com/8625680A007CA5C6/1AC66549A21402188625680B0002037E
/B4EAB2F23609F1098625708300792A91 

Happy Coding,

Gregory Simmons
Development Programmer, Tech Services
Jack Henry & Associates

-----Original Message-----
From: wdsci-l-bounces+gsimmons=jackhenry.com@xxxxxxxxxxxx
[mailto:wdsci-l-bounces+gsimmons=jackhenry.com@xxxxxxxxxxxx] On Behalf
Of wdsci-l-request@xxxxxxxxxxxx
Sent: Monday, May 08, 2006 12:00 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: WDSCI-L Digest, Vol 4, Issue 255

Send WDSCI-L mailing list submissions to
        wdsci-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/wdsci-l
or, via email, send a message with subject or body 'help' to
        wdsci-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        wdsci-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WDSCI-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

   1. Compile in Batch hangs (Scotta@xxxxxxxxxxxxxxxxxxxx)
   2. Re: Receiveing RSEF1002E when saving source member (Gene Burns)


----------------------------------------------------------------------

message: 1
date: Mon, 8 May 2006 09:16:44 -0400
from: Scotta@xxxxxxxxxxxxxxxxxxxx
subject: [WDSCI-L] Compile in Batch hangs



We are having a problem compiling in RSE when the 'Compile in Batch' is
selected under Window>Preferences>RemoteSystems>iSeries>Command
Execution.

We are using WDSC version 6.0.1.

When the compile is submitted from RSE, the compile command appears at
the
bottom of the screen, and the status bar begins moving, but it hangs.
We
end up having to hit the cancel button.  If we turn off 'Compile in
Batch',
the compiles work fine.

The 'Compile in Batch' option did work for a couple of weeks, then last
week, quit working again.  Nothing has changed on the iSeries.  Is there
a
job or subsystem that needs to be running on the iSeries to handle the
'compile in batch'  that may not be running on our iSeries?

Has anyone else had a similar problem?

Scott Angalich

Web Specialist
Wheeling-Nisshin, Inc.
(304) 527-4848
scotta@xxxxxxxxxxxxxxxxxxxx

------------------------------

message: 2
date: Mon, 08 May 2006 09:14:32 -0500
from: Gene Burns <burns.gene@xxxxxxxxx>
subject: Re: [WDSCI-L] Receiveing RSEF1002E when saving source member

Hi Violaine,

No, no one else was trying to access the member.  However, I have not 
seen this happen again in the last two weeks or so.  I'm not sure what 
might have changed.  The only WDSC PTF's installed on the iSeries did 
not mention anything about LPEX, only debugger and webfacing.  We aren't

using webfacing.

Thanks,

Gene Burns
Haulers Insurance Company

Violaine Batthish wrote:
> Hey Gene,
>
> When you go to the Jobs subsystem and expand  My active jobs, then
QUSRWRK,
> does that same job appear listed there?
> Is there any possibility that someone else might try to edit the same
> member while you are?
>
> thanks,
>
>
> Violaine Batthish
> WebSphere Development Studio Client, IBM Toronto Lab
>
> You know you've achieved perfection in design, not when you have
nothing
> more to add, but when you have nothing more to take away. - Antoine de
> Saint-Exup?ry
>
>
>
> wdsci-l-bounces@xxxxxxxxxxxx wrote on 20/04/2006 09:43:09 AM:
>
>   
>> Hi Violaine,
>>
>> Here is the error from the log:
>>
>> !ENTRY com.ibm.etools.systems.core 4 0 Apr 13, 2006 12:18:25.509
>> !MESSAGE RSEF1002E: SUB#0:Member LKEEL/QDDSSRC(ATD050FM) can not be
>> saved on HAULERS. The member is locked by job QRWTSRVR
>>
>> Gene Burns
>> Haulers Insurance Company
>>
>> Violaine Batthish wrote:
>>     
>>> Hi Gene,
>>>
>>> Do you see any errors in your worspace\.metadata\.log file when this
>>> occurs?
>>>
>>> thanks,
>>>
>>> Violaine Batthish
>>> WebSphere Development Studio Client, IBM Toronto Lab
>>>
>>>       
>
>
>   


------------------------------


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.