IBM

To: Licensees of Tivoli Workload Scheduler for z/OS, Version 9 Subject: Program Number 5698-T08 — Release 2, Modification Level 0 Features 5803, 5823, 5843, 5853, 5863

The material you have received is listed on the enclosed Packing List. Please review the Packing List to ensure you have received all items listed.

Attached to this memorandum: Summary of Changes. Interoperability. Additional Software. Known Problems.

Please refer to the attachment for further description.

IBM Software Manufacturing Solutions

GC27-4088-01 1

2

Summary of Changes

The following new features have been included in Tivoli Workload Scheduler for z/OS Version 9— Release 2, Modification Level 0: New filter for operations waiting for pending predecessors: on ISPF and on the Dynamic Workload Console you can browse and modify operations in the current plan that are in waiting status for pending and mandatory pending predecessors. When you enter the 5.3 menu fast path on ISPF and display the SELECTING OPERATIONS(EQQSOPFP) panel, you can request lists of operations that are waiting for pending predecessors, for mandatory pending predecessors, or for either or both. From the ensuing list, you can then browse operation details or run any of the permitted actions. This option is featured also in the Dynamic Workload Console. Dependency resolution time interval shown for mandatory pending predecessors: in ISPF, starting from choice 5 (Modify the current plan) or 6 (Query the current plan), selecting 3 (Operations) to display the Selecting Operations (EQQSOPFP) panel, and entering the appropriate selection criteria, you first display a list of operations in waiting status for mandatory pending predecessors. You then proceed to view the information related to the predecessors and successors of a specific operation and find the following columns: – Resl Crit: displays the criteria specified for the resolution of the dependency in the dependency definition. – Mandatory Pending Interval: Shows the interval where the Input Arrival Time of the predecessor must be so that the dependency is solved. The interval boundaries are listed in terms of From and To dates. A blank From date signifies that the left side of the interval is open. This information can be viewed also in the Dynamic Workload Console. Status of system automation workstations can be changed in the plan: system automation work- stations in the plan can have their status changed similarly to computer automatic workstations. You can see and change the status of a system automation workstation from the MCP panels in ISPF or from the Dynamic Workload Console. In ISPF you can see the status of a workstation in the current plan in the BROWSING WORK STATION ACTIVITY panel. You can then change the status of a system automation workstation (from OFFLINE to ACTIVE or viceversa) in one of the following ways: – With the VARY command from the ISPF MCP panels. – Using the WSSTAT TSO command. Maximum number of parallel servers per workstation increased to 65535: the highest number of par- allel servers that can be defined for a workstation has changed from 99 to 65535. The number of parallel servers represents the number of operations that can be started simultaneously on a work- station. Job run history reports add statuses of jobs ended in error and manually set to completed: in previous versions the reports included only the history of jobs that had been rerun after ending in error. Now they include also jobs that are manually set to complete following an error status.

© Copyright IBM Corp. 1991, 2014 3

