CA Scheduler Job Management
Release 11 - New Features and Changes

    We highly recommend the CA Scheduler Release 11 Differences Training when upgrading to Release 11
 Click here for course details

New Features

1)         Job History

The history function has been redesigned and now includes schedule level history. The history details can now be customized to span more than the last 7 executions of a job or schedule. The online and batch report has been changed to include additional history details.

2)         Auto Failover

The CA Scheduler started tasks will automatically restart themselves when the CA Datacom/AD MUF becomes unavailable.  CA Scheduler can also register with IBM's Automated Restart Management (ARM).

3)         Concurrent Submission

CA Scheduler now has multiple submission tasks which is used for submitting jobs and writing or deleting staged JCL in CA Datacom. The main submission task can now distribute request up to 15 sub-tasks at one time.

4)         Distributed Submission

In multiple CPU environments, the master copy of CA Scheduler can now use the other CA Scheduler started task running on other systems to submit jobs.

5)         CA Unicenter CA OPS/MVS Interface

CA Scheduler now has an interface with CA OPS/MVS and reports it's status (Starting, UP, Stopping or Down) to the CA OPS/MVS system state manager.

6)         CA Unicenter Service Desk Interface

CA Scheduler can generate and send requests to CA Unicenter Service desk to open a service ticket based on job events in CA Scheduler.

7)         Threshold Rules

CA Scheduler can notify users by email or CA Unicenter Service Desk when a specified condition exists in CA Scheduler such as CA Datacom database file utilization or job events.

8)         ENF Event Control

Optional ENF event notifications can now be 'turn off' using the CAS9 ENF initialization statement.

9)       Warning for Missing Date Tables

Starting on December 1, any Date Tables missing hat are required for January 1 will cause a warning message to be sent to the console .

10)       IBM Health Checker Interface

CA Scheduler can now provide two health check routines for z/OS to verify that CA Scheduler 's address spaces are active and receiving events from CAIENF.

 

Changes to existing features

 

1)       Autoscan Date Keyword

The CA Scheduler manual autoscan now accepts a date keyword which will load only schedule and jobs specified in the date keyword into the current workload.

2)       Critical Path Monitoring - Loading

A new installation option is available to issue the load event when the first job is added to the current workload, usually during autoscan.  In previous release's, the load event was issued when the first job started.

3)       Email Reply Address

The email definition now supports an optional reply address so that emails created from that particular email definition will have the specified reply address.

4)       High Availability Option (HAO)

CA Scheduler supports the cross-platform High Availability Option that supports the moving of the master copy of CA Scheduler from one LPAR to another and to continue to track those cross-platform jobs submitted before the move.

5)       Repeat from Clock

Two additional features of the repeat option are now available:

1 - CLOCK - A Repeat From of CLOCK indicates that the next instance's early start time should be calculated from the previous instance's early start time, regardless of

2 - XCLOCK - A Repeat From of XCLOCK works the same as a value of CLOCK, but any missed iterations are skipped.

6)       TALTER Command

Four additional keywords have been added to the TALTER JOB command:

1 - MAXTIME

2 - MEMO

3 - SDRNUM

4 - TESTPARM

Two additional keywords have been added to the TALTER SCHEDULE command:

1 - MAXTIME

2 - SDRNUM

7)       True OR in criteria statement

A new keyword has been added to criteria -OR- (dashes before and after OR). The existing OR keyword acts like a Boolean "or" during selection, but sometimes acts like a Boolean "and" during predecessor evaluation. The new -OR- keyword always acts like a Boolean "or," allowing a successor job or schedule to start with either of two, but not both, predecessors are satisfied.

8)       Virtual Resources for Schedules

The virtual resources feature, previously available only for jobs, can now be used for schedules as well.