z/VSE Release Migration Considerations Part 1 & 2 · z/VSE Release Migration Considerations Part 1 ... Failure of a mark to appear does not mean that IBM does not use the mark

© 2013 IBM Corporation

http://www.ibm.com/zVSE

http://twitter.com/IBMzVSE

z/VSE Live Virtual Class 2013

z/VSE Release Migration Considerations

Part 1 & 2

August Madlener

http://www.ibm.com/zVSE

http://twitter.com/IBMzVSE


z/VSE LVC 2013

The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.

The following are trademarks or registered trademarks of other companies.

* All other products may be trademarks or registered trademarks of their respective companies.

Notes:

Performance 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 will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here.

IBM 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. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.

This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area.

All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Information 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 performance, compatibility, 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 products.

Prices subject to change without notice. Contact your IBM representative or Business Partner for 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, and/or 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 therefrom. Java 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 countries.UNIX 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 U.S. 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 www.ibm.com/legal/copytrade.shtml:

*, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA, WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter®

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 ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.

2


z/VSE LVC 2013

Notice Regarding Specialty Engines (e.g., zIIPs, zAAPs and IFLs):

Any information contained in this document regarding Specialty Engines ("SEs") and SE eligible workloads provides onlygeneral descriptions of the types and portions of workloads that are eligible for execution on Specialty Engines (e.g., zIIPs,zAAPs, and IFLs). IBM authorizes customers to use IBM SE only to execute the processing of Eligible Workloads ofspecific Programs expressly authorized by IBM as specified in the “Authorized Use Table for IBM Machines” provided atwww.ibm.com/systems/support/machine_warranties/machine_code/aut.html (“AUT”).

No other workload processing is authorized for execution on an SE.

IBM offers SEs at a lower price than General Processors/Central Processors because customers are authorized to use SEsonly to process certain types and/or amounts of workloads as specified by IBM in the AUT.

3

http://www.ibm.com/systems/support/machine_warranties/machine_code/aut.html


z/VSE LVC 2013

AgendaPART 1

Planning Issues

New Hardware

Performance

System layout

Optional and Vendor Products

Test

Latest Service, RSL, PSP

Migration Options

FSU – Fast Service Upgrade

Initial Installation

PART 2

Independent Migration Issues

Migration of VSAM and other Data

Security Setup

Compiler/Languages

Performance Considerations

Hardware Issues

Vendor Software

4


z/VSE LVC 2013

Planning

– Hardware upgrades– Software, Release or Version upgrades– Performance Considerations– System layout– Optional products and vendor products– First Test– Latest service, RSL and PSP bucket– Regression Test– Cutover

5


z/VSE LVC 2013

Planning Hardware Upgrades

– New Processor• Performance consideration• New OSAX cards• New channel concept → FICON• Sizing of the new processor

– New disks• Consider consolidation to larger packs• Carefull with micro code updates, plan ahead

– New tape library, drop old tapes• Usage of VTAPE • Tapeless system?• Migration of tape data, multi-volume support

– Shared environment • CPU ID is new

– Storage, System layout– Check Hardware PSP if appropriate

6


z/VSE LVC 2013

Planning Performance

– Have performance numbers from old system available• CICS Statistics (DFH0STAT, DMF) • SMF Data

– SIR SMF

– SIR MON• Job Account Data• Monitor Data• CPUMON• If running a two or three way, Turbo dispatcher data

– QUERY TD

– POWER WORKUNIT=PA?– Refer to performance documentation for impact of new release– Sizing of the new processor

• Consult IBM for help– Check performance parameters like

• PRTY, consider partition balancing.• TCP/IP related parameters• LSR pools in CICS• Threshold for turbo dispatcher to stop unneeded CPU (Balancing)

7


z/VSE LVC 2013

Planning System Layout

– Verify selected Environment if modified and if still fits and adjust (FSU). Initial install recommended Environment C. • Consider NOPDS, optimize VSIZE versus available storage• Partition sizes for CICS, POWER VTAM DB2 etc. • More tasks required ?• Check if VTAM IOBUF31 is used

