× 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: File Upload to 400
  • From: "Weatherly, Howard" <hweatherly@xxxxxxxxxxxx>
  • Date: Thu, 10 Dec 1998 13:14:32 -0500

Sannon,

Maybe I am not understanding the problem completely, but! try creating
a PF (CRTPFM) with the record size of 60, then try to FTP the data to
that file. You still wont have <CR> at the end of each line but from
there you should be able to use CPYF to get the data where you need
it. In fact if the upload is working, and I assume it does from what
you said, you should be able to CPYF from that to the real file. Note
you may need to specify ADD records and NOCHK or perhaps CVTSRC on the
CPYF command, but if you tinker with that I believe you will be Ok.

______________________________________________________________________
___
Howard Weatherly

hweatherly@dlis.dla.mil
howard.weatherly@ctg.com
hweath@ibm.net

X4324

 <<File Upload to 400>> 


I have a file on my PC that is simple text file but the vendor
neglected to
put end-of-record markers at the end of each (60 char) record.  Each
field
in the record is fixed length and starting column, ie. no delimiters.
I've
tried a few things such as uploading through a file description on the
PC of
the physical, and it hated that there was no marker.  I uploaded the
file
into a document folder and tried CPYFRMPCD into 60 char flat physical
(no
fields) and it didn't like that either.  I even tried using the most
recent
posts regarding CPYFRMINPF and didn't seem to get anywhere (it also
didn't
lilke anything I gave it).  Any ideas???  (TIA)   I am avoiding having
to
massage the file on the PC at all costs.

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