A little more insight on the Java strangeness I'm encountering

2006-05-22 Thread Steve Comstock

As I mentioned this weekend, some Java code
that used to run no longer runs. When I run
a simple lab exercise, I get:

Howdy.class 4: FSUM7343 cannot open "ÈëÈÊÁ/_---" for output: EDC5129I No 
such file or directory.


Howdy.class 4: FSUM7343 cannot open "¦/Î/Ñ?" for input: EDC5129I No such 
file or directory.


Howdy.class 4: FSUM7343 cannot open "¦/Î/%/" for input: EDC5129I No such 
file or directory.



I mentioned that I suspected some kind of ASCII/EBCDIC
interference was happening. Indeed, when I cut and paste
the quoted strings in the above messages and then browse
the text and then say 'dis utf8', I see:

tStream
javaio
javala

Looks like some kind of set up error.

java -version
returns:

java version "1.4.2" 

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) 

Classic VM (build 1.4.2, J2RE 1.4.2 IBM z/OS Persistent Reusable VM 
build cm142-20040917 (JIT enabled: jitc))



javac compiles seem to work


And a newly compliled applet, run from some html,
also works.


So, I'm looking for diagnosis that would fit these
symptoms. Suggestions for where to look, what to
look at, what to look for.

Thanks.

Kind regards,

-Steve Comstock

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-22 Thread Kevin Pintar
Steve,
Talking to a few fellows who have been working with Java on the
mainframe, they suggested looking at the value of 'file.encoding' system
property.

Here is a page that has some code snippets and a discussion that may
help.

http://java.sun.com/developer/JDCTechTips/2003/tt0110.html

Hope it helps,
Kevin

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-22 Thread Steve Comstock

Kevin Pintar wrote:

Steve,
Talking to a few fellows who have been working with Java on the
mainframe, they suggested looking at the value of 'file.encoding' system
property.




And where would I expect to find that? In /usr/lpp/java/J1.4/bin
there is a java.properties file, but it does not have a 'file.encoding'
string anywhere I could find.



Here is a page that has some code snippets and a discussion that may
help.

http://java.sun.com/developer/JDCTechTips/2003/tt0110.html


Well, interesting, but not helpful in telling me where
and how to change my ecoding. I think that's what I need.

Kind regards,

-Steve

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Kevin Pintar
Steve,

Not being an expert in this area, I apologize for possibly wasting your
time, but I was hoping to seed your exploration with the information I
was given as a starting point.

It "seems" as though the file.encoding system property is related to the
file system you are using (HFS, z/FS).  

It very well could be that there is an esoteric property related to the
actual mount point you are using... heck I don't know.

Here is a small java program I wrote to see what my file.encoding system
property was:

import java.io.*;
public class Jtest   
{
  public static void main(String args[]) 
  {  
System.out.println("file.encoding is "   
 + System.getProperty("file.encoding")); 
  }  
}

In my case, the result was: 
file.encoding is Cp1047

