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




Larry,

from command PKZ231410/PKZIP . . . .parameter FILETYPE( )

Type of file . . . . . . . . . .   *CALC         *TEXT, *BINARY, *EBCDIC,
*CALC

                                  Help

Specifies whether the files selected are treated as text or binary data.
For text files added to an archive, trailing spaces in each line are
removed, the text is converted to ASCII by default and a carriage return
and line feed (CR/LF) are added to each line before the data is
compressed into the archive.  Binary files are not converted at all.
PKZIP has tables optimised for textual or binary data, so for the best
compression results specify this option appropriately.  Refer to the
XLATETAB keyword for details on how to specify a special translate table
for use with text data.

Use of text file options is usually faster because PKZIP has to process
less data than with *BINARY.

If the file is a Save File then it will be processed as such, no matter
what option is specified here.

The possible values are:

*CALC
    PKZIP will do a statistical analysis of the data to determine if it
    is TEXT or BINARY. If the file is very small then PKZIP may get it
    wrong - but normally it gets it right.  This is the default.

*BINARY
    No conversion is to be performed.

*TEXT
    CR/LF appending and character translation to ASCII is performed.

*EBCDIC
    The file is opened and processed as a text file, but no translation
    is performed.  This option is faster than *TEXT but only use it for
    archives which are not to be transferred to another platform.


So. . . .CPYTOIMPF (DB-DB) to get flat file. . . . .PKZIP to compress and
xlate. . . .FTP Binary to send

_______________________________________________________________

Regards,        Rod Orr


>>>>>>>.
I guess I am not making my self understood.  We FTP a zipped file therefore

not translation can talk place.  The sole purpose is to reduce the amount
of
time transfering the data because the files being FTPd are very big.  Last
nights file was 976MB  unzipped.  We did the CPYTOSTMF but that takes a lot

of time.

I want to be able to translate the PF back and forth from  ASCII to EBCDIC
etc.  This would eliminate the timely CPYTOSTMF.  The zipping would
eliminate
the costly transfer by FTP.

Larry
<<<<<<<<


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