– If used check copyblock usage• SVA layout

– Most likely tuned to a low unused number which may change

» LISTDIR SDL for PSIZE on new system

» GETVIS SVA on old

– Newer releases move lot of code above the 16MB line →

IODEV=1024• Check available and used DSPACE• CICS, DLI or DB2 statistics – SOS• Shared environment required (shared DASD, shared Spool)?

8


z/VSE LVC 2013

Planning System Layout Things that Should not be Changed

– Don't change library structure – IJSYSRS, PRD1, PRD2, SYSDUMP– Don't change catalog layout, especially storage for master and user catalog

VSESP.USER.CATALOG (VSESPUC)– Control files IESCNTL and BSTCNTL must be unique in the system and

accessible by BSM (FB) and each CICS with IUI (DBDCCICS and PRODCICS)• Files should not be shared between VSE systems• Especially BSTCNTL do not copy via VSAM REPRO services, use

logical backup/restore vie SKBSTSAV in ICCF 59– It is not recommended to change allocation of IJSYSRS and IJSYSR1 – Use STDLABEL procedure to implement your DLBLs (BAM), STDLABUP

and IESVCLUP program for VSAM DLBLs, STDLABUS for user labels– Do not change volids DOSRES and SYSWK1– History file, work history file, job manager file, text repository file, text

repository work file and PTF file, if changed, reflect change in dialog 141 (Verify Location of Involved Serviced Files)

9


z/VSE LVC 2013

Planning Optional and Vendor Products, Extended Base

– Optional IBM Products should be reordered and (re)installed after upgrade.– Extended Base Products will be delivered and should be (re)installed if used.

• Some of them have new components/CLCs like OS390 API• After FSU you may delete old products see DELxxx in ICCF library 59,

e.g. DELOS390– Vendor Products

• Make sure you order appropriate updates in time • If FSU is the way to upgrade, it is recommended to upgrade vendor

products ahead of the FSU where applicable. Please contact vendor fordetails.

– Special care is required with external security manager like

Topsecret

– Make sure you have all service available before you start the

upgrade, especially fixes enabling the vendor product for the new

z/VSE release.• In case of Initial Installation Vendor Products are installed after the Initial

Install

10


z/VSE LVC 2013

Planning Latest Service Upgrade

– Make sure current refresh is installed– Order latest RSL (Recomended Service Level)

• IBM can provide information, RSLs have a cutoff date and are produced every two or three months.

• Test with current RSL on• If final cutover is delayed consider to reinstall current RSL

– Order latest PSP Bucket• Contains all important fixes

– Vendor Products• Check also for know problems with Vendor Products

11


z/VSE LVC 2013

Planning Test

Test most likely is only possible with a test LPAR or test VM guests.– FSU will allow some very limited test at the end of Stage 2, but this is

only in basic startup mode.– In case a test system is available,

• Test applications• Verify data, eventually reorganize data • Verify system layout and performance data• Does new hardware work ok

– Plan also for final cutover

12


z/VSE LVC 2013

Planning Fallback and Backup

Backup – Before you start take Backups of the most recent data – FSU optionally takes backup of the installation libraries, not really

recommended, except for DTSFILE – VSAM catalogs and data backup as described earlier

• All VSAM controlled volumes need to be flashcopied at the same time, otherwise not recommended

– For the system volumes and all volumes with space for the master catalog and VSESP.USER.CATALOG (VSESPUC) take SA FCOPY or DDR backups. Also IXFP flashcopy is fine.• SA FCOPY and DDR are recommended, VSE system needs to be shut

down for the system packs

Fallback– Plan for a fast and effective way to switch back

• Very fast is PPRC or flashcopy. But see above• If not applicable VSAM backup restore and FCOPY/DDR

– This fallback process is usually also part of a disaster recovery solution which can be used in general.

– Please consult IBM in case you have to perform a fallback, especially if fallback from z/VSE 5.1 to an older release

13


z/VSE LVC 2013

FSU Versus Initial Installation

