Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Infrastructure
Infrastructure
Technical Services
November
November2014
2014| Nordic
| Nordic
TWS
TWS
Conference
Conference
IBM
IBM
Copenhagen
Copenhagen
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
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:
In the IBM Support Newsletter for TWS for z/OS: November 2014
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!
TWS Upgrade - 2
TWS Upgrade - 3
Decide migration strategy for TWS MDM, BMDM, Agents (FTAs & Dynamic Agents)
TWS Upgrade - 4
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
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
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 dont have much here but maybe SimCorp can share some of their experiences
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
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
10
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
11
RACF
TWS resources to be defined: RG and RG.*
(Run-cycle groups TWS for z/OS 9.1)
12
13
14
15
Create switch log job in TWS for z/OS to switch e.g every day at midnight
16