| Previous | TContents | YIndex |
E The SCHEDULE system is controlled via a group of parameters E which are contained in the file SCH0_PARAMETER.DAT, which is created D automatically when the distribution tape is loaded. This is a plain H text file and can be edited with any editor. Typically once setup these $ parameters do not change very often.
G The SCH0_PARAMETER.DAT is the parameter data file for scheduling group E 0. Each of the other 9 potential groups (1 through 9) would have its ? own parameter data file. See the section on Scheduling l groups on Section 2.4.1 for more information on scheduling groups. R F.1 Formatting rules
C The format of the data in the parameter file must follow the below rules.
D IN GENERAL LEAVE THE PARAMETER VALUES BLANK. The default values are ( designed to be acceptable in most cases.
B Once you have changed a parameter value for it to take affect the E server(s) must be restarted. Use the following type of command to do : this. This is best done at a time when the server is idle.
|
" % $ SCHEDULE SERVER RESTART [/CLUSTER] |
N F.2 Database node
D The data files (CONTROL, QUEUE, HISTORY) can be on any node in your C cluster or network. The below parameter indicates on what node. By " default it is on the current node.
|
" DATABASE_NODE = node_name DATABASE_NODE = CLSTR |
@ If the node is in the current cluster and is locally accessible H ordinary RMS operations are used to read/write the data. If the node is F on a remote node then the I/O requests are routed over the network to the SERVER process on that node. T F.3 Cluster parameters
D The cluster parameters define what the VMS system considers to be a C management unit. (e.g. a cluster with disks, tapes, queue data and E authorization files shared). If these parameters are left blank then - the configuration will be picked up from VMS.
A The Alias is the "cluster alias" defined in the NCP database. If F defined it appears in the logical name SYS_$CLUSTER_NODE. If you have F not defined such an alias then the current node name from the logical C SYS_$NODE is used. If an alias is not defined it is a good idea to H define an alias name here but it is not required. The alias define here is used only internally.
|
" CLUSTER_ALIAS = node_name CLUSTER_ALIAS = CLSTR |
C In a cluster all resource locks are usually shared but if you have E logically (but not physically) partitioned your cluster (e.g. common G HSC, separate disks, separate queues, separate authorization files) it E is important that all these cluster parameters be different for each E partition. Each partition should have a different lock group letter, alias and list of members.
|
" % CLUSTER_LOCK_GROUP = a single letter CLUSTER_LOCK_GROUP = A |
| Previous | VNext | TContents | YIndex |