Re: Writing and FTP'ing IFS Stream File

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Mary,

If you create the file with 819 (instead of creating with 37 and 
duplicating to 819) it will still be readable...

If the goal is to have an archive of what your client has downloaded, 
then by all means make another copy of it.  But I would suggest 
generating it originally as 819, and then just making an archive copy of 
it.  That's a bit more straightforward, and your archive will be exactly 
what the client downloaded (instead of a translated version.)

The system will have no problem reading/displaying a file that's in 
CCSID 819.  (Or, indeed, most flavors of ASCII or Unicode...)


On 8/26/2015 4:21 PM, Mary Lynn Riggins wrote:
> As for the conversion - yes it would make sense to create it with 819
> on one hand, on the other hand, if I create it as 37 and convert to
> another file, which is the file that will be sent to the client and
> then removed from the IFS, I will have the original on the IFS folder
> in a format that is readable as a reference if the client has
> questions about the data and/or file sent.