This option consists of three Blocks:
Field | Type & Length |
Description |
---|---|---|
Password Retention | N2 | Number of days before a user should be forced to change their Oracle password to be used on a system wide basis. This may be overridden in a per user fashion via option {USERS-5b1}. |
Maximum Number of Login Tries per User | N2 | The maximum number of times a user is allowed to try to log in. |
Maximum Number of Entries per Queue | N5 | This is the limit set for the number of entries that may be submitted to the batch processing module for any one queue. |
Maximum Number of Entries in All Queues | N5 | This is the limit set for the number of entries allowed in all queues. |
Total Number of Immediate Batch Jobs Allowed in the System | N2 | The total number of immediate batch jobs in the queue may have a serious impact on system resources: this value may aid in the control of the resources. |
Number of Days after which Completed/Cancelled Requests will be Deleted | N6 | {BATCH-6} will delete all completed / cancelled requests after the number of days specified here have expired. |
Directory for Output Files | A30 | This is the default directory where all output files are to be stored, if there are no entries in {USERS-4}. |
|
Field | Type & Length |
Description |
---|---|---|
Queue Code | A2 | A unique code for each queue must be assigned here. |
Queue Description | A40 | The name of the queue is entered here. |
Is the Queue | Opened / Closed | An indicator as to whether the queue is Open or Closed. |
Number of Queue Processes Allowed | N2 | Normally a 1 will be entered here to assign one queue processor per queue. It is, however, possible to increase this number: this allows more than one queue processor per queue to be activated simultaneously when the queue is opened. |
Command to Use when Submitting Immediate Batch Jobs | Nohup/Batch | A (N)ohup will use the "nohup" command when immediate batch requests are submitted: a (B)atch will use the "Batch" command. Remember that certain UNIX pre-requisites must be met before the "batch" command can be widely used. |
Maximum Number of Immediate Batch Jobs Allowed in this Queue | N2 | This is the maximum number of jobs that can be submitted for immediate batch processing in the queue specified in A above. |
The Number of Seconds the Queue must wait before Checking for More Jobs | N5 | While a queue processor is running, it could finish one request and find that there are no more requests to be processed by the queue. If the automatic termination is set to (N), then the queue processor will wait for the number of seconds specified here before attempting to find a request that it can process. |
Must the Queue Terminate and Close if No More Jobs | (Y/N) | If this field is set to (Y)es, the queue processor will terminate when no more requests can be found for the queue. The last queue processor in a queue will then close the queue. |
Directory for Saving Job Output | A30 | This is the full absolute directory name, starting with a "/", where the output of jobs from this queue will be saved. |
|
Field | Type & Length |
Description |
---|---|---|
Day Number | N1 | The number of the day for which the user wishes to enter start and end times, starting with Sunday as Day 1. If no record exists for a given day, this will mean that no limitation exists for that day. The name of the day will be displayed. |
Start Time | N4 | This is the start time when Immediate Batch Jobs may be submitted, e.g. 1300 for 1 p.m. |
End Time | N4 | This is the end time after which no more Immediate Batch Jobs may be submitted. |
|
Processing Rules |
|
---|---|
No special processing rules. |
Date | System Version | By Whom | Job | Description |
---|---|---|---|---|
12-Dec-2006 | v01.0.0.0 | Charlene van der Schyff | t134783 | New manual format. |
10-Mar-2008 | v01.0.0.0 | Vaughn Dumas | t134783 | System owner proof read. |
11-Sep-2008 | v01.0.0.0 | Charlene van der Schyff | t152060 | Edit language obtained from proof read language Juliet Gillies. |