Create incident reports through OSLC integration with Smart Cloud Control Desk: Tivoli Workload Scheduler for z/OS integrates with Smart Cloud Control Desk, through an Open Services for Lifecycle Collaboration (OSLC) interface, so that when a job matching a defined policy ends in error, an incident report is automatically opened. It is possible to configure this integration through the new OSLCOPTS statement (see Tivoli Workload Scheduler for z/OS Customization and Tuning). By configuring the OSLCOPTS parameters, users can: – Select the policies that determine which jobs that ended in error will have an incident opened – Provide the ticket description text with the possibility to use predefined variables. Heartbeat checking mechanism for z-centric agents and dynamic domain managers: the Tivoli Work- load Scheduler for z/OS controller uses the HTTP protocol to communicate with z-centric agents and dynamic domain managers. If at any time any of these become unavailable, the controller does not register it until the next job submission takes place. To prevent the inherent loss of time, an internal heartbeat checking mechanism is added with this version, whereby the controller checks at specified intervals the status of all attached z-centric agents and dynamic domain managers. This feature is optional and the pulse interval (in minutes) can be configured both globally for all attached devices and individually for each agent. Destination pulse intervals can be updated using the HTTP refresh destination command without having to stop the controller. New JOBREC keyword for the script file extension: the new EXTENSION keyword can now be added in JOBREC statements defining native jobs launched by z-centric agents. The keyword is to be used in conjunction with the JOBCMD(SCRIPT) keyword and its value is the file extension of the script started by the job. The script file extension can be specified also through the Tivoli Dynamic Workload Console in the executable plugin. Product version displayed in the Message Log (EQQMLOG): the message log now displays message EQQZ403I with the version of the Tivoli Workload Scheduler for z/OS installation. For example, MLOG listings for this product version display the following message: EQQZ403I RUNNING TWS for z/OS 9.2.0 The message follows the lines showing the parsing of the started task parameters in all the currently available message logs; that is: – Controller – Tracker – Server – Output collector – Datastore – Batch MLOG New message EQQIC66I issued in the MLOG of the migration JCL when VSAM files of the Applica- tion Description data base are migrated with the EQQICTOP conversion program. The EQQICTOP conversion program is now capable of issuing message: EQQIC66I PROCESSING APPLICATION AD_data_set_name VALID FROM From_date STATUS status each time it migrates a data set in the Application Description database to a new Tivoli Workload Installation for z/OS product release. It is possible to inhibit this feature by setting to N the TRACE parameter of the CONVERT command that is included in the EQQICTOP conversion program.

4

Configuring Tivoli Workload Scheduler for z/OS to use two message log data sets, EQQMLOG and EQQMLOG2: using two MLOG data sets removes the necessity of stopping the controller to be able to save, or clear, the contents of a single data set. It also prevents the messages from being recorded in the system log when the controller is not stopped for a long period of time and EQQMLOG runs out of space. The two MLOGs are used alternatively: while one logs messages, the other remains inac- tive. Then, when the active data set reaches a pre-set level of completion, its contents are copied into a GDG data set and goes idle, while the other data set starts logging. When the same level of com- pletion is reached in the now active data set, the switch is repeated. Viewing z/OS job logs with Tivoli Output Manager: if you run Tivoli Output Manager in your enterprise, you can use it to view the z/OS job logs of operations run with Tivoli Workload Scheduler for z/OS. To do so, after having properly configured Tivoli Workload Scheduler for z/OS and Tivoli Output Manager, enter the Browse joblog via ITOM (LJ command which is available in the ISPF panels where the Browse joblog (L) command is available). The panels are those related to browsing or modifying operations in the current plan; that is: – modifying operations in the current plan (EQQMMOPL, EQQMOPRL, and EQQMOPRR) – operations history list (EQQHISTL) – handling operations ended in error (EQQMEE1L, EQQMEE2L, EQQMEP1L, and EQQMEP2L) – list dependency status change (EQQMOSTL) – rerunning an occurrence in the current plan (EQQMROCL) – operations in the current plan (new panels - EQQMOPRV or EQQSRCLP) – operation in the current plan (new panel - EQQSOPSD - Operation menu) The following features that were implemented on Tivoli Workload Scheduler and Dynamic Workload Console are available also for Tivoli Workload Scheduler for z/OS: Self-Service Dashboards mobile application: you can use your mobile device to define one or more dashboards filtering on subsets of jobs and workstations. The dashboards give an overall picture of your jobs and workstations and enable to drill down and view more detailed information about jobs, such as job details and the job log, and about workstations and their availability. You can also perform some recovery actions on jobs and workstations. New look-and-feel for Self-service Catalog mobile app: Self-Service catalog is a mobile device applica- tion to submit service requests to Tivoli Workload Scheduler and Tivoli Workload Scheduler for z/OS. Service requests correspond to Tivoli Workload Scheduler job streams and to Tivoli Workload Sched- uler for z/OS applications. Self-Service Catalog has undergone a design update, improving its general look-and-feel. Single sign-on configuration for Self-Service Catalog and Self-Service Dashboards applications: if the Dynamic Workload Console instance to which the applications connect is configured for single sign-on, then a user can log in once on the Dynamic Workload Console and then gain access to the applica- tions without being prompted to log in again. Global settings file also available with local installation TdwcGlobalSettings.xml, is a file that users can optionally edit to configure some advanced Dynamic Workload Console settings. This file is now also installed locally and you can find it in the following path after you install the Dynamic Workload Console on your workstation:

