35
© 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

  • Upload
    others

  • View
    6

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2010 IBM Corporation

Moving to IBM i 6.1 or 7.1 Alison ButterillPower Systems Software

Page 2: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

2

Overview

•Why and What?• Improvement examples•About program conversion•Refresh choices

Page 3: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

3

Why move to IBM I 6.1? • Safe computing initiative

– i encryption, intrusion prevention & system integrity enhancements

• High availability initiative– Cross site mirroring and administrative system domain

• Advanced virtualization– Hosting storage for i partitions, virtual I/O server client support

• Extended SAN integration– New Fibre adapter & tools investments enhance interoperability &

performance• Web-based multi-platform systems management

– IBM Systems Director • Optimizing Java™ performance

– New IBM 64-bit JVM & data access performance enhancements• Integrated Web services environment

– Simpler deployment and better integration with Web services

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

Page 4: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

4

Why move to IBM i 7.1 ? • DB2

– Support for XML and column level encryption

• PowerHA – Async Geographic Mirroring & LUN-level switching

• Virtualization – IBM i 6.1 virtualization for i 7.1 partitions

• Solid State Drives– Automatic movement of hot data to SSDs

• Open Access for RPG– Extend application reach to pervasive

devices• Zend Server Community Edition

– PHP environment preloaded with IBM i• Systems Director Navigator

– Richer management of IBM i via Systems Director Navigator

PO #

Customer #

Date Credit Card

Purchase Order

123 2468 5/27/09 &#^$&$ ~XML

~

Power Systems

VIOS

IBM i 6.1 IBM i 7.1

Page 5: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

5

Security Enhancements• Offer Encryption to Meet Regulatory Requirements

– Encrypted BRMS backups of user data to tape or virtual tape device Encrypted Backup Enablement – IBM i Option 44

– Encryption of data residing in an ASP Encrypted ASP Enablement – IBM i Option 45

• Enhanced Intrusion Detection and Prevention – Real time notification (e-mail, pagers),

improved auditing, Navigator for IBM i– Dynamic throttling down for clients initiating

DoS attacks

• Strengthen IBM i Integrity– Digitally sign all IBM i executables – Eradicate any altered programs through

automatic retranslation of IBM i executables

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

Page 6: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

6

Comparing Security Advisories

Windows® Server 2003

Source http://secunia.com/product/1174/?task=statistics Sept, 2008

Between 2003 and 2008, Microsoft Windows Server 2003 Enterprise Edition was affected by 166 Secunia issued advisories, 7% of which remain unfixed

Page 7: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

7

Comparing Security Advisories

Souce http://secunia.com/product/13949/?task=statistics Sept, 2008

Between 2003 and 2008, i5/OS V5Rx was affected by 1 Secunia issued advisory which was non critical and has been fixed

IBM i IBM i Security Conference

Page 8: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

8

IBM i Life Cycle

IBM i

06 07 08 09 10 11 12 13 14 15 16

V5R2

V5R3

5.4*

6.1*

7.1*

Service*The projected date for the service of IBM i releases is based on current IBM planning assumptions. Note that it is IBM’s current practice to support an IBM i release until the next two releases have been made available, plus twenty four months. This presentation contains information about IBM’s plans and directions. Such plans are subject to change without notice.

IBM i Upgrade

paths

01/11

Page 9: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

9

IBM i Program Conversion Preview

•Program conversion is required for IBM i 6.1 – Program conversion automatically upgrades software to

exploit latest system enhancements– IBM i 6.1 is not required for POWER6, can run i5/OS V5R4

•Conversion requires program's creation data (observability) – Since V5R1, all programs being created have had their

creation data automatically saved•Tool to analyze program conversion for i5/OS V5R3 / V5R4

– Identifies any potential issues and estimates conversion time

•Program conversion is performed during install/restore of applications, at first use or at scheduled time

Ensures unprecedented system integrityEnables exploitation of future system and processor capabilities

Delivers improved performance

Page 10: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

10

What to Do…?

• A Redpaper is available from www.ibm.redbooks.com– REDP-4293 “i5/OS Program

Conversion”

• Authors:– Paul Godtland

IBM i Development, Rochester

– Ian J Mills IBM i Support Centre, UK

– Debbie Landon ITSO, Rochester

Page 11: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

11

Planning Tools Available

•Tools are available to help validate your system •The Analyze Object Conversion (ANZOBJCVN) CL command is provided for i5/OS versions V5R3 and V5R4. –V5R3

MRI PTF SI27515 requires: PTF SI27513 (code). Code PTF SI27513 requires two PTFs:

– PTF for spooled files estimations SI25504.– PTF for analyze integrated file system names SI27473.

–V5R4 MRI PTF SI25550 requires: PTF SI25543 (code). Code PTF SI25543 requires two PTFs:

– PTF for spooled files estimations SI25502.– PTF for analyze integrated file system names SI26706.

•More PTFs may be required (language support) –Refer to Informational APAR II14306– http://www-

