Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Neil Truby asked for a way to compress onunload output on the fly and decompress directly into onload, like ontape STDIO. Christian Knappke's replies are garbled in the archive. Neil said the source and target were on separate UNIX servers and thought of using rsh. No clear solution shown.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Neil Truby — — source: Usenet: comp.databases.informix
Has anyone a technique for compressing onunload output as it's created ...
and uncompressing it directly to onload?
Similat to the ontape -s -t STDIO facility.
thx
--
Neil Truby t:01932 724027
Director m:07798 811708
Ardenta Limited e:neil.truby@ardenta.com
Neil Truby — — source: Usenet: comp.databases.informix
"Christian Knappke" <chknews@gmx.net> wrote in message
news:Xns993B63CFC8D52HZqjX8Z9@news.sap-ag.de...
> From the keyboard of "Neil Truby" <neil.truby@ardenta.com>:
>
>> Has anyone a technique for compressing onunload output as it's
>> created ... and uncompressing it directly to onload?
>>
>> Similat to the ontape -s -t STDIO facility.
>
> Unload to a fifo/named pipe, let gzip/compress read from there and> write to another fifo/named pipe, let onload read from that.
>
> But why would you want to do that instead of piping directly from
> onunload to onload?
The source and target databases are on separate UNIX servers. I guess I can
try something clever with rsh ....
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.