IBM Z Workload Scheduler Small Programming Enhancements released in June 2019

The following features were provided with IBM® Z Workload Scheduler small programming enhancements (SPEs) released for Version 9.5, in June 2019 (APAR PH12689).

DB2 Reporting feature

You can now customize the DB2 table prefix, whose default is set to MDL. For details, see the DBOPT initialization statementDBOPT initialization statement in Customization and Tuning.
The following columns have been added to tables DB2TablePrefix.JOS_JOB_STATISTICS and DB2TablePrefix.JHR_JOB_HISTORY_RUNS:
- SUBSYSTEM NAME
- WORKSTATON TYPE (either FTA, zCentric, Dynamic, or zOS)
In the Dynamic Workload Console, the following columns have been added to the DB2 reports. You can filter on their values.
- SUBSYSTEM NAME
- WORKSTATON TYPE

For details about the DB2 Reporting feature, see Reporting with IBM Z Workload Scheduler

TLS V1.2 support

The connection through the Transport Layer Security (TLS) V1.2 protocol is now supported between IBM Z Workload Scheduler and:

IBM Z Workload Scheduler Agents. For details, see Customizing the SSL connection between the agents and the Z controller when using your certificates.
Fault-tolerant agents. For details, see Configuring TLS to connect with the IBM Z Workload Scheduler server.
Dynamic Workload Console. For details, see Customizing TLS to connect components with IBM Z Workload Scheduler.
Master domain manager and dynamic domain manager.

New keywords for JOBREC

In the Syntax diagram for file transfer job types, the following keywords have been added :

APPENDTEXT(YES | NO)
DELETEAFTERDOWNLOAD(YES | NO)
DELETEAFTERUPLOAD(YES | NO)
EXTRACOMMAND(FTP SIte subcommand)
LOCALPWD(YES | NO)
LOCALUSR(YES | NO)

MCP performance has been improved: The performance, when updating the current plan, has been improved; in particular, when you change the status of a job and/or when you are using the MCP Data Space.
Message EQQN228I has been created to track the number of JT and MCP events that accumulate during DP batch job run. The frequency of the message is determined by the JTAPPLCNT and JTAPPLMCP parameters in the JTOPTS statement.

With the Dynamic Workload Console V9.5, Fix Pack 1 the following enhancements have been implemented.

Dynamic Workload Console can be installed on WebSphere Application Server for z/OS Liberty.

For details, see Prerequisite step to install on WebSphere Application Server for z/OS Liberty.

Filtering jobs that are late

From the General filter for z/OS jobs window, you can browse the jobs in the current plan that are late according to the following criteria:

Their latest start time
The day and time you specified in the Not Started Alert or Not Started Action field.
Either their latest start time, or by the day and time that you specified in the Not Started Alert or Not Started Action field.

Setting alerts or actions if a job in plan does not start or complete

You can edit the properties of a job in plan, by modifying or setting that an action is taken if the job does not start or complete within the specified date and time.

Dependencies Resolution

From the Self-Service Catalog you can define the dependencies resolution for the service, as follows:

None: No dependency resolution is necessary. This is the default value.
All: Both predecessor and successor dependencies must be resolved.
Predecessor: Predecessor dependencies must be resolved.
Successor: Successor dependencies must be resolved.