912.ibm.com/n_dir/nas4apar.nsf/c79815e083182fec862564c00079d117/3af47a966c4df94586257306003c6868?OpenDocument&Highlight=2,ii14306

Page 12: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

12

Overview

•What and why?• Improvement examples•About program conversion•Refresh choices

Page 13: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

13

What is being done?

•(Re-)create ALL MI programs– Integrated Language Environment– Original Program Model– Applications– IBM i and other IBM products

•Application re-creation usually done via conversion

Page 14: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

14

Trusted Code Trusted Code GeneratorGenerator

DatabaseDatabase CommCommStacksStacks

SecuritySecurityTask Task MgmtMgmt

Compilers

TIMI

ADDNCRTPGM

TIMI Instructions

CompilersCompilers User User ApplicationsApplications Work Work

MgmtMgmt

IBM i System Architecture

Save/RestoreSave/Restore

Page 15: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

15

source codecompiler

"machine" instructions

Thing

TIMI

HW-specificinstructions

"Translator"

LIC

•Key notes:–Must eventually get some hardware-specific instructions–IBM i architecture incorporates "translation" under the TIMI–Translator is hardware-specific

This is "observability"

Program Model Architecture

CRTPGM

Page 16: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

16

Historical Perspective

•6.1 MI program refresh – Easier for customers

been planned for awhile– Includes more investment in program

environment– Much less overall system change

•NOT like previous MI program refreshes– System/38 to AS/400 (V1R1, 1988)– CISC to RISC (V3R6, 1996)

48-bit to 64-bit addresses

Page 17: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

17

Why?

•Upgrade software without source changes– Capitalize on Machine Interface (MI) architecture

•Enhance:– Integrity– Performance– Function

•System technical vitality– MI architecture is not new– Provides refresh and

improvement capabilities that are among the best in the industrythis refresh while using these capabilities is also

providing foundation to extend them

Page 18: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

18

Integrity improvement examples

•Eradicate any altered programs that exist now– No chance to interfere with the system

•Extend unique ability to remove any future code corruption– Any runnable MI application can be refreshed at any time

Vendor programs with no source can be converted to check for possible corruption

– Prevent load of non-i ‘system state’ programs masquerading as ‘system state’ programsSystem state = higher privileged running environmentCan only be loaded as

part of operating system– Make system more robust

Page 19: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

19

Performance improvement examples

•Faster activation, procedure calls, pointer use

•More efficient memory handling– Remove limitation of software

teraspace emulation and use direct hardware support

– Improves speed of performance for ILE, PASE, etc

•Generate processor-specific code– Can “opt out” of adaptive code generation if desired

•New create options, no source changes required:– Optimize procedure call argument passing, between

modules (+20%) – ARGOPTPassing space pointers into a general purpose

register– Defer service program activation significantly improving

startup of applications – BNDSRVPGM(*DEFER)

Page 20: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

20

Adaptive Code Generation details•Defaults:

– Use features of hardware on which program is created/converted

– Convert when moving to different hardware only if required

•Use only features found on all systems (opt out)– Use LICOPT(‘CodeGenTarget=Common’) on CRT* or

CHG* commands– Set QIBM_BN_CREATE_WITH_COMMON_CODEGEN

environ var to 2•Optimize to latest hardware if not created there

– CHG(SRV)PGM FRCCRT(*YES) if observable creation data

– Restore (from save file, e.g.) using one of:RST{OBJ,LIB} FRCOBJCVN(*YES *ALL)

•First set system value QFRCCVNRST to 2 or higher•See ILE Concepts document

Page 21: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

21

Further create-time options detail

•CRTPGM and CRTSRVPGM parameters– Only available for target release 6.1– Optimize procedure calls between modules, within a

(service) program: ARGOPT(*YES)– Choose deferred activation, by service program:

BNDSRVPGM( (libA/srvpgmA *IMMED) (libB/srvpgmB *DEFER) ) for best performance, specify all *IMMED uses first

•See ILE Concepts document

Page 22: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

22

About Conversion

•Replace existing program object without compile•One-time process, but required either direction

V5R4 or V5R3 6.1 V5R4 or V5R3 6.1

•Part of all 6.1 systems– No options or added fees

•Average per-program convert times, large sample– Sub-second on fastest processors, <4 seconds on

slowest– Programs with many modules may take longer

Page 23: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

23

IBM i System Support

Servers IBM i 5.4 IBM i 6.1 IBM i 7.1

POWER7750, 770, 780

POWER6JS12, 22, 23/43, 550* 560

POWER6520, 550*, 570, 595

POWER5+515, 525

POWER5520, 550, 570, 595

800, 810, 825, 870, 890

270, 820, 830, 840

* Specific models

Page 24: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

24

Conversion exception cases

•Creation data (observability subset) not available– Creation data is available to Licensed Internal Code, unless

program (or constituent module) target release is before V5R1--AND--

