| Summary: | Generic job configuration/launching | ||
|---|---|---|---|
| Product: | [Tools] PTP | Reporter: | Dave Hudak <dhudak> |
| Component: | Launch | Assignee: | Project Inbox <ptp-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | arossi |
| Version: | 4.0.6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Dave Hudak
Dave, I'm not sure what you are asking for here. 1. If you are referring to PBS 4.0.6, tbat is no longer supported; it has been deprecated for the JAXB PBS. 2. The generic batch PBS (JAXB) supports the uploading and use of custom batch scripts (the third tab). These are not edited in the windows/widgets, though. The procedure is: a. import the script into your workspace b. open it in a normal editor, change it c. open the launch configuration (Run Configuration), choose the third tab for the PBS Generic Batch RM, select the script from the workspace. 3. If you mean, however, something like uploading the batch script, and having it automatically "parsed" into widgets displaying job name, account, etc., that is not currently supported. It is sort of like managed vs makefile builds. Either you use one or the other. 4. You can always create your own Resource Manager to support the third-party software, building into it the commands and the batch script necessary. Then the users could just use the UI that you give them through the configuration you have designed in the xml. There already is functionality to import batch scripts for PBS jobs. If this is not sufficient, please reopen the bug. |