- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Limit to DCL parameter string size for Java Runtim...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2010 04:59 AM
тАО07-02-2010 04:59 AM
Limit to DCL parameter string size for Java Runtime.exec()
package XXX.filerelease;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import org.apache.log4j.Logger;
public class FileReleaseVmsImpl implements FileReleaseIntf{
private String DUMMYEMAIL = "\"Test@test.com\"";
public String searchForFiles(FileReferenceVmsImpl fileReference) {
String result = "";
String command = "findme.com"
+ " " + DUMMYEMAIL
+ " " + fileReference.getFormattedDateString()
+ " " + fileReference.getBatch()
+ " " + fileReference.getSequence();
Runtime run = Runtime.getRuntime();
Process pr;
try {
pr = run.exec(command);
BufferedReader buf = new BufferedReader(new InputStreamReader(pr.getInputStream()));
String line = "";
while ((line = buf.readLine()) != null) {
result += line + "\n";
}
} catch (IOException e) {
result = MHConstants.FILE_RELEASE_SEARCH_FOR_FILES_VMS_ERROR;
return (result);
}
return result;
}
}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2010 05:21 AM
тАО07-02-2010 05:21 AM
Re: Limit to DCL parameter string size for Java Runtime.exec()
>> I have noticed that it fails for parameter strings longer than
>> roughly 215 characters.
What error message are you getting ?
Discussion on a similar problem -
http://unix.derkeiler.com/Newsgroups/comp.os.vms/2004-12/1375.html
Regards,
Murali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2010 05:30 AM
тАО07-02-2010 05:30 AM
Re: Limit to DCL parameter string size for Java Runtime.exec()
%DCL-W-NOLBLS, label ignored - use only within command procedures
\_MBA26400:\
%DCL-W-NOCOMD, no command on line - reenter with alphabetic first character
Actually, I am using a dcl wrapper file as described here : http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1434352
to invoke a second .com file. The wrapper .com file does not get invoked because the DCL command string is too long. Once it is shortened a little, the wrapper is called correctly and all works fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2010 05:38 AM
тАО07-02-2010 05:38 AM
Re: Limit to DCL parameter string size for Java Runtime.exec()
Looks like the logical "JAVA$ENABLE_ENVIRONMENT_EXPANSION" might
help solve your problem.
Refer the following link -
http://sh.ncsd.k12.ca.us/java-docs/release_notes.html#javaenableenvironmentexp
-> Section "Using JAVA$ENABLE_ENVIRONMENT_EXPANSION"
Check if this is applicable in your case.
Hope this helps.
Regards,
Murali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2010 06:46 AM
тАО07-02-2010 06:46 AM
Re: Limit to DCL parameter string size for Java Runtime.exec()
$ define/job JAVA$EXEC_TRACE true
give you some insight? If that has no effect, you may want to try
$ set verify
before starting Java.
As already implicitly explained, java passes the command string to the spawned process via a mailbox. But before invoking your wrapper command file, there are Java generated define-commands for some process permanent files. With one of these settings you should be able to see them.
You may get some insight in how the mailbox is used and whether that is the same mailbox you see in the error message.