24x7 Automation Suite version 3.2 is available

This upgrade is highly recommended because of the several important issues that were fixed in the new version, including:
-- non-intended job start when another job is changed and saved
-- RunAsUser incorrect behavior on WinNT systems

Here is what's new in this version
===========================================================================

1. 24x7 Remote Automation Server for Digital UNIX and Tru64 UNIX

2. New job load balancing option allows you to avoid specifying static job server name. The execution server is assigned dynamically using "least busy" method. Yet, you can specify available target servers.

3. New extensions for JAL:
-- Advanced programmatic job manipulation and replication methods: RemoteJobList, RemoteJobCreate, RemoteJobDelete, RemoteJobEnable, RemoteJobDescribe, RemoteJobModify, RemoteCopyJob, RemoteCopyJobFolder, RemoteCopyJobDatabase, RemoteCopySettings

-- Improved error trapping and handling in JAL scripts: OnErrorGoTo, OnErrorStop, OnErrorResumeNext

-- New directory and file comparison statements: CompareLocalDir, CompareRemoteDir, CompareFTPDir

-- Other new statements: RegistryList, RegistryDelete, JobList

4. New job templates. The total number of ready-to-use job templates is now near 100.

5. 24x7 GUI MacroRecorder is now able to automatically schedule recorded GUI automation jobs.

6. Fixes for known bugs found in version 3.1 and prior.

7. Improved on-line documentation.

: This upgrade is highly recommended because of the several important issues
: that were fixed in the new version, including: -- non-intended job start
: when another job is changed and saved
: -- RunAsUser incorrect behavior on WinNT systems

: Here is what's new in this version
: ===========================================================================

: 1. 24x7 Remote Automation Server for Digital UNIX and Tru64 UNIX

: 2. New job load balancing option allows you to avoid specifying static job
: server name. The execution server is assigned dynamically using
: "least busy" method. Yet, you can specify available target
: servers.
A job that I have was working in 3.1 now the job recieves error. "Invalid schedule type." what the deal with that?
: 3. New extensions for JAL: -- Advanced programmatic job manipulation and
: replication methods: RemoteJobList, RemoteJobCreate, RemoteJobDelete,
: RemoteJobEnable, RemoteJobDescribe, RemoteJobModify, RemoteCopyJob,
: RemoteCopyJobFolder, RemoteCopyJobDatabase, RemoteCopySettings

: -- Improved error trapping and handling in JAL scripts: OnErrorGoTo,
: OnErrorStop, OnErrorResumeNext

: -- New directory and file comparison statements: CompareLocalDir,
: CompareRemoteDir, CompareFTPDir

: -- Other new statements: RegistryList, RegistryDelete, JobList

: 4. New job templates. The total number of ready-to-use job templates is now
: near 100.

: 5. 24x7 GUI MacroRecorder is now able to automatically schedule recorded GUI
: automation jobs.

: 6. Fixes for known bugs found in version 3.1 and prior.

: 7. Improved on-line documentation.

A job that I have was working in 3.1 now the job recieves error. "Invalid schedule type." what the deal with that?

How this job is scheduled?

: A job that I have was working in 3.1 now the job recieves error.
: "Invalid schedule type." what the deal with that?

The schdule type is "On 24x7 startup". I have duplicated this on two different machines. This seems the only type of schule that exhibits this behavior.

An additional note:
This behavior can be duplicated in the example database, 2.x-3.1-3.2 updated databases and new job databases.

Please my response in the new message thread.

: An additional note: This behavior can be duplicated in the example database,
: 2.x-3.1-3.2 updated databases and new job databases.