• SCHEDULE V7.3.12 - 8529
  Problem: Extract/insert failing for jobs whose total parameters length is 256 characters or longer.
  Solution: Fixed.
• SCHEDULE V7.3.12 - 8525
  Problem: Nodename displayed twice in the GUI explorer when server database node was set as an alias name.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8524
  Problem: Layout control "show external dependencies" not saved in the layout definition.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8523
  Problem: GUI crashes when too many non-basic prerequisites. Solution: Fixed.
• SCHEDULE V7.3.12 - 8518
  Problem: Initiates on Success and Initiates ANY displayed in the same color in the layout
  Solution: Initiates on ANY now use only the first color defined in the layout options, Initiates on SUCCESS or Information use both colors.
• SCHEDULE V7.3.12 - 8516
  Problem: Windows jobs calling program accessing stdin don't work anymore.
  Solution: fixed
• SCHEDULE V7.3.12 - 8508
  Problem: On VMS the name of the temporary .schedule_com file did not follow the name of the specified log file.
  Resolution: This has been fixed.
• SCHEDULE V7.3.12 - 8504
  Problem: Submit/complete parameter and tag can't be preset
  Solution: Added possibility to preset them in the job "notes" page through the settings "submit_tagdata_value", "submit_parameter_value", "complete_tagdata_value" and "complete_parameter_value"
• SCHEDULE V7.3.12 - 8503
  Problem: Security testing sending junk data to Schedule Server port caused excessive Server CPU cycles.
  Solution: Added logic to quickly identify and disgard invalid data sent to Schedule server port.
• SCHEDULE V7.3.12 - 8502
  Problem: Event field in Reports not displayed correctly on AIX and HPUX.
  Solution: Corrected Big Indian byte mapping issue.
• SCHEDULE V7.3.12 - 8499
  Problem: Pre and Post file includes were properly include on a Windows systems.
  Solution: This has been fixed.
• SCHEDULE V7.3.12 - 8498
  Problem: Layout doesn't check if there job duplicates when loading.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8495
  Problem: GUI doesn't detect when documents exceed max size
  Solution: Fixed.
• SCHEDULE V7.3.12 - 8494
  Problem: On HP-UX not recording job accounting completion information .
  Solution: This has been fixed.
• SCHEDULE V7.3.12 - 8484
  Problem: New feature enable/disable job requested
  Solution: Added in the explorer view and in the layout. "Disabled" jobs are displayed striked out.
• SCHEDULE V7.3.12 - 8483
  Request: Expand options controls to do preprocessing.
  Response: Preprocessing added to the options declarations.
• SCHEDULE V7.3.12 - 8479
  Added parameter value DISABLE_USER_PROFILE to toggle off sourcing of user login file such as .profile, .cshrc, .profile_bash etc.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8478
  Problem: Modification of the notification text doesn't work the 2nd time the apply is pressed.
  Solution: Fixed.
• SCHEDULE V7.3.12 - 8473
  Problem: Aborting jobs on Windows doesn't work if the server restarted after the job was submitted.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8471
  Problem: calendar marks not replicated when a calendar is member of a workgroup.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8467
  Problem: Add retention time for failed P entries as a monitor option.
  Solution: Option added.
• SCHEDULE V7.3.12 - 8461
  Problem: New layout type "Highest set id per job" requested.
  Solution: Implemented.
• SCHEDULE V7.3.12 - 8460
  Problem: resetproxy option does not delete correctly remote proxies.
  Solution: Fixed.
• SCHEDULE V7.3.12 - 8457
  Problem: Windows servers takes a long time to (re)start.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8453
  Problem: UNIX jobs fail when there is an odd number of the character ' in the job description.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8450
  Problem: Display failed jobs in the right pane of the explorer view in another color.
  Solution: Implemented.
• SCHEDULE V7.3.12 - 8448
  Script error in schedule_start.ksh for AIX platform, that displayed misleading information at startup of server.
  Solution: Case corrected.
• SCHEDULE V7.3.12 - 8447
  Problem: Using blank in descriptive nodename causes problems.
  Solution: Blanks not allowed anymore in nodenames
• SCHEDULE V7.3.12 - 8446
  Problem: A SCHEDULE DIR XXX command on a Unix system does not return a failure status code to the shell.
  Solution: This has been fixed.
• SCHEDULE V7.3.12 - 8440
  Problem: Report command doesn't work in the Windows client
  Solution: Fixed
• SCHEDULE V7.3.12 - 8438
  Problem: Replication error messages in server log file not accurate.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8437
  Problem: delete key doesn't behave correctly in layouts when an edit box is selected.
  Solution: Fixed.