Summary of Changes 5

JazzSM_Installation_Path/profile/registry/ The file is installed as TdwcGlobalSettings.xml.template. If you edit it, save it as TdwcGlobalSettings.xml. Monitoring task query for jobs, job streams, workstations or resources: you can now define a task to monitor jobs, job streams, workstations, and resources by specifying a query in a query line. You can specify the query by selecting from a series of user interface options. You can save your queries and then reuse or edit them as necessary. Performance improvement for batch operations with large number of job streams on the Dynamic Workload Console: previously a timeout error was returned or the performance was very slow when batch operations were performed. Instead of sending separate requests for each job stream now only a single request is sent for all selected job streams. Self-Service Catalog mobile application: administrators can tailor services by defining variable vali- dation criteria to be applied to the job streams associated to a service. By defining variable validation criteria, Administrators can ensure that input entered by the mobile user is checked against the criteria and onl input that satisfies the criteria is accepted. When defining variable validation criteria, Adminis- trators can specify, for example, whether the input value is numeric or alphabetic, whether the entry must be within a range of values or a certain length, or if the value is obligatory. A new predefined role to use and manage the Self-Service Catalog and Self-Service Management mobile applications: users with the new role assigned, TWSWEBUIBusinessDeveloper, can access and use the Self-Service Catalog and the Self-Service Dashboards mobile applications. From the Self- Service Catalog mobile application, these users can create and edit catalogs, create and edit services, add services to catalogs, and submit services associated to job streams. From the Self-Service Dashboards mobile application, these users can create and edit services to filter for jobs and work- stations, run services to view a dashboard of results, perform recovery actions on a single result. To catalogs and services with other user, the TWSWEBUIBusinessDeveloper can assign the catalog or service to custom roles they possess, and not to predefined roles. Users with these same custom roles can work with the catalogs and services. New global setting for displaying the rows in a table view corresponding to results of a monitoring task: the Dynamic Workload Console administrator can set the maximum number of rows to display in a table view after running a monitoring task. A new property, maxRowsToDisplay, has been added to Section 8 of the Dynamic Workload Console global settings file, TdwcGlobalSettings.xml. Auditing mobile device application activities: administrators can configure logging information in the Dynamic Workload Console global settings file, TdwcGlobalSettings.xml, related to operations per- formed from the Self-Service Catalog and Self-Service Dashboards mobile applications. A new section, Section 11, has been added to the global settings file and the log file is enabled by default Monitor critical jobs from your mobile device: you can use your mobile device to define one or more dashboards filtering on subsets of jobs and workstations. The dashboards give an overall picture of your jobs and workstations and enable to drill down and view more detailed information about jobs and perform recovery actions. Jobs can be further filtered to produce a set of results corresponding to critical jobs in the network categorized by jobs with a high risk and jobs with a potential risk. New browser support: the Dynamic Workload Console, the Self-Service Catalog and Self-Service Dashboards mobile applications are all supported on Firefox 24 ESR.

6

Interoperability

This section contains information about the interoperability of Tivoli Workload Scheduler for z/OS Version 9— Release 2, Modification Level 0 with: Dynamic Workload Console Tivoli Workload Scheduler for z/OS Agent

Dynamic Workload Console

The Tivoli Workload Scheduler for z/OS Version 9— Release 2, Modification Level 0 engine requires the Tivoli Dynamic Workload Console version 9.2.0.

The z/OS Connector version 9.2.0 is automatically installed when you install the Tivoli Dynamic Workload Console version 9.2.0. Note: For detailed system requirements refer to System Requirements for Dynamic Workload Console version 9.2: http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27041008

