IBM. Please refer to the attachment for further description. IBM Software Manufacturing Solutions GC

Transcription

1 IBM To: Licensees of Tivoli Workload Scheduler for z/os, Version 9 Subject: Program Number 5698-T08 Release 1, 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. Ensuring the compatibility of the new default security certificates Interoperability. Additional Software. Known Problems. Please refer to the attachment for further description. IBM Software Manufacturing Solutions GC

2 2

3 Summary of Changes The following new features have been included in Tivoli Workload Scheduler for z/os Version 9 Release 1, Modification Level 0: New run cycle group database object. A run cycle group is a list of run cycles that, combined together, produce a set of run dates. It can be reused in different job streams, and can be used to enforce the use of exclusive run cycles by identifying the days when a job stream would normally be scheduled, but is not required to run. You can use the Dynamic Workload Console or the ISPF panels to define and manage run cycle groups. There are multiple advantages in using run cycle groups. They are: A run cycle group is a distinct database object. The same run cycle group can be used on different applications. Run cycle groups enhance the use of negative run cycles. Run cycle groups allow the use of a logical AND between individual run cycles in the group. Full compatibility with traditional run cycles. Availability of the GENDAYS command at run cycle group level. In the long term plan (LTP) run cycle groups are interpreted as non-cyclic periods with open intervals (no end dates) where the generated days are used as start dates for the intervals and where every interval starting from a generated day finishes at the next generated day. Several matching criteria have been added for defining in the Application Description how a dependency between predecessor and successor operations is resolved. The criterion chosen to pick a matching predecessor that best resolves the dependency can be that the matching predecessor is the one with: The nearest preceding input arrival time. This option was already available in previous versions. The nearest input arrival time within the same day of the successor. The closest input arrival time within a specified interval. The interval boundaries are calculated using an offset expressed in hours and minutes before or after the IA time of the successor. The interval can be timed entirely before, entirely after, or across the IA time of the successor. The closest input arrival time within a specified interval. The interval boundaries are specified by a time and a number of days before or after the IA time of the successor. The interval can be timed entirely before, entirely after, or across the IA time of the successor. In addition, the resolution of a normal dependency may be defined mandatory at plan level where, if the predecessor is not in the plan, the plan (LTP and DP) fails directly, or at control level where, if the predecessor is missing, a pending mandatory predecessor entry is added and the occurrence remains in waiting status. If no predecessor matches the specified criteria, the successor operation will not start until it is manually unblocked by the operator. The mandatory dependency resolution mechanism does not apply to conditional or cross dependencies. Copyright IBM Corp. 1991,

4 Dependencies are defined in the database and resolved in the plans (long-term, current, and daily). In the long-term and daily plans, they are resolved when the batches run. In the current plan, they are resolved when occurrences are added dynamically through PIF, ETT, ISPF, or the Dynamic Workload Console. You can configure Tivoli Workload Scheduler for z/os to comply with Federal Information Processing Standards (FIPS) standard over SSL secured connections. A new parameter named ENABLEFIPS was added to the initialization statements on the Tivoli Workload Scheduler for z/os controller. You can adopt the Workload Service Assurance (WSA) with prioritization on z-centric jobs. This will permit an automatic promotion of the z-centric jobs that are on a critical path and are late. The integration with IBM Tivoli Monitoring now uses a new customizable IBM Tivoli Monitoring agent instead of the Universal Agent for monitoring. Starting from version 9.1, the integration between Tivoli Workload Scheduler and IBM Tivoli Monitoring requires the installation of a new customizable agent, the IBM Tivoli Monitoring agent for Tivoli Workload Scheduler. This agent replaces the Universal Agent used in previous versions. The new agent must be installed on the systems that you want to monitor, and it collects and distributes data to the Tivoli Enterprise Monitoring Server. For information about Tivoli Workload Scheduler for z/os Version 9 Release 1, Modification Level 0 functions, see Tivoli Workload Automation Overview, SC If you are working in an end-to-end environment, depending on the type of configuration you have, see the following publications: Scheduling End-to-end with z-centric Capabilities, SC , if you are working with agents connected to the z/os controller. Scheduling End-to-end with Fault-Tolerant Capabilities, SC , if you are working with agents connected to the z/os server. 4

