Tom writes:
>   ** first off, the file is/was packaged up using "winzip", but
> in such a way that (g)unzip is having trouble extracting the
> files.  Only mildly annoying, and the simple solution was to
> extract the files on my PC and use ftp to transfer the files
> [and/or reflection file transfer]

You should be able to use the Java 'jar' utility as an unzip on the 3000.
JAR files are just ZIP files by another name and with some conventions for
including a "manifest" file.  You can try just renaming the .zip file to
.jar, but I'm not positive you have to do that.

>   ** the problem we're coming up with now is that the files are
> "corrupt" after the transfer; I suspect the problem is in
> converting "to byte stream files" [used binary mode on the
> initial transfer, then MPEX %altfile;byte to do the whole lot of
> them at once]

See if jar can read your .jar files before you convert them to bytestream.

Be sure MPEX isn't trying to do something funny like text file conversion.

>   -- even tried an explicit reflection transfer [not reflection
> FTP] to send "as a bytestream file" in the first place; still no joy
>
>   ** at least, we THINK they are "corrupt" because the command
>
>       /usr/local/java/jdk1.2.2/bin/jar tvf AnyOfTheFiles.jar
>
>      reports errors trying to extract the contents [things like
> "file too large"]

Make sure you can open the .jar files on the PC using WinZip (or equivalent)
also (may need to rename them to .zip).

Keep in mind that most jar files are used as-is with java and not extracted
first into individual files (but I guess you're just doing this to test that
the files are not corrupt).

>   ** one thing that seems a bit strange [to me] is that he is
> setting this HUGE classpath variable that is essentially listing
> each and every .jar file as a separate component of the path
> [maybe this needs to be this way -- haven't done much java];

That's typical (though usually you don't have more than a small number of
jar files for one application).  Putting a jar file on the class path puts
all the files in the jar file on the class path without having to extract
them somewhere, so it's quite convenient.  You definitely want to make sure
that these get converted to bytestream files for performance reasons.

> what OTHER things do I have
> to be on the lookout for when using "the shell" vs. MPE or MPEX?

Java stuff will probably be simpler and happier when invoked from the shell.

>   ** the truly astute among you noted I'm using the 1.2.2 JRE --
> is this the "latest" that is actually available for MPE, and if
> not, how/where can I get a better (more current) JRE?

You should be able to get 1.3.mumble from HP (or find it included on 7.5
maybe?).  I'm actually a little behind on the state of Java at the moment
:-)

I think at least one person reported that the readme file for 1.3 says it's
1.2.mumble, so make sure you don't actually have 1.3 already.

> Any other helpful words of wisdom in dealing with either java or
> MQ-series ?

Sounds like you're off to a good start.  The corruption problems should just
be a matter of getting the filetransfer and/or "to byte" operations correct.
Do everything in "binary" mode if there's ever a question.

G.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *