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



Hello again:

I left out a detail in my last post.

The read only issue happens when your cursor on one of the error messages
AND your next verify has no errors.

The verify process removes the old error messages and at that point the
source changes to read only.

John


"John Larimer" <jklarimer@xxxxxxxxxxx> wrote in
message news:bo968j$k51$1@xxxxxxxxxxxxxxxx
> Hello:
>
> I figured out what is causing this problem!
>
> When you do a verify and have errors, the error list pops in a seperate
> window.  You select an error from the error list window and CODE positions
> you to the line of your source with the error.  Below the source line in
> error are additional information messages which on my display, have a
yellow
> background.  I think these are considered 'show lines'.
>
> What I found is if you have your cursor positioned on one of the error
> message lines and try to do another verify, your open source member
changes
> to read only.
>
> Now that I know what to watch for, I think I can keep it from happening in
> the future.
>
> John
>
>
> "Hak Lui" <haklui@xxxxxxxxxx> wrote in
message
>
news:OF16B36DDA.AB76BC6D-ON85256DC1.00473BCA=G1DYhSM1WHSmdvSpIQae8A@xxxxxxxx
mane.org
> >
> >
> >
> >
> > >>The windows that pop during verify process seemed to have an extra
> > 'flash'
> > >>and then I notice the save button for the source I just verified
changes
> > to
> > >>dimmed out.
> > >>..
> > >>When I checked the file properties, the description for the source had
> > >>changed to 'GLOBAL.LOCKLOCALFILES', the record length was set to zero
> and
> >
> > >>the source type was blank.
> >
> > I did a little bit of investigation, and I have no clue how this has
> > happened.
> > A few questions though.
> > 1. Does your source contain COPY?
> > 2. Do you find anything suspicious related to connection in the
> > communications error log?
> > 3. Do you see the C:\WDSC\Tmp\VERIFY.LST on your editor window?
> >
> > Have you tried by first 'Save as ..' a local file for verify/edit and
then
> > restore back later?
> >
> >
> >
> > Best regards,
> >     Hak
> > _______________________
> > Hak Lui
> > WebSphere Development Studio Client for iSeries, IBM Canada Ltd.
> > e-mail: haklui@xxxxxxxxxx
> >
> > _______________________________________________
> > This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> > To post a message email:
CODE400-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/code400-l
> > or email: CODE400-L-request@xxxxxxxxxxxx
> > 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
> >
> >
>
>
>
> _______________________________________________
> This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> To post a message email: CODE400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/code400-l
> or email: CODE400-L-request@xxxxxxxxxxxx
> 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
>
>




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.