Twszos Twsd Upgrade

IBM Infrastructure Technical Services

November 2014 | Nordic TWS Conference IBM Copenhagen © 2014 IBM Corporation

IBM Technical Infrastructure Services

November 2014 | Nordic TWS Conference IBM Copenhagen © 2014 IBM Corporation

Upgrade considerations for

TWS for z/OS and TWS Decentralised

Finn Bastrup Knudsen, IBM Denmark A/S

[email protected]


Upgrade considerations for TWS for z/OS and for TWS © 2014 IBM Corporation2

Some general notes – getting started – and get a good start

Always very good to follow all the important news from IBM– For example:

– IBM Support Newsletter for Tivoli Workload Scheduler: November 2014

– IBM Support Newsletter for TWS for z/OS: November 2014

Take a look at IBM Knowledge Center– http://www-01.ibm.com/support/knowledgecenter/SSGSPN_9.2.0/com.ibm.tivoli.itws.doc_9.2/twa_landing.html

– For example:

– Read the overview and check Summary of enhancements

– Download all the manuals in pdf format from the product library

– For decentralized check “Download Documents, Systems Requirements and Release Notes:

http://www-01.ibm.com/support/knowledgecenter/SSGSPN_9.2.0/com.ibm.tivoli.itws.doc_9.2/twa_landing.html



TWS for z/OS Upgrade

In the IBM Support Newsletter for TWS for z/OS: November 2014

http://www-01.ibm.com/support/docview.wss?uid=swg21608030&lnk=uctug_tivoli_nwsltr_TWSZOS&acss=danl_1424_email



TWS Upgrade - 1

No direct upgrade path from TWS 8.4.0, TWS 8.5.0 or TWS 8.5.1 to TWS 9.2.0!

– You have to decide what to do and how to upgrade to TWS 9.2.0

– In IBM Support Newsletter for Tivoli Workload Scheduler: November 2014

http://www-01.ibm.com/support/docview.wss?uid=swg21685948&lnk=uctug_tivoli_nwsltr_TWS&acss=danl_1440_email



TWS Upgrade - 2

Getting started with TWS in general …..

– In IBM Support Newsletter for Tivoli Workload Scheduler: November 2014

http://www-01.ibm.com/support/docview.wss?uid=swg21657701&lnk=uctug_tivoli_nwsltr_TWS&acss=danl_1440_email



TWS Upgrade - 3 I’m sorry – read chapter 6 in TWS Planning and Installation V 9.2

– Decide migration strategy for TWS MDM, BMDM, Agents (FTA’s & Dynamic Agents)



TWS Upgrade - 4

And remember – it isn’t that complicated - but

– From version 8.4, 8.5.0, 8.5.1 and 8.6.0 to version 9.1 or 9.2 TDWC infrastructure changes

– Not eWAS anymore but “standard stand-alone WAS”

– Start with TDWC upgrade before upgrading TWS MDM, BMDM and agents=> This is also the case if TDWC is used for TWS for z/OS GUI access

– What about the database used for TWS?

– Is it necessary to upgrade the database version as well?

– When should it be done?

– At same time as TWS upgrade or before/after?

– Is it time to change Operating System (OS) level and/or TWS infrastructure or?

– How long time do you have to upgrade the TWS MDM and BMDM and when to do it

– Consider to establish a “new” TWS BMDM and switch to it when performing the upgrade

– This is “parallel upgrade”

– Maybe –Don't upgrade. Install new, fresh, and migrate the data. You'll get better performance and fewer headaches.


Upgrade considerations for TWS for z/OS and for TWS © 2014 IBM Corporation

Practical Upgrade Experiences

8

TWS for z/OS 9.2.0

– System Automation Workstations in status UNKNOWN when Controller task is started

– APAR PI26895

– EWTROPTS parameter HOLDJOB(YES) not working as expected when using z/OS 2.1

– APAR PI24927

– If using HOLDJOB(YES) please avoid migrating to z/OS 2.1 until the fix for APAR PI24927

is installed

TWS

– I don’t have much here – but maybe SimCorp can share some of their experiences



TWS for z/OS Upgrade notes from real life - 1

From TWS 8.5.1 or TWS 8.6.0 to TWS 9.1.0

– ALWAYS run EQQJOBS to recreate

– JCL and skeleton

Added in or at TWS for z/OS 8.6.0

– Datasets:

– EQQLOGRC

=> Allocated by EQQPCS01 Job and must add to Controller Start Procedure JCL

– EQQXDnDS, EQQNXDDS

=> Allocated by EQQPCS01 Job and must add to Controller Start Procedure JCL as well

=> as to CP Extend/Replan/Trial job JCL

– EQQTMPL

=> Add to TSO LOGON Procedure JCL or CLIST

– Parameters

– JTOPTS

=> MAXJSFILE Unit Change from KB to MB




Added at TWS for z/OS 8.5.1:

– Datasets

– EQQHTTP0

=> Allocated by EQQPCS02 Job and add to Controller Start Procedure JCL

– Parameters

– TCPOPTS

=>CONNTIMEOUT Default changed from 15 to 60

– SPE (Small Program Enhancements)

=> PM14386

http://eclient.lenexa.ibm.com:9082/search/?fetch=source/APAR/PM14366




Added at TWS for z/OS 8.5.0:

– Datasets

– EQQEVLIB

=> Allocated by EQQPCS01 Job and must add to Controller Start Procedure JCL

– LTPRIN/LTPROUT LRECL/BLKSIZE changed

=> Temporary dataset allocated by LTP Extend/Modify/Trial/Print Job JCL