FSU will update IBM provided Parts like System Libraries, ICCF members and System Files like Online Message Explanation (OME), but keep all user data, applications and products installed.

Initial Installation will just establish the VSE system, user data, applications and additional products need to be reestablished. Usually II is done on a test system (LPAR or VM guest).

Initial Installation is always possible and is necessary if FSU can not be done. Possible reasons:

• Previous System is too old, In general only two releases/versions.

• No FSU from VSE/ESA 2.3 and earlier.

• Change of system disk architecture, like switching from ECKD to FBA SCSI.

• Change of the System language (actually only Japanese and English is supported)

• Change of Environment like change to C (big). However this can be switched after FSU.

Both methods require careful planning, saving of original system in case a fallback is required. For Initial Installation, the effort may be higher in order to reestablish all applications, application data etc.

14


z/VSE LVC 2013

Performing an FSU

FSU is done in three steps– Downlevel Check

• This is an installation check showing service to be reinstalledafter FSU

• Does not change the system• Makes no sense in case of a release/version upgrade

– Preparation• This is very important, this step establishes the new FSU code

and enables it on the old system.– Installation

• Two stages, stage 1 install of

– IJSYSRS onto SYSWK1 Incl. NLS

– PRD1.MACLIB

– PRD2.GEN1 (optional will be cleared if not selected)

– Prepare JCL for Stage 2• At the end of Stage 1 generate POWER phase

15


z/VSE LVC 2013

Performing an FSU

FSU is done in three stepsInstallation• Stage 2

– Restore ICCF parts, base and NLS

– Install of PRD2.SCEEBASE (LE)

– Install of PRD1.BASE (CICS, VTAM, etc)

– Refresh OME

– Refresh Text Repository File, upgrade CSD

– Clear local and global catalog for a so called ice cold start of CICS

– Install DB2 (optional)

– Reorganize DTSFILE (optional)

– Copy back IJSYSR1• Stage 2 runs without CICS, TCPIP, VTAM, at the end basic CICS and

VTAM are started

– Stage 2 is started with special FSU JCL and normal IPL procedure.

OEM products are not started

See System Upgrade and Service manual and also Program Directory

16


z/VSE LVC 2013

Performing an FSU

Post FSU tasks• Perform tasks described in the manuals below• Re-install optional and extended base products• Reinstall vendor products or install service• Install RSL and PSP• Generate SA Dump disk or tape

See System Upgrade and Service manual and also Program Directory

17


z/VSE LVC 2013

Migration Layout and System FSU

– Own startup and allocation is used ($xJCLyyy procedures and own IPL procedure, ALLOC procedure). Rework as indicated in Program Directory and System Upgrade and Service manual.• Verify PRD2.SAVE for correct contents• If SVA size was optimized, verify on new system and adjust • Please verify also standard labels, FSU will use STDLABEL,

STDLABUP and STDLABUS procedures• LIBDEF chain is defined using skeleton SKLIBCHN defining

LIBDEF and LIBDEFs procedures.

Initial Installation– Take startup and allocation from your old system, please rework as

above with regard to Program Directory and System Upgrade and Service.

– It is recommended to have a current copy of all startup and alloc procedures in PRD2.SAVE

– Rework Partition setup using skeletons SKJCLx and SKALLOCx in ICCF library 59. and also LIBDEF and standard labels .Please refer also to the Administration guide.

In both cases– Fine tuning, SVA size, data space, storage layout after upgrade.

18


z/VSE LVC 2013

Migration Connectors, Miscellaneous

In general, Connectors are backward compatible, after upgrade always take newest code from the home page

http://www-03.ibm.com/systems/z/os/zvse/

– Optionally install or update the Workstation component from the Extended Base tape

– See also latest news on the download site

After each upgrade check above home page for any service related news

19

http://www-03.ibm.com/systems/z/os/zvse


z/VSE LVC 2013

Post Migration Tasks

SA Dump – Generate SA dump to disk (recommended) or tape

• IUI dialog fastpath 461 or 462

Dump Library– Dump library is now a VSAM library (since z/VSE 5.1), which is more