5 Ensuring the compatibility of the new default security certificates Tivoli Workload Scheduler for z/os Version 9 Release 1, Modification Level 0 comes with new default SSL certificates that are valid until the year The default security certificates provided with previous Tivoli Workload Scheduler for z/os versions expire on 10 February Since the Version 9.1 default certificates are not backward compatible, you must ensure, if in your network you run any earlier versions of the z-centric agents, dynamic domain managers and master domain managers, or other components to which the z/os controller is connected through cross dependencies, that they are patched with the new certificates. If you install the version 9.1 Tivoli Workload Scheduler for z/os controller directly, or migrate it from an older version (which may or may have not been patched with PTF UK90065), and run the EQQRCERT sample job, the controller will point to the new default SSL certificates. Attention: as the controller uses the new default certificates, it is no longer able to communicate with any other components in the network - that is, Tivoli Workload Scheduler for z/os agents, dynamic domain managers and master domain managers, or any other components to which it may be connected through cross dependencies - that are older than version 9.1 and have not been patched with the new default certificates. You must therefore patch your older components in the network and activate the new default security certificates before they expire. To activate the new certificates, before you migrate to Version 9.1, ensure that the following conditions are met: You are already using the security certificates connected with the EQQRING key ring or you are planning to use them. The old security certificates have not expired. On any other connected z/os controller that is not Version 9.1 you have installed PTF UK On the Tivoli Workload Scheduler components, you have installed either of the following: Tivoli Workload Scheduler V8.6 Fix Pack 2 or later The Fix Packs related to Tivoli Workload Scheduler V8.5 or V8.5.1 The version_number-tiv-twa-certificates package downloadable from the IBM Fix Central support site. and have run the related manual steps. Copyright IBM Corp. 1991,

6 6

7 Interoperability This section contains information about the interoperability of Tivoli Workload Scheduler for z/os Version 9 Release 1, 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 1, Modification Level 0 engine requires the Tivoli Dynamic Workload Console version The z/os Connector version is automatically installed when you install the Tivoli Dynamic Workload Console version Note: For detailed system requirements refer to System Requirements for Dynamic Workload Console version 9.1: 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.1 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,

8 Operating system Microsoft Windows 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 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 Server 2012 Red Hat 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

9 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 connector TWS for z/os Agent , 8.6.0, , 8.5.0, 8.5.1, 8.6.0, FTA 8.5.1, 8.6.0, , 8.5.0, 8.5.1, 8.6.0, , 8.6.0, , 8.5.0, 8.5.1, 8.6.0, N/A 8.4.0, 8.5.0, 8.5.1, 8.6.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 10

11 Additional Software This section contains information about the additional software distributed with Tivoli Workload Scheduler for z/os Version 9 Release 1, Modification Level 0 via CD/DVD support: LCD IBM Tivoli Workload Scheduler for z/os TEP Integration and Reporting features Agent for multiplatform The installation CD contains the following directories: SendReportMacro: contains the macro to send via reports generated by running batch programs. Reporting: contains the scripts used for DB2 reporting. TEPIntegration: contains the scripts used for ITM/TEP (IBM Tivoli Monitoring/Tivoli Enterprise Portal) integration. LK4T IBM Tivoli Dynamic Workload Console, zconn, and SDK Kit LCD IBM Tivoli Workload Scheduler for z/os Dynamic Workload Console, z/os Connector for AIX LCD IBM Tivoli Workload Scheduler for z/os Dynamic Workload Console, z/os Connector, and TWS Integration Workbench for Windows X86-64 LCD IBM Tivoli Workload Scheduler for z/os Dynamic Workload Console, z/os Connector, and TWS Integration Workbench for Linux X86-64 LCD IBM Tivoli Workload Scheduler for z/os Dynamic Workload Console, z/os Connector for Linux S390 LCD IBM Tivoli Workload Scheduler Batch Reports LCD IBM DB Enterprise Server Edition - for Linux on AMD64 and Intel EM64T systems (x64) LCD IBM DB Enterprise Server Edition - for Linux on POWER (System i and System p) systems LCD IBM DB Enterprise Server Edition - for Linux on System z LCD IBM DB Enterprise Server Edition - for 64-bit AIX LCD IBM DB Enterprise Server Edition - for HP-UX on HP Integrity Itanium-based systems LCD IBM DB Enterprise Server Edition - for Solaris on UltraSPARC systems LCD IBM DB Enterprise Server Edition - for Solaris on x64 systems LCD IBM DB Enterprise Server Edition - for Windows on 32-bit AMD and Intel systems (x86) Copyright IBM Corp. 1991,

12 LCD IBM DB Enterprise Server Edition - for Windows on AMD64 and Intel EM64T systems (x64) LCD IBM DB Enterprise Server Edition - Restricted Use - Quick Start and Activation 12

13 Known Problems None IBM is the registered trademark of International Business Machines Corporation. Copyright IBM Corp. 1991,

14 IBM July 2013 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, 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. GC