Cp1047 is EBCDIC Latin-1 (If I'm not mistaken).

I'm curious if yours says the same thing.  It may not be a Java setting
that is causing your problem but a file system attribute somewhere.

Just trying to help,
Kevin

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Kirk Wolf

Steve,

Java System properties can be set on the java command line:

java -Dfile.encoding=iso8859-1 HelloWorld

I'm sorry, but I've lost track of exactly what you are trying to do.
Can you post some sample code / commands to reproduce your problem?

A canonical example (from a z/OS shell):

$ cat HelloWorld.java
public class HelloWorld {
public static void main(String[] args) {
 System.out.println("Hello World");
}
}

$ javac HelloWorld.java
$ java HelloWorld
Hello World
$

Does this work for you?

Kirk

Steve Comstock wrote:


Kevin Pintar wrote:


Steve,
Talking to a few fellows who have been working with Java on the
mainframe, they suggested looking at the value of 'file.encoding' system
property.




And where would I expect to find that? In /usr/lpp/java/J1.4/bin
there is a java.properties file, but it does not have a 'file.encoding'
string anywhere I could find.



Here is a page that has some code snippets and a discussion that may
help.

http://java.sun.com/developer/JDCTechTips/2003/tt0110.html



Well, interesting, but not helpful in telling me where
and how to change my ecoding. I think that's what I need.

Kind regards,

-Steve

--
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



--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Steve Comstock

Kevin Pintar wrote:

Steve,

Not being an expert in this area, I apologize for possibly wasting your
time, but I was hoping to seed your exploration with the information I
was given as a starting point.

It "seems" as though the file.encoding system property is related to the
file system you are using (HFS, z/FS).  


It very well could be that there is an esoteric property related to the
actual mount point you are using... heck I don't know.

Here is a small java program I wrote to see what my file.encoding system
property was:

import java.io.*;
public class Jtest   
{
  public static void main(String args[]) 
  {  
System.out.println("file.encoding is "   
 + System.getProperty("file.encoding")); 
  }  
}

In my case, the result was: 
file.encoding is Cp1047


Cp1047 is EBCDIC Latin-1 (If I'm not mistaken).

I'm curious if yours says the same thing.  It may not be a Java setting
that is causing your problem but a file system attribute somewhere.

Just trying to help,
Kevin


Doesn't run. I compiled it OK, but when I run, same set of messages:


Jtest.class 5: FSUM7343 cannot open "ÈëÈÊÁ/_---" for output: EDC5129I No 
such file or directory.


Jtest.class 5: FSUM7343 cannot open "¦/Î/%/" for input: EDC5129I No such 
file or directory.


Jtest.class 5: FSUM7343 cannot open "¦/Î/Ñ?" for input: EDC5129I No such 
file or directory.



Kind regards,

-Steve Comstock

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Steve Comstock

Kirk Wolf wrote:

Steve,

Java System properties can be set on the java command line:

java -Dfile.encoding=iso8859-1 HelloWorld

I'm sorry, but I've lost track of exactly what you are trying to do.
Can you post some sample code / commands to reproduce your problem?

A canonical example (from a z/OS shell):

$ cat HelloWorld.java
public class HelloWorld {
public static void main(String[] args) {
 System.out.println("Hello World");
}
}

$ javac HelloWorld.java
$ java HelloWorld
Hello World
$

Does this work for you?

Kirk


OK, from the beginning.

File Howdy.java --- :

/**
* Java sample
* @version 1.1 05/24/2001
* @author Steve Comstock
*/
public class Howdy
{
  public static void main(String[] args)
  {
   System.out.println("Hello, Steve, Ha Ha to Java!");
  } // end main method
} // end of class Howdy


The compile (no diagnostics) --- :

javac Howdy.java


The execution --- :

Howdy.class
Howdy.class 4: FSUM7343 cannot open "¦/Î/Ñ?" for input: EDC5129I No such 
file or directory.
Howdy.class 4: FSUM7343 cannot open "ÈëÈÊÁ/_---" for output: EDC5129I No 
such file or directory.
Howdy.class 4: FSUM7343 cannot open "¦/Î/%/" for input: EDC5129I No such 
file or directory.



Kind regards,

-Steve Comstock

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Steve Comstock

[re-send with correct Reply-to]
Kirk Wolf wrote:

Steve,

Java System properties can be set on the java command line:

java -Dfile.encoding=iso8859-1 HelloWorld

I'm sorry, but I've lost track of exactly what you are trying to do.
Can you post some sample code / commands to reproduce your problem?

A canonical example (from a z/OS shell):

$ cat HelloWorld.java
public class HelloWorld {
public static void main(String[] args) {
 System.out.println("Hello World");
}
}

$ javac HelloWorld.java
$ java HelloWorld
Hello World
$

Does this work for you?

Kirk


OK, from the beginning.

File Howdy.java --- :

/**
* Java sample
* @version 1.1 05/24/2001
* @author Steve Comstock
*/
public class Howdy
{
  public static void main(String[] args)
  {
   System.out.println("Hello, Steve, Ha Ha to Java!");
  } // end main method
} // end of class Howdy


The compile (no diagnostics) --- :

javac Howdy.java


The execution --- :

Howdy.class
Howdy.class 4: FSUM7343 cannot open "¦/Î/Ñ?" for input: EDC5129I No such 
file or directory.
Howdy.class 4: FSUM7343 cannot open "ÈëÈÊÁ/_---" for output: EDC5129I No 
such file or directory.
Howdy.class 4: FSUM7343 cannot open "¦/Î/%/" for input: EDC5129I No such 
file or directory.



Kind regards,

-Steve Comstock

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread John Tergerson
Steve,

Might a profile entry help?

_BPXK_AUTOCVT=ON; export _BPXK_AUTOCVT

John

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Birger Heede

IIRC

For the execution you need:

java hello

and not just 'hello.class' (which is not executable)

Birger Heede
IBM SWG


Steve Comstock wrote:

Kevin Pintar wrote:

Steve,

Not being an expert in this area, I apologize for possibly wasting your
time, but I was hoping to seed your exploration with the information I
was given as a starting point.

It "seems" as though the file.encoding system property is related to the
file system you are using (HFS, z/FS). 
It very well could be that there is an esoteric property related to the

actual mount point you are using... heck I don't know.

Here is a small java program I wrote to see what my file.encoding system
property was:

import java.io.*;public class 
Jtest   
{  public static void 
main(String args[])   
{  
System.out.println("file.encoding is "+ 
System.getProperty("file.encoding"));   
}  
}   
In my case, the result was: file.encoding is Cp1047


Cp1047 is EBCDIC Latin-1 (If I'm not mistaken).

I'm curious if yours says the same thing.  It may not be a Java setting
that is causing your problem but a file system attribute somewhere.

Just trying to help,
Kevin


Doesn't run. I compiled it OK, but when I run, same set of messages:


Jtest.class 5: FSUM7343 cannot open "ÈëÈÊÁ/_---" for output: EDC5129I No 
such file or directory.


Jtest.class 5: FSUM7343 cannot open "¦/Î/%/" for input: EDC5129I No such 
file or directory.


Jtest.class 5: FSUM7343 cannot open "¦/Î/Ñ?" for input: EDC5129I No such 
file or directory.



Kind regards,

-Steve Comstock

--
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


--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread McKown, John
> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Steve Comstock
> Sent: Tuesday, May 23, 2006 8:45 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: A little more insight on the Java strangeness 
> I'm encountering
> 



> OK, from the beginning.
> 
> File Howdy.java --- :
> 
> /**
> * Java sample
> * @version 1.1 05/24/2001
> * @author Steve Comstock
> */
> public class Howdy
> {
>public static void main(String[] args)
>{
> System.out.println("Hello, Steve, Ha Ha to Java!");
>} // end main method
> } // end of class Howdy
> 
> 
> The compile (no diagnostics) --- :
> 
> javac Howdy.java
> 
> 
> The execution --- :
> 
> Howdy.class
> Howdy.class 4: FSUM7343 cannot open "¦/Î/Ñ?" for input: 
> EDC5129I No such 
> file or directory.
> Howdy.class 4: FSUM7343 cannot open "ÈëÈÊÁ/_---" for output: 
> EDC5129I No 
> such file or directory.
> Howdy.class 4: FSUM7343 cannot open "¦/Î/%/" for input: 
> EDC5129I No such 
> file or directory.
> 
> 
> Kind regards,
> 
> -Steve Comstock

I tried your code, cut-n-paste using ISHELL. I then compiled it using javac 
from IBM J1.3. Initial test is OK. I did the same using J1.4 with the same 
results.

But I can duplicate your output. It appears you are entering the command:

Howdy.class

at the prompt. True? If so that is the problem. Try:

java Howdy

instead. I'm not too sure how the shell is interpreting "Howdy.class", but that 
is NOT a executable file, regardless of the fact that the "eXecute" bit is on 
in the directory entry!

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and its content is protected by 
law.  If you are not the intended recipient, you should delete this message and 
are hereby notified that any disclosure, copying, or distribution of this 
transmission, or taking any action based on it, is strictly prohibited. 
 

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Steve Comstock

McKown, John wrote:

-Original Message-
From: IBM Mainframe Discussion List 
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Comstock

Sent: Tuesday, May 23, 2006 8:45 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: A little more insight on the Java strangeness 
I'm encountering








OK, from the beginning.

File Howdy.java --- :

/**
* Java sample
* @version 1.1 05/24/2001
* @author Steve Comstock
*/
public class Howdy
{
  public static void main(String[] args)
  {
   System.out.println("Hello, Steve, Ha Ha to Java!");
  } // end main method
} // end of class Howdy


The compile (no diagnostics) --- :

javac Howdy.java


The execution --- :

Howdy.class
Howdy.class 4: FSUM7343 cannot open "¦/Î/Ñ?" for input: 
EDC5129I No such 
file or directory.
Howdy.class 4: FSUM7343 cannot open "ÈëÈÊÁ/_---" for output: 
EDC5129I No 
such file or directory.
Howdy.class 4: FSUM7343 cannot open "¦/Î/%/" for input: 
EDC5129I No such 
file or directory.



Kind regards,

-Steve Comstock



I tried your code, cut-n-paste using ISHELL. I then compiled it using javac 
from IBM J1.3. Initial test is OK. I did the same using J1.4 with the same 
results.

But I can duplicate your output. It appears you are entering the command:

Howdy.class

at the prompt. True? If so that is the problem. Try:

java Howdy

instead. I'm not too sure how the shell is interpreting "Howdy.class", but that is NOT a 
executable file, regardless of the fact that the "eXecute" bit is on in the directory 
entry!

--
John McKown


Well, that did it!

I knew it would be something simple.

I swear I could run Java classes without saying 'java'
but it must be the ol' memory failure again.

Thanks all.

Kind regards,

-Steve Comstock

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Jon Brock
It might also depend on your particular environment (whether you formerly ran 
in some sort of IDE you are no longer in, for instance).  I think I recall that 
the "java " format is standard, though.

Jon



Well, that did it!

I knew it would be something simple.

I swear I could run Java classes without saying 'java'
but it must be the ol' memory failure again.


--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-23 Thread Hunkeler Peter (KIUB 34)
>I swear I could run Java classes without saying 'java'
>but it must be the ol' memory failure again. 

Any chance this remembrance is related to playing on 
Windoze? Or on a Mac? They care for file extensions,
UNIX does not.

BTW, someone mentioned the execute bit being set. 
.class files don't need it, don't set it.


Peter Hunkeler
CREDIT SUISSE

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-24 Thread McKown, John
> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Hunkeler Peter (KIUB 34)
> Sent: Wednesday, May 24, 2006 1:33 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: A little more insight on the Java strangeness 
> I'm encountering
> 
> 
> >I swear I could run Java classes without saying 'java'
> >but it must be the ol' memory failure again. 
> 
> Any chance this remembrance is related to playing on 
> Windoze? Or on a Mac? They care for file extensions,
> UNIX does not.
> 
> BTW, someone mentioned the execute bit being set. 
> .class files don't need it, don't set it.
> 
> 
> Peter Hunkeler
> CREDIT SUISSE

Talk about a weirdness. I just checked my "Howdy.java" file, which the
shell attempted to execute and IT DOES NOT HAVE THE EXECUTE BIT ON! The
shell should NOT even attempt to run the file, what is with that? That
is WRONG, WRONG, WRONG!

And if I invoke the BASH shell, I get:

bash: ./Howdy.class: cannot execute binary file

With the tcsh shell, I get:

./Howdy.class: EDC5130I Exec format error.. Binary file not executable.

Hum, sounds like it is time for a little talk with z/OS UNIX shell
programmers.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law.  If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited. 
 

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-24 Thread Steve Comstock

McKown, John wrote:

-Original Message-
From: IBM Mainframe Discussion List 
[mailto:[EMAIL PROTECTED] On Behalf Of Hunkeler Peter (KIUB 34)

Sent: Wednesday, May 24, 2006 1:33 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: A little more insight on the Java strangeness 
I'm encountering





I swear I could run Java classes without saying 'java'
but it must be the ol' memory failure again. 


Any chance this remembrance is related to playing on 
Windoze? Or on a Mac? They care for file extensions,

UNIX does not.

BTW, someone mentioned the execute bit being set. 
.class files don't need it, don't set it.



Peter Hunkeler
CREDIT SUISSE



Talk about a weirdness. I just checked my "Howdy.java" file, which the
shell attempted to execute and IT DOES NOT HAVE THE EXECUTE BIT ON! The
shell should NOT even attempt to run the file, what is with that? That
is WRONG, WRONG, WRONG!


No, it's RIGHT, RIGHT, RIGHT!

As Peter mentioned above, the file does not need the execute
bit set: it is not executable.

What is executable is the JVM. So the "java" command must
have the execute bit set; when you enter:

java Howdy

then the JVM runs and interprets the byte code in Howdy.class.

It all makes {perfect | reasonable} sense.





And if I invoke the BASH shell, I get:

bash: ./Howdy.class: cannot execute binary file

With the tcsh shell, I get:

./Howdy.class: EDC5130I Exec format error.. Binary file not executable.

Hum, sounds like it is time for a little talk with z/OS UNIX shell
programmers.


No. Class files are not executable in the classic sense: they
are interpreted by "java".

Kind regards,

-Steve Comstock

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-24 Thread McKown, John
> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Steve Comstock
> Sent: Wednesday, May 24, 2006 8:13 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: A little more insight on the Java strangeness 
> I'm encountering
> 



> > shell should NOT even attempt to run the file, what is with 
> that? That
> > is WRONG, WRONG, WRONG!
> 
> No, it's RIGHT, RIGHT, RIGHT!

I guess that I was not plain. The standard shell, sh, should not have
even attempted to execute a file that does not have the execute bit on.
But it does try to execute it despite the lack of the execute bit being
on. That is what is WRONG. I agree that the file should not have the
execute bit on. And the javac compiler generates it correctly, without
the execute bit.

> 
> As Peter mentioned above, the file does not need the execute
> bit set: it is not executable.

Agreed.

> 
> What is executable is the JVM. So the "java" command must
> have the execute bit set; when you enter:
> 
> java Howdy
> 
> then the JVM runs and interprets the byte code in Howdy.class.
> 
> It all makes {perfect | reasonable} sense.
> 
> 
> 


> 
> No. Class files are not executable in the classic sense: they
> are interpreted by "java".

Right. That is why the shell, sh, should not have even attempted to
execute the file when you only entered its name on the command prompt.
There is a "bug" in the standard shell, sh, if it tries to execute a
file which does not have the eXecute bit on.

> 
> Kind regards,
> 
> -Steve Comstock

The whole problem stemmed, IMO, from the shell trying to execute a file
which was not marked as executable. This is WRONG. And does not happen
with BASH or tcsh.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law.  If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited. 
 

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-24 Thread Steve Comstock

McKown, John wrote:




shell should NOT even attempt to run the file, what is with 


that? That


is WRONG, WRONG, WRONG!


No, it's RIGHT, RIGHT, RIGHT!



I guess that I was not plain. The standard shell, sh, should not have
even attempted to execute a file that does not have the execute bit on.
But it does try to execute it despite the lack of the execute bit being
on. That is what is WRONG. I agree that the file should not have the
execute bit on. And the javac compiler generates it correctly, without
the execute bit.



Ah, now I see your point. And I agree with it.
Thanks for the extra clarification.

Kind regards,

-Steve Comstock

[snip]

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-25 Thread Hunkeler Peter (KIUB 34)
>shell should NOT even attempt to run the file, what is with 
>that? That is WRONG, WRONG, WRONG!

Here is what I get on z/OS V1.7. I can't get the shell to
execute the java class nor the source file when the X bit is not
set:

A @ S1(z/OS V17) CH.IBM-1148: /u/a $> ls -l Hello*
-rw-r--r--   1 A  OMVSGRP1 425 Mai 24 08:30 HelloWorld.class
-rw-r--r--   1 A  OMVSGRP1 112 Mai 24 08:30 HelloWorld.java

A @ S1(z/OS V17) CH.IBM-1148: /u/a $> HelloWorld.java
HelloWorld.java: cannot execute

A @ S1(z/OS V17) CH.IBM-1148: /u/a $> HelloWorld.class
HelloWorld.class: cannot execute

A @ S1(z/OS V17) CH.IBM-1148: /u/a $> HelloWorld
HelloWorld: FSUM7351 not found

A @ S1(z/OS V17) CH.IBM-1148: /u/a $> ./HelloWorld
./HelloWorld: FSUM7351 not found

A @ S1(z/OS V17) CH.IBM-1148: /u/a $> ./HelloWorld.class
./HelloWorld.class: FSUM9209 cannot execute: reason code = 5b4c0002:
EDC5111I Permission denied.

A @ S1(z/OS V17) CH.IBM-1148: /u/a $> ./HelloWorld.java
./HelloWorld.java: FSUM9209 cannot execute: reason code = 5b4c0002:
EDC5111I Permission denied. 


On what release do you see the wrong behaviour?

Peter Hunkeler
CREDIT SUISSE

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-26 Thread McKown, John
> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Hunkeler Peter (KIUB 34)
> Sent: Friday, May 26, 2006 12:38 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: A little more insight on the Java strangeness 
> I'm encountering
> 
> 
> >shell should NOT even attempt to run the file, what is with 
> >that? That is WRONG, WRONG, WRONG!
> 
> Here is what I get on z/OS V1.7. I can't get the shell to
> execute the java class nor the source file when the X bit is not
> set:
> 
> A @ S1(z/OS V17) CH.IBM-1148: /u/a $> ls -l Hello*
> -rw-r--r--   1 A  OMVSGRP1 425 Mai 24 08:30 HelloWorld.class
> -rw-r--r--   1 A  OMVSGRP1 112 Mai 24 08:30 HelloWorld.java
> 
> A @ S1(z/OS V17) CH.IBM-1148: /u/a $> HelloWorld.java
> HelloWorld.java: cannot execute
> 
> A @ S1(z/OS V17) CH.IBM-1148: /u/a $> HelloWorld.class
> HelloWorld.class: cannot execute
> 
> A @ S1(z/OS V17) CH.IBM-1148: /u/a $> HelloWorld
> HelloWorld: FSUM7351 not found
> 
> A @ S1(z/OS V17) CH.IBM-1148: /u/a $> ./HelloWorld
> ./HelloWorld: FSUM7351 not found
> 
> A @ S1(z/OS V17) CH.IBM-1148: /u/a $> ./HelloWorld.class
> ./HelloWorld.class: FSUM9209 cannot execute: reason code = 5b4c0002:
> EDC5111I Permission denied.
> 
> A @ S1(z/OS V17) CH.IBM-1148: /u/a $> ./HelloWorld.java
> ./HelloWorld.java: FSUM9209 cannot execute: reason code = 5b4c0002:
> EDC5111I Permission denied. 
> 
> 
> On what release do you see the wrong behaviour?
> 
> Peter Hunkeler

Peter,

z/OS 1.6. This may be fixed in a PTF that I don't have on. Or in 1.7.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law.  If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited. 
 

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-26 Thread Jeffrey D. Smith
-Original Message-
From: "Hunkeler Peter (KIUB 34)" <[EMAIL PROTECTED]>
Sent: 5/25/2006 11:38 PM
To: "IBM-MAIN@BAMA.UA.EDU" 
Subject: Re: A little more insight on the Java strangeness I'm encountering




>shell should NOT even attempt to run the file, what is with 
>that? That is WRONG, WRONG, WRONG!

Here is what I get on z/OS V1.7. I can't get the shell to
execute the java class nor the source file when the X bit is not
set:
/snip/

Trying to execute a *.java source file is a non-sequitur. That's
like trying to execute a *.asm or *.c source file.

The java *.class files are interpreted by the java.exe interpreter.
That's why the 'java' command is used and the top level class file
name is specified as a command line argument.

Some command shells may be smart enough to know that a *.class file
is supposed to be passed to the 'java' command program and they
will automatically build the correct command line with the 'java'
command and the class file name. Apparently, the standard command
shell doesn't know how to do that, so the user must explicitly
use the 'java' command to run the class file.

2 cents worth. Your mileage may vary.


Jeffrey D. Smith
Farsight Systems Corporation
24 BURLINGTON DR
LONGMONT, CO 80501
303-774-9381 direct
303-709-8153 cell
303-484-6170 fax

--
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


Re: A little more insight on the Java strangeness I'm encountering

2006-05-29 Thread Hunkeler Peter (KIUB 34)
>z/OS 1.6. This may be fixed in a PTF that I don't have on. Or in 1.7.

John,
I tried on a V1.6 system in the meantime and I've got the same
correct behaviour as on V1.7. Haven't searched PTFs, though.


Peter Hunkeler
CREDIT SUISSE

--
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