Date:         Fri, 2 Aug 2002 09:36:29 -0400
Reply-To:     Michael Raithel <RAITHEM@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Michael Raithel <RAITHEM@WESTAT.COM>
Subject:      OT: But Helpful; WinZip In Batch!
Content-Type: text/plain; charset="iso-8859-1"

Dear SAS-L-ers,

Even though my middle name is MVS, I do all of my work here at SAS Mecca in
either the Unix or Windows environments.  In "nuking out" a recent project,
I ran across something that might be of great benefit to those who make
their living programming in Windows environments.  It is the absolutely new
"WinZip Command Line Support Add-ON".  If you are not interested in it, or
are already familiar with it, do not read past this line:

----------------------------------------------------------------------------
------------------

Okay!  Great!  We ditched them; now we can talk:

We have a person who is charged with WinZip-ing dozens of files (that are
reports generated by the SAS System for Information Delivery) into various
WinZip files for clients.  That person is saturated with
pointing-and-clicking--especially on Monday when she must create the Daily
_AND_ Weekend WinZip files.  The manual effort is mind (and finger) numbing!

I wondered if there was a way to run WinZip in batch and found the following
on the WinZip site:

        http://www.winzip.com/wzcline.htm

I downloaded the WinZip Command Line Support Add-ON, and tested it out.  It
worked as advertised!  SAS Mecca is at an earlier version of WinZip, and you
need Version 8.0 or above for the WinZip Command Line Support Add-ON to
function.  So, I upgraded my desktop copy.  I was pleased to see that the
Zip files I created were usable with the earlier version of WinZip--just as
WinZip technical support said that they would be.

Here is an example of the contents of a ".bat" file that I wrote to create a
WinZip file:

"C:\MIKEDIR\WINZIP63\WZZIP" -u -s"sasguru" "H:\PROD Files\Zipped\DRDH02.zip"
Report1.RPT Report2.RPT Report3.RPT

In the example, above, the Zip file "H:\PROD Files\Zipped\DRDH02.zip" is
created if it does not exist, or updated (the "-u" is for "update the Zip
file's contents").  The password "sasguru" is assigned for all of the files
in the Zip file.  Three files, Report1.RPT, Report2.RPT, and Report3.RPT are
either added to the Zip file if it is new, or updated if the Zip file is old
and they already exist.

I am going to create a number of batch files that I will kick off with (of
course) SAS programs that check for report file existence and currentness.

Is this way-cool, or what?!?!?!?!

Best of luck to all of you SAS-L-ers reading this Off Topic posting on a
Friday morning!

I hope that this suggestion proves helpful now, and in the future!

Of course, all of these opinions and insights are my own, and do not reflect
those of my organization or my associates. All SAS code and/or methodologies
specified in this posting are for illustrative purposes only and no warranty
is stated or implied as to their accuracy or applicability. People deciding
to use information in this posting do so at their own risk.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Michael A. Raithel
"The man who wrote the book on performance"
E-mail: MichaelRaithel@westat.com
Author: Tuning SAS Applications in the MVS Environment
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A computer lets you make more mistakes faster than any invention
in human history - with the possible exceptions of handguns
and tequila. - Mitch Ratliffe
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++