HP 1032 ClusterPack V2.4 Tutorial - Page 91

Add pre/post run scripts to specified queues

Get HP 1032 PDF manuals and user guides View all HP 1032 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 91 highlights

PRIORITY = to the queue definition. Queues with higher priority values are searched first during scheduling. After adding, removing or modifying queues, it is necessary to reconfigure LSF to read the new queue information. This is done from the Management Server using the Clusterware Pro V5.1 CLI: % badmin reconfig Verify the queue has been modified by using the Clusterware Pro V5.1 CLI: % bqueues -l References: z 1.8.1 Add new Job Submission Queues z 3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface? Back to Top 1.8.6 Add pre/post run scripts to specified queues The file /share/platform/clusterware/conf/lsbatch//configdir/lsb.queues controls the pre and post commands associated with each queue. The name of your cluster can be determined by using the Clusterware Pro V5.1 CLI: % lsid Pre-execution commands are executed before a job is run from the queue. Post-execution commands are executed when a job successfully completes execution from the queue. This can be useful for acquiring and releasing special resources such as access to hardware devices or software licenses. Note: Application Restart already makes use of these pre and post execution commands. Therefore, AppRS queues cannot have their PRE_EXEC and POST_EXEC values modified. Edit the lsb.queues file and look for PRE_EXEC or POST_EXEC lines for the queue you wish to change. If such lines exist, you can change the values specified. Otherwise, add lines of the form: PRE_EXEC = POST_EXEC =

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
PRIORITY = <integer value>
to the queue definition. Queues with higher priority values are searched first during scheduling.
After adding, removing or modifying queues, it is necessary to reconfigure LSF to read the new
queue information. This is done from the Management Server using the Clusterware Pro V5.1
CLI:
%
badmin reconfig
Verify the queue has been modified by using the Clusterware Pro V5.1 CLI:
%
bqueues -l <queue_name>
References:
1.8.1 Add new Job Submission Queues
3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface?
Back to Top
1.8.6 Add pre/post run scripts to specified queues
The file /share/platform/clusterware/conf/lsbatch/<clustername>/configdir/lsb.queues controls
the pre and post commands associated with each queue.
The name of your cluster can be determined by using the Clusterware Pro V5.1 CLI:
%
lsid
Pre-execution commands are executed before a job is run from the queue. Post-execution
commands are executed when a job successfully completes execution from the queue. This can
be useful for acquiring and releasing special resources such as access to hardware devices or
software licenses.
Note:
Application Restart already makes use of these pre and post execution
commands. Therefore, AppRS queues cannot have their PRE_EXEC and
POST_EXEC values modified.
Edit the lsb.queues file and look for PRE_EXEC or POST_EXEC lines for the queue you wish
to change. If such lines exist, you can change the values specified. Otherwise, add lines of the
form:
PRE_EXEC = <command or full path to a script>
POST_EXEC = <command or full path to a script>