zos v1r13 migration to r13 part1
TRANSCRIPT
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 130
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 230
Migrating to zOS R13 - Part 1 of 3 Agenda
bull Content of zOS R13
bullChanging and Withdrawn Elements and Features
bull zOS Ordering and Deliverables
bullProducts Related to zOSbull zOS Policies
bullzOS End of Service dates
bullzOS Coexistence-Migration-Fallback
bull Planning for zOS R13
bullEnsuring System Requirements are Satisfied
bullDriving and Target System Requirements
bullCoexistence System Requirements
bullProgrammatic Verification is Available
bullMigration Actions You Can Do NOW
bullProgrammatic Verification of Migration Actions for zOS R13 copy 2003 IBM Corporation
bullInstallation Enhancements for zOS R13Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
2 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 2 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 330
copy 2012 IBM Corporation3 Migrating to zOS R13 - Part 1 of 3
Structure of Migrating to zOS R13 Presentations
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
bull Session Part 1 of 3
bullContent is what you just saw on the previous slide
bull Session Part 2 of 3
bullMigrations actions for zOS R13 and R12 from selected elements
bullGeneral migration actionsbullBCP
bullCommunications Server
bullDFSMS
bullInfoprint Server
bullSystem SSL and TSOE
bull Session Part 3 of 3
bullMigrations actions for zOS R13 and R12 from selected elements
bullDistributed File Service
bullJES2 and JES3
bullLanguage Environment
bullzOS UNIXbullSMPE and ServerPac Installation Enhancements
bullSome Helpful zOS R13 Sysprog Enhancements
zOS_V1R13_Migration-to-R13-Part1ppt Page 3 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 430
Scope
bull Focus on Migrating to zOS R13 from zOS R12 and R11
If migrating to a new server level see
bullfor z890 and z990 migration action in zOS MigrationMigrate to a z990 or z890 server
bullfor z9 EC and BC migration action in zOS MigrationMigrate to a System z9 server
bullfor z10 EC and BC migration action in zOS MigrationMigrate to a System z10 serverldquo
bullfor z196 and z114 migration action in zOS MigrationMigrate to an IBM zEnterprise serverldquo or attend session
ldquozOS Software Positioning for the zEnterprise (z196 or z114) Serverrdquo
4 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
copy 2007 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 4 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 530
copy 2007 IBM Corporation art 1 of 3 Get Ready
zOS R13 Changing Elements (from zOS R11 and R12)
SDSF
Security Server - RACF
SMPE (V3R6)
TSOE
zOS Security Level 3
BCP
CC++ Without Debug Tool
Common Information Model(CIM)
Communications Server
Communications Server SecurityLevel 3
Cryptographic Services
ICSF (FMID HCR7780)
PKI Services
System SSL
DFSMSdfp
DFSMSdss
DFSMShsm
DFSMSrmm
DFSMStvs
DFSORT
Distributed File Service
HCD
HCM IBM Tivoli Directory Server
Infoprint Server
zOS UNIX
KEY
1048573 Black (in bold) are base elements
1048573 Green (also in bold) are optional priced features
1048573 Brown (also in italics ) are optional unpriced features with exportcontrols
This element changed in zOS R13 (from zOS R11)
This element changed in zOS R13 (from zOS R12) copy 2003 IBM Corporation
All other elements not listed have not changed since z OS R11
There are no new elements since zOS R9
copy 2012 IBM Corporation
Migrating to zOS R8 P
5 Migrating to zOS R13 - Part 1 of 3
Integrated Security Services
Network AuthenticationService
ISPF
JES2
JES3
Language Environment
Library Server
Metal C Runtime Library
Network File System
RMF
Run-Time Library Extensions
IBM Tivoli DirectoryServer Security Level 3
Network AuthenticationService Level 3
SSL Level 3
zOS_V1R13_Migration-to-R13-Part1ppt Page 5 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 630
copy 2 0 12 I B M C o r o ra t o nM r at n t o z O S R 1 3 P a rt 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
Migrating to zOS R8 Part 1 of 3 G et Ready
Optional setting for Base Element ndash All IP security filters must As of R12
RFC4301 compliance (from be compliant with RFC4301 You can noCommunications Server) longer use the RFC4301Compliance
parameter on the IpFilterPolicy statementmig to specify whether Policy Agent enforces
compliance It is ignored and the PolicyAgent will enforce the rule that all IP filtersare compliant
CSVRTLS services in the Base Element support ndash LE RTLS support As of R12BCP for Language was removed in zOS R5 BCP RTLSEnvironment RunTime services (SET RTLS DISPLAY RTLS
Library Services RTLS in IEASYSxx and CSVRTLSxx andCSVRTLS macro) are removed in zOS
R12 Usage tracking assistance is
provided in OA29995 (R11) and OA29019(R10)
msys for Setup Base Element ndash CBPDO users should run
job CLNOS390 ServerPac users do notneed to do anything
As of R12
Element and Functions Withdrawn from zOS R12
ig i g - p i
zOS_V1R13_Migration-to-R13-Part1ppt Page 6 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 730
copy 2003 IBM CorporationfInfInInfo
i
Migrating to zOS R8 Part 1 of 3 G et Ready
zOS UNIX ConnectionManager and Process
Manager
Base Element In zOS R13
DCE and DCE Security
Server
Base Elements ndash IBM WebSphere
Application Server the IBM NetworkAuthentication Service andor theIBM Directory Server asreplacement strategies for each of
the DCE technologies
In zOS R13
DFS support that usesthe DCE architecture
mig
Base Element support ndash zOS
Network File System (NFS)implementation as the replacement
In zOS R13
Element and Functions Withdrawn from zOS R13
copy 2007 IBM Corporat on
7 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 7 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 830
copy 2012 IBM CorporatonM gratng to z OS R13 Par t 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
i
i
i
ii i
Functions Planned to be Withdrawnin the release after zOS R13hellip
zFS multi-file system aggregates(from Distributed File Service)
m g
Base Element ndash copy zFS multi-file system aggregates to zFScompatibility mode aggregates
In the releaseafter zOS R13
zFS cloning support (such aszfsadm clone and zfsadm
clonesys commands) Do not
mount file systems containing a
cloned file system (bak)
Base elements ndash when support for cloning is removed only zFScapability mode aggregates will be supported Find (with
modify zfsquery command) and copy any cloned files to
compatibility mode aggregrates
In the releaseafter zOS R13
BIND 920 function (from theCommunications Server)
Base Element support ndash for use as a caching-only name serveruse Resolver cache function (in zOS R11) For use as a
primary or secondary authoritative name server consider using
BIND on Linux for System z
In the releaseafter R13
BPXDEFAULTUSERm g
Base Element support ndash use BPXUNIQUEUSER instead (as ofR11) or assign unique UIDs and GIDs
In the releaseafter R13
Capacity Provisioning usingSystem z API with SE and HMC
Base Element support ndash will use BCPii instead System z APIwill still be supported on the SE and HMC Use Tracking
Facility with OA35284 Look for ldquoCPO-WSNMP usage domainname rdquo
In the releaseafter R13
Language Environment runtimeoptions via USERMOD
m g
Base Element support ndash use CEEPRMxx instead (with zOSR12 NONOVR support if necessary)
In the releaseafter R13
-
zOS_V1R13_Migration-to-R13-Part1ppt Page 8 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 230
Migrating to zOS R13 - Part 1 of 3 Agenda
bull Content of zOS R13
bullChanging and Withdrawn Elements and Features
bull zOS Ordering and Deliverables
bullProducts Related to zOSbull zOS Policies
bullzOS End of Service dates
bullzOS Coexistence-Migration-Fallback
bull Planning for zOS R13
bullEnsuring System Requirements are Satisfied
bullDriving and Target System Requirements
bullCoexistence System Requirements
bullProgrammatic Verification is Available
bullMigration Actions You Can Do NOW
bullProgrammatic Verification of Migration Actions for zOS R13 copy 2003 IBM Corporation
bullInstallation Enhancements for zOS R13Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
2 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 2 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 330
copy 2012 IBM Corporation3 Migrating to zOS R13 - Part 1 of 3
Structure of Migrating to zOS R13 Presentations
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
bull Session Part 1 of 3
bullContent is what you just saw on the previous slide
bull Session Part 2 of 3
bullMigrations actions for zOS R13 and R12 from selected elements
bullGeneral migration actionsbullBCP
bullCommunications Server
bullDFSMS
bullInfoprint Server
bullSystem SSL and TSOE
bull Session Part 3 of 3
bullMigrations actions for zOS R13 and R12 from selected elements
bullDistributed File Service
bullJES2 and JES3
bullLanguage Environment
bullzOS UNIXbullSMPE and ServerPac Installation Enhancements
bullSome Helpful zOS R13 Sysprog Enhancements
zOS_V1R13_Migration-to-R13-Part1ppt Page 3 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 430
Scope
bull Focus on Migrating to zOS R13 from zOS R12 and R11
If migrating to a new server level see
bullfor z890 and z990 migration action in zOS MigrationMigrate to a z990 or z890 server
bullfor z9 EC and BC migration action in zOS MigrationMigrate to a System z9 server
bullfor z10 EC and BC migration action in zOS MigrationMigrate to a System z10 serverldquo
bullfor z196 and z114 migration action in zOS MigrationMigrate to an IBM zEnterprise serverldquo or attend session
ldquozOS Software Positioning for the zEnterprise (z196 or z114) Serverrdquo
4 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
copy 2007 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 4 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 530
copy 2007 IBM Corporation art 1 of 3 Get Ready
zOS R13 Changing Elements (from zOS R11 and R12)
SDSF
Security Server - RACF
SMPE (V3R6)
TSOE
zOS Security Level 3
BCP
CC++ Without Debug Tool
Common Information Model(CIM)
Communications Server
Communications Server SecurityLevel 3
Cryptographic Services
ICSF (FMID HCR7780)
PKI Services
System SSL
DFSMSdfp
DFSMSdss
DFSMShsm
DFSMSrmm
DFSMStvs
DFSORT
Distributed File Service
HCD
HCM IBM Tivoli Directory Server
Infoprint Server
zOS UNIX
KEY
1048573 Black (in bold) are base elements
1048573 Green (also in bold) are optional priced features
1048573 Brown (also in italics ) are optional unpriced features with exportcontrols
This element changed in zOS R13 (from zOS R11)
This element changed in zOS R13 (from zOS R12) copy 2003 IBM Corporation
All other elements not listed have not changed since z OS R11
There are no new elements since zOS R9
copy 2012 IBM Corporation
Migrating to zOS R8 P
5 Migrating to zOS R13 - Part 1 of 3
Integrated Security Services
Network AuthenticationService
ISPF
JES2
JES3
Language Environment
Library Server
Metal C Runtime Library
Network File System
RMF
Run-Time Library Extensions
IBM Tivoli DirectoryServer Security Level 3
Network AuthenticationService Level 3
SSL Level 3
zOS_V1R13_Migration-to-R13-Part1ppt Page 5 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 630
copy 2 0 12 I B M C o r o ra t o nM r at n t o z O S R 1 3 P a rt 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
Migrating to zOS R8 Part 1 of 3 G et Ready
Optional setting for Base Element ndash All IP security filters must As of R12
RFC4301 compliance (from be compliant with RFC4301 You can noCommunications Server) longer use the RFC4301Compliance
parameter on the IpFilterPolicy statementmig to specify whether Policy Agent enforces
compliance It is ignored and the PolicyAgent will enforce the rule that all IP filtersare compliant
CSVRTLS services in the Base Element support ndash LE RTLS support As of R12BCP for Language was removed in zOS R5 BCP RTLSEnvironment RunTime services (SET RTLS DISPLAY RTLS
Library Services RTLS in IEASYSxx and CSVRTLSxx andCSVRTLS macro) are removed in zOS
R12 Usage tracking assistance is
provided in OA29995 (R11) and OA29019(R10)
msys for Setup Base Element ndash CBPDO users should run
job CLNOS390 ServerPac users do notneed to do anything
As of R12
Element and Functions Withdrawn from zOS R12
ig i g - p i
zOS_V1R13_Migration-to-R13-Part1ppt Page 6 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 730
copy 2003 IBM CorporationfInfInInfo
i
Migrating to zOS R8 Part 1 of 3 G et Ready
zOS UNIX ConnectionManager and Process
Manager
Base Element In zOS R13
DCE and DCE Security
Server
Base Elements ndash IBM WebSphere
Application Server the IBM NetworkAuthentication Service andor theIBM Directory Server asreplacement strategies for each of
the DCE technologies
In zOS R13
DFS support that usesthe DCE architecture
mig
Base Element support ndash zOS
Network File System (NFS)implementation as the replacement
In zOS R13
Element and Functions Withdrawn from zOS R13
copy 2007 IBM Corporat on
7 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 7 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 830
copy 2012 IBM CorporatonM gratng to z OS R13 Par t 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
i
i
i
ii i
Functions Planned to be Withdrawnin the release after zOS R13hellip
zFS multi-file system aggregates(from Distributed File Service)
m g
Base Element ndash copy zFS multi-file system aggregates to zFScompatibility mode aggregates
In the releaseafter zOS R13
zFS cloning support (such aszfsadm clone and zfsadm
clonesys commands) Do not
mount file systems containing a
cloned file system (bak)
Base elements ndash when support for cloning is removed only zFScapability mode aggregates will be supported Find (with
modify zfsquery command) and copy any cloned files to
compatibility mode aggregrates
In the releaseafter zOS R13
BIND 920 function (from theCommunications Server)
Base Element support ndash for use as a caching-only name serveruse Resolver cache function (in zOS R11) For use as a
primary or secondary authoritative name server consider using
BIND on Linux for System z
In the releaseafter R13
BPXDEFAULTUSERm g
Base Element support ndash use BPXUNIQUEUSER instead (as ofR11) or assign unique UIDs and GIDs
In the releaseafter R13
Capacity Provisioning usingSystem z API with SE and HMC
Base Element support ndash will use BCPii instead System z APIwill still be supported on the SE and HMC Use Tracking
Facility with OA35284 Look for ldquoCPO-WSNMP usage domainname rdquo
In the releaseafter R13
Language Environment runtimeoptions via USERMOD
m g
Base Element support ndash use CEEPRMxx instead (with zOSR12 NONOVR support if necessary)
In the releaseafter R13
-
zOS_V1R13_Migration-to-R13-Part1ppt Page 8 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 330
copy 2012 IBM Corporation3 Migrating to zOS R13 - Part 1 of 3
Structure of Migrating to zOS R13 Presentations
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
bull Session Part 1 of 3
bullContent is what you just saw on the previous slide
bull Session Part 2 of 3
bullMigrations actions for zOS R13 and R12 from selected elements
bullGeneral migration actionsbullBCP
bullCommunications Server
bullDFSMS
bullInfoprint Server
bullSystem SSL and TSOE
bull Session Part 3 of 3
bullMigrations actions for zOS R13 and R12 from selected elements
bullDistributed File Service
bullJES2 and JES3
bullLanguage Environment
bullzOS UNIXbullSMPE and ServerPac Installation Enhancements
bullSome Helpful zOS R13 Sysprog Enhancements
zOS_V1R13_Migration-to-R13-Part1ppt Page 3 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 430
Scope
bull Focus on Migrating to zOS R13 from zOS R12 and R11
If migrating to a new server level see
bullfor z890 and z990 migration action in zOS MigrationMigrate to a z990 or z890 server
bullfor z9 EC and BC migration action in zOS MigrationMigrate to a System z9 server
bullfor z10 EC and BC migration action in zOS MigrationMigrate to a System z10 serverldquo
bullfor z196 and z114 migration action in zOS MigrationMigrate to an IBM zEnterprise serverldquo or attend session
ldquozOS Software Positioning for the zEnterprise (z196 or z114) Serverrdquo
4 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
copy 2007 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 4 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 530
copy 2007 IBM Corporation art 1 of 3 Get Ready
zOS R13 Changing Elements (from zOS R11 and R12)
SDSF
Security Server - RACF
SMPE (V3R6)
TSOE
zOS Security Level 3
BCP
CC++ Without Debug Tool
Common Information Model(CIM)
Communications Server
Communications Server SecurityLevel 3
Cryptographic Services
ICSF (FMID HCR7780)
PKI Services
System SSL
DFSMSdfp
DFSMSdss
DFSMShsm
DFSMSrmm
DFSMStvs
DFSORT
Distributed File Service
HCD
HCM IBM Tivoli Directory Server
Infoprint Server
zOS UNIX
KEY
1048573 Black (in bold) are base elements
1048573 Green (also in bold) are optional priced features
1048573 Brown (also in italics ) are optional unpriced features with exportcontrols
This element changed in zOS R13 (from zOS R11)
This element changed in zOS R13 (from zOS R12) copy 2003 IBM Corporation
All other elements not listed have not changed since z OS R11
There are no new elements since zOS R9
copy 2012 IBM Corporation
Migrating to zOS R8 P
5 Migrating to zOS R13 - Part 1 of 3
Integrated Security Services
Network AuthenticationService
ISPF
JES2
JES3
Language Environment
Library Server
Metal C Runtime Library
Network File System
RMF
Run-Time Library Extensions
IBM Tivoli DirectoryServer Security Level 3
Network AuthenticationService Level 3
SSL Level 3
zOS_V1R13_Migration-to-R13-Part1ppt Page 5 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 630
copy 2 0 12 I B M C o r o ra t o nM r at n t o z O S R 1 3 P a rt 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
Migrating to zOS R8 Part 1 of 3 G et Ready
Optional setting for Base Element ndash All IP security filters must As of R12
RFC4301 compliance (from be compliant with RFC4301 You can noCommunications Server) longer use the RFC4301Compliance
parameter on the IpFilterPolicy statementmig to specify whether Policy Agent enforces
compliance It is ignored and the PolicyAgent will enforce the rule that all IP filtersare compliant
CSVRTLS services in the Base Element support ndash LE RTLS support As of R12BCP for Language was removed in zOS R5 BCP RTLSEnvironment RunTime services (SET RTLS DISPLAY RTLS
Library Services RTLS in IEASYSxx and CSVRTLSxx andCSVRTLS macro) are removed in zOS
R12 Usage tracking assistance is
provided in OA29995 (R11) and OA29019(R10)
msys for Setup Base Element ndash CBPDO users should run
job CLNOS390 ServerPac users do notneed to do anything
As of R12
Element and Functions Withdrawn from zOS R12
ig i g - p i
zOS_V1R13_Migration-to-R13-Part1ppt Page 6 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 730
copy 2003 IBM CorporationfInfInInfo
i
Migrating to zOS R8 Part 1 of 3 G et Ready
zOS UNIX ConnectionManager and Process
Manager
Base Element In zOS R13
DCE and DCE Security
Server
Base Elements ndash IBM WebSphere
Application Server the IBM NetworkAuthentication Service andor theIBM Directory Server asreplacement strategies for each of
the DCE technologies
In zOS R13
DFS support that usesthe DCE architecture
mig
Base Element support ndash zOS
Network File System (NFS)implementation as the replacement
In zOS R13
Element and Functions Withdrawn from zOS R13
copy 2007 IBM Corporat on
7 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 7 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 830
copy 2012 IBM CorporatonM gratng to z OS R13 Par t 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
i
i
i
ii i
Functions Planned to be Withdrawnin the release after zOS R13hellip
zFS multi-file system aggregates(from Distributed File Service)
m g
Base Element ndash copy zFS multi-file system aggregates to zFScompatibility mode aggregates
In the releaseafter zOS R13
zFS cloning support (such aszfsadm clone and zfsadm
clonesys commands) Do not
mount file systems containing a
cloned file system (bak)
Base elements ndash when support for cloning is removed only zFScapability mode aggregates will be supported Find (with
modify zfsquery command) and copy any cloned files to
compatibility mode aggregrates
In the releaseafter zOS R13
BIND 920 function (from theCommunications Server)
Base Element support ndash for use as a caching-only name serveruse Resolver cache function (in zOS R11) For use as a
primary or secondary authoritative name server consider using
BIND on Linux for System z
In the releaseafter R13
BPXDEFAULTUSERm g
Base Element support ndash use BPXUNIQUEUSER instead (as ofR11) or assign unique UIDs and GIDs
In the releaseafter R13
Capacity Provisioning usingSystem z API with SE and HMC
Base Element support ndash will use BCPii instead System z APIwill still be supported on the SE and HMC Use Tracking
Facility with OA35284 Look for ldquoCPO-WSNMP usage domainname rdquo
In the releaseafter R13
Language Environment runtimeoptions via USERMOD
m g
Base Element support ndash use CEEPRMxx instead (with zOSR12 NONOVR support if necessary)
In the releaseafter R13
-
zOS_V1R13_Migration-to-R13-Part1ppt Page 8 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 430
Scope
bull Focus on Migrating to zOS R13 from zOS R12 and R11
If migrating to a new server level see
bullfor z890 and z990 migration action in zOS MigrationMigrate to a z990 or z890 server
bullfor z9 EC and BC migration action in zOS MigrationMigrate to a System z9 server
bullfor z10 EC and BC migration action in zOS MigrationMigrate to a System z10 serverldquo
bullfor z196 and z114 migration action in zOS MigrationMigrate to an IBM zEnterprise serverldquo or attend session
ldquozOS Software Positioning for the zEnterprise (z196 or z114) Serverrdquo
4 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
copy 2007 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 4 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 530
copy 2007 IBM Corporation art 1 of 3 Get Ready
zOS R13 Changing Elements (from zOS R11 and R12)
SDSF
Security Server - RACF
SMPE (V3R6)
TSOE
zOS Security Level 3
BCP
CC++ Without Debug Tool
Common Information Model(CIM)
Communications Server
Communications Server SecurityLevel 3
Cryptographic Services
ICSF (FMID HCR7780)
PKI Services
System SSL
DFSMSdfp
DFSMSdss
DFSMShsm
DFSMSrmm
DFSMStvs
DFSORT
Distributed File Service
HCD
HCM IBM Tivoli Directory Server
Infoprint Server
zOS UNIX
KEY
1048573 Black (in bold) are base elements
1048573 Green (also in bold) are optional priced features
1048573 Brown (also in italics ) are optional unpriced features with exportcontrols
This element changed in zOS R13 (from zOS R11)
This element changed in zOS R13 (from zOS R12) copy 2003 IBM Corporation
All other elements not listed have not changed since z OS R11
There are no new elements since zOS R9
copy 2012 IBM Corporation
Migrating to zOS R8 P
5 Migrating to zOS R13 - Part 1 of 3
Integrated Security Services
Network AuthenticationService
ISPF
JES2
JES3
Language Environment
Library Server
Metal C Runtime Library
Network File System
RMF
Run-Time Library Extensions
IBM Tivoli DirectoryServer Security Level 3
Network AuthenticationService Level 3
SSL Level 3
zOS_V1R13_Migration-to-R13-Part1ppt Page 5 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 630
copy 2 0 12 I B M C o r o ra t o nM r at n t o z O S R 1 3 P a rt 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
Migrating to zOS R8 Part 1 of 3 G et Ready
Optional setting for Base Element ndash All IP security filters must As of R12
RFC4301 compliance (from be compliant with RFC4301 You can noCommunications Server) longer use the RFC4301Compliance
parameter on the IpFilterPolicy statementmig to specify whether Policy Agent enforces
compliance It is ignored and the PolicyAgent will enforce the rule that all IP filtersare compliant
CSVRTLS services in the Base Element support ndash LE RTLS support As of R12BCP for Language was removed in zOS R5 BCP RTLSEnvironment RunTime services (SET RTLS DISPLAY RTLS
Library Services RTLS in IEASYSxx and CSVRTLSxx andCSVRTLS macro) are removed in zOS
R12 Usage tracking assistance is
provided in OA29995 (R11) and OA29019(R10)
msys for Setup Base Element ndash CBPDO users should run
job CLNOS390 ServerPac users do notneed to do anything
As of R12
Element and Functions Withdrawn from zOS R12
ig i g - p i
zOS_V1R13_Migration-to-R13-Part1ppt Page 6 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 730
copy 2003 IBM CorporationfInfInInfo
i
Migrating to zOS R8 Part 1 of 3 G et Ready
zOS UNIX ConnectionManager and Process
Manager
Base Element In zOS R13
DCE and DCE Security
Server
Base Elements ndash IBM WebSphere
Application Server the IBM NetworkAuthentication Service andor theIBM Directory Server asreplacement strategies for each of
the DCE technologies
In zOS R13
DFS support that usesthe DCE architecture
mig
Base Element support ndash zOS
Network File System (NFS)implementation as the replacement
In zOS R13
Element and Functions Withdrawn from zOS R13
copy 2007 IBM Corporat on
7 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 7 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 830
copy 2012 IBM CorporatonM gratng to z OS R13 Par t 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
i
i
i
ii i
Functions Planned to be Withdrawnin the release after zOS R13hellip
zFS multi-file system aggregates(from Distributed File Service)
m g
Base Element ndash copy zFS multi-file system aggregates to zFScompatibility mode aggregates
In the releaseafter zOS R13
zFS cloning support (such aszfsadm clone and zfsadm
clonesys commands) Do not
mount file systems containing a
cloned file system (bak)
Base elements ndash when support for cloning is removed only zFScapability mode aggregates will be supported Find (with
modify zfsquery command) and copy any cloned files to
compatibility mode aggregrates
In the releaseafter zOS R13
BIND 920 function (from theCommunications Server)
Base Element support ndash for use as a caching-only name serveruse Resolver cache function (in zOS R11) For use as a
primary or secondary authoritative name server consider using
BIND on Linux for System z
In the releaseafter R13
BPXDEFAULTUSERm g
Base Element support ndash use BPXUNIQUEUSER instead (as ofR11) or assign unique UIDs and GIDs
In the releaseafter R13
Capacity Provisioning usingSystem z API with SE and HMC
Base Element support ndash will use BCPii instead System z APIwill still be supported on the SE and HMC Use Tracking
Facility with OA35284 Look for ldquoCPO-WSNMP usage domainname rdquo
In the releaseafter R13
Language Environment runtimeoptions via USERMOD
m g
Base Element support ndash use CEEPRMxx instead (with zOSR12 NONOVR support if necessary)
In the releaseafter R13
-
zOS_V1R13_Migration-to-R13-Part1ppt Page 8 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 530
copy 2007 IBM Corporation art 1 of 3 Get Ready
zOS R13 Changing Elements (from zOS R11 and R12)
SDSF
Security Server - RACF
SMPE (V3R6)
TSOE
zOS Security Level 3
BCP
CC++ Without Debug Tool
Common Information Model(CIM)
Communications Server
Communications Server SecurityLevel 3
Cryptographic Services
ICSF (FMID HCR7780)
PKI Services
System SSL
DFSMSdfp
DFSMSdss
DFSMShsm
DFSMSrmm
DFSMStvs
DFSORT
Distributed File Service
HCD
HCM IBM Tivoli Directory Server
Infoprint Server
zOS UNIX
KEY
1048573 Black (in bold) are base elements
1048573 Green (also in bold) are optional priced features
1048573 Brown (also in italics ) are optional unpriced features with exportcontrols
This element changed in zOS R13 (from zOS R11)
This element changed in zOS R13 (from zOS R12) copy 2003 IBM Corporation
All other elements not listed have not changed since z OS R11
There are no new elements since zOS R9
copy 2012 IBM Corporation
Migrating to zOS R8 P
5 Migrating to zOS R13 - Part 1 of 3
Integrated Security Services
Network AuthenticationService
ISPF
JES2
JES3
Language Environment
Library Server
Metal C Runtime Library
Network File System
RMF
Run-Time Library Extensions
IBM Tivoli DirectoryServer Security Level 3
Network AuthenticationService Level 3
SSL Level 3
zOS_V1R13_Migration-to-R13-Part1ppt Page 5 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 630
copy 2 0 12 I B M C o r o ra t o nM r at n t o z O S R 1 3 P a rt 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
Migrating to zOS R8 Part 1 of 3 G et Ready
Optional setting for Base Element ndash All IP security filters must As of R12
RFC4301 compliance (from be compliant with RFC4301 You can noCommunications Server) longer use the RFC4301Compliance
parameter on the IpFilterPolicy statementmig to specify whether Policy Agent enforces
compliance It is ignored and the PolicyAgent will enforce the rule that all IP filtersare compliant
CSVRTLS services in the Base Element support ndash LE RTLS support As of R12BCP for Language was removed in zOS R5 BCP RTLSEnvironment RunTime services (SET RTLS DISPLAY RTLS
Library Services RTLS in IEASYSxx and CSVRTLSxx andCSVRTLS macro) are removed in zOS
R12 Usage tracking assistance is
provided in OA29995 (R11) and OA29019(R10)
msys for Setup Base Element ndash CBPDO users should run
job CLNOS390 ServerPac users do notneed to do anything
As of R12
Element and Functions Withdrawn from zOS R12
ig i g - p i
zOS_V1R13_Migration-to-R13-Part1ppt Page 6 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 730
copy 2003 IBM CorporationfInfInInfo
i
Migrating to zOS R8 Part 1 of 3 G et Ready
zOS UNIX ConnectionManager and Process
Manager
Base Element In zOS R13
DCE and DCE Security
Server
Base Elements ndash IBM WebSphere
Application Server the IBM NetworkAuthentication Service andor theIBM Directory Server asreplacement strategies for each of
the DCE technologies
In zOS R13
DFS support that usesthe DCE architecture
mig
Base Element support ndash zOS
Network File System (NFS)implementation as the replacement
In zOS R13
Element and Functions Withdrawn from zOS R13
copy 2007 IBM Corporat on
7 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 7 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 830
copy 2012 IBM CorporatonM gratng to z OS R13 Par t 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
i
i
i
ii i
Functions Planned to be Withdrawnin the release after zOS R13hellip
zFS multi-file system aggregates(from Distributed File Service)
m g
Base Element ndash copy zFS multi-file system aggregates to zFScompatibility mode aggregates
In the releaseafter zOS R13
zFS cloning support (such aszfsadm clone and zfsadm
clonesys commands) Do not
mount file systems containing a
cloned file system (bak)
Base elements ndash when support for cloning is removed only zFScapability mode aggregates will be supported Find (with
modify zfsquery command) and copy any cloned files to
compatibility mode aggregrates
In the releaseafter zOS R13
BIND 920 function (from theCommunications Server)
Base Element support ndash for use as a caching-only name serveruse Resolver cache function (in zOS R11) For use as a
primary or secondary authoritative name server consider using
BIND on Linux for System z
In the releaseafter R13
BPXDEFAULTUSERm g
Base Element support ndash use BPXUNIQUEUSER instead (as ofR11) or assign unique UIDs and GIDs
In the releaseafter R13
Capacity Provisioning usingSystem z API with SE and HMC
Base Element support ndash will use BCPii instead System z APIwill still be supported on the SE and HMC Use Tracking
Facility with OA35284 Look for ldquoCPO-WSNMP usage domainname rdquo
In the releaseafter R13
Language Environment runtimeoptions via USERMOD
m g
Base Element support ndash use CEEPRMxx instead (with zOSR12 NONOVR support if necessary)
In the releaseafter R13
-
zOS_V1R13_Migration-to-R13-Part1ppt Page 8 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 630
copy 2 0 12 I B M C o r o ra t o nM r at n t o z O S R 1 3 P a rt 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
Migrating to zOS R8 Part 1 of 3 G et Ready
Optional setting for Base Element ndash All IP security filters must As of R12
RFC4301 compliance (from be compliant with RFC4301 You can noCommunications Server) longer use the RFC4301Compliance
parameter on the IpFilterPolicy statementmig to specify whether Policy Agent enforces
compliance It is ignored and the PolicyAgent will enforce the rule that all IP filtersare compliant
CSVRTLS services in the Base Element support ndash LE RTLS support As of R12BCP for Language was removed in zOS R5 BCP RTLSEnvironment RunTime services (SET RTLS DISPLAY RTLS
Library Services RTLS in IEASYSxx and CSVRTLSxx andCSVRTLS macro) are removed in zOS
R12 Usage tracking assistance is
provided in OA29995 (R11) and OA29019(R10)
msys for Setup Base Element ndash CBPDO users should run
job CLNOS390 ServerPac users do notneed to do anything
As of R12
Element and Functions Withdrawn from zOS R12
ig i g - p i
zOS_V1R13_Migration-to-R13-Part1ppt Page 6 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 730
copy 2003 IBM CorporationfInfInInfo
i
Migrating to zOS R8 Part 1 of 3 G et Ready
zOS UNIX ConnectionManager and Process
Manager
Base Element In zOS R13
DCE and DCE Security
Server
Base Elements ndash IBM WebSphere
Application Server the IBM NetworkAuthentication Service andor theIBM Directory Server asreplacement strategies for each of
the DCE technologies
In zOS R13
DFS support that usesthe DCE architecture
mig
Base Element support ndash zOS
Network File System (NFS)implementation as the replacement
In zOS R13
Element and Functions Withdrawn from zOS R13
copy 2007 IBM Corporat on
7 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 7 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 830
copy 2012 IBM CorporatonM gratng to z OS R13 Par t 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
i
i
i
ii i
Functions Planned to be Withdrawnin the release after zOS R13hellip
zFS multi-file system aggregates(from Distributed File Service)
m g
Base Element ndash copy zFS multi-file system aggregates to zFScompatibility mode aggregates
In the releaseafter zOS R13
zFS cloning support (such aszfsadm clone and zfsadm
clonesys commands) Do not
mount file systems containing a
cloned file system (bak)
Base elements ndash when support for cloning is removed only zFScapability mode aggregates will be supported Find (with
modify zfsquery command) and copy any cloned files to
compatibility mode aggregrates
In the releaseafter zOS R13
BIND 920 function (from theCommunications Server)
Base Element support ndash for use as a caching-only name serveruse Resolver cache function (in zOS R11) For use as a
primary or secondary authoritative name server consider using
BIND on Linux for System z
In the releaseafter R13
BPXDEFAULTUSERm g
Base Element support ndash use BPXUNIQUEUSER instead (as ofR11) or assign unique UIDs and GIDs
In the releaseafter R13
Capacity Provisioning usingSystem z API with SE and HMC
Base Element support ndash will use BCPii instead System z APIwill still be supported on the SE and HMC Use Tracking
Facility with OA35284 Look for ldquoCPO-WSNMP usage domainname rdquo
In the releaseafter R13
Language Environment runtimeoptions via USERMOD
m g
Base Element support ndash use CEEPRMxx instead (with zOSR12 NONOVR support if necessary)
In the releaseafter R13
-
zOS_V1R13_Migration-to-R13-Part1ppt Page 8 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 730
copy 2003 IBM CorporationfInfInInfo
i
Migrating to zOS R8 Part 1 of 3 G et Ready
zOS UNIX ConnectionManager and Process
Manager
Base Element In zOS R13
DCE and DCE Security
Server
Base Elements ndash IBM WebSphere
Application Server the IBM NetworkAuthentication Service andor theIBM Directory Server asreplacement strategies for each of
the DCE technologies
In zOS R13
DFS support that usesthe DCE architecture
mig
Base Element support ndash zOS
Network File System (NFS)implementation as the replacement
In zOS R13
Element and Functions Withdrawn from zOS R13
copy 2007 IBM Corporat on
7 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 7 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 830
copy 2012 IBM CorporatonM gratng to z OS R13 Par t 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
i
i
i
ii i
Functions Planned to be Withdrawnin the release after zOS R13hellip
zFS multi-file system aggregates(from Distributed File Service)
m g
Base Element ndash copy zFS multi-file system aggregates to zFScompatibility mode aggregates
In the releaseafter zOS R13
zFS cloning support (such aszfsadm clone and zfsadm
clonesys commands) Do not
mount file systems containing a
cloned file system (bak)
Base elements ndash when support for cloning is removed only zFScapability mode aggregates will be supported Find (with
modify zfsquery command) and copy any cloned files to
compatibility mode aggregrates
In the releaseafter zOS R13
BIND 920 function (from theCommunications Server)
Base Element support ndash for use as a caching-only name serveruse Resolver cache function (in zOS R11) For use as a
primary or secondary authoritative name server consider using
BIND on Linux for System z
In the releaseafter R13
BPXDEFAULTUSERm g
Base Element support ndash use BPXUNIQUEUSER instead (as ofR11) or assign unique UIDs and GIDs
In the releaseafter R13
Capacity Provisioning usingSystem z API with SE and HMC
Base Element support ndash will use BCPii instead System z APIwill still be supported on the SE and HMC Use Tracking
Facility with OA35284 Look for ldquoCPO-WSNMP usage domainname rdquo
In the releaseafter R13
Language Environment runtimeoptions via USERMOD
m g
Base Element support ndash use CEEPRMxx instead (with zOSR12 NONOVR support if necessary)
In the releaseafter R13
-
zOS_V1R13_Migration-to-R13-Part1ppt Page 8 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 830
copy 2012 IBM CorporatonM gratng to z OS R13 Par t 1 of 3
copy 2003 IBM CorporationfInfInInfo
copy 2007 IBM Corporation
i
i
i
ii i
Functions Planned to be Withdrawnin the release after zOS R13hellip
zFS multi-file system aggregates(from Distributed File Service)
m g
Base Element ndash copy zFS multi-file system aggregates to zFScompatibility mode aggregates
In the releaseafter zOS R13
zFS cloning support (such aszfsadm clone and zfsadm
clonesys commands) Do not
mount file systems containing a
cloned file system (bak)
Base elements ndash when support for cloning is removed only zFScapability mode aggregates will be supported Find (with
modify zfsquery command) and copy any cloned files to
compatibility mode aggregrates
In the releaseafter zOS R13
BIND 920 function (from theCommunications Server)
Base Element support ndash for use as a caching-only name serveruse Resolver cache function (in zOS R11) For use as a
primary or secondary authoritative name server consider using
BIND on Linux for System z
In the releaseafter R13
BPXDEFAULTUSERm g
Base Element support ndash use BPXUNIQUEUSER instead (as ofR11) or assign unique UIDs and GIDs
In the releaseafter R13
Capacity Provisioning usingSystem z API with SE and HMC
Base Element support ndash will use BCPii instead System z APIwill still be supported on the SE and HMC Use Tracking
Facility with OA35284 Look for ldquoCPO-WSNMP usage domainname rdquo
In the releaseafter R13
Language Environment runtimeoptions via USERMOD
m g
Base Element support ndash use CEEPRMxx instead (with zOSR12 NONOVR support if necessary)
In the releaseafter R13
-
zOS_V1R13_Migration-to-R13-Part1ppt Page 8 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 930
i
copy 2012 IBM Corporation9 Migrating to zOS R13 - Part 1 of 3
13
copy 2007 IBM Corporat on
zOS Ordering and Deliverables Schedule
912910
911
zOS V1R11 (SystemPac)
zOS R planned
zOS V1R12 (SystemPac)
zOS V1R13
Cryptographic Support for zOS V1R10-R12 (FMIDHCR7780) available starting 91010
zOS V1R12 ServerPac orderingends 102511 recommended by101111
SystemPac ordering ends 72412
recommended by 62612
zSO V1R11 ServerPac ordering ended 102610
SystemPac ordering ended 72611
zOS R
913
zOS V1R13 ServerPac ordering
starts 91611
Planned ServerPac ordering ends
October 2012
Cryptographic Support for zOS V1R11-R13 (FMID
HCR7790) available starting 9911
zOS_V1R13_Migration-to-R13-Part1ppt Page 9 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1030
copy 2007 IBM Corporationigrating to zOS R8 Part 1 of 3 Get Ready
copy 2012 IBM Corporation10 Migrating to zOS R13 - Part 1 of 3
Crypto Support in zOS Releases
Release Level Integrated and Available
ICSF FMID HCR7780 is incorporated
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R13
ICSF FMID HCR7770 is incorporated
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R12
ICSF FMID HCR7751 is incorporated
1114109Cryptographic Support for zOS V1R9-R11 Web deliverable (FMIDHCR7770) available on 112009
1114109Cryptographic Support for zOS V1R10-R12 Web deliverable (FMIDHCR7780) available on 91010
1114109Cryptographic Support for zOS V1R11-R13 Web deliverable (FMIDHCR7790) planned to be available on 9911
zOS R11
Your current ICSF level indicates which migration actions yoursquoll need to perform when going to zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 10 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1130
Some popular (no-charge) products for zOSbull IBM zOS Management Facility V1 R13 (5655-S28 5655-S29)
bull IBM Ported Tools for zOS V1 R2 (5655-M23 5655-M29) available 7910
bull V1R2 is updated with newer versions of the associated open source code specificallyOpenSSH 50p1 OpenSSL 098k and zlib 123 and features (all the same prior
level) IBM Ported Tools for zOS Perl Feature IBM Ported Tools for zOS PHPFeature IBM Ported Tools for zOS Suppl Toolkit Feature (bzip2 cURL 7161)IBM Ported Tools for zOS IBM HTTP Server V70 Feature (5655-M23 )
bull XML Toolkit for zOS V1 R9 (5655-J51 5655-I30)
bull Contains XML V1R8 and V1R7 levels as well
bull XML Toolkit for zOS V1 R10 (5655-J51 5655-I30) ndash only contains XML V1R10 level
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V5 (5655-N99 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V5 (5655-N98 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V6 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V6 (5655-R31 5655-I48)
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V601 (5655-R32 5655-I48)
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V601 (5655-R31 5655-I48) copy 2003 IBM Corporation
bull V601 available since 31811
bull IBM 64-bit SDK for zOS Java 2 Technology Edition V7 (5655-W44 5655-I48) copy 2007 IBM Corporation
bull IBM 31-bit SDK for zOS Java 2 Technology Edition V7 (5655-W43 5655-I48)11 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporationbull V7 to be available 102811
zOS_V1R13_Migration-to-R13-Part1ppt Page 11 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1230
i
i
zOS Policies
bull Annual Release Frequency
bullzOS V1 R13 GA is planned for Sept 30 2011
bullAll zOS releases are planned to GA everySeptember
bull Service Support Policy
bull Coexistence-Migration-Fallback Policy
bull Policy ChangebullzOS V113 is planned to be the last release to support a staged migration
copy 2003 IBM Corporat onfor JES2 and JES3 Future releases will require you to migrate to all elementsof zOS at the same time including JES2 JES3 or both
copy 2007 IBM Corporat on
12 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 12 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1330
L O O K
zOS Service Policy
bull Release serviceable for three years following GA
bull Then for up to two additional years you can purchase
bullIBM Lifecycle Extension for zOS V19 (5646-A01)
bullIBM Lifecycle Extension for zOS V110 (5656-A01)
bull At least 12 months notice before withdrawing service
bull Handy websitehttpwwwibmcomserverseserverzserieszossupportzos_eos_dateshtml
GA Date End of Service Date
zOS V1R9 28 Sept 2007 Occurred on 30 Sept 2010 (and SMPE V34)
Lifecycle Extension until 30 Sept 2012
zOS V1R10 26 Sept 2008 Occurred on 30 Sept 2011
Lifecycle Extension until 30 Sept 2013
zOS V1R11 25 Sept 2009 Announced to be 30 Sept 2012
zOS V1R12 24 Sept 2010 Planned to be Sept 2013
copy 2003 IBM Corporation
zOS V1R13 30 Sept 2011 Planned to be Sept 2014
Migrating to zOS R8 Part 1 of 3 Get Ready copy 2007 IBM Corporation
13 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 13 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1430
i
i
copy 2012 IBM Corporation14 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporat on
18
copy 2007 IBM Corporat on
zOS Coexistence Policy
bullStarting with zOS R6 IBM has aligned the coexistence fallback andmigration policy with the service policy
bullzOS R11 zOS R12 and zOS R13 are supported for coexistence
migration and fallback
bullKeep in mind exploitation of new function can require that all systemsbe at zOS R13 before use Fallback maintenance may not be availablefor all exploitation cases Consult the appropriate exploitationdocumentation to understand the limitations on fallback
zOS R9zOSR10
zOSR11
zOSR12
zOSR13
With zOS V110 Lifecycle Extended Service
With zOS V19 Lifecycle Extended Service
zOS_V1R13_Migration-to-R13-Part1ppt Page 14 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1530
i
copy 2012 IBM Corporation15 Migrating to zOS R13 - Part 1 of 3
copy 2003 IBM Corporation
copy 2007 IBM CorporationMigrating to zOS R8 Part 1 of 3 Get Ready
Positioning for zOS R13
bull Read Documentation and PSP bucketsbullzOS Migration and zOS Planning for Installation
bullSoftware PSP buckets ZOSV1R13 ZOSGEN SERVERPAC bullMust use FIXCATs for coexistence verification
bull DASD Storage Requirements for zOS R13
bull Ensuring System Requirements Are SatisfiedbullDriving System Requirements ndash no new news
bullSMPE IO11698 PTF (RSU1004) for access authority
bullTarget System RequirementsbullHardware and Software
bullCoexistence System Requirementsbull Migration Actions You Can Do NOW
zOS R11 zOS R12 zOS R13
Target 6063 5891 5868
DLIB 8781 8599 8941
File
System3100 3100 3293 (HFS)
3309 (zFS)
sizes in 3390 cylinders
Approaching 3390-3 limit of
3339 cylinders
The 3390-6 limit is 6678
cylinders
m g
zOS_V1R13_Migration-to-R13-Part1ppt Page 15 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1630
bull Hardware Requirements
bullProcessor Requirements
bullIBM System z server z114 z196 z10 z9 z990
Target System HW Requirements for zOS R13
z890 z900 or z800bullCoupling Facility seehttpwwwibmcomeserverzseriespsocftablehtml
bullz114 and z196 initially ships with CFCC level 17
bullCFCC level 17 support requires coexistence on zOS R11
bullThese PTFs are identified with FIXCATsIBMDeviceServerz196-2817 IBMDeviceServerz114
2818 IBMFunctionSYSPLEXDataSharing
IBMCoexistencezOSV1R12 andIBMCoexistencezOSV1R13
bullLarger CF structure sizes may be necessary for CFCC level 17 copy 2003 IBM Corporation
Use CFSIZER for planning structure sizes to get to the current copy 2007 IBM CorporationCFCC level
16 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 16 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1730
IBM Corporaton
I M Corporation
IBM Corporation
Migration Action with z196 and z114 and zOS R13
Accommodate HiperDispatch default of YES on IBM zEnterprise(Recommended)
bull As of R13 when running on z196 or z114 IEAOPTxx keyword HIPERDISPATCHwill default to YES if not specified
bull If HIPERDISPATCH=NO is specified the specification will be honored as it wason previous zOS releases
bull Action Examine your IEAOPTxx members that will be used for zOS R13 thatwill be IPLed on a zEnterprise
bull If YES then nothing to do If omitted then the default for you will switch from NOto YES Understand YES considerations Recommended to use FIXCAT foryour server (IBMDeviceServerxxxxxxx ) for installing HIPERDISPATCH fixes
bull If NO then investigate
bull Recommendation is to use YES where the LPAR weight guarantees a share
of two or more physical processors without a compelling reason for runningHIPERDISPATCH=NO
bull If you still want NO change the SUP_HiperDispatch health check to succeed
add the machine type to the MachTypes parameter and verify that theHIPERDISPATCH parameter is NOPARM(lsquoHIPERDISPATCH(NO)MachTypes(28172818)rsquo)
YES considerations include WLM policy considerations and using17 Migrating to zOS R13 - Part 1 of 3the ldquoGlobal Performance Data Controlrdquo in LPAR profiles copy 2012 i
copy 2003 B
copy 2007
zOS_V1R13_Migration-to-R13-Part1ppt Page 17 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1830
bull Software Requirements
bullCoexistence Software (on other zOS systems)
Software Requirements for zOS R13
bullTarget Software (correct levels of IBM non-zOS and non-IBM products on the zOS system)
bullIf the IBM products are still service-supported they may beused on zOS V1R13 with some exceptions found inzOS V1R13 Planning for Installation Appendix B
bullFunctional Requirements
1048573Some functions may need specific SW or HW levels forexploitation
1048573Reminder Consult the appropriate exploitation copy 2003 IBM Corporation
documentation to understand the limitations on fallback copy 2007 IBM Corporation
18 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 18 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 1930
copy 2003 IBM Corporation
copy 2012 IBM Corporation19 Migrating to zOS R13 - Part 1 of 3
25
Migrating to zOS R8 Part 1 of 3 Get ReadyUse FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
Website httpwww-306ibmcomsoftwaresupportlifecyclecan be helpful
V5 R2 with PTFs UA42145 and UA46832 ndash end of service 33112
(V5R1 is still in service until 33112)
Tivoli Netview
V5 R0
(V1R4 was end of service 93011 zOS R11 was the last release for which SDK V1R4was supported)
IBM SDK Java TechnologyEdition (31-bit or 64-bit)
V32 + PTFs UA43003 UA44993 UA47085 UA43533 and UA52313
(V31 was end of service 93010 V23 was end of service 93007)
Tivoli System Automation
V41 + PTFs described in XE Technotes
(V31 is end of service 43011 V22 was end of service 93008)
Tivoli OMEGAMON XE
V61 ndash end of service 93012
(V601 was end of service 93010 V50 was end of service 93008)
WebSphere Application
Server
V10 R1 with PTFs UK47628 UK38953 UK41225 and UK41224 (end of service 111212)
(V7 R1 was end of service 11805 V8 R1 was end of service 110508 V9 R1 was end ofservice 11710)
IMS
V8 R1
(V71 was end of service 63008)
DB2
V3 R1 + PTFs UK29210 UK29407 and UK40130
(V2R2 was end of service 43008 V2R3 was end of service 93009)
CICS TS
Minimum supported levelProduct name
Some IBM SW Target System Reqrsquos for zOS R13
zOS_V1R13_Migration-to-R13-Part1ppt Page 19 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2030
Target System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA
from the ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF witha minimum or functional level for zOS R13
++HOLD(HWRE320) FIXCAT FMID(HWRE320) REASON(AA31274)
RESOLVER(UA52313) CATEGORY(IBMTargetSystemRequiredServicezOSV1R11 IBMTargetSystemRequiredServicezOSV1R12 IBMTargetSystemRequiredServicezOSV1R13) DATE(11154)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your Tivoli System Automation global
REPORT MISSINGFIX ZONES(TIVTGT) copy 2003 IBM Corporation
FIXCAT(IBMTargetSystem-RequiredServicezOSV1R13 )
20 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 20 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2130
copy 2012 IBM Corporaton
copy 2003 IBM Corporation
copy 2007 IBM Corporation
Coexistence System PTF Verification for zOS R13
bull Must use FIXCATs to verify coexistence PTFs areinstalled
bull Other related coexistence FIXCATs you may want to use
bullIBMCoexistencezOSV1R13
bullIBMCoexistenceICSFzOS_V1R11-V1R13-HCR7790
i21 Migrating to zOS R13 - Part 1 of 3
bullIBMCoexistencezOSMFV1R13
bullhellipand there may be others
Use the FIXCAT Explorer
SMPE panels 11 global 2 Optionsselect your options 7 2 YES for explore
zOS_V1R13_Migration-to-R13-Part1ppt Page 21 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2230
Coexistence System PTF Verification for zOS R13
1 RECEIVE the latest HOLDDATA (If you pull HOLDDATA fromthe ftp website make sure you use FULL)
bull HOLDDATA is produced to associate a particular PTF ascoexistence between zOS R11 or zOS R12 with zOS R13
++HOLD(HQX7760) FIXCAT FMID(HQX7760) REASON(AM03128)
RESOLVER(UK90030) CATEGORY(IBMCoexistencezOSV1R13)DATE(11082)
2 Run the REPORT MISSINGFIX command to see what isneeded but not yet installed
SET BDY(GLOBAL) Your zOS R11 global
REPORT MISSINGFIX ZONES(ZOSR11T)
FIXCAT(IBMCoexistencezOSV1R13) copy 2003 IBM Corporation
An even better idea is to also include here the FIXCAT
IBMFunctionHealthChecker22 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 22 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2330
i
i
Some Migration Tasks You Can Do NOW
1 Transition off of removed functions and elements
1048573 In R12 RFC4301 compliance CSVRTLS removal hellip
1048573 In R13 DCE removals DCE Security Server
1048573 Beyond R13 zFS multi-fs BPXDEFAULTUSER BIND 920
2 Review documentation and PSP buckets
3 Prepare Driving and Target Systems
1048573 Driving systems ndash nothing new here if yoursquove handled SMPE APARIO11698
1048573 Target systems
ndash Preparation for CFCC level 17
ndash DASD storage for zOS R13 ndash position root on larger DASD
ndash IBM product level research FIXCAT IBMTargetSystem-RequiredServicezOSV1R13
ndash ISV research for zOS R13
1048573 Coexisting systems - FIXCAT IBMCoexistencezOSV1R13 (and others)
4 Use IBM Health Checker for zOS FIXCAT IBMFunctionHealthChecker copy 2003 IBM Corporat on
bull Activate the Migration Health Checks (they are shipped INACTIVE) copy 2007 IBM Corporat on5 Perform zOS R13 migration actions you can do NOW
29
23 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 23 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2430
IBM Health Checker for zOS for Migration Use
1 Install all Migration Health Check PTFs on your current release PTFswill be marked with FIXCAT IBMFunctionHealthChecker
2 Activate the Migration Health Checks appropriate for your migration
path specifying releases you are migrating through and to Forexample one way is
ndash F HZSPROCACTIVATECHECK=(IBMMIG)Could also be IBMZOSMIG or other wayshellip
3 Migration Health Checks will run on your current release
4 Review output for exceptions to create planning items for yourmigration plan
Note some ldquoBest Practicerdquo health checks
can also be useful for migration
These checks are shipped ACTIVE
24 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
Migration Health Checks are intended to be used in a scenario such as the following on your current release
1Install all the latest Migration Health Checks Migration Health Checks are recommended to run on your existing systembefore you migrate to a new release therefore they are provided in the service stream in PTFs (or ++APARs during ESP)You must install the PTFsAPARs on your current system to have the Migration Health Checks available Migration HealthChecks added to the PTF service stream like other Health Checks can be found using the functional PSP bucketHCHECKER You can also use a website to see all Health Checks available athttpwwwibmcomsystemszoszoshcheckercheck_tablehtml You may want to install the PTFs during a regular servicewindow so that an IPL is scheduled afterwards Health Checks are often added by a function when it is started or restartedso you may find that putting the PTFsAPARs on before a scheduled IPL may work best for you Additional Migration HealthChecks could be added at different times so having the latest ones installed is best
2Activate the Migration Health Checks appropriate for your migration path Because the naming convention for MigrationHealth Checks indicate which release introduced the migration action you can activate just the checks appropriate for yourmigration path Using SDSF (or another method for viewing Health Checks especially using filters) you can view ahead oftime which Migration Health Checks you have available on your system As a theoretical example if you are migrating fromzOS V1R8 to zOS V1R10 you would need to activate the Migration Health Checks that occurred in both zOS V1R9 andzOS V1R10 If you were migrating from zOS V1R9 to zOS V1R10 you would only need to activate the Migration HealthChecks that occurred in zOS V1R10 There are many ways of making a check active and many ways of using wildcardingto include specific checks Here are some examples of using the MODIFY command to make checks active
F HZSPROCACTIVATECHECK=(IBMMIGV1)
F HZSPROCACTIVATECHECK=(IBMICSFMIG)
F HZSPROCACTIVATECHECK=(IBMZOSMIGV1R10)
Remember that for zOS there are two naming conventions used one for ICSF (that starts with ICSFMIGnnnn) and one forthe rest of zOS (that starts with ZOSMIGVvvRrr) Use a wildcard filter that includes the intended Migration Health Checks
3Migration Health Checks will run and gather information
4Review the Health Check output and re-run checks as appropriate Any exceptions should be addressed in yourmigration plan If you can complete the migration action before moving to the new zOS release you can re-run the check to
verify that it was completed correctly on your current systemDeactivate the Migration Heatlh Checks if you desire For example
F HZSPROCDEACTIVATECHECK=(IBMMIGV1)
F HZSPROCDEACTIVATECHECK=(IBMICSFMIG)
F HZSPROCDEACTIVATECHECK=(IBMZOSMIGV1R10)
zOS_V1R13_Migration-to-R13-Part1ppt Page 24 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2530
General System REXX Reminder
917501 Some IBM Health Checker for zOS checks are written inSystem REXX
917501 Exploiters of System REXX (not just checks) require both of the
following ndash Compiled REXX needs either Alternate Library for REXX
(available in zOS since V1R9) or from the IBM Library forREXX on zSeries (5695-014) The runtime library will need to
be available to the systembull REXXSEAGALT can be put in the LNKLSTbull REXXSEAGLPA can be put in the LPALST
bull If you do not APF-authorize the library you will get an abendwhen the runtime routines are requested by an APF-Authorized routine
ndash System REXX customization must be performed
Customization tasks are documented in System REXX in zOSMVS Programming Authorized Assembler Services Guide
25 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 25 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2630
copy 2012 IBM Corporatongratng to z OS R13 Par t 1 of 3
i26 i i -
1 ZOSMIGREC_ROOT_FS_SIZE
2 XCF_SYSPLEX_CDS_CAPACITY
3 RSM_MEMLIMIT
4 ZOSMIGREC_SUP_TIMER_INUSE
5 SUP_HiperDispatchCPUConfig
6 ZOSMIGV1R13_CNZ_CONS_OPER_MODE
7 SUP_HiperDispatch
8 CNZ_SYSCONS_ALLOWCMD
9 ZOSMIGV1R12_SUP_LCCA_ABOVE_16M
10 ZOSMIGV1R12_RCF_PCCA_ABOVE_16M
11 GRS_AUTHQLVL_SETTING
12 ZOSMIGV1R11_CS_RFC4301
13 ZOSMIGV1R11_CS_BIND9
IBM Health Checker for zOS Checks for Migration
14 CATALOG_IMBED_REPLICATE
15 ZOSMIGV1R11_ZFS_RM_MULTIFS ZOSMIGREC_ZFS_RM_MULTIFS
16 ZOSMIGV1R13_ZFS_FILESYS
17 ZOSMIGREC_SMB_RPC18 INFOPRINT_PRINTWAY_MODE
19 ZOSMIGV1R12_INFOPRINT_INVSIZE
20 INFOPRINT_V2DB_CHECK
21 JES2_Z11_Upgrade_CK_JES2
22 CEE_USING_LE_PARMLIB
23 SDSF_ISFPARMS_IN_USE
24 USS_HFS_DETECTED
25 ZOSMIGV1R13_RO_SYMLINKS
All these checks are cross-referenced for the associated
migration action in zOS R13 Migration
zOS_V1R13_Migration-to-R13-Part1ppt Page 26 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2730
Something available for those that share IEASYSxx
Consider exploiting WARNUND for new IEASYSxx statements
1114109 Description Starting in zOS V1R13 (and rolled back to zOS V1R11 and zOS V1R12 inOA35929) you can specify the WARNUND statement in IEASYSxx
1114109 Usage of this statement indicates to produce a new warning message IEA660I whenundefined statements are encountered rather than prompting for a correct statement No
DISPLAY IPLINFOWARNUND support
1114109 Usage of WARNUND can be particularly useful when specifying new parmlib options inIEASYSxx (such as the new CATALOG= IXGCNF= AUTOR=) and allowing these newIEASYSxx specifications to be shared with pre-zOS V1R13 systems
1114109 Steps to take ndash Install OA35929 on all pre-zOS V1R13 systems ndash As you add new statements in IEASYSxx for functional exploitation and you wish to
share those modified IEASYSxx members with pre-zOS V1R13 systems addWARNUND to those IEASYSxx members at the beginning of IEASYS00 as that willcover updates in all IEASYSxx members
Beware of typos Review your messages ndash Before WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA324I SYSP INPUT TERMINATED IN IEASYSMW
IEA336A RESPECIFY PARAMETERS OR PRESS ENTER TO CANCEL
ndash After WARNUND supportIEA321I INVALID PARAMETER SYNTAX - CATALAG=(00 - UNDEFINED KEYWORDIEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND
27 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 27 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2830
Migrating to zOS R13 - Part 1 of 3 Summarybull Content of zOS R13
bullPrepare now for removed content RFC4301 DCE and DCE Security Server
bullAnd future removals zFS multi-fs aggrs BPXDEFAULTUSER LE usermod hellip
bull zOS Ordering and Deliverables
bullOrder zOS R12 on ServerPac before Oct 11 2011 if you need it
bullLatest ICSF level (HCR7790) is planned to be available on Sept 9 2011 Not in R13bullzOSMF Ported Tools (and all features) XML R9 and R10 31-bit and 64-bit SDKs
bull zOS Policies
bullzOS R13 Coexistence-Migration-Fallback from zOS R12 or zOS R11
bullThe Lifecycle Extension can help you for corrective service not extended coexistence
bull Ensuring System Requirements are Satisfied
bullDriving Target SW Target HW and Coexisting System Requirements ndash file sys is larger
bullHiperDispatch default change on zEnterprise with zOS R13
bullUse FIXCATs IBMTargetSystem-RequiredServicezOSV1R13
IBMCoexistencezOSV1R13 IBMFunctionHealthChecker and others
bull Use IBM Health Checker for Migration Actions
bullInstall and activate INACTIVE migration health checks
bullReview migration health check output for zOS R13
bull Evaluate using WARNUND helpful when sharing IEASYSxx for new statements
bull and everything applicable in the next presentations
28 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
zOS_V1R13_Migration-to-R13-Part1ppt Page 28 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 2930
copy 2012 IBM Corporation29 Migrating to zOS R13 - Part 1 of 329
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States other countries or both
The following are trademarks or registered t rademarks of other companies
All other products may be trademarks or registered trademarks of their respective companies
NotesPerformance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the users job stream the IO configuration the storage configuration and the workload processedTherefore no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance rati os stated hereIBM hardware products are manufactured from new parts or new and serviceable used parts Regardless our warranty terms apply
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditionsThis publication was produced in the United States IBM may not offer the products services or featur es discussed in this document in other countries and the information may be subject to change withoutnotice Consult your local IBM business contact for information on the product or services available in your areaAll statements regarding IBMs future direction and intent are subject to change or withdrawal without notice and represent goals and objectives onlyInformati on about non-IBM products is obtained from the manufacturers of those products or their published announcements IBM has not tested those products and cannot confirm the performancecompatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those productsPrices subject to change without notice Contact your IBM representative or Business Partner f or the most current pricing in your geography
Adobe the Adobe logo PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries
Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc in the United States other countries or both and is used under license therefromJava and all Java-based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both
Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both
Intel Intel logo Intel Inside Intel Inside logo Intel Centrino Intel Centrino logo Celeron Intel Xeon Intel SpeedStep Itanium and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countriesUNIX is a registered trademark of The Open Group in the United States and other countries
Linux is a registered trademark of Linus Torvalds in the United States other countries or both
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce and is registered in the US Patent and Trademark Office
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
For a complete list of IBM Trademarks see wwwibmcomlegalcopytradeshtml
AS400reg e business(logo)reg DBE ESCO eServer FICON IBMreg IBM (logo)reg iSeriesreg MVS OS390reg pSeriesreg RS6000reg S30 VMESAreg VSEESAWebSpherereg xSeriesreg zOSreg zSeriesreg zVMreg System i System i5 System p System p5 System x System z System z9reg BladeCenterreg
Not all common law marks used by IBM are listed on this page Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market
Those trademarks followed by reg are registered trademarks of IBM in the United States all others are trademarks or common law marks of IBM in the United States
zOS_V1R13_Migration-to-R13-Part1ppt Page 29 of 30
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback
8132019 zOS V1R13 Migration to R13 Part1
httpslidepdfcomreaderfullzos-v1r13-migration-to-r13-part1 3030
Feedback
Your feedback is valuableYou can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback
1114109 Did you find this module useful
1114109 Did it help you solve a problem or answer a question
1114109 Do you have suggestions for improvements
Click to send e-mail feedback
mailtoieausibmcomsubject=Feedback_about_zOS_V1R13_Migration-to-R13-Part1ppt
This module is also available in PDF format at zOS_V1R13_Migration-to-R13-Part1pdf
30 Migrating to zOS R13 - Part 1 of 3 copy 2012 IBM Corporation
You can help improve the quality of IBM Education Assistant content by providingfeedback