EnterpriseSCHEDULE
Installation Notes
5.7 Version 7.6.36 corrections
- SCHEDULE V7.6.36 - 8832
Problem: Add new extract option to be able to keep users but not nodes
Solution: Fixed
- SCHEDULE V7.6.36 - 8839
Problem: Request license by email not working.
Solution: Fix to
create a text file that has to be pasted in an email.
- SCHEDULE V7.6.36 - 8843
Problem: Memory leak on worker threads not properly managing exception
handler list.
Solution: Fixed
- SCHEDULE V7.6.36
Problem: PAM was not being setup properly in Linux install
Solution: Fixed
5.8 Version 7.6.34 corrections
- SCHEDULE V7.6.34
Problem: Problems with PAM Authentication in Linux.
Solution: Fixed
5.9 Version 7.6.30 corrections
- SCHEDULE V7.6.30
Problem: View Log fails on Windows Server when doing a proxy reset or
new install with No data found/incorrect parameter.
Solution: Fixed
- SCHEDULE V7.6.30
Problem: View Log fails when default path is not used.
Solution:
Fixed
- SCHEDULE V7.6.30
Problem: Monitor events not being displayed.
Solution: Fixed
- SCHEDULE V7.6.30
Problem: License Manager Send Email not working.
Solution: Fixed
5.10 Version 7.6.28 corrections
- SCHEDULE V7.6.28
Problem: When viewing job log files, that have a lot of text on one
line, the text was truncated at 255 characters per line.
Solution:
The view log function will now wrap long lines and put 255 characters
per line.
5.11 Version 7.6.26 corrections
- SCHEDULE V7.6.26
Problem: "View Log" call timed out and failed for OpenVMS and Windows
jobs on occasion.
Solution: Fixed
- SCHEDULE V7.6.26
Problem: Modifying a dynamic job variable failed under certain
circumstances.
Solution: Fixed.
5.12 Version 7.6.24 corrections
- SCHEDULE V7.6.24
Problem: If the EnterpriseSCHEDULE GUI was started and the given
"descriptive name" is a nickname not a valid node name then any
subsequent "view log" operations will fail.
Solution: Fixed
- SCHEDULE V7.6.24
Problem:
Problem: When using the License Manager to fetch a PAS number
occasionally a time-out will occur when communicating with the ISE
registrar server.
Solution: The time out interval has been extended.
5.13 Version 7.6.22 corrections
- SCHEDULE V7.6.22
Problem: The initial startup of the EnterpriseSCHEDULE GUI client could
take a long time. This can happen when the specified server is not
defined in DNS and an IP address has been entered.
Solution: Fixed