× 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: csv output from cpytoimpf
  • From: Gwecnal@xxxxxxx
  • Date: Tue, 16 May 2000 12:51:13 EDT

In a message dated 5/16/2000 10:17:01 AM EST, David Morris 
[SMTP:dmorris@plumcreek.com] writes:

> Lance,
> You have to set the code page for the output file before you run your
> CPYTOIMPF.  Look at the MOV and CPY commands.  I use a base file 
> like ASCII.CHR which has a code page of  367 and CPY this file to my 
> CPYTOIMPF target.

> David Morris


David,

Just so I'm clear on this - My cl now creates a pf in qtemp, does a CPYTOIMPF 
to that physical, followed by a CPYTOSTMF from the physical to the target on 
the Novell file server.  You are saying create a pf with a ccsid of 367 (how 
long a record or does it matter) and leave it around for export jobs.  Then 
my cl would do a cpy of this file to the Novell file server, followed by a 
CPYTOSTMF from the physical I want to export directly to the file I just 
copied to the server.  It is still a two step process, but probably faster 
because the first copy would not need to have any records.  Do I have this 
right?   Thanks, Lance
+---
| 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.