• SCHEDULE V7.3.12 - 8434
  Problem: Resources and end actions not saved in job wizard
  Solution: Fixed
• SCHEDULE V7.3.12 - 8431
  Problem: Only the first 20 users were displayed in the "Add users" dialog of the access pages.
  Solution: Fixed.
• SCHEDULE V7.3.12 - 8426
  Problem: multiple workgroup alerts displayed and not closed when the "close all alerts" function is used.
  Solution: fixed
• SCHEDULE V7.3.12 - 8425
  Problem: opening a layout can sometimes crash the GUI depending of some specific layout options.
  Solution: Fixed
• SCHEDULE V7.3.12 - 8421
  Problem: If the a node is restarted after the installation of Schedule and the license agreement has not been accepted yet, the reboot will wait for an answer and not finish.
  Solution: fixed.
• SCHEDULE V7.3.12 - 8420
  Problem:monitor connection between GUI and server cut off when no activity on the socket.
  Solution: Added a periodic message from the server to each client so that the socket doesn't timeout.
• SCHEDULE V7.3.12 - 8371
  Problem: Symbol outputs included information relevant to the wrong OS platform.
  Response: This has been fixed.
• SCHEDULE V7.3.12 - 8365
  Request: Allow the user to set defaults for whether initiates are run when using the Complete dialog.
  Response: This has been added. The job option complete_start_initiates=1/0 has been added for this purpose.
• SCHEDULE V7.3.12 - 8359
  Problem: on some linux systems the startup file uses the wrong path for the "nice" command.
  Solution: fixed
• SCHEDULE V7.3.12 - 8350
  Program: The preprocessing command was removing expressions, not related to Schedule, that are surronding by (( )).
  Response: This has been improved.
• SCHEDULE V7.3.12 - 8320
  Problem: On VMS broadcast messages failed when the username was specified as an eMail address.
  Response: This has been fixed.
• SCHEDULE V7.3.12 - 7646
  Problem: -newlog option of the server not working correctly on Windows and UNIXes
  Solution: Fixed.
• SCHEDULE V7.3.12 - 7395
  Problem: On HP-UX not recording job accounting completion information .
  Solution: This has been fixed.
• SCHEDULE V7.3.12 - 7385
  Problem: prototype jobs icons not displayed correctly.
  Solution: fixed.
• SCHEDULE V7.3.12 - 7546
  Problem: The Schedule command type -hist doesn't complete.
  Solution: fixed.

• Automated Windows client registration - The licensing of the Windows client has been automated to make the registration process easier and accessible without contacting ISE Support. Users installing the client on a Windows system with internet access and a company issued username/password can register their client by simply choosing the Web registration option in the Windows client.
• EnterpriseSCHEDULE integrated with HP Operations Manager - Integration with HP Operations Manager (formerly HP OpenView) is now available. Refer to the file HPOperationsManagerReadMe.txt for more information.
• New Shortcut parameters - The following new options have been added to the GUI command line which can be added in the Target field of the GUI shortcut:
  -nocli : disable the embedded command line client
  -nojobctl : disable all job controls
  -nopp : disable all properties pages and the edit functions of the jobs
  -layout LayoutName : This will automatically open the specified layout when opening the GUI, the format to use is:

  "\directory1\directory2\layout" or \\nodename\directory1\directory2\layout

  
  where directory2 is optional.
  -monitor : open a monitor console
  

• Extract objects menu item added to Windows client - Added a menu item to the right click menu in the Explorer view of the Windows client that allows you to extract all objects in the database to a file for insertion into another database or group.
• Added Workgroup and replication flags into Server Info - Additional information about Workgroups and replication is displayed when the schedule server info command is entered at the command prompt.
• Added "complete_start_initiates" option for prototype jobs - Added the option to turn on or off the "On completion start up all initiate jobs" checkbox on prototype jobs.

6.4 Version 7.2.14 corrections

• SCHEDULE V7.2.14 - 8341
  Problem: An invalid node name responds back as Not reachable and then gets mapped to the local VMS host and is reachable to the wrong node. Solution: An invalid or unreachable node is correctly handled.
• SCHEDULE V7.2.14 - 8356
  Problem: Big endian servers not handling correctly remote requests calls when no proxy present. Solution: fixed.
• SCHEDULE V7.2.14 - 8354
  Problem: The unsupported qualifier REPORT /SUBMIT was recognized and incorrectly attempted a submit function. Resolution: This qualifier has been removed from the parse tables.
