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


  • Subject: Re: Editing Files
  • From: Douglas Handy <dhandy1@xxxxxxxxxxxxx>
  • Date: Mon, 10 Jul 2000 09:55:34 -0400

Henrik,

>If you will continue to use your S/36-system you will have to
>do it at some time 
>anyway. 'First need to edit' is as good time to do this as any.

The obvious problem with this is in continuing to use the S/36
environment.  On the S/36 it was common to delete and recreate files
instead of clearing them.  It obviously is better on the 400 to
replace this with use of CLRPFM, but then you're looking at OCL
changes at a minimum, and potentially RPG II changes if a file is
created as an Output file instead of appending using Output Add.

These changes aren't hard, and really should be done anyway since a
delete/recreate is expensive on the AS/400 (relative to the S/36).
But the point is that the externally described file could revert back
to a flat file in normal operations unless the application is changed
too.

Perhaps the delete cache option they added to the S36EE takes care of
this problem now?  I haven't tried it.

Doug
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.