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


  1.  Home
  2. WDSCI-L
  3. September 2006

Re: Source not updated

Did you "Save" the member before compiling it? When you close a member, if you haven't saved it, it will tell you so and give you the opportunity to do so (or to decline the offer). 


        * Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Justin Taylor wrote:


This morning I made a change to an RPG/400 source member using LPEX and
compiled it from WDSc.  I ran the program from a 5250 session and the
change did not appear to have taken effect, so I debugged the program.
In debug mode, I noticed that the source did not include my change.  I
checked my compile listing and it was also missing there.  I checked the
source via PDM and it does not have my change and shows a last changed
date of 09/01/06.  I confirmed that I was working with the correct
member by attempting to open it for edit in SEU.  It gave me a message
saying that it was locked.  I closed the member in WDSc and then I was
able to open it with SEU.  I closed SEU and opened the member again in
WDSc and it does have my change.

Two questions:
1. How do I force my change to be applied?
2. How do I keep this from happening again?

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.