slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
TWS for z/OS Release Upgrade PowerPoint Presentation
Download Presentation
TWS for z/OS Release Upgrade

TWS for z/OS Release Upgrade

415 Views Download Presentation
Download Presentation

TWS for z/OS Release Upgrade

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Angelo D’Ambrosio & Giuseppe Longobardi – TWA customer support team TWS for z/OSRelease Upgrade

  2. The Agenda • Brief overview about the upgrade process • Suggestions • Switching from the end-to-end to the Z centric during the upgrade • Q&A 2

  3. The release upgrade process The upgrade process can be summarized in the following main activities: • Preparation • Ensure you have the required environment for TWS release to be installed • SMP/E code download • Installation • TWS SMP/E code installation & patching • Run EQQJOBS CLIST • Datasets conversion • Run EQQICTOP • Configuration of the new TWS release • EQQPARM setting • SYS1.PARMLIB setting • Activation • Check the new release works correctly 3

  4. Preparation • JES and SMF exits supplied with Tivoli Workload Scheduler for z/OS can also track work for previous releases. The exits are always downward compatible.You might consider installing JES and SMF exits in your current production environment at least a week before you plan to migrate any of the address spaces to Tivoli Workload Scheduler for z/OS Version 8.6.0. • The EQQMINOx load module requires special attention. EQQMINOx is the scheduler's dialog interface module, it is invoked by TSO SERVICES, and passes dialog requests and data to the controller. EQQMINOx must run APF authorized, therefore it must reside in an authorized library. By this keep in mind that any unauthorized library in a STEPLIB or LIBDEF concatenation makes the entire concatenation unauthorized. So remember to identify the library where EQQMINOx resides along with the upgraded product library. 4

  5. Installation (1) • Before you migrate to Tivoli Workload Scheduler for z/OS Version 8.6 from Version 8.2, ensure you have applied at least the fix for APARs PK24633 and PK24711 on version 8.2.This is required to successfully perform a fallback migration from Tivoli Workload Scheduler for z/OS Version 8.6 to version 8.2, if necessary at any time. • If you are migrating from Tivoli Workload Scheduler for z/OS Version 8.2 to Version 8.6, note that the default value of the GDGNONST parameter has been changed from NO to YES.Refer to the OPCOPTS initialization statement in Customization and Tuning for more information about the GDGNONST parameter. • If you are migrating from version 8.2 to version 8.5.1 or from version 8.2 to 8.6,and you have not applied the fix for APAR PK36095 on your version 8.2 installation, then ensure you set TASKUSER(NO) to maintain the current behavior of your environment. With version 8.5.1 and later, the default value for TASKUSER is YES. Refer to the OPCOPTS initialization statement in Customization and Tuning for more information about the TASKUSER parameter. 5

  6. Installation (2) • If you are migrating from version 8.2 to version 8.5.1 or from version 8.2 to 8.6, and you have not applied the fix for APAR PQ85880 on your version 8.2 installation, be aware that the default setting of the CODEPAGE keyword in the SERVOPTS initialization statement continues to be IBM-137, however, for version 8.5.1 and later, if you specify a codepage value different from the default value, a check has been implemented to use the default codepage if the first four characters of the codepage you specify are different from "IBM-". Refer to the SERVOPTS initialization statement in Customization and Tuning for additional info about CODEPAGE. • When running the EQQJOBS built JCL samples to allocate the new datasets, perform careful checks about their results and verify output logs.This is important because the datasets record length can change release by release. An issue related to the record length can lead to severe and unpredictable errors.Use EQQICTOP sample to run the upgrade of VSAM datasets • If you want to upgrade DB2 history data that is already defined, you only need to run the EQQICNVH sample. Otherwise, if you want to create a new DB2 database, tables, and indexes, you need only run the EQQINIDB sample 6

  7. Installation (3) Note that some problems have been fixed after TWS for z/OS 8.6.0 code was frozen, in the RTM phase. Also some APARs were fixed on TWSz 8.5.1 in the same time frame. All these fixes have been made available through the following HYPER APARs: • PM43014 (TWSD AGENT FOR Z/OS) • PM42987 (E2E and z/Connector) • PM42994 (NLS) • PM46822 (END-TO-END ISSUES) • PM46490 (PANELS & MESSAGES ISSUES) • PM46497 (PIF & BATCH INTERFACES ISSUES) • PM46504 (VARIOUS ISSUES) • PM46590 (JCL VARIABLE AND JCL HANDLER ISSUES) • PM46809 (CRITICAL PATH ISSUES) • PM47032 (ZCENTRIC AND TEP ISSUES) • PM47130 (MCP AND PLANNING ISSUES) • PM47271 (AR, AUDIT, R&C ISSUES) 7

  8. Configuration (1) When specifying on the first subsystem start the rebuild SSX option, specify: • BUILDSSX(REBUILD) • SSCMNAME(EQQSSCMJ,TEMPORARY) on the OPCOPTS initialization statement. Note: the new suffix letter used in TWS for z/OS 8.6.0: “J” 8

  9. TWA Study Tour 08/11/2011 Configuration (2) When updating with the new product libraries, the TSO logon profile of users running the TWS dialogs, remember that if you want to use the Advanced ISPF panels you need to: • Allocate the new DD: • The library containing the new templates • EQQTMPLSEQQLENU data set – The library containing Advanced ISPF panels• ISPPLIB SEQQGENU data set • Choose new panel style setting yes in option 0.8: 9

  10. Activation • As starting point it is fundamental to check the message log for Controller, Tracker and Server: the return codes for all initialization options must be 0 (messages EQQZ016I). All required subtasks needs to be activated (messages EQQZ005I). It is important to verify that tracker is collecting job tracking-event information and writing it to the event data set (EQQEVDS). • If the TWS system to be upgraded has either the e2e or the Z centric feature active, it is important to verify that each feature works correctly once that the TWS for z/OS engine upgrade process has been completed. Possible tests are: • Submit and track test jobs scheduled on FTWS or Z centric WS • Link / unlink a fault tolerant agent • Such kind of “health check” have to be performed for the other distributed components that can be integrated with a TWS for z/OS engine, such as: • The ITM universal agent; • The TDWC (Tivoli Dynamic workload console). 10

  11. Suggestions • Carefully examine any customization that your site has installed. • Determine whether the function is now provided in the product or if you need to modify the logic based on changes made to Tivoli Workload Scheduler for z/OS. • Ensure that any “internally grown” tool (ex. PIF based) runs the same level of software (code and messages) as the upgraded subsystem address space and eventually uses any “new” defined subsystem name. • Leverage on shipped product tools, for further massive changes to data basesfor ex. between prod and test environment: • Mass Update (ex. For changes to the application/job description text in the AD) • BCIT and BL (ex for changes to AD and CP and for data un-load and re-load) 11

  12. Switching from e2e to Z centric The upgrade process can be usefully exploited to more easily switch from the e2e to Z centric feature.Here after a very brief description of the additional steps to be added in the upgrade process to obtain this result: • The process foresees an LTP refresh, so it can be performed only if all the job in CP are completed. This is the first check to be performed. • Following the instructions reported on the manual “Scheduling end-to-end with z-centric capabilities”, perform the steps needed to change the script library and/or the job library members used for the e2e feature to make them compatible for the Z centric. • Before stopping the TWS for z/OS controller to be upgraded, refresh the long term plan from the TWS ISPF menu 9.5. • Run EQQJOBS to create the new datasets; • By using the EQQICTOP sample run the upgrade of VSAM datasets: • EQQADDS • EQQRDDS • EQQSIDS • EQQLTDS • EQQWSDS • EQQOIDS • Immediately after the activation of the new TWS for z/OS controller, change (from the 1.1.2 ISPF menu) all the FTWSs, raising the Z-CENTRIC AGENT flag. So to make them z centric WSs. • Create the current plan. 12

  13. 13