=> RECL changed from 65 to 66, BLKSIZE changed from 4550 to 4620

=> Must Modify LTP Extend/Modify/Trial/Print job JCL

=> APAR - PK96855 AVOID LOSS OF EXTERNAL DEPENDENCIES

– Parameters

– SERVOPTS

=> PROTOCOL Changed from JSC to TCP

– DSTOPTS

=> DSTHIGHJOBID and DSTLOWJOBID deleted

– MONOPTS

=> CONNTIMEOUT/LOCHOSTNAME deleted

– MONPOL

=> OPERATION(CRITPATH) deleted and integrated to CRITICAL

– SPE

– None




And remember

– RACF

– TWS resources to be defined: RG and RG.*(Run-cycle groups TWS for z/OS 9.1)

– Controller Started Task Procedure:

//EQQHTTP0 DD DISP=SHR,DSN=SYS4.TWS.HTEV

//EQQXD1DS DD DISP=SHR,DSN=SYS4.TWS.XD1


//EQQNXDDS DD DISP=SHR,DSN=SYS4.TWS.NXD

//EQQLOGRC DD DISP=SHR,DSN=SYS4.TWS.LOGRC

//EQQMONDS DD DISP=SHR,DSN=SYS4.TWS.MONDS

//EQQJTABL DD DISP=SHR,DSN=SYS4.TWS.JTAB

– TWS maintenance or plan jobs – LTPMA and LTPEXT:

//LTPRED3 DD DCB=(RECFM=FB,LRECL=100,BLKSIZE=6300),

// SPACE=(4620,(300,300)),UNIT=SYSDA0

//LTPRIN DD DCB=(RECFM=FB,LRECL=100,BLKSIZE=6300),

// SPACE=(4620,(300,300)),UNIT=SYSDA

//LTPROUT DD DCB=(RECFM=FB,LRECL=100,BLKSIZE=6300),

// SPACE=(4620,(300,300)),UNIT=SYSDA

//LTOCIN DD DCB=(RECFM=FB,LRECL=751,BLKSIZE=4506),

// SPACE=(4410,(300,300)),UNIT=SYSDA

//LTOCOUT DD DCB=(RECFM=FB,LRECL=751,BLKSIZE=4506),

// SPACE=(4410,(300,300)),UNIT=SYSDA




And remember ………

– TWS maintenance or plan jobs: DPT, DPN and DPR

=> After EQQPARM

//EQQDIN DD DSN=&&A,DISP=(NEW,PASS),

// DCB=(RECFM=FB,LRECL=558,BLKSIZE=5580),

// SPACE=(CYL,(3,1)),UNIT=SYSDA

//DX12IN DD DCB=(RECFM=FB,LRECL=90,BLKSIZE=6300),

// SPACE=(4620,(300,300)),UNIT=3390

//DX12OUT DD DCB=(RECFM=FB,LRECL=90,BLKSIZE=6300),

// SPACE=(4620,(300,300)),UNIT=3390

=> Together with other datasets that should be added



//EQQNXDDS DD DISP=SHR,DSN=SYS4.TWS.NXD




TWS for z/OS 9.2.0 updates – 1

– More or less focus on SWITH of MLOG only

– Update PARMLIB

– ADD to OPCOPTS in Controller member

=> SWITCHMLOGLIM(10000)

=> MLOGPROCNAME(OPPCSL)

– ADD to OPCOPTS in Tracker member

=> SWITCHMLOGLIM(10000)

=> MLOGPROCNAME(OPPTSL)

– Add member EQQREPRO with the contents

=> REPRO INFILE(FILEIN) OFILE(FILEOU)

– Update in SYS1.PROCLIB

– ADD member OPPCSL

– ADD member OPPTSL





– Change Controller Started Task procedure

– Change EQQMLOG dataset and add EQQMLOG2

//EQQMLOG DD DISP=SHR,

// DSN=SYS4.TWS.MLOGC.MVS&CL..ACTIVE

//EQQMLOG2 DD DISP=SHR,

// DSN=SYS4.TWS.MLOGC.MVS&CL..ACTIVE2

– Change Tracker Started Task procedure

– Change EQQMLOG dataset and add EQQMLOG2

//EQQMLOG DD DISP=SHR,

// DSN=SYS4.TWS.MLOGW.MVS&CL..ACTIVE

//EQQMLOG2 DD DISP=SHR,

// DSN=SYS4.TWS.MLOGW.MVS&CL..ACTIVE2





– Create switch log job in TWS for z/OS to switch e.g every day at midnight

– Create OPPCSLC ( Switch log controller )

– Create OPPCSLT ( Switch log writer / tracker )

– With following content:

//ST03 EXEC PGM=SDSF

//ISFOUT DD DUMMY

//ISFIN DD *

/F OPPC,SWITCHMLOG

– Create TWS for z/OS job to copy the switched and “archived” MLOGs

– Content:

//*%OPC SCAN

//*%OPC SETFORM OCDATE=(YYMMDD)

//*%OPC SETVAR TDATE1=(OCDATE-1CD)

//COPY EXEC PGM=IEBGENER,TIME=10

//SYSPRINT DD SYSOUT=*

//SYSUT1 DD DSN=SYS4.TWS.MLOGCGDG(0), DISP=SHR

//SYSUT2 DD DSN=SYS4.TWS.MLOGC.D%TDATE1,DISP=(,CATLG),

// UNIT=SYSDA,SPACE=(CYL,(1,2),RLSE)

//SYSIN DD DUMMY