flexible in space• Space is allocated in master catalog• Space allocation is dependent on environment selected• FSU will not move, if wished moving to VSAM can be done using

skeleton SKDMPEXT

Verification and Test – Check your security setup – User Profiles– Check VSAM catalogs using the catalog checker– Test applications

20


z/VSE LVC 2013

Test Considerations

If you decided for a test system – Can this test system work with test data only?– If real data is required, this means most likely sharing data with

production• Be aware of the performance impact (SHR(4,4)• External lock file required• Setup of the shared environment is difficult

– Keep things like layout, startup procedures, workfiles etc. as close as possible the same as production• This might be used to copy this sandbox type system over to

production as physical copy. This can avoid time consuming FSU on production

– To avoid data sharing, exchange and actualization of data can be done with FTP or similar tools.

– Consider also performance related parameters during test

21


z/VSE LVC 2013

Fallback and Backups

Backup – See also planning section

Fallback– This is for example if in FSU Stage 2 system will not come up, or

in case of severe problems which cannot be repaired by corrective service

– IMPORT CONNECT VSAM catalogs– Restore VSAM catalogs– Restore system volumes (SA FCOPY or appropriate tools)– In case of a fallback consider backups of the new system also in

order to allow easier and faster resuming – If a fallback is required after a migration, please contact IBM for

known problems with such fallback situations– Keep in mind that the service level on the previous system may

be very old compared to the new z/VSE. Usually the old system was not upgraded to the most up-to-date level of that release.

22


z/VSE LVC 2013

Summary Initial Installation Pros and Cons

Pro

– Total reset – start from

scratch

– Select appropriate hardware

– Each control file like

IESCNTL BSTCNTL CSD

etc just contains what it

needs

– Possibility to clean up old

stuff

– If the complete setup is kept

outside VSE e.g. on VM all

configuration, installation

and restore work is easy

– Can be used to setup a test

system which can be cloned

for production later

– Good to learn for untrained

personnel

Cons

– Every piece of customer

specific data, applications,

control information like user

profiles, program definition

etc needs to be re-

iplemented

– Requires good knowledge

of what to do and a good

overview which job is

required to define which part

– If working on ICCF, all

configuration, installation

and restore jobs first need

to be reestablished in the

DTSFILE

– Not really good to migrate a

production system directly

since too time consuming

23


z/VSE LVC 2013

Summary FSU Pros and Cons

Pro

– Fast way to get system

upgraded

– All products, applications

and data are kept

– User definition, security

setup, CSD etc ready to use

– Same look and feel after

upgrade

– Can be used for both test

and production system

– Allows testing right after

FSU

– For less skilled personnel

provides fast results

– Very stable, allows

resuming and many steps

can be redone

Cons

– Vendor products like

security manager can cause

problem

– Requires discipline to

synchronize changes in

startup process in

PRD2.SAVE

– No way to change disk type

and size

– Dependent on standard

layout like libraries and

catalaogs

– Old products, applications,

files will stay in the system

even if not used anymore,

unless deleted manually

24


z/VSE LVC 2013

Summary FSU versus Initial Installation

FSU

– No change to user data,

applications

– z/VSE code is upgraded in a

fast efficient way

– Refresh of optional products

is optional, vendor products

need updates

– After FSU all applications

and data are ready for

testing

– Data base may need

migration to newer level

– No change to

language/compiler setup

– Network definition will stay

unchanged

Initial Installation

– New vanilla system all data,

applications need to be

brought in again

– Optional and vendor

products need to be

installed

– Control data like IESCNTL,

CSD, DTSFILE, BSTCNTL

need to be migrated.

– Import customer data,

restore customer

applications

– Load POWER queues

– Implement data base

– Adjust compile options

– Adjust layout

– Adjust network setup

25


z/VSE LVC 2013

Check List FSU

– PRD2.SAVE contains all current startup procedures, label procedures, current DTSECTAB – especially procedures with same name as shipped procedures.

– PRD2.CONFIG contains all configurable files like CICS tables, TCPIP configuration, VTAM startup

– Check if own POWER phase and allocation – specify accordingly in FSU dialog. DTRPOWR.PROC refers to all POWER files? Run POWER generation at the end of Stage 1.

– Check Program Directory and System Upgrade an Service manual for further Information

– Consider to establish startup with separate JCL procedures without activating vendor software, especially with external security manager

– Test

26


z/VSE LVC 2013

Performing an Initial Installation

Initial Installation is described in the Installation manual, for details concerning layout, configuration see also Planning.

After Initial Installation, optional and vendor products must be installed. – Startup and hardware must be configured– VSAM catalogs and data must be established– POWER Files must be loaded – CSD File needs to be updated– DTSFILE (ICCF) user libraries restore– DB2 and DLI data if available, Install and restore database– Security setup (IESCNTL and BSTCNTL)– Other data

Many of above actions are not required with FSU

Parts are documented in the CICS Migration Guide and Administration

27


z/VSE LVC 2013

Check List Initial Installation

Please also see Installation Guide and Installation worksheet there.– Check if all startup procedures of previous release are available

(ICCF, CMS, Volley ...) – Under VM – prepare the new VSE guest (CMS profiles, storage,

OSA etc.)– Select large enough system packs– Select correct environment

• Correct VSIZE, processor storage – consider NOPDS – Install extended Base, Optional and Vendor Products– Reestablish ICCF, POWER queues and generation– Re-establish your startup procedures– Migrate user profiles and BSTFILE – SKBSTSAV– Reestablish VSAM data– Reestalish data base– Reestablish applications

• CSD • Application libraries• Check LE and language setup

– Test

28


z/VSE LVC 2013

Migration of VSAM Data and Other

VSAM (not required for FSU, but recommended)– VSAM Backup/Restore – VSAM catalogs with EXPORT-DISCONNECT and IMPORT-CONNECT – Please carefully check definition of models used for workfiles on other

disks than DOSRES or SYSWK1– Entire catalogs can also be copied using Flashcopy

• For each catalog, all disks where it owns space has to be flashed • Be aware that disks have to have same model type, e.g. 3390-3.

Other data– Entire disks can be copied using:

• FCOPY • IXFP Flashcopy• DDR

For the two system packs, make sure in case of DDR that the system is down. For FCOPY standalone FCOPY is recommended for the system packs. If the master catalog or VSESPUC catalog have storage on disks other than DOSRES or SYSWK1, these volumes also have to be saved.

29


z/VSE LVC 2013

Migration of Databases

DLI– Take data base backups– Data base can also be migrated – Be aware of different releases, DLI 1.10 on CICS/VSE and DL/I

1.11 are no longer supported (z/VSE 4.3.x and higher). Migration to DL/I 1.12 is required.

– Do not use disk copies – DDR or FCOPY while data base is in use

DB2– Use DB2 Data Restore feature

Other Data Bases– Use the tools provided by the data base provider

30


z/VSE LVC 2013

Migration of POWER Files

FSU– Files are migrated automatically, no POFFLOAD required– It might help in fallback case to take POFFLOAD BACKUP– For older systems (before VSE/ESA 2.7) Cold start is done

requiring POFFLOAD – Shared Spool during FSU requires special emphasis, an IPL

procedure without the SHR attribute on POWER disks and POWER generation without share are recommended.

General– Migration with POFFLOAD on a tape (VTAPE)

Shared Spool– Conversion of POWER files is not recommended, POFFLOAD

and cold start from the master system is recommended.

31


z/VSE LVC 2013

Migration of CICS CSD

FSU– IBM provided groups like VSESPG, VSETYPE LE-Group CEE

are upgraded– User definitions are not changed. – Upgrade only works with CSD file with DLBL in standard label

area – Upgrade for production CICS PRODCICS see skeleton

SKCSDFC2

Initial Installation– Standard CSD file will be established– In order to migrate CSD from old system we recommend:

• Save (VSAM Repro) new IBM provided CSD• Copy old CSD (VSAM Repro), and run SKCSDFIL to

upgrade to current level.

32


z/VSE LVC 2013

Migration of ICCF DTSFILE File and Control File IESCNTL

FSU– Only IBM provided members and libraries are updated– Optional reorganize of the DTSFILE during FSU– No change to IESCNTL during FSU

Initial Installation– User libraries migrated via DTSUTIL backup/restore

• System Libraries are:

– 1, 2 Common , 50-69 Public

• Don‘t migrate system libraries• In case System Libraries were migrated by mistake, you can reload

these from the install tape using skeleton SKICFRST.• Make sure DTRICCF.PROC reflects all extents of DTSFILE

– ICCF users are migrated with IESBLDUP together with IESCNTL• Migration with IESBLDUP utility after Initial Installation.• All user profiles, user defined selections and application definitions

will be migrated. • The Control File of the original System and a Backup of the ICCF

DTSFILE is needed.• From CICS/VSE the migration of the SNT (Phases) can be done

with IESBLDUP utility.

33


z/VSE LVC 2013

Migration of Control File IESCNTL

Initial Installation: Performing Migration with IESBLDUP– Skeleton IESBLDUP to migrate.

• Standard user profiles are used

– Special profiles can be specified • Recommended to use IESCNTL and DTSFILE backup• After IESBLDUP job, use PF6=GROUPS in dialog „Maintain

User Profiles” to update BSTCNTL with user definition. – As well as after FSU, it is recommended to sign on with SYSA

and perform PF6 in Application Profile Maintenance (fastpath 213) and Selection Panel Maintenance (fastpath 212).

34


z/VSE LVC 2013

Migration of BSTCNTL and DTSECTAB

FSU– FSU Stage 2 will run without batch security, original DTSECTAB

phase if saved in PRD2.SAVE is re-established.– BSTCNTL is updated ( transaction security ) by FSU

Initial Installation– DTSECTAB has to be re-established after installation

• No User profiles in DTSECTAB except for FORSEC and DUMMY.

– See source DTSECTRC in ICCF 59– BSTCNTL

• This file is defined on the new system, all user specific data must be migrated using skeleton SKBSTSAV

– Don't copy this file using VSAM REPRO or similar

– DTSECTXN based Security (old concept) • Converted via Dialog 285, Details in Administration manual

35


z/VSE LVC 2013

Migration LE and Languages

FSU– Everthing is done for LE – Reinstall compilers– Make sure USERBG.PROC contains

// PWR PRELEASE RDR,CEEWARC

Initial Installation– CSD Definitions may be old - SKCSDFIL– Reinstall compilers

General Remarks– Migration from old compilers please refer to manuals

• Cobol for VSE/ESA Migration Guide• PL/I for VSE/ESA Migration Guide• C for VSE/ESA Migration Guide

– Run-Time Options• Check options CEEDOPT and CEECOPT and adjust• See LE z/VSE Customization Guide

– CICS System settings• RUWAPOOL (in DFHSIT)

– SVA usage - $SVACEE

36


z/VSE LVC 2013

Migration LE and Languages

COBOL – For old compilers see VSE/ESA Migration Guide – If you have customized COBOL COBPACKs review and reapply after upgrade.– SVA usage, consider $SVAIGZM load list– If Side-File Exits (SYSDEBUG) are used, migrate to new system if needed

PLI– PL/I for VSE/ESA Migration Guide– SVA usage, consider $SVAIBMM load list– Run-Time Options unique to PL/I Applications

• Condition code handling – DEPTHCONDLMT(0), ERRCOUNT(0)• Recommended option if using full BMS and experiencing display corruption

setting STORAGE=(NONE,NONE,CLEAR,0K) elseSTORAGE=(00,NONE,CLEAR,0K)

C for VSE/ESA – SVA usage, consider $SVAEDCM load list– If you use a specific tailored C locale, keep source changes (EDCLOCI). After

upgrade extract JCL member EDCLLOCL.Z from PRD2.SCEEBASE and insert EDCLOCI.

RPG II Online (CICS TS)– Required PTF PM75512/UK83060 RPG

37


z/VSE LVC 2013

Migration Performance

Performance Measurement– CPU Monitor Tool see home page – For checking DTRIATTN can be used (POWER time controlled) – QUERY TD, always perform SYSDEF TD,RESETCNT first

• Sample • // EXEC DTRIATTN,PARM='STACKQUERTD|QUERY TD|SYSDEF TD,RESETCNT'• // EXEC DTRIATTN,PARM='QUERTD'

– Healthchecker see home page – DFH0STAT for CICS TS – DLI Statistics– POWER D STATUS command– IUI Display System Activity– IUI Channel and Device Activity– SIR SMF– SIR MON– Job Accounting via SKJOBACC – Monitor like TMON or Explore

38


z/VSE LVC 2013

Migration Performance

Performance Parameters– PRTY

• Use Balance Groups

– PRTY

N,I,E,P,F5,BG,FB,F9,F4,F6,FA,F8,F7,Y,Q,C,Z=X=W,F2,F3,F1

– PRTY SHARE,X=500,W=200– CICS related

• LSR Groups• Shared data tables• Transaction priority• MXT• SOS

– TCP/IP• Contact IBM, BSI or CSI about performance related parameters

– LE Options– POWER SET WORKUNIT=PA– Turbo dispatcher threshold to quiece a processor with low usage

• SYSDEF TD,THRQ=50

39


z/VSE LVC 2013

Migration Performance Hints

Some General Remarks– One partition can only exploit the power of a single CPU – Use as many partitions as required for selected n-way– Use/define only as many CPUs as really needed– z/VSE can exploit up to 3 CPUs in an efficient way, consult IBM if more

are required– Exploitation increases by reduction of non-parallel work units (e.g.

Shared tables/ data in memory)– Partition setup

• Set up more batch and/or (independent) CICS partitions• Split CICS production partitions into multiple partitions (MRO)• Use a database (DB2)

– Try to minimize number of CPUs • Use CPU Balancing and Threshold

Restrictions– Overall workload's non-parallel share too high– Single CICS can only exploit one CPU– Non Parallel Share too high– Try to minimize number

40


z/VSE LVC 2013

Migration Hardware

Processor– New processor if activated after software migration will cause

overlap messages cause of new CPUID on • Page data set• Label area on old systems (no virtual disk)

– In case of a shared system, make sure CPUID is changed in in ASIPROC• Check DLF NCPU parameter is CPU is added in addition

– Consider turbo dispatcher threshold parameter– z/VSE 5.1 requires a z9 or higher (Architectural Level Set)

41


z/VSE LVC 2013

Migration Hardware

OSA– What is new with OSA Express 3 (OSAX3) and higher– OSA/SF is used to configure and load a so called OSA Address Table (OAT)

onto the OSA cards for SNA running over the OSA card (OSE)• IOCD: CHPID PCHID=1B0,PATH=(B0),TYPE=OSE,PART=(ZVSE,BRSPRD),SHARED

• Configuration is done running IOACMD REXX and IOAMAIN• OSAX3 and higher supports 2 ports per CHPID, it requires

– UK82285 for z/VSE 5.1

– UK71893 and UK82199 for z/VSE 4.3

– UK58684, UK71894 and UK82200 for z/VSE 4.2• Samples for an OAT and IOACMD run can be provided

– All OSA features can be configured in the IOCDS as CHPID type OSD (1000BASE-T also supports CHPID type OSA, OSC, OSE).

– When used with CHPID type OSD they are used for TCP/IP traffic, through the DEFINE LINK,TYPE=OSAX,... command.• If port 1 is to be used TCP/IP PTF PK66917 (4.1) newer releases, code is

included in base

– DEFINE LINK,TYPE=OSAX,DEV=(D00,D01),DATAPATH=D02,OSAPORT=1

42


z/VSE LVC 2013

Migration Hardware

Tape Libraries see also http://www.redbooks.ibm.com/abstracts/sg247712.html– IOCDS

• Sample TS77xx

CNTLUNIT CUNUMBR=0850,PATH=(E2,60),UNIT=3490,UNITADD=((00,02))

IODEVICE ADDRESS=(0850,2),CUNUMBR=(0850),UNITADD=00,UNIT=3490, x

STADET=Y

• Sample TS55xx

CNTLUNIT CUNUMBR=0890,PATH=(77,73),UNIT=3590,UNITADD=((00,02))

IODEVICE ADDRESS=(0890,2),CUNUMBR=(0890),UNITADD=00,UNIT=3590, x

STADET=Y

– VSE configuration • TS7700 has virtual 3490E drives, ADD as 3490E.• TS3500 is has real 3590/3592 drives, ADD a TPA or TPAxxx• VTS usage

– LIBSERV command interface– Vendor software

• VTS support, multi-volume support

43

http://www.redbooks.ibm.com/abstracts/sg247712.html


z/VSE LVC 2013

Migration Hardware

Disks – Storage subsystems

• ECKD up to 64K-1 cylinders larger disks not supported

– VTOC must be within first 4369 cylinders (DSF)

– VSAM BIG DASD and FAT DASD

• SCSI based FBA up to 24GB BAM, 16GB VSAM

• VM based FBA up to 2GB

– See planning hints for consolidation to larger disks

Micro code update, please refer also to

http://www-03.ibm.com/systems/z/os/zvse/about/status.html

– z/VSE with the latest service level supports concurrent microcode upgrade for IBM tape and ECKD storage. Please consult your device documentation for details.

– Recommendation for Tape storage:

z/VSE recommends to take the tape units offline (z/VSE OFFLINE command) prior to the microcode upgrade or use the next maintenance window. Once the upgrade completed, take the tape units online again (z/VSE ONLINE command). Please check with your software vendors (e.g. tape management systems), if they support concurrent microcode upgrade.

44

http://www-03.ibm.com/systems/z/os/zvse/about/status.html


z/VSE LVC 2013

Migrating CICS/VSE Security Definition

Security– REXX Procedures that can help are:

• SKSECTXS Migration of PCTs• SKSECTX2 Migration of Transactions using CICS Migration Aid• SKSECTX3 Migration of DFHCSDUP Control Statements

For more information also see Hints and Tips

OLD RSL based definitions – new Concept

The profiles below can be migrated with the procedures SKRSLXS (Macro Format), SKRSLX2 (Migration Aid Band) and SKRSLX3 (DFHCSDUP Format):– DCT Profile– PCT Profile– FCT Profile – JCT Profile – PPT Profile– TST Profile

NO Migration possible for:

APPL Profile and Facility profile

45


z/VSE LVC 2013

Migrating from CICS/VSE to CICS TS Some Remarks

DFHSNT– Signon table can be migrated to IESCNTL using IESBLDUP

• Works with DFHSNT phase copied from old system

For more information see also System Utilities manual

For General Migration Aspects see CICS Migration Guide

Migration inhibitors are – Macro Level Programming– Old IBM or Vendor Applications– Security Concept or special sign on programming– Old level languages – RPG now also on CICS TS (no inhibitor anymore see page 26)

46


z/VSE LVC 2013

Merci

Gracias!

Obrigado

Danke

Japanese

English

French

Russian

German

Spanish

Brazilian PortugueseArabic

Traditional Chinese

Simplified Chinese

BedanktNederlands

47


z/VSE LVC 2013

Please forward your questions or remarks [email protected]

[email protected]

Thank You

48

mailto:[email protected]

mailto:[email protected]


z/VSE LVC 2013

z/VSE Live Virtual Classes

z/VSE @ http://www.ibm.com/zvse/education/

LINUX + z/VM + z/VSE @ http://www.vm.ibm.com/education/lvc/

Read about upcoming LVCs on @ http://twitter.com/IBMzVSE

Join the LVC distribution list by sending a short mail to [email protected]

49

Documents

z/VSE Release Migration Considerations Part 1 & 2 · z/VSE Release Migration Considerations Part 1 ... Failure of a mark to appear does not mean that IBM does not use the mark