zfs in DLF
0.55 MINUTES EXECUTION TIME without
Carmen
- Original Message -
From: "Kirk Wolf"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Friday, April 28, 2017 9:33:07 AM
Subject: Re: JZOS Java CLASSPATH
>
>
> A good practice would be to have helper shell scripts
>
>
> A good practice would be to have helper shell scripts that do site
standard setup for JZOS and then call or dot them in from STDENV.
Or simple ones:
CLASSPATH="$CLASSPATH":$(expandJars $MYDIR)
If you feel strongly that JZOS is less usable without wildcard jar
expansion of CLASSPATH, then b
On 28/04/2017 12:16 PM, Andrew Rowley wrote:
On 28/04/2017 1:28 PM, David Crayford wrote:
I agree that it would be ideal if the JZOS batch launcher was
modernized to support wildcards but disagree about the shell. I find
it's absolutely necessary just to do stuff like:
. /etc/profile #
From: "Andrew Rowley"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, April 27, 2017 8:13:03 PM
Subject: Re: JZOS Java CLASSPATH
On 28/04/2017 3:23 AM, Kirk Wolf wrote:
> And yet I fail to see why this is an issue since the JZOS sample JCL shows
> how to use the shell language
On 28/04/2017 1:28 PM, David Crayford wrote:
I agree that it would be ideal if the JZOS batch launcher was
modernized to support wildcards but disagree about the shell. I find
it's absolutely necessary just to do stuff like:
. /etc/profile # set TZ variable and other stuff
Whether ther
On 28/04/2017 9:13 AM, Andrew Rowley wrote:
On 28/04/2017 3:23 AM, Kirk Wolf wrote:
And yet I fail to see why this is an issue since the JZOS sample JCL
shows
how to use the shell language to handle this - with more flexibility.
For example, the "java" command launcher can't do this:
for i in
On 28/04/2017 10:50 AM, Denis wrote:
One example, the jvm needs to scan every java class for specific annotations.
The more unneccessary files in the classpath, the longer that takes.
Is that the JVM doing it, or is it actually done by certain frameworks
that use annotations?
My understandi
On 28/04/2017 3:23 AM, Kirk Wolf wrote:
And yet I fail to see why this is an issue since the JZOS sample JCL shows
how to use the shell language to handle this - with more flexibility.
For example, the "java" command launcher can't do this:
for i in "${MYDIR}"/foo*.jar; do
CLASSPATH="$CLAS
-
From: Andrew Rowley
To: IBM-MAIN
Sent: Fri, Apr 28, 2017 02:08 AM
Subject: Re: JZOS Java CLASSPATH
On 28/04/2017 4:34 AM, Denis wrote:
> as the classpath size affects performance, its definitly a good idea to limit
> the jars and its contents to what is required.
>
I wouldn't expect
On 28/04/2017 4:34 AM, Denis wrote:
as the classpath size affects performance, its definitly a good idea to limit
the jars and its contents to what is required.
I wouldn't expect the classpath size to have a significant effect on
performance, since Java can read and cache the directories from
e -
From: "Kirk Wolf"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, April 27, 2017 2:47:09 PM
Subject: Re: JZOS Java CLASSPATH
the JZOS batch launcher does work as designed - it allows you to use a z/OS
Unix shell script to configure everything including CLASSPATH.
What
VA_HOME}"/lib/ext
> # Add Application required jars to end of CLASSPATH
> for i in "${APP_HOME}"/*.jar; do
> CLASSPATH="$CLASSPATH":"$i"
> done
> export CLASSPATH="$CLASSPATH":
>
>
> Carmen
>
> - Original Message -
>
..@listserv.ua.edu>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, April 27, 2017 1:34:26 PM
Subject: Re: JZOS Java CLASSPATH
Hi Carmen,
as the classpath size affects performance, its definitly a good idea to limit
the jars and its contents to what is required.
In addition some customers requ
results with the order of the jars.
Denis.
-Original Message-
From: Carmen Vitullo
To: IBM-MAIN
Sent: Thu, Apr 27, 2017 8:31 pm
Subject: Re: JZOS Java CLASSPATH
Funny I'm looking at both right now, getting ready for a migration of an
application from Java on Unix to Java on
required jars to end of CLASSPATH
for i in "${APP_HOME}"/*.jar; do
CLASSPATH="$CLASSPATH":"$i"
done
export CLASSPATH="$CLASSPATH":
Carmen
- Original Message -
From: "Kirk Wolf"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, April 27, 2017
Yes, this is a feature of the "java" command JVM launcher that is not
present in the JZOS batch launcher and the "java" command launcher.
Both launchers invoke the JVM launcher API and pass in "-Djava.class.path="
as an option using $CLASSPATH, but the "java" command launcher seems to be
enhanced
On 27/04/2017 09:49 PM, Peter Hunkeler wrote:
You need to escape the * so that the shell will assign it to the environment variable
instead of "resolving" it. Try:
I don't think so. I have a small Java program to display the CLASSPATH
environement variable and what it resolves to:
import jav
>> No it is not! Oracle has a lab in France that is in charge of the porting
>> process.
>> IBM merely repackages what Oracle provides from the porting lab into PTFs.
>>
>With more testing today, it looks like the culprit is the JZOS batch
>launcher. It seems that it doesn't support the Java 1.6+
On 26/04/2017 10:37 PM, Allan Staller wrote:
Maybe the IBM JVM is different to the Oracle one? I tried to find IBM
documentation, but it is not so explicit.
No it is not! Oracle has a lab in France that is in charge of the porting
process.
IBM merely repackages what Oracle provides from the
tried what is decribed in the document you have referenced.
Denis.
-Original Message-
From: Andrew Rowley
To: IBM-MAIN
Sent: Wed, Apr 26, 2017 2:34 pm
Subject: Re: JZOS Java CLASSPATH
On 26/04/2017 09:19 PM, Denis wrote:
> Hi Andrew,
>
> your understanding is no
Maybe the IBM JVM is different to the Oracle one? I tried to find IBM
documentation, but it is not so explicit.
No it is not! Oracle has a lab in France that is in charge of the porting
process.
IBM merely repackages what Oracle provides from the porting lab into PTFs.
::DISCLAIMER::
--
On 26/04/2017 09:19 PM, Denis wrote:
Hi Andrew,
your understanding is not correct.
Wildcards do not and have never worked with CLASSPATH.
I was reading:
https://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
"Understanding class path wildcards"
I thought it was working
ichael
Von:Andrew Rowley
An: IBM-MAIN@LISTSERV.UA.EDU,
Datum: 26.04.2017 13:04
Betreff:JZOS Java CLASSPATH
Gesendet von: IBM Mainframe Discussion List
The JCL supplied with the JZOS batch launcher has a section to add jars
to the classpath:
# Add Application require
Hi Andrew,
your understanding is not correct.
Wildcards do not and have never worked with CLASSPATH.
Hope it helps.
Denis.
-Original Message-
From: Andrew Rowley
To: IBM-MAIN
Sent: Wed, Apr 26, 2017 1:04 pm
Subject: JZOS Java CLASSPATH
The JCL supplied with the JZOS batch
The JCL supplied with the JZOS batch launcher has a section to add jars
to the classpath:
# Add Application required jars to end of CLASSPATH
for i in "${APP_HOME}"/*.jar; do
CLASSPATH="$CLASSPATH":"$i"
done
My understanding is you should be able to use a wildcard instead and the
JVM w
25 matches
Mail list logo