Tivoli Workload Scheduler for z/OS Agent

For information about installing, upgrading, and uninstalling the z/OS Agent, see IBM Tivoli Workload Scheduler for z/OS Planning and Installation Guide.

It is distributed with the CD/DVD IBM Tivoli Workload Scheduler for z/OS Agent 9.2 Multiplatform.

The z/OS Agent requires one of the following operating systems:

Operating system AIX 5L, Versions 6.1, 7.1 HP-UX, Version 11i v2 Itanium HP-UX, Version 11i v3 Itanium

© Copyright IBM Corp. 1991, 2014 7

Operating system Server 2003: Standard, Enterprise, and Data Center Microsoft Windows Server 2003: Standard and Enterprise for AMD64 and EMT64T Kernel 64 Microsoft Windows Server 2008 R1: Standard, Enterprise, and Data Center Microsoft Windows Server 2008 R1/R2: Standard and Enterprise for AMD64 and EMT64T Kernel 64 Microsoft Windows Server 2012 R2: Standard and Enterprise for AMD64 and EMT64T Kernel 64 Microsoft Windows Vista Ultimate Microsoft Desktop Windows Vista Microsoft Windows Vista for AMD64 and EMT64T Microsoft Windows Vista Enterprise with FDCC Microsoft Desktop Windows Vista Enterprise with FDCC Microsoft Desktop Windows 7 Enterprise Microsoft Desktop Windows 7 Enterprise with FDCC Microsoft Desktop Windows 8 Enterprise Microsoft Desktop Windows 8.1 Enterprise Microsoft Desktop Windows Server 2012 Enterprise Linux 5.0 System x and eSeries (AMD64 and EMT64T) Kernel 32 Red Hat Enterprise Linux 5.0 System x (AMD64 and EMT64T) Kernel 64 Red Hat Enterprise Linux 5.0 System i Kernel 64 Red Hat Enterprise Linux 5.0 System p Kernel 64 Red Hat Enterprise Linux 5.0 System z Kernel 64 Red Hat Enterprise Linux 6.0 System x and eSeries (AMD64 and EMT64T) Kernel 32 Red Hat Enterprise Linux 6.0 System x (AMD64 and EMT64T) Kernel 64 Red Hat Enterprise Linux 6.0 System i Kernel 64 Red Hat Enterprise Linux 6.0 System p Kernel 64 Red Hat Enterprise Linux 6.0 System z Kernel 64 Red Hat Desktop Kernel x86-32, x86-64 Solaris Operating Environment Versions 10, 10 AMD (Opteron), 11, 11 AMD (Opteron)

8

Operating system SUSE Linux Enterprise Server 10 System x (IA32) and eseries (AMD64 and EM64T) Kernel 32 SUSE Linux Enterprise Server 10 System x Kernel 64 SUSE Linux Enterprise Server 10 System i Kernel 64 SUSE Linux Enterprise Server 10 System z Kernel 64 SUSE Linux Enterprise Server 10 System p Kernel 64 SUSE Linux Enterprise Server 10 Desktop Kernel x86-32, x86-64 SUSE Linux Enterprise Server 11 System x (IA32) and eseries (AMD64 and EM64T) Kernel 32 SUSE Linux Enterprise Server 11 System x Kernel 64 SUSE Linux Enterprise Server 11 System i Kernel 64 SUSE Linux Enterprise Server 11 System z Kernel 64 SUSE Linux Enterprise Server 11 System p Kernel 64 SUSE Linux Enterprise Server 11 Desktop Kernel x86-32, x86-64 IBM i (i5/OS), Version 5.4, 6.1, 7,1

The following table shows which versions of Tivoli Workload Scheduler for z/OS, Tivoli Dynamic Workload Console, z/OS connector, and Tivoli Workload Scheduler for z/OS agent, can work together:

TWS for z/OS TDWC and z/OS con- TWS for z/OS Agent FTA nector 9.2.0 9.2.0 8.5.1, 8.6.0, 9.1.0, 9.2.0 8.4.0, 8.5.0, 8.5.1, 8.6.0, 9.1.0, 9.2.0 9.1.0 9.1.0. 9.2.0 8.5.1, 8.6.0, 9.1.0, 9.2.0 8.4.0, 8.5.0, 8.5.1, 8.6.0, 9.1.0, 9.2.0 8.6.0 8.6.0 8.5.1, 8.6.0, 9.1.0, 9.2.0 8.4.0, 8.5.0, 8.5.1, 8.6.0, 9.1.0 9.1.0, 9.2.0 9.2.0

Notes: The z/OS connector version must be the same as the Dynamic Workload Console version. The Dynamic Workload Console version must be equal or higher than Tivoli Workload Scheduler for z/OS version.

Interoperability 9

10

Additional Software

This section contains information about the additional software distributed with Tivoli Workload Scheduler for z/OS Version 9— Release 2, Modification Level 0 via CD/DVD support: LCD7-6516-01 IBM Tivoli Workload Scheduler for z/OS 9.2.0 TEP Integration and Reporting features Agent for multiplatform The installation CD contains the following directories: – SendReportMacro: contains the macro to send via email reports generated by running batch pro- grams. – Reporting: contains the scripts used for DB2 reporting. – TEPIntegration: contains the scripts used for ITM/TEP (IBM Tivoli Monitoring/Tivoli Enterprise Portal) integration. LK4T-4917-01 IBM Tivoli Dynamic Workload Console, zConn, and SDK 9.1.0 - Kit – LCD7-6517-01 IBM Tivoli Workload Scheduler for z/OS 9.2.0 Dynamic Workload Console, z/OS Connector for AIX – LCD7-6518-01 IBM Tivoli Workload Scheduler for z/OS 9.2.0 - Dynamic Workload Console, z/OS Connector, and TWS Integration Workbench for Windows X86-64 – LCD7-6519-01 IBM Tivoli Workload Scheduler for z/OS 9.2.0 - Dynamic Workload Console, z/OS Connector, and TWS Integration Workbench for Linux X86-64 – LCD7-6520-01 IBM Tivoli Workload Scheduler for z/OS 9.2.0 - Dynamic Workload Console, z/OS Connector for Linux S390 LCD7-6521-01 IBM Tivoli Workload Scheduler Batch Reports LCD7-5193-00 IBM DB2 10.1 Enterprise Server Edition - for Linux on AMD64 and Intel EM64T systems (x64) – LCD7-5194-00 IBM DB2 10.1 Enterprise Server Edition - for Linux on POWER (System i and System p) systems – LCD7-5195-00 IBM DB2 10.1 Enterprise Server Edition - for Linux on System z – LCD7-5196-00 IBM DB2 10.1 Enterprise Server Edition - for 64-bit AIX – LCD7-5197-00 IBM DB2 10.1 Enterprise Server Edition - for HP-UX on HP Integrity Itanium-based systems – LCD7-5198-00 IBM DB2 10.1 Enterprise Server Edition - for Solaris on UltraSPARC systems – LCD7-5199-00 IBM DB2 10.1 Enterprise Server Edition - for Solaris on x64 systems – LCD7-5200-00 IBM DB2 10.1 Enterprise Server Edition - for Windows on 32-bit AMD and Intel systems (x86)

© Copyright IBM Corp. 1991, 2014 11

– LCD7-5901-00 IBM DB2 10.1 Enterprise Server Edition - for Windows on AMD64 and Intel„ EM64T systems (x64) – LCD7-5902-00 IBM DB2 10.1 Enterprise Server Edition - Restricted Use - Quick Start and Acti- vation

12

Known Problems

None

IBM is the registered trademark of International Business Machines Corporation.

© Copyright IBM Corp. 1991, 2014 13

IBM

March 2014

References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM program product in this publication is not intended to state or imply that only IBM’s program product may be used. Any functionally equivalent program may be used instead.

© Copyright International Business Machines Corporation 1991, 2014. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

GC27-488-1