• SCHEDULE V7.2.14 - 8353
  Problem: A trailing "-" (minus sign) causes a SCHEDULE INSERT command to incorrectly append subsequent lines during the insert. Resolution: This has been fixed. Minus signs are left as is inside a DECK/EOD block.
• SCHEDULE V7.2.14 - 8351
  Problem: GUI startup command line doesn't work when there is a '-' character in the nodename, in "-server nodename". Solution: Fixed, a nodename containing one or more '-' must be surrounded by single quotes.
• SCHEDULE V7.2.14 - 8349
  Problem: Recomplete of a job in a layout doesn't initialize the set id when the job is not in the queue. Solution: fixed
• SCHEDULE V7.2.14 - 8348
  Problem: expression variables dropped in layouts were not evaluated, the layouts needed to be closed and reopen for the evaluation to take place. Solution: fixed
• SCHEDULE V7.2.14 - 8347
  Problem: When renaming a level 1 directory, the old name was sometimes still present in the explorer view. Solution: Fixed
• SCHEDULE V7.2.14 - 8345
  Problem: Connections to jobs not in layout appear as single lines when the 3D connection box is unchecked. Solution: Fixed.
• SCHEDULE V7.2.14 - 7973
  Problem: GUI doesn't display folder correctly when there are "orphan" jobs file with no header in the directory. Solution: fixed
• SCHEDULE V7.2.14 - 8343
  Problem: Quote marks in an owner string fail to apply correctly. Resolution: Fixed.
• SCHEDULE V7.2.14 - 8357
  Problem: Using template_db.schedule on a Linux or Unix system causes the date strings to erroneously to contain the name of the day. Resolution: This has been fixed.
• SCHEDULE V7.2.14 - 8339
  Problem: GUI not displaying correctly variables with format "LDD" Solution: fixed.
• SCHEDULE V7.2.14 - 8337
  Problem: The boot time startup file did not install correctly. Resolution: Startup file has been fixed
• SCHEDULE V7.2.14 - 8331
  Problem: Renaming the server log file from a schedule after stopping the server fails on Windows. Solution: fixed.
• SCHEDULE V7.2.14 - 8326
  Problem: The handling of the /NOW qualifier with the PREPROCESS command was incorrect. Resolution: This has been fixed.
• SCHEDULE V7.2.14 - 8325
  Problem: The boot time startup file did not install correctly. Resolution: Startup file has been fixed
• SCHEDULE V7.2.14 - 8316
  Problem: On a Unix system schedule_start.ksh fails unless you first do a cd /schedule_library. Solution: This has been corrected.
• SCHEDULE V7.2.14 - 8304
  Problem: "schedule lswg" executed from a Tru64 terminal doesn't produce the correct output. Solution: fixed.
• SCHEDULE V7.2.14 - 8303
  Problem: Aborting jobs didn't work on Sun machines. Solution: fixed.
• SCHEDULE V7.2.14 - 8302
  Problem: Under certain cases temporary script files created on a Unix system double up the version number in the name string. Solution: fixed.
• SCHEDULE V7.2.14 - 8344
  The concatenation of the log file path and job name can now be extended beyond 80 characters. The allows the log path and/or the job name to be their true full sizes.
• SCHEDULE V7.2.14 - 8396
  Problem: A quote mark in a pre/post com file specification will not export/import correctly. Solution: This has been fixed.
• SCHEDULE V7.2.14 - 7607
  Problem: resume and cancel functions do not work on jobs held in K queue on VMS. Solution: fixed
• SCHEDULE V7.2.14 - 8216
  Problem: Deleting an external (triangle) connection in the layout doesn't work properly. Solution: Fixed
• SCHEDULE V7.2.14 - 8400
  Problem: Group proxy creation doesn't work in the GUI Solution: Fixed
• SCHEDULE V7.2.14 - 8398
  Problem: remote prerequisites sometimes don't get triggered. Solution: fixed.
• SCHEDULE V7.2.14 - 8368
  Problem: Issue with Pam Authentication conversation. Solution: fixed.
• SCHEDULE V7.2.14 - 8394
  Problem: quoted strings cannot be used in /out qualifier Solution: fixed
• SCHEDULE V7.2.14 - 8393
  Problem: dir/all command not returning the correct data in some special cases where the first term is relative. Solution: fixed
• SCHEDULE V7.2.14 - 8374
  Problem: A VMS job in a stop batch queue creates many notification mail messages without indicating what to check. Solution: The message has been improved to correctly inform the user where the problem is.
• SCHEDULE V7.2.14 - 8378
  Problem: After export a job definition and then re-inserting it some of the notification settings are not completely restored. Solution: This has been corrected.
• SCHEDULE V7.2.14 - 8377
  Problem: job log path cannot contain a nodename with a '.'. Solution: fixed
