>> /u/userid/zip31b: >zip -av -1 /tmp/BIG_FILE.zip "//'userid.BIG.FILE'"
> Sadly, it's all a dead end, because it looks like zip can't handle
> this kind of filename:
> It looks like all that "dots" stuff in the filename handling code
> needs another wrinkle added for full MVS + USS support.
Bob, thanks for confirming that infozip in USS is unable to handle MVS
files as I kept getting :
zip warning: name not matched: //userid.BIG.FILE
zip error: Nothing to do! (BIG_FILE.ZIP)
was wondering perhaps I had gotten the syntax wrong.
> See comments on the Info-ZIP forum where I offer some SWAG theorizing
> about how I must have broken the name display -- and somebody (EG, I
> think) explains the use of the 3 name fields.
Thanks, I seen the comments made on the forum and changed z->oname to
z->name which appears to resolve the display problem.
> Maybe this weekend I can refresh my memory of what I did and send you
a
> proper diff.
Thank you.
Perhaps for a different thread, but INFOZIP related, anyone know if its
possible :
1. to retain trailing blanks in the file for FB records ?
2. modify the current EBCDIC/ASCII translation table (eg. to change all
non-keyboard characters to '?')
Thanks to all for your reponses.
Please Note: This email and its contents are subject to our email legal notice
which can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
