Thanks for all the input but this has ended up being a life lesson!
It would seem that the Jar command must have some additional smarts
about it
The problem was caused when I ran the command. I was zipping up over
80,000 BOL and DR image files. Now, I have done this before without
incident. However, this time was different. When I submitted the job
either thru a program or thru QSH command line I would get a JAVA
LanguageNullPointerException. I tried all night to get this to work as
I needed to FTP the images to a partner.
After posting this earlier question. I decided to just zip the images
up via WINZIP and then transfer the file. Well, after accomplishing
this process and starting my FTP. I left to get a couple hours of sleep.
Shortly, after returning the system crashed. Yep! you guessed it, out of
DASD. The zip file put us well above the threshold and normal business
processes took us the rest of the way. Since then, the system admin and
I have cleaned up the DASD and IFS. Ran the process again, with the
same number of images and it ran without incident. Go figure! The JAR
command would not let me create a zip file that put the system over the
DASD threshold. It is probably not by design; but, due to resource
limitations to do the work. Do not have any white paper or book to back
this up just the experience first hand of witnessing it happen. Then,
we worked thru the process to clean up DASD space. Finally; I was able
to run the exact same process to completions when sufficient storage was
available to successful completion.
One thing is for sure! Next time I have a problem with a JAR command
not working with a LanguageNullPointerException. I will be checking
WRKSYSSTS to find out what % our ASP is at. Just to be sure!!
Thanks for everyone responses!
Charlie Randall
"When you have vision it affects your attitude. Your attitude is
optimistic rather than pessimistic." by Charles R. Swindoll
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Friday, May 18, 2007 1:50 PM
To: Midrange Systems Technical Discussion
Subject: Re: Qshell JAR Command
That command just creates a zip file of everything within the stmimag
directory.
No. It creates a zip file of everything that contains a dot in the
stmimag directory. That's what *.* means... anything that contains a
dot. Just as *a* means anything that contains an "a", and *b* means
anything that contains a "b", *.* means anything that contains a "."
If he wanted everything, he needed to change the *.* to just *
jar cfM /stmimag/stmimages.zip -C stmimag/*
Also, I'm skeptical about the "cfM". Shouldn't the filename follow the
"f"??? Isn't that the point of the "f" to denote that it's followed by
the filename?
So it should be:
jar cMf /stmimag/stmimages.zip -C stmimag/*
The directory names are also a bit suspect. You don't want to zip all
files in the same directory name that you're saving the ZIP file to, do
you? You'd end up including the ZIP file in the files you're backing
up... Of course, that would only be the case if the CWD was /, which
it may not be, maybe he has two separate directories with the same name
in different places. That would make sense, since a relative path is
used in one place, and an absolute path in the other.
Too bad the original poster gave so little information about the
situation. I could spend all afternoon in conjecture.
midrange.com