• SCHEDULE V7.2.14 - 8369
  Problem: An invalid node name responses back as Not reachable and then gets mapped to the local VMS host and is reachable to the wrong node. Solution: An invalid or unreachable node is correctly handled.
• SCHEDULE V7.2.14 - 8375
  Problem: Abort of jobs held in the J queue doesn't work on UNIX and Windows. Solution: fixed.
• SCHEDULE V7.2.14 - 8370
  Problem: job path in notify scripts and emails uses the Windows format with the character '\' on all platforms, which can cause problems on UNIX. Solution: Fixed to use the OS specific format.
• SCHEDULE V7.2.14 - 8385
  Problem: database could get corrupted if an invalid character '/' was present in the new name of the "clone folder" window. Solution: Fixed.
• SCHEDULE V7.2.14 - 8399
  Problem: Changed code to dynamically lookup entry points at runtime and avoid looking at the header portion of statically linked Pam entry points. Solution: fixed.
• SCHEDULE V7.2.14 - 8355
  Problem: The unsupported qualifier REPORT /SUBMIT was in the help documents Resolution: This qualifier has been removed from the help files.
• SCHEDULE V7.2.14 - 7659
  Problem: No GUI equivalent to the command "type/res/check" Solution: Button "Check" added in the job resource property page to evaluate the resources of a job.
• SCHEDULE V7.2.14 - 8321
  Problem: extract option needed in the GUI Solution: New menu option added to the explorer view to extract data to .schedule files.
• SCHEDULE V7.2.14 - 8219
  Problem: Add new option "Send GUI log file" in control window Solution: new button added
• SCHEDULE V7.2.14 - 8336
  Problem: Enhance the server information display with optional debug settings that me be set. Solution: Then have been added.
• SCHEDULE V7.2.14 - 8365
  Problem: Allow the user to set defaults for the "do initiates" attribute of the Complete dialog. Solution: This has been added. The job option complete_start_initiates=1/0 has been added for this purpose.
• SCHEDULE V7.2.14 - 8380
  Problem: no way to trace data if a Windows server is hung Solution: Added the option "ScheduleSvrMgmt /s /g n" where n is the group number.

Several new features have been added and numerous errors discovered and corrected in this version of EnterpriseSCHEDULE. They are listed below.

• Variable Expressions - have been added to expand the variable and preprocessing features of EnterpriseSCHEDULE. This feature enables the introduction of complex date expressions, arithmatic expressions and string expressions to variables and as preprocessed expressions in the command list and Notification message of a job. Variables can now be one of two types; a STRING variable or an EXPRESSION. A string variable remains as it was in previous versions and can be used for compares and assignments when a job is run. An expression is evaluated when the job is run and therefore can change at run time if a date expression is included. The PREPROCESS command now displays the resolved value of any expressions in preprocessor directives. The -result qualifier has been added to the lsvar command to display the current value of a variable expression. The -type qualifier has been added to the lsvar, chvar and mkvar to display, modify or create a variable's type of either STRING or EXPRESSION.
• Windows Client Enhancements - The Windows client has been enhanced with a new look and feel incorporating new menus and icons. Improvements have been made when converting layouts from MOTIF to Windows to allow more layout customization. A new feature, Folder Templates has been added that allows the selective transfer of objects (jobs, layouts, calendars etc) to a new folder in the Explorer View. The Variable property page now includes a dropdown menu that allows the user to choose between a string or expression as well as a tab that allows the testing of dates and times with date expressions.
• Prototype Job Enhancements - The list of Prototype jobs (templates used to create jobs that perform a specific task) has increased and is now categorized. Among the list of prototypes now included:
  1. Database Querying
  2. .NET scripting
  3. FTP and HTTP procedures
  4. System Monitoring
  5. Message Queue procedures
  6. Compression and Encryption
  7. SQL Database Operations
  8. System pinging
  9. System polling
  In addition EnterpriseSCHEDULE REPORTS have now been incorporated as prototype jobs, simplifying and automating the report creation procedure.
• Platform Matrix - EnterpriseSCHEDULE's list of supported platforms has been increased to include the following:

  Table 6-1 EnterpriseSCHEDULE Platform Summary

  Operating System	Platforms Supported
  OpenVMS	VAX
  	Alpha
  	Itanium
  Windows	X86
  	Opteron
  Linux	X86
  Solaris	SPARC
  	Opteron
  	X86
  HP-UX	PA-RISC
  	Itanium
  AIX	PowerPC
  Tru64	Alpha

• Reference Documents have been reorganized and split up to make relevant topics easier to access.