• From: "Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>
  • Date: Mon, 22 Mar 99 20:35:13 +1100

Mello Evan,

This has been bothering me for a few days now.  I think the solutions involving 
the two step process are your 
only option without writing your own program to directly create the CSV file in 
the IFS.  You could do that 
with the system APIs.  I don't have a /400 avaiable to play with the CPYFRMIMPF 
and CPYTOSTMF commands.

However what's really been niggling at me is this:  (I am not specifically 
picking on you but this attitude 
irritates me.)

You wrote:
>I have been trying to produce a comma delimited .txt file for a PC from a
>physical file for a few days now, and the correct use of the CPYTIMPF
>command escapes me.

----------- Stuff deleted ----------------------------------------------

>I am NOT INTERESTED in a commercial product at this stage, as the volume
>doesn't warrant it at present.

Yet you're quite happy to spend a few days on the problem?  Buy something and 
save your company some money!  
These sorts of utilities are generally not expensive.

Simon Coulter.

 FlyByNight Software         AS/400 Technical Specialists       
 Eclipse the competition - run your business on an IBM AS/400.  
 Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           
 Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      
 Windoze should not be open at Warp speed.                      

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


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].