EnterpriseSCHEDULE
Installation Notes
6.6 Version 7.1.27 corrections
- SCHEDULE v7.1.27
Problem: The SPISHR image on VAX VMS 7.1 does not match the one linked
with. Solution: A version has been put on this FTP site that does not
require the SPISHR.EXE image.
6.7 Version 7.1.26 corrections
- SCHEDULE V7.1.26 - 8308
Problem: Value of a newly created variable not displayed correctly in
the property page when it is the first expression variable displayed.
Solution: Fixed.
- SCHEDULE V7.1.26 - 8310
Problem: The UTC timestamp written in the event file was not the
correct time on Windows and some UNIXes. Also, event file notify option
added for OpenVMS and Unix/Linux. Solution: fixed.
6.8 Version 7.1.24 corrections
- SCHEDULE V7.1.24 - 8279
Problem: The GUI was displaying an error message if a user had no home
directory and the user had not enough rights to create a directory at
the top level. Solution: Case corrected.
- SCHEDULE V7.1.24 - 8280
Problem: GUI sometimes not displaying correctly jobs in layouts when IP
addresses are used in job connections, when DNS server are not set.
Solution: Case corrected.
- SCHEDULE V7.1.24 - 8286
Problem: variables from the folder [sys] added to the variable dropdown
menus. Solution: Added set of predefined useful date variables.
- SCHEDULE V7.1.24 - 8291
Problem: Lots of error messages sometimes displayed when connecting to
a server with lots of jobs in its queues. Solution: Corrected Gui
interaction with server at Gui start-up.
- SCHEDULE V7.1.24 - 8273
Problem: The server parameter ROOT_DIR_PROTECTION only allowed a zero
value. Solution: Parameter file processing case corrected.
- SCHEDULE V7.1.24 - 8282
Problem: VMS server sometimes sets Unix/Windows servers as having
"Decnet" connections, causing communications between the VMS and
Unix/Windows machine to hang. Solution: Network connection protocol
case corrected.
6.9 Version 7.1.22 corrections
- SCHEDULE V7.1.22 - 8259
Problem: Use of FORMAT="FF-MMMM-YYYY" in a variable that is then used
in a preprocess substitution statement did not produce the expect
result. Solution: Preprocessing case corrected.
- SCHEDULE V7.1.22 - 8255
Problem: Format expressions used inside a variable of the form
FORMAT="QQFF" when put into the commands was replaced with what appears
as another random incorrect set of digits. Solution: Preprocessing case
corrected.
- SCHEDULE V7.1.22 - 8257
Problem: When using an expression variable inside a job the
preprocessing would fail if the same variable was referenced more than
once. This resulted in invalid text in the job. Solution: Preprocessing
case corrected.
- SCHEDULE V7.1.22 - 8268
Problem: GUI taking a long time to start when a cluster member is down
Solution: GUI improved to detect this case
- SCHEDULE V7.1.22 - 8258
Problem: when connecting to remote servers the GUI was automatically
filling the remote username with the local username when no proxy was
present. Solution: username is left blank for non-Windows servers.
- SCHEDULE V7.1.22 - 8260
Problem: On a system where a DNS server is not available each client
connection results in a wait / timeout occurring. Solution: This lookup
can now be turned off by setting the parameter DISALBE_DNS_LOOKUP to a
1.
- SCHEDULE V7.1.22 - 8262
Problem: During installation and any time the Schedule_Start.com
procedure was used to load a PAS the resultant Sch0_License.dat file
was incorrectly formatted: Solution: This has been fixed.
- SCHEDULE V7.1.22 - 8265
Problem: gethostbyname error displayed in the server log file when
using a descriptive name when connecting with the GUI. Solution: fixed.
- SCHEDULE V7.1.22 - 8253
Problem: Sometimes a line is missing from the log file output when
using the GUI's "view log" feature. Solution: This has been fixed.
- SCHEDULE V7.1.22 - 8267
Problem: username/password asked several times for same node when using
resetproxy Solution: Fixed
- SCHEDULE V7.1.22 - 8210
Problem: When a job's initiate is invalid, the job will submit in an
infinite loop. Solution: This has been fixed.
- SCHEDULE V7.1.22 - 8269
Problem: GUI sometimes automatically reconnects to server when manually
disconnected Solution: Fixed
- SCHEDULE V7.1.22 - 8220
Problem: parameters in the GUI shortcut are not picked if there is no
blank between them. Solution: Fixed.
- SCHEDULE V7.1.22 - 8231
Problem: Server sometimes does not restart when the group number is not
zero. Solution: This has been fixed.
- SCHEDULE V7.1.22 - 8247
Problem: rename/dir sometimes doesn't work correctly in the embedded
command line client. Solution: fixed
- SCHEDULE V7.1.22 - 8248
Problem: rename/dir sometimes doesn't copy correctly everything.
Solution: fixed
- SCHEDULE V7.1.22 - 7482
Problem: schedule prompt -group doesn't connect to group 0 when no
answer is given but to the group defined in SCHEDULE_GROUP_NUMBER
Solution: Fixed.
- SCHEDULE V7.1.22 - 8266
Problem: problems when IP addresses are present in layouts and no DNS
present Solution: Fixed
- SCHEDULE V7.1.22 - 8254
Problem: Cannot easily tell how many monitor events are present in a
display windows. Solution: The title information has been expanded to
include the number of entries.
6.10 Version 7.1.20 corrections
- SCHEDULE V7.1.20
Problem: Events were not received correctly in Windows client.
Solution: Fixed problems when using a descriptive name to connect to a
server
- SCHEDULE V7.1.20
Problem: The folder name with same name as the server name does not
display in the explorer view when no DNS server present. Solution: Fixed
- SCHEDULE V7.1.20
Problem: Password was asked twice when connecting to a server with
"prompt_always" parameter set in Windows Client. Solution: Fixed
- SCHEDULE V7.1.20
Problem: Limit to menu items in Prototype menu in Windows client.
Solution: Increase the maximum entries which can be displayed in the
prototypes menu from 100 to 500.
- SCHEDULE V7.1.20
Problem: Reset_proxy option was not working for usernames containing
the character '.' Solution: Fixed
- SCHEDULE V7.1.20
Problem: The job function "Complete" for workgroups jobs not working
correctly. For this function to work correctly v7.1.20 of the server is
needed. Solution: Fixed
- SCHEDULE V7.1.20 - 8250
Problem: A "Complete" request for a workgroup job causes a job to
submit rather than just a status change. Solution: Fixed
- SCHEDULE V7.1.20 -8249
Problem: When a job is submitted with the "/after" qualifier,downstream
jobs fail with "Execution window exceeded". Solution: Fixed
- SCHEDULE V7.1.20 - 8236
Problem: The command "submit/noprerequisite does not work with a
rescheduled job that has a start time set. Solution: Fixed
- SCHEDULE V7.1.20 - 8235
Problem: The command "submit/noprereq" does not work with workgroups
disabled. Solution: Fixed
- SCHEDULE V7.1.20
Problem: The command "schedule monitor/type=*" can cause an access
violation in the server when a workgroup master changes. Solution: Fixed
6.11 Version 7.1.18 corrections
- SCHEDULE V7.1.18 - 7276
Problem: When a user changes the primary server a message is displayed
to give him the possibility to automatically restart the GUI with the
chosen server as primary. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7451
Problem: When creating shapes in the layout, a default size is now
defined so that users can creat objects by just clicking once in the
layout. Solution: This has been implemented.
- SCHEDULE V7.1.18 - 7003
Problem: The Type field of an access record (User, Group, Proxy, etc.)
should not normally be modified by a user. A confirmation dialog has
been added to verify the user's intention. Solution: This has been
implemented.
- SCHEDULE V7.1.18 - 7413
Problem: Demos not loading correctly when the descriptive name is
different of the netowrk name. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7401
Problem: Job fails with 196 when the owner does not have enough
permission to the temporary job files. This code fix ensures that the
user running a job has read+execute access to the job script, and
read+write access to the job's log file. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7340
Problem: The GUI refuses to connect to a node that was previously
connected, saying that the node is already in use. Solution: This has
been fixed.
- SCHEDULE V7.1.18 - 7312
Problem: The error message displayed when modifying a job whose submit
node is unreachable does not point to the real error condition.
Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7631
Problem: Stack trace on HP prints in infinite loop. Solution: This has
been fixed.
- SCHEDULE V7.1.18 - 7630
Problem: Error logging in server dump command's "NRQ open list" was
incorrect on Windows. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7629
Problem: A wildcard modity command will stop making changes when in
encounters a not reachable node in a job definition. Solution: A
command line option "/ignore_errors" has been added. This has been
implemented.
- SCHEDULE V7.1.18 - 7628
Problem: Access violations are not properly logged on Windows
platforms. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7620
Problem: The GUI gets access violation when a non-administrator user
was trying to register the GUI. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 8198
Problem: When a workgroup master changes because the power setting for
a member changed, the set id values assigned to jobs might overlap with
prevously assigned set id values from the old master. Solution: This
has been fixed.
- SCHEDULE V7.1.18 - 7285
Problem: The GUI hangs when opening layouts that contain jobs on
unreachable machines. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7454
Problem: Can't paste into layout text objects using CTRL-V shortcut.
Solution: This has been implemented.
- SCHEDULE V7.1.18 - 7275
Problem: The message "Failed to apply changes" was displayed when users
selected cancel in the dialog "The data in the database has changed
since..." when modifying jobs and other data. Solution: This has been
fixed.
- SCHEDULE V7.1.18 - 7208
Problem: The embedded command line client does not work when using the
command "help mod job qualifiers". Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7205
Problem: The "Open a new monitor for this job" option in the Job Wizard
does not work. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7195
Problem: Renaming an initiated job was emtpying the initiate condition
when there was one. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7186
Problem: There is no description for the EnterpriseSCHEDULE service on
the windows service control panel. Solution: This has been added.
- SCHEDULE V7.1.18 - 7162
Problem: Variables created in the GUI had <CR>/<LF>
characters at the end and were not displayed correctly. Solution: This
has been fixed.
- SCHEDULE V7.1.18 - 7146
Problem: The display of the type/queue command in the embedded command
line client was incorrect. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7144
Problem: The embedded command line client does not display the help
text correctly. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7126
Problem: There is a synax error in the FTP prototype job. Solution:
This has been fixed.
- SCHEDULE V7.1.18 - 7053
Problem: The GUI connection timeout can not be changed. Solution: The
timeout value can now be changed in the CTRL-SHIFT-F6 window. This has
been implmeneted.
- SCHEDULE V7.1.18 - 7032
Problem: GUI was still connecting to the previously given group when
the retry box was displayed and another group was specified. Solution:
This has been fixed.
- SCHEDULE V7.1.18 - 7618
Problem: Default job protection settings made default job not
accessible. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7645
Problem: When the GUI reconnects to a server, duplicate events
sometimes appear in the monitor. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 8193
Problem: The "NRQ histogram" debug setting does not produce output.
Solution: This has been fixed.
- SCHEDULE V7.1.18 - 8192
Problem: The "NRQ average rate" displayed in server info is not
correct. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 8190
Problem: Clients do not receive O queue event messages. Solution: This
has been fixed.
- SCHEDULE V7.1.18 - 8189
Problem: The database appears to be corrupt when the DATABASE_ROOT
parameter is used. Solution: Disabling the job cache is a workaround on
broken versions of the server. This has been fixed in 7.1.17.
- SCHEDULE V7.1.18 - 8188
Problem: Failover and Least-busy workgroups sometimes skip job runs
when the clocks on workgroup members are not synchronized. Solution:
This has been fixed.
- SCHEDULE V7.1.18 - 8186
Problem: The GUI is not able to resume VMS jobs on hold in the L queue
without restarting. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 8178
Problem: The GUI does not handle a node descriptive name that is the
same as a Schedule folder name. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 8174
Problem: Network connectivity is erratic when decnet is unavailable.
Solution: This has been fixed.
- SCHEDULE V7.1.18 - 8155
Problem: The server database cache becomes corrupt when DATABASE_ROOT
is defined in the parameter file. The problem is present on Windows and
Unix platforms. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7414
Problem: The embedded command line client was not handling large
amounts of data correctly. For example, when using the type/hist or
type/queue commands. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7649
Problem: GUI receives error when using the options "Insert job" or
"Insert variable" in the layout. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7456
Problem: Unnecessarly text displayed at the bottom of the calendar in
the GUI. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7485
Problem: Layouts do not open correctly when remote connection is of the
form "\\nodename\..\jobname". Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7457
Problem: The GUI does not resize the calendar properly. Solution: This
has been fixed.
- SCHEDULE V7.1.18 - 7476
Problem: Jobs still submit when excecution window is exceeded.
Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7478
Problem: Busy cluster environments can cause latency between multiple
nodes within queue cache system. End result occasionally job completion
events dont match-up to job prerequisite events. This is fixed by
controlling the 2 events on the same node. Solution: This has been
fixed.
- SCHEDULE V7.1.18 - 7660
Problem: The error "Internal error: Queue get-free failed" can cause
jobs to stop submitting. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7483
Problem: The "Properties" option is not always the bottom entry in the
GUI right-click menu. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7495
Problem: Server receives an access violation when clients are receiving
monitor events. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7530
Problem: Jobs that run csh on unix platforms fail with "syntax error:
'if' unmatched". Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7635
Problem: Replication uses 100% cpu time in certain error cases.
Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7639
Problem: The /symbol command qualifier was not documented for some
commands. Solution: This has been fixed.
- SCHEDULE V7.1.18 - 7303
Problem: The type/queue command does not display the number of entries
in each queue state. Solution: This has been implemented.
- SCHEDULE V7.1.18 - 7661
New Feature: The server should deliver a message to clients when a
workgroup master changes. Solution: This has been implemented.
- SCHEDULE V7.1.18 - 7634
New Feature: The primary node is not displayed to the GUI title bar.
Solution: This has been implemented.
- SCHEDULE V7.1.18 - 7177
Problem: It is not possible to set the server debug flags in the GUI.
Solution: This has been implemented.
- SCHEDULE V7.1.18 - 8191
New Feature: When schedule runs standalone, but the machine it is
running on is a VMS cluster member, superfluous messages are sent to
other cluster members. This messaging should be disabled. Solution:
This has been implemented via the DISABLE_CLUSTER parameter file value.
- SCHEDULE V7.1.18 - 7458
Problem: GUI needs a shortcut to create prerequisites in the layout.
When creating job connections in the layout, create a prerequisite
instead of an initiate when one of the control key is pressed.
Solution: This has been implemented.
- SCHEDULE V7.1.18 - 7640
New Feature: The columns "Owner" and "Protection" are not present for
folders in the right pane of the explorer view. Solution: This has been
implemented.
- SCHEDULE V7.1.18 - 8194
New Feature: Need ability to generate SNMP traps from notification
script. Solution: This has been implemented.
- SCHEDULE V7.1.18 - 7361
Problem: GUI needs a submenu "Edit->Select All..." in the layout to
enable users to select all objects of any type in the layout. This can
be particularly useful in conjonction to the "move to back" or "move to
front" options. Solution: This has been implemented.