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





> >
> > Can someone tell me if can you copy a file from a system36 file structureto 
>a
> > native 400 file with a dds created. Does the 400 put the data in the
> > appropriate fields automatically with same record lengths in the 400 pf? Or
> > do I have to write a conversion program?

No conversion program is needed (use CPYF with *NOCHK option)

when you create the DDS for the "new" externally described file, you
must account for every single byte in the record including any blank
spaces. This "normally" doesn't take long but having good file layouts
will really aid in the process. It's those little "I forgot" about
fields that will kill you.(I forgot we did a quicky program to put a "*"
in position 248 if today is Wednesday). Normally if you get the record
length correct, you will be pretty safe to do a cpyf from old to new.

The 400 doesn't "know" where to put the fields, you are just copying
from one file to another.... It assumes you know what you are doing.
+---
| 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 ...

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.