The "jar" command is really just a special launcher that runs some Java code that uses the java.util.zip package, so it would be zAAP enabled. The native library used by java.util.zip is zAAP enabled.
Using "jar" requires that the file be first stored in an HFS file, since jar can only process files, and not "stdin". It's pretty easy to fix this by writing a little java program that uses java.util.zip. The result is that you can do this: //EX1 EXEC DTLSPAWN //STDIN DD * fromdsn -t 819 //DD:ZIPIN | java -cp /home/myid ZipStream | todsn -b //DD:ZIPOUT //ZIPIN DD DSN=MYID.IN.DATA,DISP=SHR //ZIPOUT DD DSN=MYID.OUT.ZIP.DATA, // DISP=(NEW,CATLG), // DCB=(RECFM=U,BLKSIZE=27998), // SPACE=(CYL,(500,200),RLSE) // So, not only is this free and uses to zAAP, but it's pretty easy to make into a utility PROC. One downside is the cost/time required to start a java vm. This can be reduced by using the "shared classes" feature of java 5, which is even better in java 6. The source code for the java "ZipStream" program is posted here: http://www.dovetail.com/forum/viewtopic.php?t=659 Kirk Wolf Dovetailed Technologies ---------------------------------------------------------------------- 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
