giltjr
Thanks for the nice reply I really appreciate it, I see that I have a lot to learn about this sort of thing.
I'll keep the question open for a little bit to see if I can get any more info.
Thanks again
Main Topics
Browse All TopicsHi Experts
I need to have a java program run on a z/OS mainframe and do the following things:
1. Create a new directory and write a new file into that directory.
2. Call an external (external to the JVM) application to act on that file,
3. Delete the created directory and its content.
The code to do this is simple enough, use File.mkdir() method to create a new directory. Create a new FileOutputStream and write to create a new file.
Use the Runtime.exec method to run the application.
Then use File.delete() to remove the files.
I have the code written to do this and have tested it on a Unix and Windows system and all works fine. I haven’t been able to test it yet on the mainframe (political reasons). A java mainframe person here gave me the following warnings about running this code on the mainframe:
1. The code makes explicit references to the file system. File system access is not as straight-forward on MVS as it is on Unix.
2. The code issues an operating system command. Once again, MVS does not honor program invocations in the manner that Unix does.
He didn’t give me any further information about this and hasn’t elaborated any more on it either. Does anyone with knowledge about such things have any information about what is different about the way Z/OS handles file system operations. And why the Runtime.exec() method may not work in this environment?
Thanks
Dave
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>> The code makes explicit references to the file system.
Put the file path in a properties-file in the same directory as your application, and read it from the properties-file on start-up. This allows you to change the file path on subsequent runs of the program on different systems by just changing the text in the properties-file and not re-compiling the source-code.
http://www.exampledepot.co
Business Accounts
Answer for Membership
by: giltjrPosted on 2007-03-20 at 19:42:32ID: 18761295
Well, I have not run written any Java applications, but there could be some "misunderstanding" here.
z/OS has a 'split' personality. It has the traditional "MVS" side and the "OMVS" (Open MVS also called Unix System Services) side.
Each of the sides have their own files systems. The MVS is is not really like anything you are use to. However the OMVS side is just like Unix. If you are running your Java application under the OMVS side it should pretty much run like it would under Unix. z/OS (the OMVS part) is branded Unix by the Open Unix Group and is POSIX compliant).
Now if you were to try and run this on the "MVS" side, which I am not even sure you can, you would have some issues.
To make it a bit more confusing MVS has a file type called PDS (and PDSE) meaning a partitioned data set (PDSE is just extended). A PDS is basically a collection of small sequential files, normally related, called members. These are stored in a single file with a "directory" that contains information about each member. It is NOTHING like a directory in the Unix side.
So your Java mainframe guy may be referring to the MVS side of z/OS as the file handles are much different when you access MVS files instead of OMVS files.