On Thu, 26 Apr 2018 07:33:39 +0200, Peter Hunkeler wrote:
>
>>IMHO it is problem with IBM. Are you deaf?
>Sometimes it is; sometimes they are. However, not this time.
>
>>People really NEED the functionality to simply make single dataset archive,
>>transmit it to PC *with no tricks and black magic* and then upload it to a
>>z/OS and unpack.
>
>Know your job. What is difficult about running two programs one after the
>other to get the desired result?
>
IBM could make it easier, rather than assuming the burden of providing
full employment for customers' systems programmers. Ideally:
All archiving facilities such as ADRDSSU, TERSE, TSO TRANSMIT, pax, IEBCOPY,
... should treat their archives as featureless streams which can be wrtteh
to CKD DASD, tape, directed to UNIX files (which could be piped to network
or transmitted via FTP BINARY), ... Extraction should ignore record boundaries
in those archives.
pax does this well. Its archives can be CKD data sets (and it's
nondiscriminatory
concerning DCB attribute) or UNX files, and I can usefully:
pax -w directory | ssh some.host "pax -vr" # (Simplified.)
Example: GIMZIP relative files are IEBCOPY PDSU which GIMZIP transforms to UNIX
files and RECEIVE FROMNTS transforms back to Classic PDSU. Considerable
overhead
in processing and allocation of temp ds could be avoided if IEBCOPY deaht
directly
with UNIX files as PDSU.
... the others shoulc take a c[l]ue.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
