Ricoh InfoPrint Pro C900AFP InfoPrint Manager - Page 152

Monitoring file system use (automatically), Queries to Prevent

Page 152 highlights

in the commands that are generated to run the exit program. For example, %s is equivalent to server name and %t is equivalent to threshold value. If a particular exit attribute contains a value of memprob %s in the server server1, then when InfoPrint invokes the memory usage shell script it passes server1 as the first argument. For example, a shell script named uplimit might: 1. Prevent new jobs from arriving at a logical destination by disabling that InfoPrint object. 2. Prevent the listing of jobs so that queries of the current backlog do not add to the memory constraints. 3. Ensure that any actual destinations (in this case, the three pooled actual destinations named adn) are re-enabled, so that they can reduce any backlog of jobs that could be causing the problem. The uplimit script might look like this: #!/bin/ksh pddisable prt1-ld pdset -cserv -xdisallow-list-obj-class=job server1 pdenable ad1 ad2 ad3 The lowlimit script might look like this: 1. Re-enable the logical destination so that new jobs are being accepted. 2. Reset the server to allow the listing of job queries. The lowlimit script might look like this: #!/bin/ksh pdenable prt1-ld pdset -cserv -xdisallow-list-obj-class== server1 Note: You can use the Queries to Prevent section on the Memory Usage page to both add and remove the listing of any queries against a specified InfoPrint object, such as Jobs. The Jobs object is the most useful to restrict, but this should be done cautiously, because once it has been set, you cannot query any jobs from either the InfoPrint Manager Administration Interface or the InfoPrint Manager Operations GUI. Note that if the shell scripts or programs are not in the system path, you must specify the fully qualified path for the shell scripts that you have customized. If you misspell a shell script name or refer to a file that does not exist, InfoPrint lets you change the setting. For more information about the lower-memory-usagethreshold, lower-memory-usage-exit, upper-memory-usage-threshold, and upper-memory-usage-exit server attributes that support this feature, see InfoPrint Manager: Reference. Once you have selected the appropriate values, click OK to apply this change and close the Server Properties dialog. Monitoring file system use (automatically) InfoPrint Manager includes support to help you monitor file system usage. The InfoPrint Manager server polls these critical file systems at regularly scheduled intervals, and it increases the polling as the usage increases. Initially, the file system is polled for usage every 16 minutes. Here is the polling schedule: 138 InfoPrint Manager for AIX: Procedures

  • 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
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418

in the commands that are generated to run the exit program. For example,
%s
is
equivalent to
server name
and
%t
is equivalent to
threshold value
. If a particular exit
attribute contains a value of
memprob %s
in the server
server1
, then when InfoPrint
invokes the memory usage shell script it passes
server1
as the first argument.
For example, a shell script named
uplimit
might:
1.
Prevent new jobs from arriving at a logical destination by disabling that
InfoPrint object.
2.
Prevent the listing of jobs so that queries of the current backlog do not add to
the memory constraints.
3.
Ensure that any actual destinations (in this case, the three pooled actual
destinations named
ad
n
) are re-enabled, so that they can reduce any backlog of
jobs that could be causing the problem.
The
uplimit
script might look like this:
#!/bin/ksh
pddisable prt1-ld
pdset -cserv -xdisallow-list-obj-class=job server1
pdenable ad1 ad2 ad3
The
lowlimit
script might look like this:
1.
Re-enable the logical destination so that new jobs are being accepted.
2.
Reset the server to allow the listing of job queries.
The
lowlimit
script might look like this:
#!/bin/ksh
pdenable prt1-ld
pdset -cserv -xdisallow-list-obj-class== server1
Note:
You can use the
Queries to Prevent
section on the
Memory Usage
page to
both add and remove the listing of any queries against a specified InfoPrint object,
such as
Jobs
. The
Jobs
object is the most useful to restrict, but this should be done
cautiously, because once it has been set, you cannot query any jobs from either the
InfoPrint Manager Administration Interface or the InfoPrint Manager Operations
GUI.
Note that if the shell scripts or programs are not in the system path, you must
specify the fully qualified path for the shell scripts that you have customized. If
you misspell a shell script name or refer to a file that does not exist, InfoPrint lets
you change the setting. For more information about the
lower-memory-usage-
threshold
,
lower-memory-usage-exit
,
upper-memory-usage-threshold
, and
upper-memory-usage-exit
server attributes that support this feature, see
InfoPrint
Manager: Reference
.
Once you have selected the appropriate values, click
OK
to apply this change and
close the
Server Properties
dialog.
Monitoring file system use (automatically)
InfoPrint Manager includes support to help you monitor file system usage. The
InfoPrint Manager server polls these critical file systems at regularly scheduled
intervals, and it increases the polling as the usage increases. Initially, the file
system is polled for usage every 16 minutes.
Here is the polling schedule:
138
InfoPrint Manager for AIX: Procedures