PLY_SCD VSCHED_E05B021 POLYCENTER Scheduler V2.1B VAX ECO Summary
Copyright (c) Digital Equipment Corporation 1995. All rights reserved.
PRODUCT: POLYCENTER Scheduler OpenVMS
OP/SYS: OpenVMS VAX
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VSCHED_E05B021
ECO Kits Superseded by This ECO Kit: None
ECO Kit Size: Saveset A - 7,830 Blocks
Saveset B - 9,558 Blocks
Saveset C - 1,746 Blocks
Cover Letter - 5 Blocks
Total of 4 files - 19,139 Blocks
Kit Applies To: POLYCENTER Scheduler V2.1B
OpenVMS VAX V5.5-2, V5.5-2H4, V6.0, V6.1, V6.2
NOTE: This ECO is the complete POLYCENTER
Scheduler V2.1B product. POLYCENTER
Scheduler V2.1B does not need to be
installed prior to installing this
ECO. However, a valid POLYCENTER
Scheduler license must be installed.
The product version will be V2.1B-05
after installing this ECO.
System Reboot Necessary: No
ECO KIT SUMMARY:
An ECO kit exists for POLYCENTER Scheduler V2.1B on OpenVMS VAX
V5.5-2 through V6.2. This kit addresses the following problems:
Problems addressed in the VSCHED_E05B021 Kit:
o When a large number of job failures occur, the system logical
table could become full. This would prevent job failure
notification from being sent.
o When installing Scheduler in a mixed-architecture cluster,
an error occurred during the startup procedure when the
procedure could not find the shareable run time library file
SCHED_RTL.EXE. The startup procedure now runs correctly.
o The Scheduler command SHOW JOB/SYMBOLS displayed a large
decimal number instead of a blank space for SCHED$SJOB and
SCHED$TJOB, when no SJOB or TJOB had been specified.
Scheduler now correctly displays a blank space.
o Schedule Set Fiscal_Year would be off by one week if the
/Start_Date qualifier was used to modify the base date.
o Scheduler failed to send a warning message to mail distribution
lists when a job's specified max time was exceeded.
o Scheduler database was not validated after a reboot. The
database is now always validated upon reboot.
o A job with multiple dependencies could be stuck in a scheduled
state and never run if one of the predecessor jobs was set with
/noretain and the dependent job was restricted to a cluster node
that was not the default executor.
o The Scheduler command SHOW JOB node"username"::job-specifier
would not work if the user name specified was not the same as
the default proxy user name. The command now works properly.
o In earlier versions of Scheduler, wide area network support was
set up manually. The Scheduler installation procedure now
automatically sets up wide area network support for DECnet
phase IV or phase V. The installation procedure determines
which you are running, and sets up the appropriate wide area
network support.
Problems addressed in the VSCHED_E01B021 kit:
o In POLYCENTER Scheduler V2.1B-1, jobs scheduled using fiscal month
intervals were incorrectly scheduled to run a day earlier than
expected. For example, /INTERVAL=FMD2 scheduled the job to run on
26 February, rather than 27 February.
o When multiple jobs on two separate clusters were all dependent on
the same job running on a remote node, the dependent jobs on the
two clusters would run multiple times because the jobs would
receive multiple completion messages from the job on which they
depend. This would occur when commands to synchronize the jobs on
one cluster were interspersed with commands to synchronize the jobs
on the other cluster.
o If a batch mode job was set to run on a queue that was not on the
default node and the default node did not have any job slots
available, the job would go into a wait state. If the target node
had no job slots available but the default node did, the job would
run.
POLYCENTER Scheduler now correctly checks the job count and job max
for the node on which the requested batch queue resides. If any of
the following conditions occur, POLYCENTER Scheduler will assume
there are slots available and attempt to submit the job:
+ The queue is a generic queue
+ The queue is stopped or unavailable
+ The queue is not a batch queue
The job will then fail because of the condition and the job failure
will be handled as specified when the job was created or modified.
o The command SCHED SHOW JOBS jobnumber/STATUS=job returned the
following error instead of the job's status information:
%NSCHED-F-JOBSNOTFND, No jobs specified were found
o The COPY command did not copy the identifiers RDID, EXID, and WRID
to the new job.
o If a remote job failed before the job started running, the
graphical interface did not display the failure. For example,
this may occur if the agent on which the job should run was down.
o Using more than 32 remote child dependencies caused the error
message "%PAS-F-STRASGLEN, string assignment length error" when
the command SHOW JOB/FULL or DELETE was issued.
o The latest SBQUEUE.COM has been included in this ECO kit.
INSTALLATION NOTES:
The system/cluster does not need to be rebooted after this kit is
installed. However, the POLYCENTER Scheduler should be shutdown and
restarted in order for all kit changes to take effect.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vsched_e01b021.README
vsched_e05b021.CHKSUM
vsched_e05b021.CVRLET_TXT
vsched_e05b021.a-dcx_vaxexe
vsched_e05b021.b-dcx_vaxexe
vsched_e05b021.c-dcx_vaxexe
|