creation data was explicitly removed– Must compile from source if creation data gone

•Program relies on unsupported alterations– Conversion removes such modifications– Must use supported interfaces instead

Page 25: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

25

Conversion method choices

• Run new ANZOBJCVN tool on V5R4 or V5R3– Identifies potential conversion issues, estimates times

• Choose combination of methods on 6.11. Scheduled

STROBJCVN by library1. First call/activation

pay-as-you-go, some initial delay1. Restore/install

FRCOBJCVN(*YES *ALL) or change QFRCCVNRST >= 2

• Must regenerate applications that won’t convert– compile from source or acquire

Page 26: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

26

Creation data status details

•Before using ANZOBJCVN can use DSPPGM or DSPSRVPGM

•Creation data unavailable for conversion if:– For ILE (service) programs, ‘All creation

data’ is *NO– For OPM programs, ‘Observable

information’ is *NONE

Page 27: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

27

Analyze Object Conversion – ANZOBJCVN (V5R3 & V5R4)

•Two ways to run ANZOBJCVN –Collect and Report

•Run collect in Batch – SBMJOB CMD(ANZOBJCVN OPTION(*COLLECT) LIB(*ALLUSR) SPLFILE(*YES) OBJ(‘/’)) JOB(ANZOBJCOL)

Page 28: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

28

Analyze Object Conversion…

Page 29: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

29

Program conversion methods

• Strongly advised to make all necessary preparations for object conversion prior to starting the upgrade or migration process.

• Conversion to 6.1 compatible format is a one-time only operation.

• The following methods are available to perform program object conversion:1. Using the 6.1 Start Object Conversion (STROBJCVN) CL

command to manually initiate conversion on program objects within libraries and the integrated file system.

2. During a restore3. The first time the program is run

Page 30: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

30

Object Conversion

1. Scheduled conversion– The 6.1 Start Object Conversion (STROBJCVN) command

is provided to manually initiate conversion on program objects within libraries and Java programs in the integrated file system

1. Restore– During an upgrade to 6.1, some IBM-supplied program

objects will either convert during the upgrade, or will be provided in a 6.1-compatible format on your install media.

1. Conversion the first time a program is run– Program objects that have not been converted earlier,

during restore or due to running the STROBJCVN command, will be converted when the program is first run.

Page 31: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

31

Start Object Conversion – STROBJCVN (6.1)

Page 32: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

32

Refresh method choices - ISVs•Application converted on each customer system

– Test conversion, inform customers of best methodconsider application time-out potential and

adaptive code generation•Rebuild and redistribute programs (and fixes)

– Required if program altered or lacks creation data – Recommended if:

VERY large programs usedapplication profiling data applied but was

removedyou add a digital signature, still needed on

customer systems– Perhaps build, ship both pre-6.1 and 6.1 versions

must build on separate partitionshave application install code select correct

version

Page 33: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

33

Summary

•Upgrade software without more programming– All MI programs refreshed, most by conversion– Deliver enhanced integrity, performance and function

•Increase system value with EXTREME integrity and flexibility – Now can convert any MI program (except IBM i) any

time– Enable much easier leverage of new hardware and

future system structure changes •Demonstrate IBM i technical vitality

Page 34: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

34

References• i5/OS Program Conversion Redpaper –

REDP-4293– http://www.redbooks.ibm.com/redpieces/abstracts/redp4293.html

• 6.1 Information Center document entitled IBM i: Installing, upgrading, or deleting IBM i and related software Version 6 Release 1 SC41-5120-09

• 6.1 Memo to Users• IBM i Upgrade planning Web site

– http://www-304.ibm.com/jct01004c/systems/support/i/planning/upgrade/index.html• Preparing for 6.1, IBM Systems Magazine

– http://www.ibmsystemsmag.com/print/print.aspx?print_page=%2Fibmi%2Fmarch08%2Ffeatures%2F19662printp1.aspx&string_referer=/ibmi/march08/features/19662p3.aspx

Page 35: Moving to IBM i 6.1 or 7.1 Power Systems Software · © 2010 IBM Corporation Moving to IBM i 6.1 or 7.1 Alison Butterill Power Systems Software

© 2009 IBM Corporation

IBM Power Systems

35

8 IBM Corporation 1994-2007. All rights reserved.References in this document to IBM products or services do not imply that IBM intends to make them available in every country.

Trademarks of International Business Machines Corporation in the United States, other countries, or both can be found on the World Wide Web at http://www.ibm.com/legal/copytrade.shtml.

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.Linux is a registered trademark of Linus Torvalds 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.UNIX is a registered trademark of The Open Group in the United States and other countries.Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.Other company, product, or service names may be trademarks or service marks of others.

Information is provided "AS IS" without warranty of any kind.

The customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products.

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

Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance 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 or performance improvements equivalent to the ratios stated here.

Photographs shown may be engineering prototypes. Changes may be incorporated in production models.

Trademarks and Disclaimers