Opened 11 years ago
Closed 7 years ago
#721 closed enhancement (invalid)
IZ3144: Array job using multiple job scripts
Reported by: | maritac | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.2u3 |
Severity: | minor | Keywords: | execution |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=3144]
Issue #: 3144 Platform: All Reporter: maritac (maritac) Component: gridengine OS: All Subcomponent: execution Version: 6.2u3 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: pollinger (pollinger) QA Contact: pollinger URL: * Summary: Array job using multiple job scripts Status whiteboard: Attachments: Issue 3144 blocks: Votes for issue 3144: Opened: Wed Sep 30 11:32:00 -0700 2009 ------------------------ I have an SGE user who has asked me to enter an enhancement request for the ability to chain multiple jobs scripts together to form an array with one jobid number. This would be different from the current form of array job, which submits one job script the designated number of times. ------- Additional comments from reuti Thu Oct 1 04:43:42 -0700 2009 ------- What is the detail beind it: to run two or more scripts with the index 1..n or ignoring the index completely and having the ability to group the jobscripts together for easier handling? On the one hand you can have it right now with a selector.sh script like: #!/bin/sh eval SCRIPT="$"$SGE_TASK_ID if [ ! -r "$SCRIPT" -o ! -x "$SCRIPT" ]; then echo "Can execute script $SCRIPT, step aborted" exit -1 fi exec $SCRIPT to submit with: qsub -t 1-3 selector.sh script1.sh script2.sh script3.sh If you want to group jobs together and ignore the index, you may find this RFE interesting: http://gridengine.sunsource.net/issues/show_bug.cgi?id=2943 ------- Additional comments from petrik Mon Oct 5 05:15:37 -0700 2009 ------- I agree with Reuti. It's easily possible right now. Unless you can provide an interesting usecase I'd suggest to close this request. Can you ask your SGE user if Reuti's solution is what he wanted?
Change History (1)
comment:1 Changed 7 years ago by dlove
- Resolution set to invalid
- Severity set to minor
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
See also the array job howto.