sg248249 IBMi7.2

Front cover
Draft Document for Review December 10, 2014 2:51 pm
SG24-8249-00
IBM i 7.2 Technical Overview with

Technology Refresh Updates
Covers new functions and enhancements

through IBM i 7.2 TR1
Easy to use web-based system
management
Integrated Data-Centric
approach
Justin C. Haase
Dwight Harrison
Yohichi Nakamura
Edward Handy Satio
Jiri Sochr
Tom Vernaillen
Marcin Wilk
ibm.com/redbooks
8249edno.fm
International Technical Support Organization

IBM i 7.2 Technical Overview with Technology
Refresh Updates
December 2014
SG24-8249-00
8249edno.fm
Note: Before using this information and the product it supports, read the information in Notices on
page xxi.
First Edition (December 2014)

This edition applies to Version 7, Release 2, Modification 0, Technology Refresh 1 of IBM i (5770-SS1) and
related licensed programs.
This document was created or updated on December 10, 2014.
Copyright International Business Machines Corporation 2014. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
8249TOC.fm
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Now you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1
3
4
4
Chapter 1. Introduction to IBM i 7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 IBM i 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Technology Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.1 Definition and description of Technology Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.2 Ordering and checking installation status of the Technology Refresh . . . . . . . . . . 8
1.3 Upgrading or installing IBM i 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3.1 Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3.2 Pre-upgrade Verification Tool (PRUV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.3 POWER8 reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.4 POWER8 Update Access Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.5 Load source usable space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.6 HMC and CEC firmware levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.7 IBM i resave levels and their relationship to Technology Refresh . . . . . . . . . . . . 11
1.3.8 Network installation support for SLIC updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4 Documentation and support locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4.1 IBM Knowledge Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4.2 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4.3 Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4.4 Blogs and wikis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4.5 IBM i technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5 Sections of this Redbook publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.1 Systems Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.2 Cloud and Virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.4 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.5 High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.6 Backup and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.7 IBM DB2 for i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.8 Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.5.9 Server Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.6 Functions available at previous releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 2. Systems management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1 IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Copyright IBM Corp. 2014. All rights reserved.
iii
8249TOC.fm
2.1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.2 Usability and performance improvements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1.3 Search task by keywords and CL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1.4 Bookmark your favorite tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.1.5 File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1.6 Target system and System group support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1.7 PTF management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1.8 Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.1.9 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.1.10 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2.1.11 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.1.12 Omnifind Text Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
2.1.13 Disk management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
2.1.14 Partition management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
2.1.15 Support added for additional system values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2.1.16 Integrated Server Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
2.1.17 Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
2.1.18 Printers and printer output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
2.2 IBM i Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2.2.1 IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
2.2.2 IBM i Access for Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
2.2.3 IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
2.3 Application Runtime Expert for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
2.4 Journal management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
2.4.1 STRJRN parameter on restore commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
2.4.2 Deferred journal restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
2.4.3 Secure remote journal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
2.4.4 QJOSJRNE API change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
2.4.5 Journal conversion after IBM i 7.2 install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
2.4.6 Journal limits changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
2.4.7 New journal entry types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
2.4.8 Displaying journal information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
2.4.9 Journal Sizing and Planning Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
2.5 Work management enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
2.5.1 Temporary Storage Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
2.5.2 PTF related changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
2.5.3 IBM i command changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
2.5.4 API changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
2.6 Operating System Limitation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
2.7 IBM Advanced Job Scheduler for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
2.7.1 Advanced Job Scheduler Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
2.7.2 Work Flow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
2.8 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
2.8.1 Collection Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
2.8.2 Job Watcher Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Chapter 3. Cloud and virtualization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Cloud and virtualization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Cloud and IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 IBM PowerVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 OpenStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 IBM PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 IBM SmartCloud Entry for Power Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
IBM i 7.2 Technical Overview with Technology Refresh Updates
169
170
170
170
171
171
172
8249TOC.fm
3.2.5 IBM Cloud Manager with OpenStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.6 IBM Power Systems Solution Edition for Cloud . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.7 IBM i cloud offering summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 IBM PowerVP Virtualization Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 PowerVP components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 PowerVP GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 IBM i virtualization enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Virtual Partition Manager adds GUI to IBM Navigator for i . . . . . . . . . . . . . . . . .
3.4.2 iVirtualization release support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Utilizing SSDs for network storage spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4 Support of additional disks attached via VSCSI . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.5 Less-complex assignment of tape and optical resources . . . . . . . . . . . . . . . . . .
3.4.6 Define system resource usage during storage space creation . . . . . . . . . . . . . .
3.5 Live Partition Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Licensing and service provider accommodations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
172
173
174
174
174
175
176
176
177
177
178
178
178
179
179
Chapter 4. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Single Sign-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Password Rule & User Profile Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Intrusion Detection/Prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Intrusion Detection Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 IM Audit record detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 Cryptographic enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1 Vector Scalar eXtension and crypto acceleration . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2 Cryptographic Key Protection - Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3 Crypto Key Management Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 Cryptography for SSL and TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.1 Default value for QSSLPCL system value . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.2 Cipher specification list changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3 Elliptic Curve Cryptography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4 Multiple server certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.5 Signature and hash algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.8 DB2 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9 Networking security refrence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
181
182
183
184
186
186
187
187
187
188
190
190
191
191
192
195
195
196
Chapter 5. Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Domain Name System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Domain Name System Security Extensions (DNSSEC) . . . . . . . . . . . . . . . . . . .
5.1.2 IBM i resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Simple Network Management Protocol manager APIs . . . . . . . . . . . . . . . . . . . . . . . .
5.3 SR-IOV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 System SSL enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Virtual private networks (VPNs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 Internet Key Exchange (IKE) Protocol Version 2 . . . . . . . . . . . . . . . . . . . . . . . .
5.5.2 IKEv2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.3 IKEv2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.4 IBM i 7.2 IKEv2 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 Virtual Local Area Network (VLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.1 IBM i VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Retrieve and update TCP/IP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.1 Retrieve TCP/IP Information (RTVTCPINF) CL command . . . . . . . . . . . . . . . . .
5.7.2 Update TCP/IP Information (UPDTCPINF) CL command. . . . . . . . . . . . . . . . . .
5.8 IPv6 proxy neighbor discovery for virtual Ethernet and PPP . . . . . . . . . . . . . . . . . . .
197
198
198
199
199
200
200
201
202
202
202
203
206
206
208
209
209
209
Contents
8249TOC.fm
5.9 Single Sign-on for both FTP and TELNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

5.10 IBM i 7.2 Ethernet Device Server Support (WAN over LAN). . . . . . . . . . . . . . . . . . . 211
5.10.1 WAN over LAN requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
vi
Chapter 6. High availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 IBM PowerHA SystemMirror for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 PowerHA SystemMirror for i Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2 DS8000 HyperSwap Support with PowerHA for i 7.2 Express Edition . . . . . . . .
6.2.3 Support for SVC/Storwize Global Mirror with Change Volumes . . . . . . . . . . . . .
6.2.4 GUI changes in IBM Navigator for i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.5 Minimum cluster and PowerHA version for upgrading nodes to IBM i 7.2 . . . . .
6.3 Administrative Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Increased Administrative Domain Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2 Synchronization of object authority and ownership. . . . . . . . . . . . . . . . . . . . . . .
6.4 Independent Auxiliary Storage Pool (IASP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.1 DSPASPSTS improvements for better monitoring of vary-on time . . . . . . . . . . .
6.4.2 Reduced UID/GID processing time during vary-on . . . . . . . . . . . . . . . . . . . . . . .
6.4.3 IASP assignment for consolidated backups . . . . . . . . . . . . . . . . . . . . . . . . . . . .
215
216
217
217
218
221
222
222
223
223
224
224
224
226
226
Chapter 7. Backup and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 Newly-supported tape hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.1 IBM 3592-E08 Tape Drive specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.2 Media types and compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.3 Encryption capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 General save and restore functions provided by the OS . . . . . . . . . . . . . . . . . . . . . .
7.2.1 Better control over journaling during restoration of objects. . . . . . . . . . . . . . . . .
7.2.2 Faster configuration of independent disk pools with CFGDEVASP . . . . . . . . . .
7.2.3 Spooled file save enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.4 Select parameter (SELECT) added to various commands . . . . . . . . . . . . . . . . .
7.2.5 TCP/IP configuration data saved automatically . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.6 Even better IFS save performance with Asynchronous Bring. . . . . . . . . . . . . . .
7.2.7 Modifications on the SAVE and RESTORE menus . . . . . . . . . . . . . . . . . . . . . .
7.2.8 Removal of obsolete functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Backup, Recovery, and Media Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.1 BRMS Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.2 Usability improvements at IBM i 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.3 Backup function enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.4 Recovery function enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.5 Media services enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.6 Maintenance enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.7 BRMS GUI in IBM Navigator for i enhancements . . . . . . . . . . . . . . . . . . . . . . . .
7.3.8 Miscellaneous BRMS enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
229
230
230
230
231
231
231
232
233
234
234
235
235
235
235
236
239
240
244
244
250
252
259
Chapter 8. IBM DB2 for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Separation of duties concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.1 IQIBM_DB_SECADM function usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.2 Row and Column Access Control (RCAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.3 Special registers used for user identifications. . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.4 VERIFY_GROUP_FOR_USER Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.5 RCAC short example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.6 Add OR REPLACE for masks and permissions . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.7 InfoSphere Guardium 9.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
263
264
264
265
267
268
268
268
274
274
8249TOC.fm
8.3 Security Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.3.1 Add QIBM_DB_ZDA and QIBM_DB_DDMDRDA function usage IDs . . . . . . . .
8.3.2 Authorization List detail added to Authorization catalogs . . . . . . . . . . . . . . . . . .
8.3.3 QSYS2.GROUP_USERS() user defined table function . . . . . . . . . . . . . . . . . .
8.3.4 QSYS2.GROUP_PROFILE_ENTRIES new security view. . . . . . . . . . . . . . . .
8.3.5 SYSIBM.AUTHORIZATIONS new attribute column. . . . . . . . . . . . . . . . . . . . .
8.3.6 QSYS2.SQL_CHECK_AUTHORITY() UDF for determining select capability . .
8.3.7 Refined Object auditing control on the QIBM_DB_OPEN exit program . . . . . . .
8.3.8 Simplified DDM/DRDA authentication management using group profiles . . . . .
8.4 Functional enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.1 Increased timestamp precision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2 Named and Default parameter support on UDF/UDTFs . . . . . . . . . . . . . . . . . . .
8.4.3 Function resolution using casting rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4 Use of ARRAYs within scalar UDFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.5 Built-in global variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.6 Expressions on PREPARE & EXECUTE IMMEDIATE . . . . . . . . . . . . . . . . . . . .
8.4.7 Autonomous procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.8 New SQL statement TRUNCATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.9 New Built-in Functions LPAD() & RPAD(). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.10 Pipelined table functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.11 Regular expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.12 JOB_NAME & SERVER_MODE_JOB_NAME built-in global variables . . . . . .
8.4.13 RUNSQL control of output listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.14 LOCK TABLE ability to target non-*FIRST members . . . . . . . . . . . . . . . . . . . .
8.4.15 QUSRJOBI() retrieval of DB2 built-in global variables . . . . . . . . . . . . . . . . . . .
8.5 DB2 for i Services and Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.1 IBM DB2 for i Services tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.2 IBM DB2 for i Catalogs tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6 DB2 performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.1 SQE I/O cost model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.2 SQE support for native file opens, Query/400, and OPNQRYF . . . . . . . . . . . . .
8.6.3 PDI for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.4 Queries with a long IN predicate list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.5 Index advice and OR predicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.6 KEEP IN MEMORY for tables and indexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.7 Collection Services enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 Database engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7.1 IBM System i Navigator DB2 related functionality. . . . . . . . . . . . . . . . . . . . . . . .
8.7.2 IBM Navigator for i DB2 related functionality . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7.3 Queued exclusive locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7.4 CREATE TABLE AS SELECT from remote RDB . . . . . . . . . . . . . . . . . . . . . . . .
8.7.5 Live movement of tables and indexes to SSD . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7.6 Range partitioned tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8 DB2 Web Query for i (5733-WQX, 5733-WQE, and 5733-WQS) . . . . . . . . . . . . . . . .
8.9 OmniFind Text Search Server for DB2 for i (5733-OMF) . . . . . . . . . . . . . . . . . . . . . .
275
275
275
276
276
277
277
277
278
280
280
281
282
284
285
286
287
289
289
291
292
293
293
294
294
294
295
297
301
302
303
305
308
308
309
316
316
316
320
325
326
326
326
327
328
Chapter 9. Application development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1 Languages and Compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Control Language (CL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 ILE RPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 ILE COBOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4 ILE C/C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5 System APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
331
332
332
336
344
346
348
Contents
vii
8249TOC.fm
viii
9.2 Java on i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.1 IBM Developer Kit for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.2 IBM Toolbox for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Rational Tools for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.1 IBM Rational Developer for i (RDi) V9.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.2 IBM Rational Application Developer for WebSphere Software (RAD) . . . . . . . .
9.3.3 IBM Rational Business Developer (RBD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.4 IBM Rational Team Concert (RTC) for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.5 IBM Rational Host Access Transformation Services (HATS) . . . . . . . . . . . . . . .
9.3.6 IBM Rational Application Management Toolset (AMT) . . . . . . . . . . . . . . . . . . . .
9.3.7 ARCAD Pack for Rational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 PASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5 Ruby on Rails for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6 Zend Server and PHP on i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6.1 What is new in Zend Server 7? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6.2 Zend Server Community Edition for IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6.3 Zend Server for IBM i Version 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6.4 Zend Studio for IBM i V11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6.5 Zend DBi and actual PHP database support . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.7 Mobile application development for IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
348
348
351
352
353
359
360
362
363
366
368
370
370
370
371
371
372
373
373
374
Chapter 10. IBM i server functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.1 IBM HTTP Server for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.1 Licensed program requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.2 Upgraded to Apache 2.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.3 Web Admin for managing WebSphere Application Server installation . . . . . . .
10.2 IBM i Integrated Web Application and Web Services Server . . . . . . . . . . . . . . . . . .
10.2.1 IBM i Integrated Web Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2 IBM i Integrated Web Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 IBM WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 Supported WebSphere Application Server on IBM i 7.2 . . . . . . . . . . . . . . . . . .
10.3.2 WebSphere Application Server Liberty Core Packaging. . . . . . . . . . . . . . . . . .
10.3.3 WebSphere Application Server Liberty Profile . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.4 Installation of WebSphere Application Server to IBM i . . . . . . . . . . . . . . . . . . .
10.3.5 Upgrading to IBM i 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 IBM Social Collaboration products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5 IBM Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.1 CPYSPLF command now support PDF format . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.2 Controlling the method of sending spooled files from list panels . . . . . . . . . . .
10.5.3 Changes to TrueType and OpenType Fonts. . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.4 New bar code types for printer DDS BARCODE keyword . . . . . . . . . . . . . . . .
10.5.5 Common Image Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.6 Color Management Support added to Print Services Facility for IBM i . . . . . . .
10.5.7 Host Print Transform now supports color images . . . . . . . . . . . . . . . . . . . . . . .
10.5.8 AFP color and grayscale solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
375
376
376
376
378
378
379
380
382
382
383
384
384
384
385
385
385
385
386
386
387
387
387
388
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
389
389
389
389
389
8249LOF.fm
Figures
1-1 Graphical representation of the cumulative structure of Technology Refresh . . . . . . . . 7
1-2 The IBM i 7.2 section of the Knowledge Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2-1 Search task by keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2-2 save action as a Favorite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2-3 Upload files to IFS on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2-4 Download files from IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2-5 Edit files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2-6 IFS edit functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2-7 Deep IFS path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2-8 Target systems and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2-9 Program Temporary Fixes tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2-10 Display PTFs - options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2-11 Display PTFs - specific licensed product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2-12 Install PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2-13 Install PTFs - options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2-14 Remove PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2-15 Confirm remove PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2-16 Cleanup PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2-17 Clean up PTFs - confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2-18 Send PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2-19 Send PTF Wizard - Add Target system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2-20 Send PTF Wizard - Target system added. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2-21 Send PTF Wizard - How to send PTFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2-22 Send PTF Wizard - summary with selected options . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2-23 Sending PTFs progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2-24 Send and Install PTFs option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2-25 Send and Install PTFs progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2-26 Send PTF group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2-27 Send PTF group wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2-28 Send PTF group wizard - Target system added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2-29 Send PTF group wizard - available options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2-30 Send PTF group wizard - summary screen with selected options . . . . . . . . . . . . . . . 35
2-31 Sending PTF group progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2-32 Send and install PTF group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2-33 Send and install PTF group progress and results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2-34 Load individual PTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2-35 Apply individual PTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2-36 Remove individual PTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2-37 Remove individual PTF - confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2-38 Clean up individual PTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2-39 Clean up individual PTF - confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2-40 Display PTF properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2-41 Display PTF properties - details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2-42 Send individual PTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2-43 Install individual PTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2-44 Install PTFs - PTF ID to select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2-45 Install PTFs by PTF ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2-46 Send and install PTF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
ix
8249LOF.fm
2-47
2-48
2-49
2-50
2-51
2-52
2-53
2-54
2-55
2-56
2-57
2-58
2-59
2-60
2-61
2-62
2-63
2-64
2-65
2-66
2-67
2-68
2-69
2-70
2-71
2-72
2-73
2-74
2-75
2-76
2-77
2-78
2-79
2-80
2-81
2-82
2-83
2-84
2-85
2-86
2-87
2-88
2-89
2-90
2-91
2-92
2-93
2-94
2-95
2-96
2-97
2-98
2-99
x
Compare and update PTFs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Compare and update wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compare and update wizard - available options . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compare and update wizard - add target system . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compare and update wizard - products to compare . . . . . . . . . . . . . . . . . . . . . . . . . .
Compare and update wizard - missing / extra PTFs result . . . . . . . . . . . . . . . . . . . . .
Compare and update wizard - results for target system . . . . . . . . . . . . . . . . . . . . . . .
Create new message monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create message monitor - General page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create message monitor - Message Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create message monitor - Message set 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create message monitor - Add A Message Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create message monitor - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Monitor Actions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create New Message Monitor - Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Monitor - Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create New System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create System Monitor - General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create New System Monitor - Add Metric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create New System Monitor - Configure Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create New System Monitor - Summary Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Monitors - Actions menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Investigate Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure Collection Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure Collection Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Retention configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Monitor Categories - customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performance Data Reports task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report Data Definition example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drill down information in Performance Data Investigator title bar . . . . . . . . . . . . . . . .
System Information view in PDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Batch Model menu in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Batch Model page in IBM Navigator for i. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completed batch model creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Change Batch Model Calibration page in Batch Model . . . . . . . . . . . . . . . . . . . . . . .
Change Batch Model page in Batch Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting batch model investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Batch Model investigation result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Storage Allocation Overview in PDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Storage Allocation/Deallocation Overview Perspective . . . . . . . . . . . . . . . . . . . . . . .
Storage Allocation/Deallocation by thread or task . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory Perspective in Performance Data Investigator . . . . . . . . . . . . . . . . . . . . . . .
Memory Pool Sizes and Fault Rates in Performance Data Investigator . . . . . . . . . . .
Memory Pool Activity Levels in Performance Data Investigator . . . . . . . . . . . . . . . . .
DB and Non-DB Page Faults Overview in Performance Data Investigator. . . . . . . . .
Java perspective menu in Performance Data Investigator . . . . . . . . . . . . . . . . . . . . .
Java memory graph in Performance Data Investigator. . . . . . . . . . . . . . . . . . . . . . . .
Java Memory by job in Performance Data Investigator . . . . . . . . . . . . . . . . . . . . . . .
Temporary Storage perspective in Performance Data Investigator . . . . . . . . . . . . . .
Security Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security Wizard - startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enterprise Identity Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
45
45
46
47
48
48
50
50
51
52
52
53
54
55
55
58
58
58
59
60
60
61
62
66
67
67
68
69
70
70
71
72
73
73
74
75
76
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
2-100
2-101
2-102
2-103
2-104
2-105
2-106
2-107
2-108
2-109
2-110
2-111
2-112
2-113
2-114
2-115
2-116
2-117
2-118
2-119
2-120
2-121
2-122
2-123
2-124
2-125
2-126
2-127
2-128
2-129
2-130
2-131
2-132
2-133
2-134
2-135
2-136
2-137
2-138
2-139
2-140
2-141
2-142
2-143
2-144
2-145
2-146
2-147
2-148
2-149
2-150
2-151
2-152
8249LOF.fm
Omnifind text search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Concurrent removal of disk unit from ASP - confirmation . . . . . . . . . . . . . . . . . . . . . 92
Removal of disk units from ASP - available actions . . . . . . . . . . . . . . . . . . . . . . . . . 92
Cancel disk unit removal process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Solid state disks (SSD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Service tools - Disk management tasks access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Disk pool menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Rebuild disk unit data - failed disk within RAID protected set . . . . . . . . . . . . . . . . . . 95
Stop and resume allocating data to disk units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Create Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Create Partition Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Work with partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
IBM Navigator for i - System values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
System values - Network attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Resource allocation prioriity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Resource allocation priority parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4K sector size support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Sector size in bytes parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
SSD support added. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Preferred storage unit parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Allowed/restricted tape or optical device resources . . . . . . . . . . . . . . . . . . . . . . . . 106
Integrated server administration - Server Properties . . . . . . . . . . . . . . . . . . . . . . . 107
Allow access and Restrict access fro devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Windows Server 2012 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
New ReFS file system for Windows 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Integrated Server Storage Space creation - Storage pool selection . . . . . . . . . . . . 110
Storage pool selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Virtual printer support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Exporting spoolfiles as PDF using Infoprint Server. . . . . . . . . . . . . . . . . . . . . . . . . 113
IBM i Access Client Solutions components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Main user interface of IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . 117
Functions restriction example in IBM i Access Client Solutions . . . . . . . . . . . . . . . 118
Restricted functions in IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . 119
Console bar in 5250 console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Virtual Control Panel connection to HMC console . . . . . . . . . . . . . . . . . . . . . . . . . 120
Convert Macro menu in 5250 Session Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Convert Macro window in IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . . . 121
IBM i Access for Web main user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
IBM i Access for Web page showing alternative views of active jobs . . . . . . . . . . . 124
IBM i Access for Web page showing elapsed data for active jobs . . . . . . . . . . . . . 125
IBM i Access for Web page showing thread data for active jobs . . . . . . . . . . . . . . 125
IBM i Access for Web page showing installed products . . . . . . . . . . . . . . . . . . . . . 126
IBM i Access for Web page showing PTF status . . . . . . . . . . . . . . . . . . . . . . . . . . 126
IBM i Access for Web page showing PTF groups. . . . . . . . . . . . . . . . . . . . . . . . . . 127
IBM i Access for Web page showing system values categories . . . . . . . . . . . . . . . 127
IBM i Access for Web page showing list of IBM i object data that can be extracted 128
Filter box for context-based filtering in IBM i Access for Web. . . . . . . . . . . . . . . . . 128
Start session parameter for secure telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Secure telnet in 5250 session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Main user interface of IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Working with active jobs in IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Action buttons pop-up menu in IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . 133
Running SQL on IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figures
xi
8249LOF.fm
2-153 SQL output viewed in IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-154 Starting 5250 session on IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-155 5250 telnet session on IBM i Mobile Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-156 5250 secure telnet session on IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . .
2-157 Journaling information available for particular table on Tables panel . . . . . . . . . . .
2-158 Detailed journaling information for database table . . . . . . . . . . . . . . . . . . . . . . . . .
2-159 New View Entires... menu option on Journals panel. . . . . . . . . . . . . . . . . . . . . . . .
2-160 Journal Viewer panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-161 Accessing temporary storage buckets information . . . . . . . . . . . . . . . . . . . . . . . . .
2-162 Temporary Storage Deatils panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-163 System-wide temporary storage usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-164 Temporary storage information on Extended System Status screen . . . . . . . . . . .
2-165 Temporary storage information on the Work with Active Jobs screen . . . . . . . . . .
2-166 Active Jobs panel with Temporary Storage Information for every job. . . . . . . . . . .
2-167 Peak temporary storage value on Display Job Run Attributes screen . . . . . . . . . .
2-168 Temporary storage information on the Display Job Tables screen. . . . . . . . . . . . .
2-169 Maximum temporary storage information on CPF1164 message. . . . . . . . . . . . . .
2-170 Message text for CPI112E, new to IBM i 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-171 CPF090A message when ASP temporary storage threshold is reached . . . . . . . .
2-172 CPI11AB message when temporary storage bucket threshold is reached . . . . . . .
2-173 Display PTF details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-174 Display Delayed Superseded PTFs - option 12 . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-175 Advanced Job Scheduler Properties page in IBM Navigator for i . . . . . . . . . . . . . .
2-176 Job Controls/Applications page in Advanced Job Scheduler Properties . . . . . . . .
2-177 Library Lists page in Advanced Job Scheduler Propoerties . . . . . . . . . . . . . . . . . .
2-178 Command Variables page in Advanced Job Scheduler Properties . . . . . . . . . . . .
2-179 Permissions page in Advanced Job Scheduler Properties . . . . . . . . . . . . . . . . . . .
2-180 Fiscal Calendar page in Advance Job Scheduler Properties . . . . . . . . . . . . . . . . .
2-181 New Data Library enhanced parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-182 Work Flow Manager in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-183 CRTPFRSUM parameter in CRTPFRDTA command. . . . . . . . . . . . . . . . . . . . . . .
3-1 PowerVP architecture showing system agents communicating with the GUI . . . . . . .
3-2 Sample PowerVP CPU affinity view.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3 Creating a new network storage space with a preferred storage unit of *SSD . . . . . .
4-1 STRTCPTELN F4 (Prompt) or TELNET F4 (Prompt) . . . . . . . . . . . . . . . . . . . . . . . . .
4-2 FTP F4 (Prompt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3 iNav GUI interface for configuration IDS policies . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4 iNav GUI interface for configuration - Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-5 Intrusion Detection Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6 How do you securely store this master key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-7 Manage Master Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-8 Key Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-9 Create Key Store Files via Navigator (6.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-10 Digital certificate manager, updating certificate assignments . . . . . . . . . . . . . . . . . .
4-11 Default cipher suites for IBM i 7.2 and 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1 Internet Key Exchange (IKE) version setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2 Virtual Private Networking Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-3 ECDSA Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-4 IBM i VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-5 Interfaces list has new VLAN ID column to display VLAN ID assignments. . . . . . . . .
5-6 Equivalent CL configuration IBM i VLAN Naming Considerations . . . . . . . . . . . . . . .
5-7 WAN over LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-8 CRTLINASC Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii
135
136
137
138
141
142
142
142
145
145
146
147
148
148
149
150
151
152
153
153
155
155
158
159
160
161
162
163
163
164
167
175
176
178
182
183
185
185
186
188
188
189
189
193
194
202
203
204
207
207
208
212
213
8249LOF.fm
6-1 PowerHA SystemMirror for i Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-2 PowerHA SystemMirror for i Replication Technology . . . . . . . . . . . . . . . . . . . . . . . . .
6-3 PowerHA SystemMirror for i Express Edition with DS8000 HyperSwap. . . . . . . . . . .
6-4 DSPHYPSTS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5 CHGHYSSTS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-6 DSPHYSSTS command when suspended . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-7 HyperSwap with Live Partition Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-8 ADDHYSSTGD command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-9 PowerHA GUI in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-10 The cluster and PowerHA version in IBM i 7.2 release level . . . . . . . . . . . . . . . . . .
6-11 Managing MRE options in PowerHA GUI in IBM Navigator for i. . . . . . . . . . . . . . . .
6-12 DSPASPSTS ENTRIES(*ALL) displays records of the previous varying operations
6-13 Displaying UDFS information via DSPASPSTS command . . . . . . . . . . . . . . . . . . . .
6-14 Attaching IASPs out of the cluster device domain to a single partition . . . . . . . . . . .
6-15 CFGDEVASP ASPDEV(*ALL) ACTION(*PREPARE) command . . . . . . . . . . . . . . .
6-16 'Detect attached IASP disk units' screen of SST. . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-17 'Display Disk Configuration Status' screen of SST . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1 Initial display from the Configure Device ASP (CFGDEVASP) command . . . . . . . . .
7-2 Display allowing selection of non-configured disk units for ASP creation . . . . . . . . . .
7-3 Section of the Save Object (SAVOBJ) command with the new SELECT parameter .
7-4 View of the Update TCP/IP Information (UPDTCPINF) command . . . . . . . . . . . . . . .
7-5 Panel showing the default value for automatic refresh within BRMS Enterprise . . . .
7-6 The drop-down in Hub Administration which allows setting the refresh interval. . . .
7-7 The BRMS Enterprise hub center with an automatic refresh of 30 minutes selected .
7-8 Choosing *ENT as an option for reporting within BRMS Enterprise . . . . . . . . . . . . . .
7-9 A view of a BRMS Enterprise group containing a system with a failed backup . . . . .
7-10 System-specific options available from the Failed Backups panel . . . . . . . . . . . . . .
7-11 Options available for subsetting a view of failed backups. . . . . . . . . . . . . . . . . . . . .
7-12 BRMS Enterprise view of an unsuccessful control group on a node . . . . . . . . . . . .
7-13 BRMS object list containing the *ALLUSR value along with specific exclusions . . .
7-14 View for the same object list within IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . .
7-15 Subsystem end options at IBM i 7.2 in BRMS System Policy. . . . . . . . . . . . . . . . . .
7-16 Reset move cycle in Change Move Policy screen . . . . . . . . . . . . . . . . . . . . . . . . . .
7-17 Reset move cycle in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-18 Change Move Policy with optIon to move marked for duplication. . . . . . . . . . . . . . .
7-19 Move policy parameters in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-20 Change Media Class screen with parameter for expired media initialization . . . . . .
7-21 Initialize media on expiration in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . .
7-22 DUPPMEDBRM command with submit batch options . . . . . . . . . . . . . . . . . . . . . . .
7-23 RGZBRMDB parameter in STRMNTBRM command . . . . . . . . . . . . . . . . . . . . . . . .
7-24 Reorganize BRMS database option in IBM Navigator for i . . . . . . . . . . . . . . . . . . . .
7-25 Additional parameters in RMVMEDIBRM command. . . . . . . . . . . . . . . . . . . . . . . . .
7-26 Various BRMS Policies in BRMS Navigator for i. . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-27 BRMS System Policy in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-28 BRMS Backup Policy in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-29 BRMS Archive Policy in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-30 BRMS Retrieve Policy in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-31 BRMS Recovery Policy in IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-32 Checkboxes for marking volume for Initialize and Ignore Active Files . . . . . . . . . . .
7-33 Control Group help text in PRTRPTBRM TYPE(*CTLGRPSTAT) command . . . . . .
7-34 Data compaction help text in DUPMEDBRM command . . . . . . . . . . . . . . . . . . . . . .
8-1 Part of WRKFCNSUSG Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-2 Part of Display Function Usage screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures
216
217
218
219
219
220
221
221
222
223
224
225
226
227
227
228
228
232
233
234
234
236
237
237
238
238
238
239
239
240
241
242
245
246
246
247
248
248
249
250
251
252
253
254
255
256
257
258
259
260
261
265
266
xiii
8249LOF.fm
8-3 Part of Change Function Usage Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

8-4 Filled up Change Function Usage screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
8-5 Display Function Usage Screen with authority granted to SECADMINS group profile. 267
8-6 EMPLOYEE table as seen by the JONES user profile (Chief) . . . . . . . . . . . . . . . . . . 273
8-7 EMPLOYEEt table as seen by the KADLEC user profile. . . . . . . . . . . . . . . . . . . . . . . 274
8-8 EMPLOYEE table as seen by the JANAJ user profile. . . . . . . . . . . . . . . . . . . . . . . . . 274
8-9 Example of the use of QSYS2.GROUP_USERS() UDTF. . . . . . . . . . . . . . . . . . . . . . 276
8-10 Example of use of QSYS2.GROUP_PROFILE_ENTRIES . . . . . . . . . . . . . . . . . . . . 276
8-11 Example of use of SYSIBM.AUTHORIZATIONS Catalog. . . . . . . . . . . . . . . . . . . . . 277
8-12 Example of use of the QSYS2.SQL_CHECK_AUTHORITY UDF . . . . . . . . . . . . . . 277
8-13 Result of the first SELECT statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
8-14 Result of the second SELECT statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
8-15 Result of VALUES statement which uses the UDF. . . . . . . . . . . . . . . . . . . . . . . . . . 282
8-16 Result of VALUES statement with an error SQLCODE -204 . . . . . . . . . . . . . . . . . . 283
8-17 Result of VALUES statement with the FUNCTION found with casting rules . . . . . . 284
8-18 Result of a scalar User Defined Functions which uses an array. . . . . . . . . . . . . . . . 285
8-19 Result of a example of an AUTONOMOUS procedure . . . . . . . . . . . . . . . . . . . . . . . 288
8-20 Syntax of TRUNCATE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
8-21 Result of SELECT statement with LPAD() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
8-22 Result of SELECT statement with RPAD() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
8-23 Result of a example of LPAD() for DBCS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
8-24 New parameters described on the RUNSQL command . . . . . . . . . . . . . . . . . . . . . . 293
8-25 SQL Plan Cache Statements and Visual Explain view for OPNQRYF . . . . . . . . . . . 304
8-26 SQL Plan Cache Statements view for OPNQRYF within IBM Navigator for i . . . . . . 304
8-27 New Database related perspectives for PDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
8-28 SQL CPU Utilization by Job and Task PDI view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
8-29 Plan Cache Searches PDI view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
8-30 Memory-preference information for table definition on IBM System i Navigator . . . . 310
8-31 Memory-preference information for table description on IBM System i Navigator . . 311
8-32 Memory-preference information for index definition on IBM System i Navigator . . . 312
8-33 Memory-preference information for index description on IBM System i Navigator . . 313
8-34 Memory-preference information for table definition on IBM Navigator for i. . . . . . . . 314
8-35 Memory-preference information for table description on IBM Navigator for i . . . . . . 314
8-36 Memory-preference information for index definition on IBM Navigator for i . . . . . . . 315
8-37 Memory-preference information for index description on IBM Navigator for i . . . . . . 315
8-38 New Date Created column on the Indexes list panel. Filtered view . . . . . . . . . . . . . 317
8-39 SQL Performance Monitor Wizard enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 318
8-40 New fields on the table definition panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
8-41 Specific Program Statements for user-defined table function in Visual Explain . . . . 319
8-42 Investigate Performance Data menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
8-43 New Show Job History menu option on the SQL Plan Cache Statements panel . . . 321
8-44 New column Times Advised Dependent on Other Advice on Index Advisor panel. . 322
8-45 New filter option on the Show Statements Filters panel . . . . . . . . . . . . . . . . . . . . . . 322
8-46 New options available on Generate SQL panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
8-47 New View Contents menu option on Tables panel . . . . . . . . . . . . . . . . . . . . . . . . . . 324
8-48 New information on the Table Reorganization status panel . . . . . . . . . . . . . . . . . . . 325
9-1 OPM (Original Program Model) RPG from OS/400 V2R3 . . . . . . . . . . . . . . . . . . . . . 337
9-2 /FREE and /END-FREE in C-Spec of ILE RPG in OS/400 V5R1 . . . . . . . . . . . . . . . . 337
9-3 Support of embedded SQL within /Free and /END-FREE at ILE RPG in i5/OS V5R3 338
9-4 Free-form control, file, definition, and procedure statements in ILE RPG of IBM i 7.2 338
9-5 Result of java -version under specifying IBM Technology for Java 7.1 64-bit. . . . . . . 351
9-6 Launching Batch Code Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
9-7 Code Coverage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
xiv
8249LOF.fm
9-8 Source member with annotations which lines were covered . . . . . . . . . . . . . . . . . . .

9-9 Example of Code Coverage HTML report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-10 D-Specification Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-11 Procedure Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-12 Java Method Call Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-13 Filter field of the Outline view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-14 Concept of Push-to-client function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-15 Application Management Toolset for i includes modified components of ADTS. . . .
9-16 Main menu for Application Management Toolkit for i . . . . . . . . . . . . . . . . . . . . . . . .
9-17 Zend PHP Application development and deployment architecture for IBM i. . . . . . .
9-18 Zend DBi and MySQL using DB2 Storage engine . . . . . . . . . . . . . . . . . . . . . . . . . .
10-1 Create Application Server wizard in IBM Web Administration for i in IBM i 7.1 . . . .
10-2 Create Application Server wizard in IBM Web Administration for i in IBM i 7.2 . . . .
10-3 Concept of IWS V2.6 powered by Liberty Profile and JAX-RS . . . . . . . . . . . . . . . . .
10-4 WebSphere Application Server for i packaging options . . . . . . . . . . . . . . . . . . . . . .
Figures
355
355
356
356
357
358
359
367
368
371
373
379
380
381
383
xv
8249LOF.fm
xvi
8249LOT.fm
Tables
2-1 System Monitor Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2-2 Program launcher locations for IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . 116
2-3 Filed name changes on Work with System Status screen . . . . . . . . . . . . . . . . . . . . . 146
2-4 Changed files for Collection Services enhancements. . . . . . . . . . . . . . . . . . . . . . . . . 165
2-5 Changed files for Job Watcher enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
3-1 Supported iVirtualization combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
4-1 Format of an IM entry type journal record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
5-1 New Key Exchange Policy Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
5-2 New Data Policy Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
5-3 Legacy Key Exchange and Data Policy algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . 206
7-1 3592-E08 Tape Drive specification compared to the previous models . . . . . . . . . . . . 230
7-2 Usability improvements in IBM i 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
8-1 Special registers for identifying users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
8-2 Authorization catalogs containing AUTHORIZATION_LIST column. . . . . . . . . . . . . . 276
8-3 Built-in Global Variables newly introduced in IBM i 7.2. . . . . . . . . . . . . . . . . . . . . . . . 285
8-4 Function or Predicate for Regular Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
8-5 DB2 for i Services - Health Center Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
8-6 DB2 for i Services - Utility Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
8-7 DB2 for i Services - Plan Cache Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
8-8 Performance Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
8-9 Application Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
8-10 Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
8-11 PTF Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
8-12 TCP/IP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
8-13 Work Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
8-14 Object Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
8-15 Storage Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
8-16 journal Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
8-17 System Health Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
8-18 Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
8-19 Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
8-20 Database Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
8-21 Tables - Views - Indexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
8-22 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
8-23 Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
8-24 Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
8-25 ROUTINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
8-26 XML Schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
8-27 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
8-28 Miscellaneous objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
8-29 Disk read times for storage technologies compared to original SQE cost model . . . 302
8-30 SQE_NATIVE_ACCESS parameter values in QAQQINI file . . . . . . . . . . . . . . . . . . 303
8-31 MEMORY_POOL_PREFERENCE parameter values. . . . . . . . . . . . . . . . . . . . . . . . 309
8-32 PREVENT_ADDITIONAL_CONFLICTING_LOCKS parameter values . . . . . . . . . . 325
9-1 Classic Java levels and the suggested IBM Technology for Java replacement . . . . . 349
9-2 Supported options of 5770JV1 IBM Technology for Java in IBM i 7.2 . . . . . . . . . . . . 350
xvii
8249LOT.fm
xviii
8249LOE.fm
Examples
1-1 Listing of various IBM i 7.2 PTF Group packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2-1 Displaying content of temporary storage buckets in SYSTMPSTG file. . . . . . . . . . . . 144
5-1 Load filter rules on all interfaces, including VPN rules . . . . . . . . . . . . . . . . . . . . . . . . 201
5-2 Export VPN configuration to a stream file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
5-3 Start and end a VPN connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
7-1 Restoration of 15 libraries using RSTLIBBRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
7-2 Restoration of libraries specified in a *RSTLST using RSTLIBBRM. . . . . . . . . . . . . . 244
8-1 Group profiles for hospital example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
8-2 User profiles for hospital example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
8-3 Creating schema, table, index, and filling up with data . . . . . . . . . . . . . . . . . . . . . . . 270
8-4 Example of Row access rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
8-5 Example of creating column mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
8-6 Denying user profile the usage of DDM and DRDA application server access. . . . . . 275
8-7 Object auditing control on the QIBM_DB_OPEN exist program . . . . . . . . . . . . . . . . . 278
8-8 Using group profile authentication entry to access remote database. . . . . . . . . . . . . 278
8-9 How to set up the QIBM_DDDMDRDA_SVRNAM_PRIORITY environment variable 279
8-10 Increased timestamp precision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
8-11 Named and default parameter support on UDF/UDTFs . . . . . . . . . . . . . . . . . . . . . . 281
8-12 VALUES statement which specifying a different value to the parameter in UDF . . . 282
8-13 Sample function that casting might have occurred . . . . . . . . . . . . . . . . . . . . . . . . . . 282
8-14 Array Support in scalar User Defined Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
8-15 Example of a SELECT statement to get a client information from global variables . 286
8-16 Getting a client information from TCP/IP Services in QSYS2 . . . . . . . . . . . . . . . . . . 286
8-17 Example of EXECUTE IMMEDIATE with concatenating strings prior to IBM i 7.2 . . 286
8-18 Example of EXEXUTE IMMEDIATE with concatenating strings at IBM i 7.2 . . . . . . 287
8-19 Autonomous Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
8-20 LPAD() built-in functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
8-21 SELECT statement with RPAD() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
8-22 Example of Pipeline SQL UDTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
8-23 Example of External UDTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
8-24 Example of regular expressions in a pipelined table function . . . . . . . . . . . . . . . . . . 292
8-25 DSPDF partial output with Keep in memory field . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
8-26 Creating a table that reflects definition on a remote server with data . . . . . . . . . . . . 326
8-27 Creating range partitioned table with partitions out of order . . . . . . . . . . . . . . . . . . . 327
9-1 Retrieving a numeric value from a string by using %CHECK and %CHECKR . . . . . . 333
9-2 Searching for a specific string by using %SCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
9-3 Trimming blanks by using %TRIM function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
9-4 Example of %SUBDT built-in function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
9-5 Example of TIMESTAMP keyword in a free-form definition . . . . . . . . . . . . . . . . . . . . 340
9-6 The content of info1.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
9-7 Example of specifying remove as ns option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
9-8 The content of info2.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
9-9 Example of specifying merge as ns option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
9-10 The content of info3.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
9-11 Example of specifying ns_ as nsprefix option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
9-12 The content of info4.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
9-13 Example of specifying convert as case option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
9-14 Example of setting IBM Technology for Java 71 64-bit to JAVA_HOME . . . . . . . . . 351
xix
8249LOE.fm
10-1 Example of CPYSPLF command with *PDF option . . . . . . . . . . . . . . . . . . . . . . . . . 385
xx
8249spec.fm
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product, program, or service that does not
infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not grant you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any
manner serve as an endorsement of those websites. The materials at those websites are not part of the
materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring
any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the results
obtained in other operating environments may vary significantly. Some measurements may have been made
on development-level systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of 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.
This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs.
xxi
8249spec.fm
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. These and other IBM trademarked terms are
marked on their first occurrence in this information with the appropriate symbol ( or ), indicating US
registered or common law trademarks owned by IBM at the time this information was published. Such
trademarks may also be registered or common law trademarks in other countries. A current list of IBM
trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
AIX
AS/400
AS/400e
CICS
DB2
developerWorks
Domino
DRDA
DS8000
FICON
FlashCopy
Global Technology Services
Guardium
HyperSwap
i5/OS
IBM
IBM Flex System
IBM SmartCloud
InfoSphere
Integrated Language Environment
iSeries
Jazz
Language Environment
Lotus
Lotus Notes
Notes
OmniFind
OS/400
POWER
Power Systems
POWER6
POWER6+
POWER7
POWER7+
POWER8
PowerHA
PowerVM
PowerVP
Print Services Facility
ProtecTIER
PureFlex
PureSystems
Rational
Rational Team Concert
Redbooks
Redpaper
Redbooks (logo)
S-TAP
Sametime
Storwize
System i
SystemMirror
Systems Director VMControl
Tivoli
WebSphere
Worklight
z/OS
z/VM
The following terms are trademarks of other companies:

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States,
other countries, or both.
Java, and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its
affiliates.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.
xxii
8249pref.fm
Preface
This IBM Redbooks publication provides a technical overview of the features, functions,
and enhancements available in IBM i 7.2, including all the available Technology Refresh (TR)
levels, which for this version of this publication covers TR1. This publication provides a
summary and brief explanation of the many capabilities and functions in the operating
system. It also describes many of the licensed programs and application development tools
that are associated with IBM i.
The information that is provided in this book is useful for clients, IBM Business Partners, and
IBM service professionals that are involved with planning, supporting, upgrading, and
implementing IBM i 7.2 solutions.
Authors
This book was produced by a team of specialists from around the world working at the
International Technical Support Organization, Rochester Center.
Justin C. Haase is a technical manager for Sirius Computer

Solutions headquartered in San Antonio, TX. He works in the
Managed Services practice of the company, where Sirius
provides system management and technical support for
customers running various platforms, including IBM i running
on Power Systems. He has 15 years of experience in service
bureau and hosting environments running the IBM i family of
operating systems, with his first managed system being a
9406-740 12-way AS/400e at V4R5 of the OS, the largest
AS/400 machine IBM produced at the time. Mr. Haase has
also assisted IBM in development of Power Systems
certification tests as a subject matter expert. He resides in
Kasson, MN with his wife Rayelle and son Noah.
Dwight Harrison is an IBM i hardware remote support
specialist at the IBM i Global Support Center in Rochester,
Minnesota. After serving in the United States Marine Corps, he
started his IBM career in January 1970 in Rochester,
Minnesota. One year later he transferred to Omaha, Nebraska,
as a customer engineer. In January 1984, he transferred back
to the Rochester site as a lab technician. In August 1987, he
transferred back to North Platte, Nebraska, as a remote
customer engineer where he installed and serviced the AS/400
until January 1993 when he accepted a position in the IBM i
Global Support Center in Rochester, Minnesota. From 1993 to
present, he assists with world wide IBM i hardware support. He
has helped author several System Handbooks, System
Builders, and other Redbooks publications.
8249pref.fm
Yohichi Nakamura is an Advisory IT Specialist for IBM Power

Systems and IBM i. He joined IBM Japan Systems Engineering
Co., Ltd., which is a subsidiary of IBM Japan, as IBM i
Advanced Technical Support in 2003. From 2010 to 2013, he
worked as a Technical Sales Specialist, which holds both of
FTSS and ATS roles, in IBM Japan. From 2013 to present, he
assists many of actual projects related to Power Systems and
IBM i as a subject matter expert. His areas of expertise include
virtualization, external storage, high availability, iSCSI
integration, performance analysis, WebSphere Application
Server for i, backup/recovery, ProtecTIER with i, and overall
of IBM i operations. He holds a master degree of aerospace
engineering at Osaka Prefecture University, Japan.
Edward Handy Satio is an IT Specialist for IBM i and Power
Systems in IBM Indonesia. His area of expertise includes IBM i
on external storage, high availability, performance analysis and
tuning, and IBM i problem determinations. He has been
supporting IBM i and Power Systems implementation projects,
technical support, and consultancy in Indonesia. He is also one
of technical advocates to an IBM regional customer. He holds
Bachelor of Computer Science in Artificial Intelligence and
Bachelor of Applied Science in Computational Mathematics,
both from Universitas Pelita Harapan. Apart from IBM
publications, he has several technical publications related to
artificial intelligence.
Jiri Sochr is an Open Group Master Certified IT Specialist at
IBM Delivery Centre Central Europe in Brno, Czech Republic.
He provides third level support for IBM i customers located in
Europe. Jiri is Senior Subject Matter expert in EMEA Technical
Leadership Team. He has 25 years experience in AS/400,
iSeries, and POWER Systems hardware, IBM i software
products, application development, workload management,
security, performance, and external and internal storage
solutions. He has a broad knowledge of other IBM platforms
and products. He specializes in IBM i complex problem
determination and multiplatform solutions. He also works as an
IT Architect for projects where IBM i is part of the whole
solution, Jiri holds Doctor degree in Natural Sciences from the
Faculty of Mathematics and Physics, Charles University,
Prague, Czech Republic. Jiri joined IBM in 2009. Before joining
IBM, he worked for an IBM Business Partner company as an
IBM i systems engineer and technical leader. Jiri can be
reached at Jiri.Sochr@cz.ibm.com.
Tom Vernaillen is a Senior IT Specialist in Belgium. His areas
of expertise include IBM i problem determination, network
connectivity, and communications, including TCP/IP. He has
participated in previous ITSO residencies, preparing technical
overview presentation material and writing TCP/IP
communications-related IBM Redbooks publications for IBM i.
He is an Enhanced Technical Support remote Account
Advocate for several IBM Power Systems customers.
8249pref.fm
Marcin Wilk is an IBM Certified Expert IT Specialist working as

a Front Office technical support specialist at IBM Global
Technology Services in Poland. He joined IBM in 2003. After
taking extensive technical training at Global Support Center in
Rochester, MN, USA he has been supporting IBM i customers
in Poland. His area of expertise includs: Power Systems
virtualization, consolidation, performance analysis and tuning
for IBM i and WebSphere Application Server, and complex
problem determination. He holds a mater degree in Computer
Science in databases, networks and computer systems at
Silesian University of Technology, Poland.
This first edition of this IBM Redbooks project was led by:
Debbie Landon
International Technical Support Organization, Rochester Center
Thanks to the following people for their contributions to this project:
Ann Lund
International Technical Support Organization, Rochester Center
Craig Aldrich, Robert Bestgen, David Bhaskaran, Jeff Block, John Broich, David Charron,
Jim Chen, Jenny Dervin, Scott Forstie, Mark Goff, Michael Groeschel, Bruce Hansel,
Joe Kochan, Daniel Laun, Terry Luebbe, Tim Mullenbach, Matthew Neill, Brian Nordland,
Chad Olstad, Lora Powell, Scott Prunty, Carol Ramler, Marilin Rodriguez, Tim Rowe,
Mike Russell, Mike Schambureck, Curt Schemmel, Dennis Schroeder, Robert Seemann,
Ellie Streifel, Jim Tilbury, Jeff Uehling, Nancy Uthke-Schmucki, Duane Wenzel, Steve Will,
Jill Wilson, Don Zimmerman
IBM Rochester
Zhang Gan, Shuang Hong Wang, Chang Qing Zheng
IBM China
Edmund Reinhardt, Alfonso Rodriguez,
IBM Canada
Jay Johnson
Sirius Computer Solutions
Now you can become a published author, too!

Heres an opportunity to spotlight your skills, grow your career, and become a published
authorall at the same time! Join an ITSO residency project and help write a book in your
area of expertise, while honing your experience using leading-edge technologies. Your efforts
will help to increase product acceptance and customer satisfaction, as you expand your
network of technical contacts and relationships. Residencies run from two to six weeks in
length, and you can participate either in person or as a remote resident working from your
home base.
Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html
Preface
8249pref.fm
Comments welcome
Your comments are important to us!
We want our books to be as helpful as possible. Send us your comments about this book or
other IBM Redbooks publications in one of the following ways:
Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
Send your comments in an email to:
redbooks@us.ibm.com
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400
Stay connected to IBM Redbooks

Find us on Facebook:
http://www.facebook.com/IBMRedbooks
Follow us on Twitter:
http://twitter.com/ibmredbooks
Look for us on LinkedIn:
http://www.linkedin.com/groups?home=&gid=2130806
Explore new Redbooks publications, residencies, and workshops with the IBM Redbooks
weekly newsletter:
https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm
Stay current on recent Redbooks publications with RSS Feeds:
http://www.redbooks.ibm.com/rss.html
8249_Intro.fm
Chapter 1.
Introduction to IBM i 7.2

This chapter describes the newest release of the IBM i operating system, version 7.2. It
includes details relating to new features and functionality available at this release, as well as a
brief history of the operating system. Hardware prerequisites are also listed in this chapter.
Many of the topics covered in this IBM Redbook publication will be summarized in this
introduction chapter. For further details on the specific topics, refer to the appropriate
chapters later in this book.
8249_Intro.fm
1.1 IBM i 7.2

On May 2, 2014, IBM i 7.2 was made generally available. This release is the 23rd major
release of the IBM i family of operating systems. Previous releases included i5/OS and
OS/400.
On October 6, 2014, IBM i 7.2 Technology Refresh 1 was announced.
The following website indicates the dates of support for various IBM i releases:
http://www-947.ibm.com/systems/support/i/planning/upgrade/suptschedule.html
1.2 Technology Refresh

IBM i 7.2 will continue to use the Technology Refresh concept for product updates throughout
the life of the operating system.
For more information about the Technology Refresh PTF Group, as well as much more detail
regarding the Technology Refresh concept, see this website:
http://www-947.ibm.com/systems/support/i/planning/techrefresh/index.html
1.2.1 Definition and description of Technology Refresh

Technology Refresh was introduced in IBM i 7.1 and allows for updates to the operating
system which affect mainly the System Licensed Internal Code (SLIC), I/O, and virtualization
functions. These updates are delivered using a PTF Group, but provide changes and
enhancements which were normally reserved for SLIC updates or even full releases.
Definition of Technology Refresh: A collection of OS software for new function
enablement that is packaged together, tested together, and delivered as a single PTF
Group.
Additionally, new and updated products within the OS are bundled together and delivered at
approximately the same time as a Technology Refresh - these also use PTF Groups. This
allows for major enhancements to occur during the same timeframe as the Technology
Refresh release.
By implementing Technology Refresh, IBM i became even more flexible and responsive to a
changing environment without adding the burden of installing and qualifying a new release in
order to keep their systems up-to-date. The Technology Refresh made it possible to
implement new hardware and software features in a way which was relatively seamless and
using a familiar PTF application process for end-users. By simply ordering and applying the
latest Technology Refresh PTF Group, the system would be updated and the new features
would be ready to use.
8249_Intro.fm
Note: Large enhancements to parts of IBM i are released at the same time as Technology
Refreshes, but they are typically not dependent upon each other. For example, if you
ordered only the new Technology Refresh PTF Group, you would not receive the
improvements to DB2 for i or for BRMS. Updates to DB2 for i are included in the
Database PTF Group. Updates to BRMS are handled within the Backup and Recovery
Solutions PTF Group. Schedules of releases have potential to vary in cadence among PTF
Group releases and Technology Refreshes.
It is important to review cover letters and online documentation for all groups and
Technology Refreshes to ensure that you are ordering the necessary fixes to acquire the
new functionality which is desired.
Similar to firmware updates, Technology Refreshes are cumulative - all the new features
which are introduced in earlier Technology Refreshes are included in later ones, and only the
most current version is orderable. Previous versions become unavailable for ordering once a
new Technology Refresh is released.
Figure 1-1 shows a representation of how Technology Refreshes relate to the IBM i operating
system, as well as how the Technology Refresh PTF Group is ordered. The figure indicates
how contents of Technology Refresh 1 are included in Technology Refresh 2, and likewise
how the contents of Technology Refresh 1 and 2 are included with Technology Refresh 3.
This pattern continues through all iterations of Technology Refreshes for the current release
of the IBM i version which supports Technology Refreshes.
Note: To order the newest Technology Refresh, you must order the IBM i 7.2 Technology
Refresh PTF Group - SF99717.
Technology Refresh 3
Base OS
IBM i 7.2 Technology Refresh PTF Group

SF99717
Figure 1-1 Graphical representation of the cumulative structure of Technology Refresh
Chapter 1. Introduction to IBM i 7.2
8249_Intro.fm
Examples of notable contents of Technology Refreshes

IBM i 7.1 TR4: Support for Live Partition Mobility (LPM).
IBM i 7.1 TR8: Increased number of disks for VSCSI connections from 16 to 32.
IBM i 7.1 TR9: Support for IBM i 7.1 on POWER8 Enterprise Systems hardware.
IBM i 7.2 TR1: Support for IBM i 7.2 on POWER8 Enterprise Systems hardware.
1.2.2 Ordering and checking installation status of the Technology Refresh

To order the most recent Technology Refresh PTF Group at IBM i 7.2, you should use the
group identifier of SF99717. All Technology Refreshes are ordered using the PTF Group.
Future Technology Refresh packages are orderable using the SF99717 identifier, but will
contain additional fixes to support the level of the most recent Technology Refresh.
It is not possible to remove an installed Technology Refresh level without performing a
reinstallation of the Licensed Internal Code - this is colloquially known as slipping the SLIC.
See 1.3.7, IBM i resave levels and their relationship to Technology Refresh on page 11 for
more details.
Always review cover letters for the Technology Refresh PTF Group, as well as any other
PTFs, prior to applying to your system to ensure there are no special instructions for which
you should account.
To order fixes, use IBM Fix Central located at the following link:
http://www.ibm.com/support/fixcentral
You can review your installed Technology Refresh level by using the Work with PTF Groups
command (WRKPTFGRP) and looking at the installed level of SF99717.
Releases of software enhancements which are produced at the same approximate time as
Technology Refreshes are orderable and viewable the same manner. Ordering is performed
by using the appropriate PTF Group identifier. Examples of some IBM i 7.2 PTF Group
identifiers are shown in Example 1-1.
Example 1-1 Listing of various IBM i 7.2 PTF Group packages
SF99720
SF99776
SF99775
SF99767
SF99766
SF99759
SF99747
SF99721
SF99719
SF99718
SF99717
SF99716
SF99715
SF99713
SF99702
SF99481
SF99480
IBM i 7.2 Cumulative PTF Package

High Availability for IBM i
Hardware and Related PTFs
TCP/IP PTF Group
Print PTF Group
IBM MQ for IBM i - v7.1.0/v8.0.0
DB2 Web Query for i v2.1.0
All PTF Groups Except Cumulative PTF Package
Group Hiper
Group Security
Technology Refresh
Java
Backup Recovery Solutions
IBM HTTP Server for i
DB2 for IBM i
WebSphere App Server v8.5
WebSphere App Server v8.0
8249_Intro.fm
1.3 Upgrading or installing IBM i 7.2

Upgrading from IBM i 7.1 and 6.1 to version 7.2 are both supported paths. If a system is
running at a release older than 6.1, upgrading to either IBM i 6.1 or 7.1 is required prior to
performing the upgrade to IBM i 7.2.
1.3.1 Supported hardware

IBM i 7.2 will run on many different models of Power Systems machines. There are various
prerequisites which must be met to ensure a successful installation or upgrade.
Note: IBM i 7.2 is not supported on any POWER5 or POWER5+ system.
POWER8 Enterprise Systems models (Requires IBM i 7.2 with TR1)
E880 9119-MHE
E870 9119-MME
POWER8 Scale-out Power Systems models
S814 8286-41A
S824 8286-42A
POWER7/7+
POWER7+ 750/760 (these models do not support native I/O)
Power 710, 720, 730, 740, 770, 780, 795
PureFlex p260/p460
POWER6/6+
POWER6+ JS23, JS43, 520, 550, 560
POWER6 JS12, JS22, 520, 550, 570, 595
Note: IBM i 7.2 provides no support for IOPs or for HSL connectivity.
Additional information about hardware and firmware prerequisites can be found on the
developerWorks web site:
http://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/IBM%20i%20Tec
hnology%20Updates/page/Hardware%20and%20Firmware
Also, review the Memo to Users for IBM i 7.2 for further detail on hardware requirements and
supported combinations, especially as they relate to POWER6 hardware. The Memo to Users
also includes many useful links showing where to begin planning for your particular upgrade
strategy.
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaq9/rzaq9.pdf
8249_Intro.fm
1.3.2 Pre-upgrade Verification Tool (PRUV)

Use of the PRUV tool is optional, but can provide excellent benefit. It can help in determining
if needed prerequisite fixes are on the system, as well as ensure all pre-upgrade steps have
been taken in an effort to ensure the smoothest and fastest upgrade possible. It additionally
checks for various items that may have been caused during previous migrations
Link to PRUV:
http://www-01.ibm.com/support/docview.wss?uid=nas8N1014074
1.3.3 POWER8 reference documentation

For detailed information about POWER8 Enterprise Servers, refer to the IBM Power Systems
E870 and E880 Technical Overview and Introduction:
http://www.redbooks.ibm.com/redpieces/abstracts/redp5137.html
For detailed information about POWER8 Scale-out systems, refer to the IBM Power Systems
S814 and S824 Technical Overview and Introduction:
http://www.redbooks.ibm.com/abstracts/redp5097.html
For specific IBM i information relating to hardware, visit the IBM developerWorks site for IBM i
hardware:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/beb2d3aa-56
5f-41f2-b8ed-55a791b93f4f/page/Hardware%20and%20Firmware
1.3.4 POWER8 Update Access Keys

POWER8 servers include an Update Access Key (UAK) which is checked when system
firmware updates are applied to the system. UAKs include an expiration date, and system
firmware updates will not be processed if the calendar date has passed the UAKs expiration
date.
As these update access keys expire, they need to be replaced using either the Hardware
Management Console (HMC), the Advanced Management Interface (ASMI) on the service
processor, or directly using the update_flash command.
See the document at the following link for details on UAK on POWER8 servers:
http://www-01.ibm.com/support/docview.wss?uid=isg3T1020902
1.3.5 Load source usable space

When using native-attached SAS and SCSI disk units, IBM i 7.2 requires a 70 GB load source
disk with a certain amount of usable space. As of Technology Refresh 1, externally-attached
and iVirtualization-attached virtual disks have lower space requirements.
Review the calculation data at this website to ensure the appropriate space exists on your
machine:
http://www.ibm.com/developerworks/ibmi/software
10
8249_Intro.fm
1.3.6 HMC and CEC firmware levels

Be sure to validate your CEC and HMCs are at an appropriate version to run IBM i 7.2. CEC
firmware requirements and compatible HMC releases can be found at the following links:
IBM i server firmware and HMC code wizard:
http://www-912.ibm.com/s_dir/slkbase.NSF/DocNumber/408316083
IBM Power code matrix:
https://www-304.ibm.com/webapp/set2/sas/f/power5cm/home.html
1.3.7 IBM i resave levels and their relationship to Technology Refresh

Resaves of IBM i are created from time to time due to new hardware releases and other
issues which require addressing by IBM i development. Resaves are also produced when a
new Technology Refresh is released.
In the normal course of business, using a resave to install a Technology Refresh is not
required. However, there may be situations where utilizing a new resave may be necessary.
See this link for the most current information regarding IBM i 7.2 resave levels and information
on determining what is currently installed on a particular system:
http://www-947.ibm.com/systems/support/i/planning/resave/v7r2.html
1.3.8 Network installation support for SLIC updates

Replacing the Licensed Internal Code from an image located in NFS is supported at IBM i
7.2. See the following link for more details:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahc/restor.htm
1.4 Documentation and support locations

Systems used to ship with large volumes of paper-based reference documentation. Over the
past several years, the tendency has moved to online access of support information. Even
more recently, tools such as wikis have made documentation much more fluid and immediate.
1.4.1 IBM Knowledge Center

Reference documentation is located at the IBM Knowledge Center, formerly known as
InfoCenter.
The Knowledge Center for IBM i is located at the following link:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i/welcome
Navigation and search in the Knowledge Center has been significantly improved over the
previous InfoCenter. See Figure 1-2 on page 12 for an example view of the Knowledge
Center for IBM i 7.2.
11
8249_Intro.fm
Figure 1-2 The IBM i 7.2 section of the Knowledge Center
1.4.2 IBM Redbooks

IBM Redbook publications are another level of technical documentation for IBM i, as well as
many other IBM products and solutions. The Redbooks website is located here:
http://www.redbooks.ibm.com
1.4.3 Announcements
Another communication method the IBM i team uses is the Request for Announcement
(RFA). The RFA is the formal document that contains information about a function that is
being delivered to the market. For more information and to search for various RFAs, go to the
IBM Offering Information - Announcement letters website at:
http://www-01.ibm.com/common/ssi/
1.4.4 Blogs and wikis

Social media outlets such as wikis, developerWorks, Twitter, and blogs are meant as a way to
immediately distribute new information to customers and users. Many times, these locations
will provide links back to Redbooks or the Knowledge Center for reference.
developerWorks for IBM i is located here:
http://www.ibm.com/developerworks/ibmi/
Steve Will is the IBM i Chief Architect. His You and i blog is located here:
http://ibmsystemsmag.blogs.com/you_and_i/
Dawn May is an IBM Senior Technical Staff Member. Her iCan blog is located here:
http://ibmsystemsmag.blogs.com/i_can/
12
8249_Intro.fm
1.4.5 IBM i technical support

IBM i technical support can be reached online or via telephone for opening of service
requests. Use the IBM support website at the following link, or contact 800.IBM.SERV toll-free
in the US.
http://www.ibm.com/support
1.5 Sections of this Redbook publication

Following is a brief description of the different chapters in this document.
1.5.1 Systems Management

Various items will be covered in this chapter, including things such as IBM Navigator for i,
Advanced Job Scheduler, improved mobile access, as well as other work management
topics.
1.5.2 Cloud and Virtualization

In this chapter, you will find coverage of items pertaining to virtualization and cloud
implementations. Topics include PowerVP, SmartCloud Entry, and iVirtualization.
1.5.3 Security
This chapter will cover enhancements to security in IBM i 7.2, as well as methods these new
features can be implemented to help make your system more secure.
1.5.4 Networking
Many new functions have been added to networking in IBM i 7.2. This chapter will cover these
enhancements, as well as discuss how they can be put in place to help improve your
environment.
1.5.5 High Availability

PowerHA and improvements to processes relating to other high availability software
products will be covered in this chapter.
1.5.6 Backup and Recovery

IBM i 7.2 provides another leap in functionality for Backup, Recovery, and Media Services
(BRMS). Improvements to base save and restore operations also have been implemented.
This chapter will discuss these enhancements and provide examples.
1.5.7 IBM DB2 for i

Significant enhancements are introduced in IBM DB2 for i at release 7.2 of IBM i. Security,
performance, and usability improvements are covered within this chapter. Additionally, an
13
8249_Intro.fm
overview of Row and Column Access Control and links to more specific documentation is
provided.
1.5.8 Application Development

Coverage of free-form RPG, mobile access and data consumption improvements, PHP,
WebSphere, Liberty, and other new items.
1.5.9 Server Enhancements

Any topics which didnt fit specifically in the previous sections are included in this chapter.
Some items include printing and social collaboration tools.
1.6 Functions available at previous releases

This publication is in support of improved features and functionality available at IBM i 7.2.
Certain things listed in this book may be possible using previous releases of IBM i. For
example, running on a Power Systems E880 server is supported at IBM i 7.1 as long as
Technology Refresh 9 is installed. Additionally, some features of BRMS, DB2 for i, and IBM
Navigator for i have been backleveled in to IBM i 7.1 and 6.1. However, many other features
such as Row and Column Access Control are available at IBM i 7.2 only.
This document is not meant as a reference guide for cross-release compatibility, and
statements of existence of a feature or requirement at IBM i 7.2 does not necessarily confirm
or deny existence at any other release.
14
8249_SystemsMgmnt.fm
Chapter 2.
Systems management
This chapter provides the explanation on System Management on IBM i, which includes:
2.1, IBM Navigator for i on page 16

2.2, IBM i Access on page 113
2.3, Application Runtime Expert for i on page 138
2.4, Journal management on page 138
2.5, Work management enhancements on page 143
2.6, Operating System Limitation Changes on page 157
2.7, IBM Advanced Job Scheduler for i on page 157
2.8, Performance on page 165
15
2.1 IBM Navigator for i

The IBM Navigator for i is a Web console interface. It allows you to perform the key tasks to
administer your IBM i. The vast majority of tasks that are available in the System i Navigator
Windows client application are also supported within IBM Navigator for i. There is also
additional function available in IBM Navigator for i that is not found in the System i Navigator
Windows client. Unlike the Windows client application, nothing needs to be installed on your
workstation to be able to use IBM Navigator for i. The Web application is part of the base IBM
i operating system, and can easily be accessed by pointing your browser to
http://system:2001.
2.1.1 Requirements
IBM Navigator for i is installed as part of the IBM i operating system. It is part of SS1 option 3.
The following list of IBM i license programs is recommended to use with IBM Navigator for i:
5770SS1 option 1, Extended Base Support
5770SS1 option 3, Extended Base Directory Support
5770SS1 option 12, Host Servers
5770SS1 option 30, Qshell
5770SS1 option 33, Portable App Solutions Environment
5770DG1 value *BASE, IBM HTTP Server for i
5770JV1 value *BASE, IBM Developer Kit for Java
5770JV1 option 11, Java SE 6 32 bit
5770JV1 option 12, Java SE 6 64 bit
5770PT1 option 1, Manager Feature (provides access to PDI Disk Watcher, Database and
PEX packages, Batch model)
5770PT1 option 3, Job Watcher (provides access to PDI Job Watcher package)
The actual PTFs are all packaged and delivered as part of the HTTP PTF group. In addition,
there are also a number of other PTF groups that are required to ensure that all parts of the
IBM Navigator for i interface function properly:
SF99713 - level 3 - HTTP Server group
SF99714 - level 1 - Performance Tools Group PTF
SF99702 - level 2 - Database Group PTF
SF99716 - level 3 - Java Group PTF
For the most current list of required PTFs for IBM Navigator for i, see the following website:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20T
echnology%20Updates/page/IBM%20Navigator%20for%20i%20-%20V7R2%20Content
For more information about IBM Navigator for i, see the IBM i 7.2 Knowledge Center at the
following website:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzat10/rzatgdirectorove
rview.htm?lang=en
16
2.1.2 Usability and performance improvements

By using dojo technology, we now have significant improvements in IBM i 7.2 within the
workspace for the following areas:
the navigation area
common list view
handling of tabs
Navigation area
Similar to the IBM i Navigator client application, the task categories can now be opened to
display any resource containers in the navigation area. It is now much easier and quicker to
access desired tasks.
Common list view

Common list views now use new dojo tables that make it easier and quicker to filter lists, scroll
through large lists, and select items in the list to perform related actions.
Handling of tabs
Once multiple tasks are selected, resulting in multiple tabs in the console workspace, data is
no longer refreshed each time you click back to a previous tab.
Note: Both IBM i 7.1 and IBM i 6.1 will have the same performance improvements starting
with the Fall 2014 PTF (TR1) for IBM Navigator for i. In this PTF the IBM i 7.2 performance
improved code will be released in the PTFs for IBM i 7.1 and IBM i 6.1.
2.1.3 Search task by keywords and CL commands

On the welcome page within the IBM Navigator for i, it is now possible to simply enter a
keyword as search argument and the related commands will automatically show up. Simply
clicking on the corresponding CL command, will redirect you to the corresponding task within
the navigation pane as shown in Figure 2-1. This is a quick way to access a particular task
without having to navigate to it via the navigation hierarchy.
Chapter 2. Systems management
17
Figure 2-1 Search task by keyword
Note: You can also simply type in a phrase that describes what you want to find (ex: create
a user) or a system value (ex: qpwdlvl).
2.1.4 Bookmark your favorite tasks

We have a new Favorites node in the navigation area. Those favorites will be saved and
shown by user profile and system:
It is possible to save a particular list view as a favorite
Favorites can also be organized by category
There are probably a few specific areas of the IBM i that you quite often use during your daily
job. So if youre interested in the jobs for a specific user, select Users and Groups Users.
Find the user profile you are interested in. Right-click the user profile. Select User
Objects Jobs. From the Actions menu, select Save as Favorite from the list. You can
specify a name for the task (TOMV_jobs in our example) and the category (SYSMGMT in our
example) that you want.
From now on, task TOMV_jobs will show up in the SYSMGMT category under the Favorites
node in the navigation area for further reference as shown in Figure 2-2 on page 19.
18
Figure 2-2 save action as a Favorite
2.1.5 File Systems

The following new actions were added to IBM Navigator for i for IBM i 7.2, allowing users to:
upload files to an IBM i directory
download files from an IBM i directory
edit certain types of files
Upload files to an IBM i directory

In IBM i 7.2, within the File System task in IBM Navigator for i, the users can now upload files
from their PC or some mapped drive to an IBM i, as shown in Figure 2-3 on page 20.
19
Figure 2-3 Upload files to IFS on IBM i
Download files from an IBM i directory

A similar interface is available for downloading files from IBM i IFS to the users desired
location, as shown in Figure 2-4 on page 21.
20
Figure 2-4 Download files from IBM i
Edit certain types of files

Another feature that is now available with IBM i 7.2 is the ability to edit files via the IBM
Navigator for i interface. First of all you have to specify the file types you want to be able to
edit as shown in Figure 2-5 on page 22:
from the main IFS list, select Properties from the actions drop-dead menu
enter the file extensions you want to be able to edit afterwards
select OK
21
Figure 2-5 Edit files
The user will now see the Edit action appear for this type of files when right clicking on such
files within the IBM Navigator for i. Selecting that action will result in the edit window as shown
in Figure 2-6.
Figure 2-6 IFS edit functionality
The user now has full edit functionality for that specific file: he can modify it and afterwards
save it accordingly.
Go to Integrated File System Folder

The Go to Integrated File System Folder function has been added in IBM i 7.2. It allows you to
quickly go to a desired folder within the Integrated File System. All the previous selections are
saved by user profile and system within the IBM Navigator for i environment.
Within IBM Navigator for i in IBM i 7.2, it is now possible to enter directly a specific IFS path as
shown in Figure 2-7. This will save you a lot of time by not having to drill down the whole IFS
path.
22
Figure 2-7 Deep IFS path
2.1.6 Target system and System group support

Target Systems and Groups is a brand new navigation node in the IBM Navigator for i
navigation area as shown in Figure 2-8.
Figure 2-8 Target systems and Groups
A new interface is available to specify the target system to manage and to be able to group
similar target systems into groups. A specific target system can be part of several systems
groups however. You can select to manage another IBM i 7.2 system. IBM i 7.1 as well as IBM
i 6.1 systems are also supported.
In our example, we have defined one System group with 2 Target systems:
one running IBM i 7.2
23
one running IBM i 7.2 with TR1 installed
2.1.7 PTF management

Within IBM Navigator for i in IBM i 7.2, it is now possible to perform PTF management related
functions. Program Temporary Fixes is a brand new section under the Configuration and
Service task navigation area as shown in Figure 2-9 on page 24.
It allows you to perform the following:
Display PTFs: display PTFs for a specified product
Display PTF groups: display all group PTFs on an IBM i system
Load PTFs: load selected PTFs
Apply PTFs: apply selected PTFs
Install PTFs: install selected PTFs
Remove PTF: remove selected PTFs
Cleanup PTFs: delete PTF save files and cover letters for selected PTFs or all PTFs for
selected products
Figure 2-9 Program Temporary Fixes tasks
24
Working with PTFs

On the Display PTFs screen, for the different licensed products installed on the system, you
have the following options available, as shown in Figure 2-10 on page 25.
Open
Install PTFs
Remove PTFs
Cleanup PTFs
Send
Send and install
Figure 2-10 Display PTFs - options
Display PTFs
To display PTFs for a specific licensed product, select Open results in the screen as shown in
Figure 2-11 on page 25.
Figure 2-11 Display PTFs - specific licensed product
Install PTFs
To install PTFs for a specific licensed product, select Install PTFs results in the screen as
shown in Figure 2-12 where you click Next.
25
Figure 2-12 Install PTFs
You can now specify the install source as well and the install type from the following options
as shown in Figure 2-13 on page 27:
Install source:
service support system
tape or optical device
Install type:
install fixes immediately
install fixes and restart the system
install fixes the next time the system is restarted
Select Next will bring you to the screen as shown in Figure 2-13 on page 27.
26
Figure 2-13 Install PTFs - options
Select Next to confirm the install source and install type for the PTF installation.
Remove PTFs
In order to remove PTFs for a specific licensed product, select Remove PTFs. This will get
the user to the remove PTF screen as shown in Figure 2-14. Now click OK to confirm the
remove PTF function.
27
Figure 2-14 Remove PTFs
Note: Specifying to include the removal of dependent PTFs for all PTFs is NOT valid and
results in an error.
Click Remove to confirm the final remove PTFs option results in the screen as shown in
Figure 2-15 Confirm remove PTFs
This will start the removal process of all PTFs for the specified licensed program product.
Clean up PTFs
To cleanup PTFs for a specific licensed product, select Clean up PTFs as shown in
Figure 2-16 on page 29. Then click OK on the Clean up PTFs screen.
28
Figure 2-16 Cleanup PTFs
You now get to the Confirm clean up PTFs screen. Click Clean up will start the clean up
process of the PTFs for the specified licensed program product.
Figure 2-17 Clean up PTFs - confirm
This will remove all save files and cover letters for the specified licensed program product
from the system.
Send PTFs
It is now also possible within IBM Navigator for i to send PTFs from one system to a target
system or even a system group (as discussed earlier in 2.1.6, Target system and System
29
group support on page 23). In order to send PTFs for a specific licensed product, select
Send as shown in Figure 2-18 on page 30.
Figure 2-18 Send PTFs
This will get you to the Send PTF wizard screen as shown in Figure 2-19. You can select the
Target system you want the PTFs to be sent to at the left side of the screen and select Add
and then select Next.
Note: The Send PTFs can also be applied to a specific product option, not only to the
product itself.
Figure 2-19 Send PTF Wizard - Add Target system
The Target system will be added as shown in Figure 2-20 on page 31. Select Next.
30
Figure 2-20 Send PTF Wizard - Target system added
This will bring you to the screen as shown in Figure 2-21 where you have the following options
when sending the PTFs:
send requisite PTFs, which is the recommended way
send PTFs even though they are already installed on the target system
send the cover letters
override the savefiles if they already exist on the target system
Figure 2-21 Send PTF Wizard - How to send PTFs

31
You will get to the screen as shown in Figure 2-22 with a summary of the selected options to
be taken into account when sending the PTFs. Click Finish.
Figure 2-22 Send PTF Wizard - summary with selected options
The screen, as shown in Figure 2-23, will show you the progress of sending the PTFs:
copying the PTFs to an image on the local IBM i system
sending the PTF package
clean up on the local IBM i system
Figure 2-23 Sending PTFs progress
Note: In case of failure, there is the possibility for the user to have a look into the log with
the View Log option in the descriptions column.
Send and install PTFs

It is also possible within IBM Navigator for i to first send PTFs from one system to a target
system or a system group (as discussed earlier in 2.1.6, Target system and System group
support on page 18) and then immediately afterwards install those PTFs on the target
system or system group. In order to send and install PTFs for a specific licensed product,
select Send and Install as shown in Figure 2-24 on page 33.
32
Figure 2-24 Send and Install PTFs option
The process would be exactly the same as described earlier in, Send PTFs on page 29
except that afterwards those PTFs would also immediately be installed on the target system
or system group. The result is shown in Figure 2-25.
Note: The Send and install PTFs can also be applied to a specific product option, not only
to the product itself.
Figure 2-25 Send and Install PTFs progress
the View Log option in the descriptions column
Send PTF groups

From the Display PTF Groups screen, it is also possible to send a specific PTF group to a
target system or a system group by right-clicking that group PTF as shown in Figure 2-26 on
page 33 and selecting Send.
Figure 2-26 Send PTF group
33
The Send PTF group wizard screen will show up as shown in Figure 2-27 on page 34. You
can select the target system you want the group PTF to be sent to, at the left side of the
screen and select Add and then select Next.
Figure 2-27 Send PTF group wizard
The target system will be added as shown in Figure 2-28. Select Next.
Figure 2-28 Send PTF group wizard - Target system added
This will bring you to the screen as shown in Figure 2-29 on page 35, where you have the
following options when sending the group PTF:
How to replace existing PTF groups of same names on target systems:
Replace only if PTF groups being copied have higher levels
Never replace
Always replace
Which related PTF groups to send from the source system
None
Latest level installed on system
34
Latest level on system
Figure 2-29 Send PTF group wizard - available options
You will now get to the screen as shown in Figure 2-30 with a summary of the selected
options to be taken into account when sending the PTF group. Click Finish.
Figure 2-30 Send PTF group wizard - summary screen with selected options
The screen, as shown in Figure 2-31, will show you the progress of sending the PTF group:
copying the group PTF to an image on the local IBM i system
sending the PTF group
clean up on the local IBM i system
35
Figure 2-31 Sending PTF group progress
Send and Install PTF groups

From the Display PTF Groups screen, it is also possible to send a PTF group to a target
system or a system group and immediately afterwards install this group PTF on the target
system or system group. In order to send and install a group PTF, right-click a specific group
PTF as shown in Figure 2-32 and select Send and Install.
Figure 2-32 Send and install PTF group
The process would be exactly the same as described earlier in, Send PTF groups on
page 33, except that afterwards the PTF group would also immediately be installed on the
target system or system group.
Note: In the Send and Install PTF group Wizard there is an additional option to be
specified to either immediately install the group PTF or at the next IPL of the target system.
The result is shown in Figure 2-33 on page 36.
Figure 2-33 Send and install PTF group progress and results
36
Individual PTF navigation

Depending on its status, it is also possible to perform the following on an individual PTF level.
These are similar to the actions that can be performed on all PTFs for a specific licensed
program product, which has been discussed earlier in this chapter:
load PTF
apply PTF temporarily or permanently
remove PTF temporarily or permanently
cleanup PTF
send PTF
send and install PTF
display the properties of a PTF
Load PTF
In order to load an individual PTF for a specific licensed program product, perform the
following from the display PTF screen within IBM Navigator for i, as shown in Figure 2-34 on
page 37:
right-click on the specific PTF and click Load
on the Load PTF screen, click OK
Figure 2-34 Load individual PTF
This will start loading the individual PTF for the licensed program product.
Apply PTF
In order to apply an individual PTF for a specific licensed program product, perform the
page 38:
right-click on the specific PTF and click Apply
on the Apply PTF screen, click OK
You have the following options available:
extent of change
temporarily apply
37
permanently apply
apply requisite PTFs
yes
no
Figure 2-35 Apply individual PTF
This will temporarily apply the individual PTF for the specific licensed program product.
Remove PTF
In order to remove an individual PTF for a specific licensed program product, perform the
following from the display PTF screen within IBM Navigator for i, as shown in Figure 2-36:
right-click on the specific PTF and click Remove
on the Remove PTFs screen, click OK
You also have the possibility to specify that you want to remove dependent PTFs.
Figure 2-36 Remove individual PTF
38
On the Confirm Remove screen, click Remove to confirm the removal of the individual PTF
from the licensed program product, as shown in Figure 2-37 on page 39.
Figure 2-37 Remove individual PTF - confirm
This will temporarily remove the individual PTF from the specified licensed program product.
Clean up PTF
In order to cleanup an individual PTF for a specific licensed program product, perform the
page 39:
right-click on the specific PTF and click Clean up
on the Clean up PTFs screen, click OK
Figure 2-38 Clean up individual PTF
On the Confirm Clean up screen, click Clean up to confirm the clean up of the individual PTF
from the licensed program product, as shown in Figure 2-39.
Figure 2-39 Clean up individual PTF - confirm
This will delete the save file and the cover letter for the individual PTF for the designated
licensed program product.
39
Display PTF properties

In order to display the properties of an individual PTF, right-click on the specific PTF and click
Properties as shown in Figure 2-40.
Figure 2-40 Display PTF properties
This will bring you to the Display properties PTF screen as shown in Figure 2-41.
Figure 2-41 Display PTF properties - details
You can get the following information by clicking on the corresponding option available:
General information
PTF objects
Requisite PTFs
Superseded PTFs
Symptom strings
Exit programs
APARs fixed
Cover letter
Dependent PTFs
Preconditions
40
Send PTF
In order to send an individual PTF for a specific licensed program product to a target system
or system group, right-click on the specific PTF and click Send as shown in Figure 2-42 on
page 41.
Figure 2-42 Send individual PTF
This will bring you to the Send PTF wizard screen as shown Figure 2-19 on page 30 where
the next actions to be performed, were also discussed.
Install PTFs
It is now also possible to install an individual PTF on the system from within the IBM Navigator
for i interface: in order to do this, select Configuration and Service All Tasks Program
Temporary Fix Install PTFs as shown in Figure 2-43. On the Install PTFs screen, select
the PTF id option and click Next.
Figure 2-43 Install individual PTF
It will bring you to the Install PTFs screen, as shown in Figure 2-44 on page 42.
41
Figure 2-44 Install PTFs - PTF ID to select
You can specify a specific PTF ID to be installed. You have the following possibilities to be
installed from:
service support system
savefile
Click Next will bring you to the screen shown in Figure 2-45 on page 43.
42
Figure 2-45 Install PTFs by PTF ID
Click Finish to start the PTF installation process.
Send and install PTF

In order to send and install an individual PTF for a specific licensed program product to a
target system or system group, right-click on the specific PTF and click Send and install as
shown in Figure 2-46.
Figure 2-46 Send and install PTF
This will bring you to the Send And Install PTFs wizard screen as discussed earlier in Send
PTFs on page 29, where the next actions to be performed, were also discussed.
Note: In the Send and Install PTF Wizard there is an additional option to be specified to
either immediately install the group PTF or at the next IPL of the target system.
43
Send and install PTFs and PTF groups to multiple systems

Similar to what we discussed for send and install PTFs in , Send and install PTFs on
page 32, there is also the possibility within IBM Navigator for i:
to send and install PTFs to multiple systems
to send and install PTF groups to multiple systems
Compare PTFs and PTF Groups on different systems

Within IBM Navigator for i, it is now possible to compare PTFs and PTF groups on different
systems. From the Display PTFs screen, on the Action menu, select Compare and Update
as shown in Figure 2-47 on page 44.
Figure 2-47 Compare and update PTFs
This will bring you to the Compare and Update Wizard, as shown in Figure 2-48, that can
compare the PTF and PTF group levels of a source system to the levels of one or more target
systems. Click Next.
44
Figure 2-48 Compare and update wizard
You now get towards the screen shown in Figure 2-49 on page 45
Figure 2-49 Compare and update wizard - available options
Note: You can click Cancel any time to cancel the compare and update.
You have the following options available:
Update the target system directly from the source system without viewing the compare
results
View compare results to see the difference for PTFs or PTF Groups for each target system
View compare results only
Send missing PTFs only
Send and install missing PTFs
What types of PTFs or PTF groups would you like the compare to find:
45
Missing
Extra
Click Next now.
You will get now to the screen as shown in Figure 2-50 on page 46 where you can add the
target system you want to compare the PTFs or PTF groups with.
Figure 2-50 Compare and update wizard - add target system
Click Next.
On the Compare and Update screen, as shown in Figure 2-51 on page 47, you can choose
between the following options:
all products: PTFs for all installed licensed programs will be compared
selected products: PTFs for the selected licensed programs will be compared
46
Figure 2-51 Compare and update wizard - products to compare
Now click Next.

You get to the following screen, as shown in Figure 2-52 on page 48, where you get the
comparison result with missing PTFs and extra PTFs.
47
Figure 2-52 Compare and update wizard - missing / extra PTFs result
When you click on the specified Target Systems and Groups link, youll get to the screen as
Figure 2-53 Compare and update wizard - results for target system
48
This contains the comparison results between the source system and the specified target
system (or system group):
missing PTFs: PTFs that are on the source system and not on the target system (or
system group)
extra PTFs: PTFs that are on the target system (or system group) and not on the source
system
Note: Be aware that the Extra PTFs or PTF Groups are for display only and cannot be sent
and installed to the target system or system group.
Multi-system PTF comparison

With IBM Navigator for i in IBM i 7.2, it is also possible to compare and update PTFs between
one source system and multiple targets where the targets can be systems or system groups.
2.1.8 Monitors
With IBM i 7.2, we have added the ability to define, run and respond to system and message
monitors within IBM Navigator for i.
Message monitor
With IBM i 7.2 Navigator for i, you are able to create a message monitor to monitor any
message queue on the system.
For each message queue, you can specify two separate and independent message sets to
monitor. For each message set, you can specify the following:
threshold that will trigger an event
an operating system command that will run as soon as the event is triggered
Message monitors can be used to monitor for when an application completes
successfully/unsuccessfully or monitor for other specific messages that are critical to your
business needs.
As a system administrator, you need to be aware of inquiry messages as they occur across
your system.
We now describe the steps to set up a message monitor to display any inquiry messages in
your message queue that occur on your system by doing the following as shown in
Figure 2-54 on page 50:
In IBM Navigator for i, select Monitors Message Monitors.
From the Actions menu, select Create New Message Monitor.
49
Figure 2-54 Create new message monitor
This will bring you to the screen as shown in Figure 2-55.
Figure 2-55 Create message monitor - General page
On the General page, enter a name and description for this monitor. Click Next.
This will bring you to the screen as shown in Figure 2-56.
50
Figure 2-56 Create message monitor - Message Queue
On the Message Queue page, enter the following values:

For Message Queue to Monitor, specify QSYSOPR
For Library, specify QSYS
Click Next.
You now get to the Create New Message Monitor screen, as shown in Figure 2-57.
51
Figure 2-57 Create message monitor - Message set 1
On the Message Set page, perform the following: on the Message Set 1 tab, click Add.
You get to the screen as shown in Figure 2-58.
Figure 2-58 Create message monitor - Add A Message Set
On the Add A Message Set page, perform the following:

Select Add a user defined set of messages
For Message Type, select Inquiry
Click OK
You get to the screen, as shown in Figure 2-59 on page 53.
52
Figure 2-59 Create message monitor -
You can now perform the following:

Select Set the message trigger and reset.
Specify 1 for Trigger at the following message count.
Click Next.
This will get you to the screen as shown in Figure 2-60 on page 54:
53
Figure 2-60 Set Monitor Actions Information
Click Next will get you to the view the monitor summary page as shown in.
54
Figure 2-61 Create New Message Monitor - Summary
Click Finish to save the monitor. From the list of message monitors, as shown in Figure 2-62
on page 55, right-click the new monitor and select Start.
Figure 2-62 Message Monitor - Start
55
The new message monitor displays any inquiry messages sent to QSYSOPR.
Note: This monitor responds to only inquiry messages sent to QSYSOPR. However, you
can include two different sets of messages in a single monitor, and you can have several
message monitors that run at the same time. Message monitors can also carry out IBM i
commands when specified messages are received.
System monitor
To effectively monitor system performance, you have to decide which aspects of system
performance you want to monitor. Performance metrics are performance measurements to
help you pinpoint different aspects of the system performance. When configuring a system
monitor with IBM i 7.2 in IBM Navigator for i, you can use any metric, a group of metrics, or all
the metrics from Table 2-1 below.
Table 2-1 System Monitor Metrics
56
Metric groups
Metric description
CPU Utilization
The percentage of available processing unit time that is consumed by jobs

on your system. Choose from the following types of CPU Utilization metrics
for use in your monitors:
CPU Utilization (Average)
CPU Utilization (Interactive Jobs)
CPU Utilization (Uncapped)
CPU Utilization (SQL)
Interactive Response
Time (Average and
Maximum)
The response time that interactive jobs experience on your system.
Transaction Rate
(Interactive)
The number of transactions per second completed on your system by

interactive jobs (Job type = 'I').
Batch Logical
Database I/O
The average number of logical database input/output (I/O) operations

currently performed by batch jobs (Job type = 'B') on the system.
Disk Arm Utilization

(Average and
Maximum)
The disk unit busy percent.
Disk Arm Utilization for

System / User /
Independent ASP
(Average and
Maximum)
The disk unit busy percent for all disks in the system ASP, user ASPs, or
independent ASPs.
Disk Storage
Utilization (Average
and Maximum)
The percentage of disk storage that is full on your system during the time
you collect the data.
Disk Storage
Utilization for System /
User / Independent
ASP (Average and
Maximum)
The percentage of disk storage that is full in the system ASP, user ASPs,
or independent ASPs during the time you collect the data.
Communications Line
Utilization (Average
and Maximum)
The amount of data that was actually sent and received on all your system
communication lines.
Metric groups
Metric description
LAN Utilization
(Maximum and
Average)
The amount of data that was actually sent and received on all your local
area network (LAN) communication lines.
Machine Pool Faults
The number of faults per second occurring in the machine pool on the
system.
User Pool Faults

(Maximum and
Average)
The number of faults per second per pool.
Temporary Storage
Used
The total amount of temporary storage (megabytes) in use within the

system. This includes both system and user temporary storage.
Spool File Creation

Rate
The number of spool files that are created per second.
Shared Processor
Pool Utilization (Virtual
and Physical)
The amount of CPU consumed in the shared pool by all partitions that are
using the pool relative to the CPU available within the pool.
The system monitor within IBM Navigator for i uses data from Collection Services to track the
elements of system performance of specific interest to you.
Within IBM Navigator for i, you have the following System Monitor related functions available:
Monitors:
Create a new system monitor or create one based on an existing monitor
Change the configuration of a system monitor
Delete a system monitor
Start/stop a system monitor
Thresholds and event logs:

Capture events and trigger actions when a threshold is reached
List event log of a selected system monitor
List event log of all system monitors
Display properties of an event log
Delete an event log
Investigate monitor data using Performance Data Investigator (PDI)
Creating a new system monitor

We will now describe the different steps to create a system monitor as shown in Figure 2-63:
In IBM Navigator for i, select Monitors System Monitors.
From the Actions menu, select Create New System Monitor.
57
Figure 2-63 Create New System Monitor
You will get to the Create New System Monitor screen as shown in Figure 2-64 on page 58.
Figure 2-64 Create System Monitor - General Page
On the General page, enter a name and description for this monitor. Click Next.
This will bring you to the screen as shown in Figure 2-65 on page 58.
Figure 2-65 Create New System Monitor - Add Metric
58
You can select the Disk Storage Utilization (Average) Metric and select Add.
Now you can click on the Disk Storage Utilization (Average) Metric in the right pane in order to
configure it as shown in the Configure Metric screen in Figure 2-66 on page 59.
Figure 2-66 Create New System Monitor - Configure Metric
You can configure the following for the selected metric name on the Configure Metric screen:
collection interval
treshold 1
treshold 2
Note: You need to enable the treshold(s) by selecting Enable Treshold for the
treshold(s)
Threshold
This is a setting for a metric that is being collected by a monitor with the following details:
It allows you to specify actions to be taken when:
A specified value (called the trigger value) is reached
A second value (called the reset value) is reached
An event is added to the Event Log whenever the trigger value or the reset value is
reached.
Set up to two thresholds for each metric that the monitor is collecting.
Trigger: considered bad (usually high but can be low)
59
Reset: considered good (opposite of trigger)

When a threshold is reached, IBM Navigator for i captures the event and executes actions
Select OK will bring you back to the screen as shown before in Figure 2-65 on page 58.
Now select Next.
This will bring you to the Summary Screen as shown in Figure 2-67 on page 60.
Figure 2-67 Create New System Monitor - Summary Screen
Now click Finish.

This will bring you to the System Monitors screen as shown in Figure 2-68 on page 60.
Figure 2-68 System Monitors - Actions menu
From the Actions menu, you have the following functions available:
Properties: Display the attributes of this monitor.
Investigate Monitor Data: Use PDI to graph the monitored metrics.
Event Log: Show the Event Log List for this monitor.
Start: Start this system monitor.
60
Stop: Stop this system monitor.

New Based On: Create a new system monitor based on this system monitor.
Delete: Delete this system monitor.
Note: With the Fall 2014 PTF (TR1), we will have the following:
Support for monitor auto-restart.
Support for multiple users access monitors in the same machine concurrently.
Support to modify an active monitor.
<< the above text in the note box was added on request of Lora Powell (253-4191): please
double-check with her later on if this info is correct - closer to Fall 2014 PTF availability>>
System Monitor Graphs in PDI

From within the IBM System Monitor screen, you can go to the System Monitor Graphs
directly in PDI, as shown in Figure 2-69 on page 61:
Figure 2-69 System monitor
On the System Monitor screen, you can do the following:

Right-click the System Monitor
Select Disk Storage Utilization (Average) as the metric you specified in Figure 2-65 on
page 58.
This will bring you straight to the PDI interface.
61
Note: The refresh button is visible when displaying the currently active collected monitor
data and the current chart will be refreshed with the latest monitored data from the active
real time collection.
New PDI package

With IBM i 7.2, there is a new PDI package available as shown in Figure 2-70 on page 62:
Figure 2-70 Investigate Data
This provides 35 lightweight perspectives for System Monitor metrics.

Batch Logical Database I/O Rate
Communications Line Utilization (Average)
Communications Line Utilization (Maximum)
CPU Utilization (Average)
CPU Utilization (Interactive Jobs)
CPU Utilization (SQL)
CPU Utilization (Uncapped)
Disk Arm Utilization (Average)
Disk Arm Utilization (Maximum)
Disk Arm Utilization for Independent ASP (Average)
Disk Arm Utilization for Independent ASP (Maximum)
Disk Arm Utilization for System ASP (Average)
62
Disk Arm Utilization for System ASP (Maximum)

Disk Arm Utilization for User ASP (Average)
Disk Arm Utilization for User ASP (Maximum)
Disk Storage Utilization (Average)
Disk Storage Utilization (Maximum)
Disk Storage Utilization for Independent ASP (Average)
Disk Storage Utilization for Independent ASP (Maximum)
Disk Storage Utilization for System ASP (Average)
Disk Storage Utilization for System ASP (Maximum)
Disk Storage Utilization for User ASP (Average)
Disk Storage Utilization for User ASP (Maximum)
Interactive Response Time (Average)
Interactive Response Time (Maximum)
LAN Utilization (Average)
LAN Utilization (Maximum)
Machine Pool Faults Rate
Shared Processor Pool Utilization (Physical)
Shared Processor Pool Utilization (Virtual)
Spool File Creation Rate
Temporary Storage Utilization
Transaction Rate (Interactive)
User Pool Faults Rate (Average)
User Pool Faults Rate (Maximum)
Collection Services System Monitor Support

With IBM i 7.2, IBM i Collection Services is used to collect system monitor data 24x7.
System Monitor metrics are derived:
they do not exist in raw collected performance data.
they are a function of selection, grouping, and other calculations
rates
percents
maximums
IBM Navigator for i System Monitor metrics are now produced by Collection Services and
exported to database files (they are no longer stored in a private *MGTCOL like Management
Central).
New files contain metrics defined for system monitoring along with othersupporting data.
Includes metrics supported by Management Central and more.
Existing Collection Services files can be used for drill down and detailed data.
Data is easily accessible by the monitoring function and visualization tools (PDI).
63
Data is also easily accessible to any other consumers and can be used for more in depth
analysis as necessary.
When system monitor data collection is enabled, monitor metrics are exported by Collection
Services into a second Collection Services File Based Collection for the active collection.
A second batch job (CRTPFRDTA2) is submitted to produce the System Monitor collection.
System Monitor file collection names will be based on the *MGTCOL name except that it will
begin with R rather than with Q.
System Monitor file collections will only contain database files related to the categories
selected for system monitoring.
The database file interval used by CRTPFRDTA2 is always 15 seconds. Data will be present
based on the interval each category was collected at.
System Monitor file collections have a separate retention (expiration) period than standard
Collection Services file collections.
Existing Performance Data Investigator perspectives can be used with this collection,
provided that all required data is present.
We have the following Collection Services System Monitor files:
QAPMSMCMN (*CMNBASE): Line and LAN metrics
Breakdown: Lines and LANs
Still have ability to exclude unwanted lines
Line count, avg / max utilization, avg kilobits received and sent, line with highest
utilization
QAPMSMDSK (*DISK ): Disk metrics
Breakdown: all units, system ASP, user ASPs, IASPs
Number of entries in data, avg / max busy & device name, avg & max capacity used &
device name
Total capacity available and used
For both reads and writes: Ops, avg response & service time, max response time, max
device name
QAPMSMJMI (*JOBMI ): Job metrics dependent on the MI
Breakdown: Interactive and Batch
Job count, total and max unscaled CPU consumed and percent and job, Interactive
transaction rate
QAPMSMJOS (*JOBOS): Job metrics dependent on the OS
Job count, Batch LIO rate, avg/max interactive response time & job
Spool file creation rate, count and name of job creating most
QAPMSMPOL (*POOL): Pool metrics
Machine pool fault rate, count of user pools, avg / max user pool fault rate and pool
QAPMSMSYS (*SYSLVL): System metrics
Scaled and unscaled: Configured, uncapped, and virtual CPU percent
Speed percent, virtual & physical shared pool percent
64
Temp storage used and percent, unscaled SQL CPU percent

The same system monitor metric data can also be generated without starting a System
Monitor within IBM Navigator for i.
System monitor files (QAPMSM*) can be generated for your Collection Services collection by
specifying:
CRTPFRSUM(*ALL) on the Configure Performance Collection (CFGPFRCOL) command
CRTPFRSUM(*ALL or *SYSMON) on the Create Performance Data (CRTPFRDTA)
command when running manually.
System monitor data collection can also be enabled via the Configure Performance Collection
(CFGPFRCOL) command by specifying ENBSYSMON(*YES).
This will not actually start any monitors.
Specify the categories you want collected more frequently on the SYSMONCGY parameter of
Configure Performance Collection (CFGPFRCOL).
This will start the CRTPFRDTA2 job that creates the second database file collection starting
with an R.
Note: When monitors override the settings of Collection Services to gather performance
data more frequently, the settings are not undone when a monitor stops. You must
manually change the Collection Services settings if you no longer want to collect the data
as often
We can enable system monitor data collection from the Performance tasks within IBM
Navigator for i as shown in Figure 2-71.
65
Figure 2-71 Configure Collection Service
Click Performance All Tasks Collectors Collection Services Configure

Collection Services.
You will get to the Configure Collection Services screen as shown in Figure 2-72 on
page 67.
66
Figure 2-72 Configure Collection Services
On the General page, you can select the Enable system monitoring in the System options.
You can also configure the Data Retention as shown in Figure 2-73 on page 67.
Figure 2-73 Data Retention configuration
It is also possible to configure the System Monitor Categories as shown in Figure 2-74 on
page 68.
67
Figure 2-74 System Monitor Categories - customization
Differences with Management Central Monitors

IBM Navigator for i system monitors and Management Central monitors are two separate
functions.
Management Central monitors (using the IBM i Navigator client) still work and run against a
7.2 system.
Both system monitor functions have dependencies on Collection Services to control what
data is collected and at what interval.
Management Central uses application override support which can allow any of the
Collection Services data categories to be collected more frequently than what is specified
for the configured collection profile.
IBM Navigator for i system monitors use the new system monitoring settings specified on
the Configure Performance Collection (CFGPFRCOL) command or in the Configure
Collection Services GUI in IBM Navigator for i.
Management Central gets and stores the monitor data differently than the IBM Navigator for i
system monitoring support.
Management Central stores the monitor data in private *MGTCOL objects.
IBM Navigator for i system monitors use the monitor data exported by Collection Services
into DB2 files (file name starting with QAPMSM*).
Note: IBM Navigator for i system monitor functions will not work when a 6.1 or 7.1 target
system is specified. The underlying Collection Services support is only available in 7.2.
2.1.9 Performance
This section will explain the enhancements in IBM Navigator for i related to the Performance
tasks.
IBM Navigator for i Performance Interface

The performance interface includes Performance Data Investigator (PDI), Collection
Manager, and web-based GUI interfaces for Collection Services, Job Watcher, and Disk
Watcher. New functions for Batch Model, System Monitor, and Performance Reports are
described here.
68
Performance Data Reports

A Performance Data Report can be generated for a set of PDI perspectives. You can view the
report in IBM Navigator for i or generate a PDF or zip file. By using Performance Data
Reports, you can efficiently export multiple charts or tables for a collection at one time.
In Performance Data Reports, users are allowed to perform several operations, such as:
add definition
delete definition
add new definitions using existing definitions
and view report definition.
Figure 2-75 Performance Data Reports task
Figure 2-76 on page 70 shows the example of Report Data Definition.
69
Figure 2-76 Report Data Definition example
Drill down information

In Performance Data Investigator, users are allowed to view additional information shown in
the blue title bar of the PDI, called as drill down information. To view the drill down
information, users need to select the intervals anddo the drill down. Additional information in
the blue title bar for the drilled-down chart shows what parameters are used for that specific
drill down.
Figure 2-77 shows the drill down information when viewing the when selecting data in
Performance Data Investigator.
Figure 2-77 Drill down information in Performance Data Investigator title bar
System Information panel

On PDI perspectives display panel, the Show System Information view option provides more
detailed information for the system that the displayed collection came from such as processor,
memory, and partition specifications.
Figure 2-78 on page 71 shows the System Information panel in PDI.
70
Figure 2-78 System Information view in PDI
Option to show SQL error messages

The Show SQL error messages option on the Options panel in PDI provides specific error
information on SQL errors when the Modify SQL function is used.
Health Indicators
Health Indicators perspective for Database Health is added to the Health Indicators package.
For more information related to the Healh Indicators, see the Introduction to Health Indicators
using Performance Data Investigator Redpaper publications REDP-5150.
Batch Model
IBM Navigator for i in 7.2 release provides the modelling tool for system utilization and run
times of IBM i batch workloads. It is really helpful for analyzing and predict batch job
performance on the IBM i and help the users to know what improvements that they can do to
meet a certain batch window target.
Below are the functions of Batch Model in IBM Navigator for i:
Helps users to optimize workloads by locating times during the batch window when more
efficient job scheduling can improve total system throughput
Models workload increments
Predicts the changes in throughput that will result from hardware upgrades (processor or
disk)
Predicts run times for individual workloads and the overall batch window
Models batch workloads that are CPU or disk intensive
Note: The Batch Model functions and content package require the installation of IBM
Performance Tools for i (5770-PT1) Option 1 - Manager Feature.
71
To open the Batch Model function in IBM Navigator for i, click Performance All Tasks
Sizing Batch Model. Figure 2-79 on page 72 shows the entire menu of Batch Model.
Figure 2-79 Batch Model menu in IBM Navigator for i
Note: You can also view any batch model collections in the main table under Manage
Collections. It is also possible to use the Create Batch Model function from the Action
menu under Manage Collections when selecting a valid CS collection.
Batch Model collection is created based on existing performance data collected by Collection
Services. During the process of creating a batch model, the measured data is analyzed and a
model is built over the measured data. To create a new batch model, click Performance
All Tasks Sizing Batch Model Create Batch Model. A Create Batch Model page
will appear as ashown in Figure 2-80 on page 73. Specify the collection name and the library
where the performance collection data located and click OK.
72
Figure 2-80 Create Batch Model page in IBM Navigator for i
Note: The Create Batch Model action submits a batch job to create the model. It can
sometimes be a long running operation. The creation is done when the status of Batch
Model collection is in Complete state.
To check the status of batch model creation, click Performance All Tasks Sizing
Batch Model Batch Models. Once batch model creation finishes, it will show Complete
status shown in Figure 2-81.
Figure 2-81 Completed batch model creation
Batch Model provides the facility to change the calibration of batch model measured data if it
was modeled incorrectly by the system. To do this, select Performance All Tasks
Sizing Batch Model Change Model Calibration. Specify the batch model name to be
changed and click OK. Users are allowed to change the storage and workload for batch
model calibration as shown in Figure 2-82 on page 74.
73
Figure 2-82 Change Batch Model Calibration page in Batch Model
Note: After changing the calibration of a batch model, users are required to perform
Calibrate Batch Model so that the system can re-create the model after calibration
changes. To calibrate the batch model, click Performance All Tasks Sizing
Batch Model Calibrate Batch Model. Similar to creating a batch model, calibrating a
batch model will submit a batch job to re-create the model and can be a long running
operation.
Batch Model also enables the user to change the batch model to model various what if
scenario. Users can change a batch model to the following scenarios:
Overall system workload growth

Processor Upgrade
Disk Upgrade
Changes to individual workloads
In order to specify the above what if changes, click Performance All Tasks Sizing
Batch Model Batch Models then right click the batch model result and select Change
Model. Specify the changes to the batch model and click OK to apply the changes.
74
Figure 2-83 Change Batch Model page in Batch Model
Users can start investigating the completed batch model by right click the batch model and
click Investigate Results.
75
Figure 2-84 Starting batch model investigation
Figure 2-85 shows the investigation result of a batch model. The upper diagram shows the
Measured Workload Timeline Overview, which describes the measured performance data
collected in the Collection Services. The lower diagram shows the Modeled Workload
Timeline Overview, which describes the condition of performance modeled with the specified
scenario. This diagram is based on Performance Data Investigator (PDI), so that users can
easily explore these diagrams and see the detail of the modeled performance.
Figure 2-85 Batch Model investigation result
For more information about how to use Batch Model in detail, see the IBM i 7.2
developerWorks at:
76
https://www.ibm.com/developerworks/ibmi/library/i-how-to-use-the-batch-model-perfo
rmance-tool/
For more information about Batch Model, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahx/rzahxwebnavbatchm
odel.htm?lang=en
Performance Perspectives
IBM Navigator for i in 7.2 provides several new perspectives in displaying performance data
through Performance Data Investigator (PDI) as below:
1. Storage Allocation/Deallocation
In IBM i 7.2, users can display the storage allocation and deallocation from PDI. To view
this, click Performance Investigate Data in the right hand navigation menu. Select
Collection Services Storage Allocation as shown in Figure 2-86 on page 77.
Figure 2-86 Storage Allocation Overview in PDI
Allocation/Deallocation perspective allows users to view below functions:

Storage Allocation/ Deallocation Overview
This chart shows allocation and deallocation of the temporary and permanent storage
for all contributors over time for the selected collections. Use this chart to select a time
frame for further detailed investigation.
Figure 2-87 on page 78 shows the Storage Allocation/Deallocation Overview.
77
Figure 2-87 Storage Allocation/Deallocation Overview Perspective
Storage Allocation/ Deallocation by Thread or Task

This chart shows allocation and deallocation of the temporary and permanent storage,
net frames requested by thread or task. Use this chart to select a thread or task for
viewing its storage statistics over time.
Figure 2-88 on page 79 shows the Storage Allocation/Deallocation by thread or task.
78
Figure 2-88 Storage Allocation/Deallocation by thread or task
2. Memory
79
IBM Navigator for i 7.2 provides the capability of viewing system performance from
memory point of view through Performance Data Investigator (PDI). To view the memory
perspective, click Performance Investigate Data in the navigation menu. Select
Collection Services Memory as shown in Figure 2-89.
Figure 2-89 Memory Perspective in Performance Data Investigator
Memory Perspective in PDI allows you to view several memory performance data as
below:
Memory Pool Sizes and Fault Rates
This chart shows the memory pool sizes and page fault rates for all memory pools on
the system over time for the selected collection or collections. Use this chart to select a
specific memory pool for further detailed investigation.
Figure 2-90 on page 81 shows the example of viewing memory pool size and fault
rates over time from a system.
80
Figure 2-90 Memory Pool Sizes and Fault Rates in Performance Data Investigator
Memory Pool Activity Levels

This chart shows the average memory activity levels and the number of transitions
from active or wait state to ineligible state per second for all memory pools on the
system over time for the selected collection or collections. Use this chart to select a
specific memory pool for further detailed investigation.
Figure 2-91 on page 82 shows the example of viewing memory pool activity level over
time from a system.
81
Figure 2-91 Memory Pool Activity Levels in Performance Data Investigator
DB and Non-DB Page Fault

Charts that show the database and non-database page fault rates for all memory pools
on the system over time for the selected collection or collections. Use this chart to
select a specific memory pool for further detailed investigation.
Figure 2-92 on page 83 shows the example of viewing DB and Non-DB page fault rate
over time in a system.
82
Figure 2-92 DB and Non-DB Page Faults Overview in Performance Data Investigator
3. Java
IBM Navigator for i 7.2 provides the capability of viewing memory consumed by IBM
Technology for Java through Java Perspective in Performance Data Investigator (PDI).
This enables users to monitor and investigate the performance of their Java application
over time. To view the memory perspective, click Performance Investigate Data in the
navigation menu. Select Collection Services Java as shown in Figure 2-93 on
page 84.
83
Figure 2-93 Java perspective menu in Performance Data Investigator
Java perspectives allows you to view the below charts:

IBM Technology for Java Memory Overview
This chart shows garbage collection information including heap sizes and other
general information related to JVM memory. Figure 2-94 on page 85 shows the
example of memory graph consumed by Java over time.
84
Figure 2-94 Java memory graph in Performance Data Investigator
IBM Technology for Java Memory by Job

This chart shows average and peak garbage collection information including heap
sizes and other general information related to JVM memory by job. Figure 2-95 on
page 86 shows the Java memory consumption per job.
85
Figure 2-95 Java Memory by job in Performance Data Investigator
4. Temporary Storage
IBM Navigator for i 7.2 also provides the capability of viewing temporary storage allocation
and deallocation through Temporary Storage Perspective in Performance Data
Investigator. To view the the temporary storage perspective, click Performance
Investigate Data in the navigation menu. Select Collection Services Storage
Allocation Temporary Storage as shown in Figure 2-96 on page 87.
86
Figure 2-96 Temporary Storage perspective in Performance Data Investigator
Temporary Storage perspectives allows you to view the below charts:

Temporary Storage Allocation Accounting
This chart shows the amount of temporary storage charged to active and ended jobs,
the amount of user temporary storage, and the amount of temporary storage used for
database and non database operations by the IBM i operating system across the
system over time for the selected collections. Use this chart to select a time frame for
further detailed investigation.
Temporary Storage Allocation/Deallocation Overview
This chart shows allocation and deallocation of the temporary storage for all
contributors over time for the selected collections. Use this chart to select a time frame
for further detailed investigation.
Temporary Storage Allocation/Deallocation by Job or Task
This chart shows allocation and deallocation of the temporary storage by job or task.
Use this chart to select a job or task for viewing its temporary storage statistics over
time.
Temporary Storage Allocation/Deallocation by Thread or Task
This chart shows allocation and deallocation of the temporary storage by thread or
task. Use this chart to select a thread or task for viewing its temporary storage statistics
over time.
Temporary Storage Allocation/Deallocation by Generic Job or Task
This chart shows allocation and deallocation of the temporary storage by generic job or
task. Use this chart to select a generic job or task for viewing its temporary storage
statistics over time.
Temporary Storage Allocation/Deallocation by Job User Profile
87
This chart shows allocation and deallocation of the temporary storage by job user
profile. Use this chart to select a job user profile for viewing its temporary storage
statistics over time.
Temporary Storage Allocation/Deallocation by Job Current User Profile
This chart shows allocation and deallocation of the temporary storage by job current
user profile. Use this chart to select a job current user profile for viewing its temporary
storage statistics over time.
Temporary Storage Allocation/Deallocation by Subsystem
This chart shows allocation and deallocation of the temporary storage by subsystem.
Use this chart to select a subsystem for viewing its temporary storage statistics over
time.
Temporary Storage Allocation/Deallocation by Server Type
This chart shows allocation and deallocation of the temporary storage by server type.
Use this chart to select a server type for viewing its temporary storage statistics over
time.
2.1.10 Security
In IBM i 7.2, the security wizard support has been enabled within IBM Navigator for i. Click
Security All Tasks Configure, as shown in Figure 2-97 on page 88.
Figure 2-97 Security Wizard
This will start the Security Wizard interface, as shown in Figure 2-98 on page 89.
88
Figure 2-98 Security Wizard - startup
This allows the user to do perform the following functions:

create a set of security recommendations
create reports explaining the security recommendations
optionally apply the recommendations to the system
2.1.11 Network
Enterprise Identity Mapping (EIM) support is enabled within IBM Navigator for i in IBM i 7.2.
Click Network Enterprise Identity Mapping as shown in Figure 2.1.12 on page 90.
89
Figure 2-99 Enterprise Identity Mapping
This allows administrators and application developers to solve the issue of managing multiple
user registries across the enterprise.
The EIM migration is mainly described in two parts:
the EIM configuration
the EIM domain management
EIM configuration
The EIM configuration part includes the following:
EIM configuration wizard
the configuration list
the configuration actions
The configuration wizard will guide the user in order to configure the system to participate in
an EIM domain.
EIM domain management

The Domain management part describes all objects and actions related to the EIM domain,
including the domain folder actions, the User Registries sub-folder actions, the Identifier
sub-folder actions, the User Registry object actions and the Identifier object actions.
2.1.12 Omnifind Text Search

The ability to search text from files in IFS and spooled files in output queues has been added
to IBM Navigator for i for IBM i 7.2. Select System Search will get you to the screen shown
in Figure 2-100 on page 91.
90
Figure 2-100 Omnifind text search
Note: The OmniFind product (5733-OMF) must be installed in order to be able to use this
function.
In IBM i 7.2, OmniFind supports indexing the files not only from the top level of the directories
but also from the sub-directories of the directories recursively. From IBM Navigator for i, there
is the possibility to search text from IFS and within spoolfiles without the need to understand
stored procedures.
For more OmniFind Text Search related information, please also see 8.9, OmniFind Text
Search Server for DB2 for i (5733-OMF) on page 328.
For more in-depth information about OmniFind Text Search, see the IBM i 7.2 Knowledge
Center at the following website:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzash/rzashkickoff.htm?
lang=en
2.1.13 Disk management

Within IBM Navigator for IBM i 7.2, the concurrent removal of disk units was enabled:
from an ASP.
from an IASP that is varied on.
After selecting the disk unit, the user will be asked to confirm the removal from the ASP as
shown in Figure 2-101 on page 92.
91
Figure 2-101 Concurrent removal of disk unit from ASP - confirmation
Once the removal got started, the user is able to perform the following actions as shown in
Figure 2-102 on page 92:
pause
resume
cancel
Figure 2-102 Removal of disk units from ASP - available actions
There is a possibility to pause the disk unit removal process and afterwards cancel the
running process if necessary, as shown in Figure 2-103 on page 93.
92
Figure 2-103 Cancel disk unit removal process
A Solid State Drive column has also been added to the disk units list now in order to indicate
if the disk unit is a SSD (Solid State Drive) as shown in Figure 2-104. Before the users were
not able to find the SSD information from the type and model of some disks.
Figure 2-104 Solid state disks (SSD)
Some of the user access restrictions on IBM Navigator for i were removed: this now allows
users to have a different user id and password for IBM i and within system service tools (SST)
as.
Figure 2-105 Service tools - Disk management tasks access
93
Note: Within IBM i 7.2 IBM Navigator for i, the user is able to access the disk management
tasks in the same way they do it in IBM i Navigator by using a service tools user
independent from the IBM i profile used to sign-on to the system.
If you have a matching service tools userid and IBM i userid, the signon panel will not show
up and you can access the disk management functions as usual. If that fails, a signon
panel is presented asking for the service tool userid and password.
The first time you access disk management functions, if your service tools userid and
password does not match your IBM i userid and password, the signon panel will be
displayed. Once you get access to the disk management functions, you do not need to
signon again even if you log out and log in. If your service tools userid or password is
changed or expired, when you access disk management interface, an error message will
be displayed and the user should signon again.
The following actions were added for disk pools as shown in Figure 2-106 on page 94:
start tracing
stop tracing
clear trace
start balance
These allow the user to trace the hot data on each disk unit in the specific disk pool and
balance them in the disk pool by different balance types.
Figure 2-106 Disk pool menu
The rebuild disk unit data action was added for disk units: this allows users to rebuild data on
a failed disk unit within a parity set.
94
Figure 2-107 Rebuild disk unit data - failed disk within RAID protected set
The following options are available for the user as shown in Figure 2-108 on page 95:
stop allocating data on specific disk units.
resume allocating data on specific disk units.
Figure 2-108 Stop and resume allocating data to disk units
2.1.14 Partition management

Within IBM Navigator for i, you can now perform the following partition management tasks:
Create partition
Work with partitions
95
Create partition
Within IBM Navigator for i in IBM i 7.2, the user can create a partition, as shown in
Figure 2-109, by clicking Configuration and Service Create partition.
Figure 2-109 Create Partition
This will start the Create Partition Wizard interface where you can define the partition
properties as shown in Figure 2-110.
96
Figure 2-110 Create Partition Wizard
You will have to define the following setup parameters for the partition to be created:
General
partition ID
partition name
partition type: IBM i or Linux
Memory: specify the memory to be assigned to the partition.
The minimum allowed for a partition to IPL successfully is 128 MB. The maximum allowed
is the current available memory. Partitions must have memory assigned in multiples of the
memory region size.
Processors: specify the desired number of processors and the processing mode
(dedicated or shared processor pool).
Ethernet: configure the virtual ethernet setup
Storage: select the virtual disk to be assigned to the partition.
Note: VPM does not provide the function assigning the storage resource to the new
partition such as virtual disk, optical device and physical disks. The users have to use CL
commands to create NWSD (Network Server Description) for the new partition and link the
storage device to the new partition by using ADDNWSSTGL (Add Server Storage Link)
Work with partitions

You also have the possibility to work with the existing partitions within IBM Navigator for i, as
shown in Figure 2-111 on page 98.
97
Figure 2-111 Work with partitions
You have the following options available for the existing partitions on the system:
delete
power on
power off
vary off NWSDs
vary on NWSDs
Properties
For more information about the partion management interface on IBM i 7.2 within IBM
Navigator for i, see the following URL:
echnology%20Updates/page/IBM%20Navigator%20for%20i%20-%20V7R2%20Changes
For more information about VPM (Virtual Partition Manager), you can have a look at the
following documentation material:
Creating IBM i Client Partitions Using Virtual Partition Manager, REDP-4806
For more information about virtualization on IBM i 7.2, refer to 3.4.1, Virtual Partition
Manager adds GUI to IBM Navigator for i on page 176.
2.1.15 Support added for additional system values

A limited number of system values were missing from the IBM Navigator for i interface. With
IBM i 7.2, those missing system values have now been added, including those dealing with
network attributes. Select Configuration And Service System values, as shown in
98
Figure 2-112 IBM Navigator for i - System values
Right-click the Network category and select Properties, brings you to the Network Attributes
System Values screen, as shown in Figure 2-113 on page 99.
Figure 2-113 System values - Network attributes
99
2.1.16 Integrated Server Administration

We have the following enhancements related to the integrated server support within IBM i 7.2:
Resource allocation priority
Disk units with 4K sectors
SSD (solid state drive) can be selected
Restricted/allowed device resources
Storage pool size limit
Windows Server 2012 support
Windows Server 2003 support removed
Create quorum disks support removed
No support of IXS and IXA hardware
Integrated server cloning

Resource allocation priority is used to let the user define the cost on the hosting IBM i
resources when formatting the storage spaces linked to the client servers as shown in
Figure 2-114.
Create NWS Storage Space (CRTNWSSTG)
Type choices, press Enter.
Network server storage
Size . . . . . . . . .
From storage space . .
Format . . . . . . . .
Auxiliary storage pool
ASP device . . . . . .
Text 'description' . .
space
. . .
. . .
. . .
ID .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
NWSSTG
NWSSIZE
FROMNWSSTG
FORMAT
ASP
ASPDEV
TEXT
*CALC
*NONE
*NTFS
1
*BLANK
Additional Parameters
Data offset . . . . . . . .
Sector size in bytes . . . .
Preferred storage unit . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
F5=Refresh
OFFSET
SCTSIZ
UNIT
RSCALCPTY
F12=Cancel
*FORMAT
512
*ANY
9
Bottom
F13=How to use this display
Figure 2-114 Resource allocation prioriity
In IBM i 7.2, on the CRTNWSSTG (Create NWS Storage Space), you have the resource
allocation priority parameter that depicts in a range from 1to 9 how much resource should be
given to the process that zeros out the disk during a format request:
A lower value requires more time to complete a format but consumes fewer resources
from the host system.
100
A higher value completes the format faster, but consumes more resources on the host
system.
If you want to perform this action within IBM Navigator for i, select Integrated Server
Administration Servers New Virtual Storage as shown in Figure 2-115:
Figure 2-115 Resource allocation priority parameter
You can change the Resource allocation priority parameter to a value between 1 and 9:
1 - the format completes faster, but consumes more resources on the host system
9 - the format completes slower, but consumes less resources on the host system
4K disk units sector support

Disk units with 4K sectors are now supported when creating a virtual disk as shown in
101

Size . . . . . . . . .
Format . . . . . . . .
space
. . .
. . .
. . .
ID .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
NWSSTG
NWSSIZE
FROMNWSSTG
FORMAT
ASP
ASPDEV
TEXT
*CALC
*NONE
*NTFS
1
*BLANK
Data offset . . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
F5=Refresh
OFFSET
SCTSIZ
UNIT
RSCALCPTY
F12=Cancel
*FORMAT
512
*ANY
9
Bottom
Figure 2-116 4K sector size support
We have the following options on the CRTNWSSTG(Create NWS Storage Space) command for
the sector size in bytes parameter:
512: configure this storage for 512 bytes in each sector.
4096: Configure this storage for 4096 bytes in each sector.
Note: A sector size of 4096 cannot be specified when FORMAT(*FAT) or
FORMAT(*FAT32) is specified,.
Administration Servers New Virtual Storage as shown in Figure 2-117 on page 103:
102
Figure 2-117 Sector size in bytes parameter
You can select the Sector size in bytes:

512 bytes per sector
4096 bytes per sector
SSD (solid state drive) support

In IBM i 7.2 , a SSD (solid state drive) disk unit type can be selected as preference when
creating network server storage space as shown in Figure 2-118.
103

Size . . . . . . . . .
Format . . . . . . . .
space
. . .
. . .
. . .
ID .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
NWSSTG
NWSSIZE
FROMNWSSTG
FORMAT
ASP
ASPDEV
TEXT
*CALC
*NONE
*NTFS
1
*BLANK
Data offset . . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
F5=Refresh
OFFSET
SCTSIZ
UNIT
RSCALCPTY
F12=Cancel
*FORMAT
512
SSD
9
Bottom
Figure 2-118 SSD support added
We have the following options on the CRTNWSSTG(Create NWS Storage Space) command for
the preferred storage unit parameter:
SSD: Solid-state drive storage media is preferred. Storage should be allocated from
solid-state drive storage media if available.
*ANY: No storage media is preferred. Storage will be allocated from any available storage
media.
104
Figure 2-119 Preferred storage unit parameter
You can now specify the Preferred storage unit parameter:

ANY: storage will be allocated from any available storage media
SSD: storage should be allocated from solid-state drive storage media if available
Restricted/allowed resources
With IBM i 7.2, you can select either restricted devices to restrict access or allowed device
resources to allow access for tape and optical device resource names, as shown in
Figure 2-120.
105
Create Network Server Desc (CRTNWSD)

Virtual Ethernet path:
VRTETHPTH
Port number . . . . . . . . .
Network server host adapter .
IP security rules:
Remote interface 1 rule . . .
+ for more values
Allowed device resources . . . . ALWDEVRSC
+ for more values
Restricted device resources . . RSTDDEVRSC
+ for more values
Network server configuration:
NWSCFG
Remote system name . . . . . .
Connection security name . . .
F3=Exit F4=Prompt F5=Refresh F12=Cancel
F24=More keys
Messages pending on other displays.
*DFTSTGPTH
*DFTSECRULE
*DFTSECRULE
*DFTSECRULE
*DFTSECRULE
*UNRSTD
*NONE
*DFT
*DFT
More...
Figure 2-120 Allowed/restricted tape or optical device resources
You have the following possible values for the ALWDEVRSC parameter:
*UNRSTD
*ALLTAPE
*ALLOPT
You have the following possible values for the RSTDEVRSC parameter:
*NONE
*ALL
*ALLTAPE
*ALLOPT
Note: The ALWDEVRSC parameter is mutually exclusive with the RSTDDEVRSC
parameter: if a value other than *UNRSTD is specified, *NONE must be specified on the
RSTDDEVRSC parameter.
Within IBM Navigator for i, select Integrated Server Administration Servers Your
server Properties as shown in Figure 2-121 on page 107
106
Figure 2-121 Integrated server administration - Server Properties
You can now select System tab Advanced IBM i Devices where you can either
Restrict access or Allow access for the tape devices and the optical devices as shown in
Figure 2-122.
Figure 2-122 Allow access and Restrict access fro devices

107
Storage pool size limit

Within IBM i 7.2, the storage pool size limit which has been increased to use 8 byte integer, is
now supported.
Note: QWCRSSTS API ( Retrieve System Status) change is supported within IBM
Navigator for i.
Windows Server 2012 support

Added support for Windows Server 2012, including a new ReFS file system type for storage
and shared disk linking as shown in Figure 2-123.
Size . . . . . . . . .
Format . . . . . . . .
space
. . .
. . .
. . .
ID .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
NWSSTG
NWSSIZE
FROMNWSSTG
FORMAT
ASP
ASPDEV
TEXT
*CALC
*NONE
*REFS
1
*BLANK
Data offset . . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
OFFSET
SCTSIZ
UNIT
RSCALCPTY
F5=Refresh
F12=Cancel
*FORMAT
512
*ANY
9
Bottom
Figure 2-123 Windows Server 2012 support
ReFS is a new file system that got introduced with Windows 2012 as the next generation file
system after NTFS. If you install a NWSD with Windows 2012, you can create a network
server storage space which will later be formatted as ReFS in Windows.
108
Figure 2-124 New ReFS file system for Windows 2012
In the Planned file system parameter, you can select the following:
NTFS
ReFS
FAT-32
FAT
Open source
Windows Server 2003 support removed

In IBM i 7.2, support for Windows Server 2003 has been removed.
Note: No new integrated Windows Server 2003 (and R2) servers can be installed/cloned
on IBM i 7.2. Integrated Windows Server 2003 (and R2) servers that were installed on prior
IBM i releases and then migrated to IBM i 7.2 can continue to run as is, but without service
support. The suggested migration path for these servers however is to upgrade to
Windows Server 2008 or newer version.
Create quorum disks removed

In IBM i 7.2, the ability to create quorum disks has been removed.
No support of IXS and IXA Hardware

With IBM i 7.2, Integrated xSeries Server (IXS) and System x servers attached using
Integrated xSeries Adapter (IXA) are no longer supported.
Integrated server cloning

Support is added to let the user select the storage pool where virtual storage should be
created as shown in Figure 2-125 on page 110.
109

Network server storage space . .
Size . . . . . . . . . . . . . .
From storage space . . . . . . .
Format . . . . . . . . . . . . .
Auxiliary storage pool ID . . .
ASP device . . . . . . . . . . .
Text 'description' . . . . . . .
NWSSTG
NWSSIZE
FROMNWSSTG
FORMAT
ASP
ASPDEV
TEXT
TOMV
*CALC
FROMTEST
> *REFS
1
*BLANK
Data offset . . . . . . . .
F3=Exit F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
F5=Refresh
OFFSET
SCTSIZ
UNIT
RSCALCPTY
F12=Cancel
*FORMAT
512
*ANY
9
Bottom
Figure 2-125 Integrated Server Storage Space creation - Storage pool selection
You can specify where the where the storage space should be created:
Auxiliary storage pool ID: you can select an ASP id between 1 and 255
ASP device: you can specify the ASP device name in case of an Independent ASP
Administration Servers New Virtual Storage as shown in Figure 2-126:
Figure 2-126 Storage pool selection
110
Note: The Data offset parameter is used to specify how IBM i should align the disk, either
align the first logical partition or logical disk. For *ReFS, we use the default
*ALIGNLGLPTN (align first logical partition) which is the same as NTFS. The customer can
specify a different value when the disk is created.
For more information about the IBM i iSCSI-attached servers, please see the following:
IBM i iSCSI Solution guide
http://www-03.ibm.com/systems/power/software/i/integratedserver/guide/iscsi.html
IBM i 7.2 KnowledgeCenter
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahq/rzahqntspo.htm?la
ng=en
2.1.17 Database
The enhancements related to database for IBM i 7.2 within IBM Navigator for i are covered in
8.7.2, IBM Navigator for i DB2 related functionality on page 320.
2.1.18 Printers and printer output

Within IBM i 7.2, automatic and silent printing support is added. It allows users to
automatically and silently print spooled files in one output queue to client printers. It also
allows an IBM i ISV moving their business application towards a cloud environment to print
output to any printer a client may have attached to their PC.
A new task category Virtual Printers is added to the tasks listed under the Printers task
category in the navigation area as shown in Figure 2-127.
111
Figure 2-127 Virtual printer support
Note: This functionality only appears if the user is managing a system with IBM i 7.1 or
above
The functions of exporting spooled files as PDF by using the Infoprint Server
5722-IP1licensed product to an output queue, to the integrated file system or to an email have
been simplified for IBM i 7.2. Those functions were previously implemented as wizards, being
very inappropriate for actions on a spooled file. Figure 2-128 on page 113 shows that these
actions are now implemented as a single panel with as many options set to defaults as
possible.
112
Figure 2-128 Exporting spoolfiles as PDF using Infoprint Server
For more in-depth information about IBM Navigator for i on IBM i 7.2, see the developerworks
link:
echnology%20Updates/page/IBM%20Navigator%20for%20i
2.2 IBM i Access

IBM i 7.2 provides several enhancements to the IBM i Access family. These enhancements
were made to deliver robust, reliable and easy to use interfaces for accessing the IBM i. The
7.2 IBM i Access Family provides:
1. IBM i Access Client Solutions
2. IBM i Access for Web
3. IBM i Mobile Access
Features included are:
Simplicity of setup, use, and operations
Cross-platform infrastructure support
Non-windows based tools
Support for access from web-enabled mobile devices
Continuous support and maintenance
113
2.2.1 IBM i Access Client Solutions

IBM i Access Client Solutions is the newest member of the IBM i Access family. Originally
announced together with IBM i 7.1 TR 6, the IBM i Access Client Solutions has three
components:
Core offering (platform-independent)
Windows Application Package
Linux Application Package
First off, the Core offering of the product offers platform-independence through a Java based
implementation. This portion of the product does not require a platform-centric installer. In
order to use it, you can extract the content of the file you download from IBM and start using
it. The other two are platform-specific package for Windows and Linux, which inherit a subset
of functions from IBM i Access for Windows and IBM i Access for Linux, including middleware
for developing client applications.
The three components are described in Figure 2-129.
Figure 2-129 IBM i Access Client Solutions components
For more information about IBM i Access Client Solutions, see the IBM i Access product
page:
http://www-03.ibm.com/systems/power/software/i/access/solutions.html
Access Client Solutions: Core Offering (platform-independent)

The core offering is built as a Java based, platform-independent interface that runs on most
operating systems that support Java, including Linux, Apple Mac OS, Microsoft Windows,
AIX, and IBM i. This product is an easy-to-use, simple, yet powerful tool, which consolidates
most commonly used tasks for managing your IBM i systems into one simplified location.
The core offering of Access Client Solutions provides the following advantages:
Supported in multiplatform environments
Can be run from any type of media including USB sticks, CD/DVDs, and network shares.
Easy to install, deploy and update
Configuration can be stored on any media
IBM i Access Client Solutions version 1.1.3 has the following enhancements:
Ability for admin to restrict and hide features
114
Support for using a .netrc file in place of manually entering credentials when using prompt
once
Virtual Control Panel that supports both LAN and HMC consoles
Console Bar status is available for both LAN and HMC consoles from a 5250 session
5250 display emulation enhancements:
Insert paste support
Double and triple click text selection
Option to wrap on line boundary
Option to automatically scale font when resizing display
Option to enable displaying Unicode characters on screens with Unicode fields
Improved compatibility when converting macros from PCOMM
Character Backspace and Character Advance support
Support for up to 52 sessions
Data Transfer enhancements
Option to download column headings, instead of column names
Option to change line ending on download to CRLF, CR, LF
Option to upload and round decimals
Command line plug-in enhancements for: cfg, ping, download, upload, restrict, and
restrictview
Note: IBM i Access Client Solutions will connect to any supported IBM i release. Most
features also work with IBM i release 5.4 except for 5250 console and Virtual Control
Panel.
Prerequisites
Below are the minimum requirements necessary before using IBM i Access Client Solutions:
1. Java 6.0 or higher should be installed on the system which could be running any number
of OSs including Linux, Apple Mac OS, Microsoft Windows, AIX, and IBM i.
Note: To check the version of Java installed on your system, go to your systems
Command Prompt, Terminal, Shell, etc. and execute java -version command.
2. If the systems use SSL connections, the following PTFs are mandatory to be loaded and
applied prior to connecting with Access Client Solutions:
a. SI45601 for 5.4 release
b. SI45248 for 6.1 release
c. SI45610 for 7.1 release
3. For using 5250 Console or the Virtual Control Panel feature for an IBM i at release 6.1,
load and apply the following PTFs:
a. MF55543 (or its supersedes)
b. MF55549 (or its supersedes)
4. For using 5250 Console or the Virtual Control Panel feature for an IBM i at release 6.1 with
machine code 6.1.1, load and apply the following PTFs:
115

5. For using 5250 Console or the Virtual Control Panel feature for an IBM i at release 7.1,
load and apply the following PTFs:
Note: There are no prerequisite PTFs for connecting IBM i Access Client Solutions to IBM
i at release 7.2.
For more information about connecting IBM i Access Client Solutions to IBM i systems, see
the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzajr/rzajr
pdf.pdf
Note: Customers using IBM i 6.1 or IBM i 7.1 can acquire IBM i Access Client Solutions by
downloading it from the Entitled Software Support (ESS) website
(https://www-304.ibm.com/servers/eserver/ess/index.wss) under 5761-SS1 or
5770-SS1. Customers can acquire media by ordering 5761-SS1 or 5770-SS1 refresh
feature 6288. The physical media for IBM i Access Client Solutions does not contain the
optional Windows and Linux Application Packages. Those packages are only available
from the Entitled Software Support (ESS) website.
Program launchers
The Table 2-2 shows the launcher locations for IBM i Access Client Solutions.
Table 2-2 Program launcher locations for IBM i Access Client Solutions
Operating Systems
Program Launcher Locations
Windows 32-bit
Start_Programs\Windows_i386-32\acslaunch_win-32.exe
Windows 64-bit
Start_Programs\Windows_x86-64\acslaunch_win-64.exe
Linux 32-bit
Start_Programs/Linux_i386-32/acslaunch_linux-32
Linux 64-bit
Start_Programs/Linux_x86-64/acslaunch_linux-64
Macintosh
Start_Programs/Mac_i386-32_x86-64/acslaunch_mac
Main User Interface

Figure 2-130 on page 117 shows the main user interface of IBM i Access Client Solutions
core offering version 1.1.3.
116
Figure 2-130 Main user interface of IBM i Access Client Solutions
Function restrictions
IBM i Access Client Solutions version 1.1.3 allows the workstation administrator to restrict the
functions of the client. This function is available in Edit Preferences Restrictions. For
example, in Figure 2-131 on page 118, the administrator can select the checkboxes
representing what functions to restrict for non-administrator users. Click OK to save the
restrictions and they will be applied after the next application restart.
117
Figure 2-131 Functions restriction example in IBM i Access Client Solutions
Figure 2-132 on page 119 shows the result of restricted functions.
118
Figure 2-132 Restricted functions in IBM i Access Client Solutions
5250 emulation console bar

In IBM i Access Client Solutions version 1.1.3, 5250 console gets a new feature called
console bar. The console bar will show the current state of IPL type, System Reference
Codes (SRCs) and so on. To display the console bar, click View Console bar. It will add a
console bar to your 5250 console as shown in Figure 2-133 on page 120. This function works
on both HMC and LAN console.
119
Figure 2-133 Console bar in 5250 console
Virtual control panel

Virtual control panel capability is enhanced in IBM i Access Client Solutions version 1.1.3 to
support the connection to an HMC console in addition to LAN console. The Virtual Control
Panel to an HMC console is shown in Figure 2-134.
Figure 2-134 Virtual Control Panel connection to HMC console
Improved macro conversion capability

IBM i Access Client Solutions gives users the facility to convert macros made in IBM Personal
Communications (PCOMM) to IBM Host-on-Demand. This feature helps IBM i users to
migrate from PCOMM to Host-on-Demand in IBM i Access Client Solutions. Macro
conversion compatibility is improved in version 1.1.3 to support the conversion of more
keystrokes.
To convert a macro, click 5250 Session Manager from IBM i Access Client Solutions, then on
the session manager window click File Convert Macro as shown in Figure 2-135.
120
Figure 2-135 Convert Macro menu in 5250 Session Manager
The Convert Macro window as shown in Figure 2-136 appears from which you can specify
the location of the original macro file (*.mac) and the target location of the newly converted
macro. Click Convert to start the conversion process.
Figure 2-136 Convert Macro window in IBM i Access Client Solutions
121
Note: The samples of features above were tested in IBM i Access Client Solutions core
offering version 1.1.3.
Access Client Solutions: Windows Application Package

The Access Client Solutions Windows Application Package provides middleware for using
and developing client applications for Windows operating systems. Windows Application
Package is an optional package for Windows that is part of the IBM i Access Client Solutions
product. Users and application programmers can use Windows Application Package to
leverage business information, applications, and resources across an enterprise by extending
the IBM i resources to the PC desktop.
Access Client Solutions Windows Application Package provides the following features:
An extensive number of Application Programming Interfaces (APIs)
Provides accessibility to DB2 for i using ODBC, .NET, and OLE DB
Secure connection to IBM i using Secure Socket Layer (SSL)
FIPS (Federal Information Processing Standard) compliance
Access Client Solutions: Linux Application Package

Similar to Windows Application Package, the Linux Application Package is an optional
package for Linux platforms that contain the following features:
Full 64-bit ODBC support
Both RPM and deb packages for Debian and Ubuntu distributions
Linux on Power support
When combined with the products core offering (IBM i Access Client Solutions), the Linux
Application Package provides a complete replacement for the legacy product IBM i Access for
Linux. In addition, the core product offering provides several additional features that are not
available in IBM i Access for Linux.
For more information about IBM i Access Client Solutions Application Packages, see the IBM
i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahg/rzahgicca2.htm
2.2.2 IBM i Access for Web

IBM i Access for Web offers web-based access to IBM i. IBM i Access for Web enables end
users to leverage business information, applications, and resources across an enterprise by
extending the IBM i resources to the client desktop or a mobile device through a web browser.
Feature enhancements
In the 7.2 release, IBM i Access for Web provides the following enhancements:
Viewing active jobs on the system in three different views similar to the Work with Active
Jobs (WRKACTJOB) command
Viewing PTFs and PTF Groups similar to the Display PTF (DSPPTF) and Work with PTF
Groups (WRKPTFGRP)
A new System category for displaying installed products, system values and other system
related information
122
IBM integrated web application server for i Version 8.5

RC4 and AES encryption types with SPNEGO environments
Password expiration based on the QPWDEXPWRN system value
In addition to the above features, PTF SI54619 for IBM i Access for Web will be released to
provide the following enhancements:
A Filter box for row context-based filtering
Support for secure telnet when connecting to port 992
Supported environments
IBM i Access for Web in 7.2 is supported for these web application servers:
1. IBM Integrated Web Application server for i
2. WebSphere Application Server (WAS) Express V8.5 for IBM i, WAS V8.5 for IBM i, and
WAS V8.5 Network Deployment for IBM i
5. WAS - Express V6.1 for i5/OS, WAS V6.1 for i5/OS, and WAS V6.1 Network Deployment
for i5/OS
In addition to the above, IBM i Access for Web can be used with any of the following portal
servers:
1. WebSphere Portal V8.0
2. WebSphere Portal V7.0
3. WebSphere Portal for Multiplatforms V6.1
Note: 7.2 IBM i Access for Web is supported on IBM i releases 7.2, 7.1 and 6.1. For
customers using 7.1 and 6.1 IBM i Access Family (57xx-XW1) it is possible to acquire 7.2
IBM i Access for Web and stay on their current release of IBM i.
For more information about configuring IBM i Access for Web using various supported
application server environment, see the IBM i 7.2 Knowledge Center at:
http://www.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzamm/rzammpdf
.pdf
Main user interface

Figure 2-137 shows the main user interface of IBM i Access for Web in 7.2. The main
navigation menus are located on the left side of the window.
123
Figure 2-137 IBM i Access for Web main user interface
Displaying active jobs

IBM i Access for Web in 7.2 provides the capability to view active jobs in the system. It
enables three different views similar to the Work with Active Jobs (WRKACTJOB) command, such
as: status, elapsed data, and thread data. To view the active jobs, click Jobs Active jobs
menu on the left side of the window. These views are shown in Figure 2-138. Choose the list
at the top of the table, and you can select the alternative views for displaying active jobs.
Figure 2-138 IBM i Access for Web page showing alternative views of active jobs
Figure 2-139 on page 125 shows the elapsed data information from active jobs.
124
Figure 2-139 IBM i Access for Web page showing elapsed data for active jobs
Figure 2-140 shows the thread data information from active jobs.
Figure 2-140 IBM i Access for Web page showing thread data for active jobs
Viewing System information

IBM i Access for Web in 7.2 also enables the user to view system information, such as:
installed products, system values, and so on. To do this, click System on the left side of the
window. The sub-menu of System tasks is displayed. Figure 2-141 on page 126 shows the
installed products from IBM i Access for Web.
125
Figure 2-141 IBM i Access for Web page showing installed products
IBM i Access for Web in 7.2 allows you to view the PTF status with the similar view as the
Display PTF (DSPPTF) command. Click System PTFs on the left side of the window, then
the PTF status will be displayed. Figure 2-142 shows the example of viewing PTF status.
Figure 2-142 IBM i Access for Web page showing PTF status
In addition to PTF status, you can list the PTF Groups installed on the IBM i system. Click
System PTF Groups on the left side of the window. The PTF Groups will be displayed.
Figure 2-143 on page 127 shows the example of viewing PTF groups.
126
Figure 2-143 IBM i Access for Web page showing PTF groups
IBM i Access for Web enables you to display the system values of the IBM i system. To
perform this, click System System values on the left side of the window. The system
value categories will be displayed as shown in Figure 2-144. Click the desired category and it
will display the system values.
Figure 2-144 IBM i Access for Web page showing system values categories
Apart from the systems information above, you can also extract other IBM i object data and
store it in a database table. Once the table is created, it can be queried or modified like any
other database table. However, the created table contains only the snapshot of the object
information. Therefore, to access the most recent information, you need to run the extract
request again. Figure 2-145 on page 128 shows the IBM i object data extraction menu.
127
Figure 2-145 IBM i Access for Web page showing list of IBM i object data that can be extracted
Context-based filtering
IBM i Access for Web in 7.2 provides the filter box for context-based filtering. This filter box is
available from various features in IBM i Access for Web, such as: displaying messages, jobs,
PTF, system values, and so on. It enables the users to easily search the information within the
table based on the entered text.
Figure 2-146 shows the example of filtering PTF ID using TC in the filter box.
Figure 2-146 Filter box for context-based filtering in IBM i Access for Web
Secure telnet in 5250 session

IBM i Access for Web in 7.2 has added support for making a secure telnet connection. When
specifying port 992 for a 5250 display session, a secure telnet connection will be made
128
pending certificate validation. The secure telnet session will validate the certificate chain, but
will not perform server authentication nor client authentication.
To start a secure telnet in 5250 session, select 5250 Start session. The Start Session
page will appear as shown in Figure 2-147. Specify port 992 in the Port field.
Figure 2-147 Start session parameter for secure telnet
Secure telnet in the 5250 session shown in Figure 2-148, can be identified by the SSL label at
the bottom of the 5250 screen.
Figure 2-148 Secure telnet in 5250 session
129
2.2.3 IBM i Mobile Access

IBM i Access for Web (5770XH2) has also added support for mobile devices. This enables
IBM i users to access IBM i resources from web-enabled mobile devices in a mobile-friendly
view.
Mobile Features
The same features available from IBM i Access for Web are now available from a mobile
device including:
View and manage jobs, messages, output queues, files and printers
View PTFs and PTF Groups
View, add, insert and update database records
Build, run, save SQL statements with an SQL wizard
Start one or more emulation sessions with the ability to reconnect even after a device
power down
Extract data from a variety of IBM i resources into a table using optional column selection
Distribute and manage files to other users from a common download location
Support for making secure telnet connections
With PTF SI54619 (or its supersedes), the following additional features are enabled:
Enhanced mobile navigation menu
Filter box for row context-based filtering
Action buttons appear in a context menu when the row is selected
Prerequisites and configurations

The following are the prerequisites and configurations that are needed to enable IBM i Mobile
Access:
Install 7.2 5770XH2 on IBM i system
Load 5770XH2 PTF: SI53292 (or its supersedes)
Load the latest IBM i HTTP Group PTF for the IBM i release you are using
Release 7.2: SF99713 (level 1 or later)
Start the HTTP *ADMIN server on the system by using this command: STRTCPSVR
SERVER(*HTTP) HTTPSVR(*ADMIN)
Configure the mobile instance by using this command: CFGACCWEB
APPSVRTYPE(*INTAPPSVR) INSTANCE(*MOBILE)
Access this URL from a web-enabled mobile device:
http://your_system_name:2001/iamobile/
Sign on with User ID and Password
130
Note: This feature is provided as part of 7.2 IBM i Access for Web (5770XH2) which can
be installed on IBM i release 7.2, 7.1 and 6.1. If you are using IBM i release 6.1 or 7.1, it is
available on the Entitled Software Support (ESS) website
(https://www-304.ibm.com/servers/eserver/ess/index.wss) as feature 6289 under SS1
or Licensed Program publication number: LCD8-1965-00.
Mobile user interface

Figure 2-149 shows the user interface for IBM i Mobile Access. It provides a similar navigation
menu to IBM i Access for Web in a mobile-friendly web page.
Figure 2-149 Main user interface of IBM i Mobile Access
Working with active jobs

Displaying active jobs in IBM i Mobile Access also enables users to view various job
information, similar to Work with Active Jobs (WRKACTJOB) command in 5250 session. To view
the active jobs, select Jobs Active jobs. Figure 2-150 on page 132 shows the interface of
working with active jobs in IBM i Mobile Access.
131
Figure 2-150 Working with active jobs in IBM i Mobile Access
Action buttons in pop-up menu

IBM i Mobile Access in 7.2 provides enhancements to the user interface, where users can
easily select an entry in a view, then select operations related to it. Figure 2-151 on page 133
shows the example of action buttons for a row entry in working with active jobs. When users
click the specific row, a pop-up menu containing action buttons will be displayed. This
improves the user experience when viewing IBM i resources from their mobile devices.
132
Figure 2-151 Action buttons pop-up menu in IBM i Mobile Access
SQL functions
IBM i Mobile Access also provides the capability of running SQL statements and viewing the
results in the mobile browser. To run SQL, select Database Run SQL. This will show the
Run SQL page as shown in Figure 2-152 on page 134. An SQL wizard is available for building
SQL statements.
133
Figure 2-152 Running SQL on IBM i Mobile Access
The Figure 2-153 on page 135 shows the SQL output page on mobile browser.
134
Figure 2-153 SQL output viewed in IBM i Mobile Access
5250 sessions
Similar to IBM i Access for Web, IBM i Mobile Access also provides the capability to start
5250 sessions for accessing IBM i via green screen. To start a 5250 session, select 5250
Start session. The Start Session page will appear as shown in Figure 2-154 on page 136.
On this page, you can configure the parameter for your 5250 session.
135
Figure 2-154 Starting 5250 session on IBM i Mobile Access
The Figure 2-155 on page 137 shows the interface of 5250 telnet session from a mobile
browser.
136
Figure 2-155 5250 telnet session on IBM i Mobile Access
Secure telnet in 5250 session

Similar to IBM i Access for Web, IBM i Mobile Access also allows the users to start a secure
telnet in a 5250 session using SSL. This function derives its support from the same support in
IBM i Access for Web, where the secure telnet connection will be made pending certificate
validation and its session will validate the certificate chain, but will not perform server
authentication nor client authentication.
To perform this function, users can select 5250 Start session and specify port 992 in the
Port field. Figure 2-156 on page 138 shows the example of secure telnet started in a mobile
browser. The SSL keyword at the bottom of the screen identifies that the telnet session is
secured using SSL.
137
Figure 2-156 5250 secure telnet session on IBM i Mobile Access
2.3 Application Runtime Expert for i

Application Runtime Expert for i (ARE) is a product that is first introduced in IBM i 7.1 and the
feature has been leveraged to IBM i 6.1 as well. ARE can help users to ensure consistent
performance and deployment for any workload that is running on systems.
IBM i 7.2 release still supports ARE for i under the 5733ARE product. For detailed
functionality and configuration, a Redpaper publication has been released at:
http://www.redbooks.ibm.com/redpieces/abstracts/redp4805.html?Open
For more information about Application Runtime Expert for i, see the IBM i 7.1 Technical
Overview with Technology Refresh Updates Redbooks publication and at:
http://www.redbooks.ibm.com/abstracts/sg247858.html
2.4 Journal management

This section describes journal enhancements implemented in IBM i 7.2.
138
2.4.1 STRJRN parameter on restore commands

New parameter Start journaling (STRJRN) has been added to Restore Object (RSTOBJ) and
Restore Library (RSTLIB) CL commands.This parameter controls if the journaling should be
automatically started for the new objects after restore. Journal information that was saved will
be restored regardless of the value of the parameter. Existing objects are not affected. This
parameter takes precedence over QDFTJRN data area and journal inheritance
2.4.2 Deferred journal restore

In IBM i 7.2 restore processing has been enhanced to allow start of journaling to be deferred
for database files, data areas, data queues and libraries when the object or library is restored
prior to the journal. Once the journal is restored, the object that deferred start of journaling will
now reestablish and resume journaling.
To use this feature, the user must specify the Defer ID (DFRID) on the restore operation. The
DFRID is an optional parameter on the Restore Library (RSTLIB) command, Restore Object
(RSTOBJ) command, and Restore Object List (QSRRSTO) API. Currently the Defer ID is used
to defer the restore of Views (Logical Files) and Materialized Query Tables (MQTs) that are
restored prior to their based on files.This enhancement allows the Defer ID support to be
used to defer starting journaling on an object.
To explicitly use this enhancement, the Restore Deferred Objects (RSTDFROBJ) new command
can be called directly using the same DFRID value that was used on RSTOBJ or RSTLIB.
Following restore operations are configured to utilize Defer ID:
GO RESTORE option 21
Start Recovery using BRM (STRRCYBRM)
For more information about deferred journal restore, see IBM i Technology Updates website
at:
echnology%20Updates/page/Deferred%20Journal%20Restore
2.4.3 Secure remote journal

Starting from V7R2 remote journaling now honors the secure connection field in a Relational
Database (RDB) Directory Entry screen (ADDRDBDIRE, CHGRDBDIRE). Secure remote journaling
uses default TCP/IP port 3889 and cipher defined in Digital Certificate Manager under
application ID:
IBM i Remote Journaling Source (as application client)
IBM i Remote Journaling Target (as application server)
Note: To secure remote journaling work, both source and the target systems must be at
V7R2.
Depending on the cipher used under DCM, performance impact and remote entry
synchronization delay can occur.
For more information secure remote journaling, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaq9/rzaq9osJRNrjsecur
econnect.htm?lang=en
139
2.4.4 QJOSJRNE API change

Force journal entry key now accepts new value of 2 which means that the journal receiver is
forced to auxiliary storage, but no journal entry is sent.
For more information about QJOSJRNE API, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/QJOSJRNE.htm?lang=
en
2.4.5 Journal conversion after IBM i 7.2 install

After IBM i 7.2 is installed or updated, a Change Journal (CHGJRN) command is issued once for
all journals on the system. This action supports a conversion, which is required for internal
information of the journal and journal receiver objects.
2.4.6 Journal limits changes

Following journal limits changes have been implemented in IBM i 7.2:
Maximum number of journal receivers allowed in a range of receivers on a journal
command has been increased from 1024 to 2045.
Maximum number of active commitment definitions with object-level changes that can be
processed concurrently by an APYJRNCHG or APYJRNCHGX command has been increased
from 1023 to 32767 if commitment control if already active.
Maximum number of journal receivers that can be associated with one journal has been
added and its value is 131036.
For more information about journal limits, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzamp/rzampjournal.htm?
lang=en
2.4.7 New journal entry types

Following new journal entry types have been added in V7R2:
D code new types (row and column access control):
M1 for create mask
M2 for drop mask
M3 for alter mask
P1 for create permission
P2 for drop permission
P3 for alter permission
T code new types (audit journal):
X2 for query manager profile changes
AX for row and column access control
PF for PTF operations
PU for PTF object changes
For more information about journal entry codes and types, see IBM i 7.2 Knowledge Center
at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaki/rzakijournalfinde
rall2.htm?lang=en
140
2.4.8 Displaying journal information

Following section depicts changes that have been made in IBM i 7.2 to retrieve journal
information easier.
Journal information for table on IBM Navigator for i

IBM Navigator for i has been extended with option to display journal information for a table.
new menu option Journaling has been added to the context menu on Tables panel as shown
on Figure 2-157 on page 141.
Figure 2-157 Journaling information available for particular table on Tables panel
Journaling menu option opens detailed journaling information panel for choosen table as
shown on Figure 2-158 on page 142.
141
Figure 2-158 Detailed journaling information for database table
It is now available to view journal entries from IBM i Navigator for i. Journals panel has been
enhanced with new menu option View Entries... for a selected journal as shown on
Figure 2-159 New View Entires... menu option on Journals panel
View Entries... menu option opens Journal Viewer panel with ability to filter and present
journal entires for the selected journal an shown on Figure 2-160 on page 142. Viewing entry
specific data is also available from this panel.
Figure 2-160 Journal Viewer panel
For more information about journaling information for table on IBM Navigator for i, see IBM i
7.2 Knowledge Center at:
142
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaki/rzakidspjrni.htm?
lang=en
Display_Journal table function

Now users can use QSYS2/Display_Journal SQL table function to view journal entries. This
function is more efficient than displaying journal entries to an output file using Display Journal
(DSPJRN) CL command and then querying the resulting file.
For more information about QSYS2/Display_Journal SQL table function, see IBM i 7.2
Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzajq/rzajq
udfdisplayjournal.htm
2.4.9 Journal Sizing and Planning Tool

Journal sizing and planning tool is available for IBM i 7.2. The tool can be used to determine
the amount of additional I/O workload that might be generated by journaling one or more
database files.
Note: Journal Sizing and Planning Tool only predicts workload for database files, not for
any other object types.
For information about downloading and using the tool, search following website for Journal
Sizing and Planning Tool:
http://www-03.ibm.com/systems/power/software/i/db2/support/code/journal-utilities.
html
2.5 Work management enhancements

This section describes IBM i 7.2 enhancements for temporary storage management, IBM i
commands, and APIs.
2.5.1 Temporary Storage Enhancements

Temporary storage in IBM i system, also called as an unprotected storage, is a place in the
system storage where programs, running under jobs and system functions, put objects
required during execution time. It is used to keep automatic, static, heap and teraspace
storage for programs, temporary objects created by programs either for a single job or reused
across multiple jobs or working storage for Licensed Internal Code (LIC) to support the
operating system. Temporary storage is reclaimed on each IPL.
IBM i 7.2 introduces significant temporary storage enhancements which allow for accurate
temporary storage usage tracking system-wide and at a job level. Following section describes
new features related to the temporary storage.
Storage Management buckets

Prior to IBM i 7.2 retrieving information about temporary storage used by the system or a
particular job was not easy and often required using multiple tools or IBM support. The
143
information might have been misleading or inaccurate especially when the storage was
allocated by one job or task and then returned by the other.
In IBM i 7.2 storage management has been changed to use new buckets to collect storage
usage information. The buckets track temporary storage:
scoped to a single job

scoped to multiple jobs
scoped to the system
for LIC allocations (so called no charge)
for allocations that persist after job ends
Total value of all buckets will match to Current temporary storage value on Work with
System Status (WRKSYSSTS) screen. Figure 2-163 on page 146 shows temporary storage
currently used by the system in megabytes. SYSTMPSTG file in QSYS2 library can be queried for
the current size of all available storage buckets on the system as shown in Example 2-1.
Running SQL query over this file is a quick way to find biggest temporary storage consumers
during the problem situation.
Example 2-1 Displaying content of temporary storage buckets in SYSTMPSTG file
SELECT * FROM QSYS2/SYSTMPSTG ORDER BY BUCKET_CURRENT_SIZE DESC

BUCKET_NUMBER
1
65,981
9
65,724
65,726
65,878
65,699
65,572
65,683
65,641
65,714
65,537
3
65,671
65,543
8
65,542
66,010
4,096
GLOBAL_BUCKET_NAME
*MACHINE
*DATABASE SQE Heap
*PASE
*DATABASE Segment Cache
*OS
JOB_NAME
JOB_USER_NAME JOB_NUMBER BUCKET_CURRENT_SIZE
690,081,792
ADMIN2
QLWISVR
001418
427,245,568
195,182,592
ADMIN4
QWEBADMIN
001163
188,657,664
ADMIN1
QLWISVR
001162
167,432,192
ADMIN3
QLWISVR
001315
163,217,408
QUSRDIR
QDIRSRV
001136
155,234,304
QTCPWRK
QSYS
001014
151,543,808
Q1ACPDST
QBRMS
001120
129,605,632
QYPSPFRCOL QSYS
001078
98,832,384
QYPSJSVR
QYPSJSVR
001151
91,832,320
SCPF
QSYS
000000
87,728,128
76,705,792
QSRVMON
QSYS
001108
64,876,544
QDBSRV05
QSYS
000985
61,415,424
60,076,032
QDBSRV04
QSYS
000984
58,044,416
QZRCSRVS
QUSER
001447
54,501,376
53,792,768
More...
The same information is now available thorugh IBM Navigator for i under System --> System
Status. This is presented on Figure 2-161 on page 145.
144
Figure 2-161 Accessing temporary storage buckets information
Temporary Storage Details button on Disk Space tab opens Temporary Storage Details
panel shown on Figure 2-162 on page 145.
Figure 2-162 Temporary Storage Deatils panel
145
Controlling temporary storage

In V7R2, Work with System Status (WRKSYSSTS) screen, Work with Active Jobs (WRKACTJOB)
screen, Display Job Run Attributes (DSPJOB) screen, and Display Job Tables (DSPJOBTBL)
screen has been changed or extended with temporary storage information.
Work with System Status (WRKSYSSTS)

Work with System Status screen has been changed to the new field names as shown in
Table 2-3.
Table 2-3 Filed name changes on Work with System Status screen
V7R1 and earlier
V7R2
Current unprotect used
Current temporary used
Maximum unprotect
Peak temporary used
Work with System Status screen is shown on Figure 2-163 on page 146.
Work with System Status
09/26/14
% CPU used . . .
Elapsed time . .
Jobs in system .
% perm addresses
% temp addresses
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:
:
:
:
:
3.9
00:09:06
492
.007
.010
Auxiliary storage:
System ASP . . . . . .
% system ASP used . .
Total . . . . . . . .
Current temporary used
Peak temporary used .
:
:
:
:
:
UT30P05
15:51:56
95.44 G
40.3456
95.44 G
4259 M
4344 M
Type changes (if allowed), press Enter.

System
Pool
Reserved
Max -----DB----- ---Non-DB--Pool Size (M) Size (M) Active Fault Pages Fault Pages
1
471.41
222.58
+++++
.0
.0
.1
.1
2
3134.42
7.21
71
.0
.1
.0
.8
3
405.14
.00
102
.0
.0
.3
.6
4
40.51
.00
5
.0
.0
.0
.0
Bottom
Command
===>
F3=Exit F4=Prompt F5=Refresh
F19=Extended system status
F9=Retrieve F10=Restart
F24=More keys
F12=Cancel
Figure 2-163 System-wide temporary storage usage
Extended System Status screen (F19 from WRKSYSSTS) has been extended with new fields
showing percentage of temporary storage used and limit. For more information about
temporary storage limits, see Temporary storage limits on page 151. New fields added to
Extended System Status screen are shown on Figure 2-164 on page 147.
Note: % temporary storage used and % temporary storage limit fields on the Extended
System Status screen are visible only when notification limit is set for system ASP. For
more information about temporary storage limits, see Temporary storage limits on
page 151.
146
Work with System Status

UT30P05
..............................................................................
:
Extended System Status
UT30P05
:
:
09/26/14 16:56:39 :
: Elapsed time . . . . . . . . . . . . . . . : 01:13:49
:
: % CPU used . . . . . . . . . . . . . . . . :
4.6
:
: % uncapped CPU capacity used . . . . . . . :
1.1
:
: % temporary storage used . . . . . . . . . :
4.5
:
: % temporary storage limit . . . . . . . . . :
50
:
:
:
:
:
:
:
:
:
:
Bottom :
:
:
: F3=Exit F5=Refresh
F10=Restart
F12=Cancel
:
:
:
:............................................................................:
Bottom
Command
===>
F3=Exit F4=Prompt F5=Refresh F9=Retrieve F10=Restart F12=Cancel
F19=Extended system status
F24=More keys
Figure 2-164 Temporary storage information on Extended System Status screen
Work with Active Jobs (WRKACTJOB)

Work with Active Jobs screen has been extended with temporary storage information for
every job. It allows to sort jobs according to temporary storage used for ease of control.
Sorting can be done using either SEQ(*TMPSTG) on the WKRACTJOB CL command or by using
F16 with the cursor Temporary Storage column. Figure 2-165 on page 148 shows temporary
storage used by jobs in megabytes.
147
Work with Active Jobs

CPU %:
4.1
Elapsed time:
Type options, press Enter.

2=Change 3=Hold 4=End
8=Work with spooled files
Opt Subsystem/Job
ADMIN2
ADMIN4
ADMIN1
QUSRDIR
QTCPWRK
ADMIN3
QYPSJSVR
SCPF
QYPSPFRCOL
User
QLWISVR
QWEBADMIN
QLWISVR
QDIRSRV
QSYS
QLWISVR
QYPSJSVR
QSYS
QSYS
04:10:31
09/26/14
Active jobs: 227
5=Work with 6=Release

13=Disconnect ...
Number
001418
001163
001162
001136
001014
001315
001151
000000
001078
7=Display message
Type CPU % Threads

BCI
.2
93
BCI
.0
41
BCI
.0
34
BCH
.0
12
SYS
.0
2
BCI
.0
33
BCH
.0
39
SYS
.0
1
BCH
.0
30
Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F12=Cancel
F17=Top
F18=Bottom
F23=More options
UT30P05
17:38:37
Temporary
Storage
405
176
157
148
145
141
87
84
79
More...
F11=Display status
F24=More keys
Figure 2-165 Temporary storage information on the Work with Active Jobs screen
The same information is now available thorugh IBM Navigator for i under Work
Mangement Active Jobs as presented on Figure 2-166 on page 148 has been
customized for readability.
Figure 2-166 Active Jobs panel with Temporary Storage Information for every job
148
Display Job Run Attributes (DSPJOB)

Display Job Run Attributes screen has been extended with Peak temporary storage used
field showing maximum temporary storage used by the job. Figure 2-167 on page 149 shows
peak temporary storage used by sample job in megabytes.
Display Job Run Attributes
Job:
QPADEV0002
User:
WILKU
Run priority . . . . . . . . . . . . .
Time slice in milliseconds . . . . . .
Eligible for purge . . . . . . . . . .
Default wait time in seconds . . . . .
Maximum CPU time in milliseconds . . .
CPU time used . . . . . . . . . . . .
Maximum temporary storage in megabytes
Temporary storage used . . . . . . .
Peak temporary storage used . . . . .
Maximum threads . . . . . . . . . . . .
Threads . . . . . . . . . . . . . . .
Thread resources affinity:
Group . . . . . . . . . . . . . . . .
Level . . . . . . . . . . . . . . . .
Resources affinity group . . . . . . .
Number:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:
:
:
:
:
:
:
:
:
:
:
. . . . . :
. . . . . :
. . . . . :
System:
002154
UT30P05
20
2000
*YES
30
*NOMAX
5
*NOMAX
2
2
*NOMAX
1
*NOGROUP
*NORMAL
*NO
Press Enter to continue.

F3=Exit
F5=Refresh
F9=Change job
F12=Cancel
F16=Job menu
Figure 2-167 Peak temporary storage value on Display Job Run Attributes screen
Display Job Tables (DSPJOBTBL)

Display Job Tables screen has been extended with Storage used value which represents
temporary storage in megabytes for both active and available temporary job structures.
Figure 2-168 on page 150 shows storage used in megabytes on the Display Job Tables
screen.
149
Display Job Tables
UT30P05
Permanent job structures:

Initial . . . . : 200
Additional . . . :
30
Available . . . :
6
Total . . . . . : 500
Maximum . . . . :
163520
Table
1
09/29/14 09:23:25
Temporary job structures:
Initial . . . . :
200
Additional . . . :
30
Available . . . :
21
Storage used . . : 24.00 M
---------------------Entries---------------------Total
Available
In-use
Other
500
6
493
1
Size
529152
Bottom
F3=Exit
F5=Refresh
F11=In-use entries
F12=Cancel
Figure 2-168 Temporary storage information on the Display Job Tables screen
Message CPF1164
When the job ends, message CPF1164 is sent to the QHST and the jobs job log. In IBM i 7.2
the message has been extended with the maximum temporary storage value for the job, as
shown on Figure 2-169 on page 151.
150
Display Formatted Message Text

System:
Message ID . . . . . . . . . :
Message file . . . . . . . . :
Library . . . . . . . . . :
UT30P05
CPF1164
QCPFMSG
QSYS
Message . . . . : Job &3/&2/&1 ended on &14 at &15; &10 seconds used; end
code &8 &13.
Cause . . . . . : Job &3/&2/&1 completed on &14 at &15 after it used &10
seconds processing unit time. The maximum temporary storage used was &18
megabytes. The job had ending code &8. The job ended after &7 routing steps
with a secondary ending code of &9. The job ending codes and their meanings
are as follows:
0 - The job completed normally.
10 - The job completed normally during controlled ending or controlled
subsystem ending.
20 - The job exceeded end severity (ENDSEV job attribute).
30 - The job ended abnormally.
40 - The job ended before becoming active.
More...
F3=Exit
F11=Display unformatted message text
F12=Cancel
Figure 2-169 Maximum temporary storage information on CPF1164 message.
Temporary storage limits

As in previous releases, maximum temporary storage for a job can be controlled via
MAXTMPSTG parameter in the class description (CRTCLS, CHGCLS). In IBM i 7.2 the same
parameter has been added to CHGJOB command allowing a user to change that limit after the
job started execution. Use following command to change maximum temporary storage limit
for a job to 20 MB, substituting NUMBER, JOBUSER, and JOBNAME with proper values:
CHGJOB JOB(NUMBER/JOBUSER/JOBNAME) MAXTMPSTG(20)
This is especially useful in conjunction with changed system behavior when a job reaches
maximum temporary storage limit. V7R2 will now hold the job, instead of ending it. A user has
been given opportunity to examine held job and decide whether it should be ended, released
or investigated further. He can use CHGJOB command to extend the limit and release the job for
further execution. Now, when a job reaches maximum temporary storage limit, a new
message CPI112E is sent to QHST and the jobs job log as shown on Figure 2-170 on
page 152.
151

System:
Message ID . . . . . . . . . :
Message file . . . . . . . . :
Library . . . . . . . . . :
UT30P05
CPI112E
QCPFMSG
QSYS
Message . . . . : Job &3/&2/&1 held by the system, MAXTMPSTG limit exceeded.

Cause . . . . . : The current routing step for job &3/&2/&1 specifies a
maximum temporary storage limit of &4 megabytes.
Recovery . . . :
If you want the job to continue, use the Change Job (CHGJOB) command to
specify a larger MAXTMPSTG value for the job and then use the Release Job
(RLSJOB) command.
If the application is in error, use the End Job (ENDJOB) command to end
the job.
To avoid this condition in the future, use the Change Class (CHGCLS)
command to specify a larger MAXTMPSTG value or use the Change Routing Entry
(CHGRTGE) command to specify a different class.
Bottom
F3=Exit
F12=Cancel
Figure 2-170 Message text for CPI112E, new to IBM i 7.2
Control Temporary Storage API

V7R2 introduces new API Control Temporary Storage (QWCCTLTS). The API allows a user
for:
setting temporary storage notification threshold for system ASP as a percentage of total
system ASP
setting temporary storage notification threshold for a specific storage bucket in megabytes
or gigabytes
resetting previously set threshold
displaying current threshold values
Exceeding threshold for system ASP triggers new CPF090A message as shown on
Exceeding threshold for one of the buckets triggers new CPI11AB message as shown on
Threshold notification messages are sent once per hour as long as the threshold is exceeded.
152

System:
Message ID . . . . . . . . . :
Message file . . . . . . . . :
Library . . . . . . . . . :
UT30P05
CPF090A
QCPFMSG
QSYS
Message . . . . : Temporary storage threshold reached.

Cause . . . . . : The amount of storage used for temporary objects in the
system ASP is &4 percent. This is a serious system condition. The temporary
storage used is &6 &5 (&1 bytes). The storage available is &7 &5 (&2 bytes).
This message will be repeated until the amount of storage used is reduced to
less than &3 percent.
Recovery . . . : Use the WRKSYSSTS command to monitor storage used. To
reduce the amount of temporary storage, use the Work with Active Jobs
command (WRKACTJOB SEQ(*TMPSTG)) to find jobs that are consuming large
amounts of storage. Storage used by a job can be released by ending the job
(ENDJOB). Holding a job (HLDJOB) will stop a job from consuming more
storage.
Bottom
F3=Exit
F12=Cancel
Figure 2-171 CPF090A message when ASP temporary storage threshold is reached

System:
Message ID . . . . . . . . . :
Message file . . . . . . . . :
Library . . . . . . . . . :
UT30P05
CPI11AB
QCPFMSG
QSYS
Message . . . . : Storage limit reached for temporary storage bucket &1.

Cause . . . . . : The amount of auxiliary storage used for temporary storage
bucket &1 has reached &2 &4 which is &5 percent of all disk storage in the
system auxiliary storage pool. The limit is &3 &4 (&6 percent).
Recovery . . . : You can run the STRSQL command to start the interactive
SQL program and then run SQL statement SELECT * FROM QSYS2.SYSTMPSTG to see
the amount of temporary storage for &1 and the other temporary storage
buckets on the system. &7
Technical description . . . . . . . . : Use the Control Temporary Storage
(QWCCTLTS) API to change the storage limit for the temporary storage bucket.
Bottom
F3=Exit
F12=Cancel
Figure 2-172 CPI11AB message when temporary storage bucket threshold is reached
153
Following are usage examples for the QWCCTLTS API showing how to set, reset and display
threshold notifications limits for temporary storage.
To set temporary storage notification threshold for system ASP to 40% of the size use this
command:
CALL QWCCTLTS PARM(*SETLMTPCT *ALL 40)
To set temporary storage notification threshold to 50 gigabytes for Save/Restore storage
bucket (category) use this command:
CALL QWCCTLTS PARM(*SETLMTG *SR 50)
To remove temporary storage notification limit system-wide use this command:
CALL QWCCTLTS PARM(*SETLMTPCT *ALL 0)
To display temporary storage notification threshold use this command:
CALL QWCCTLTS PARM(*DSPLMT *ALL)
For more information about QWCCTLTS API and temporary storage categories, search IBM i
7.2 Knowledge Center for QWCCTLTS at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahg/ic-homepage.htm
Temporary Storage enhancements within IBM Navigator for i

IBM i 7.2 introduces significant enhancements to temporary storage in IBM Navigator for i.
This new functionality has been described in detail in section , Work with Active Jobs
(WRKACTJOB) on page 147 of this publication.
Collection Services enhancements

New fields has been added to QAPMJOBMI (job level) and QAPMSYSTEM (system level)
performance data files to keep temporary storage information on a job and system level.
For more information about collection services file description, see IBM i 7.2 Knowledge
Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahx/rzahxcatfilerelat
ion.htm?lang=en
2.5.2 PTF related changes

Conditional immediate PTFs
In IBM i 7.2 we now have conditional immediate PTFs. PTFs are identified with a type of
either delayed or immediate. A delayed PTF must be applied or removed during IPL. An
immediate PTF can be applied or removed either while the system is active, or during IPL.
Before IBM i 7.2, when a new PTF supersedes a delayed PTF, the new PTF was required to
be delayed even if only immediate parts/objects are being changed or added. Within IBM i
7.2, we can now have superseding PTFs being immediately applied when only immediate
parts/objects are being changed. When the PTF is applied or removed, PTF management
will determine if the PTF can be applied or removed immediately or not, depending on if the
most recent delayed superseded PTFs are permanently applied.
154
The DSPPTF (Display Program Temporary Fix)command will add new option 12 to the
Display PTF Details panel for delayed superseded PTFs, as shown in Figure 2-173 on
page 155.
Display PTF Details
Product ID/PTF ID . . . . . . . . . :
Release . . . . . . . . . . . . . . :
5770SS1
V7R2M0
SI53649
Select one of the following:

1. General information
4. Superseded PTFs
6. PTF Objects
7. Symptom strings
9. APARs fixed
12. Delayed superseded PTFs
More...
Selection
F3=Exit
F12=Cancel
Figure 2-173 Display PTF details
When option 12 is selected, a new panel will be displayed listing the delayed superseded
PTFs for the conditional immediate PTF as shown in Figure 2-174.
Display Delayed Superseded PTFs
Product ID/PTF ID . . . . . . . . . :
Release . . . . . . . . . . . . . . :
5770SS1
V7R2M0
PTF ID
SI52813
PTF ID
SI53649
Bottom
Press Enter to continue
F3=Exit
F12=Cancel
Figure 2-174 Display Delayed Superseded PTFs - option 12
Note: The QPZRTVFX API will support a new format PTFR1100 to return the list of
delayed superseded PTF ids for a conditional immediate PTF.
155
For OUTPUT(*PRINT), the new delayed superseded PTFs section will be added to the
spoolfile.
Note: A conditional immediate PTF will not be identified by a new type (immediate or
delayed), but rather by the presence of the new delayed superseded PTFs list. This new list
is used at apply and remove time to determine if the PTF can be applied or removed
immediately or if the operation must be delayed. This is consistent with immediate PTFs
that specify delayed prerequisite PTFs. If the delayed prerequisite PTFs have a status of
temporarily or permanently applied, the dependent PTF can be applied immediate,
otherwise, the dependent PTF is set for delayed apply. Also if an immediate PTF has
preconditions that are not satisfied, the PTF is set for delayed apply.
Display PTF Apply Information (DSPPTFAPYI)

The Display PTF Apply Information (DSPPTFAPYI) command will indicate if the selected
PTFs can be applied immediately from *SERVICE. All selected PTFs and their requisite PTFs
that are not currently applied are displayed. If a PTF has a status of Superseded, the PTF it is
superseded by is displayed in place of the superseded PTF. Each PTF displayed will have the
Apply Type field set to one of the following:
*IMMED - The PTF can be applied immediately. For Licensed Internal Code (LIC) PTFs,
the PTF install must be done from the ##MACH#B IPL source.
*DELAYED - The PTF requires an IPL to apply because it has a PTF type of Delayed.
*PRECND - The PTF can be applied immediately if all of its preconditions are met.
*ACTRQD - The PTF would have an Action required if the selected PTFs were installed.
*DLYSPR - The immediate PTF requires an IPL to apply because it supersedes a delayed
PTF that is not temporarily or permanently applied.
*REQIPLRQD - The PTF has a requisite PTF that requires an IPL to apply.
*REQPRECND - The PTF has a requisite PTF that has a precondition.
The selected PTFs and requisite PTFs to be installed must exist in *SERVICE. Save files
must exist for the selected PTFs that have not been loaded. The specified PTF group must
exist on the system along with its PTFs and requisite PTFs that are not yet installed.
If the PTFs and PTF groups are on physical media or in an image catalog, use one of the
following methods to copy the PTF save files and PTF groups into *SERVICE before running
this command:
Use the QPZCPYSV API to copy the PTF save files and PTF groups into *SERVICE.
Use the Copy PTF (CPYPTF) command to copy the PTF save files from media into
*SERVICE. Use the Copy PTF Group (CPYPTFGRP) command to copy the PTF groups
into *SERVICE.
Note: :This command is shipped with exclude (*EXCLUDE) public authority and the
QPGMR, QSYSOPR, QSRV, and QSRVBAS user profiles are shipped with private
authorities to use this command.
2.5.3 IBM i command changes

This section describes changes made to IBM i 7.2 commands.
156
CRTIMGCLG changes
Create Image Catalog (CRTIMGCLG) can now add all .ISO and .BIN image files from image
catalog directory to image catalog as virtual volumes. To achieve this use *DIR value for
ADDVRTVOL parameter and *ALL for IMGTYPE parameter. Other options for IBMTYPE parameter
are:
*BIN for all binary images
*ISO for all iso images
For more information about Create Image Catalog command, see IBM i 7.2 Knowledge
Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/crtimgclg.htm?lang=e
n
Other commands changes

For information about changes to other IBM i commands, see IBM i Memo to Users Version
7.2 publication at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzaq9/rzaq9
.pdf
2.5.4 API changes

For detailed description of IBM i 7.2 changes, see IBM i Memo to Users Version 7.2
publication at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzaq9/rzaq9
.pdf
2.6 Operating System Limitation Changes

Variuos system limitations has been changed in IBM i 7.2. Exceeding system limit can cause
application or system outage. It is important to be aware of these limitation during system
planing, configuration, and application design.
For detailed information about current system capacities, see Maximum capacities section
of IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzamp/rzamp
overview.htm
2.7 IBM Advanced Job Scheduler for i

IBM i 7.2 release provides several enhancements on IBM Advanced Job Scheduler for i,
especially its integration with IBM Navigator for i. The enhancements in IBM Navigator for i
related to IBM Advanced Job Scheduler for i are as below:
Support for accessing Schedule, Holiday, and Fiscal Calendar
Support for configuring Command Variables, Application/Job Controls, Permissions, and
Library List in Advanced Job Scheduler Properties
Work Flow Manager added for workflow management
157
New fields available for adding Data Library: Initial ASP group and ASP device
2.7.1 Advanced Job Scheduler Properties

In IBM 7.2 release, IBM Navigator provides more configurations in Advanced Job Scheduler
Properties. From IBM Navigator for i, click Work Management All Task Advanced Job
Scheduler Properties.
Note: For more information about accessing IBM Navigator for i, see the 2.1, IBM
Navigator for i on page 16.
As shown in Figure 2-175, there are several new tabs that are added in IBM Navigator for i
related to Advanced Job Scheduler. This section will explain those new tabs in detail.
Figure 2-175 Advanced Job Scheduler Properties page in IBM Navigator for i
Job Controls/Applications
Applications are jobs that have been grouped together for processing. Job controls are the
defaults assigned to a job as you add it to the job scheduler. Job control defaults include such
things as default application, calendar, holiday calendar, and so on. Each application contains
job control information. The application specified in the definition of a job is used to determine
the job controls used by the job when the job is submitted. If the job does not contain an
application the job will use the job controls in the System Default.
Figure 2-176 on page 159 shows the Job Controls/Applications in Advanced Job Scheduler
Propeties. Users can create, delete, and modify the job control in this page.
158
Figure 2-176 Job Controls/Applications page in Advanced Job Scheduler Properties
Library Lists
Library List contains user-defined list of libraries that is used by an Advanced Job Scheduler
job when it is processing. From this page, you may add a new library list, add a new library list
based on an existing one, or remove a library list, provided that it is not being used by a
currently scheduled job. You may also select a list and display its properties to make changes.
159
Figure 2-177 Library Lists page in Advanced Job Scheduler Propoerties
Command Variables
As shown in Figure 2-178 on page 161, Command Variables page in Advanced Job
Scheduler Properties allows the users to display all the existing command variables on the
system. Command variables are variables that can be stored in Advanced Job Scheduler and
used in jobs submitted through Advanced Job Scheduler. Examples of command variables
include the beginning of each month, a division number, a company number, and so on. From
this page, users can add new variables, add new variables based on existing ones, remove,
and modify them.
160
Figure 2-178 Command Variables page in Advanced Job Scheduler Properties
Permissions
Permissions page allows users to add or modify permissions for functions.
The Figure 2-179 on page 162 shows the Permission page with various default functions
whose authorities can be changed for Advanced Job Scheduler. The name of the function
and a description is displayed. If your user profile has the proper authority, users can add,
remove or edit the authorities for functions. If not, users can still view the function authority
properties, but cannot change them.
161
Figure 2-179 Permissions page in Advanced Job Scheduler Properties
Calendar
In addition to Holiday Calendar access in IBM Navigator for i in previous releases, IBM
Navigator for i release 7.2 allows you to also access the Fiscal Calendar from the web. A
fiscal calendar is a calendar of selected days that can be used by users for scheduleing a job
or a job group. Users can simply configure their start and end dates for each period in the
fiscal year in this web page.
Figure 2-180 on page 163 shows the Fiscal Calendar page in Advanced Job Scheduler
Properties.
162
Figure 2-180 Fiscal Calendar page in Advance Job Scheduler Properties
Data Libraries
Data Libraries in IBM Navigator for i is enhanced with several new parameters to enables the
users easily specify new data library parameters used for Advanced Job Scheduler. The new
parameters are: Initial ASP group and ASP device as seen in Figure 2-181
This enhancements allow the users to specify their initial ASP group and ASP device where
their library resides.
Figure 2-181 New Data Library enhanced parameters
2.7.2 Work Flow Manager

Scheduling a job in IBM Advanced a Job Scheduler for i is more enhanced in IBM i 7.2
release, as IBM Navigator for i now provides a feature that allows users to specify
predecessor and successor of each Advanced Job Scheduler jobs. This feature is called
163
Work Flow Manager. In Work Flow Manager, you can define units of work that consist of
automated or manual steps. There units of work can then be scheduled or run interactively.
Each step within the work flow can have one or more predecessor Advanced Job Scheduler
jobs and one or more successor Advanced Job Scheduler jobs. When a work flow starts, the
first step is flagged to run. When it completes, the next step is flagged to run.
There are several considerations when you use Work Flow Manager:
1. You can manually start a work flow at any step. When you do so, you bypass all previous
steps in the work flow.
2. Automatic steps complete after all prior steps complete. This includes all predecessor
Advanced Job Scheduler jobs.
3. After a step completes, the successor Advanced Job Scheduler jobs are flagged to run.
4. Manual steps can complete in any sequence after the steps predecessor jobs complete.
5. You can mark completed manual steps as not complete and run them again after there are
no subsequent incomplete automatic steps.
6. You can cause a step to wait until the job completes before notifying of the steps by
specifying predecessor jobs that are the same as the successor jobs of the previous step.
7. You can notify other users when a particular step starts, stops, did not start by a specific
time, or is taking too long. For example, you can notify a user who is responsible for a
particular manual step that the previous automated steps complete.
Figure 2-182 shows the Work Flow Manager page in IBM Navigator for i. It displays all the
existing work flows in the system. For displaying Work Flow Manager, click Work
Management All Task Advanced Job Scheduler Work Flow Manager Work
Flow Manager.
Figure 2-182 Work Flow Manager in IBM Navigator for i
164
For more information about how to create and manage work flow in IBM Advanced Job
Scheduler for i, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasn/rzasnajsworkflowa
bout.htm?lang=en
For more information about IBM Advanced Job Scheduler for i, see the IBM i 7.2 Knowledge
Center and IBM i 7.1 Technical Overview with Technology Refresh Updates Redbooks at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasn/rzasnajsmanage.ht
m?cp=ssw_ibm_i_72%2F17-8-3-4-1&lang=en
and
http://www.redbooks.ibm.com/redbooks/pdfs/sg247858.pdf
2.8 Performance
IBM i 7.2 release provides some enhancements in performance to allow the users to monitor
and manage their systems performance easily and ensure they are keeping pace with the
changing business demands.
This section will explain about the IBM i 7.2 enhancements from performance standpoint.
2.8.1 Collection Services

There are several enhancements in Collection Services in IBM i 7.2 related to Collection
Services data files. The enhancements are as below:
Collection Services Metrics

Table 2-4 shows the changed files related to the Collection Services enhancements.
Table 2-4 Changed files for Collection Services enhancements
Changed Files
Collection Services Enhancements
QAPMJOBOS
Number of spool files created by a job

Number of jobs submitted or spawned b a job
Job level activity metrics plus connection data for server jobs
QAPMJOBMI
Activation group metrics per thread: Groups created and PGM /

SRVPGM activation created
Temporary storage metrics per job: allocated, deallocated,
max allowed, peak, current
QAPMSYSTEM
Temporary storage metrics for the system: OS, active jobs,

ended jobs
System level SQL CPU time
QAPMPOOLB
Memory usage metric enhancement to include many new metrics

along with separately reporting metrics for 4K versus 46K page
sizes.
165
Changed Files
Collection Services Enhancements
QAPMDISK
RAID 10 support: new field to indicate vel of mirrored

protection
SSDs: new DSCAT value to identify unit is an SSD
Log Sense command: new fields for counts and response
times
QAPMETHP
SR-IOV Ethernet physical ports: new file for physical Ethernet

ports of an SR-IOV adapter. (This feature is also available with
IBM i 7.1 TR 8 and PTF SI47870)
QITAMON
WRKSYSACT replaced DB CPU with SQL CPU
QAPMSQLPC
SQL plan cache collection category (*SQL) and file (QAPMSQLPC)
For supporting POWER8 Instruction Count and Virtual Time Base, new metrics such as:
QAPMJOBMI, QAPMSYSTEM, QAPMLPARJH, QAPMSYSVP have also been improved to track thread level,
system level, partition level, and processor level.
Enhanced database files to support IBM Navigator for i

To support the performance functions in IBM Navigator for i, several new files in Collection
Services are enhanced to summarize those collected data. The following are the new system
monitor files:
QAPMSMCMN
This database file contains summarized metrics from communication protocol data
(*CMNBASE collection category) that may be used in support of system monitoring.
QAPMSMDSK
This database file contains summarized metrics from disk data (*DISK collection category)
that may be used in support of system monitoring.
QAPMSMJMI
This database file contains summarized metrics from job data (*JOBMI collection
category) that may be used in support of system monitoring.
QAPMSMJOS
This database file contains summarized metrics from job data (*JOBOS collection category)
that may be used in support of system monitoring.
QAPMSMPOL
This database file contains summarized metrics from pool data (*POOL collection
QAPMSMSYS
This database file contains summarized metrics from system data (*SYSLVL collection
To produce the above files, Create Performance Data (CRTPFRDTA) command exports the data
when parameter Create standard summary data (CRTPFRSUM) parameter is set to *SYSMON or
*ALL as in Figure 2-183. Even without running monitors, users can still create those files to
view new system monitoring perspectives within Performance Data Investigator (PDI).
166
Create Performance Data (CRTPFRDTA)

From collection .
Library . . . .
To member . . . .
To library . . . .
Text 'description'
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. > Q123456789
.
QPFRDATA
. *FROMMGTCOL
. *FROMMGTCOL
.
*SAME
Name, *ACTIVE, *SELECT

Name
Name, *FROMMGTCOL
Name, *FROMMGTCOL
Categories to process . . . . . *FROMMGTCOL

+ for more values
Time interval (in minutes) . . . *FROMMGTCOL
Create standard summary data . . > *SYSMON
*FROMMGTCOL, 0.25, 0.5, 1...

*NONE, *ALL, *PFRSUM, *SYSMON
Starting date and time:

Starting date . . . . . . . .
Starting time . . . . . . . .
Date, *FROMMGTCOL
Time
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
*FROMMGTCOL
F12=Cancel
Name, *FROMMGTCOL, *APPN...
More...
Figure 2-183 CRTPFRSUM parameter in CRTPFRDTA command
For more information about performance data files, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahx/rzahxperfdatafile
s1.htm?lang=en
2.8.2 Job Watcher Metrics

Some of the database files in performance is also enhanced in IBM i 7.2. Table 2-5 shows the
list of changed files for supporting Job Watcher enhancements.
Table 2-5 Changed files for Job Watcher enhancements
Changed Files
Job Watcher enhancements
QAPYJWTDE
QAPYJWPRC
SQL Metrics
I/O counts for database, non-database, and logical
Clock time
Statements
Thread scaled and unscaled CPU
Miscellaneous information
Number of spooled files created
Number of jobs submitted
Number of job instructions changed
Wait object library
167
Changed Files
Job Watcher enhancements
QAPYJWTDE
POWER8 Instruction Count and Virtual Time Base
QAPYJWPRC
Support for temporary storage in Job Watcher collection

Support for memory usage
168
8249_Virtualization.fm
Chapter 3.
Cloud and virtualization

This chapter provides, describes, discusses, or contains the following topics:
3.1, Cloud and virtualization overview on page 170

3.2, Cloud and IBM i on page 170
3.3, IBM PowerVP Virtualization Performance on page 174
3.4, IBM i virtualization enhancements on page 176
3.5, Live Partition Mobility on page 179
3.6, Licensing and service provider accommodations on page 179
169
3.1 Cloud and virtualization overview

Many improvements and enhancements have been implemented since the first logical
partition was allowed in the IBM i family of servers. This chapter will include some of the new
options available at IBM i 7.2 running on Power Systems. Additionally, with the industry-wide
push for the cloud, this chapter will also cover things which are available to help implement
and manage IBM i in that environment.
An excellent technical summarization of virtualization relating to IBM i has been produced by
IBM Lab Services. Below is a link to the developerWorks website with a reference to this
document:
5f-41f2-b8ed-55a791b93f4f/page/IBM%20i%20Virtualization%20and%20Open%20Storage
3.2 Cloud and IBM i

Although the latest cloud enhancement on IBM i are not strictly related to the IBM i 7.2, this
section describes the most recent cloud capabilities and offerings regarding IBM i. All
currently available options provide IBM i as an infrastructure as a service (IaaS) cloud model
where IBM i partitions are infrastructure services. Currently, no cloud management,
provisioning, and automation software is supported natively on the IBM i operating system.
However, the IBM i operating system is a supported operating system on virtual machines
(VMs) that can be managed by the software products described in this section.
IBM i has been cloud-ready server platform for years with its hypervisor-managed logical
partitions and robust virtualization capabilities. Since the year 2012, when using the cloud
management software described in this section, it has been a fully cloud-enabled platform.
Note: In order to leverage current cloud capabilities on IBM Power Systems, the
environment hosting VMs has to been fully virtualized with VIOS.
3.2.1 IBM PowerVM

IBM PowerVM provides a secure and scalable server virtualization environment for AIX,
IBM i and Linux applications built upon the advanced RAS features and leading performance
of the Power Systems platform. PowerVM is a building block for all current IBM cloud on
Power solutions. Following are introduced key features of PowerVM:
Deliver services with superior economics by consolidating virtualized workloads
Deliver services built for the cloud faster by automating deployment of virtual machines
(VMs) and storage
Optimize utilization of server and storage resources to control cost and boost return on
investment (ROI)
Scale out or scale up your virtualized deployments without paying underlying performance
penalties
Eliminate scheduled downtime by deploying live mobility between servers
Deliver higher quality services by improving virtual resource management
For more information about IBM PowerVM, see:
http://www-03.ibm.com/systems/power/software/virtualization/index.html
170
3.2.2 OpenStack
OpenStack is a global collaboration of developers and cloud computing technologists working
to produce an ubiquitous Infrastructure as a Service (IaaS) open source cloud computing
platform for public and private clouds. OpenStack provides open source software for creating
and managing private and public cloud environments. The software provides tools and
standards required to mange storage, processor, and network resources which compose
cloud solution. IBM, among other entities, has been a key player in developing the OpenStack
software.
OpenStack is a building block for IBM PowerVC software and other cloud solutions, described
in following sections of this publication.
For more information about OpenStack, see OpenStack website at:
http://www.openstack.org/
3.2.3 IBM PowerVC

IBM Power Virtualization Center (PowerVC) is an advanced virtualization management
offering, built on OpenStack, that provides simplified virtualization management for IBM AIX,
IBM i and Linux virtual machines (VMs) running on IBM Power Systems. PowerVC is
designed to improve administrator productivity and simplify the management of VMs and
LPARs on Power Systems servers. PowerVC provides the foundation for Power Systems
scalable cloud management, including integration to higher-level cloud managers based on
OpenStack technology. After registering resources within PowerVC, following capabilities are
available:
Creating virtual machines by deploying images and then resize and attach volumes to
them.
Importing existing virtual machines and volumes so they can be managed by PowerVC.
Monitoring the utilization of the resources that are utilized in the environment.
Migrating virtual machines while they are running (Live Partition Mobility).
Capturing a virtual machine that is configured for later deployment elsewhere in the
environment.
Deploying images quickly to create new virtual machines in response to changing
business needs.
Automatically deploying or migrating virtual machines based on the specified criteria.
PowerVC is a building block for IBM SmartCloud Entry for Power Systems cloud solution (for
details see section 3.2.4, IBM SmartCloud Entry for Power Systems on page 172 of this
publication).
At the time of writing this publication the latest available version of the PowerVC is 1.2.1.
For detailed hardware and software requirements for PowerVC, see following website at:
http://www-01.ibm.com/support/knowledgecenter/api/content/SSXK2N_1.2.1/com.ibm.pow
ervc.standard.help.doc/powervc_hwandsw_reqs_hmc.html
Note: IBM PowerVC is meant to replace IBM Systems Director VMControl tool. There is
no migration support of IBM Systems Director VMControl installation to the new PowerVC
configuration.
Chapter 3. Cloud and virtualization
171
For more information about PowerVC, see IBM Power Virtualization Center Standard
documentation at:
http://www-01.ibm.com/support/knowledgecenter/api/content/SSXK2N_1.2.1/com.ibm.pow
ervc.standard.help.doc/kc_welcome-standard-supermap.html?locale=en&ro=kcUI
And IBM Power VC - Virtualization Center website at:
http://www-03.ibm.com/systems/power/software/virtualization-management/index.html
3.2.4 IBM SmartCloud Entry for Power Systems

IBM SmartCloud Entry for Power Systems has evolved to IBM Cloud Manager with
OpenStack which is described in section 3.2.5, IBM Cloud Manager with OpenStack on
page 172. The latest, and last, available version of IBM SmartCloud Entry for Power Systems
is 3.2.
Documentation for IBM SmartCloud Entry has been merged with documentation for IBM
Cloud Manager with OpenStack, and is available at:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W21ed5ba0f4
a9_46f4_9626_24cbbb86fbb9/page/Documentation
For more information about IBM SmartCloud Entry for Power Systems, see following website
at:
http://www-03.ibm.com/systems/power/solutions/cloud/smartcloudentry/
3.2.5 IBM Cloud Manager with OpenStack

IBM Cloud Manager with OpenStack is a robust Infrastructure as a Service software offering
that simplifies management of a virtualized environment which has been driven from IBM
SmartCloud Entry product. It helps to convert virtualized environments to a cloud quickly and
easily. Users can request and provision an environment quickly through an easy-to-use
web-based interface. IT managers can monitor and manage this environment for improved
efficiency and utilization of data center resources. The IBM Cloud Manager with OpenStack
includes heterogeneous server architecture support from a single user interface. This gives
you the flexibility to manage IBM Power System, System x, IBM BladeCenter, IBM NeXtScale
System, IBM Flex System and PureFlex System platforms with a single, consolidated image
of IBM Cloud Manager with OpenStack software. IBM Cloud Manager with OpenStack
supports multiple virtualization environments, including VMware, Hyper-V and KVM as well
as IBM PowerVM and IBM z/VM environments. Following are capabilities of the IBM Cloud
Manager with OpenStack:
Managing images:
Easily create new golden master images and software appliances using corporate
standard operating systems.
Convert images from physical systems or between various x86 hypervisors.
Reliably track images to ensure compliance and minimize security risks.
Optimize resources, reducing the number of virtualized images and the storage
required for them.
Deploying virtual machines (VMs):
Deploy application images across compute and storage resources.
End user self-service for improved responsiveness.
Enable security through VM isolation, project-level user access controls.
Easy to useno need to know all the details of the infrastructure
172
Investment protection from full support of existing virtualized environments

Operating a cloud:
Delegate provisioning to authorized users to improve productivity.
Maintain full oversight to ensure an optimally running and safe Cloud through
automated approval/rejection.
Built-in workload metering delivers the foundation for pay-per-use model.
Standardize deployment and configuration to improve compliance and reduce errors by
setting policies, defaults and templates.
Simplify administration with an intuitive interface for managing projects, users,
workloads, resources, billing, approvals and metering.
Integrated platform management allows easy transition between physical/virtual
resource views to facilitate diagnosis and maintenance.
Manage automated approvals, metering, billing, users and projects through a single
pane of glass.
The latest available version is IBM Cloud Manager with OpenStack version 4.2 (Juno).
For detailed hardware and software requirements for IBM Cloud Manager with OpenStack,
see IBM Cloud Manager with OpenStack documentation website at:<< the documentation is
not available yet, but will be at the time the book is published>>
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W21ed5ba0f4
a9_46f4_9626_24cbbb86fbb9/page/Documentation
For more information about IBM Cloud Manager with OpenStack, see IBM Cloud Manager
with OpenStack website at:
http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/877/ENUSZ
P14-0482/index.html&lang=en&request_locale=en#h2-keyprx
and:
http://www-03.ibm.com/systems/x/solutions/cloud/cloud-manager-openstack/
3.2.6 IBM Power Systems Solution Edition for Cloud

IBM Power Systems Solution Edition for Cloud is a pre-built and pre-installed solution of
hardware, software, and implementation services for private cloud implementations. The IBM
Power Systems Solution Edition for Cloud helps speed up and simplify the deployment of a
cloud with OpenStack based cloud management software delivered on a ready to use
appliance. The Solution Edition is easy to order, includes configurable hardware choices to
address customer needs and preferences. Building on IBM PowerVM virtualization and IBM
PowerVC management, the Solution Edition for Cloud provides cloud capabilities based on a
flexible and extensible OpenStack platform with fast and automated installation, an intuitive
and easy to use interface, automated deployment, image management, workload metering,
and the self-service features of cloud.
For more information about IBM Power Systems Solution Edition for Cloud, see IBM Power
System Solution Edition for Cloud website at:
http://www-03.ibm.com/systems/power/hardware/solutioneditions/cloud/
For more information about Cloud on Power Systems, see following website at:
http://www-03.ibm.com/systems/power/solutions/cloud/resources.html
173
3.2.7 IBM i cloud offering summary

For the environments where just VM management, deployment, and migration is a case,
PowerVC would be sufficient in most cases. It is also required step and starting point for
leveraging robust cloud capabilities with IBM Could Manager with OpenStack. IBM Cloud
Manager with OpenStack provides the most comprehensive capabilities including automated
cloud service management process, cloud oversight, workload metering, billing, and much
more. Using IBM Cloud Manager with OpenStack requires skilled professionals for
implementation and operation. If this is a problem or low time-to-market (TTM) factor is a key
than, the best option would be IBM Power Systems Solution Edition for Cloud, a pre-installed,
pre-configured appliance based on the customers needs. It can also came with optional
implementation services.
3.3 IBM PowerVP Virtualization Performance

IBM Power Virtualization Performance (PowerVP) for Power Systems is a licensed program
that provides a performance view into the PowerVM virtualized environment. PowerVP
displays graphically the utilization of individual cores and their mapping to Logical Partitions
on a Power Systems in real time. The dashboard view of PowerVP gives a simple to
understand snapshot of resource usage that can be used by system administrators to
understand resource usage by different applications that run on Logical Partitions.
Customers who are using Power Systems in Cloud computing with large and small
enterprises with PowerVM features now can use PowerVP to understand resource distribution
among the virtual workloads and plan for business demands.
PowerVP collects performance data directly from the Hypervisor, which offers the most
accurate performance information about logical partitions that are running on IBM Power
Systems. This performance information is then displayed on a real-time, continuous graphical
dashboard. Data collection is available for historical review.
The product can also be used along with existing operating system performance utilities to
identify performance bottlenecks on Power Systems. System administrators can use
PowerVP to diagnose resource contention issues quickly.
3.3.1 PowerVP components

The architecture of PowerVP includes components that interact with the PowerVM
Hypervisor, operating system, a Graphical User Interface (GUI), and a Java JAR file that is
used for data recording without the use of the GUI.
.Following list contains components of the PowerVP:
System level agent - a central point to collect system-wide resource utilization data
Partition level agent - collects partition resource utilization data and interacts with System
level agent
Graphical user interface - a Java based application that connects to System level agent
and displays PowerVP dashboard
Background recorder - a Java based application used to collect system level resource
utilization data without GUI.
174
Figure 3-1 shows a high-level architecture of PowerVP. It displays the data flow between the
components of PowerVP and PowerVM.
Client GUI
VIOS
AIX
System Agent
Linux
IBM i
Partition Agent
Partition Agent
OS Interface
PHYP
Interface
OS Interface
Partition Agent
OS Interface
POWER Hypervisor
Core HPMCs (CEC level)
Thread PMUs (Partition Level)
Chip PMUlets (CEC level)
Figure 3-1 PowerVP architecture showing system agents communicating with the GUI
3.3.2 PowerVP GUI

System and partition resource utilization data collected by the agents is accessed and
displayed on the GUI. Dashboard allows a user to access system wide performance data as
well as for particular VM and than drill down to get detailed view of it. It also allows to record
and play back performance metrics on the workstation where the GUI runs. Sample PowerVP
CPU resource affinity view is shown on Figure 3-2 on page 176.
175
Figure 3-2 Sample PowerVP CPU affinity view.
For further information about PowerVP implementation in an IBM i environment, see the IBM
Redpaper publication IBM PowerVP Introduction and Technical Overview, REDP-5112-00.
3.4 IBM i virtualization enhancements

Many new features were added at IBM i 7.2. These enhancements relate to iVirtualization as
well as non-hosted partitions and virtualization using VIOS.
Terminology reminder: When referring to an IBM i partition hosting another IBM i
instance, this is known as iVirtualization.
For an overview of various IBM i virtualization methods and helpful tips, see the "IBM i
Virtualization and Open Storage (read-me first)" document located at:
5f-41f2-b8ed-55a791b93f4f/page/IBM%20i%20Virtualization%20and%20Open%20Storage
3.4.1 Virtual Partition Manager adds GUI to IBM Navigator for i

IBM Navigator for i provides a graphical interface for Virtual Partition Manager. To create a
new logical partition using IBM Navigator for i, follow these steps:
1. In IBM Navigator for i navigation area, expand Configuration and Services.
176
2. Select Create Partition to start the wizard.

3. Follow the steps within the wizard to create IBM i or Linux partition.
Note: You can not use Virtual Partition Manager on an IBM i server that is configured using
an HMC. You can only use Virtual Partition Manager on the hosting IBM i partition.
PowerVM Standard or Enterprise edition is required to support up to four client partitions
using VPM.
3.4.2 iVirtualization release support

Various releases of IBM i running on Power Systems support hosting of other releases. See
Table 3-1 for a list of supported combinations when using iVirtualization.
Table 3-1 Supported iVirtualization combinations
Processor family
Host IBM i versions
Client IBM i versions
POWER5
Not available
Not available
POWER6
6.1, 7.1, 7.2
6.1, 7.1, 7.2
POWER7
6.1, 7.1, 7.2
6.1, 7.1, 7.2
POWER8
7.1, 7.2
7.1, 7.2
Note: Machine code release 6.1.1 is required for any host or client at version 6.1 of IBM i.
IBM i 7.1 and 7.2 will require certain technology refresh levels based upon the hardware on
which the partitions are running.
3.4.3 Utilizing SSDs for network storage spaces

Using the command for creation of network server storage spaces (CRTNWSSTG), affinity for
solid-state disk for iVirtualization partitions - as well as anything else using a network storage
space - can be selected. See Figure 3-3 on page 178 for an example of how to create a new
storage space and set its preference for SSD using the preferred storage unit parameter.
177

Size . . . . . . . . .
Format . . . . . . . .
space
. . .
. . .
. . .
ID .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
> NEW001
> 100000
*NONE
> *OPEN
1
Name
*CALC, 1-1024000 megabytes
Name, *NONE
*NTFS, *OPEN, *REFS...
1-255
Name
> 'Storage space which should go to SSD'
Data offset . . . . . . . .
.
.
.
.
.
*FORMAT
.
512
. > *SSD
.
9
*FORMAT, *ALIGNLGLPTN...
512, 4096
*ANY, *SSD
1, 2, 3, 4, 5, 6, 7, 8, 9
Figure 3-3 Creating a new network storage space with a preferred storage unit of *SSD
3.4.4 Support of additional disks attached via VSCSI

At IBM i 7.2, 32 virtual disks can now be attached via a VSCSI link, where the prior limitation
was 16. This allows for a potentially less-complex setup and easier expansion of an existing
environment when needed.
3.4.5 Less-complex assignment of tape and optical resources

In previous releases, all optical and tape devices were available to client partitions when
using iVirtualization unless they were restricted individually in the network server description.
When running IBM i 7.2 as the host, a new parameter on the Create Network Server
Description and Change Network Server Description commands are available to specify only
the devices which are allowed. This can be of great assistance on environments with a
significant quantity of optical and tape resources.
Note: You cannot specify resources on the allowed and restricted lists at the same time - if
resources are being specifically allowed, the restricted resources must be *NONE. If
resources are being restricted, the allowed resources must be *UNRSTD. See the
command help text for further detail on this requirement.
3.4.6 Define system resource usage during storage space creation

On systems running IBM i 7.2, a new parameter has been added to the Create Network
Server Storage Space and Change Network Server Storage Space commands. The
parameter is Resource Allocation Priority (RSCALCPTY) and allows the process to use a
variable amount of system resources during creation of the storage space.
In the past, creation of the storage space attempted to use as much system resource as
possible and could potentially affect other processes on the system in a negative manner.
178
This new parameter enables the user to modify the create priority to reduce the chance of
significant delays to other jobs on the system.
The parameter can accept values from 1 to 9, with 9 being the maximum and 1 being the
minimum. Setting the value to the default of 9 will create the storage space in a manner equal
to prior release behaviors. Modifying the value from 9 to any other setting will reduce the
resources used during creation.
Note: Setting a lower priority can reduce server resource utilization, but ultimately will
cause the creation of the storage space to take a longer amount of time.
3.5 Live Partition Mobility

Live Partition Mobility (LPM) is part of the base functionality of IBM i 7.2.
With the release of IBM i 7.2 with Technology Refresh 1, a customer can migrate from a
POWER7 or POWER7+ system to all POWER8 systems with no downtime - simply perform a
move with LPM and accommodate for licensing changes on the new server.
Note: For partitions running IBM i 7.2, Technology Refresh 1 is required for Live Partition
Mobility to or from POWER8 systems.
LPM is the recommended no downtime maintenance strategy for IBM i customers running
on POWER8 Enterprise servers. There is no longer any option for CEC Hot Add Repair
Maintenance (CHARM) on the POWER8 Enterprise systems, so certain maintenance items
which may have been concurrent in the past will now require a CEC outage to perform.
To ensure the most stability when using LPM, it is a good idea to review firmware and OS
updates for the CEC, HMC, and IBM i environment. Specific fixes may be released which are
necessary to ensure a stable and seamless transition among CECs.
Remember: Live Partition Mobility requires that all resources allocated to the mobile
partition are virtual. The partition can own no physical hardware if it is to be mobile.
LPM with IBM i is discussed in great detail in the Redbook publication IBM PowerVM
Virtualization Introduction and Configuration.
http://www.redbooks.ibm.com/abstracts/sg247940.html
3.6 Licensing and service provider accommodations

Ever since the release of the Power Systems servers, impressive advances have been made
in relation to performance and virtualization. At the same time, businesses are constantly
striving to streamline operations and utilize their servers in the most cost-effective manner.
Certain systems are available from IBM pre-configured in a manner to better support a cloud
infrastructure. See the link below for more information about Power Systems solution editions
optimized for cloud.
http://www-03.ibm.com/systems/power/hardware/solutioneditions/cloud/
179
The IBM i operating system is also positioned strategically for implementation in cloud.
Advances in virtualization and tape technologies have made it much easier to migrate
environments from an on-premise system to a remote location. Additionally, IBM has multiple
offerings for both customers and Managed Service Providers to help defray some costs
during a migration to a new operating environment.
See the link below for information on these and more benefits available to support cloud
services on Power Systems.
http://www-03.ibm.com/systems/power/hardware/solutioneditions/service-providers/so
lutions.html
180
8249_Security.fm
Chapter 4.
Security
With the announcement of IBM i 7.2, this new release of IBM i provides significant new
security as well as enhancing many other integrated components and licensed programs. The
following topics are covered in this chapter:
4.1, Single Sign-on

4.2, Password Rule & User Profile Enhancements on page 183
4.3, Intrusion Detection/Prevention on page 184
4.4, Intrusion Detection Implementation on page 186
4.5, IM Audit record detail on page 186
4.6, Cryptographic enhancements on page 187
4.7, Cryptography for SSL and TLS on page 190
4.8, DB2 Security on page 195
4.9, Networking security refrence on page 196
New functions in the integrated IBM i security enable SSO between a Kerberos-enabled FTP
client and an IBM i FTP server and between a Kerberos-enabled Telnet client and an IBM i
Telnet server. This opens the door for more applications to participate in a single sign-on
environment.
181
8249_Security.fm
4.1 Single Sign-on

Added support to use Kerberos ticket for automatic sign-on.
Enhance both FTP server and TELNET server to support authenticating with Kerberos
(SSO)
Kerberos authentication and Enterprise Identity Mapping integrated in FTP & TELNET
Integrates into the IBM i SSO application suite
FTP client and server support
Telnet client and server support (server support introduced Version 5 of IBM i5/OS,
Telnet client support is introduced in IBM I 7.2)
Start TCP/IP TELNET (STRTCPTELN)

ASCII full screen options . . .
+ for more values
Display character attributes . .
ASCII page scroll feature . . .
ASCII answerback feature . . . .
ASCII tab stops . . . . . . . .
+ for more values
Coded character set identifier
ASCII operating mode ID . . . .
Remote virtual display . . . . .
Remote user . . . . . . . . . .
Remote password . . . . . . . .
*MULTINAT
*VT220B7
*DFT
*NONE
*NONE
1-65533, *MULTINAT...
*VT220B7, *VT220B8, *VT100...
Name, *DFT
Name, *NONE, *KERBEROS...
Remote password encryption . . .

Remote initial program . . . . .
*DES7
*RMTUSRPRF
F3=Exit F4=Prompt
F24=More keys
F12=Cancel
*DES7, *SHA1, *NONE

Name, *RMTUSRPRF, *NONE
More...
F5=Refresh
*NONE
*NONE, *ALL, *LOCALECHO...
*YES
*NO
*NONE
*DFT
*NO, *YES
*NO, *YES
0-133, *DFT, *NONE
Figure 4-1 STRTCPTELN F4 (Prompt) or TELNET F4 (Prompt)
182
8249_Security.fm
FTP client command
Start TCP/IP File Transfer (FTP)

Remote system . . . . . . . . .
Internet address . . . . . . . .
Coded character set identifier
*DFT
1-65533, *DFT
Port . . . . . . . . . . . . . . *DFT
1-65535, *DFT, *SECURE
Secure connection . . . . . . . *DFT
*DFT, *NONE, *SSL...
NOTE: F4 (Prompt) *IMPLICIT, *KERBEROS
Data protection . . . . . . . . *DFT
*DFT, *CLEAR, *SAFE, *PRIVATE
Outgoing EBCDIC/ASCII table . .
Library . . . . . . . . . . .
*CCSID
F3=Exit F4=Prompt
F24=More keys
F12=Cancel
F5=Refresh
Name, *CCSID, *DFT

Name, *LIBL, *CURLIB
More...
Figure 4-2 FTP F4 (Prompt)
Read about new or significantly changed information for the Telnet topic collection
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaiw/rzaiwrzaiwwhatsne
w.htm?lang=en
For more information related to related to creating a single sign-on test environment,
reference IBM i 7.2 Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzamz/rzamz
enablesso.htm
Securing FTP with Kerberos authentication. With Kerberos authentication you can eliminate
the exposure of transmitting passwords and data in the clear when using the File Transfer
Protocol (FTP) server with an FTP client that also uses Kerberos authentication. Besides the
Kerberized FTP server, with Enterprise Identity Mapping, is able to support a single sign on
environment. For more information reference Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzaiq/rzaiq
kerberos.htm?locale=en&ro=kcUI
4.2 Password Rule & User Profile Enhancements

New system values supported
QPWDRULES, define new password rules
QPWDEXPWRN, define password expired warning interval
QPWDCHGBLK, prevent passwords from being changed repeatedly
Chapter 4. Security
183
8249_Security.fm
Changed system value

QLMTDEVSSN, Limit device sessions (*NONE, 1-9 sessions)
Changed/New user profile parameters
LMTDEVSSN, Limit device sessions (1-9 sessions)
PWDCHGBLK - Block password change (1-99 hours)
4.3 Intrusion Detection/Prevention

While IDS is active, it reports the suspected intrusions and extrusions that are defined by the
enabled IDS policies. The production and service stacks detect these intrusions and
extrusions. When an intrusion or extrusion event occurs that exceeds user-defined or default
thresholds, IDS writes an intrusion monitor record to the audit journal, and optionally sends a
notification to a message queue and e-mail message. For more information about IDS
support on IBM i, go to the following website:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaub/rzaubidsoperation
.htm?lang=en
Real time notification enablement
E-mail, messages, etc. (i.e., pagers, ISV solutions) in addition to IM records
Intrusion events detected/audited W
Well-known attacks such as Smurf, Fraggle, ACK storms, Address Poisoning (both
IPv4 ARP poisoning, and IPv6 neighbor discovery poisoning), Ping-Of-Death, etc.
Extrusions detected attacks, scans, traffic regulation anomalies initiating from your IBM
i server
IPv4 & IPv6 support
GUI
Management of IDS policies
Display of intrusion events as an alternative to viewing the audit journal
184
8249_Security.fm
Figure 4-3 iNav GUI interface for configuration IDS policies
Figure 4-4 iNav GUI interface for configuration - Notification
Chapter 4. Security
185
8249_Security.fm
4.4 Intrusion Detection Implementation

Intrusion Detection System (IDS) behavior defined as policies in a policy file
Audit events logged to the security audit journal
When Intrusion detected, logged in message queue and e-mail
Figure 4-5 Intrusion Detection Implementation
4.5 IM Audit record detail

The Intrusion Detection section in the Information Center contains information about the
format of an IM entry type journal record.
Table 4-1 Format of an IM entry type journal record.
186
Journal value
Meaning
Potential intrusion event detected.
2006-01-11-13.19.42.329688
Timestamp (11 Jan 2006, 13:19:42.329688)
1107
Detection point identifier
02
Local address family
119
Local port number
9.5.92.48
Local IP address associated with the detected event.
02
Remote address family
3511
Remote port number
9.5.92.102
Remote IP address associated with the detected event.
SCANE
Probe type identifier (SCANE = Scan Event)
0020
Unique identifier for this specific intrusion event. You can use
this identifier to correlate this audit record with other intrusion
detection information.
8249_Security.fm
4.6 Cryptographic enhancements

In IBM i 7.2, POWER 8 vector instructions can be used to improve the performance of
cryptographic operations. In particular, Advanced Encryption Standard (AES) encryption and
decryption performance for Electronic codebook (ECB) and Cipher-block chaining (CBC)
modes will be improved. This improvement is utilized by the internal software cryptographic
library, and will therefore be automatically utilized for the particular cryptograhpic algorithms
in cryptographic services APIs and other system provided encryption funtionality. Use of
vector instructions will not be directly available, such as through the use of a new hardware
provider, via cryptographic services APIs. However, PASE for i applications running on these
can use VSX instructions. This functionality can be unlocked when SLIC PTF MF58198 has
been applied.
Power 8 in-core Cryptographic Performance Acceleration:
Support within the processor itself, no additional products or HW required
Automatic performance acceleration for certain cryptographic algorithms

AES & SHA-2 message digest
Does not support cryptographic key storage
Certain customers will still need the HW Cryptographic Coprocessor Card
Performance gains will be realized in support such as:

Customer applications that use the Crypto Services APIs
SSL (Secure Socket Layer)
VPN (Virtual Private Network)
Software Tape Encryption
4.6.1 Vector Scalar eXtension and crypto acceleration

POWER8 features enhanced Vector Scalar eXtension (VSX) capabilities, including new
instructions to accelerate some frequently used cryptographic operations. VSX in Power
Systems provides support for vector and scalar binary floating point operations conforming to
the Institute of Electrical and Electronics Engineers Standard for Floating Point Arithmetic
(IEEE-754). VSX can be used to increase parallelism by providing single-instruction,
multiple-data (SIMD) execution functionality for floating point double-precision operations,
greatly improving the performance of some applications. IBM i Portable Application Solutions
Environment (PASE) applications running on IBM i 7.2 with POWER8 processors can now
take advantage of VSX. IBM i 7.2 leverages the enhanced POWER8 vector processing
capabilities to accelerate AES cryptographic operations when operating in the POWER8
processor compatibility mode. Cryptographic services APIs, SSL, VPN, Backup Recovery
and Media Services (BRMS) tape encryption, and SQL encryption functions automatically
use POWER8 enhanced vector processing capabilities to deliver significant increases in
performance. Figure 2 exemplifies the gains resulting from POWER8 cryptographic
acceleration. Additional information is available at developerWorks:
http://www.ibm.com/developerworks/ibmi/library/i-ibmi-7_2-and-ibm-power8/
4.6.2 Cryptographic Key Protection - Terminology

A data encryption key should be well protected or data is exposed
Used to encrypt data (SSNs, credit card numbers, etc.)
Chapter 4. Security
187
8249_Security.fm
It is recommended to encrypt the data key with a key encrypting key (KEK)
Used to encrypt data encryption keys
A Master Key can then be used to encrypt all KEKs
The master key is used to encrypt KEKs or Data Encryption Keys
Top level key, in the clear! If master key is compromised, data is compromised
How do you securely store this master key? Refer to Figure 4-6 on page 188
Figure 4-6 How do you securely store this master key
4.6.3 Crypto Key Management Enhancements

GUI & CL interface to manage master keys
GUI and CL commands to manage master keys
GUI & CL interface to manage i/OS keystore and keys
GUI and CL commands to manage key store files
Create key store files
Create encryption keys
Create Master Key(s) via Navigator

Navigate to Security / Cryptographic Services Key Management / Master Keys. Refer to
Figure 4-7 on page 188
Figure 4-7 Manage Master Keys
188
8249_Security.fm
Note: The SAVRST Master Key is not yet set in the example above. A default key is in
place to provide minimal protection until you set your key. This means that the master keys
are not in the clear on your SAVSYS tape, but any IBM i system can decrypt them.
Key Store Enhancements

Key stores protected by master keys
Cryptographic Services APIs used to manage key stores
A single key store file can be encrypted under one master key
One master key can encrypt multiple key store files
KEKs and data keys are stored in the key store file
Key store is a database file
normal file access methods disabled
Figure 4-8 Key Store
Create Key Store Files via Navigator (6.1)

Navigate to Security / Cryptographic Services Key Management / Keystores. Use Create
New Keystore to create file and New Key Record Wizard to add encryption key entries.
Figure 4-9 Create Key Store Files via Navigator (6.1)
Chapter 4. Security
189
8249_Security.fm
Note: Q1AKEYFILE in QUSRBRM is for BRMS tape encryption. Application keystore files
can be assigned any file name.
4.7 Cryptography for SSL and TLS

This section describes the enhancements of crypthography, system values related to
cryptography, Digital Certificate Manager, and so on.
The following are covered in more detail in this section:
4.7.1, Default value for QSSLPCL system value

4.7.2, Cipher specification list changes on page 191
4.7.3, Elliptic Curve Cryptography on page 191
4.7.4, Multiple server certificates on page 192
4.7.5, Signature and hash algorithms on page 195
4.7.1 Default value for QSSLPCL system value

The secure sockets layer protocols system value, QSSLPCL, controls the TLS versions
supported by System SSL, with the special value *OPSYS indicating the default behavior. In
IBM i 7.2, the TLSv1.2 and TLSv1.1 protocols are on and SSLv3 is off by default. Changing
the setting for QSSLPCL or the value of *OPSYS influences every System SSL consuming
application on the system.
When migrating from an earlier release, a user defined QSSLPCL value is retained,
preventing the new default behavior for this release from being in effect. In this case, after the
migration, the system administrator can set QSSLPCL to *OPSYS if its definition for the
release meets their security policy requirements.
Following are the QSSLPCL *OPSYS definitions by release:
IBM i 7.2: *TLSV1.2, *TLSV1.1, and *TLSV1
IBM i 7.1: *TLSV1 and *SSLV3
Disabling SSLv3 in the default configuration reflects the security community's position that
SSLv3 should no longer be used. The reality is that some old devices or applications used in
production environments are still dependent on this deprecated protocol version. If such a
device must continue to use SSLv3 with the 7.2 partition, the administrator must update
QSSLPCL to once again include *SSLV3.
When *SSLV3 is included in QSSLPCL, SSLv3 is added to the default protocols used by a
majority of applications. In this case SSLv3 use should be restricted to the one application
that needs it to limit the exposure. Unfortunately, this means that all applications using the
default protocols must have it individually turned off to prevent its use. For the core IBM
networking applications, this can be controlled using the Digital Certificate Manager (DCM)
Application Definition. If SSLv3 is re-enabled, create an action plan to eliminate the external
dependency on SSLv3 so it can be turned off again.
IBM i 7.2 enables TLSv1.2 and TLSv1.1 under the covers for applications coded to use
TLSv1.0. This is due to the focus on improving the default security position without requiring
client intervention. The possibility exists that an application's internal code will not tolerate
negotiation of a new protocol it does not know about. In this situation the mitigation is to turn
off the new protocols at the application layer if possible. This is accomplished through
190
8249_Security.fm
changing the application definition in DCM or by changing the application code to explicitly
turn off TLSv1.2. The last option is to disable TLSv1.2 with QSSLPCL for the entire system
until the application can be updated to tolerate TLSv1.2.
4.7.2 Cipher specification list changes

The secure sockets layer cipher specification list system value, QSSLCSLCTL, determines
who controls the values in system value QSSLCSL. The *OPSYS value indicates the
operating system determines the list and the *USRDFN value indicates the system
administrator controls the QSSLCSL values.
The new definition of the cipher suite list in QSSLCSL, when QSSLCSLCTL is set to
*OPSYS, also has an impact to clients. QSSLCSL governs both the supported and default
cipher suites. IBM i 7.2 *OPSYS introduces over a dozen new cipher suites for the first time.
The default cipher suites are a release restricted subset of the supported cipher suites. Some
cipher suites previously in the restricted default subset have been removed from the subset.
The order of some suites in the default subset has also changed which can impact which
cipher suite is negotiated.
For more information, see, Default cipher specification list on page 193
4.7.3 Elliptic Curve Cryptography

Elliptic Curve Cryptography (ECC) is a new function available for the first time with IBM i 7.2.
ECC is an asymmetric encryption algorithm and in simplistic terms it is similar to RSA. One
the attributes of ECC is that it has smaller key sizes than RSA to obtain the same strength.
ECC encompasses many different elliptic curve types, families, and strengths.
System SSL and DCM support five named elliptic curves referred to as the following:
Secp521r1
Secp384r1
Secp256r1
Secp224r1
Secp192r1
All five of the named curves are enabled by default. System SSL support for one or more of
the named curves can be disabled at the system level using the System Service Tools
advanced analysis SSLCONFIG command.
As it relates to TLS, there are two components to ECC. The first part of ECC is Elliptic Curve
Digital Signature Algorithm (ECDSA) certificates. These certificates use ECDSA for the key
type rather than RSA. The second part is the Elliptic Curve Diffie-Hellman Ephemeral
(ECDHE) key exchange. The ephemeral part means that a key associated with a certificate is
not used but rather new anonymous key pairs are used for each handshake.
ECDHE does not use the key in the certificate, so it works with both RSA and ECDSA
certificates. The keyword ECDHE in a cipher suite name indicates ECDHE is used for the key
exchange. The keywords RSA or ECDSA in the cipher suite indicate which certificate type to
use. If ECDHE is not in the cipher suite name, this means there is an unwritten RSA keyword
to indicate RSA key exchange. RSA key exchange uses the key from the RSA certificate and
therefore it does not work with ECDSA certificates. ECDSA certificates can only be used with
ECDHE key exchange.
Chapter 4. Security
191
8249_Security.fm
The transition to ECDHE for the key exchange in TLS connections is painless. It requires that
each side support the same ECDHE cipher suite and has one supported named curve in
common. The server's ordered cipher suite list also must prefer the ECDHE cipher suite over
any RSA key exchange cipher suites for it to be selected.
The transition to ECDSA is more complicated since in addition to the ECDHE requirements,
ECDSA requires a new certificate be generated and assigned to the application. A server
application can not migrate from RSA certificates to ECDSA certificates until all of its potential
clients are able to negotiate ECDSA and ECDHE cipher suites. This is a long term
consideration when negotiating with previous IBM i releases that do not support ECC.
4.7.4 Multiple server certificates

To assist with the interoperability issues of transitioning to ECDSA certificates, IBM i 7.2
server applications can now have multiple server certificates assigned at one time. The new
multiple certificates infrastructure supports up to four concurrent certificates, although two
certificates will be typical. An administrator rolling out the use of ECDSA would assign both
an RSA certificate and an ECDSA certificate to the server configuration.
Servers with a DCM application definition use the DCM Update Certificate Assignment panel
to assign multiple certificate labels. GSKit based servers can configure multiple certificate
labels to be used by setting the GSK_KEYRING_LABEL_EX attribute.
The Telnet server's DCM Update Certificate Assignment panel is shown in Figure 4-10. Telnet
currently has one certificate assigned, although the four certificates with the check mark next
to the label names are about to be assigned instead.
Note: Assigning two or more certificates that have the exact same cryptographic
properties adds unnecessary processing as only the first one as determined internally will
ever be selected.
The certificate selected for a secure connection is determined by the server configuration
paired with each client's advertised capabilities. The certificate selection logic is deterministic
and is described in detail in the Multiple Certificate Selection topic of the IBM i 7.2 Knowledge
Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzain/rzainmultcert.htm
?cp=ssw_ibm_i_72
192
8249_Security.fm
Figure 4-10 Digital certificate manager, updating certificate assignments
DCM local certificate authority (CA)

IBM i 7.2 DCM supports creating ECDSA local CAs and ECDSA certificates. Multiple local
certificate authority (CAs) can exist on the same partition and which one signs a new
certificate is selected when it is created.
A RSA server certificate can be signed by an ECDSA CA and vise-versa. An early phase of
the roll out of ECDSA could include signing an ECDSA server certificate with an existing RSA
local CA. The peer clients (user PCs) trust the new certificate chain since they already trust
the root RSA local CA. Otherwise the new ECDSA local CA must be distributed to all the
peers so they can trust a pure ECDSA certificate chain.
Default cipher specification list

As mentioned in 4.7.3, Elliptic Curve Cryptography on page 191, the list of values for the
QSSLCSL system value when QSSLCSLCTL is *OPSYS has changed in IBM i 7.2.
The default cipher suites for each release are shown in Figure 4-11 as the shaded values. A
system administrator can alter the default list for the system in two ways:
If a default cipher suite is removed from the list completely, it is no longer supported,
thereby removing it from the default list at the same time.
For the default cipher suites, the order they appear in the list is the order they are preferred
by server applications. By rearranging the order in QSSLCSL, the order is changed for all
applications using the default list.
Chapter 4. Security
193
8249_Security.fm
Figure 4-11 Default cipher suites for IBM i 7.2 and 7.1
As shown in Figure 4-11, four new ECDHE_ECDSA_AES based cipher suites are positioned
first. This is the first time a new cipher suite has been added to the top position in the list. This
positioning is due to this set of cipher suites remaining dormant for a server until the
administrator assigns an ECDSA certificate. If an administrator goes to the effort to configure
ECDSA, it is assumed they would like it to be used whenever possible.
Since ECDHE requires no explicit configuration, the ECDHE_RSA_AES based cipher suites
are positioned after the RSA_AES set. This is to prevent a new (to System SSL) cipher suite
from being the primary cipher suite used by the majority of server applications without
administrator action.
When migrating from an earlier release, a user defined QSSLCSL value is retained
preventing the new cipher suites from being supported. In that case after the migration, the
system administrator can set QSSLCSLCTL to *OPSYS to have QSSLCSL primed with the
new list. Working with the full list, the administrator can then modify the list as needed to meet
their security requirements.
194
8249_Security.fm
4.7.5 Signature and hash algorithms

The TLSv1.2 protocol made the signature algorithm and the hash algorithm used for digital
signatures an independent attribute. In previous protocol versions the negotiated cipher suite
and certificate determined these algorithms.
System SSL has a default ordered list of allowed signature/hash algorithm pairs. The list
serves two purposes for TLSv1.2 and has no meaning for prior protocols:
The first use is that the ordered signature algorithm list is sent to the peer when System
SSL requests a certificate during the handshake. The peer uses the received list to guide
its certificate selection process when it has more than one certificate to pick from.
The second use is that the list of algorithm pairs restricts which signature and hash
algorithms can be used for handshake message signatures. A TLSv1.2 handshake
message signature algorithm can be different from the signature algorithm of the
certificate that is used for the session. For example, the handshake message can be
protected by SHA512 even though a MD5 certificate is selected for the session. This
increases the security attributes of the handshake without requiring a new certificate.
There are two methods of setting this list for an application:
Applications with a DCM application definition can use the DCM Update Application
Definition panel to configure the list.
GSKit based applications can configure the list by setting the GSK_SSL_EXTN_SIGALG
attribute.
There is no system value for this property but the entries in the system list can be removed or
reordered using SSLCONFIG. Anytime a value is removed from a supported list, the potential
exists to introduce interoperability issues. The typical user will not care about this list, but it
could be important for the most restrictive security policies.
Following is the IBM i 7.2 default System SSL signature algorithm list:
ECDSA_SHA512
ECDSA_SHA384
ECDSA_SHA256
ECDSA_SHA224
ECDSA_SHA1
RSA_SHA512
RSA_SHA384
RSA_SHA256
RSA_SHA224
RSA_SHA1
RSA_MD5
4.8 DB2 Security

Separation of Duties short description
In IBM i versions older than 7.2, in order to grant or revoke privileges to an object, a user must
have one of the following:
Chapter 4. Security
195
8249_Security.fm
An object's owner
Object management authority
*ALLOBJ special authority (*ALLOBJ)
Anyone with authority to grant privileges can also perform any operations that require those
privileges. If you can grant the SELECT privilege, today, you are also allowed to query the
data.
IBM i 7.2 user has to have
Security administration function usage (QIBM_DB_SECADM) will be able to grant or
revoke privileges on any object to anyone regardless of whether they have any of the
above privileges.
Users may be authorized to manage security, but not be authorized to see or modify the
data. Authorization to see and/or modify the data is controlled by Row and Column
Access Control related SQL statements. The control is done for rown and for columns
separately.
Note:
A security administrator cannot grant data privileges to himselfonly to others.
Only QSECOFR or another security administrator can grant the security administrator
function usage.
DB2 Security is described in detail in 3 sections of DB2 in this book:
8.2, Separation of duties concept on page 264
8.2.2, Row and Column Access Control (RCAC) on page 267
8.3, Security Enhancements on page 275
4.9 Networking security refrence

Security improvements in networking area are described in: Chapter 5, Networking on
page 197. The networking chapter describes:
5.1.1, Domain Name System Security Extensions (DNSSEC) on page 198
5.2, Simple Network Management Protocol manager APIs on page 199
5.4, System SSL enhancements on page 200
5.5, Virtual private networks (VPNs) on page 201
5.5.1, Internet Key Exchange (IKE) Protocol Version 2 on page 202
5.5.3, IKEv2 Troubleshooting on page 202
196
8249_Networking.fm
Chapter 5.
Networking
This chapter describes the following topics that are related to networking enhancements
enabled in IBM i 7.2:
5.1, Domain Name System on page 198

5.2, Simple Network Management Protocol manager APIs on page 199
5.3, SR-IOV on page 200
5.4, System SSL enhancements on page 200
5.5, Virtual private networks (VPNs) on page 201
5.6, Virtual Local Area Network (VLAN) on page 206
5.7, Retrieve and update TCP/IP information on page 208
5.8, IPv6 proxy neighbor discovery for virtual Ethernet and PPP on page 209
5.9, Single Sign-on for both FTP and TELNET on page 210
5.10, IBM i 7.2 Ethernet Device Server Support (WAN over LAN) on page 211
For more information about the IBM i 7.2 networking enhancements, see the IBM i
Technology Updates developerWorks wiki:
echnology%20Updates/page/IBM%20i%207.2%20-%20Base%20Enhancements
197
8249_Networking.fm
5.1 Domain Name System

This chapter introduces that the DNS Security Extensions (DNSSEC) Server available on
IBM i now has DNSSEC capabilities. DNSSEC is a suite of IETF RFC specifications which
add security extensions to DNS. Additional information is available at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzakk/rzakkconceptdnsse
c.htm
For IBM i 7.2, DNS services are based on the industry-standard DNS implementation, known
as Berkeley Internet Name Domain (BIND) version 9. For previous IBM i releases, DNS
services were based on older BIND version 9 or BIND version 8.
To use the new BIND version 9 DNS server in IBM i 7.2, you must have the following options
installed on your system:
IBM i option 31 (DNS)
IBM i option 33 (Portable Application Solutions Environment (PASE))
IBM i 5733-SC1 option 1 (OpenSSH, OpenSSL, zlib)
Starting from IBM i V6R1, for security reasons, BIND 4 and 8 has been replaced with BIND 9.
Therefore, the migration to BIND 9 is required for your DNS server.
For more information, see the Domain Name System topic in the IBM i 7.2 Knowledge
Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzakk/rzakkkickoff.htm
5.1.1 Domain Name System Security Extensions (DNSSEC)

Domain Name System Security Extensions (DNSSEC) provides a means to secure DNS data
by using digital signatures and public key cryptography.
In a DNS zone, DNS zone data will be signed by a Zone Signing Keys (ZSK), and the ZSK is
signed by a Key Signing Key (KSK). A Delegation Signer (DS) resource record (RR), which is
derived from the KSK, can be copied to the parent zone to form a trust chain. So a secured
zones RRsets will contain: DNSKEY (ZSK and KSK) RRs, RRSIG (Resource Record
Signature) RRs, Next Secure (NSEC) RRs, and (optionally) DS RRs of the child zone.
Additional information is available at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzakk/rzakkconceptdnsse
c.htm?lang=en
DNSSEC allows a resolver or name server to verify the authenticity and integrity of DNS
response data by establishing a chain of trust to the source of the DNS data and validating
the digital signatures.
The main function of DNSSEC is to protect the user from forged data in the following ways:
Validate the origin of a DNS response, trust that the data came from the expected source.
Validate the integrity of a DNS response, trust that the data itself is correct
Validate denial of existence, trust a no records to return response.
DNSSEC does not provide any of the following functions:
Encryption of data (for example, SSL).
Protection from denial of service attacks.
Protection from going to phishing sites.
198
8249_Networking.fm
5.1.2 IBM i resolver

DNSSEC support in the IBM i resolver can be enabled by using the Change TCP/IP Domain
(CHGTCPDMN) command.
Note: CHGTCPDMN DNSSEC(*YES)
In DNSSEC terms, the IBM i resolver is a non-validating security-aware stub resolver. This
means that when DNSSEC is enabled, the IBM i resolver sets the DNSSEC OK bit in its
query messages to indicate that it can handle DNSSEC fields in responses. However, it relies
on the name server to do the actual authentication and validation of the DNS response data.
This dependency implies that to have a secure DNS solution, IBM i must trust the name
server and also have a secure communication channel to the name server. One option to
secure the communication channel is to configure the DNS server on the same partition as
the resolver and have them communicate via the loopback address (127.0.0.1 for IPv4 or ::1
for IPv6). Another option is to use IP Security (IPSec) to secure the communication channel
between IBM i and the name server.
For more information, see the Domain Name System Security Extensions (DNSSEC) topic
in the IBM i 7.2 Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzab6/dnssec.htm
5.2 Simple Network Management Protocol manager APIs

A new set of Simple Network Management Protocol (SNMP) manager APIs are now
available. An IBM i SNMP manager application can use this new set of APIs to take
advantage of the security features for authentication and data privacy associated with SNMP
version 3 (SNMPv3). The APIs support SNMPv3 agent discovery and the GET, GETNEXT,
and SET operations using the SNMPv3 protocol.
Following are the SNMPv3 APIs:
These APIs perform SNMPv3 agent discovery and manage authentication:
snmpDiscovery_v3()
snmpFreeAuthCB_v3()
These APIs perform the SNMP operations of GET, GETNEXT, and SET:
snmpGet_v3()
snmpGetnext_v3()
snmpSet_v3()
For an example of using the SNMPv3 APIs, see the Using SNMP Manager APIs - Example
topic in the IBM i 7.2 Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/snmpexmp.htm
For more information about the SNMPv3 APIs, see the Simple Network Management
Protocol (SNMP) Manager APIs topic in the IBM i 7.2 Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/unix6b.htm?lang=en
Chapter 5. Networking
199
8249_Networking.fm
5.3 SR-IOV
SR-IOV is PCI standard architecture that enables PCIe adapters to become self-virtualizing. It
enables adapter consolidation, through sharing, much like logical partitioning enables server
consolidation. With an adapter capable of SR-IOV, you can assign virtual slices of a single
physical adapter to multiple partitions through logical ports; all of this is done without the need
for a Virtual I/O Server (VIOS).
For more information, see the following references:
IBM Redbooks publication, IBM Power Systems SR-IOV: Technical Overview and
Introduction, REDP-5065:
http://www.redbooks.ibm.com/abstracts/redp5065.html?Open
IBM i IO Support Details topic in the IBM i Technology Updates developerWorks wiki:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%
20Technology%20Updates/page/IBM%20i%20IO%20Support%20Details
Following are the supported adapters:
FC EN0H; CCIN 2B93

FC EN0L; CCIN 2CC1
FC EN10: CCIN 2C4C
FC EN11; CCIN 2C4D
5.4 System SSL enhancements

System SSL is a set of services provided in the IBM i Licensed Internal Code to protect
TCP/IP communications using the SSL/TLS protocol. System SSL is accessible to application
developers from the following programming interfaces and Java Secure Socket Extension
(JSSE) implementation:
Global Security Kit (GSKit) APIs
Integrated IBM i SSL_ APIs (Note, not recommended, use GSKit APIs instead.)
Integrated IBM i JSSE implementation
SSL applications created by clients or by IBM that leverage an interface listed above use
System SSL. FTP and Telnet are examples of IBM applications that use System SSL. Not all
SSL enabled applications running on IBM i use System SSL.
IBM i 7.2 System SSL underwent the most significant updates since Transport Layer Security
(TLS) version 1.0 was originally introduced in V4R5 over a decade ago. System SSL added
support for the Transport Layer Security version 1.2 (TLSv1.2) protocol and the TLSv1.1
protocol.
The new TLSv1.2 support includes Elliptic Curve Diffie-Hellman (ECDHE) key exchange
cipher suites. In conjunction with the Digital Certificate Manager (DCM), support was added
for Elliptic Curve Digital Signature Algorithm (ECDSA) certificates.
Online Certificate Status Protocol (OCSP) support was also added to System SSL. OCSP is
a method to determine the revocation status for a digital certificate.
For detailed descriptions of cryptographic features please refer to 4.7, Cryptography for SSL
and TLS on page 190
200
8249_Networking.fm
5.5 Virtual private networks (VPNs)

Virtual private networks (VPNs) on IBM i are used to securely extend private intranets over
public networks. IBM i 7.1 and 7.2 enhancements to VPN give clients new security options
and management and configuration flexibility, including new CL commands for VPN
management and configuration, Internet Key Exchange (IKE) version 2, and enhanced
cryptographic algorithms. VPN is configurable on IBM i through Navigator for i.
Four new commands are provided in IBM i 7.2 to assist clients with VPN configuration and
management actions previously only possible through Navigator.
Load/Unload IP Filter (LODIPFTR) command is used to load and unload internet protocol
(IP) LODIPFTR. The VPN rules included in the load or unload are the rules that reside in
/QIBM/UserData/OS400/TCPIP/OPNAVRULES/VPNPOLICYFILTERS.I3P and are
generated by Navigator.
Example 5-1 Load filter rules on all interfaces, including VPN rules
LODIPFTR OPTION(*LOAD) LIND(*ALL)

STMF('/QIBM/UserData/OS400/TCPIP/PacketRules/test.i3p')
INCVPN(*YES)
Copy VPN Configuration File (CPYVPNCFGF) command provides new functionality to
import, export, or validate all VPN configurations on a system.
When used to import, all of the current VPN connections on the system, except the
IBM Universal Connection Wizard (UCW) connections QVPN01IBM1 and
QVPN01IBM2, are deleted and replaced with the imported configuration. It cannot be
used to import or export individual connections. Importing the VPN configuration file
with CPYVPNCFGF does not import the filter rules. The filter rules need to be
re-created to be used with the imported connections.
Exported VPN configuration information is stored in an XML file in the same schema
used by AIX, which creates instant cross-platform compatibility with AIX for VPN
configurations. AIX provides an XML schema mapping tool which is capable of
converting the AIX XML schema to the Linux XML schema, providing the capability for
cross-platform compatibility with Linux.
Another consideration for using CPYVPNCFGF is clients can create VPN
configurations on one system, then use CPYVPNCFGF to export the configuration to
be distributed to other systems. The XML VPN configuration file can be modified as
necessary for different systems and locations without requiring Navigator to recreate
the configuration for each system.
CPYVPNCFGF is also a simple method to assist in debugging VPN configuration
issues. The OPTION(*VALIDATE) parameter verifies if the VPN configuration in the
stream file is correct. The exported configuration file can also be used to confirm each
VPN connection's configuration without Navigator.
Example 5-2 Export VPN configuration to a stream file
CPYVPNCFGF OPTION(*EXPORT) STMF('/mydir/vpncfg')

The Retrieve TCP/IP Information (RTVTCPINF) and Update TCP/IP Information
(UPDTCPINF) commands can also be used in 7.2 to save and restore the TCP/IP
configuration of a system, which includes the VPN configuration files. Under the covers,
RTVTCPINF uses CPYVPNCFGF to retrieve the VPN configuration information.
Additional information is available at New IBM i 7.2 and 7.1 VPN Enhancements
http://www.ibmsystemsmag.com/Blogs/i-Can/
201
8249_Networking.fm
The Start VPN Connection (STRVPNCNN) and End VPN Connection (ENDVPNCNN)
commands provide the options to start and end VPN connections, respectively.
Example 5-3 Start and end a VPN connection
STRVPNCNN CNN(conn1)
ENDVPNCNN CNN(conn1)
5.5.1 Internet Key Exchange (IKE) Protocol Version 2

The IKE version 2 protocol (IKEv2) is an enhancement to the Internet Key Exchange protocol
and is supported starting in 7.1. IKEv2 enhances the function of performing dynamic key
exchange and partner authentication for VPN. IKEv2 simplifies the message flow for key
exchange negotiations and introduces measures to fix ambiguities and vulnerabilities
inherent in IKE version 1 (IKEv1). IKEv2 is the basis for future enhancements to the key
exchange protocol for VPN. Despite the differences, IKEv1 and IKEv2 both negotiate a
security association (SA) to protect data between two endpoints.
5.5.2 IKEv2 Configuration

IKEv2 presents minimal impacts to Navigator and current VPN configuration objects. IBM i
7.1 or 7.2 is required to use an IKEv2 connection. To enable IKEv2, use the new Internet Key
Exchange version setting on the new connection wizard and on the connection properties
panel for existing connections.
Key exchange and data policies can be used for either IKEv1 or IKEv2. If the key exchange
policy is used with IKEv2, the settings for main mode and aggressive mode are ignored as
these are only valid for IKEv1 negotiations.
Figure 5-1 Internet Key Exchange (IKE) version setting
5.5.3 IKEv2 Troubleshooting

Troubleshooting issues for IKEv2 connections is similar to troubleshooting issues for IKEv1
connections. The VPN jobs run in the subsystem QSYSWRK. VPN connection management
and IKEv1 processing are handled under the jobs QTOVMAN and QTOKVPNIKE,
respectively. IKEv2 processing is handled under a new key manager job, QTOKVPNIK2. The
VPN key manager listens to UDP port 500 to perform the IKEv2 protocol processing. The logs
for these jobs are accessible from Navigator or the command line interface.
202
8249_Networking.fm
IKEv2 uses the same diagnostic tools used for VPN in previous releases. The VPN job logs
for QTOVMAN, QTOKVPNIKE, and QTOKVPNIK2 display successes and failures during
connection negotiation, which can be analyzed for problems with VPN connections.
TRCTCPAPP *VPN traces the VPN connection manager and both key manager servers.
Separate trace files are created for the connection manager and key manager servers.
5.5.4 IBM i 7.2 IKEv2 Enhancements

NAT-compatible IPsec Negotiation Support
VPN support for network address translation traversal (NAT-T) is essential for IKE
negotiations across NAT devices as conventional NAT does not work with IPsec. IBM i
previously supported NAT-T for IKEv1, and 7.2 now supports NAT-T for IKEv2. NAT-T uses
UDP encapsulation to wrap an IPsec packet inside a IP/UDP header so that the packet is
correctly translated. This UDP encapsulation only applies to VPN implementations that
use IPsec encapsulating security payload (ESP) packets in tunnel mode or transport
mode. To enable NAT-compatible IPsec negotiation for IKEv2, use the new option for IPsec
through NAT on the VPN properties panel.
IKE_SA Rekey
Like IKEv1, IKEv2 key negotiation operates in two phases. The IKE_SA rekey option in 7.2
allows IKEv2 to regenerate the IKE_SA keys negotiated during the first phase of the key
exchange without doing a full re-authentication. The IKE_SA rekey operation takes place
as an independent exchange when one side determines the IKE_SA has expired. A new
IKE_SA key is regenerated in time for the rekey attempt of the CHILD_SA, which is
generated during the second phase negotiations. The key life times of IKE_SA and
CHILD_SA are managed independently of the peer system. To enable the IKE_SA rekey,
use the new rekey setting on the VPN properties panel.
HTTP Certificate Lookup via URL
IKE negotiation partners can send a URL link to a certificate being used to authenticate
the key exchange with the new HTTP lookup of certificates via URL option in 7.2. The
purpose of using the URL lookup is to save bandwidth in the IKE negotiation payload.
IKEv2 on IBM i supports peers sending the URL lookup of certificates but does not
implement sending a URL itself. Allowing URL lookup of certificates is enabled by default.
To disable the URL lookup of certificates, uncheck the new option for HTTP lookup of
certificates on the VPN properties panel.
Figure 5-2 Virtual Private Networking Properties
203
8249_Networking.fm
Elliptic Curve DSA (ECDSA) Authentication

IKE processing requires both sides authenticate each other using a negotiated
authentication method. Prior to 7.2, the two options for the authentication method were
pre-shared keys or public key cryptography with RSA authentication. ECDSA signatures
are available in 7.2 as a third method for authentication. ECDSA signatures are smaller
than RSA signatures of similar strength. IKE authentication methods in key exchange
policies now support ECDSA-256, ECDSA-384, and ECDSA-521 in addition to pre-shared
keys and public key cryptography with RSA.
Figure 5-3 ECDSA Authentication Method
New Cryptographic Algorithms

Stronger encryption and integrity algorithms may be required for VPN compliance with
security policies. These algorithms are available for both IKEv1 and IKEv2 negotiations
starting in 7.1. Additional algorithms are provided in 7.2 for IKEv2 negotiations for further
flexibility and interoperability. The new cryptographic algorithms are listed in the tables
below.
Table 5-1 New Key Exchange Policy Algorithms
Algorithm Type
Encryption, confidentiality
algorithms used to encrypt
the data
Hash, integrity algorithms

used to protect data against
tampering
Pseudo Random Function
(PRF), used for generating
keying material and
authentication of the IKE SA
204
Algorithm
AES-CBC (128 bit)
IBM I 7.1
IBM i 7.2
IKEv1
IKEv2
IKEv1
IKEv2
AES-CBC (192 and 256 bit)
AES-CTR (128, 192, and

256 bit)
AES-XCBC-MAC
(Hash 96 bit/PRF 128 bit)
HMAC-SHA-256
HMAC-SHA-384
HMAC-SHA-512
8249_Networking.fm
Algorithm Type
Diffie-Hellman, used to
generate a shared secret
key to encrypt further IKE
communications
Algorithm
IBM I 7.1
IBM i 7.2
IKEv1
IKEv2
IKEv1
IKEv2
Group 14 (2048 bit MODP)
Group 24(4096 bit MODP)
Group 19 (256 bit ECP)
Table 5-2 New Data Policy Algorithms

Algorithm Type
Algorithm
IBM i 7.1
IKEv1
the data
Authentication method,
used to verify the identity of
each peer (pre-shared keys,
RSA authentication,
ECDSA authentication)
Diffie-Hellman for Perfect

Forward Secrecy (PFS), the
group used to generate
random public keys when
negotiating the IPsec SA to
ensure it as not derived
from any other secret
IBM i 7.2
IKEv2
IKEv1
IKEv2
3DES-CBC
AES-CBC (128, 192, and

256 bit)
AES-GCM (128, 192, and

256 bit)
AES-CCM (128, 192, and

256 bit)
AES-GCM (128, 192, and

256 bit)
AES-GMAC (128, 192, and

256 bit)
AES-XCBC-MAC
HMAC-SHA-256
HMAC-SHA-384
HMAC-SHA-512
Group 14 (2048 bit MODP)
Group 24(4096 bit MODP)
Note: The preexisting algorithms are still supported for use with VPN. However, the new
key exchange and data policy encryption and hash algorithms are recommended over the
older algorithms listed below.
205
8249_Networking.fm
Table 5-3 Legacy Key Exchange and Data Policy algorithms

Algorithm Type
the data
Hash, integrity algorithms

used to protect data against
tampering
Pseudo Random Function
(PRF), used for generating
keying material and
authentication of the IKE SA
Algorithm
IBM i 7.1
IBM i 7.2
IKEv1
IKEv2
IKEv1
IKEv2
DES
RC4
RC5
MD5
5.6 Virtual Local Area Network (VLAN)

IBM i now supports IEEE 802.1Q VLAN tagging to allow access to multiple VLANs on a single
adapter.
A VLAN allows a single LAN to be sub-divided so that broadcast and multicast traffic targeted
to a specific VLAN is not seen or processed by other systems on that LAN which are not part
of the same VLAN. This technology provides performance improvement as well as an
isolation level, which improves security. With the VLAN support it is possible to assign
configured IP interfaces to a particular VLAN and access multiple VLANs with a single
adapter.
IBM i TCP/IP Virtual LAN support now allows you to use a single adapter to connect to
multiple VLANs
Add redundant network connections without adding additional adapters
Connect to a new network VLAN without adding another adapter
Supported by all IBM i Ethernet and Virtual Ethernet adapters
Supported for IPv4 and IPv6
5.6.1 IBM i VLAN configuration

IBM i VLAN configuration can be done from either IBM i Navigator for i or CL commands. The
following are some examples.
206
8249_Networking.fm
Figure 5-4 IBM i VLAN configuration
Figure 5-5 Interfaces list has new VLAN ID column to display VLAN ID assignments
Note: Interfaces using native VLAN (e.g. 192.168.31.12 above) are configured with no
VLAN identifier.
Equivalent CL configuration:
ADDTCPIFC INTNETADR('192.168.41.62') LIND(ETH2 3)
SUBNETMASK('255.255.255.0)
NETSTAT interface list also displays VLAN ID (press F11 to show)
207
8249_Networking.fm
Work with TCP/IP Interface Status

System:
UT30P05
5=Display details
8=Display associated routes
9=Start
10=End
12=Work with configuration status
14=Display multicast groups
Opt
Internet
Address
9.5.10.216
127.0.0.1
192.168.1.12
192.168.31.12
192.168.31.62
192.168.41.12
192.168.41.62
Network
Address
9.5.19.0
127.0.0.0
192.168.1.0
192.168.31.0
192.168.31.0
192.168.41.0
192.168.41.0
F3=Exit
F9=Command line
F13=Sort by column
Line
Description
ETHLINE
*LOOPBACK
VETH1
ETH2
ETH3
ETH3
ETH4
Virtual
LAN
ID
*NONE
*NONE
*NONE
*NONE
2
*NONE
3
F11=Display Virtual LAN ID

F20=Work with IPv6 interfaces
Bottom
F12=Cancel
F24=More keys
Figure 5-6 Equivalent CL configuration IBM i VLAN Naming Considerations
VPN policy filters and IP packet rules use format linename.vlanid.

Note: ETH2.3 is VLAN ID 3 on line description ETH2
Sockets APIs taking an interface name also use linename.vlanid.
Note: if_nametoindex(ETH2.3)
fe80::1234%eth2.3 (IPv6 link-local address with scope identifier).
Note: If VLANs are used, do not use line description names with periods.
For example, with two line descriptions of ETH2.3 and ETH2, VPN and Sockets interpret
ETH2.3 as line ETH2.3 rather than VLAN 3 on line ETH2.
5.7 Retrieve and update TCP/IP information

The following new CL commands are available to save and restore the sets of configuration
files and settings used by the IBM i TCP/IP configuration and select TCP/IP application
servers:
Retrieve TCP/IP Information (RTVTCPINF)
Update TCP/IP Information (UPDTCPINF)
208
8249_Networking.fm
Theses commands help address the complexities of managing TCP/IP and application server
configuration files. The new commands are modeled from the Retrieve System Information
(RTVSYSINF) and Update System Information (UPDSYSINF) commands which perform a
similar function for general system information.
5.7.1 Retrieve TCP/IP Information (RTVTCPINF) CL command

The Retrieve TCP/IP Information (RTVTCPINF) CL command retrieves selected TCP/IP
configuration and application information. The retrieved information is stored as save files and
user spaces in a user selected library.
The RTVTCPINF command allows for easy backup of TCP/IP related information which can
be restored later or propagated to another system.
5.7.2 Update TCP/IP Information (UPDTCPINF) CL command

The Update TCP/IP Information (UPDTCPINF) CL command updates selected TCP/IP
configuration and application information. This command uses objects generated by the
RTVTCPINF command. This command provides a simple way to move application
configuration files from one system to another.
The following information types are supported by the UPDTCPINF command:
TCP/IP configuration
Bootstrap Protocol
Dynamic Host Configuration Protocol (DHCP)
File Transfer Protocol (FTP)
HTTP administration server
Internet daemon
IP packet filtering
Line printer daemon
NetServer
OMPROUTE daemon
Point-to-point
Post Office Protocol (POP)
Quality of Service
Remote execution
Router daemon
Simple Mail Transfer Protocol (SMTP)
Simple Network Management Protocol (SNMP)
Service and support proxy
Telnet
Trivial File Transfer Protocol (TFTP)
Virtual Private Network (VPN)
Note: User data for applications such as SMTP and POP is not supported. Only
configuration related data for these servers is supported.
5.8 IPv6 proxy neighbor discovery for virtual Ethernet and PPP
The ND proxy allows two separate links to operate as if nodes on each link are on a single
common link. This is similar to bridging two networks at the link layer, but operates instead at
the IP level. This allows nodes on different types of networks (for example Ethernet and PPP)
209
8249_Networking.fm
to operate as if they are on the same network. The ND Proxy provides function similar to the
Transparent Subnet Proxy for IPv4, allowing virtual Ethernet and point-to-point links to be
proxied on a physical Ethernet link.
5.9 Single Sign-on for both FTP and TELNET

Single Sign-on for both FTP and TELNET is described in: Chapter 4.1, Single Sign-on on
page 182.
210
8249_Networking.fm
5.10 IBM i 7.2 Ethernet Device Server Support (WAN over LAN)
IBM i 7.2 adds support connections to Ethernet device servers, which are also known as
Ethernet serial servers or Ethernet terminal servers. These devices are external non-IBM
equipment which are Ethernet-attached and contain one or more serial ports to which
external modems can be attached. A compatible Ethernet device server must support RFC
2217. An IBM i RFC 2217 session provides a virtual com port for an Async or PPP line.
RFC 2217 (Telnet Com Port Control Protocol) is an extension of the Telnet Protocol that
provides a method for device servers to accept Telnet sessions and pass the Telnet data
received to a com port, and pass data received from the com port to the client. It also allows
the device server to send the client any serial line status changes, and allows the client to
manage flow control with the device server. It also allows a client to send configuration
information to a device server.
This new support for "WAN over LAN" asynchronous configurations expands advanced
virtualization capabilities
Saves PCI slots for applications requiring a modem, thus reducing configuration cost
Provides WAN connectivity for servers that do not have available PCIe slots
Allows IBM i client partitions with virtual I/O to use FAX and other WAN asynchronous
applications
Allows the same Ethernet adapter that provides TCP/IP connectivity for an IBM i partition
to provide WAN asynchronous connectivity
IBM i asynchronous applications that have traditionally run on PCIe WAN adapters will now
run seamlessly over an Ethernet connection to an Ethernet device server without application
changes. For an existing IBM i configuration definition, the only change is that the Async or
PPP line description must be modified to specify that it is for an Ethernet device server, and
specify the Ethernet device server IP address and port. IBM i clients requiring a large number
of serial ports or running on systems without PCIe adapter slots (such as PureSystems or
BladeCenter devices) now have the option to run IBM i Communication Applications on their
systems.
A compatible Ethernet device server must support RFC 2217. An IBM i RFC 2217 session
provides a virtual com port for an Async or PPP line. Ethernet device servers with RFC 2217
support are available from a variety of vendors, in models containing anywhere from 1 to 48
serial ports. IBM i has been tested with the following Ethernet device servers:
Digi PortServer TS 4 (firmware version 82000747_V2 01/29/2013)
Perle IOLAN SDS4 (firmware version 4.5) Ethernet device servers.
Each serial port on an Ethernet device server has an assigned TCP port number
Facsimile Support for IBM i has been tested with the MT9234ZBA modem attached to
these Ethernet device servers
211
8249_Networking.fm
Figure 5-7 WAN over LAN
Note: Ethernet device servers typically provide a web-based interface for configuration
and management.
For example, if a Digi PortServer has an IP address of 9.5.80.73, then entering
http://9.5.80.73 in a web browser accesses the configuration and management
interface.
An specific serial port is accessed by establishing a Telnet session to the Ethernet
device server IP address and the TCP port number assigned to the serial port (for
example 9.5.80.73:2001)
IBM i support is limited to IBM's implementation of RFC 2217 and IBM software and
hardware. The non-IBM vendor provides the support for its implementation of RFC 2217, its
TCP/IP network connection, and any downstream modems or fax devices. In case a problem
does occur at the client site, like other non-IBM products attached through IBM LAN adapters
and standard protocols, IBM will participate with clients and other vendors in problem
determination under standard IBM warranty and service agreements. If IBM determines the
problem is associated with the IBM adapter or with the IBM protocol implementation, normal
problem resolution procedures will follow.
5.10.1 WAN over LAN requirements

Here are the WAN over LAN requirements:
Ethernet device server to support COM Port Control Protocol RFC 2217 for transport of
serial data and RS-232 control signals
IBM i 7.2 PTFs:
5770SS1 PTF SI54771 or supersede
5770999 PTF MF57686 or supersede
PTFs for Licensed Product 5798FAX V5R8M0
SI54319 or supersede
SI52896 or supersede
212
8249_Networking.fm
CRTLINASC example:
Create Line Desc (Async) (CRTLINASC)
Line description . . . .
Resource name . . . . .
Online at IPL . . . . .
Connection type . . . .
Switched network backup
Data bits per character
Type of parity . . . . .
Stop bits . . . . . . .
Duplex . . . . . . . . .
Echo support . . . . . .
Line speed . . . . . . .
Modem type supported . .
Remote internet address
Remote port. . . . . . .
Maximum buffer size . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . .
. . . .
F3=Exit
F4=Prompt
F5=Refresh
FAXLINE
*ETHDEVSVR
*YES
*NONSWTPP
*NO
8
*NONE
1
*FULL
*NONE
1200
*NORMAL
___________
___________
896
Name
Name, *ETHDEVSVR
*YES, *NO
*NONSWTPP, *SWTPP...
*NO, *YES
8, 7
*NONE, *ODD, *EVEN
1, 2
*FULL, *HALF
*NONE, *ALL, *CNTL
50, 75, 110, 150, 300, 600...
*NORMAL, *V54, *IBMWRAP
1-65535
128-4096
F10=Additional parameaters
F24=More keys
More...
F12=Cancel
Figure 5-8 CRTLINASC Example
Note: Fax Support 5798-FAX V5R8M0 also works on V7R1, but does not support the
*ETHDEVSRV resource name.
For more information about the IBM i 7.2 networking enhancements, see the IBM i
Technology Updates wiki:
echnology%20Updates/page/IBM%20i%20Functional%20Enhancements%20Details
213
8249_Networking.fm
214
8249_HA.fm
Chapter 6.
High availability
This chapter describes an introduction and enhancements of IBM PowerHA SystemMirror for
i and related functions in IBM i 7.2. This includes:
Introduction
IBM PowerHA SystemMirror for i
Administrative Domain
Independent Auxiliary Storage Pool (IASP)
215
8249_HA.fm
6.1 Introduction
To realize a high availability (HA) and a disaster recovery (DR) IBM i environment, IBM
provides PowerHA SystemMirror for i. PowerHA SystemMirror for i provides a hardware
based (disk level) data and application resiliency solution that is an integrated extension of
IBM i operation system and storage management architecture as shown in Figure 6-1 and
also supports both of IBM i (Geographic Mirroring) replication and an external storage such
as DS8000, Storwize, and SVC replication. PowerHA SystemMirror for i offers solutions
covering simple data center to multiple-site configuration and enables 24x365 operational
availability and provides automation for planned and unplanned outages.
Figure 6-1 PowerHA SystemMirror for i Architecture
The levels of the replication technology by PowerHA SystemMirror for i are generally divided
into five levels described in Figure 6-2.
Level 1 technology is one site shared storage technology. The solution in this level is called
LUN-level switching. LUN-level switching supports DS8000, Storwize, and SVC.
Level 2 is one site replication technology. IBM i based second level replication is realized by
Synchronous Geographic Mirroring. An External storage based replication is realized by
Metro Mirror. These two level technology is applied as an high availability solution for simple
data center.
Level 3 of the replication technology is two site replication. This level is achieved by
asynchronous replication technology, namely Asynchronous Geographic Mirroring as IBM i
based technology and Global Mirror as an external storage based technology.
Level 4 is two site HA + DR configuration. This level is accomplished by combining Level 1
technology and Level 3 technology. On the production site, one storage is shared by a
production system and an HA standby system. When the outage of the production system
occurs, the storage will be switched to the HA standby system. And when the production site
down occurs, the DR standby system will be raised to a primary node by role swapping.
216
8249_HA.fm
Level 5 is three site replication. This configuration is a combination of Level 2 and Level 3
technologies. By aligning the HA standby system to the difference site from the production
site, higher level of availability can be accomplished than Level 4 technology. This level is now
supported on only DS8000.
Figure 6-2 PowerHA SystemMirror for i Replication Technology
For more information and the details of PowerHA SystemMirror for i, see PowerHA
SystemMirror for IBM i Cookbook, SG24-7994
http://www.redbooks.ibm.com/abstracts/sg247994.html?Open
6.2 IBM PowerHA SystemMirror for i

This section describes the following enhancements of IBM PowerHA SystemMirror for i as the
time of IBM i 7.2 released:
PowerHA SystemMirror for i Packaging

DS8000 HyperSwap Support with PowerHA for i 7.2 Express Edition
Support for SVC/Storwize Global Mirror with Change Volumes
GUI changes in IBM Navigator for i
Minimum cluster and PowerHA version for upgrading nodes to IBM i 7.2
6.2.1 PowerHA SystemMirror for i Packaging

PowerHA SystemMirror for i has the following three editions. Enterprise Edition as a
multiple-site DR solution and Standard Edition, that is for simple data center HA solution, are
already provided in IBM i 7.1. In IBM i 7.2, Express Edition is added to the lineup of PowerHA
SystemMirror for i.
Enterprise Edition (5770-HAS Option 1)
Standard Edition (5770-HAS Option 2)
Chapter 6. High availability
217
8249_HA.fm
Express Edition (5770-HAS Option 3)
6.2.2 DS8000 HyperSwap Support with PowerHA for i 7.2 Express Edition
With PowerHA SystemMirror for i 7.2, the first stage of the Express Edition offering enables
single-node, full-system HyperSwap with the DS8700 (or above) that provide customers
with continuously available storage through either planned or unplanned storage outage
events. HyperSwap is a instantly switching capability between DS8000 servers leveraging
Metro Mirror. Once HyperSwap is configured, switching will occur automatically in the event of
a DS8000 outage with no downtime. And a command for switching a storage node, so this
solution is valid for planned outage events on DS8000 side as shown in Figure 6-3.
Figure 6-3 PowerHA SystemMirror for i Express Edition with DS8000 HyperSwap
To configure PowerHA SystemMirror for i Express Edition with DS8000 HyperSwap, follow the
following steps:
1. Create LUNs (Logical Unit Numbers) on the source DS8000.
2. Assign LUNs on source DS8000 to the IBM i.
3. Create LUNs on the target DS8000.
Note: Do not assign target LUNs to the IBM i until after Metro Mirror is configured on
DS8000 side.
4. Configure Metro Mirror between the source and target DS8000.
5. Assign the LUNs on the target DS8000 to the same IBM i.
6. Verify the HyperSwap configuration with the Display HyperSwap Status (DSPHYSSTS)
command.
218
8249_HA.fm
Figure 6-4 shows the example of result of DSPHYSSTS command. A direction of arrows in Copy
Status of DSPHYSSTS screen express the direction of mirroring between LUNs.
Display HyperSwap Status
Resource
DMP366
DMP006
DMP013
DMP369
DMP371
DMP373
DMP376
DMP393
DMP380
DMP395
DMP384
DMP386
DMP388
DMP390
DMP392
Volume
Identifier
IBM.2107-75TT911/3F00
IBM.2107-75TT911/3F01
IBM.2107-75TT911/3F02
IBM.2107-75TT911/3F03
IBM.2107-75TT911/3F04
IBM.2107-75TT911/3F05
IBM.2107-75TT911/3F06
IBM.2107-75TT911/3F07
IBM.2107-75TT911/3F08
IBM.2107-75TT911/3F09
IBM.2107-75TT911/3F0A
IBM.2107-75TT911/3F0B
IBM.2107-75TT911/3F0C
IBM.2107-75TT911/3F0D
IBM.2107-75TT911/3F0E
Copy
Status
--->
--->
--->
--->
--->
--->
--->
--->
--->
--->
--->
--->
--->
--->
--->
Resource
DMP004
DMP005
DMP007
DMP009
DMP010
DMP011
DMP012
DMP014
DMP016
DMP017
DMP018
DMP020
DMP021
DMP023
DMP025
Y319BP17
10/15/14 12:18:04
Volume
Identifier
IBM.2107-75BPF81/3D00
IBM.2107-75BPF81/3D01
IBM.2107-75BPF81/3D02
IBM.2107-75BPF81/3D03
IBM.2107-75BPF81/3D04
IBM.2107-75BPF81/3D05
IBM.2107-75BPF81/3D06
IBM.2107-75BPF81/3D07
IBM.2107-75BPF81/3D08
IBM.2107-75BPF81/3D09
IBM.2107-75BPF81/3D0A
IBM.2107-75BPF81/3D0B
IBM.2107-75BPF81/3D0C
IBM.2107-75BPF81/3D0D
IBM.2107-75BPF81/3D0E
More...

F3=Exit
F5=Refresh
F11=View 2
F12=Cancel
Figure 6-4 DSPHYPSTS command
Change HyperSwap Status (CHGHYSSTS) command can be used for suspending and resuming
mirror operations between a storage node, and switching a storage node manually as shown
in Figure 6-5. So this solution can be also leveraged for planned outage events on a storage
node side. When you suspend mirroring via CHGHYSSTS command, Copy Status in
DSPHYPSTS screen will change from ---> to -\-> as shown in Figure 6-6.
Change HyperSwap Status (CHGHYSSTS)
Option . . . . . . . . . . . . .
*STOP, *START, *SWAP
Figure 6-5 CHGHYSSTS command
219
8249_HA.fm
Display HyperSwap Status
Resource
DMP366
DMP006
DMP013
DMP369
DMP371
DMP373
DMP376
DMP393
DMP380
DMP395
DMP384
DMP386
DMP388
DMP390
DMP392
Volume
Identifier
IBM.2107-75TT911/3F00
IBM.2107-75TT911/3F01
IBM.2107-75TT911/3F02
IBM.2107-75TT911/3F03
IBM.2107-75TT911/3F04
IBM.2107-75TT911/3F05
IBM.2107-75TT911/3F06
IBM.2107-75TT911/3F07
IBM.2107-75TT911/3F08
IBM.2107-75TT911/3F09
IBM.2107-75TT911/3F0A
IBM.2107-75TT911/3F0B
IBM.2107-75TT911/3F0C
IBM.2107-75TT911/3F0D
IBM.2107-75TT911/3F0E
Copy
Status
-\->
-\->
-\->
-\->
-\->
-\->
-\->
-\->
-\->
-\->
-\->
-\->
-\->
-\->
-\->
Resource
DMP004
DMP005
DMP007
DMP009
DMP010
DMP011
DMP012
DMP014
DMP016
DMP017
DMP018
DMP020
DMP021
DMP023
DMP025
Y319BP17
10/15/14 12:19:11
Volume
Identifier
IBM.2107-75BPF81/3D00
IBM.2107-75BPF81/3D01
IBM.2107-75BPF81/3D02
IBM.2107-75BPF81/3D03
IBM.2107-75BPF81/3D04
IBM.2107-75BPF81/3D05
IBM.2107-75BPF81/3D06
IBM.2107-75BPF81/3D07
IBM.2107-75BPF81/3D08
IBM.2107-75BPF81/3D09
IBM.2107-75BPF81/3D0A
IBM.2107-75BPF81/3D0B
IBM.2107-75BPF81/3D0C
IBM.2107-75BPF81/3D0D
IBM.2107-75BPF81/3D0E
More...

F3=Exit
F5=Refresh
F11=View 2
F12=Cancel
Figure 6-6 DSPHYSSTS command when suspended
HyperSwap can be also combined with IBM i Live Partition Mobility (LPM) as shown in
Figure 6-7. By using with LPM, you can realize a minimal downtime solution to migrate from
one server/storage combination to another. Once affinity between a Power Systems server
and a DS8000 server is defined, moving a partition by LPM will also trigger a switching
DS8000 server by HyperSwap when appropriate. To define a affinity between them, use Add
HyperSwap Storage Desc (ADDHYSSTGD) command as shown in Figure 6-8.
220
8249_HA.fm
Figure 6-7 HyperSwap with Live Partition Mobility
Add HyperSwap Storage Desc (ADDHYSSTGD)

System Serial Number . . . . . .
IBM System Storage device . . .
Character value
Figure 6-8 ADDHYSSTGD command
For more information including how to configure and manage the Express Edition with
HyperSwap environment, see the following:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Power
HA%20SystemMirror%20for%20i/page/7.2%20Enhancements
6.2.3 Support for SVC/Storwize Global Mirror with Change Volumes

IBM PowerHA SystemMirror for i 7.2 will support Global Mirror with Change Volumes
(GCMV) of SAN Volume Controller (SVC) and Storwize by applying a PTF which will be
released in the future. A PTF for this enhancement of IBM PowerHA SystemMirror for i 7.1 is
already available as 5770HAS V7R1M0 SI52687.
GMCV was introduced on the V6.3 release for SVC and Storwize. Prior to this release, Global
Mirror guaranteed a consistent copy on the target side, but the recovery point objective (RPO)
was not tunable, and usually within seconds. This solution required enough bandwidth to
support the peak workload. GMCV uses FlashCopy internally to guarantee the consistent
221
8249_HA.fm
copy, but offers a tunable RPO, called a cycling period. GMCV may be appropriate when
bandwidth is an issue, although if bandwidth cannot support the replication, the cycling period
may need to be adjusted from seconds up to 24 hours.
Configuring GMCV is done from the SVC/Storwize user interface as well as Global Mirror.
Once the above and related PTFs are applied, IBM PowerHA SystemMirror for i will recognize
that GMCV has been configured and manage the replication environment accordingly.
For more information about Global Mirror with Change Volumes, see the IBM System Storage
SAN Volume Controller and Storwize V7000 Replication Family Services, SG24-7574
available at:
6.2.4 GUI changes in IBM Navigator for i

From PowerHA SystemMirror for i 7.2, the High Availability Solution Manager GUI and the
Cluster Resource Services GUI in IBM Navigator for i have been removed. Alternatively, the
PowerHA GUI can be used for configuring and managing a high availability environment as
Figure 6-9 PowerHA GUI in IBM Navigator for i
6.2.5 Minimum cluster and PowerHA version for upgrading nodes to IBM i 7.2
When upgrading existing IBM i cluster node to IBM i 7.2, you must consider the version of the
cluster and PowerHA. The cluster version in IBM i 7.2 release level is 8 and PowerHA version
is 3.0 as shown in Figure 6-10. Change Cluster Version (CHGCLUVER) command can be used
for adjusting the cluster and PowerHA version.
222
8249_HA.fm
Display Cluster Information

Cluster . . . . . . . . . . . . .
Consistent information in cluster
Current PowerHA version . . . . .
Current cluster version . . . . .
Current cluster modification level
Configuration tuning level . . . .
Number of cluster nodes . . . . .
Number of device domains . . . . .
Number of administrative domains .
Number of cluster resource groups
Cluster message queue . . . . . .
Library . . . . . . . . . . . .
Failover wait time . . . . . . . .
Failover default action . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:
:
:
:
:
:
:
:
:
:
:
:
:
:
CLUSTER
Yes
3.0
8
0
*NORMAL
2
0
0
0
*NONE
*NONE
*NOWAIT
*PROCEED

F1=Help
F12=Cancel
F3=Exit F5=Refresh F7=Change versions

F13=Work with cluster menu
F8=Change cluster
Figure 6-10 The cluster and PowerHA version in IBM i 7.2 release level
6.3 Administrative Domain

To maintain the consistency of objects in SYSBAS in a clustering environment, IBM i provides
Administrative Domain function since IBM i 5.4. In this section covers the following
enhancements of Administrative Domain in IBM i 7.2:
Increased Administrative Domain Limit
Synchronization of object authority and ownership
The details of the above enhancements, refer to the following:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Power
HA%20SystemMirror%20for%20i/page/7.2%20Enhancements
6.3.1 Increased Administrative Domain Limit

Prior to IBM i 7.2, the supported number of monitored resources entries (MREs) was 25,000.
In IBM i 7.2, the number of MREs are increased to 45,000. To maintain MREs, you can use
either Work with Monitored Resources (WRKCADMRE) command or PowerHA GUI in IBM
Navigator for i.
The more information about WRKCADMRE command, see the IBM i 7.2 Knowledge Center
at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/cl/wrkcadmr
e.htm
223
8249_HA.fm
6.3.2 Synchronization of object authority and ownership

Object authority and ownership can be monitored and synchronized with Administrative
Domain. The supported object attributes of these entries are object owner, authority entry,
authorization list, primary group.
If you add new MREs in IBM i 7.2 Administrative Domain, these four attributes will be had by
default. Existing MREs which were added with *ALL attributes, these four attributes will be
synchronized after upgrading PowerHA version to 3.0. Note that MREs will be marked as
inconsistent until source node for new attributes is determined. If you want to synchronize
these attributes instantly, perform Remove Admin Domain MRE (RMVCADMRE) command
followed by Add Admin Domain MRE (ADDCADMRE) command for the specific objects or you
can use the new option screen of PowerHA GUI in IBM Navigator for i which enables
selecting a source node when synchronizing as shown in Figure 6-11.
Figure 6-11 Managing MRE options in PowerHA GUI in IBM Navigator for i
For more information about RMVCADMRE and ADDCADMRE commands, see the IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/rmvcadmre.htm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/addcadmre.htm
6.4 Independent Auxiliary Storage Pool (IASP)

In this section introduces the following enhancements related to IASP:
DSPASPSTS improvements for better monitoring of vary-on time
Reduced UID/GID processing time during vary-on
IASP assignment for consolidated backups
6.4.1 DSPASPSTS improvements for better monitoring of vary-on time

Display ASP Status (DSPASPSTS) command now have an ability to preserve and display up to
64 vary histories and shows additional information such as UDFS and STATFS. Figure 6-12
shows the example of DSPASPSTS ENTRIES(*ALL) command which lists several histories of
varying on and off an IASP. And shows the example of displaying UDFS information via
DSPASPSTS command.
224
8249_HA.fm
Display ASP Vary Status

ASP Device . . . . :
ASP State . . . . :
Step . . . . . . . :
033 IASP01
AVAILABLE
/ 35
Current time . . . :
Previous time . . :
Start date . . . . :
Step
Cluster vary job submission
Waiting for devices - none are present
Waiting for devices - not all are present
DASD checker
Storage management recovery
Synchronization of mirrored data
Synchronization of mirrored data - 2
Scanning DASD pages
00:00:22
00:00:32
10/14/14
Elapsed time
00:00:00
00:00:00
00:00:00
00:00:00
More...

------------------------------------------------------------------------------Display ASP Vary Status
ASP Device . . . . :
ASP State . . . . :
Step . . . . . . . :
033 IASP01
VARIED OFF
/ 5
Step
Cluster vary job submission
Ending jobs using the ASP
Waiting for jobs to end
Image catalog synchronization
Writing changes to disk
Current time . . . :
Previous time . . :
Start date . . . . :
00:00:24
00:00:30
10/14/14
Elapsed time
00:00:00
00:00:03
00:00:21
Bottom

Figure 6-12 DSPASPSTS ENTRIES(*ALL) displays records of the previous varying operations
225
8249_HA.fm
Display User-Defined FS
User-defined file system . . . :
/dev/IASP01/qdefault.udfs
Owner . . . . . . . . . . .
Coded character set ID . . .
Case sensitivity . . . . . .
Default file format . . . .
Default disk storage option
Default main storage option
Creation date/time . . . . .
Change date/time . . . . . .
Path where mounted . . . . .
QSYS
37
*MONO
*ANY
*TYPE2
*NORMAL
*NORMAL
10/14/14
10/14/14
/IASP01
.
.
.
.
.
.
.
.
.
.
:
:
:
:
:
:
:
:
:
:
13:27:15
13:27:15
Description . . . . . . . . . :
Bottom
F3=Exit
F12=Cancel
Figure 6-13 Displaying UDFS information via DSPASPSTS command
For more information about DSPASPSTS command, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/dspaspsts.htm
6.4.2 Reduced UID/GID processing time during vary-on

In IBM i 7.2, the processing time for /QSYS.LIB objects is eliminated and the processing time
for IFS objects is minimized during vary-on an IASP. Addition to these elimination and
minimization, the processing time for correcting the mismatch of UID and GID is also
significantly reduced. It is still recommended that synchronizing the UID/GID between cluster
nodes by using administrative domain in order to eliminate all UID/GID processing time during
vary-on.
6.4.3 IASP assignment for consolidated backups

In IBM i 7.2, an existing IASP which is not in the cluster device domain can be attached to a
partition. This enhancement provides the benefit to a environment which utilize FlashCopy for
minimizing a backup window. Prior to IBM i 7.2, an IASP as a FlashCopy target must be
attached to a partition within the cluster device domain. For the environment that is configured
multiple production clusters and utilize FlashCopy in each cluster, each cluster requires a
backup partition for attaching the FlashCopy target and perform a backup operation on it.
With this enhancement, only one partition is needed as a backup partition for multiple
different clusters as shown in Figure 6-14.
226
8249_HA.fm
Figure 6-14 Attaching IASPs out of the cluster device domain to a single partition
Note that only one IASP can be attached to a single backup partition at a time and an IPL of
that partition is required before a different IASP is attached.
Prior to attach a different IASP to that partition, removing any existing IASPs and performing
CFGDEVASP ASPDEV(*ALL) ACTION(*PREPARE) command shown in Figure 6-15 is required on
that partition and IPL.
Configure Device ASP (CFGDEVASP)
ASP device . . . . . . . . . . .
Action . . . . . . . . . . . . .
*ALL
*PREPARE
Name, *ALL
*CREATE, *DELETE, *PREPARE
Figure 6-15 CFGDEVASP ASPDEV(*ALL) ACTION(*PREPARE) command
After an IPL, a FlashCopy IASP can be recognized on a single backup partition by connecting
it. Figure 6-16 shows 'Detect attached IASP disk units' screen of SST of a single backup
partition. In Figure 6-16, disk unit DD003 is the target FlashCopy LUN that contains the IASP
data on the production partition. By pressing Enter, the IASP which consists of DD003 is
configured. Figure 6-17 shows 'Display Disk Configuration Status' screen of SST which
shows the IASP exists and disk unit DD003 is assigned to it.
227
8249_HA.fm
Comfirm Configure IASPs

Press Enter to confirm Configure IASPs.
Press F12=Cancel to return.
Serial
ASP Unit Number
Resource
Type Model Name
1
1 Y9D7RD3HCKHG
6B22
050 DMP002
70
4002 50-050340F
2107 A81
DD003
Protection
Unprotected
Unprotected
Unprotected
Unprotected
Hot Spare
Protection
N
N
Figure 6-16 'Detect attached IASP disk units' screen of SST
Display Disk Configuration Status

Serial
ASP Unit Number
1
1 Y9D7RD3HCKHG
70
4001 50-050340F
Resource
Type Model Name
6B22
050
2107 A81
DMP002
DD003
Status
Unprotected
Configured
Unprotected
Configured
Hot Spare
Protection
N
N
Figure 6-17 'Display Disk Configuration Status' screen of SST
For more Information about multiple IASPs assignment to a single backup partition, see the
IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaly/rzalyattachiasp.h
tm
228
8249_Backup.fm
Chapter 7.
Backup and recovery

In this chapter, the following enhancements to backup and recovery at IBM i 7.2 are
discussed:
7.1, Newly-supported tape hardware on page 230
7.2, General save and restore functions provided by the OS on page 231
7.3, Backup, Recovery, and Media Services on page 235
229
8249_Backup.fm
7.1 Newly-supported tape hardware

IBM has released a new Tape Drive 3592 Model E08, which is also called TS1150 Tape Drive
or Jaguar-5 drive. It is supported in IBM i 7.2 for backup and recovery purposes, which allows
improvements in capacity, performance, and functions.
7.1.1 IBM 3592-E08 Tape Drive specifications

Table 7-1 shows the general specification of 3592-E08 compared to the previous models.
Table 7-1 3592-E08 Tape Drive specification compared to the previous models
3592 Model
Jag-1 3592
Jag-2 TS1120
Jag-3 TS1130
Jag-4 TS1140
Jag-5 TS1150
Maximum
Cartridge
Capacity
300 GB
700 GB
1.0 TB
4.0 TB
8-10 TB
Data Rate
40 MB/s
100 MB/s
160 MB/s
250 MB/s
Up to 360 MB/s
Cartridge
Support
JA/JJ/JW/
JR
JA/JJ/JW/
JR/JB/JX
JA/JJ/JW/
JR/JB/JX
JA/JJ/JW/
JR/JB/JX
JC/JY/JK
JC/JY/JK
JD/JZ/JL
Encryption
N/A
Yes
Yes
Yes
Yes
Partitioning /
LTFS
N/A
N/A
N/A
Yes
Yes
Server
Attachment
Fibre
FICON
ESCON
Fibre
FICON
ESCON
Fibre
FICON
ESCON
Fibre
FICON
ESCON
Fibre
FICON
7.1.2 Media types and compatibility

Media types
IBM TS1150 Tape Drive introduces new media types as below:
IBM 3592 Advanced Data Cartridge, Type D (JD)
Read/Write (R/W) Data Media
Up to 10 TB native capacity
IBM 3592 Advanced WORM Cartridge, Type D (JZ)
Write-Once Read-Many (WORM) Media
IBM 3592 Economy Cartridge, Type D (JL)
Read/Write (R/W) Data Media
In addition to new media types, two new logical formats are also introduced:
Jag-5 or EFMT5 for Base Jaguar 5 logical format
Jag-5 or EEFMT5 for Encrypted Jaguar 5 logical format
230
8249_Backup.fm
Media compatibility
The overall media supports for 3592-E08 are as follow:
JD, JZ, and JL media types with Read/Write support in the new Jag-5.
JC/JY/JK (Type C) media types with Read/Write support in Jag-5 format at improved
capacity and performance.
JC/JY/JK (Type C) media types with Read/Write support in Jag-4 format
JA and JB media types (including short and WORD versions) are not supported on the
3592-E08 drives.
7.1.3 Encryption capability

Compared to the previous model, there is no changes to the supported encryption methods
for 3592-E08. The supported encryption method supported in IBM i is Library Managed
Encryption (LME) using IBM Security Key Lifecycle Manager (SKLM), or previously known as
IBM Tivoli Key Lifecycle Manger (TKLM).
For more information about TS1150, see the IBM TS1150 product page at:
http://www-03.ibm.com/systems/storage/tape/ts1150/index.html
For more information about removable media on IBM i, see the IBM developerWorks at:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Remov
able%20Media%20on%20IBM%20i/page/IBM%20Removable%20Media%20on%20IBM%20i
7.2 General save and restore functions provided by the OS

IBM i 7.2 introduced new native save and restore functionality which can improve
recoverability of systems and assist with reducing the time necessary to perform saves and
restores. More granular control of system backup and recovery has also been implemented.
Minor changes relating to features which are obsolete also occurred. Details regarding the
OS changes as well as examples of some of these options are below.
7.2.1 Better control over journaling during restoration of objects

Defer ID (DFRID) during restore now includes journal start requests
At IBM i 7.2, new function has been added which allows for the DFRID processing to also
include journal start requests. This accommodates easier restoration of objects in libraries
which are on the system prior to the library containing the journal to which they should be
assigned being restored.
The types of objects whose journal start requests can be deferred are file, data area, data
queue, and library. When the deferred objects are processed in subsequent commands,
journaling is started if the journals are available at that time.
Start journaling (STRJRN) parameter added to commands and APIs

Multiple restore commands and APIs now include the parameter STRJRN which can apply to
new objects upon restore. The default is *YES, but if *NO is specified, two caveats to the
restore operation apply:
Journaling information will be restored whether journaling is selected to be started or not.
Chapter 7. Backup and recovery
231
8249_Backup.fm
Journaling will not be changed for any existing objects. The parameter applies to new
objects only.
7.2.2 Faster configuration of independent disk pools with CFGDEVASP

Prior to IBM i 7.2, when performing a disaster recovery of a system with independent disk
pools, an IPL was required in order to start IBM Navigator for i. The IPL was required because
the function for creation of the disk pool was available only through the web interface.
At the base release of IBM i 7.2, the command Configure Device ASP (CFGDEVASP) was
included and removes the requirement for an IPL during the recovery. Using this command,
ASPs can be created using the character-based interface. Use of this function has also been
included in the BRMS reports for supporting a system restoration containing multiple ASPs.
Point of technical clarification: The command CFGDEVASP was introduced at IBM i 7.1,
technology refresh 4. It is not included the base release of IBM i 7.1, but it is included in the
base release of IBM i 7.2. The *PREPARE action is not available at any level of IBM i 7.1.
The command allows for creation, deletion, and preparation of a new ASP. Figure 7-1 shows
an example of how an ASP can be created using the character-based interface.
Configure Device ASP (CFGDEVASP)
ASP device
Action . .
ASP type .
Protection
Encryption
Disk units
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
+
. .
. .
. .
. .
. .
. .
for
. . . . . . > MYNEWASP
. . . . . . > *CREATE
. . . . . . > *PRIMARY
. . . . . .
*NO
. . . . . .
*NO
. . . . . .
*SELECT
more values
Name, *ALL
*CREATE, *DELETE, *PREPARE
*PRIMARY, *SECONDARY, *UDFS
*NO, *YES
*NO, *YES
Name, *SELECT
Figure 7-1 Initial display from the Configure Device ASP (CFGDEVASP) command
Once the data has been entered, if *SELECT is chosen for the Disk Units parameter,
proceeding to the next screen allows the selection of non-configured disk units. Figure 7-2
shows the selection of the units as well as the processing of the ASP creation indicated at the
bottom of the display.
232
8249_Backup.fm
Select Non-Configured Disk Units

ASP device . . . . . . . . . . . . . . . :
Selected capacity . . . . . . . . . . . :
Selected disk units . . . . . . . . . . :
MYNEWASP
55929
3

1=Select
Opt
1
1
1
Resource
Name
DPH001
DPH002
DPH003
Serial Number
Y77MMXCMPQE5
Y3PL6FPHL33X
YZUG2T3V6YG8
Type
6B22
6B22
6B22
Model
0050
0050
0050
Capacity
18643
18643
18643
Rank
002
002
002
Eligible
Yes
Yes
Yes
Bottom
F1=Help
F9=Calculate Selection
F11=View 2
F12=Cancel
Configuration of ASP device MYNEWASP is 99% complete.
Figure 7-2 Display allowing selection of non-configured disk units for ASP creation
Once the command processing is complete, a message stating the results is presented. The
ASP can then be varied on and used.
7.2.3 Spooled file save enhancements

Save Changed Object (SAVCHGOBJ) supports saving spooled files
Saving of spooled files is now supported in the SAVCHGOBJ command at IBM i 7.2 by
specifying *NEW for the SPLFDTA parameter. There are various requirements and situations
which may apply depending on the Reference Date (REFDATE) and Reference Time
(REFTIME) specified on the command.
For each output queue that is saved, spooled file data created since the Reference Date
and Reference Time is saved.
Output queues which contain spooled files created after the Reference Date and
Reference Time will be considered changed and will be saved.
Output queues which contain spooled files with creation dates and times before the
Reference Date and Reference Time will not be considered changed and will not be
saved.
Save Object List API can now specify spooled file expiration
New function has been added to the Save Object List API (QSRSAVO) which allows for expiry
of spooled files once theyve been saved. See this detailed description of the API and its
improved options at the IBM i Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/qsrsavo.htm
233
8249_Backup.fm
7.2.4 Select parameter (SELECT) added to various commands

The Select (SELECT) parameter has been added to many save and restore commands, as
well as APIs. This new parameter allows for more granular saves and restores. Figure 7-3
shows an example of the new parameter in a Save Object (SAVOBJ) command. The SELECT
parameter can be used up to 300 times per command or with a *USRSPC input. The
300-item limit still applies even when utilizing a user space.
When using a user space, it must define the parameters in the format used by the Save
Object List (QSRSAVO) API. A link describing the API and necessary user space formatting
requirements are located in the section Save Object List API can now specify spooled file
expiration.
Save Object (SAVOBJ)
Select:
Include or omit .
Object . . . . . .
Library . . . .
Object type . . .
Object attribute .
File member . . .
+ for
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
more values
*ALL
*ALL
*ALL
*ALL
*ALL
*USRSPC, *INCLUDE, *OMIT

Name, generic*, *ALL
Name, generic*, *ALL
*ALL, *ALRTBL, *BNDDIR...
Character value, *ALL, *BLANK
Name, generic*, *ALL, *ALLMBR
Figure 7-3 Section of the Save Object (SAVOBJ) command with the new SELECT parameter
7.2.5 TCP/IP configuration data saved automatically

Whenever library QUSRSYS is saved with the Save Library (SAVLIB) or Save Changed
Objects (SAVCHGOBJ) commands, the current TCP/IP configuration information will also be
retrieved and saved. The step being performed automatically to gather the systems current
configuration information is the Retrieve TCP/IP Information (RTVTCPINF) command.
If a system needs to be reloaded from distribution media, the TCP/IP configuration
information can be updated by restoring the QUSRSYS library as part of the user data
restore, and then running the command UPDTCPINF LIB(QUSRSYS). Figure 7-4 shows an
example of the command structure.
Update TCP/IP Information (UPDTCPINF)
Library . . . . . . . . . . . . > QUSRSYS
Type of information . . . . . .
*ALL
Name
*ALL, *TCP, *TCPCFG...
Figure 7-4 View of the Update TCP/IP Information (UPDTCPINF) command
Additional subsetting of what is restored during UPDTCPINF can be performed by specifying

desired items on the Type of Information parameter.
234
8249_Backup.fm
Details on this command and its function are available at this location in the IBM i Knowledge
Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/updtcpinf.htm
Important: TCP/IP must be inactive when executing the UPDTCPINF command.
7.2.6 Even better IFS save performance with Asynchronous Bring

The Asynchronous Bring (ASYNCBRING) parameter is part of the base function of IBM i 7.2
and is included in the SAV command. By specifying *YES on the parameter, there is potential
to improve the performance of some save operations.
Asynchronous bring will attempt to pre-load items in to memory to improve save performance.
Note: In situations where a large number of objects reside in a single directory, few objects
qualify for the save, or the system is memory constrained, the ASYNCBRING parameter
being set to *YES may actually degrade performance. Testing is recommended to ensure
the desired results are achieved.
7.2.7 Modifications on the SAVE and RESTORE menus

Various items have been changed on the SAVE and RESTORE menus.
Removed from SAVE menu: save storage and save calendars
Removed from RESTORE menu: restore calendars
Additionally, new prompting fields have been added to some of the commands when executed
from the SAVE or RESTORE menu to increase the customization of the particular save or
restore command.
7.2.8 Removal of obsolete functions

The Save Storage (SAVSTG) and Restore Storage (RSTSTG) commands have been
removed from IBM i 7.2.
7.3 Backup, Recovery, and Media Services

Many new functions have been introduced for BRMS at IBM i 7.2. The sections below include
details on some of these and how to utilize them.
Be sure to visit the BRMS DeveloperWorks website for many detailed examples and usability
tips which are much too volumes to list here. The site also includes up-to-the-minute data of
new PTFs and enhancements. The website can be found at:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Backu
p%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i
235
8249_Backup.fm
7.3.1 BRMS Enterprise

BRMS Enterprise was covered in significant detail in a Redpaper published prior to this
Redbook. For overall functionality and usage tips, reference that Redpaper.
http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/redp4926.html
Reminders: BRMS Enterprise considers the system managing the remaining systems in
the group as the hub. All other systems participating are nodes. It is not necessary for
systems to be in a BRMS network for them to participate in BRMS Enterprise. In fact, even
systems in various BRMS networks can participate in the same BRMS Enterprise
instance.
New features specific to IBM i 7.2 are described below.
Q1ABRMENT subsystem for specific BRMS Enterprise functions

A new subsystem called Q1ABRMENT will run in order to process specific jobs and tasks
related to BRMS Enterprise. This is in addition to the standard Q1ABRMNET subsystem
used for BRMS networking.
Auto-refresh of the node status via IBM Navigator for i

At IBM i 7.2, BRMS Enterprise provides an automatic refresh interval for the list of nodes.
Default configurations have no automatic refresh selected - it must be manually configured
post-installation for the value desired. The base installation value is shown in Figure 7-5.
Figure 7-5 Panel showing the default value for automatic refresh within BRMS Enterprise
To modify the value of the automatic refresh frequency, perform the following steps:
1. Inside IBM Navigator for i, select Backup, Recovery, and Media Services.
2. Once in the Backup, Recovery, and Media Services section, select Enterprise Services
3. Click on Hub Administration and a panel shown in Figure 7-6 on page 237 will appear.
Modify the value to the desired setting and click OK at the bottom of the panel
236
8249_Backup.fm
Figure 7-6 The drop-down in Hub Administration which allows setting the refresh interval
4. After clicking OK, the panel will return to the Enterprise view. The selection made on the
Hub Administration screen should now appear at the top of the pane, as shown in
Figure 7-7.
Figure 7-7 The BRMS Enterprise hub center with an automatic refresh of 30 minutes selected
Print Report using BRM (PRTRPTBRM) supported for reporting

In addition to new options being added to Print Report using BRM (PRTRPTBRM) at IBM i
7.2, the report is available with additional options within BRMS Enterprise. Reports can be
defined within BRMS Enterprise and processed against all nodes in the enterprise, not just
nodes in a particular systems BRMS network.
Note: The functionality to perform reporting for all systems in the BRMS Enterprise group
exists only in the GUI.
To process the reports against systems in the BRMS Enterprise configuration, select *ENT as
the target system as shown in Figure 7-8 on page 238.
237
8249_Backup.fm
Figure 7-8 Choosing *ENT as an option for reporting within BRMS Enterprise
Failed Control Group View to identify backup problems faster

BRMS Enterprise provides a consolidated view of backup status for multiple systems. This
allows a user to quickly determine if backups are occurring properly, and if not, make it
simpler to take steps to remediate the situation.
To view the list of failed backups, enter the BRMS Enterprise section of IBM Navigator for i.
Once there, click on Failed Backups. A screen will be presented similar to the one in
Figure 7-9 which shows that one of the systems - Appn.reo - has had a failed backup on the
current day.
Figure 7-9 A view of a BRMS Enterprise group containing a system with a failed backup
More detail can be reviewed about the system and its failed backups by clicking on the widget
to the right of the system name, as shown in Figure 7-10.
Figure 7-10 System-specific options available from the Failed Backups panel
After clicking on the View failed backups item, another panel will appear which allows you to
choose various options for subsetting. Either a date range or specifying the most recent
failure are available options. These choices are shown in Figure 7-11.
238
8249_Backup.fm
Figure 7-11 Options available for subsetting a view of failed backups
Once the appropriate subsetting options have been chosen, a panel as shown in Figure 7-12
on page 239 will be presented. This panel allows options such as viewing the BRMS logs,
backup histories, failed backup histories, and producing a report of the failure.
Figure 7-12 BRMS Enterprise view of an unsuccessful control group on a node
7.3.2 Usability improvements at IBM i 7.2

Many features which at prior releases were addressed by running programs or creating data
areas are now a part of BRMS screens and commands at IBM i 7.2.
Some of these items are listed Table 7-2.
Table 7-2 Usability improvements in IBM i 7.2
Function
Prior Release
IBM i 7.2
Modification of BRMS Flight

Recorder size
Call programs with various

parameters
Available in System Policy
Allow volumes marked for

duplication to be moved
Call programs with various

parameters
Available in Move Policies
Restore of spooled files from

different time zones
Creation of data areas required

based on needs
BRMS now handles time zone

data automatically
Disable the deleted library block

on recovery reports
Creation of data area
Parameter within report

creation command
239
8249_Backup.fm
7.3.3 Backup function enhancements

Backup lists now allow for *ALLUSR
To support more granular saves, at IBM i 7.2, a backup list can now support an entry of
*ALLUSR. This allows for specifying *ALLUSR as the main inclusion, and then omitting
specific objects or groups of objects. Additionally, by putting *ALLUSR in a backup list, the
libraries will reflect their individual save times rather than all libraries within the *ALLUSR
selection showing the same save timestamp.
See Object-level omits available in 5250 interface on page 240 for more details on
performing object-level omits at IBM i 7.2.
Object-level omits available in 5250 interface

Prior to IBM i 7.2, excluding specific objects within libraries required usage of the BRMS GUI.
At IBM i 7.2, this is no longer required.
However, any control groups with object-level omits defined by the BRMS GUI at IBM i 7.1 or
an earlier release must continue to be managed with the BRMS GUI. In order to manage a
control groups object-level omits in either the 5250 interface or the GUI, the control group
must be recreated at IBM i 7.2 and exclusions using BRMS lists must be implemented.
Note: Omits which are specified via the BRMS Backup Policy will be ignored by any control
group that uses a BRMS list with object omits.
An example is in Figure 7-13 showing an object list which will save the *ALLUSR set of
libraries, but exclude specific objects within various libraries.
Display Object List
Use . . . . . . . . . :
List name . . . . . . :
Text . . . . . . . . :
Seq
10
20
30
40
Library
*ALLUSR
ARCHIVE
YEAREND
MUSIC
REO
*BKU
ALLUSROMIT
Save *ALLUSR but add omits
Object
*ALL
BIGFILE*
PREMERGER
*ALL
Type
*ALL
*FILE
*FILE
*ALL
Attribute
*ALL
*ALL
*ALL
*ALL
Member
*ALL
*ALL
*ALL
*ALL
Inc/Exc
*INC
*EXC
*EXC
*EXC
Figure 7-13 BRMS object list containing the *ALLUSR value along with specific exclusions
The same list can be accessed and modified via IBM Navigator for i. Pictured in Figure 7-14 is
the same ALLUSROMIT object list accessed via that interface.
240
8249_Backup.fm
Figure 7-14 View for the same object list within IBM Navigator for i
Note: In IBM i 7.2, to enable the functionality for include/exclude within BRMS object lists,
PTF SI53306 or its most current supersede is required.
Control groups can save libraries in order of size

By default, BRMS saves libraries alphabetically. In an effort to potentially improve save
performance, especially in environments where multiple tape devices are used in parallel, a
value of *SIZE can be chosen.
When specifying *SIZE for the Sort By parameter in the control group attributes - or
alternatively in the backup policy if the control group specifies *BKUPCY for its attribute
retrieval - the system will save the libraries in order of largest to smallest based upon size
attributes acquired during prior save operations.
Note: If a save by *SIZE is chosen and a new library which has not been saved by BRMS
is selected to be saved, the new library will be saved after all libraries with known sizes
have been processed. BRMS is unable to acquire the size and include the new library in a
sort order until it has been saved once and its size determined.
Save contents of data queues

In addition to the data queue objects themselves, BRMS can now be instructed to save the
contents of the data queues.
To activate this option, simply change the control group attribute of Save Queue Data to
*DTAQ. If this is desired on a system-wide level, ensure the control group is set to *BKUPCY
for Save Queue Data and change the parameter in the backup policy instead.
Failure to reach restricted state recovery options

Certain situations exist where intentions for a restricted state save do not function as desired.
In this case, the system can potentially become hung in a manner where it is not entirely
down, but unable to restart. This usually results in a skipped Save System (SAVSYS) section
of the backup, as well as unpredictable results when completed. BRMS has multiple new
options to assist in handling these situations in a more automatic manner.
241
8249_Backup.fm
Abnormal end delay time option in System Policy

BRMS includes a new option at IBM i 7.2 which can issue abnormal job ends against
processes which fail to terminate during normal shutdown processes. The option is available
in the System Policy and is shown in Figure 7-15 on page 242.
V7R2M0
Change System Policy
REO

End all subsystems options
Controlled end delay time . . . . . . 1200
Abnormal end delay time . . . . . . . 30
End servers wait time . . . . . . . .
0
1-99999 seconds,*IMMED
10-999 minutes,*NOLIMIT
0-9999 seconds
Figure 7-15 Subsystem end options at IBM i 7.2 in BRMS System Policy
By using this function, the system can issue End Job Abnormal (ENDJOBABN) commands
against jobs which have not ended normally using controlled options.
The Controlled end delay time field is used to determine how long to wait before ending
active jobs immediately. Once active jobs have started to end with the end job immediate
option, the Abnormal end delay time field will be used to determine how long to wait before
ending active jobs abnormally.
Note: Issuing ENDJOBABN in any situation will cause the subsequent IPL to be flagged as
abnormal. This can significantly increase the amount of time for the IPL to process.
Alternate option for BRMS behavior when unable to restrict system

BRMS can now be configured to fail rather than bypass the Save System (SAVSYS)
command if the system is unable to reach restricted state.
To enable this function on a system-wide basis, run the following command:
CRTDTAARA DTAARA(QUSRBRM/Q1ANOSYSBP) TYPE(*CHAR) LEN(1)
To enable this function for only a specific job, (for example, create the data area in a control
group exit prior to running the SAVSYS command), run the following command:
CRTDTAARA DTAARA(QTEMP/Q1ANOSYSBP) TYPE(*CHAR) LEN(1)
Note: When desiring only in a specific job, a good example would be creating the data
area in a control group exit prior to running the SAVSYS command.
BRMS can automatically IPL if controlling subsystem unable to start

BRMS can also be configured to automatically IPL the system in the event a CPF1099 is
received when attempting to restart the controlling subsystem. This message would be
received if the system previously attempted to restrict the machine, but has thus far been
unable to reach a restricted state. The only recovery option in this situation is to IPL. BRMS
can handle this on its own now, potentially saving hours of downtime.
If BRMS receives a CPF1099 when it tries to start the controlling subsystem and data area
QUSRBRM/Q1AIPLSUB exists, the system will be IPLed. IPL options from the control group
are used. These options may be referencing the BRMS Backup Policy or even the BRMS
System Policy.
242
8249_Backup.fm
Important: The Control Group does not need to be set to IPL *YES in order for this IPL to
occur.
To enable this functionality, run the following command:
CRTDTAARA DTAARA(QUSRBRM/Q1AIPLSUB) TYPE(*CHAR) LEN(1)
Automatic restart on abnormal ends of STRBKUBRM

Options now exist on the STRBKUBRM command to allow for automatic retries if the backup
ends abnormally.
Allow Retry - ALWRTY
Provides choices of *NO or *YES.
Retry Time Limit - RTYTIMLMT
If Allow Retry is set to *YES, if an abnormal end occurs within the specified time limit
after the control group has begun processing, then the backup control group will be
retried. Allowable values are *NOMAX and 1-99999 where the 1-99999 are in minutes.
Retry Starting Sequence - RTYSTRSEQ
Three choices are available: *ERRSEQ, *STRSEQ, or *NXTSEQ. If *ERRSEQ is selected,
the sequence which received the abnormal end will be retried. If *STRSEQ is selected, the
entire control group will be started from the beginning. If *NXTSEQ is selected, the next
sequence in the control group will be processed, skipping the one which ended
abnormally.
Journal receiver save exclusions

Function exists in BRMS across multiple versions of IBM i to allow saving of only changed or
detached journal receivers using the values of *CHGJRNRCV or *DTCJRNRCV in a control
group. These special values now have been modified to process journals from libraries with
names that start with the letter Q.
In IBM i 7.2, exclude entries can be specified in object list QCHGJRNRCV or QDTCJRNRCV
to exclude certain journals from the save.
Numerous customization options exist for this particular feature. The most updated
information and required PTFs are available at the BRMS wiki page on DeveloperWorks.
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Backu
p%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i
Incremental spool file backup support

At IBM i 7.2, BRMS now includes the ability to perform incremental spooled file saves without
requiring the use of a BRMS *SPL list.
Users who have previously handled spool file saves using BRMS lists may find that simply
changing the attribute on a different control group (one which contains the outqueues
needed) to save spool data will meet their needs of saving spool files. This could potentially
save time and effort by reducing the number of save operations required.
243
8249_Backup.fm
7.3.4 Recovery function enhancements

Recovery reports now use command for ASP creation
In 7.2, recovery reports created using the Start Recovery using BRM (STRRCYBRM) or Start
Maintenance for BRM (STRMNTBRM) command have been enhanced to use the Configure
Device ASP (CFGDEVASP) command to configure independent auxiliary storage pools
(IASP). The step to IPL the system to configure IASPs has been removed from recovery
reports.
See 7.2.2, Faster configuration of independent disk pools with CFGDEVASP on page 232
for details of the command and how it can improve recovery times.
Spool file restore based on time zone

At version 7.2 of IBM i, BRMS now keeps track of the time zone in which a spooled file was
created. This assists with restoration of spooled files based on time, especially when being
performed on a system in a different time zone.
The time zone is now tracked within the saved spooled file details file in field OQTIMZON.
Note: The time zone in which the spooled file was created is not available for viewing
within standard BRMS screens.
Restoring libraries using BRM (RSTLIBBRM) with *RSTLST

When performing a library restoration using BRMS, a list of libraries can be specified in a
BRMS list. Once that list has been defined, the list can be specified and restoration
processed. To create the list, issue the command WRKLBRM and create a new *BKU list of
type *OBJ. Specify each library for restore in the newly-created list.
One example where this could be useful is if a restore is integral to a compiled program.
Rather than needing to modify the program code each time a library needed to be removed or
added to the process, all that would be necessary is to modify the BRMS object list.
In the Example 7-1 the command syntax for saving 15 libraries is shown.
Example 7-1 Restoration of 15 libraries using RSTLIBBRM
RSTLIBBRM SAVLIB(DATALIB001 DATALIB002 DATALIB003 OBJLIB001A OBJLIB002A

OBJLIB003A CUSTOM123 ARCH_2013 ARCH_2012 ARCH_2011 ARCH_2010 SECURE UNSECURE
MISC_STUFF MYNEWDATA) DEV(TAPMLB01)
Using a BRMS *RSTLST, the command is significantly smaller and now can easily be
modified using the BRMS list rather than needing to modify a program - an example of this
improvement is shown in Example 7-2.
Example 7-2 Restoration of libraries specified in a *RSTLST using RSTLIBBRM
RSTLIBBRM SAVLIB(*RSTLST) DEV(TAPMLB01) RSTLST(MYRSTLST)
7.3.5 Media services enhancements

Reset move cycle in Move Policy
Move policy in IBM i 7.2 introduces *RESET as a new value for Duration field. This *RESET
means that the media will remain in that location sequence until it expires or until another
244
8249_Backup.fm
save is written to the media. If no writes are done to the media, the media stays in this
location until it expires and then returns to the home location. On the other hand, If a write is
done to the media while in this location, the move pattern is reset to the first move sequence
and the creation date of the media is set to the current date and time.
Note: Move policy sequences after a sequence with *RESET duration will not be used.
Figure 7-16 shows the example of *RESET in Change Move Policy.
Change Move Policy
Move policy . . . . . . . . . :
Home location . . . . . . . . .
Use container . . . . . . . . .
Verify moves . . . . . . . . . .
Calendar for working days . . .
Calendar for move days . . . . .
Move marked for duplication . .
Text . . . . . . . . . . . . . .
OFFSITE
*SYSPCY
*NO
*YES
*ALLDAYS
*ALLDAYS
*NO
Move Policy
UT30P05
Name, *SYSPCY, *ORIGIN, F4 list

*YES, *NO
*YES, *NO
Name, *ALLDAYS, F4 for list
*NO, *YES
01

Seq
10
20
Location
LOC01
LOC02
Duration
10
*RESET
Container Action
Bottom
F3=Exit
F4=Prompt
F5=Refresh
F12=Cancel
Figure 7-16 Reset move cycle in Change Move Policy screen
This feature is also available in IBM Navigator for i as shown in Figure 7-17 on page 246.
245
8249_Backup.fm
Figure 7-17 Reset move cycle in IBM Navigator for i
Support for moving media marked for duplication

IBM i 7.2 allows you to move the media that is marked for duplication. You can see this feature
in Change Move Policy screen with the Move marked for duplication as shown in
Figure 7-18. If this parameter is set to *YES, the move policy will include volumes marked for
duplication during media movement.
Change Move Policy
Move policy . . . . . . . . . :
Home location . . . . . . . . .
Use container . . . . . . . . .
Verify moves . . . . . . . . . .
Calendar for working days . . .
Calendar for move days . . . . .
Move marked for duplication . .
Text . . . . . . . . . . . . . .
UT30P05
OFFSITE
*SYSPCY
Name, *SYSPCY, *ORIGIN, F4 list
*NO
*YES, *NO
*YES
*YES, *NO
*ALLDAYS
*ALLDAYS
*YES
*NO, *YES
Entry created by BRM configuration

Seq
10
Location
Duration
VAULT
*EXP
Container Action
Bottom
F3=Exit
F4=Prompt
F5=Refresh
F12=Cancel
Figure 7-18 Change Move Policy with optIon to move marked for duplication
246
8249_Backup.fm
This feature is also available in IBM Navigator for i as shown in Figure 7-19.
Figure 7-19 Move policy parameters in IBM Navigator for i
Initialize media on expiration in Media Class

IBM i 7.2 supports the option to initialize media on expiration in setting up the media class. If
this parameter is set to *YES, BRMS will automatically initialize the media after it is expired.
Initialization will occur during the STRMNTBRM process and will require the media to be
mounted on a device.
Figure 7-20 shows the Change Media Class screen, enhanced with Initialize media on
expiration parameter.
247
8249_Backup.fm
Change Media Class

Media class . . . . . . . . . . . :
SAVSYS

Density . . . . . . . . . . . .
Media capacity . . . . . . . .
Unit of measure . . . . . . .
Mark for label print . . . . .
Label size . . . . . . . . . .
Label output queue . . . . . .
Library . . . . . . . . . . .
Shared media . . . . . . . . .
Write once media . . . . . . .
Initialize media on expiration.
Text . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*UDF
*DENSITY
F4 for list
*DENSITY, Number nnnnn.nn
1=KB, 2=MB, 3=GB
*NONE
*NONE, *MOVE, *WRITE
1
1=6 LPI, 2=8 LPI, 3=9 LPI
*SYSPCY
Name, *SYSPCY, *PRTF
Name, *LIBL
*NO
*YES, *NO
*NO
*YES, *NO
*NO
*NO, *YES
Entry created by BRM configuration
More...
F3=Exit
F4=Prompt
F12=Cancel
Figure 7-20 Change Media Class screen with parameter for expired media initialization
This feature is also available in IBM Navigator for i as shown in Figure 7-21.
Figure 7-21 Initialize media on expiration in IBM Navigator for i
Submit DUPMEDBRM into batch job

IBM i 7.2 enhances the Duplicate Media using BRM (DUPMEDBRM) command with the Submit
batch options parameter, allowing users to run media duplication process in batch and
indicate the number of media sets to be produced. The job queue and the job description for
this batch job submission will use the settings specified in the system policy.
248
8249_Backup.fm
Figure 7-22 shows the DUPMEDBRM screen with submit batch options.
Duplicate Media using BRM (DUPMEDBRM)
From system . . . . . . . . . .
*LCL
Submit batch options:
Submit to batch . . . . . . . > *YES
Media sets . . . . . . . . . . *MEDSET
*NO, *YES
1-99, *MEDSET
To volume identifier
+ for
Retain object detail
Expiration date . .
Move policy . . . .
Media class . . . .
Location . . . . . .
Secure volume . . .
Required volumes . .
. . . . . .
more values
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
*MOUNTED
*NO
*MEDPCY
*MEDPCY
*MEDPCY
*MEDPCY
*MEDPCY
*MEDPCY
F12=Cancel
*NO, *YES
Date, *MEDPCY, *PERM...
*MEDPCY, *NONE, OFFSITE
*MEDPCY, *SYSPCY ...
*MEDPCY, *ANY, *HOME ...
*MEDPCY, *NO, *YES
1-9999, *MEDPCY, *NONE
More...
Figure 7-22 DUPPMEDBRM command with submit batch options
This new DUPMEDBRM enhancement is helpful in the following cases:

1. There are multiple media sets produced from backup processes.
In order to have multiple media sets duplicated using multiple tape resources, users can
easily issue only one DUPMEDBRM command with Submit to batch parameter set to *YES
and Media sets parameter set to a desired number of output media set.
2. Backup and recovery processes that use ProtecTier TS7650 Virtual Tape Library (VTL).
Users that utilize VTL for their backup and recovery usually have multiple tape resources
for parallel save and restore. When duplicating multiple virtual tapes to physical tapes,
they usually expect less physical tapes produced then the virtual ones. With this
enhancement, Media sets parameter enables users to specify the number of output media
sets to be less then the number of input media sets. Therefore they can have less media
sets produced as physical tapes.
Note: DUPMEDBRM in batch process does not work for auto duplication.
For more information about DUPMEDBRM command, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/dupmedbrm.htm?lang=e
n
249
8249_Backup.fm
7.3.6 Maintenance enhancements

Reorganize BRMS database using batch job
When performing BRMS maintenance using Start Maintenance for BRM (STRMNTBRM)
command, IBM i 7.2 enables you to set Reorganize BRMS database (RGZBRMDB) parameter to
*BATCH as shown in Figure 7-23 on page 250. This will allow you to submit database
reorganization to a batch job. The job queue and the job description are specified in the
system policy for BRMS submitted jobs.
When this is used, STRMNTBRM has potential to complete processing much sooner than the
batch job performing the reorganization. Normal BRMS activity may be resumed while the
batch job is still active.
Start Maintenance for BRM (STRMNTBRM)
Audit system media . . . . . . .
*NONE
+ for more values
Change BRM journal receivers . . *YES
Print expired media report . . .
*YES
Print version report . . . . . . *EXPMED
Print media information . . . . *YES
Print recovery reports . . . . . *ALL
+ for more values
Recovery locations . . . . . . . *ALL
+ for more values
Print system information . . . .
*NO
Reorganize BRMS database . . . . > *BATCH
Auto-retrieved objects:
Refree . . . . . . . . . . . .
*NO
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
*YES, *NO
*YES, *NO
*EXPMED, *NO, *YES
*YES, *NO
*ALL, *NONE, *RCYACT...
Name, *ALL, *HOME
*NO, *YES
*NO, *YES, *BATCH
*NO, *YES
Bottom
Figure 7-23 RGZBRMDB parameter in STRMNTBRM command
Figure 7-24 shows the option to run BRMS database reorganization in IBM Navigator for i. To
modify it, click Backup, Recovery and Media Services then click Advanced button. Click
the small arrow beside the Backup, Recovery, and Media Services for IBM i, the click Run
Maintenance.... Click Option File Management and change the Reorganize BRMS
database value.
250
8249_Backup.fm
Figure 7-24 Reorganize BRMS database option in IBM Navigator for i
Additional parameters in RMVMEDIBRM

As shown in Figure 7-25, IBM i 7.2 release adds more parameters in Remove Media Info from
BRM (RMVMEDIBRM) command to give users more control on files detail and how long the users
wish to retain the information.
The following are the additional parameters in RMVMEDIBRM:
Link level detail
Link level detail parameter specifies when you want to remove directory and file level detail
for media records in the media content information.
Spooled file level detail
Spooled file level detail specifies when you want to remove spooled file level detail for
media records in the media content information. This will only apply to spooled file detail
that was created by specifying *YES for the Spooled file data (SPLFDTA) parameter on the
SAVLIBBRM/SAVOBJBRM command or in the control group attributes. However, spooled file
lists will not be affected as you must have detail history to restore them.
Folder level detail
Folder level detail specifies when you want to remove folder level detail for media records
in the media content information.
251
8249_Backup.fm
Remove Media Info from BRM (RMVMEDIBRM)

Media contents . . . . . .
Object level detail . . .
Link level detail . . . .
Spooled file level detail
Folder level detail . . .
F3=Exit F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
*EXP
*MEDCON
*OBJDTL
*MEDCON
*OBJDTL
F12=Cancel
*EXP, *REUSE
1-9999, *MEDCON
1-9999, *OBJDTL, *MEDCON
1-9999, *MEDCON, *OBJDTL
1-9999, *OBJDTL, *MEDCON
Bottom
Figure 7-25 Additional parameters in RMVMEDIBRM command
For more information about RMVMEDIBRM command and its parameter values, see the IBM
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/rmvmedibrm.htm?lang=
en
7.3.7 BRMS GUI in IBM Navigator for i enhancements

In IBM i 7.2, BRMS gets GUI enhancements in IBM Navigator for i. It improves the usability of
BRMS GUI functions as well as its coexistence with functions in green screen.
BRMS policies
IBM Navigator for i enables the users to view or modify various BRMS policies, such as:
System policy
Backup policy
Archive policy
Retrieve policy
Recovery policy
Figure 7-26 shows the policy properties available in IBM Navigator for i. To view or modify
these policies, click File Systems Backup Recovery and Media Services. Click the small
arrow next to Backup, Recovery and Media Services for IBM i, then choose the policy you
want to view or modify.
252
8249_Backup.fm
Figure 7-26 Various BRMS Policies in BRMS Navigator for i
253
8249_Backup.fm
System Policy
System Policy in 7.2 IBM Navigator for i provides the same functionality as in 5250 green
screen with Work with System Policy (WRKPCYBRM TYPE(*SYS)) command. It allows you to
configure the media, notification, IPL options, presentation, and so on. The overall System
Policy Properties in IBM Navigator for i is shown in Figure 7-27 on page 254.
Figure 7-27 BRMS System Policy in IBM Navigator for i
254
8249_Backup.fm
Backup Policy
Backup Policy Properties in 7.2 IBM Navigator for i enables the users to look ahead into what
parameters or information are set in system policy. Figure 7-28 on page 255 shows the
example of seeing System Policy value while modifying Backup Policy.
Figure 7-28 BRMS Backup Policy in IBM Navigator for i
255
8249_Backup.fm
Archive Policy
Similar to Backup Policy, Archive Policy in IBM Navigator for i also allows you to look ahead
into what parameters or information are set in system policy as shown in Figure 7-29 on
page 256.
Figure 7-29 BRMS Archive Policy in IBM Navigator for i
256
8249_Backup.fm
Retrieve Policy
IBM Navigator for i in 7.2 release allows you to view and modify the parameters used in
BRMS retrieval process as in green screen. Figure 7-30 on page 257 shows the Retrieve
Policy properties that can be modified in IBM Navigator for i.
Figure 7-30 BRMS Retrieve Policy in IBM Navigator for i
257
8249_Backup.fm
Recovery Policy
7.2 Navigator for i also allows you to view and modify the parameters of BRMS Recovery
Policy as in green screen. Figure 7-31 on page 258 shows the Retrieve Policy properties that
can be modified in IBM Navigator for i.
Figure 7-31 BRMS Recovery Policy in IBM Navigator for i
Volume Initialization and Ignoring Active Files

IBM Navigator for i in 7.2 release provides the select/deselect all for initialize and
select/deselect all for Ignore Active Files. They are very useful in the case you have large
number of volumes for initialization and ignoring active files. To perform this feature, click File
Systems Backup Recovery and Media Services, click the small arrow next to Volumes
then click Add. Figure 7-32 on page 259 shows the Add Volumes - Initialize Volumes page,
where you can select the actions for: Select all for Initialize, Deselect all for Initialize,
Select all Ignore Active Files, and Deselect all for Ignore Active Files. They will check or
uncheck the Initialize or Ignore Active Files checkboxes.
258
8249_Backup.fm
Figure 7-32 Checkboxes for marking volume for Initialize and Ignore Active Files
7.3.8 Miscellaneous BRMS enhancements

Performance enhancement in INZBRM *RUNPRDINZ
BRMS product initialization process is required after you performed a product update or when
you received BRM40A2 - BRMS product initialization required. As this initialization
process usually takes a long time to complete, BRMS in IBM i 7.2 release is enhanced to
allow you to perform BRMS product initialization faster than in the previous releases. The new
INZBRM OPTION(*RUNPRDINZ) command will only rebuild a logical file when the whole physical
file is changed. If there is no physical file change, BRMS product initialization will not process
anything. In addition, this product initialization will use Alter Table on detail files, instead of
creating more logical files. These two changes will improve the overall BRMS product
initialization.
Improved help text in BRMS functions

IBM i 7.2 release provides the improvements of help texts in BRMS functions. These will
equip BRMS users with more detailed and complete explanations on BRMS functions.
Control Group in PRTRPTBRM

Figure 7-33 on page 260 shows the improved help text, which explains the Control Group
options in PRTRPTBRM TYPE(*CTLGRPSTAT) command.
259
8249_Backup.fm
Print Report using BRM (PRTRPTBRM)

..............................................................................
:
Control Group (CTLGRP) - Help
:
:
:
: Specifies which backup control group should be included in the report.
:
: This parameter is ignored when parameter Type (TYPE) is not *CTLGRPSTAT. :
: Note: Backups produced by running STRBKUBRM commands will be included in :
: the report for all values except *NONE.
:
:
:
: *ALL
:
:
All backups produced by running STRBKUBRM will be included in this
:
:
report. Note: The output generated by CTLGRP(*NONE) will not be
:
:
included in this report.
:
:
:
: *SYSTEM
:
:
Backups produced by the *SYSTEM control group will be included in
:
:
the report.
:
:
:
: *BKUGRP
:
:
More... :
: F2=Extended help F3=Exit help F10=Move to top F11=Search Index
:
: F12=Cancel
F13=Information Assistant
F14=Print help
:
:
:
:............................................................................:
Figure 7-33 Control Group help text in PRTRPTBRM TYPE(*CTLGRPSTAT) command
Data Compaction in DUPMEDBRM

Figure 7-34 on page 261 shows the added help text in Duplicate Media using BRM
(DUPMEDBRM) command, which explains the Data compaction parameter in detail.
260
8249_Backup.fm
Duplicate Media using BRM (DUPMEDBRM)

Save media information . . . . . SAVMEDINF
*NONE
Data compaction . . . . . . . . COMPACT
*FROMFILE
................................................................
:
Data Compaction Key (COMPACT) - Help
:
:
:
: Specifies whether device data compaction is performed. If :
: the device specified does not support compaction, this
:
: parameter is ignored.
:
:
:
: *FROMFILE
:
:
Device data compaction is performed if the file being :
:
read from the device specified on the From device
:
:
(FROMDEV) parameter was written using device data
:
:
compaction.
:
:
:
:
More... :
: F2=Extended help F10=Move to top F11=Search Index
:
F3=Exit F4= : F12=Cancel
F20=Enlarge
F24=More keys
:
F24=More keys :
:
Messages pend :..............................................................:
Figure 7-34 Data compaction help text in DUPMEDBRM command
For more information about Backup, Recovery, and Media Services in IBM i 7.2, see the IBM i
7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzai8/rzai8overview.htm
?lang=en
261
8249_Backup.fm
262
8249_DB2.fm
Chapter 8.
IBM DB2 for i

This chapter describes what is new for DB2 for i in IBM i 7.2 and discusses the following
topics:
8.1, Introduction on page 264

8.2, Separation of duties concept on page 264
8.3, Security Enhancements on page 275
8.4, Functional enhancements on page 280
8.5, DB2 for i Services and Catalogs on page 294
8.6, DB2 performance on page 301
8.7, Database engineering on page 316
8.8, DB2 Web Query for i (5733-WQX, 5733-WQE, and 5733-WQS) on page 327
8.9, OmniFind Text Search Server for DB2 for i (5733-OMF) on page 328
263
8249_DB2.fm
8.1 Introduction
IBM DB2 for i is a traditional member of IBM DB2 family. This database is integrated in IBM i
operating system and delivered together with it. DB2 for i has been known for ease of use,
reliability, and scalability.
DB2 for i has been enhanced from release to release.DB2 for i is also enhanced via DB2 PTF
Groups, where PTF Group SF99702 applies to IBM i 7.2. This does not change in V7R2.
IBM i 7.2 brings a number of functional, security, performance, and management
enhancements. Majority of them have been implemented to support agility and, so called,
Data-Centric approach for the platform. Data-Centric paradigm requires business application
designers, architects, and developers, focus on the database as a central point of modern
applications, for better data integrity, security, business agility, and lower time to market (TTM)
factor. Contrary to the Application-Centric approach, where data manipulation, security, and
integrity is, at least partially, governed by the application code, Data-Centric concept moves
these responsibilities over the underlying database. This approach allows to ensure
consistent and secure data access and manipulation regardless of the application and the
database interface used. Implementing security patterns for business critical data, and data
access and manipulation procedures within DB2 for i is now easier than ever. What is more
important, it also allows to remove code complexity and security related burden from the
existing code of business applications. This is especially crucial for contemporary IT
environments where the same data is being manipulated by web, mobile, and legacy
applications at the same time. Moving data manipulation logic over the DB2 for i also
leverages all the current and future performance enhancements, database monitoring
capabilities, and performance problem investigation tools and techniques.
Key IBM i 7.2 database enhancements supporting Data-Centric paradigm are:
Row and column access control (RCAC)

Separation of duties
DB2 Services
Global variables
Named and Default parameter support on UDF/UDTFs
Pipelined Table Functions
SQL plan cache management
Performance enhancements
Interoperability and portability
Other
This section describes all major enhancements to DB2 for i in IBM i 7.2.
8.2 Separation of duties concept

Separation of duties is a concept, which helps companies to stay compliant with standards
and government regulations.
One of such requirements is that peopled doing administration tasks on operating systems
(usually they have *ALLOBJ special authority) should not be able to see and manipulate
customer data in DB2 databases.
Before IBM i version 7.2 when users had *ALLOBJ special authority they were not only able to
manipulate with DB2 files on logical level, but they were also allowed to see the data in these
database files. Also there was a problem, that someone who was able to grant permission to
264
8249_DB2.fm
other users to work with data in the database had also authority to see and manipulate with
the data inside databases.
To spread the operating system administration permissions and data manipulation
permissions, DB2 for i uses QIBM_DB_SECADM function. For this function authorities to see
and manipulate of data can be setup for individual users or groups. Also default option can be
setup. The example of setting it up is in 8.2.1, IQIBM_DB_SECADM function usage
While QIBM_DB_SECADM function usage can decide who can manipulate with DB2
security, there is another concept in DB2 for i 7.2 which helps to define which users or groups
can access rows and columns called Row and Column Access Control (RCAC).
8.2.1 IQIBM_DB_SECADM function usage

IBM i 7.2 now allows management of security without exposing the data to be read or
modified. User with *SECADM special authority can grant or revoke privileges to any object
even if he does not have these privileges. This can be done in WRKFCNUSG command
specifying if authority is *ALLOWED or *DENIED for particular user for QIBM_DB_SECADM
function.
Work with Function Usage
2=Change usage 5=Display usage
Opt Function ID
QIBM_DIRSRV_ADMIN
QIBM_ACCESS_ALLOBJ_JOBLOG
QIBM_ALLOBJ_TRACE_ANY_USER
QIBM_WATCH_ANY_JOB
QIBM_DB_DDMDRDA
QIBM_DB_SECADM
QIBM_DB_SQLADM
Function Name
IBM Tivoli Directory Server Administrator
Access job log of *ALLOBJ job
Trace any user
Watch any job
DDM & DRDA Application Server Access
Database Security Administrator
Database Administrator
Figure 8-1 Part of WRKFCNSUSG Screen
Lets select option 5=Display besides QIBM_DB_SECADM field and press ENTER.
Chapter 8. IBM DB2 for i
265
8249_DB2.fm
Display Function Usage

Function ID . . . . . . :
Function name . . . . . :
QIBM_DB_SECADM
Description . . . . . . :
Database Security Administrator Functions
Product . . . . . . . . :
Group . . . . . . . . . :
QIBM_BASE_OPERATING_SYSTEM
QIBM_DB
Default authority . . . . . . . . . . . . :
*ALLOBJ special authority . . . . . . . . :
User
Type
DEVELOPER1 User
DEVELOPER2 User
Usage
*DENIED
*DENIED
User
*DENIED
*NOTUSED
Type
Usage
Figure 8-2 Part of Display Function Usage screen
On the screen Figure 8-2 we can see that default authority for unspecified user profiles is
*DENIED. Also both DEVELOPER1 and DEVELOPER2 user profiles are *DENIED. Lets
return back to the WRKFCNUSG screen and place 2=Change besides the
IBM_DB_SECADM field and press ENTER. We will get to Change Function Usage Screen.
Change Function Usage (CHGFCNUSG)

Function ID . . . . . . .
User . . . . . . . . . . .
Usage . . . . . . . . . .
Default authority . . . .
*ALLOBJ special authority
.
.
.
.
.
.
.
.
.
.
. > QIBM_DB_SECADM
.
Name
.
*ALLOWED, *DENIED, *NONE
. *DENIED
*SAME, *ALLOWED, *DENIED
. *NOTUSED
*SAME, *USED, *NOTUSED
Figure 8-3 Part of Change Function Usage Screen
On screen in Figure 8-3 we will fill User field with SECADMINS group profile and usage field
as *ALLOWED
266
8249_DB2.fm
Change Function Usage (CHGFCNUSG)

Function ID . . . . . . .
User . . . . . . . . . . .
Usage . . . . . . . . . .
Default authority . . . .
*ALLOBJ special authority
.
.
.
.
.
.
.
.
.
.
. > QIBM_DB_SECADM
.
DBADMINS
Name
. *ALLOWED
*ALLOWED, *DENIED, *NONE
. *DENIED
*SAME, *ALLOWED, *DENIED
. *NOTUSED
*SAME, *USED, *NOTUSED
Figure 8-4 Filled up Change Function Usage screen
.Then we will press enter and after return to WRKFCNUSG screen, we will place option
5=Display again besides to QIBM_DB_SECADM function. The result we will see is in
Figure 8-4.
Display Function Usage

Function ID . . . . . . :
Function name . . . . . :
QIBM_DB_SECADM
Description . . . . . . :
Database Security Administrator Functions
Product . . . . . . . . :
Group . . . . . . . . . :
QIBM_BASE_OPERATING_SYSTEM
QIBM_DB
Default authority . . . . . . . . . . . . :
*ALLOBJ special authority . . . . . . . . :
User
SECADMINS
DEVELOPER1
DEVELOPER2
Type
Group
User
User
Usage
*ALLOWED
*DENIED
*DENIED
User
*DENIED
*NOTUSED
Type
Usage
Figure 8-5 Display Function Usage Screen with authority granted to SECADMINS group profile.
All users from SECADMINS group are now able to manage DB2 security.
8.2.2 Row and Column Access Control (RCAC)

BM i is now distributed with option 47 - IBM Advanced Data Security for IBM i. This option
must be installed prior using RCAC or masks.
RCAC is currently described in detail in the following redbook, so we will describe here only
basic principles and short example which shows the ease of implementing basic separation of
duties concept:
Row and Column Access Support in DB2 for IBM i, REDP-5110
267
8249_DB2.fm
The principle of RCAC

RCAC is based on the DB2 for i ability to define rules for row access control (using SQL
statement CREATE PERMISSION) and to define rules for column access control and
creation of masks for specific users or groups (using SQL statement CREATE MASK).
For implementing RCAC we need special registers via which we can check which user is
trying to display or use data in particular tables.
8.2.3 Special registers used for user identifications

To be able to identify users for the purpose of the RCAC, IBM i distinguishes several special
registers included in Table 8-1
Table 8-1 Special registers for identifying users
Special register
Definition
USER
or
SESSION_USER
The effective user of the thread Is returned
SYSTEM_USER
The authorization ID that initiated the connection is returned.
CURRENT USER
or
CURRENT_USER
The most recently program adopted authorization ID within the thread

is returned. When no adopted authority is active, the effective user of the
thread Is returned.
CURRENT_USER special register is new in DB2 for 7.2. For more information about it, see
the IBM Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaq9/rzaq9osDBcurrentu
ser.htm
8.2.4 VERIFY_GROUP_FOR_USER Function

The VERIFY_GROUP_FOR_USER function has two parameters, userid and group.
For the purpose of RCAC the userid parameter is usually one of special register values
(SESSION_USER, SYSTEM_USER, or CURRENT_USER) as described in 8.2.3, Special
registers used for user identifications on page 268.
This function returns a large integer value. If the user is member of group, this function
returns a value of 1, otherwise it returns a value of 0.
8.2.5 RCAC short example

Lets imagine that we will have employee database table in library HR. It contains last name,
first name, Date of birth, Account number, department number, and salary.The another table
CHIEF contains for each employee number, the employee number of his chiefLets first
prepare following groups:
EMPGRP - having members from all employees
HRGRP - having members from HR department
BOARDGRP - having members from chiefs of the company.
Lets prepare the group profiles:
268
8249_DB2.fm
Example 8-1 Group profiles for hospital example
CRTUSRPRF USRPRF(EMPGRP)
PASSWORD(*NONE)
TEXT('Employee group')
CRTUSRPRF USRPRF(HRGRP)
PASSWORD(*NONE)
TEXT('Human resources group')
CRTUSRPRF USRPRF(BOARDGRP)
PASSWORD(*NONE)
TEXT('Chiefs group')
Create these user profiles in the Example 8-2.
For simplicity let suppose:
1. We create user profile password the same as the user profile name)
2. For all employees - the user profile name is the same as employee's last name.
Example 8-2 User profiles for hospital example
CRTUSRPRF USRPRF(JANAJ)
TEXT('Jana Jameson')
GRPPRF(EMPNO)
SUPGRPRF(HRGRP)
Jana Jameson works at HR department
CRTUSRPRF USRPRF(JONES)
TEXT('George Jones - the company chief')
GRPPRF(EMPGRP)
SUPGRPPRF(BOARDGRP)
-- George James is a chief of the company and its employee.
CRTUSRPRF USRPRF(FERRANONI)
TEXT('Fabrizion Ferranoni')
GRPPRF(EMPGRP)
CRTUSRPRF USRPRF(KADLEC)
TEXT('Ian Kadlec')
GRPPRF(EMPGRP)
CRTUSRPRF USRPRF(NORTON)
TEXT('Laura Norton')
GRPPRF(EMPGRP)
CRTUSRPRF USRPRF(WASHINGTON)
TEXT('Kimberly Washington')
GRPPRF(EMPGRP)
Now we will create the DB2 Schema (collection) HR and employee table EMPLOYEE. We
suppose that there is not existing HR library in the system. The primary key for this table will
be the social security number column, After creating database table EMPLOYEE, we will also
create index EMPLOYEE01 and EMPLOYEE02 for faster access.
269
8249_DB2.fm
The next step will be filling the database by patient data using insert command.
Note: For entering SQL commands we can use either STRSQL command starting
interactive SQL, or IBM System i Navigator. If you will use STRSQL and interactive SQL
session using 5250 emulator, please remove the semicolon marks at the end of each SQL
statement.
Example 8-3
Creating schema, table, index, and filling up with data
CREATE TABLE HR/EMPLOYEE

(FIRST_NAME FOR COLUMN FNAME CHARACTER (15 ) NOT NULL WITH DEFAULT,
LAST_NAME FOR COLUMN LNAME CHARACTER (15 ) NOT NULL WITH DEFAULT,
DATE_OF_BIRTH FOR COLUMN BIRTHDATE DATE NOT NULL WITH DEFAULT,
BANK_ACCOUNT
CHARACTER (9 ) NOT NULL WITH DEFAULT,
EMPLOYEE_NUM
FOR COLUMN EMPNO CHARACTER(6) NOT NULL WITH DEFAULT,
DEPARTMENT FOR COLUMN DEPT DECIMAL (4, 0) NOT NULL WITH DEFAULT,
SALARY
DECIMAL (9, 0) NOT NULL WITH DEFAULT,
PRIMARY KEY (EMPLOYEE_NUM)) ;
CREATE INDEX HR/EMPLOYEE01 ON HR/EMPLOYEE
(LAST_NAME ASC,
FIRST_NAME ASC) ;
CREATE INDEX HR/EMPLOYEE02 ON HR/EMPLOYEE
(DEPARTMENT ASC,
LAST_NAME ASC,
FIRST_NAME ASC);
-- Now we created table CHIEF and fill its data
CREATE TABLE HR/CHIEF
(
EMPLOYEE_NUM FOR COLUMN EMPNO CHARACTER(6 ) NOT NULL WITH DEFAULT,
CHIEF_NO
CHARACTER(6 ) NOT NULL WITH DEFAULT,
PRIMARY KEY (EMPLOYEE_NUM)) ;
INSERT INTO HR/CHIEF VALUES
(
'G76852', 'G00012') ;
(
'G12835', 'G00012');
(
'G23561', 'G00012');

(
'G00012', 'CHIEF ');
(
270
8249_DB2.fm
'G32421', 'G00012');
-- Now we will load exapmple data into EMPLOYEE table
INSERT INTO HR/EMPLOYEE
VALUES('Fabrizio', 'Ferranoni',
DATE('05/12/1959') , 345723909, 'G76852','0001', 96000) ;
VALUES('Ian', 'Kadlec',
DATE('11/23/1967') , 783920125, 'G23561', '0001', 64111) ;
VALUES('Laura', 'Norton',
DATE('02/20/1972') , 834510932, 'G00012', '0001', 55222) ;
VALUES('Kimberly', 'Washington',
DATE('10/31/1972') , 157629076, 'G12435', '0005' , 100000);
VALUES('George', 'Jones',
DATE('10/11/1952') , 673948571, 'G00001', '0000' , 1100000);
VALUES('Jana ', 'Jameson',
DATE('10/11/1952') , 643247347, 'G32421', '0205' ,
30000);
Now it will come the most important and most interesting part - definig the row and column
access rules.
First let specify the row permission access rules at Example 8-4
We will want to implement these rules:
Each employee should see only its own record except for employees from human resources
department (group HRGRP), and chiefs (BOARDGRP) who should have access to all rows.
Example 8-4 Example of Row access rule
-- Definition of row permissions follows

CREATE PERMISSION ACCESS_TO_ROW ON HR/EMPLOYEE
FOR ROWS WHERE
(
VERIFY_GROUP_FOR_USER(SESSION_USER,'BOARDGRP') = 1
)
OR
(
VERIFY_GROUP_FOR_USER(SESSION_USER,'EMPGRP') = 1
AND UPPER(LAST_NAME) = SESSION_USER
)
OR
(
VERIFY_GROUP_FOR_USER(SESSION_USER,'HRGRP') = 1
)
271
8249_DB2.fm
ENFORCED FOR ALL ACCESS

ENABLE ;
-- We activate row access control, so the rule ACCESS_TO_ROW will start work
ALTER TABLE HR/EMPLOYEE ACTIVATE ROW ACCESS CONTROL ;
Explanation of Example 8-4 on page 271:

1. We are creating a rule called ACCESS_ON_ROW
2. First we will check, if the user profile of the person who is quering the employee file
(SESSION_USER) is part of the group BOARDGRP. We use
VERIFY_GROUP_FOR_USER function. I the user he is member of BOARDGRP (function
will return value 1 he is granted access to the row.
3. If the user is member of EMPGRP, we check if this user has records in the file
(UPPER(LAST_NAME) = SESSION_USER). That means that for instance employee Ian
Kadlec cannot see row (record) of employee Laura Norton.
4. Other verification is if user profile is member of group HRGRP. If yes, such user profile has
access to all employee records (row).
5. If none of conditions is true, the user looking at the table data will see no records.
6. Then using SQL command ALTER TABLE....ACTIVATE ROW ACCESS CONTROL we
activate this rule.
The next example will show how to use the column mask.
Example 8-5 Example of creating column mask
-- Following are masks for two columns, BANK_ACCOUNT and SALARY.

CREATE MASK BANKACC_MASK ON HR/EMPLOYEE FOR
COLUMN BANK_ACCOUNT RETURN
CASE
WHEN (VERIFY_GROUP_FOR_USER(SESSION_USER,
AND UPPER(LAST_NAME) = SESSION_USER
THEN BANK_ACCOUNT
WHEN VERIFY_GROUP_FOR_USER(SESSION_USER,
THEN BANK_ACCOUNT
WHEN UPPER(LAST_NAME) = SESSION_USER
AND
VERIFY_GROUP_FOR_USER(SESSION_USER,
THEN BANK_ACCOUNT
ELSE '*********'
END
ENABLE;
'BOARDGRP' ) = 1
)
'HRGRP' ) = 1
'EMPGRP' ) = 1
CREATE MASK SALARY_MASK ON HR/EMPLOYEE FOR

COLUMN SALARY RETURN
CASE
WHEN UPPER(LAST_NAME) = SESSION_USER
AND VERIFY_GROUP_FOR_USER(SESSION_USER, 'EMPNO') = 1
THEN SALARY
WHEN VERIFY_GROUP_FOR_USER(SESSION_USER, 'BOARDGRP' ) = 1
THEN SALARY
WHEN VERIFY_GROUP_FOR_USER(SESSION_USER, 'HRGRP' ) = 1
THEN SALARY
ELSE 0
272
8249_DB2.fm
END
ENABLE;
-- We activate both column rules
ALTER TABLE HR/EMPLOYEE ACTIVATE COLUMN ACCESS CONTROL ;
The puirpose of SQL CREATE MASK statement in Example 8-5 is to hide some columns
which contain sensitive personal information like bank account nuber, or credit card number,
and present the dat only to persons which should know it.
Lets look at this example in detail:
1. We are creating mask BANKACC_MASK.
2. This mask will be related to BANK_ACCOUNT column.
3. If user accessing the data is chief (member of BORADGRP group), then we show the
column containing his credit card data
4. If user accessign the data is HR department employee (member of HRGRP group), then
we show the column (HR depatrment should see all employees bank account numbers.
5. All other users should not know the credit card number, so we will display *********.
6. Then we create mask SALARY MASK.
7. This mask will be related to SALARY column containing salary data.
8. If user accessing the data is employee (member of EMPGRP group), then we show the
column containing his salary data
9. If user accessign the data is HR employee (member of HRGRP group), then we show the
column (accounitng clerk will need salary dat.
10.If user accessing the data is a chief (member of BOARDGRP group), then we show the
column. Heshould know the slaries of employees.
11.All other users should not know the credit card number, so we will display *********.
12.Using SQL Command ALTER TABLE .... ACTIVATE COLUMN ACCESS CONTROL we
activate both rules.
Results
Lets now look at the reuslts:
When JONES user will logon (member of BOARDGRP), he will see the followning results
from EMPLOYEE:
Figure 8-6 EMPLOYEE table as seen by the JONES user profile (Chief)
Chief sees all employees, their salaries, but only own account number.
When any employe (here we will use KADLEC user profile) will logon, he will see the
followning results from EMPLOYEE table:
273
8249_DB2.fm
Figure 8-7 EMPLOYEEt table as seen by the KADLEC user profile.
In this case each employee sees all data, but only data related to his person. For this the
ACCESS_TO_ROW row access rule is responsible.
When human resources employee (here we will use JANAJ user profile) will logon, she will
see the followning results from EMPLOYEE table:
Figure 8-8 EMPLOYEE table as seen by the JANAJ user profile.
The human resources employee sees bank accounts and salaries of all employees.
All other user profiles see empty database file.
I
Note: Row and Column Access control brings much more cosnsiderations than in this
example, for instance when changing data, using joins, etc. For more detail please consult
Redpaper Row and Column Access Support in DB2 for IBM i, REDP-5110.
8.2.6 Add OR REPLACE for masks and permissions

Similar to other Data Definition Language (DDL) statements, the OR REPLACE clause has
been added to:
CREATE OR REPLACE MASK

CREATE OR REPLACE PERMISSION
The use of OR REPLACE makes it easier to re(deploy) Row & Column Access Control
(RCAC) rule text.
Consult the updated IBM i 7.2 SQL reference for details.
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafzintro.htm
8.2.7 InfoSphere Guardium 9.0

InfoSphere Guardium is an enterprise information database audit and protection solution.
It helps enterprises protect and audit information across a diverse set of relational and
non-relational data sources. It allows companies to stay compliant with wide range of
standards. Lets name here several security areas which are usually monitored:
Access to Sensitive Data (Successful/Failed SELECTs)
274
8249_DB2.fm
Schema Changes (CREATE, DROP, ALTER TABLES, etc.)

Security Exceptions (Failed Logins, SQL errors, etc.)
Accounts, Roles & Permissions (GRANT, REVOKE)
With InfoSphere Guardium V9.0, DB2 for IBM i can now be included as a data source,
enabling the monitoring of accesses from native interfaces as well as through SQL.
Supported DB2 for i data sources are from IBM i version 6.1, 7.1, and 7.2. Of course specific
PTFs must be used for each of IBM i version,
InfoSphere Guardium product now take data from DB2 for i using AIX based S-TAP
software module running in PASE.. Both audit information and SQL Monitor information is
streamed to S-TAP. Data passed to S-TAP can be filtered for both audit data, and also DB2
monitor data for performance reasons.
For deeper information abot DB2 Guardium 9.0 and DB2 for i support plese use the following
IBM developeworks link:
echnology%20Updates/page/Infosphere%20Guardium%20V9%20%E2%80%93%20target%20DB2%20f
or%20i%20as%20a%20data%20source
8.3 Security Enhancements

8.3.1 Add QIBM_DB_ZDA and QIBM_DB_DDMDRDA function usage IDs
These function usage IDs block database server inbound connections. The function usage
IDs ship with default authority = *ALLOWED. The security officer can easily deny access to
specific users or groups.
The QIBM_DB_ZDA function usage ID restricts ODBC and JDBC Toolbox from the server side,
including Run SQL Scripts, System i Navigator and DB2 specific portions of Systems Director
Navigator for i.
The QIBM_DB_DDMDRDA function usage ID allows to lock down DDM and DRDA application
server access.
These function usage IDs can be managed from WRKFCNUSG command screen or by using
CHGFCNUSG command.
Example 8-6 Denying user profile the usage of DDM and DRDA application server access
CHGFCNUSG FCNID(QIBM_DB_DDMDRDA) USER(user1) USAGE(*DENIED)
8.3.2 Authorization List detail added to Authorization catalogs

The following DB2 for i catalogs were enhanced to contain column AUTHORIZATION_LIST.
Using authorizations list eases the security management and also improves performance,
because user profiles do not need to contain a list of objects to which they are authorized.
They just need to contain authorization list which contains these objects.
Catalogs QSYS2/SYSXSROBJECTAUTH and QSYS2/SYSVARIABLEAUTH were updated at already at
version 7.1, but to have complete overview of catalogs having now AUTHORIZATION_LIST
column are in the following Figure 8-2
275
8249_DB2.fm
Table 8-2 Authorization catalogs containing AUTHORIZATION_LIST column

Catalog
Catalog description|
QSYS2/SYSPACKAGEAUTH
*SQLPKG - Packages
QSYS2/SYSUDTAUTH
*SQLUDT - User defined typed
QSYS2/SYSTABAUTH
*FILE - Tables
QSYS2/SYSSEQUENCEAUTH
*DTAARA - sequences
QSYS2/SYSSCHEMAAUTH
*LIB - Sechema
QSYS2/SYSROUTINEAUTH
*PGM and *SRVPGM - Procedures and Functions
QSYS2/SYSCOLAUTH
Columns
QSYS2/SYSXSROBJECTAUTH
*XSROBJ - XML Schema Repositories
QSYS2/SYSVARIABLEAUTH
*SRVPGM - Global Variables
8.3.3 QSYS2.GROUP_USERS() user defined table function

This new user defined table functions allows to make queries which specify group profile as
its parameter and list user profiles in this group as the output.
The QSYS2.GROUP_USERS() functions returns user profiles which have the specified group
set up as their main or supplemental group.
Figure 8-9 Example of the use of QSYS2.GROUP_USERS() UDTF
8.3.4 QSYS2.GROUP_PROFILE_ENTRIES new security view

This view returns table with 3 colums:
GROUP_PROFILE_NAME
USER_PROFILE_NAME
USER_TEXT
It takes into account both group and supplemental group profiles.
Figure 8-10 Example of use of QSYS2.GROUP_PROFILE_ENTRIES
276
8249_DB2.fm
8.3.5 SYSIBM.AUTHORIZATIONS new attribute column

The SYSIBM.AUTHORIZATIONS catalog has been extended to include a new column, which
differentiates users from groups.
The SYSIBM.AUTHORIZATIONS view is a DB2 family compatible catalog which contains one
row for every authorization ID.
Figure 8-11 Example of use of SYSIBM.AUTHORIZATIONS Catalog
8.3.6 QSYS2.SQL_CHECK_AUTHORITY() UDF for determining select

capability
This UDF functions should check if the user calling this function has or has not the authority
ro object specified by parameters. Object type must be *FILE First parameter is library, the
second one is object name.
The result type is SMALLINT.
There are 2 possible result vallues:
1 - User has authority
0 - User does not have authority
Figure 8-12 Example of use of the QSYS2.SQL_CHECK_AUTHORITY UDF
The example in Figure 8-12 shows that user has authority to CZZ62690/QTXTSRC object.
8.3.7 Refined Object auditing control on the QIBM_DB_OPEN exit program

Previously, an exit program control (*OBJAUD) was added to limit exit program calls. Due to
the wide use of *CHANGE object auditing in some environments, the *OBJAUD control did
not reduce the calls to the exit program enough, in some environments.
Now the Open Data Base File Exit Program is enhanced to support two new values for the
Exit Program Data - OBJAUD(*ALL) and OBJAUD(*CHANGE).
Three approaches now exist as it is seen in Example 8-7
277
8249_DB2.fm
Example 8-7 Object auditing control on the QIBM_DB_OPEN exist program
1st example:
ADDEXITPGM EXITPNT(QIBM_QDB_OPEN) FORMAT(DBOP0100) PGMNBR(7) PGM(MJATST/OPENEXIT2)
THDSAFE(*YES) TEXT('MJA') REPLACE(*NO)
PGMDTA(*JOB *CALC '*OBJAUD')
The exit program will be called when any object auditing is encountered
2nd Example:
PGMDTA(*JOB *CALC 'OBJAUD(*ALL)')
The exit program will be called when *ALL object auditing is encountered
3rd Example:
PGMDTA(*JOB *CALC 'OBJAUD(*CHANGE)')
The exit program will be called when *CHANGE object auditing is encountered
8.3.8 Simplified DDM/DRDA authentication management using group profiles

This new functionality enhances the authentication process when user connects to a
database on another system or LPAR using DDM or DRDA (for instance using SQL command
CONNECT TO <database>.
Prior to this enhancement every user connecting to another LPAR database needed to have
server authentication entry (using ADDSVRAUTHE command) with password for his user profile.
This enhancement allows to have server authentication entry based on group profile. When
user is member to this group profile, or has this group profile set up as supplemental in his
user profile, then only group profile should have server authentication entry.
Lets see the folowing example:
Example 8-8 Using group profile authentication entry to access remote database.
First lets create the group profile TESTGROUP:

CRTUSRPRF USRPRF(TESTGROUP) PASSWORD(*NONE)
Then crate the user profile TESTUSR and make it a member of TESTGROUP:
CRTUSRPRF USRPRF(TESTUSR) PASSWORD(somepasswd) GRPPRF(TESTTEAM)
Now lets create the server authentication entry:
ADDSVRAUTE USRPRF(TESTGROUP) SERVER(QDDMDRDASERVER or <RDB-name>) USRID(sysbusrid)
PASSWORD(sysbpwd)
User TESTUSR then uses STRSQL command to get to interactive SQL session and issues
the following command:
CONNECT TO <RDB-name>
Where RDB-name is remote relational database registered using command WRKRDBDIRE.
278
8249_DB2.fm
The connection attempt is done to to system with <RDB-name> using <sysbusrid> user
profile and <sysbpwd> password.
The process of authentication is as follows:
1. Search the authentication entries where USRPRF=user profile and SERVER= application
server name
2. Search the authentication entries where USRPRF=user profile and
SERVER='QDDMDRDASERVER'
3. Search the authentication entries where USRPRF=group profile and SERVER=
application server name
4. Search the authentication entries where USRPRF=group profile and
5. Search the authentication entries where USRPRF=supplemental group profile and
SERVER= application server name
6. Search the authentication entries where USRPRF=supplemental group profile and
7. If no entry has been found in all previous steps, a USERID-only authentication attempt
Note: To use ADDSRVAUTE command you need
Requirements to use ADDSRVAUTE
Authorization Requirement:
Security administrator (*SECADM) user special authority

Object management (*OBJMGT) user special authority
When the default authentication entry search order (explained above) is used, the search
order will cease at connect time if a match is found for QDDMDRDASERVER.
The QIBM_DDMDRDA_SVRNAM_PRIORITY environment variable dictates whether we
favor an explicit server name order when searching for authentication entries:
1.
2.
3.
4.
5.
6.
7.
USRPRF=user profile & SERVER= application server name

USRPRF=group profile & SERVER= application server name
USRPRF=supplemental group profile & SERVER=application server name
USRPRF=user profile & SERVER='QDDMDRDASERVER'
USRPRF=group profile & SERVER='QDDMDRDASERVER'
USRPRF=supplemental group profile & SERVER='QDDMDRDASERVER'
If no entry has been found in all previous steps, a USERID-only authentication attempt will
be used
Example 8-9 How to set up the QIBM_DDDMDRDA_SVRNAM_PRIORITY environment variable
Create environment variable:

ADDENVVAR ENVVAR(QIBM_DDMDRDA_SVRNAM_PRIORITY)
VALUE(Y) LEVEL(*JOB or *SYS)
Detailed information how to setup authority for DDM and DRDA can be found in IBM
Knowledge Center using the following link:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/ddp/rbal1sourcesecurity
.htm?lang=en
279
8249_DB2.fm
8.4 Functional enhancements

This section introduces the functional enhancements with DB2 for i 7.2 which include the
following:
Increased timestamp precision

Named and Default parameter support on UDF/UDTFs
Function resolution using casting rules
Use of ARRAYs within scalar UDFs
Built-in global variables
Expressions on PREPARE & EXECUTE IMMEDIATE
Autonomous procedures
New SQL statement TRUNCATE
New Built-in Functions LPAD() & RPAD()
And this section also introduces the functional enhancements with IBM i 7.2 TR1 timed
including:
Pipelined table functions

Regular expressions
JOB_NAME & SERVER_MODE_JOB_NAME built-in global variables
RUNSQL control of output listing
LOCK TABLE ability to target non-*FIRST members
QUSRJOBI() retrieval of DB2 built-in global variables
8.4.1 Increased timestamp precision

In IBM i 7.2, between 0 to 12 digits can be set as timstamp precision. Prior to IBM i 7.2, only 6
digits is only supported as timestamp precision. This enhancement applies to not only DDL,
but also DML. You can specify timestamp precision in CREATE TABLE statement and you
can also adjust existing tables by using ALTER TABLE. Example 8-10 shows the results of
mixed precision time in a CREATE TABLE statement, and INSERT statements.
Example 8-10 Increased timestamp precision
CREATE TABLE
old_time
new_time
no_time
Last_Change
corpdb.time_travel(
TIMESTAMP,
TIMESTAMP(12),
TIMESTAMP(0),
TIMESTAMP NOT NULL IMPLICITLY HIDDEN FOR EACH ROW ON UPDATE AS
ROW CHANGE TIMESTAMP);
INSERT INTO corpdb.time_travel

VALUES(current timestamp, current timestamp,
current timestamp);
INSERT INTO corpdb.time_travel
VALUES(current timestamp, current timestamp(12),
current timestamp);
SELECT old_time,
new_time,
no_time,
last_change
FROM corpdb.time_travel;
280
8249_DB2.fm
SELECT new_time - last_change as new_minus_last,

new_time - old_time as new_minus_old,
new_time - no_time as new_minus_no
FROM corpdb.time_travel;
Figure 8-13 shows the result of the first SELECT statement in Example 8-10. The precision of
data of each field is vary the precision digits.
Figure 8-13 Result of the first SELECT statement
The second SELECT statement calculates the difference of NEW_TIME and each other
field. Figure 8-14 shows the result of this SELECT statement. The second record of the result
is expressed as the precision with 12 digits because the value which stored in NEW_TIME
has 12 digits as its the precision.
Figure 8-14 Result of the second SELECT statement
Note: You can adjust precision of timestamp columns of existing tables by using an ALTER
TABLE statement, but existing data in those columns have remain initial digits because a
precision of timestamp data is determined at the time of generating.
For more information about timestamp precision, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafzch2timestamp.h
tm
8.4.2 Named and Default parameter support on UDF/UDTFs

Similar to Named & Default parameters for procedures in IBM i 7.1 TR5, IBM i 7.2 adds
support for SQL and External User Defined Functions (UDFs). This enhancement brings the
usability found with CL Commands to UDF/UDTFs.
Example 8-11 shows the example UDF which specifies a default value to a parameter.
Example 8-11 Named and default parameter support on UDF/UDTFs
CREATE OR REPLACE FUNCTION DEPTNAME(

P_EMPID VARCHAR(6) , P_REQUESTED_IN_LOWER_CASE INTEGER DEFAULT 0)
RETURNS VARCHAR(30)
LANGUAGE SQL
D:BEGIN ATOMIC
DECLARE V_DEPARTMENT_NAME VARCHAR(30);
DECLARE V_ERR VARCHAR(70);
SET V_DEPARTMENT_NAME = (
SELECT CASE
WHEN P_REQUESTED_IN_LOWER_CASE = 0 THEN
D.DEPTNAME
ELSE
281
8249_DB2.fm
LOWER(D.DEPTNAME)
END CASE
FROM DEPARTMENT D, EMPLOYEE E
WHERE E.WORKDEPT = D.DEPTNO AND
E.EMPNO = P_EMPID);
IF V_DEPARTMENT_NAME IS NULL THEN
SET V_ERR = 'Error: employee ' CONCAT P_EMPID CONCAT ' was not found';
SIGNAL SQLSTATE '80000' SET MESSAGE_TEXT = V_ERR;
END IF ;
RETURN V_DEPARTMENT_NAME;
END D;
Example 8-12 shows the VALUES statement which uses the example UDF in Example 8-11
as specifying different values to P_REQUESTED_IN_LOWER_CASE parameter.
Example 8-12 VALUES statement which specifying a different value to the parameter in UDF
VALUES(DEPTNAME('000110'),
DEPTNAME('000110', 1 ),
DEPTNAME('000110', P_REQUESTED_IN_LOWER_CASE=>1));
Figure 8-15 shows the result of Example 8-12.
Figure 8-15 Result of VALUES statement which uses the UDF.
8.4.3 Function resolution using casting rules

Prior to IBM i 7.2, function resolution looked for only an exact match with the following
perspective.
Function name
Number of parameters
Data type of parameters
With IBM i 7.2, if DB2 for i does not find an exact match when function resolution, it look for
best fit with using casting rules. In this newly rules, If CAST() is supported for the parameter
data type mismatch, the function will be found. For more information about rules, see the IBM
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafzbestfit.htm
Example 8-13 describes a sample function and a VALUES statement which uses that
function. Figure 8-16 shows the result of VALUES statement with an error SQLCODE -204 at
prior to IBM i 7.2, Figure 8-17 shows the result at IBM i 7.2 which the function found with
casting rules.
Example 8-13 Sample function that casting might have occurred
CREATE OR REPLACE FUNCTION MY_CONCAT(

FIRST_PART VARCHAR(10),
SECOND_PART VARCHAR(50))
RETURNS VARCHAR(60)
LANGUAGE SQL
282
8249_DB2.fm
BEGIN
RETURN(FIRST_PART CONCAT SECOND_PART);
END;
VALUES(MY_CONCAT(123,456789));
Figure 8-16 Result of VALUES statement with an error SQLCODE -204
283
8249_DB2.fm
Figure 8-17 Result of VALUES statement with the FUNCTION found with casting rules
8.4.4 Use of ARRAYs within scalar UDFs

IBM i 7.1 supports to create a type that is an array and use it in SQL procedures. In addition to
this array support, An array can be used in scalar User Defined Functions as well as in SQL
procedures. Example 8-14 and Figure 8-18 show the example and result of creating an array
type and using it in a User Defined Function.
Example 8-14 Array Support in scalar User Defined Functions
CREATE TABLE EMPPHONE(ID

PRIORITY
PHONENUMBER
PRIMARY KEY
VARCHAR(6) NOT NULL,

INTEGER NOT NULL,
VARCHAR(12),
(ID, PRIORITY));
INSERT INTO EMPPHONE VALUES('000001', 1, '03-1234-5678');

CREATE TYPE PHONELIST AS VARCHAR(12) ARRAY[10];
CREATE OR REPLACE FUNCTION getPhoneNumbers (EmpID CHAR(6)) RETURNS VARCHAR(130)
BEGIN
DECLARE numbers PHONELIST;
DECLARE i INTEGER;
DECLARE resultValue VARCHAR(130);
SELECT ARRAY_AGG(PHONENUMBER ORDER BY PRIORITY) INTO numbers
FROM EMPPHONE
WHERE ID = EmpID;
284
8249_DB2.fm
SET resultValue = '';

SET i = 1;
WHILE i <= CARDINALITY(numbers) DO
SET resultValue = TRIM(resultValue) ||','|| TRIM(numbers[i]);
SET i = i + 1;
END WHILE;
RETURN TRIM(L ',' FROM resultValue);
END;
VALUES(getPhoneNumbers('000001'));
Figure 8-18 Result of a scalar User Defined Functions which uses an array
8.4.5 Built-in global variables

New built-in global variables are supported in IBM i 7.2. These variables are referenced
purpose only variables and maintained by DB2 for i automatically. If And these can be
referenced anywhere a column name can be used. Global variables fit nicely into view
definitions and RCAC masks/permissions.
Table 8-3 Built-in Global Variables newly introduced in IBM i 7.2
Variable Name
Schema
Data Type
Size
CLIENT_IPADDR
SYSIBM
VARCHAR
128
CLIENT_HOST
SYSIBM
VARCHAR
255
285
8249_DB2.fm
Variable Name
Schema
Data Type
Size
CLIENT_PORT
SYSIBM
INTEGER
PACKAGE_NAME
SYSIBM
VARCHAR
128
PACKAGE_SCHEMA
SYSIBM
VARCHAR
128
PACKAGE_VERSION
SYSIBM
VARCHAR
64
ROUTINE_SCHEMA
SYSIBM
VARCHAR
128
ROUTINE_SPECIFIC_NAME
SYSIBM
VARCHAR
128
ROUTINE_TYPE
SYSIBM
CHAR
Example 8-15 shows the example of a SELECT statement which queries the client
information.
Example 8-15 Example of a SELECT statement to get a client information from global variables
SELECT SYSIBM.client_host AS CLIENT_HOST,

SYSIBM.client_ipaddr AS CLIENT_IP,
SYSIBM.client_port AS CLIENT_PORT
FROM SYSIBM.SYSDUMMY1
As for getting a client information, TCP/IP Services in QSYS2, which is already introduced in
IBM i 7.1, can be also used as like in Example 8-16.
Example 8-16 Getting a client information from TCP/IP Services in QSYS2
SELECT * FROM QSYS2.TCPIP_INFO
8.4.6 Expressions on PREPARE & EXECUTE IMMEDIATE

In IBM i 7.2, expressions can be used in PREPARE and EXECUTE IMMEDIATE statements
addition to variables. Example 8-17 and Example 8-18 are the statements for getting the
information about advised indexes from QSYS2 and putting them into a table in QTEMP.
Example 8-17 is the example prior to 7.2 and Example 8-18 is the example at IBM i 7.2. With
this enhancement, many SET statement can be eliminated from the part of generating the
WHERE clause.
Example 8-17 Example of EXECUTE IMMEDIATE with concatenating strings prior to IBM i 7.2
SET INSERT_STMT = 'INSERT INTO QTEMP.TMPIDXADV SELECT * FROM

QSYS2.CONDENSEDINDEXADVICE WHERE ';
IF (P_LIBRARY IS NOT NULL) THEN
SET WHERE_CLAUSE = 'TABLE_SCHEMA = ''' CONCAT
RTRIM(P_LIBRARY) CONCAT ''' AND ';
ELSE
SET WHERE_CLAUSE = '';
END IF;
IF (P_FILE IS NOT NULL) THEN
SET WHERE_CLAUSE = WHERE_CLAUSE CONCAT ' SYSTEM_TABLE_NAME = ''' CONCAT
RTRIM(P_FILE) CONCAT ''' AND ';
END IF;
IF (P_TIMES_ADVISED IS NOT NULL) THEN
SET WHERE_CLAUSE = WHERE_CLAUSE CONCAT ' TIMES_ADVISED >= ' CONCAT
286
8249_DB2.fm
P_TIMES_ADVISED CONCAT ' AND ';

END IF;
IF (P_MTI_USED IS NOT NULL) THEN
SET WHERE_CLAUSE = WHERE_CLAUSE CONCAT 'MTI_USED >= ' CONCAT
P_MTI_USED CONCAT ' AND ';
END IF;
IF (P_AVERAGE_QUERY_ESTIMATE IS NOT NULL) THEN
SET WHERE_CLAUSE = WHERE_CLAUSE CONCAT ' AVERAGE_QUERY_ESTIMATE >= ' CONCAT
P_AVERAGE_QUERY_ESTIMATE CONCAT ' AND ';
END IF;
SET WHERE_CLAUSE = WHERE_CLAUSE CONCAT ' NLSS_TABLE_NAME = ''*HEX'' ';
SET INSERT_STMT = INSERT_STMT CONCAT WHERE_CLAUSE;
EXECUTE IMMEDIATE INSERT_STMT;
Example 8-18 Example of EXEXUTE IMMEDIATE with concatenating strings at IBM i 7.2
EXECUTE IMMEDIATE 'INSERT INTO QTEMP.TMPIDXADV SELECT * FROM

QSYS2.CONDENSEDINDEXADVICE WHERE ' CONCAT
CASE WHEN P_LIBRARY IS NOT NULL THEN
' TABLE_SCHEMA = ''' CONCAT RTRIM(P_LIBRARY) CONCAT ''' AND '
ELSE '' END CONCAT
CASE WHEN P_FILE IS NOT NULL THEN
' SYSTEM_TABLE_NAME = ''' CONCAT RTRIM(P_FILE) CONCAT ''' AND '
ELSE '' END CONCAT
CASE WHEN P_TIMES_ADVISED IS NOT NULL THEN
' TIMES_ADVISED >= ' CONCAT P_TIMES_ADVISED CONCAT ' AND '
ELSE '' END CONCAT
CASE WHEN P_MTI_USED IS NOT NULL THEN
' MTI_USED >= ' CONCAT P_MTI_USED CONCAT ' AND '
ELSE '' END CONCAT
CASE WHEN P_AVERAGE_QUERY_ESTIMATE IS NOT NULL THEN
' AVERAGE_QUERY_ESTIMATE >= ' CONCAT P_AVERAGE_QUERY_ESTIMATE CONCAT ' AND '
ELSE '' END CONCAT
' NLSS_TABLE_NAME = ''*HEX'' ';
8.4.7 Autonomous procedures

In IBM i 7.2, an autonomous procedure is introduced. An autonomous procedure is executed
in a unit of work that is independent from the calling application. New AUTONOMOUS option
is supported in CREATE PROCEDURE and ALTER PROCEDURE statement. By specifying a
procedure as an autonomous, any process in that procedure can be performed regardless of
the result of the invoking transaction. Example 8-19 shows the example of creating an
autonomous procedure which is intended to write an application log to a table. In this
example, procedure WriteLog is specified as AUTONOMOUS. Figure 8-19 shows the result
of Example 8-19, which shows all of insert operations into EMPPHONE table were rolled
back but all of log messages remain recorded in TRACKING_TABLE.
Example 8-19 Autonomous Procedures
CREATE TABLE TRACKING_TABLE (LOGMSG VARCHAR(1000),

LOGTIME TIMESTAMP(12));
COMMIT;
CREATE OR REPLACE PROCEDURE WriteLog(loginfo VARCHAR(1000))
AUTONOMOUS
287
8249_DB2.fm
BEGIN
INSERT INTO TRACKING_TABLE VALUES(loginfo, current TIMESTAMP(12));
END;
CALL WriteLog('*****INSERTION 1 START*****');
CALL WriteLog('*****INSERTION 1 END*****');
CALL WriteLog('*****INSERTION 2 START*****');
CALL WriteLog('*****INSERTION 2 END*****');
/**roll back insertions**/
ROLLBACK;
SELECT * FROM EMPPHONE WHERE ID = '000002';
SELECT * FROM TRACKING_TABLE;
Figure 8-19 Result of a example of an AUTONOMOUS procedure
288
8249_DB2.fm
For more information about AUTONOMOUS, see the DB2 for i 7.2 Database SQL References
at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/db2/rbafzpd
f.pdf
8.4.8 New SQL statement TRUNCATE

TRUNCATE statement, which is added on IBM i 7.2, deletes all rows from a table. This
statement can be used in an application program and also interactive.
TRUNCATE has additional functions to:
DROP or REUSE storage
IGNORE or RESTRICT when delete triggers are present
CONTINUE or RESTART identity values
IMMEDIATE performs the operation without commit even if running under commitment
control
Figure 8-20 shows the syntax of TRUNCATE statement.
Figure 8-20 Syntax of TRUNCATE statement
For more information about TRUNCATE, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafztruncate.htm
8.4.9 New Built-in Functions LPAD() & RPAD()

LPAD() and RPAD() built-in functions are introduced in IBM i 7.2. These functions returns a
string composed of strings that is padded on the left or right. Example 8-20 shows the
example of LPAD(). Assume that CUSTOMER table which has NAME column with
VARCHAR(15) that contains the values Chris, Meg, and John. Figure 8-21 show the result
of SELECT statement will completely pad out a value on the left with periods.
Example 8-20 LPAD() built-in functions
CREATE
INSERT
INSERT
INSERT
TABLE CUSTOMER(CUSTNO CHAR(6),

INTO CUSTOMER VALUES('000001',
NAME VARCHAR(15));
'Chris');
'Meg');
'John');
SELECT LPAD(NAME, 15, '.') AS NAME FROM CUSTOMER;
289
8249_DB2.fm
Figure 8-21 Result of SELECT statement with LPAD()
Example 8-21 shows the example of RPAD(). Opposite to LPAD(), the result of SELECT
statement which is shown in Figure 8-22 will pad out a value on the right with periods. Note
that 10 is specified as the length parameter in RPAD() so that the result will be returned as 10
digits value.
Example 8-21 SELECT statement with RPAD()
SELECT RPAD(NAME, 10, '.') AS NAME FROM CUSTOMER;
Figure 8-22 Result of SELECT statement with RPAD()
Both of LPAD() and RPAD() can be used for not only single byte character set (SBCS) data
but also double byte character set (DBCS) data, such as Japan Mix CCSID 5035. And also
DBCS characters can be specified as a pad string as well as SBCS characters. Figure 8-23
shows the example of LPAD() for DBCS data within a column which is defined as
VARCHAR(15) CCSID 5035 and aligning each row at the right end. A double byte space
(x4040 in CCSID 5035) is used as a pad string in this example. Like Figure 8-23, specifying
DBCS data as a pad string is required for aligning DBCS data at the right or left end.
Figure 8-23 Result of a example of LPAD() for DBCS data
For more information about LPAD() and RPAD() including the considerations when using for
unicode, DBCS, or SBCS/DBCS mixed data, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafzscalpad.htm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafzscarpad.htm
290
8249_DB2.fm
8.4.10 Pipelined table functions

Pipelined Table Functions, which is already available in DB2 for LUW, are introduced as IBM i
7.2 TR1 timed enhancement. This enhancement also provides as IBM i 7.1 TR9 timed
enhancement. Pipelined Table Functions allow the flexibility to programmatically create
virtual tables with greater than SELECT or CREATE VIEW can provide. Pipelined Table
Functions have an ability of passing a result of an SQL statement or an processing and
returning as the result of UDTFs. Prior to IBM i 7.2 TR1, creating an external UDTF is
required for obtaining the same result as Pipelined Table Function. Example 8-22 shows the
example of creating a pipeline SQL UDTF which returns a table of CURRENT_VALUE from
QSYS2.SYSLIMITS. And Example 8-23 shows the example of creating a external UDTF
which returns a same result of a pipeline SQL UDTF of Example 8-22. These examples
shows that pipelined functions allow the flexibility to code more complex User-Defined Table
Functions purely in SQL without having to build and manage a compiled program or service
program.
Example 8-22 Example of Pipeline SQL UDTF
CREATE FUNCTION producer()

RETURNS TABLE (largest_table_sizes INTEGER)
LANGUAGE SQL
BEGIN
FOR LimitCursor CURSOR FOR
SELECT CURRENT_VALUE
FROM QSYS2.SYSLIMITS
WHERE SIZING_NAME = 'MAXIMUM NUMBER OF ALL ROWS'
ORDER BY CURRENT_VALUE DESC
DO
PIPE (CURRENT_VALUE);
END FOR;
RETURN;
END;
Example 8-23 Example of External UDTF
CRTSQLCI OBJ(applib/producer) SRCFILE(appsrc/c80) COMMIT(*NONE) OUTPUT(*PRINT)

OPTION(*NOGEN)
CRTCMOD MODULE(applib/producer) SRCFILE(qtemp/qsqltemp) TERASPACE(*YES)
STGMDL(*INHERIT)
CRTSRVPGM SRVPGM(applib/udfs) MODULE(applib/producer) EXPORT(*ALL) ACTGRP(*CALLER)
CREATE FUNCTION producer() RETURNS TABLE (int1 INTEGER) EXTERNAL NAME
applib.udfs(producer) LANGUAGE C PARAMETER STYLE SQL
Pipelined table functions can be utilized in such the following case.
UDTF input parameters
Ability to handle errors and warnings
Application logging
References to multiple database in a single query
291
8249_DB2.fm
Customized join behavior

And these table functions are preferred in the case such as only a subset of the result table is
consumed in Big Data/Analytics/Performance scenarios rather than building a temporary
table. Using pipelined table functions provides memory savings and better performance by
avoiding creating a temporary table.
For more information about pipelined table functions, see the developerWorks at:
echnology%20Updates/page/Pipelined%20Table%20Functions
8.4.11 Regular expressions

A regular expression in SQL statement is supported with IBM i 7.2 TR1 timed enhancements.
Regular expression is known as one of the way of expressing a collection of strings as a
single string and is utilized for specifying a pattern for a complex search. Table 8-4 shows
built-in functions and predicate for Regular Expressions in DB2 for i.
Table 8-4 Function or Predicate for Regular Expressions
Function or Predicate
Description
REGEXP_LIKE predicate
Searches for a regular expression pattern in a string and returns True

or False
REGEXP_COUNT
REGEXP_MATCH_COUNT
Returns a count of the number of times that a pattern is matched in

a string
REGEXP_INSTR
Returns the starting or ending position of the matched substring
REGEXP_SUBSTR
REGEXP_EXTRACT
Returns one occurrence of a substring of a string that matches the

pattern
REGEXP_REPLACE
Returns a modified version of the source string where occurrences of

the pattern found in the source string are replaced with the specified
replacement string
Example 8-24 shows the example of regular expressions in a pipelined table function which
searches and returns url candidates from a given string.
Example 8-24 Example of regular expressions in a pipelined table function
CREATE OR REPLACE FUNCTION FindHits(v_search_string CLOB(1M), v_pattern

varchar(32000) DEFAULT '(\w+\.)+((org)|(com)|(gov)|(edu))')
RETURNS TABLE (website_reference varchar(512))
LANGUAGE SQL
BEGIN
DECLARE V_Count INTEGER;
DECLARE LOOPVAR INTEGER DEFAULT 0;
SET V_Count = REGEXP_COUNT(v_search_string, v_pattern,1,'i');
WHILE LOOPVAR < V_Count DO
SET LOOPVAR = LOOPVAR + 1;
PIPE(values(REGEXP_SUBSTR(v_search_string,v_pattern, 1, LOOPVAR, 'i')));
END WHILE;
RETURN;
END;
292
8249_DB2.fm
SELECT * FROM TABLE(FindHits('Are you interested in any of these colleges:

abcd.EDU or www.efgh.Edu. We could even visit WWW.ijkl.edu if we have time.')) A;
For more information about regular expressions, see the developerWorks at:
echnology%20Updates/page/Regular%20Expressions
8.4.12 JOB_NAME & SERVER_MODE_JOB_NAME built-in global variables

New built-in global variables JOB_NAME and SERVER_MODE_JOB_NAME are supported
with IBM i 7.2 TR1 timed enhancements. JOB_NAME contains the name of the current job
and SERVER_MODE_JOB_NAME contains the name of the job that established the SQL
server mode connection.
Each of these global variable has the following characteristics:
It is read-only, with values maintained by system.
The type is VARCHAR(28).
The schema is QSYS2.
The scope of this global variable is session.
If there is no server mode connection, the value of SERVER_MODE_JOB_NAME is NULL.
This means that SERVE_MODE_JOB_NAME is valid for only QSQSRVR and if it referenced
outside of a QSQSRVR job, the NULL value is returned.
For more information about these global variables, see the developerWorks and the DB2 for i
7.2 Database SQL Reference at:
echnology%20Updates/page/JOB_NAME%20%26%20SERVER_MODE_JOB_NAME%20-%20DB2%20built-i
n%20global%20variables
f.pdf
8.4.13 RUNSQL control of output listing

The parameters shown in Figure 8-24 are available in Run SQL (RUNSQL) command with IBM i
7.2 TR1 timed enhancements. RUNSQL command can be used for execute a single SQL
statement. These new parameters work as same as described on the RUNSQLSTM command.
Run SQL (RUNSQL)
Source listing options
Print file . . . . . .
Library . . . . . .
Second level text . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. OPTION
. PRTFILE
.
. SECLVLTXT
*NOLIST
QSYSPRT
*LIBL
*NO
Figure 8-24 New parameters described on the RUNSQL command

293
8249_DB2.fm
For more information about RUNSQL command, see the developerWorks at:
echnology%20Updates/page/RUNSQL%20control%20of%20output%20listing
8.4.14 LOCK TABLE ability to target non-*FIRST members

With IBM i 7.2 TR1 timed enhancements, the LOCK TABLE SQL statement has been
enhanced to allow applications to target specific members within a multiple member physical
file. The application can utilize the Override Database File (OVRDBF) or the CREATE ALIAS
SQL statement to identify the non-*FIRST member.
For more information about LOCK TABLE SQL statement, see the DB2 for i 7.2 Database
SQL Reference at:
f.pdf
8.4.15 QUSRJOBI() retrieval of DB2 built-in global variables

The QUSRJOBI() API JOBI0900 format has been extended to allow for direct access to the
following DB2 for i built-in global variable values that are mentioned in 8.4.5, Built-in global
variables.
CLIENT_IPADDR
CLIENT_HOST
CLIENT_PORT
ROUTINE_TYPE
ROUTINE_SCHEMA
ROUTINE_NAME
For more information about this enhancement including the position of each value in
JOBI0900, see the developerWorks at:
echnology%20Updates/page/QUSRJOBI%28%29%20retrieval%20of%20DB2%20built-in%20global
%20variables
8.5 DB2 for i Services and Catalogs

DB2 for i now allows the programmers to use SQL as traditional programming language, not
only as a query language. Over the time SQL language got new language elements which
allow traditional programming patterns. Using user defined functions, stored procedures,
triggers, and referential integrity support, it is now easy to keep part of the programming logic
encapsulated within the database itself, thus reducing the complexity of programming in 3rd
generation programming language like ILE RPG, ILE C/C++, ILE COBOL, Java, etc.
DB2 for i Catalogs contain information about DB2 related objects like tables, indexes,
schemas, columns, fields, labels, views, etc. There are currently 3 catalog vies:
DB2 for i catalog views (QSYS2)
ODBC and JDBCcatalog views (SYSIBM)
294
8249_DB2.fm
ANS and ISO catalog views (QSYS2)

Note: IBM i Catalogs contain only tables or views related to IBM i operating system only.
DB2 for i Services is consistent set of procedures, user defined functions, user defined table
functions, tables, and views which make programming in SQL easier.
IBM i Services are part of IBM DB2 for i Services. They represent procedures, tables, user
defined functions, user defined table functions, and views which allows the SQL programmer
or user to get information about operating system objects like PTFs, Group PTFs, user
profiles, TCP/IP information, system values, and so on.
Official list of DB2 for i Services is here:
http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqservicessys.htm
Note: IBM i Services provide information related only to IBM i operating system.
8.5.1 IBM DB2 for i Services tables
Table 8-5 DB2 for i Services - Health Center Procedures

Service name
Service
Type
QSYS2.HEALTH_ACTIVITY
DB2 for i Service
Procedure
QSYS2.HEALTH_DATABASE_OVERVIEW
DB2 for i service
Procedure
QSYS2.HEALTH_DESIGN_LIMITS
DB2 for i service
Procedure
QSYS2.HEATH_ENVIRONMENTAL_LIMITS
DB2 for i service
Procedure
QSYS2.HEALTH_SIZE_LIMITS
DB2 for i service
Procedure
QSYS2.RESET_ENVIRONMENTAL_LIMITS
DB2 for i service
Procedure
Service name
Service
Type
QSYS2.CANCEL_SQL
DB2 for i service
Procedure
QSYS2.DUMP_SQL_CURSORS
DB2 for i service
Procedure
QSYS2.EXTRACT_STATEMENTS
DB2 for i service
Procedure
QSYS2.FIND_AND_CANCEL_QSQSRVR_SQL
DB2 for i service
Procedure
QSYS2.FIND_SQSRVR_JOBS
DB2 for i service
Procedure
QSYS2.GENERATE_SQL
DB2 for i service
Procedure
QSYS2.RESTART_IDENTITY
DB2 for i service
Procedure
SYSTOOLS.CHECK_CST
DB2 for i service
Procedure
SYSTOOLS.CHECK_SYSROUTINE
DB2 for i service
Procedure
Table 8-6 DB2 for i Services - Utility Procedures
295
8249_DB2.fm
Table 8-7 DB2 for i Services - Plan Cache Procedures

Service name
Service
Type
QSYS2.CHANGE_PLAN_CACHE_SIZE
DB2 for i service
Procedure
QSYS2.DUMP_PLAN_CACHE
DB2 for i service
Procedure
QSYS2.DUMP_PLAN_CACHE_PROPERTIES
DB2 for i service
Procedure
QSYS2.DUMP_PLAN_CACHE_topN
DB2 for i service
Procedure
QSYS2.DUMP_SNAP_SHOT_PROPERTIES
DB2 for i service
Procedure
QSYS2.END_ALL_PLAN_CACHE_EVENT_MONITOR
DB2 for i service
Procedure
QSYS2.END_PLAN_CACHE_EVENT_MONITOR
DB2 for i service
Procedure
QSYS2.START_PLAN_CACHE_EVENT_MONITOR (2)
DB2 for i service
Procedure
Service name
Service
Type
SYSTOOLS.ACT_ON_INDEX_ADVICE
DB2 for i service
Procedure
SYSTOOLS.HARVEST_INDEX_ADVICE
DB2 for i service
Procedure
QSYS2.OVERRIDE_QAQQINI
DB2 for i service
Procedure
QSYS2.RESET_TABLE_INDEX_STATISTICS
DB2 for i service
Procedure
QSYS2.SYSIXADV
DB2 for i service
Table
SYSTOOLS.REMOVE_INDEXES
DB2 for i service
Procedure
Service name
Service
Type
QSYS2.QCMDEXC
IBM i service
Procedure
QSYS2.OVERRIDE_TABLE
DB2 for i service
Procedure
QSYS2.DELIMIT_NAME
DB2 for i service
UDF
SYSPROC.WLM_SET_CLIENT_INFO
DB2 for i service
Procedure
Service name
Service
Type
QSYS2.FUNCTION_INFO
IBM i service
View
QSYS2.FUNCTION_USAGE
IBM i service
View
QSYS2.GROUP_PROFILE_ENTRIES
IBM i service
View
SYSPROC.SET_COLUMN_ATTRIBUTE
IBM i service
Procedure
QSYS2.SQL_CHECK_AUTHORITY
IBM i service
UDF
QSYS2.USER_INFO
IBM i service
View
Table 8-8 Performance Services
Table 8-9 Application Services
Table 8-10 Security Services
296
8249_DB2.fm
Table 8-11 PTF Services

Service name
Service
Type
QSYS2.PTF_INFO
IBM i service
View
QSYS2.GROUP_PTF_INFO
IBM i service
View
Service name
Service
Type
QSYS2.TCP_INFO
IBM i service
View
SYSIBMADM.ENV_SYS_INFO
IBM i service
View
Service name
Service
Type
QSYS2.SYSTEM_VALUE_INFO
IBM i service
View
QSYS2.GET_JOB_INFO
IBM i service
UDTF
Service name
Service
Type
QSYS2.OBJECT_STATISTICS
IBM i service
UDTF
Service name
Service
Type
QSYS2.SYSDISKSTAT
IBM i service
View
QSYS2.SYSTMPSTG
IBM i service
View
QSYS2.USER_STORAGE
IBM i service
View
Service name
Service
Type
QSYS2.DISPLAY_JOURNAL
IBM i service
UDTF
Service name
Service
Type
QSYS2.SYSLIMTBL
IBM i service
Table
QSYS2.SYSLIMITS
IBM i service
View
Table 8-12 TCP/IP Services
Table 8-13 Work Management Services
Table 8-14 Object Services
Table 8-15 Storage Services
Table 8-16 journal Services
Table 8-17 System Health Services
8.5.2 IBM DB2 for i Catalogs tables
297
8249_DB2.fm
Table 8-18 Catalogs

Name
Catalog type
SYSCATALOGS
DB2
INFORMATION_SCHEMA_CATALOG_NAME
ANS/ISO
Table 8-19 Schemas

Name
Catalog type
SYSSCHEMAS
DB2
SQLSCHEMAS
ODBC/JDBC
SCHEMATA
ANS/ISO
Table 8-20 Database Support

Name
Catalog type
SQL_FEATURES
ANS/ISO
SQL_LANGUAGES
ANS/ISO
SQL_SIZING
ANS/ISO
CHARACTER_SETS
ANS/ISO
Table 8-21 Tables - Views - Indexes

Name
Catalog type
SYSCOLUMS
DB2
SYSCOLUMS2
DB2
SYSFIELDS
DB2
SYSINDEXES
DB2
SYSKEYS
DB2
SYSTABLEDEP
DB2
SYSTABLES
DB2
SYSVIEWDEP
DB2
SYSVIEWS
DB2
SQLCOLUMNS
ODBC/JDBC
SQLSPECIALCOLUMNS
ODBC/JDBC
SQLTABLES
ODBC/JDBC
COLUMNS
ANS/ISO
TABLES
ANS/ISO
VIEWS
ANS/ISO
298
8249_DB2.fm
Table 8-22 Constraints

Name
Catalog type
SYSCHKCST
DB2
SYSCST
DB2
SYSCSTCOL
DB2
SYSCSTDEP
DB2
SYSKEYCST
DB2
SYSREFCST
DB2
SQLFOREIGNKEYS
ODBC/JDBC
SQLPRIMARYKEYS
ODBC/JDBC
CHECK_CONSTRAINTS
ANS/ISO
REFERENTIAL_CONSTRAINTS
ANS/ISO
TABLE_CONSTRAINTS
ANS/ISO
Table 8-23 Privileges

Name
Catalog type
SYSCOLAUTH
DB2
SYSCONTROLS
DB2
SYSCONTROLSDEP
DB2
SYSPACKAGEAUTH
DB2
SYSROUTINEAUTH
DB2
SYSSCHEMAAUTH
DB2
SYSSEQUENCEAUTH
DB2
SYSTABAUTH
DB2
SYSUDTAUTH
DB2
SYSVARIABLEAUTH
DB2
SYSXSROBJECTAUTH
DB2
SQLCOLPRIVILEGES
ODBC/JDBC
SQLTABLEPRIVILEGES
ODBC/JDBC
AUTHORIZATIONS
ANS/ISO
ROUTINE_PRIVILEGES
ANS/ISO
UDT_PRIVILEGES
ANS/ISO
USAGE_PRIVILEGES
ANS/ISO
VARIABLE_PRIVILEGES
ANS/ISO
299
8249_DB2.fm
Table 8-24 Triggers

Name
Catalog type
SYSTRIGCOL
DB2
SYSTRIGDEP
DB2
SYSTRIGGERS
DB2
SYSTRIGUPD
DB2
Table 8-25 ROUTINES

Name
Catalog type
SYSFUNCS
DB2
SYSJARCONTENTS
DB2
SYSPARMS
DB2
SYSPROCS
DB2
SYSROUTINEDEP
DB2
SYSROUTINES
DB2
SQLFUNCTIONSCOLSS
ODBC/JDBC
SQLFUNCTIONS
ODBC/JDBC
SQLPROCEDURECOLS
ODBC/JDBC
SQLPROCEDURES
ODBC/JDBC
PARAMETERS
ANS/ISO
ROUTINES
ANS/ISO
Table 8-26 XML Schemas

Name
Catalog type
XSRANNOTATIONINFO
DB2
XSROBJECTCOMPONENTS2
DB2
XSROBJECTHIERARCHIES
DB2
XSROBJECTS
DB2
Table 8-27 Statistics

Name
Catalog type
SYSCOLUMSTAT
DB2
SYSINDEXSTAT
DB2
SYSMQTSTAT
DB2
SYSPACKAGESTAT
DB2
SYSPACKAGESTMTSTAT
DB2
SYSPARTITIONDISK
DB2
300
Name
Catalog type
SYSPARTITIONINDEXES
DB2
SYSPARTITIONINDEXDISK
DB2
SYSPARTITIONINDEXSTAT
DB2
SYSPARTITIONMQTS
DB2
SYSPARTITIONSTAT
DB2
SYSPROGRAMSTAT
DB2
SYSPROGRAMSTMTSTAT
DB2
SYSTABLEINDEXSTAT
DB2
SYSTABLESTAT
DB2
SQLSTATISTICS
ODBC/JDBC
8249_DB2.fm
Table 8-28 Miscellaneous objects

Name
Catalog type
SYSPACKAGE
DB2
SYSSEQUENCES
DB2
SYSTYPES
DB2
SYSVARIABLEDEP
DB2
SYSVARIABLES
DB2
SQLTYPEINFO
ODBC/JDBC
SQLUDTS
ODBC/JDBC
USER_DEFINED_TYPES
ANS/ISO
SEQUENCES
ANS/ISO
8.6 DB2 performance

In the IBM i 7.2 release of DB2 for i, a considerable effort was undertaken to enhance the
runtime performance of the database, either by extending existing functions or by introducing
new mechanisms.
Runtime performance is affected by many issues, such as the database design (the
entity-relationship model, which is a conceptual schema or semantic data model of a
relational database), the redundancy between functional environments in composite
application environment, the level of normalization, and the size and volumes processed. All
of these items influence the run time, throughput, or response time, which is supported by the
IT components and is defined by the needs of the business. Performance optimization for
database access must address all the components that are used in obtained acceptable and
301
8249_DB2.fm
sustainable results, covering the functional aspects and the technical components that
support them.
This section describes DB2 for i performance related enhancements in IBM i 7.2. To benefit
from them neither application or system configuration changes are needed in most cases.
8.6.1 SQE I/O cost model

SQL Query Engine (SQE) uses structure called access plan for every database query in
order to retrieve the data in an optimized manner. An access plan is a control structure that
describes the actions necessary to satisfy each query request. It contains information about
the data and how to extract it. For any query, whenever optimization occurs, the query
optimizer develops an optimized plan of how to access the requested data. Preparing
optimized access plan is a complex task and requires the optimizer to rely on many sources
of information. One of them is I/O cost for accessing database object (table scan, index probe,
and so on). I/O cost can be described as amount of time needed for all I/O operations
required to access the object. Prior to IBM i 7.2, I/O cost model was based on the assumption
that any I/O operation time was 25 milliseconds, regardless of the configuration of the system
and attached storage solution. In response to significant HW changes including storage
solutions for modern IBM i systems, and Big Data paradigm that is often reflected in I/O
intensive database operations, I/O cost model in 7.2 has changed. Table 8-29 compares disk
read times for various IBM i storage types with original SQE I/O cost model.
Table 8-29 Disk read times for storage technologies compared to original SQE cost model
Storage technology
Typical read time in

millisecondsa
Internal Disks
from 4 to10
External Disks/SAN
from 1 to 6
Solid State Drives (SSD)
less than 1
Original SQE model
25
a. Disk read times depend on many factors and may

differ between environments
Now SQE optimizer relies on sample actual access times instead of fixed value. Hence, the
optimizer is provided with more accurate disk read times which results in more accurate I/O
cost calculation. More accurate I/O cost prediction means better access plan preparation for
faster query execution. Sample access times are measured during every IPL and at
independent ASP vary on time by recording disk read times for sample pages. These sample
times are evaulated and updated at appropriate intervals during system operation. This
ensures that the optimizer always has a current view of disk performance. This data allows
the optimizer to distinguish unique I/O performance characteristics for internal, external, and
solid state drives.
As a result, for modern systems, I/O cost is now often lower (comparing to original SQE cost
model based on 25 millisecond read operation - see Table 8-29 on page 302), hence SQE
processes I/O in a more intensive manner (more aggressively). In many cases, this results in
a moderate performance improvement for I/O intensive queries comparing to IBM i 7.1
running on the same hardware. In one example workload, online analytical processing
(OLAP) queries with an execution time > 3 seconds ran about 30% faster1. OLAP queries are
important part of Big Data and Analytical processing.
302
8249_DB2.fm
8.6.2 SQE support for native file opens, Query/400, and OPNQRYF
Release to release SQE has been enhanced to support broader scope of database
operations, SQL statements, and IBM i interfaces. The purpose of these efforts hasnt
changed since introduction of SQE in V5R2. SQE can process database access and execute
queries faster than classic query engine (CQE). It also provides more detailed information,
kept in the plan cache, about query implementation and statistics. This data can be used by
the database application developers and DB2 engineers to optimize query performance.
Investigation DB2 for i performance problems is easier when SQE processes query instead of
CQE.
Accessing data through following DB2 for i interfaces is now supported by SQE, without any
application or user change:
file open and read operations in programs written in high level languages (like: COBOL,
RPG, C++) for tables with RCAC enabled only
Open Data Base File (OPNDBF) CL command for native SQL views and partitioned tables
opens
Open Query File (OPNQRYF) CL command
IBM Query for i (formerly Query/400) licensed program 5770QU1
New option SQE_NATIVE_ACCESS is now available in QAQQINI file that allows to change default
behavior of IBM i 7.2 and force CQE to process native opens in HLL programs, OPNDBF,
OPNQRYF, or IBM Query for i queries. Table 8-30 on page 303 describes values available for
SQE_NATIVE_ACCESS option.
Table 8-30 SQE_NATIVE_ACCESS parameter values in QAQQINI file
Value
Description
*NO
V7R1 native open unless SQE is requireda
*YES
SQE will attempt to implement native open of an SQL view or

native query
*DEFAULT
The same as *YES
a. SQE is required for: RCAC enabled tables, sequence objects, global variables,
OLAP, CUBE, ROLLUP
Using IBM System i Navigator one can search SQL plan cache for statements using native
opens if the statement was processed by the SQE. Figure 8-25 shows SQL Plan Cache
Statements view for OPNQRYF statements and Visual Explain view for the selected
statement. Highlighted Query Engine Used value is SQE.
Note: Use OPNDBF string for searching for OPNDBF native open statements and
QUERY/400 string for searching for IBM Query for i native open statements.
Note: performance gains are complex to anticipate and they are strongy related to the application design and
environment configuration. 30% in the provided example is simply measured improvement for one set of OLAP
queries in one environment. It does not mean the same result for other environments and applications.
303
8249_DB2.fm
Figure 8-25 SQL Plan Cache Statements and Visual Explain view for OPNQRYF
One can see the same statements by using IBM Navigator for i web interface. Under
Database section expand Databases and right click the database of your choice in the
Databases tab. Select SQL Plan Cache Show Statements.... Filters view allows to filter
statements using the same criteria as for IBM System i Navigator. Though, Visual Explain
functionality is not available from the web interface at the time of writing of this publication.
Figure 8-26 SQL Plan Cache Statements view for OPNQRYF within IBM Navigator for i
304
8249_DB2.fm
For more information about CQE, SQE, query dispatcher, and SQL plan cache, see IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/queryoptimize.htm
?lang=en
For more information about QAQQINI file and its options, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/qryopt.htm?lang=e
n
8.6.3 PDI for DB2

Performance Data Investigator (PDI) has been significantly enhanced to allow database
engineers (DBE) and administrators (DBA) quickly access database performance related
information. PDI is part of IBM Navigator for i tool and is accessible through Investigate Data
link under Performance section. It is a common interface for variety of performance data
collected on IBM i system. Database content page of the PDI requires IBM Performance
Tools for i (5770-PT1) Option 1 - Manager Feature licensed program installed.
Figure 8-27 on page 306 shows perspectives available as a Database part of the PDI in IBM i
7.2.
305
8249_DB2.fm
Figure 8-27 New Database related perspectives for PDI
Starting from top level system-wide overview DBE or DBA can step into more detailed
sections of the performance data related to particular job or thread or SQL plan cache.
Figure 8-28 on page 307 PDI view of SQL CPU utilization for jobs and tasks.
306
8249_DB2.fm
Figure 8-28 SQL CPU Utilization by Job and Task PDI view
PDI data can be presented in graphs or tables. One can choose performance data files (either
current or previous), zoom in and out range of intervals of interest, or even modify SQL
statement to retrieve other than default set of data.
Sample Plan Cache Searches view is shown on Figure 8-29 on page 308.
307
8249_DB2.fm
Figure 8-29 Plan Cache Searches PDI view
For more information about PDI, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahx/rzahxpdilaunch.ht
m?lang=en
8.6.4 Queries with a long IN predicate list

In IBM i 7.2 SQE will recognize when a large number of values are specified on an IN list and
automatically convert the IN list to a more efficient INNER JOIN.
8.6.5 Index advice and OR predicates

In IBM i 7.2 Index Advisor has been extended to include queries that OR together local
selection (WHERE clause) columns over a single table. OR advice requires two or more
indexes to be created as a dependent set. If any of the OR'd indexes are missing, the
optimizer wont be able to cost and choose these dependent indexes for implementation of
the OR based query.
This relationship between OR based indexes in the SYSIXADV index advice table is with a
new DEPENDENT_ADVICE_COUNT column.
For more information about Index Advisor, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/idxadvisor.htm?la
ng=en
For more information about index advice and OR predicates, see IBM i 7.2 Knowledge Center
at:
308
8249_DB2.fm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqidxadvorpred
.htm?lang=en
8.6.6 KEEP IN MEMORY for tables and indexes

Prior to IBM i 7.1, the only way to pre-load an object into main storage pool was the Set
Object Access (SETOBJACC) CL command. Loading database files or programs in to a main
storage pool significantly reduces data access time and therefore results in performance
gains. Effect of the SETOBJACC command is temporary and does not persist over an IPL. In
order to remove the object from the main storage, run the SETOBJACC command with the
*PURGE option.
In IBM i 7.1, the CHGPF and CHGLF CL commands have been extended with Keep in memory
parameter (KEEPINMEM) to allow the operating system to automatically bring a table or index
into main storage pool when the table or index is used in a query. For queries running within
SQE this enhancement results in performance gains. The operating system also
automatically purges the objects with the memory-preference from the main store when no
longer used by the query.
IBM i 7.2 has been enhanced with the comprehensive support for the keep-in-memory. The
following SQL statements have been extended with the KEEP IN MEMORY keyword:
CREATE TABLE
CREATE INDEX
ALTER TABLE
DECLARE GLOBAL TEMPORARY TABLE
A new option called MEMORY_POOL_PREFERENCE is now available in the QAQQINI file that allows
you to direct the database engine to attempt to load objects to a specified storage pool. This
option does not guarantee that specified storage pool is used. Table 8-31 describes values
available for the MEMORY_POOL_PREFERENCE option.
Table 8-31 MEMORY_POOL_PREFERENCE parameter values
Value
Description
*JOB
Storage pool of the job is attempted to use.
*BASE
Base storage pool is attempted to use.
nn
Storage pool nn is attempted to use.
*DEFAULT
The same as *JOB
The Display File Description (DSPFD) CL command output has been extended with the new
Keep in memory field, under the Data Base File Attributes section, as shown on
Example 8-25.
Example 8-25 DSPDF partial output with Keep in memory field
Access path . . . . . . . .
Maximum record length . . .
Volatile . . . . . . . . .
Keep in memory . . . . . .
File is currently journaled
Current or last journal . .
Library . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:
:
:
: KEEPINMEM
:
:
:
Arrival
26
No
*YES
Yes
QSQJRN
CORPDB
309
8249_DB2.fm
This enhancement, also known as memory-preference, is comprehensive and affects all

available BD2 management interfaces:
CL commands (as already presented)
IBM System i Navigator
IBM Navigator for i
Figure 8-30 on page 310 shows memory-preference information on a definition of a table,
available from IBM System i Navigator.
Figure 8-30 Memory-preference information for table definition on IBM System i Navigator
Figure 8-31 on page 311 shows memory-preference information on a description of a table,

310
8249_DB2.fm
Figure 8-31 Memory-preference information for table description on IBM System i Navigator
Figure 8-32 on page 312 shows memory-preference information on a definition of an index,

311
8249_DB2.fm
Figure 8-32 Memory-preference information for index definition on IBM System i Navigator
Figure 8-33 on page 313 shows memory-preference information on a description of an index,

312
8249_DB2.fm
Figure 8-33 Memory-preference information for index description on IBM System i Navigator
The same information is available from IBM Navigator for i.

Figure 8-34 on page 314 shows memory-preference information on a definition of a table,
available from IBM Navigator for i.
313
8249_DB2.fm
Figure 8-34 Memory-preference information for table definition on IBM Navigator for i
Figure 8-35 on page 314 shows memory-preference information on a description of a table,

Figure 8-35 Memory-preference information for table description on IBM Navigator for i
Figure 8-36 on page 315 shows memory-preference information on a definition of an index,

314
8249_DB2.fm
Figure 8-36 Memory-preference information for index definition on IBM Navigator for i
Figure 8-37 on page 315 shows memory-preference information on a description of an index,

Figure 8-37 Memory-preference information for index description on IBM Navigator for i
For more information about memory-preference enhancement, see IBM i Technology

Updates site at:
315
8249_DB2.fm
echnology%20Updates/page/Comprehensive%20support%20for%20%E2%80%98Keep%20In%20Memo
ry%E2%80%99
For more information about DB2 for i SQL statements, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafzintro.htm?lang
=en
n
8.6.7 Collection Services enhancements

Collection Services now collect SQL statistics on a job and system level. Following is a list of
performance data files extended with SQL information:
QAPMJOBOS - data specific to system jobs
QAPMSYSTEM - system-wide performance data
A new file QAPMSQLPC is now available. It contains the performance data about the SQL Plan
Cache collected by the *SQL collection category.
For more information about collection services files descriptions, see IBM i 7.2 Knowledge
Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahx/rzahxcatfilerelat
ion.htm?lang=en
8.7 Database engineering

Data-Centric approach requires performing various tasks, by database engineers (DBE), on a
daily basis. Examples of these tasks include:
database security management

database architecture management for particular business applications and goals
database performance analysis and tuning
database problem identification and resolution
database backup and recovery management
and other
IBM i 7.2 DB2 enhancements strongly support DBEs. Following section describes new
features and enhancements of the existing tools.
Database performance related enhancements are described in DB2 performance on
page 301.
8.7.1 IBM System i Navigator DB2 related functionality

While IBM Navigator for i has been enhanced with impressive support for database engineers
(see section IBM Navigator for i DB2 related functionality on page 320 of this publication),
IBM System i Navigator remains a tool of choice for a number of users. IBM System i
Navigator is currently the only tool that supports Visual Explain and Run SQL Scripts
316
8249_DB2.fm
functionality. It continues to be enhanced twice a year by updates service packs. Many of the
IBM i 7.2 database enhancements are reflected in the latest IBM System i Navigator updates.
Note: In order to leverage all the available enhancements of the IBM System i Navigator,
user need to install the latest IBM i Access for Windows service pack for 7.1. The 7.1 client
software contains all the IBM System i Navigator enhancements for 7.2! Also, users need
to install the latest DB2 PTF Group on the managed system.
Date Created column has been added to the Indexes view of a particular schema, for better
manageability as shown on Figure 8-38 on page 317. The view on Figure 8-38 on page 317
has been filtered for readability reasons.
Figure 8-38 New Date Created column on the Indexes list panel. Filtered view
For more information about index creation date within IBM System i Navigator panel and
system catalogs, see:
echnology%20Updates/page/Index%20%27Creation%20date%27%20added%20to%20Navigator%E2
%80%99s%20Schemas%20%26%20DB2%20for%20i%20Catalogs
SQL Performance Monitor Wizard now supports up to ten user names or group names and
generic names in the Current user or group profile field. New Host variable values (see
Figure 8-39 on page 318) field can control the way how values of the host variables are
caputer when the monitor is active. Following values are available:
*BASE value is the same behavior as on IBM 7.1 and earlier
*CONDENSED value allows for less overhead to the database
*SECURE prevents host variable values from being visible in the collected data
317
8249_DB2.fm
Figure 8-39 SQL Performance Monitor Wizard enhancements
For more information about Host variables values parameter for SQL Performance Monitors,
see:
echnology%20Updates/page/Database%20monitor%20with%20condensed%20host%20variables%
20capture
Table and partition definition information has been extended with Preferred storage media is
solid-state drive and Keep in memory fields as shown on Figure 8-40 on page 319. Show
SQL function has been enhanced to support these changes.
318
8249_DB2.fm
Figure 8-40 New fields on the table definition panel
Visual Explain now allows to see detailed program statements for user-defined table functions
(UDTF) as presented on Figure 8-41.
Figure 8-41 Specific Program Statements for user-defined table function in Visual Explain
319
8249_DB2.fm
For more information about Specific Program Statements for UDTF at Visual Explain, see:
echnology%20Updates/page/Visual%20Explain%20ability%20to%20drill%20into%20a%20UDTF
New system procedures has been added to automate SQL plan cache snatpshot and event
monitors import and removal. Prior to this change one had to perform these operations
manually from the IBM System i Navigator. Following are the new procedures:
QSYS2/IMPORT_PLAN_CACHE()
QSYS2/REMOVE_PLAN_CACHE()
QSYS2/IMPORT_EVENT_MONITOR()
QSYS2/REMOVE_EVENT_MONITOR()
For more information about automating SQL plan cache operations, see:
echnology%20Updates/page/Automated%20DBE%20tasks%20for%20Navigator
For more information about IBM System i Navigator, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahg/rzahginav.htm?lan
g=en
8.7.2 IBM Navigator for i DB2 related functionality

IBM Navigator for i has become a robust tool for IBM i management and currently allows to
administer and control all areas of the system. IBM Navigator for i is intended to replace IBM
System i Navigator tool in the future. Majority of the IBM Navigator for i enhancements are not
available in other tools. DB2 engineering functionality of the tool is not an exception of this
rule. Enhancements introduced to IBM System i Navigator are also available for IBM
Navigator for i except Visual Explain UDTF statements.
Significant number of improvements has been done in the Database perspective resulting in
enhanced usability and performance of the web tool. Key changes are:
re-designed panels for better usability and performance in a web browser:
Select Schemas
SQL Details for Jobs
Show Status (Table Reorganizations, Table Alters, Index Builds, OmniFind text index
builds)
Grid Column Chooser
performance changes to improve list retrieval, filtering, and data compression
usability changes to display lists resulting from database actions in a separate tab for
easier navigation between lists
usability changes to display selected dialogs as dojo popups
quick path access to several Database panels
On Demand Performance Center groups menu options and perspectives related to database
performance like SQL plan cache or index advisor. Following changes have been made to On
Demand Performance Center:
A menu option has been added to SQL Plan Cache snapshots and SQL database
performance monitors to view overview charts in Performance Data Investigator. See
A menu option has been added to a selected statement in the SQL Plan Cache to see the
job history for that statement. See Figure 8-43 on page 321.
320
8249_DB2.fm
Additional filters will be used when selecting to show the statements for a row from the
index advisor and condensed index advice lists. This will provide a better match of
statements that generated the advice in the SQL Plan Cache.
The index advisor list now includes a column with the times the index was advised when it
was dependent on other index advice. See Figure 8-44 on page 322.
A filter has been added to the Show Statements panel filters, which specifies whether the
other filters all need to match. See Figure 8-45 on page 322.
Figure 8-42 shows the new Investigate Performance Data menu option on the SQL Plan
Cache Snapshots panel. This option allows you to navigate directly to PDI for snapshot
analysis.
Figure 8-42 Investigate Performance Data menu option
Figure 8-43 shows new menu option Show Job History for selected statement on the SQL
Plan Cache Statements panel. It allows for viewing the jobs that run selected statement.
Figure 8-43 New Show Job History menu option on the SQL Plan Cache Statements panel
321
8249_DB2.fm
Figure 8-44 on page 322 shows new column Times Advised Dependent on Other Advice on
the Index Advisor view. The columns on the Figure 8-44 on page 322 are filtered for
readability.
Figure 8-44 New column Times Advised Dependent on Other Advice on Index Advisor panel
Figure 8-45 shows new filter option on the Show Statements panel filters, which specifies
whether the other filters all need to match.
Figure 8-45 New filter option on the Show Statements Filters panel
Database management has been extended with the following features:

Support for new database features; Row Permissions and Column Masks, and the ability
to activate these row and column level security capabilities on tables, Ability to define
multiple event triggers, Ability to define named parameters and default values for
parameters in SQL stored procedures and functions. For details, see section 8.2.1,
IQIBM_DB_SECADM function usage on page 265 of this publication.
Generate SQL now supports several new options (see Figure 8-46 on page 323):
ability to obfuscate an SQL trigger, function or procedure
ability to specify whether to schema qualify objects
ability to add the OR REPLACE clause
ability to add KEEP IN MEMORY clause
Support has been added to view the contents of a table. See Figure 8-47 on page 324.
Support for memory-preference for tables and indexes. See section 8.6.6, KEEP IN
MEMORY for tables and indexes on page 309 of this publication.
322
8249_DB2.fm
Figure 8-46 on page 323 shows new options available on Generate SQL panel.
Figure 8-46 New options available on Generate SQL panel
Figure 8-47 on page 324 shows new menu option View Contents on the Tables panel which
allows to browse and filter data within the specified table.
323
8249_DB2.fm
Figure 8-47 New View Contents menu option on Tables panel
Table Reorganizations status has been extended with the following information (see
Figure 8-48 on page 325):
record number where the reorganization started
number of deleted rows during reorganization
amount of storage returned because of deleted records
324
8249_DB2.fm
Figure 8-48 New information on the Table Reorganization status panel
For more information about general enhancements of the IBM Navigator for i, see section 2.1,
IBM Navigator for i on page 16. For more information about PDI database related changes,
see section 8.6.3, PDI for DB2 on page 305. For more information about DB2 for i, see the
IBM i 7.2 Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/dbmult/rzaf3kickoff.htm
8.7.3 Queued exclusive locks

New option PREVENT_ADDITIONAL_CONFLICTING_LOCKS is now available in QAQQINI file that
allows to direct database engine to give preference to the operation that requires an exclusive
lock over the operations to lock the object for reading. This might be useful in situations where
application activity on database is high and can not be quiesced, thus obtaining exclusive
non-read lock would be hard or even impossible. Table 8-32 describes values available for the
PREVENT_ADDITIONAL_CONFLICTING_LOCKS option.
Table 8-32 PREVENT_ADDITIONAL_CONFLICTING_LOCKS parameter values
Value
Description
*NO
When a job requests an exclusive lock on an object, do not prevent concurrent jobs
from acquiring additional exclusive locks on the object.
*YES
New requests for read locks will be queued behind the exclusive lock request and
wait until the exclusive lock completes or times out.
*DEFAULT
The same as *NO
325
8249_DB2.fm
The following SQL operations are affected by this new option, as exclusive lock requests:
ALTER TABLE (add, alter or drop column)

CREATE TRIGGER
LOCK TABLE
RENAME TABLE
For more information about DB2 for i SQL statements, see the IBM i 7.2 Knowledge Center:
=en
n
8.7.4 CREATE TABLE AS SELECT from remote RDB

It is now possible to create, on local system, a table that references one or more tables on a
remote server. Along with the select-statement, one can specify copy options to get attributes
such as the default values or identity column information copied for the new table. The WITH
DATA or WITH NO DATA clause must be specified to indicate whether to populate the table from
the remote system. Remote server connection must be defined as relational database entry
(WRKRDBDIRE). Example 8-26 shows how to create a table which definition reflects table on a
remote server and populate it with the data from the remote server.
Example 8-26 Creating a table that reflects definition on a remote server with data
CREATE TABLE EMPLOYEE4 AS

(SELECT PROJNO, PROJNAME, DEPTNO
FROM REMOTESYS.TESTSCHEMA.EMPLOYEE
WHERE DEPTNO = 'D11') WITH DATA
For more information about creating tables that reference remote database, see IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/sqlp/rbafycrttblrmt.htm
?lang=en
8.7.5 Live movement of tables and indexes to SSD

Media preference on SQL tables, SQL views, and SQL indexes (Preferred storage unit
parameter on CHGPF and CHGLF CL commands) can now be changed without obtaining
exclusive lock on the file. The change can be made when shared read (*SHRRD) or update
(*UPDATE) lock exists on the file being changed. After the *SSD was specified as a preferred
storage media, data will asynchronously move to the SSD drives.
8.7.6 Range partitioned tables

Ranged partitioned tables can now be created with partitions out of order as shown on
Example 8-27. On previous releases of IBM i 7.2 error SQL0636 - Ranges specified for
partition &1 not valid was returned in such case.
326
8249_DB2.fm
Example 8-27 Creating range partitioned table with partitions out of order
CREATE TABLE CORPDB.SALES_TABLE FOR SYSTEM NAME SALES00002 (

TRANS_DATE TIMESTAMP DEFAULT NULL)
PARTITION BY RANGE (TRANS_DATE NULLS LAST) (
PARTITION PART000001
STARTING ( '2014-01-01-00.00.00.000000' ) INCLUSIVE
ENDING ( '2014-01-31-23.59.59.999999' ) INCLUSIVE,
ENDING ( '2014-08-31-23.59.59.999999' ) INCLUSIVE,
ENDING ( '2014-05-31-23.59.59.999999' ) INCLUSIVE )
As a result, the SALES_TABLE range partitioned table was successfully created.
For range partitioned tables DB2 for i now recognizes if update operation is made to the
column which was used for range partitioning. If the update affects partition assignment of the
row, the row is automatically moved to the correct partition (database file member).
For more information about partitioned tables, see IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/dbmult/partitionedtable
s.htm?lang=en
For more information about DB2 for i SQL statements, see IBM i 7.2 Knowledge Center at:
=en
8.8 DB2 Web Query for i (5733-WQX, 5733-WQE, and

5733-WQS)
DB2 Web Query for i V2.1.0, which provides core analytics and BI (Business Intelligence)
platform capabilities including queries, reporting, OLAP, and dashboards, is supported. DB2
Web Query for i is available either Standard Edition or Express Edition in IBM i 7.2.
DB2 Web Query for i Express Edition provides an entry level software bundle that includes
report authoring tools, Query/400 import function, and analytic reporting options for a small
number of users. With Express Edition, you can generate high quality reports as well as
OLAP reports for analysts interested in understanding trends or finding exceptions in the data
to uncover what is driving results. Also, you can leverage the spreadsheet pivot table support
and integrate ad-hoc reporting directly into Microsoft Excel spreadsheets. DB2 Web Query for
i provides an array of mobile capabilities. For example, for those with mobile devices who
need to analyze data while on the road, the Active Technologies provide analytics for the
users disconnected from the server.
DB2 Web Query Standard Edition combines all of the functions included in Express Edition
plus more, providing a robust offering that can support up to thousands of users running
reports. With Standard Edition, user licenses are included to support a typical roll out of
developers and administrators, report authors, and a virtually unlimited number of run-time
users and report consumers. With Standard Edition, you can build more sophisticated
dashboards for executives monitoring key performance indicators. Use Standard Edition to
create an enterprise report distribution model with the abilities to schedule report execution
and distribution through e-mail or save the reports for later viewing. Optionally, leverage the
327
8249_DB2.fm
data adapter for Microsoft SQL Server included in Standard Edition to be able to build reports
including data from any of those databases in your network.
Each Edition of DB2 Web Query for i has its own unique ordering Product ID as mentioned
above. Express Edition is represented as 5733-WQE, and Standard Edition is 5733-WQS.
However, the Product ID that is actually installed on the system is 5733-WQX. Control of
whether you are able to use Express or Standard Edition is done by enabling the appropriate
feature through using IBM i License Management.
In addition to the data adapter for Microsoft SQL Server, the JD Edwards adapter is available
as a separate option of Standard Edition. This adapter allows you to connect to your JD
Edwards and view the information that is stored in JD Edwards as a data source of DB2 Web
Query for i environment.
For details of DB2 Web Query for i, refer to IBM DB2 Web Query for i Version 2.1
Implementation Guide, SG24-8063, available at:
DB2 Web Query for i is as independent product from DB2 for i. Enhancements and updates of
DB2 Web Query for i are provided as a separate PTF Group from DB2 for i PTG Group. In the
DB2 Web Query for i world, PTF Group is also called a hotfix. In recent hotfixes, the following
enhancements were delivered:
Leveraging Workload Group Controls
Run-time environment change from Light Weight Infrastructure (LWI) to IBM WebSphere
Liberty Profile
DB2 for z/OS Support
DB2 LUW (Linux, Unix, Windows) Support
Single Sign On capability with Kerberos
RESTful Web Services
For information on the latest DB2 Web Query for i PTF Group, refer to the following website:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W516d8b60d3
2c_4fc5_a811_5f3d840bf524/page/PTFs%20and%20On-going%20Service
8.9 OmniFind Text Search Server for DB2 for i (5733-OMF)

OmniFind Text Search Server for DB2 for i (5733-OMF V1R3M0) is available for IBM i 7.2 with
no charge. This product is not only used as an text search engine for the documents that is
stored in DB2 for i but also provides extensions that enables search for IBM i objects such as
spool files in output queue or stream files in the Integrated File System (IFS).
A text search collection describes one or more sets of system objects that will have their
associated text data indexed and searched. For example, a collection may contain an object
set of all spool files in output queue QUSRSYS/QEZJOBLOG, and/or an object set for all
stream files in directory '/home/alice/text_data'.
The text search collection referred to in this documentation should not be confused with a
DB2 schema (sometimes also referred to as a collection), or a Lucene collection (Part of the
internal structure of a DB2 text search index).
When a text search collection is created, several DB2 objects are created on the system in an
SQL schema. The following objects will be created in the schema:
328
8249_DB2.fm
Catalogs for tracking the collection's configuration.

Catalogs for tracking the objects that have been indexed.
SQL Stored procedures to administer and search the collection.
A DB2 text search index for indexing the associated text.
Administration of the collection is provided with stored procedures, most of which are created
in the schema.
In OmniFind Text Search Server for DB2 for i V1R3M0, the following enhancements are
included:
Extensions to Index and Search Non-DB2 Data
Adding an Object Set for Multiple Members Source Physical File
Adding an Object Set for Stream File Data
Altering a Text Search Collection
Remove Object Set by attribute
Removing Object Set for Spool File Data
Removing Object Set for Stream File Data
Removing an Object Set for Multiple Members Source Physical File
Searching for special characters

Remove orphaned indexes
Shutdown server
Check status and return code for each row in warning or error state
RCAC support
Create secured text search index
Alter text search index to secured index
For more information about the enhancements in OmniFind Text Search Server for DB2 for i
V1R3M0, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzash/rzashwhatsnew.htm
And see also the developerWorks at:
echnology%20Updates/page/OmniFind%20for%20IBM%20i
329
8249_DB2.fm
330
8249_AppDev.fm
Chapter 9.
Application development
This chapter describes the following topics:
9.1, Languages and Compilers on page 332

9.2, Java on i on page 348
9.3, Rational Tools for i on page 352
9.4, PASE on page 370
9.5, Ruby on Rails for i on page 370
9.6, Zend Server and PHP on i on page 370
9.7, Mobile application development for IBM i on page 374
This chapter shows selection of products from IBM and 3rd party providers which can be
selected for developing of different types of applications for IBM i, or using IBM i as
application or database server. Detailed information about application development and
modernization tools can be found in these IBM Redbooks and Redpapers:
Modernizing IBM i Applications from the Database up to the User Interface and Everything
in Between, SG24-8185
Tools and Solutions for Modernizing Your IBM i Applications, REDP-5095
331
8249_AppDev.fm
9.1 Languages and Compilers

IBM i provides many choices of languages for making programs for example IBM Integrated
Language Environment (ILE). This section introduces enhancements with IBM i 7.2 of the
following typical languages and compilers including ILE:
Control Language (CL)

ILE RPG
ILE COBOL
ILE C/C++
System APIs
9.1.1 Control Language (CL)

This section covers the following topics:
New CL retrieve exit programs running after command completion
New built-in functions support for both ILE CL and OPM CL
New CL retrieve exit programs running after command completion

The IBM i command analyzer support for the QIBM_QCA_RTV_COMMAND exit point has
been enhanced. The registered exit programs were always called just before control was
transferred to the command processing program (CPP) associated with the command being
run. Now, you will be able to register an exit program for the QIBM_QCA_RTV_COMMAND
exit point and indicate that you want the exit program to be called after control returns from
the CPP.
For more information about QIBM_QCA_RTV_COMMAND, see the IBM i 7.2 Knowledge
Center at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rbam6/cmdan
alyz.htm
New built-in functions support for both ILE CL and OPM CL

Many of new build-in functions that are similar to RPG built-in functions are available in both
ILE CL and OPM CL. The following six new built-in functions are supported for working with
character strings:
%CHECK and %CHECKR built-in function
%SCAN built-in function
%TRIM, %TRIML, and %TRIMR built-in function
The following six new built-in functions are supported for conversion operation:
%CHAR built-in function

%DEC built-in function
%INT built-in function
%UINT built-in function
%LOWER built-in function
%UPPER built-in function
And the following two new built-in functions are supported for size operation:
%LEN built-in function
%SIZE built-in function
332
8249_AppDev.fm
%CHECK and %CHECKR built-in function

The check built-in function (%CHECK) returns the first position of a base string that contains
a character that does not appear in the comparator string. The reverse check built-in function
(%CHECKR) returns the last position of a base string that contains a character that does not
appear in the comparator string. If all of the characters in the base string also appear in the
comparator string, the function returns 0. The formats of %CHECK and %CHECKR are as
follows:
%CHECK(comparator-string base-string [starting-position])
%CHECKR(comparator-string base-string [starting-position])
Example 9-1 shows the example of retrieving a numeric value from a string by using
%CHECK and %CHECKR. The first CHGVAR uses the %CHECK built-in function to find the
leftmost character that is not a dollar sign ($) or an asterisk (*) or a blank. The second
CHGVAR uses the %CHECKR built-in function to find the rightmost character that is not a
dollar sign, asterisk, or blank. The third CHGVAR computes the number of characters
between the two values and the last CHGVAR uses the substring (%SST) built-in function to
convert part of the base string to a decimal CL variable.
Example 9-1 Retrieving a numeric value from a string by using %CHECK and %CHECKR
DCL VAR(&PRICE) TYPE(*CHAR) VALUE('$******5.27***

DCL VAR(&COMP) TYPE(*CHAR) LEN(3) VALUE('$* )
DCL VAR(&SPOS) TYPE(*UINT) LEN(2)
DCL VAR(&EPOS) TYPE(*UINT) LEN(2)
DCL VAR(&DEC) TYPE(*DEC) LEN(3 2)
DCL VAR(&LEN) TYPE(*UINT) LEN(2)
CHGVAR VAR(&SPOS) VALUE(%CHECK(&COMP &PRICE))
CHGVAR VAR(&EPOS) VALUE(%CHECKR(&COMP &PRICE))
CHGVAR VAR(&LEN) VALUE(&EPOS - &SPOS + 1)
CHGVAR VAR(&DEC) VALUE(%SST(&PRICE &SPOS &LEN))
')
For more information about %CHECK and %CHECKR functions, see the IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6checkbif.htm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6checkrbif.ht
m
%SCAN built-in function

The scan built-in function (%SCAN) returns the first position of a search argument in the
source string, or 0 if it was not found. The format of %SCAN is as follows:
%SCAN(search-argument source-string [starting-position])
Example 9-2 shows the example of searching for a specific string by using %SCAN. Note that
the scan by %SCAN is case-sensitive, so a scan for John does not return a positive result if
&FNAME contains the value JOHN.
Example 9-2 Searching for a specific string by using %SCAN
PGM PARM(&FNAME)
DCL VAR(&FNAME) TYPE(*CHAR) LEN(10)
IF COND(%SCAN('John' &FNAME) *EQ 0) +
THEN(SNDPGMMSG ('NOT FOUND!'))
Chapter 9. Application development
333
8249_AppDev.fm
For more information about %SCAN function, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6scanbif.htm
%TRIM, %TRIML, and %TRIMR built-in function

%TRIM, %TRIML, and %TRIMR built-in functions with one parameter produce a character
string with blanks removed. %TRIM removes any leading and trailing blanks, %TRIML
removes any leading blanks, and %TRIMR removes any trailing blanks from a given string.
The formats of %TRIM, %TRIML, and %TRIMR are as follows:
%TRIM(character-variable-name [characters-to-trim])
%TRIML(character-variable-name [characters-to-trim])
%TRIMR(character-variable-name [characters-to-trim])
Example 9-3 shows the example of trimming blanks by using %TRIM function.
Example 9-3 Trimming blanks by using %TRIM function
DCL VAR(&FIRSTNAME) TYPE(*CHAR) VALUE('

JOHN ')
DCL VAR(&LASTNAME) TYPE(*CHAR) VALUE('
SMITH ')
DCL VAR(&NAME) TYPE(*CHAR) LEN(10)
CHGVAR VAR(&NAME) VALUE(%TRIM(&FIRSTNAME) *BCAT %TRIM(&LASTNAME))
For more information about %TRIM, %TRIML, and %TRIMR functions, see the IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6trimbif.htm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6trimlbif.htm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6trimrbif.htm
%CHAR built-in function

%CHAR converts logical, decimal, integer, or unsigned integer data to character format. The
format of %CHAR is as follows. Note that the convert-argument parameter must be a CL
variable with TYPE of *LGL, *DEC, *INT or *UINT:
%CHAR(convert-argument)
For more information about %CHAR function, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6charbif.htm
%DEC built-in function

%DEC converts character, logical, decimal, integer, or unsigned integer data to packed
decimal format. The format of %DEC is as follows. Note that the convert-argument must be a
CL variable with TYPE of *CHAR, *LGL, *DEC, *INT or *UINT:
%DEC(convert-argument [total-digits decimal-places])
For more information about %DEC, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6decbif.htm
334
8249_AppDev.fm
%INT built-in function

%INT converts character, logical, decimal, or unsigned integer data to integer format. The
format of %INT is as follows. Note that the convert-argument must be a CL variable with
TYPE of *CHAR, *LGL, *DEC or *UINT:
%INT(convert-argument)
For more information about %INT, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6intbif.htm
%UINT built-in function

%UINT converts character, logical, decimal, or integer data to unsigned integer format. The
format of %UNIT is as follows. Note that the convert-argument must be a CL variable with
TYPE of *CHAR, *LGL, *DEC or *INT:
%UINT(convert-argument) or %UNS(convert-argument)
For more information about %UNIT, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6uintbif.htm
%LOWER built-in function

The %LOWER built-in function returns a character string that is the same length as the
argument specified with each uppercase letter replaced by the corresponding lowercase
letter. The format of %LOWER is as follows. Note that the input-string parameter must be a
CL variable with TYPE of *CHAR:
%LOWER(input-string [CCSID])
For more information about %LOWER function, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6lowerbif.htm
%UPPER built-in function

The %UPPER built-in function returns a character string that is the same length as the
argument specified with each lowercase letter replaced by the corresponding uppercase
letter. The format of %UPPER is as follows. Note that the input-string parameter must be a CL
variable with TYPE of *CHAR:
%UPPER(input-string [CCSID])
For more information about %UPPER function, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6upperbif.htm
%LEN built-in function

The %LEN built-in function returns the number of digits or characters of the CL numeric or
character variable. The format of %LEN is as follows. Note that the variable-argument
parameter must be a CL variable with TYPE of *CHAR, *DEC, *INT or *UINT:
%LEN(variable-argument)
For more information about %LEN function, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6lenbif.htm
335
8249_AppDev.fm
%SIZE built-in function

The %SIZE built-in function returns the number of bytes occupied by the CL variable. The
format of %SIZE is as follows. Note that the variable-argument must be a CL variable:
%SIZE(variable-argument)
For more information about %SIZE, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rbam6/rbam6sizebif.htm
9.1.2 ILE RPG

Free-form Control, File, Definition, and Procedure statements

CCSID support for alphanumeric data and external subfields and external subfields
Enhancements related to CCSID conversion
Implicit conversion for concatenation
Control the length returned by %SUBDT
Increased precision for timestamp data
Open Access files
New XML-INTO options
VALIDATE(*NODATETIME) keyword in Control-Specification
Free-form Control, File, Definition, and Procedure statements

In IBM i 7.1 TR7 timed enhancements, ILE RPG had a significant enhancement that
Control-Specification (H-Spec), File-Specification (F-Spec), Definition-Specification (D-Spec),
and Procedure-Specification (P-Spec) syntax are supported in free-form in addition to
Calculation-Specification (C-Spec). IBM i 7.2 also includes this capability in itself. Historically,
a progress of free-form RPG is started in OS/400 V5R1. Free-form in C-Spec by specifying
/FREE and /END-FREE was introduced in ILE RPG of OS/400 V5R1. At i5/OS V5R3,
embedded SQL was supported in free-form C-Spec. This additional free-form enhancement
in IBM i 7.1 TR7 and IBM i 7.2 provides more ease of use and understand of ILE RPG not
only for existing RPG programmers but also for new comers to RPG world from other
programming languages such as Java, PHP, Visual Basic world. Figure 9-1 through
Figure 9-4 show examples the progress of free-form RPG.
336
8249_AppDev.fm
FCUSTFILEIF E
DISK
FREPORT O
E
PRINTER
ICUSTDS
E DSCUSTFILE
/COPY GETCURDAT
/COPY INVOICE
C
READ CUSTFILE
C
*INLR
DOWNE*ON
C
DUEDAT
IFGT CURDAT
C
EXSR SNOVDU
C
WRITEREPORTFM
C/EXEC SQL INSERT :NAME, :DUEDATE INTO
C+
MYLIB/MYFILE
C/END-EXEC
C
ENDIF
C
READ CUSTFILE
C
ENDDO
C*
C
SNOVDU
BEGSR
C
CALL 'SNDINVCE'
C
PARM
CUSTDS
C
PARM ISOVDU
OVERDU 10
C
ENDSR
LR
LR
Figure 9-1 OPM (Original Program Model) RPG from OS/400 V2R3
H bnddir('ACCRCV') dftactgrp(*no)
Fcustfile uf
e
disk
Freport
o
e
printer
D custDs
ds
extname(custfile)
D sendOverdueNotice...
D
pr
/free
read custfile custDs;
dow not %eof;
if dueDate > %date(); // overdue?
sendOverdueNotice ();
write reportFmt;
/end-free
C/exec sql insert :name, :duedate into
C+
mylib/myfile
C/end-exec
/free
endif;
enddo;
*inlr = '1';
/end-free
...
Figure 9-2 /FREE and /END-FREE in C-Spec of ILE RPG in OS/400 V5R1
337
8249_AppDev.fm
H bnddir('ACCRCV') dftactgrp(*no)
Fcustfile uf
e
disk
Freport
o
e
printer
D custDs
e ds
extname(custfile)
D sendOverdueNotice...
D
pr
/free
dow not %eof;
write reportFmt;
exec sql insert :name, :duedate into
mylib/myfile;
endif;
enddo;
*inlr = '1';
/end-free
P sendOverdueNotice...
P
b
/copy invoices
...
Figure 9-3 Support of embedded SQL within /Free and /END-FREE at ILE RPG in i5/OS V5R3
ctl-opt bnddir('ACCRCV');
dcl-f custfile usage(*update);
dcl-ds custDs likerec(custRec);
dcl-f report printer;
dow not %eof;
write reportFmt;
exec sql insert :name, :duedate into
mylib/myfile;
endif;
enddo;
inlr = '1';
dcl-proc sendOverdueNotice;
/copy invoices
sendInvoice (custDs : IS_OVERDUE);
end-proc;
Figure 9-4 Free-form control, file, definition, and procedure statements in ILE RPG of IBM i 7.2
For more information about free-form RPG, see the developerWorks at:
338
8249_AppDev.fm
https://www.ibm.com/developerworks/ibmi/library/i-ibmi-rpg-support/
CCSID support for alphanumeric data and external subfields

In IBM i 7.2, alphanumeric CCSID for the module can be set to many more CCSIDs including
UTF-8 and hexadecimal. Alphanumeric data can be defined with a CCSID. Supported
CCSIDs include:
Single-byte and mixed-byte EBCDIC CCSIDs

Single-byte and mixed-byte ASCII CCSIDs
UTF-8
Hexadecimal
And CCSID(*EXACT) can be used for an externally-described data structure to indicate that
the alphanumeric subfields should have the same CCSID as the fields in the file.
For more information about CCSID definition keyword, see the IBM i 7.2 Knowledge Center
at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/dccsid.htm
Enhancements related to CCSID conversion

The capability related to CCSID conversion is enhanced within IBM i 7.2 ILE RPG compiler.
This includes:
No allowance to implicit or explicit CCSID conversion of hexadecimal data
Open database files without conversion to the job CCSID
Support for CCSID conversions that cause a loss of data
No allowance to implicit or explicit CCSID conversion of hexadecimal data

CCSID conversion is not allowed for implicit or explicit conversion of hexadecimal data that
includes:
Hexadecimal literals
Alphanumeric and graphic data defined with CCSID(*HEX)
Alphanumeric and graphic data in buffers for externally-described files when the DATA
keyword is in effect for the file and the CCSID of the field in the file is 65535
Alphanumeric and graphic data in externally-described data structures defined with
CCSID(*EXACT) when the CCSID of the field in the file is 65535
Open database files without conversion to the job CCSID

Use Control keyword OPENOPT(*NOCVTDATA) or File keyword DATA(*NOCVT) to specify
that a database file will be opened so that alphanumeric and graphic data will not be
converted to and from the job CCSID for input and output operations.
For more information about OPENOPT and DATA keyword, see the IBM i 7.2 Knowledge
Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/hopenop.htm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/fkwdata.htm
Support for CCSID conversions that cause a loss of data

An exception or a diagnostic message related to a CCSID conversion by using C-Spec
keyword CCSIDCVT(*EXCP : *LIST). The meaning of CCSID keyword is:
CCSIDCVT(*EXCP): Get an exception if a CCSID conversion loses data due to the source
character not having a match in the target character set.
339
8249_AppDev.fm
CCSIDCVT(*LIST): Get a listing of every CCSID conversion in the module, with a

diagnostic message indicating whether the conversion has the potential of losing data.
For more information about CCSIDCVT keyword, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/hccsidcvt.htm
Implicit conversion for concatenation

ILE RPG compiler in IBM i 7.2 allows the implicit conversion between alphanumeric, graphic,
and UCS-2 data for concatenation expressions.
For more information about the implicit conversion, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/ccsidconv.htm
Control the length returned by %SUBDT

An optional third parameter for %SUBDT allows to specify the number of digits in the result.
The format of %SUBDT is as follows:
%SUBDT(value : unit { : digits { : decpos } })
Example 9-4 shows the example of %SUBDT.
Example 9-4 Example of %SUBDT built-in function
date = d'1999-02-17';
time = t'01.23.45';
timestamp = z'1999-02-17-01.23.45.98765';
num = %subdt(date:*YEARS:4);
// num = 1999
num = %subdt(time:*MN);
// num = 23
seconds = %subdt(timestamp:*S:5:3);
// seconds = 45.987
For more information about %SUBDT, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/bbsubd.htm
Increased precision for timestamp data

Timestamp data can have between 0 and 12 fractional seconds which is also added in DB2
for i SQL functionality. Example 9-5 shows the example of TIMESTAMP keyword that is used
in a free-form definition to indicate that the item has type timestamp. The number of fractional
seconds can be specified as the optional parameter. If this parameter do not specified, the
number of fractional seconds defaults to 6.
Example 9-5 Example of TIMESTAMP keyword in a free-form definition
DCL-S
DCL-S
DCL-S
DCL-S
DCL-S
340
TS0 TIMESTAMP(0);
TS1 TIMESTAMP(1);
TS6A TIMESTAMP;
TS6B TIMESTAMP(6);
TS12 TIMESTAMP(12);
//
//
//
//
//
YYYY-MM-DD-hh-mm-ss
YYYY-MM-DD-hh-mm-ss.f
YYYY-MM-DD-hh-mm-ss.ffffff
YYYY-MM-DD-hh-mm-ss.ffffff
YYYY-MM-DD-hh-mm-ss.ffffffffffff
8249_AppDev.fm
For more information about increased precision for timestamp data, see the IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/dtimes.htm
Open Access files

An Open Access file was introduced as the heart of Rational Open Access RPG Edition,
which was the separate license program from ILE RPG compiler in IBM i 6.1 and 7.1 at first.
In 2012, this function was delivered as PTFs and combined into ILE RPG compiler and
runtime. In IBM i 7.2, it is also available as a part of ILE RPG compiler and runtime. An Open
Access file is a file which has all its operations handled by a user-written program or
procedure, rather than by the operating system. This program or procedure is called an Open
Access Handler or simply a handler. The HANDLER keyword specifies the handler.
For more information about Open Access files, see the IBM i 7.2 Knowledge Center and
developerWorks at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/openaccessfiles.h
tm
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/We13116a562
db_467e_bcd4_882013aec57a/page/Rational%20Open%20Access.%20RPG%20Edition
New XML-INTO options

The following additional options of XML-INTO operation code are available in IBM i 7.2:
ns option
The ns option controls how XML-INTO handles XML names with a namespace when
XML-INTO is matching XML names to the names in the path option or the subfield names
of a data structure. The following values can be specified as this option:
keep
remove
merge
Example 9-7 shows the example of specifying remove as ns option. In this example,
assumes the file info1.xml contains the content as shown in Example 9-6.
Example 9-6 The content of info1.xml
<abc:info xmlns:abc="http://www.abc.xyz">
<abc:type>Chair</abc:type>
<abc:qty>3</abc:qty>
<abc:price>79.99</abc:price>
</abc:info>
Example 9-7 Example of specifying remove as ns option
D info
D
type
D
qty
D
price
DS
QUALIFIED
25A
VARYING
10I 0
7P 3
xml-into info %xml('info1.xml'

: 'doc=file ns=remove');
// info.type = 'Chair'
// info.qty = 3
341
8249_AppDev.fm
// info.price = 79.99
And also Example 9-9 shows the example of specifying merge as ns option. In this
example, assume the file info2.xml contains the content as shown in Example 9-8
<abc:info xmlns:abc="http://www.abc.xyz"
xmlns:def="http://www.def.xyz">
<def:type>Modern</def:type>
</abc:info>
Example 9-9 Example of specifying merge as ns option
D info
D
abc_type
D
def_type
D
abc_qty
D
abc_price
DS
QUALIFIED
25A
VARYING
25A
VARYING
10I 0
7P 3

: 'doc=file ns=merge path=abc_info');
// info.abc_type = 'Chair'
// info.def_type = 'Modern'
// info.abc_qty = 3
// info.abc_price = 79.99
For more information about ns option, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/nsopt.htm
nsprefix option
The nsprefix option is valid only when ns=remove is specified and allows a RPG program
to determine the values of the namespaces that were removed from the XML names.
Example 9-11 shows the example of specifying ns_ as nsprefix option. In this example,
assume the file info3.xml contains the content as shown in Example 9-10.
<abc:info xmlns:abc="http://www.abc.xyz"
xmlns:def="http://www.def.xyz">
<def:type>Modern</def:type>
</abc:info>
Example 9-11 Example of specifying ns_ as nsprefix option
D info
D
type
D
ns_type
D
qty
D
price
342
DS
QUALIFIED
25A
VARYING DIM(2)
10A
VARYING DIM(2)
10I 0
7P 3
8249_AppDev.fm
ns_price
10A
VARYING

: 'doc=file ns=remove nsprefix=ns_');
// info.type(1) = 'Chair'
// info.ns_type(1) = 'abc'
// info.type(2) = 'Modern'
// info.ns_type(2) = 'def'
// info.qty = 3
// info.price = 79.99
// info.ns_price = 'abc'
For more information about nsprefix option, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/nsprefixopt.ht
m
case=convert option
The case option specifies the way that XML-INTO should interpret the element and
attribute names in the XML document when searching for XML names that match the RPG
field names and the names in the path option. case=convert indicates that the names in
the XML document are converted to valid RPG names before matching to RPG names.
Example 9-13 shows the example of specifying convert as case option. In this example,
assume the file info4.xml contains the content as shown in Example 9-12. Option
case=convert specifies that the names in the XML document will be converted using the
*LANGIDSHR translation table for the job before matching to the RPG names in the path
and in the list of subfields. The names tudiant, ge, and cole will be converted to
ETUDIANT, AGE, AND ECOLE. The XML data itself is not converted, so the subfield
ecole will receive the value Collge Saint-Merri as it appears in the XML document.
<tudiant Nom="lise" ge="12">

<cole>Collge Saint-Merri</cole>
</tudiant>
Example 9-13 Example of specifying convert as case option
D etudiant
D age
D nom
D ecole
ds
D student
ds
qualified
3p 0
25a
varying
50a
varying
likeds(etudiant)
xml-into etudiant %xml('info4.xml'

: 'doc=file case=convert '
+ 'ccsid=ucs2');
// etudiant.nom = 'lise'
// etudiant.age = 12
// etudiant.ecole = 'Collge Saint-Merri'
For more information about case=convert, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/caseopt.htm
343
8249_AppDev.fm
VALIDATE(*NODATETIME) keyword in Control-Specification

Control-specification keyword VALIDATE(*NODATETIME) allows the ILE RPG compiler to
treat date, time, and timestamp data as character data, without performing the checks for
validity.
Note: This may improve the performance of some date, time, and timestamp operations,
but skipping the validation step can lead to serious data corruption problems. You should
only use this feature when you are certain that your date, time, and timestamp data is
always valid.
For more information about VALIDATE(*NODATETIME), see the IBM i 7.2 Knowledge Center
at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/hvalidate.htm
9.1.3 ILE COBOL

This section covers the following enhancements of ILE COBOL in IBM i 7.2 topics:
TIMESTAMP support of 0 to 12 fractional seconds

XML PARSE enhancement
PCML generation improvement
National data enhancements
Increased accuracy of NUMVAL and NUMVAL-C built-in functions
ARITHMETIC parameter for CRTBNDCBL and CRTCBLMOD
New PROCESS statement options
TIMESTAMP support of 0 to 12 fractional seconds

In IBM i 7.2, the precision of TIMESTAMP is increased and can be set 0 to 12. This
enhancement applies to ILE COBOLE as well as ILE RPG and DB2 for i SQL functionality. On
ILE COBOL, the following intrinsic functions will now allow PICOSECONDS as a duration
when specified for a timestamp item:
ADD-DURATION
EXTRACT-DATE-TIME
FIND-DURATION
SUBTRACT-DURATION
The SIZE keyword is allowed with FORMAT TIMESTAMP. The size can be 19 indicating zero
fractional seconds or a value between 21 and 32 indicating between 1 and 12 fractional
seconds.
For more information about PICOSECONDS of each functions and SIZE keyword of
TIMESTAMP, see the IBM i 7.2 Programming IBM Rational Development Studio for i ILE
COBOL Language Reference at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzasb/sc092
539.pdf
XML PARSE enhancement

XML PARSE now has the capability to parse XML files that are greater than 16MB in size,
provided that no individual document piece passed to the processing procedure is greater
than 16MB. The following new XML-CODE values are associated with this change:
XML-CODE 62 indicates that the XML document exceeds 16,000,000 bytes.
344
8249_AppDev.fm
XML-CODE 170 indicates that an XML event exceeds 16,000,000 bytes.

For more information about XML PARSE and XML-CODE, see the IBM i 7.2 Programming
IBM Rational Development Studio for i ILE COBOL Language Reference at:
539.pdf
PCML generation improvement

In IBM i 7.2 ILE COBOL compiler, the following improvements is added to PCML generation
functionality:
New init keyword for improved OCCURS DEPENDING ON array handling
PCML generation provides improved OCCURS DEPENDING ON array handling with the
addition of a new init keyword that will be set to the maximum size of the array.
Automatic data-item naming in generated PCML for filler data items and unnamed items in
a data structure
PCML generation provides automatic data-item naming in generated PCML for filler data
items and unnamed items in a data structure, helping to enable web services to use
generated PCML without first modifying it. The names for these data items will be _filler_1,
_filler_2, and so on.
For more information about PCML generation, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzase/cblpcml.htm
National data enhancements

IBM i 7.2 ILE COBOL compiler supports numeric national data type. A numeric literal can be
specified on the VALUE clause for a numeric national data item. The figurative constant
ZERO/ZEROS/ZEROES represents one or more national zero digits when used with national
data items. And when new PROCESS option NATIONALPICNLIT is specified, National 'N'
literals are supported.
For more information about national data, see the IBM i 7.2 Programming IBM Rational
Development Studio for i ILE COBOL Language Reference at:
539.pdf
Increased accuracy of NUMVAL and NUMVAL-C built-in functions

The accuracy of numeric intrinsic functions NUMVAL and NUMVAL-C increases to 31 digits
with compiler option ARITHMETIC(*EXTEND31) or PROCESS option EXTEND31.
ARITHMETIC parameter for CRTBNDCBL and CRTCBLMOD

New *EXTEND31FULL option value is available as a value of ARITHMETIC parameter for
CRTBNDCBL and CRTCBLMOD command. This new value provides the following features:
The accuracy of the following numeric intrinsic functions increases from floating-point
accuracy of up to 15 digits to decimal floating-point accuracy of up to 34 digits:
ANNUITY
MEAN
MEDIAN
MIDRANGE
NUMVAL
345
8249_AppDev.fm
NUMVAL-C
PRESENT-VALUE
VARIANCE
The intermediate result of a fixed-point arithmetic expression can be up to 34 digits and
numeric literals may have a maximum length of 34 digits.
For more information about ARITHMETIC parameter for CRTBNDCBL and CRTCBLMOD
command, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/crtbndcbl.htm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/crtcblmod.htm
New PROCESS statement options

In ILE COBOL in IBM i 7.2, the following options are added to PROCESS statement:
NOCHGFLTRND and ALWCHGFLTRND
Specifies whether or not COBOL will use the floating point rounding mode computational
attribute specified by MI instruction SETCA. SETCA allows you to set the rounding mode
of the result of a floating-point calculation to either round or truncate.
NATIONALPICNLIT
Enables N" and N' as the opening delimiter for a national literal and enables elementary
data items defined using the picture symbol N to have an implied USAGE NATIONAL
clause.
EXTEND31FULL
This option corresponds to the enhancement of CRTBNDCBL and CRTCBLMOD commands.
This option provides to increase the floating-point accuracy of up to 34 digits as well as
*EXTEND31FULL option of ARITHMETIC parameter for CRTBNDCBL and CRTCBLMOD
commands.
For more information about PROCESS statement, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzase/proc.htm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzase/optonly.htm
9.1.4 ILE C/C++

This section covers the following enhancements of ILE C/C++ in IBM i 7.2 topics:
New predefined macros
New option of LANGLVL parameter for CL commands
Implement initial C++0x features
New predefined macros

The following predefined macros are available at ILE C/C++ in IBM i 7.2:
ILE C macros
346
__C99_BOOL indicates support for the _Bool data type.

__C99_DESIGNATED_INITIALIZER indicates support for designated initialization.
__C99_DUP_TYPE_QUALIFIER indicates support for duplicated type qualifiers.
__C99_EMPTY_MACRO_ARGUMENTS indicates support for empty macro arguments.
__C99_FLEXIBLE_ARRAY_MEMBER indicates support for flexible array members.
__C99_INLINE indicates support for the inline function specifier.
8249_AppDev.fm
__C99_LLONG indicates support for C99-style long long data types and literals.
__C99_MAX_LINE_NUMBER indicates that the maximum line number is 2147483647.
__C99_MIXED_DECL_AND_CODE indicates support for mixed declaration and code.
__C99_NON_CONST_AGGR_INITIALIZER indicates support for non-constant aggregate
initializers.
__C99_NON_LVALUE_ARRAY_SUB indicates support for non-constant aggregate
initializers.
__C99_NON_LVALUE_ARRAY_SUB indicates support for non-lvalue subscripts for
arrays.
__C99_STATIC_ARRAY_SIZE indicates support for the static keyword in array
parameters to functions.
__C99_VAR_LEN_ARRAY indicates support for variable length arrays.
All of these macros are defined when the LANGLVL(*EXTENDED) compiler is in effect.
ILE C++ macros

__C99_MAX_LINE_NUMBER indicates that the maximum line number is 2147483647.
__C99_MIXED_STRING_CONCAT indicates support for concatenation of wide string and
non-wide string literals.
__IBMCPP_AUTO_TYPEDEDUCTION indicates support for the auto type deduction
feature.
__IBMCPP_C99_PREPROCESSOR indicates support for the C99 preprocessor features
adopted in the C++0x standard.
__IBMCPP_DECLTYPE indicates support for the decltype feature.
__IBMCPP_DELEGATING_CTORS indicates support for the delegating constructors
feature.
__IBMCPP_EXTENDED_FRIEND indicates support for the extended friend declarations
feature.
__IBMCPP_EXTERN_TEMPLATE indicates support for the explicit instantiation
declarations feature.
__IBMCPP_INLINE_NAMESPACE indicates support for the inline namespace definitions
feature.
__IBMCPP_STATIC_ASSERT indicates support for the static assertions feature.
All of these macros are defined when the LANGLVL(*EXTENDED0X) compiler is in effect.
New option of LANGLVL parameter for CL commands

In IBM i 7.2, new *EXTENDED0X option of LANGLVL parameter for CL commands are
supported corresponded to the implement initial C++0x features in this release. C++0x is now
called as C++11. *EXTENDED0X defines the same preprocessor variables as *EXTENDED
does, and also defines an individual preprocessor variable for each C++11 language feature
supported in this release. This option causes the compiler to use all the capabilities of ILE
C++ and currently supported C++11 features that are implemented in this version of ILE C++
compiler.
For more information about LANGLVL parameter for CL commands, see the IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzarf/compile_langlvl.h
tm
Implement initial C++0x features

ILE C++ in IBM i 7.2 supports initial C++0x features including the following features. C++0x is
a new version of the C++ programming language standard. C++0x has been ratified and
347
8249_AppDev.fm
published as ISO/IEC 14882:2011 and now is called as C++11. All references to C++0x in
this document are equivalent to the ISO/IEC 14882:2011 standard.
Note: IBM continues to develop and implement the features of the new standard. The
implementation of the language level is based on IBM's interpretation of the standard. Until
IBM's implementation of all the features of the C++0x standard is complete, including the
support of a new C++ standard library, the implementation may change from release to
release. IBM makes no attempt to maintain compatibility, in source, binary, or listings and
other compiler interfaces, with earlier releases of IBM's implementation of the new features
of the C++0x standard and therefore they should not be relied on as a stable programming
interface.
9.1.5 System APIs

For a list with detailed information about new APIs in IBM i 7.2, see the IBM i 7.2 Knowledge
Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apifinder/apifinder50.h
tm
And also for a list with detailed information about changed APIs in IBM i 7.2, see the IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apifinder/apifinder60.h
tm
9.2 Java on i
The section covers the following topics:
IBM Developer Kit for Java
IBM Toolbox for Java
9.2.1 IBM Developer Kit for Java

This section describes the following topics:
IBM Developer Kit for Java Packaging
Support for multiple Java Development Kits (JDKs)
Security Updates for Java on i
IBM Developer Kit for Java Packaging

In IBM i 6.1 and IBM i 7.1, IBM Developer Kit for Java was available as the licensed program
5761JV1. In IBM i 7.2, new product ID 5770JV1 is for IBM Developer Kit for Java. This
product covers the same options as 5761JV1, but the following options are not available on
IBM i 7.2 5770JV1:
Option 8: JDK50, 32bit
All of available Java for IBM i 7.2 are called as IBM Technology for Java, which is based on the
AIX version of the IBM Center for Java Technology Developer Kit. IBM Developer Kit for Java
348
8249_AppDev.fm
Option 6, Option 7, and Option 10, which are referred as Classic Java, were already dropped
at IBM i 7.1 and also are not available on IBM i 7.2 either. If you are still using Classic Java on
prior to IBM i 7.1, you should refer the following considerations and migrate your application to
use IBM Technology for Java:
When migrating from the Classic Java Virtual Machine (JVM), which was the 64-bit virtual
machine, to the 32-bit version of IBM Technology for Java, consider that there may be
limitations when using the 32-bit environment. For example, the amount of addressable
memory is much smaller. In 32-bit mode, the Java object heap cannot grow much larger
than 3 gigabytes. You will also be limited to running approximately 1000 threads. If your
application requires more than 1000 threads or a Java object heap larger than 3 gigabytes
use the 64-bit version of IBM Technology for Java. Table 9-1 shows the level of Classic
Java and the IBM Technology for Java replacement.
Adopted authority for Java programs is not supported by IBM Technology for Java Virtual
Machine.
IBM Technology for Java Virtual Machine works on
(Portable Applications Solutions Environment). When IBM Technology for Java Virtual
Machine or PASE for i native methods encounter problems, they will dump diagnostic files
into the IFS and you can not see messages in the job log. There are several types of these
core files, including core.*.dmp, javacore.*.txt, Snap*.trc, and heapdump.*.phd. The files
range in size from tens of KB up to hundreds of MB. In most cases, more severe problems
produce larger files. The larger files can quickly and quietly consume large amounts of IFS
space.
Note: Despite the space these files consume, they are useful for debugging purposes.
When possible, you should preserve these files until the underlying problem has been
resolved.
If your ILE programs use Java Native Interface (JNI) functions, you must compile these
programs with teraspace storage enabled.
Table 9-1 Classic Java levels and the suggested IBM Technology for Java replacement
Current Classic Java version
Possible options of IBM Technology for Java

replacements
Java Developer Kit 1.4 (5761JV1 Option 6)
Java SE 71 32-bit (5770JV1 Option 14)

Java SE 6 2.6 32-bit (5770JV1 Option 11)
Java Developer Kit 5.0 (5761JV1 Option 7)

349
8249_AppDev.fm
Current Classic Java version
Possible options of IBM Technology for Java

replacements
Java Developer Kit 6 (5761JV1 Option 10)

Note: IBM recommends Java SE 71 when migrating from Java Developer Kit 1.4 or 5.0.
Support for multiple Java Development Kits (JDKs)

IBM i 7.2 supports multiple versions of the Java Development Kits (JDKs) and the Java 2
Platform, Standard Edition. To install the IBM Technology for Java options on IBM i 7.2, follow
the steps in IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaha/rzahainstalljdk.h
tm
Table 9-2 shows the list of supported options of 5770JV1 IBM Technology for Java product
and their JAVA_HOME in IBM i 7.2.
Table 9-2 Supported options of 5770JV1 IBM Technology for Java in IBM i 7.2
5770JV1 Options
JAVA_HOME
Option 11 IBM Technology for Java 6 32-bit
/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit
Option 11 IBM Technology for Java 6 2.6 32-bit
Option 12 IBM Technology for Java 6 2.6 64-bit
IBM i also supports using multiple JDKs simultaneously through multiple JVMs. A single JVM
runs one specified JDK. The default JDK chosen in this multiple JDK environment depends
on which 5770-JV1 Options are installed. The following order of precedence determines the
default JDK:
1.
2.
3.
4.
5.
6.
Option 14 - IBM Technology for Java 7.1 32-bit

Option 11 - IBM Technology for Java 6 32-bit
Option 12 - IBM Technology for Java 6 64-bit
You can access IBM Technology for Java JDKs by setting JAVA_HOME environment variable
or by specifying a fully qualified path to the Java tool or utilities located in the JDK you want to
350
8249_AppDev.fm
use. Example 9-14 shows the example of using IBM Technology for Java 71 64-bit by setting
JAVA_HOME. Figure 9-5 shows the result of performing java -version from PASE under the
setting of Example 9-14.
Example 9-14 Example of setting IBM Technology for Java 71 64-bit to JAVA_HOME
ADDENVVAR ENVVAR(JAVA_HOME) VALUE('/QOpenSys/QIBM/ProdData/JavaVM/jdk71/64bit')
/QOpenSys/usr/bin/-sh
$
> java -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build pap6470_27sr1fp1-20140708_01(SR1 FP1))
IBM J9 VM (build 2.7, JRE 1.7.0 OS/400 ppc64-64 Compressed References jvmap64
70_27sr1fp1-20140708_01_cr (JIT enabled, AOT enabled)
J9VM - R27_Java727_SR1_20140707_1408_B205525
JIT - tr.r13.java_20140410_61421.07
GC
- R27_Java727_SR1_20140707_1408_B205525_CMPRSS
J9CL - 20140707_205525)
JCL - 20140707_01 based on Oracle 7u65-b16
$
Figure 9-5 Result of java -version under specifying IBM Technology for Java 7.1 64-bit
For more information about IBM Developer Kit for Java, see the IBM i 7.2 Knowledge Center
at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaha/whatitis.htm
Security Updates for Java on i

The following developerWorks page provides the latest security update information about
Java on i security including Java SR Delivery Schedule for IBM i and Common Vulnerabilities
and Exposures (CVE) information:
echnology%20Updates/page/Java%20on%20IBM%20i%20security%20updates
9.2.2 IBM Toolbox for Java

To access resources including data in IBM i from your Java applications, you can leverage
IBM Toolbox for Java. IBM Toolbox for Java provides a set of Java classes, which can be used
in Java client/server applications, applets, and servlets that work with data on your IBM i
system. Some typical functions of IBM Toolbox for Java are IBM Toolbox for Java JDBC
Driver, Program Call and PCML (Program Call Markup Language) functionality, and so on. An
open source version of IBM Toolbox for Java, which is referred as JTOpen, is also available.
And JTOpenLite (JTLite) is also available for accessing IBM i resources to mobile
applications.
This section covers the following enhancements of IBM Toolbox for Java in IBM i 7.2:
New AS400JDBCTimestamp class
JTOpenLite Java classes library
351
8249_AppDev.fm
New AS400JDBCTimestamp class

In IBM i 7.2, the maximum precision of a timestamp increases from 6 to 12. Correspond to
DB2 for i SQL functionality, ILE programming languages, the IBM Toolbox for Java JDBC
driver also has been enhanced to retrieve these larger timestamp value. Since the
java.sql.Timestamp class only supports 9 digits of precision, a new AS400JDBCTimestamp
class has been created to handle those cases where the data from the server includes more
then 9 digits of precision.
For more information about AS400JDBCTimestamp class, see the IBM i 7.2 Knowledge
Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahh/javadoc/com/ibm/a
s400/access/AS400JDBCTimestamp.html
New QueryTimeoutMechanism JDBC connection property

The IBM Toolbox for Java JDBC driver originally implemented the queryTimeout feature using
the QQRYTIMLMT feature of the database engine. However, this mechanism does not
correctly allow for the ending of long running operations.
The QueryTimeoutMechanism connection property allows the queryTimeout to be
implemented using a database CANCEL. The possible values are qqrytimlmt and cancel. If
qqrytimlmt is specified, the QQRYTIMLMT feature of the database engine will be used to limit
how long queries can run. If cancel is specified, the running SQL statement will be cancelled
after the specified timeout expires.
For more information about QueryTimeoutMechanism connection property, see the IBM i 7.2
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahh/jdbcproperties.ht
m
JTOpenLite Java classes library

The JTOpenLite package (com.ibm.jtopenlite) is an alternative to the IBM Toolbox for Java
and JTOpen with providing a small foot print (about 420KB). JTOpenLite enables you to write
Java programs that allow a variety of mobile devices to directly access IBM i data and
resources. Although JTOpenLite is considered a part of IBM Toolbox for Java, it is not
included in the licensed product. The JTOpenLite jar file (jtopenlite.jar) is included in the open
source version of IBM Toolbox for Java, called JTOpen. You must separately download and
set up JTOpenLite, which is contained in JTOpen.
For more information about JTOpenLite, see Modernizing IBM i Applications from the
Database up to the User Interface and Everything in Between, SG24-8185, available at:
9.3 Rational Tools for i

This section covers the following Rational and related Tools for i:
352
IBM Rational Developer for i (RDi) V9.1.1

IBM Rational Application Developer for WebSphere Software (RAD)
IBM Rational Business Developer (RBD)
IBM Rational Team Concert (RTC) for i
IBM Rational Host Access Transformation Services (HATS)
8249_AppDev.fm
IBM Rational Application Management Toolset (AMT)

ARCAD Pack for Rational
9.3.1 IBM Rational Developer for i (RDi) V9.1.1

IBM Rational Developer for i (RDi) is an Integrated Development Environment (IDE) built on
Eclipse and is the strategic desktop development tool for creating IBM i applications. RDi is
installed on a workstation and supports for developing IBM i applications in both
host-connected and disconnected modes. RDi supports development of RPG, COBOL, C,
C++, SQL, and CL applications, including the DDS (for instance display and printer files).
Both of OPM and ILE are in a scope of RDi.
RDi V9.1 is delivered in 2014 correspond to the announcement of IBM i 7.2, and in IBM i 7.2
TR1 timed, RDi V9.1.1 becomes available. Both of RDi V9.1 and V9.1.1 are build on Eclipse
4.2.2.
Rational Developer for i Packaging
What is new in the latest version of RDi
Rational Developer for i Packaging

RDi V9.1 is available in three editions:
RPG and COBOL Tools
This edition is for developing basic compiled language applications that run on the IBM i
including C, C++, CL, DDS, and SQL development. The IDE can be connected to IBM i
6.1, 7.1, and 7.2.
RPG and COBOL + Modernization Tools, Java Edition
This edition contains all functionalities of RPG and COBOL Tools and a substantial subset
of the IBM Rational Application Developer (RAD) for WebSphere Software. This edition
provides a rich Java, Web, SOA, and mobile development environment to support
extension and modernization of heritage IBM i applications. And this edition also includes
IBM Worklight Developer Edition to support development of hybrid mobile applications
that exploit the capabilities of the Worklight runtimes and connect to systems of record
implemented in RPG, COBOL, C/C++, SQL, or Java/JEE running on AIX or Linux on
Power Systems servers.
For more information about RAD, see the 9.3.2, IBM Rational Application Developer for
WebSphere Software (RAD).
And for more information about IBM Worklight Developer Edition, see the developerWorks
at:
http://www.ibm.com/developerworks/mobile/worklight/
RPG and COBOL + Modernization Tools, EGL Edition
This edition contains the complete Rational Business Developer (RBD) product to support
extension and modernization of heritage IBM i applications using the EGL language in
addition to the RPG and COBOL Tools.
For more information about RBD, see the 9.3.3, IBM Rational Business Developer
(RBD).
What is new in the latest version of RDi

RDi V9.1 has the following enhancements:
353
8249_AppDev.fm
Line level Batch Code Coverage analysis capability

Support of Free-form RPG
Filter functionality in RPG outline view
And RDi V9.1.1 also has the following enhancement:
Interactive Code Coverage support
Push-to-client function
Line level Batch Code Coverage analysis capability

Batch code coverage can be launched on any program or service program that can be
debugged. This can be used to determine the effectiveness of automated or manual tests. It
can help focus additional testing on code paths that have not been executed. It can aid the
reduction of the amount of testing required by eliminating tests that are duplicate in terms of
which code paths they exercise. Figure 9-6 shows the launching Batch Code Coverage
capability by right clicking a program object in RDi. With this capability, the developer can then
see by views, html reports, and editor annotations exactly which lines of the programs have
been execute or not executed by that particular scenario.
Figure 9-6 Launching Batch Code Coverage
Figure 9-7 shows an example of Code Coverage Report as an editor. The developer can drill
down from this report in the editor to determine which lines were covered. The editor will open
the related source member with green and red annotations showing which lines were covered
as shown in Figure 9-8.
Figure 9-7 Code Coverage Report
354
8249_AppDev.fm
Figure 9-8 Source member with annotations which lines were covered
Code Coverage Report also can be shown via HTML and PDF reports. Figure 9-9 is an
example of a html report. Those reports are available for those who are not using RDi such as
quality assurance, management.
Figure 9-9 Example of Code Coverage HTML report
For more information about Code Coverage capability, see the developerWorks at:
http://www.ibm.com/developerworks/library/d-code-coverage-tools-rational-developer
-i/index.html
Support of Free-form RPG

RDi V9.1 fully supports and exploits the free-form RPG with prompting, syntax checking,
program verifiers, source styling logic, live outline views, content assist, hover hints, and
more. Wizards such as the D-Specification Wizard as shown in Figure 9-10, Procedure
355
8249_AppDev.fm
Wizard as shown in Figure 9-10 and Java Method Call Wizard can generate free-form
definitions into the correct location of mixed free-form and fixed-form RPG source.
Figure 9-10 D-Specification Wizard
Figure 9-11 Procedure Wizard
356
8249_AppDev.fm
Figure 9-12 Java Method Call Wizard
For more information about free-form RPG support, see the developerWorks at:
https://www.ibm.com/developerworks/ibmi/library/i-ibmi-rpg-support/
And also see the Rational Developer for i V9.0 Knowledge Center at:
https://www-01.ibm.com/support/knowledgecenter/SSAE4W_9.1.0/com.ibm.etools.iseries
.rse.doc/topics/teditrpg.html
Filter functionality in RPG outline view

The outline can be quickly subset to the language elements of interest by specifying a filter.
The ability to quickly filter to the variable or procedure of interest and see all references can
be a boon to their productivity. This functionality provides an optional filter field at the top of
the Outline view as shown in Figure 9-13 and subsets the view as the developer types.
Figure 9-13 describes only the definitions containing EMP are shown in the Outline view
since the developer types EMP in the filter field.
357
8249_AppDev.fm
Figure 9-13 Filter field of the Outline view
Interactive Code Coverage support

In RDi V9.1.1, the interactive code coverage analysis capability is supported in addition to the
existing batch code coverage analysis which is mentioned in Line level Batch Code Coverage
analysis capability. With this enhancement, code coverage capability can be adopted not only
batch processes, but also interactive processes such as interactive job, web services.
For more information about Interactive Code Coverage support, see the developerWorks at
echnology%20Updates/page/IBM%20i%207.2%20-%20TR1%20Enhancements
Push-to-client function
RDi V9.1.1 supports Push-to-client function that update all RDi client workspaces from a
central IBM i. This capability provides the ability to distribute and maintain RDi across a team
of developers. Figure 9-14 shows the concept of Push-to-client function. By leveraging this
function, you can store workspace configurations in a central location and push them to client
workstations so that your developers have a consistent workspace environment.
Push-to-client can be used to administer consistent work environments or to simply share or
backup configurations.
358
8249_AppDev.fm
Figure 9-14 Concept of Push-to-client function
The following information an files can be distributed from a central IBM i.

Remote System Explorer (RSE) Connections
Filters
Eclipse Preferences
Update templates
Free-form RPG
Free-form SQL
COBOL
C/C++
Database Connections
RSE Compile Actions
RSE User Actions
For more information about Push-to-client function, see the developerWorks at:
echnology%20Updates/page/IBM%20i%207.2%20-%20TR1%20Enhancements
9.3.2 IBM Rational Application Developer for WebSphere Software (RAD)

Rational Application Developer for WebSphere Sofware (RAD) is an eclipse based IDE
primarily designed to byild Java, Java EE, Web 2.0, mobile, OSGi, portal and service-oriented
359
8249_AppDev.fm
architecture (SOA) applications. The purpose of this tool is the development of J2EE software
for multiple platforms running IBM WebSphere Application Server software. IBM i is one of
supported platforms.
There are several adavntages this software brings.
Accelerates development and maintenance of web and mobile applications with
tools for established, as well as new and emerging programming models and
technologies.
Speeds the development of services and Java applications with productivity tools
supporting the latest Java EE and SOA programming models.
Is optimized for IBM middleware, including the new, lightweight Liberty Profile, the
full WebSphere Application Server profile, the IBM WebSphere Portal Server and IBM
Workload Deployer.
Includes advanced test and analysis tools to help you achieve higher initial code quality
while accelerating application development, deployment and management.
Provides flexible deployment options and rich integrations with Rational
Collaborative Application Lifecycle Management solution to help raise productivity
and improve quality outcomes at both team and individual practitioner
Current version 9.1 offers the follwing news:
After introducing new integrations with Maven and JQuery at v9.0, RAD 9.1 continues to
broaden its integrations with key open source technologies, this time
including packaging and integration of EGit (note that this introduces support for
scenarios involving the use of RAD for development targeted to BlueMix and using
DevOps Services for BlueMix)
packaging and integration of Apache Cordova to support rapid development of hybrid
mobile apps and rapid conversion of existing web apps into hybrid mobile apps
Continuing its tradition of providing optimized tooling support for the latest WebSphere
Application Server (WAS), Liberty Profile, and WebSphere Portal runtimes. RAD 9.1
Introduces serveral new tools for Portal development
Will support newer versions of Portal server expected to be introduced later in 2014
Will deliver, in the form of a 2Q14 Fix Pack, the latest updates for the Liberty Profile
and related tool updates as WebSphere shifts to a new continuous delivery model that
introduces new GA-level WAS and Liberty updates on a quarterly basis via the "Liberty
GA Repository"
RAD 9.1 also introduces these consumability improvements:
30% faster startup time
Simplication of the product download (the downloadable image, aka the Bill of
Materials, is now comprised of a smaller and better-organized number of parts with
better part descriptions) and an improved install Launchpad
The license activation kits for Authorized User licenses are now included as part of the
Bill of Materials (so you can bypass the Rational License Key Center if desired, if you
only use Authorized User licenses)
Support for Windows 8.1
9.3.3 IBM Rational Business Developer (RBD)

Rational Business Developer (or Rational Developer for i - EGL tools) contain the following
features (examples):
Complete IDE for EGL development (IBM Rational Business Developer 9.0 functionality)
Limited Java and Web development
360
8249_AppDev.fm
IBM Rational Business Developer is an Eclipse-based integrated development environment

(IDE) that simplifies the development of service-oriented architecture (SOA) applications
using the Enterprise Generation Language (EGL).
Developers can now deliver web, Web 2.0, and mobile applications and services without
having to master Java and SOA programming. This allows them to create, test, and debug
EGL applications while generating Java, JavaScript, or COBOL code for deployment. RPG
and COBOL developers can transition to EGL easily, as it allows them to create portable
applications with modern architectures and user interfaces, without having to learn concepts
of object-oriented languages.
Following are the main features of IBM Rational Business Developer (and also EGL tools):
EGL transformation
Transforms EGL source into Java, JavaScript, or COBOL code that is optimized for
deployment to application hosting environments including Java EE servers and
traditional transactional systems.
Streamlines development by using a single, high-level language for complete
development of the business application.
Generates different languages for a single application, such as JavaScript for an
application user interface and Java or COBOL for the application back end.
Increases productivity and reduces the technology learning curve to improve business
agility and competitiveness.
Simplified service creation
Simplifies service creation, concealing the technical complexity of SOA. Multiplatform
deployment deploys applications and services on many platforms either as web
services or natively.
Provides built-in service constructs and a facility for service generation, allowing
business-oriented developers to create SOA applications without extensive training.
Creates EGL services and automates generation of web services from EGL services.
Supports development and deployment of services to IBM WebSphere Application
Server on multiple platforms.
Allows developers to work within the familiar Eclipse-based environment, leveraging
existing development skills.
UML support
Supports Unified Modeling Language (UML) to EGL transformations, allowing complex
applications to be modeled graphically.
UML supports a model-driven approach that streamlines the creation of Java and Web
2.0 applications and services.
UML supports the implementation of EGL services.
UML supports full Create, Read, Update, Delete (CRUD) applications without the need
for manual coding.
Extensible platform
Integrates with several IBM products to extend support for IBM i and expand software
lifecycle functionality.
Extends existing IT assets and provides the extensibility, scalability and productivity
features of an Eclipse-based platform.
361
8249_AppDev.fm
Integrates with IBM Rational Developer for i for SOA Construction and IBM Rational
Software Architect.
For more information about EGL, see the following websites:
EGL Cafe:
https://www.ibm.com/developerworks/community/groups/service/html/communityview?
communityUuid=3e2b35ae-d3b1-4008-adee-2b31d4be5c92
IBM Rational Business Developer Version 9.0 Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/SSMQ79_9.0.0/com.ibm.rational.rbd
.product.doc/helpindex_rbd.html?cp=SSMQ79_9.0.0%2F0&lang=en
New Features in IBM Rational Business Developer V9.1

New features are:
New Annotations
Description=#doc{}
isDeprecated
StartTransactionID/RestartTransactionID
New Dojo Widget and Dojo Mobile Widget enhancements
Addition of DojoMobileTimePicker widget
allowEmptyRows property on Datagrid to show/hide empty rows
Support for EGL web applications in the CICS V5.1 Liberty Profile
ncludes RUI/Web 2.0 based, JSF based, JavaWrappers, and VAGen style Web
transactions
Extension Points/APIs enabling development of custom code to

Support Fixed/Structured Records in RUI handlers
Extend the EGL RUI Visual Editor
Shell Share capability with other Rational V9.1 IDE products
9.3.4 IBM Rational Team Concert (RTC) for i

IBM Rational Team Concert (RTC), which is part of Rational Collaboration Lifecycle
Management (CLM) and Rational Systems and Software Engineering, is a team collaboration
tool that is built on the Jazz technology platform. RTC uses the Change and Configuration
Management (CCM) application to provide features that integrate development project tasks
including iteration planning, process definition, change management, defect tracking, source
control, build automation, and reporting. RTC provides the following capabilities:
An integrated set of collaborative software delivery tools for IBM i development including
source control, change management, build, process management and governance
Integration with IBM Rational Developer for i to enable team capabilities for native IBM
applications
Specialized support for source control, change management and builds of traditional
language artifacts such as RPG and COBOL
Support for multi tier software development and application modernization efforts using
RPG, COBOL, PHP, Java, and others
Supports IBM i native library file system and integrated file system (IFS)
IBM i artifact builds including RPG, COBOL, CL, and Java
Build agent which runs natively on the IBM i operating system (runs IBM i commands and
call programs)
Native hosting of the IBM Jazz Team Server on IBM i
362
8249_AppDev.fm
RTC consists of client and server components. To leverage RTC functionality for developing
IBM i applications, RTC client requires to be installed on a workstation with Rational
Developer for i. RTC server components are supported on several platforms including IBM i,
AIX, z/OS, Solaris, Red Hat (RHEL) and SUSE (SLES) Linux distributions, and Windows
Server.
Supported operating systems versions and limitations are described in Jazz Community Site
by RTC version. For instance, system requirements of RTC V5.0.1 is described in the
following website:
https://jazz.net/wiki/bin/view/Deployment/CLMSystemRequirements50
Note: RTC V5.0.1 is the latest released version and IBM i 7.2 is not supported as RTC
Server as of October 2014 as shown in above website. RTC client of this version supports
Eclipse 4.2.2. Both of RDi V9.1 and V9.1.1 is built on Eclipse 4.2.2 so that RTC V5.0.1
client can be leveraged to developing IBM i applications.
What is new in the latest version of RTC

New introduced functionalities in each RTC version and release are listed in the Jazz
Community Site. For instance, the website for RTC V5.0.1, which is the latest version of RTC
as of October 2014 is as follows:
https://jazz.net/downloads/rational-team-concert/releases/5.0.1?p=news
For more information about RTC, see the following websites:
https://jazz.net/products/rational-team-concert/
And see the RTC V5.0.1 Knowledge Center at:
https://www-01.ibm.com/support/knowledgecenter/SSCP65_5.0.1/com.ibm.rational.clm.d
oc/helpindex_clm.html
And also see the redbook, Modernizing IBM i Applications from the Database up to the User
Interface and Everything in Between, SG24-8185 available at:
9.3.5 IBM Rational Host Access Transformation Services (HATS)

IBM Rational Host Access Transformation Services (HATS) is a tool which allows you to
transform applications using text based 5250 user interface into web pages. Therefore quickly
creating a web application from an existing 5250 application without single touch to the
source code. It is able also to connect to IBM Mainframe 3270 screens at the same time, and
general UNIX VTY screens, run macros there, gather the data, and present data from multiple
system them in one single webpage.
HATS general description

The HATS tool is based on the Eclipse environment like other Rational development tools.
The latest version v9.0 uses Eclipse 4.2.2.
As a prerequisite for development activity it needs one of the following Rational products:
Rational Developer for i V9.0
Rational Business Developer V9.0
363
8249_AppDev.fm
Rational Application Developer for WebSphere Software V9.0

Rational Software Architect for WebSphere Software V9.0
Rational Developer for AIX and Linux V9.0
Supported runtime Java application servers:
IBM i - Release Overview V7.1 and future modification levels and their fix packs
Apache Geronimo 2.2.1 and future modification levels and fix packs
Apache Geronimo 2.1.7 and future modification levels and fix packs
WebSphere Application Server - different versions of Express/Base/Network Deployment
editions from version 7.0 to the latest 8.5.5.
Oracle WebLogic server 12c (12.1.1) and future modification levels and their fix packs
Note: Any of the WebSphere, WebLogic, and Apache Geronimo technologies can run on a
different platform from where they are supported (IBM i is not mandatory). These servers
then connect using telnet, or secure telnet protocol to the IBM i server where the original
5250 application runs.
HATS V9.0 can create two types of clients, the first is web based running in a web browser,
and the second is a client/server based client running either in Lotus Notes, Lotus Expeditor
environment, or in Eclipse SDK environment.
Supported web browsers include the following:
Mozilla Firefox
Android
Google Chrome
Apple Safari
Apple Safari on iOS
Microsoft Internet Explorer
Microsoft Internet Explorer mobile browser
Konqueror
Opera
Rational HATS can also create portlets when used with IBM Rational Application Developer
for WebSphere Software. It supports different IBM WebSphere Portal Server Editions from
version 7.0 to version 8.0.
For detailed system requirements and possible limitations see the following website:
http://www-01.ibm.com/support/docview.wss?uid=swg27011794
HATS basic functionality

IBM Rational Host Access Transformation Services (HATS) transforms traditional text-based
interfaces, such as 3270 and 5250 green-screen applications, into web, portlet, rich client or
mobile device user interfaces. It also extends 3270, 5250 and virtual terminal (VT)
applications as standard web services. With Rational HATS, you can easily convert traditional
text-based host application screens to user-friendly GUIs.
Rational HATS is available in the following packages:
Rational HATS for Multiplatforms and HATS for Linux on zSeries
Rational HATS for 5250 Applications on Multiplatforms
364
8249_AppDev.fm
Rational HATS for 5250 Applications on i5/OS

Note: Rational HATS for Multiplatforms can create applications using IBM i 5250, IBM
Mainframe 3270, and UNIX VT based screens (VT is only for capturing data, not screens).
While Rational HATS for 5250 can use only IBM i 5250 screens.
Rational HATS for Multiplatforms and Rational HATS for 5250 Applications on
Multiplatforms can use any supported HTTP server on any supported Java application
server (see Supported runtime Java application servers: on page 364). Rational HATS for
5250 Applications on i5/OS can only have Java application server runtime on IBM i.
The Rational HATS product provides both a HATS Toolkit (Windows Eclipse based plug-in for
development of HATS applications) and a HATS runtime. The HATS toolkit can be
downloaded for free from the Rational HATS product web page.
Rational HATS allows you to reuse your existing assets in the following innovative ways:
Terminal applications
Transforms the user interface of your 3270 and 5250 green-screen applications.
Allows tunable default rendering of all non-customized screens of the application.
Transforms specific screens using screen customizations and transformations.
Transforms terminal application components, such as function keys and menu items,
into intuitive links, buttons or text with images.
Web services
Extends 3270, 5250 and VT application core business logic as web services or
JavaBeans
Captures screen flows, inputs and outputs with a wizard-based macro recorder. Lets
you edit what is captured with the Visual Macro Editor, and creates integration objects
and web services from the screen flows.
Reuses terminal application business logic in new business processes and
applications.
Customization
Provides customizable workflow and application navigation.
Rational HATS simplifies screen navigation with macros and screen combinations.
Uses global variables to store data, pre-fill drop-down menus or pop-up windows, and
input information for the user.
Can transform a text-based user interface with a rich set of GUI widgets, such as
drop-down menus, calendars, tables, pop-up windows and radio buttons.
Using business logic, Rational HATS augments terminal applications by aggregating
terminal application data with other data sources.
HATS Toolkit
Provides wizard-based, visual development including visual page design and macro
editing.
Works with a supported Rational IDE environment, such as IBM Rational Application
Developer for WebSphere Software, or Rational Business Developer, or Rational
Developer for i V9.0 + Modernization Tools, EGL Edition.
Provides access to standard Eclipse features such as Java development tools.
365
8249_AppDev.fm
Features a wizard-based development process for creating Rational HATS

applications.
Deployments
Routes applications to IBM WebSphere Application Server and IBM WebSphere Portal
Server, as well as a number of devices and clients.
Creates standard web applications for deployment to WebSphere Application Server.
Customizes portlets with the Rational HATS Toolkit for deployment to WebSphere
Portal Server.
Optimizes web applications for mobile devices running Apple iPhone OS or Microsoft
Windows Mobile.
Creates a standard Eclipse rich client application for deployment to IBM Lotus Notes,
Lotus Expeditor or Eclipse Rich Client Platform.
For more information about the IBM Rational HATS product, see the following websites:
Rational HATS product web page:
http://www-03.ibm.com/software/products/us/en/rhats
IBM Rational Host Access Transformation Services (HATS) V9.0 Information Center:
http://pic.dhe.ibm.com/infocenter/hatshelp/v90/index.jsp
9.3.6 IBM Rational Application Management Toolset (AMT)

Rational Application Management Toolset for i provides IBM i system administrators and other
advanced users with a lightweight set of tools for the common tasks of working with library file
system objects and for creating and maintaining Command Language
(CL) programs.
Application Management Toolset for i is a subset of the Application Development Toolset
(ADTS), which is sold as part of WebSphere Development Studio for i V6.1 or as part of
Rational Development Studio for i V7.1. Two of the key components of ADTS are
Programming Development Manager (commonly known as PDM) and Source Entry Utility
(commonly known as SEU).
In version 7.2 the original product 5761-AMT was migrated to product 5770-AMT
The new Application Management Toolset for i includes these two components, in modified
form, is illustrated in Figure 9-15 on page 367.
366
8249_AppDev.fm
Application Development
ToolSet (ADTS)
Language Editor - COBOL
Application Management
ToolSet (AMTS)
Language Editor - RPG
SEU - Language Editor - CL
Language Editor - DDS
Programming Development Manager
Language Editor - CL
Programming Development Manager

Interactive Source Debug
Screen Design Aid
Data File Utility
Character Generator Utility
Advanced Printer Function
File Compare and Merge Utility
Figure 9-15 Application Management Toolset for i includes modified components of ADTS
The version of SEU that is included in Application Management Toolset for i supports only
editing of the CL source. It does not support editing of source members that are written in
other languages, such as RPG, COBOL, C, C++ or DDS. Like SEU, this editor provides
language-sensitive features, such as syntax checking and prompting for CL source members.
Application Management Toolset for i supports the operating system member types CL,
CLLE, CLP, TXT, and CMD in the EDTCLU (same as STRSEU) command.
The version of PDM that is included in Application Management Toolset for i can be used to
browse, move, filter, and manipulate objects of any type, but it enables only software
development options (such as Edit and Compile) for CL objects.
Application Management Toolset for i supports the following functions from PDM:
All the menu functions of STRPDM (new command STRAMT)
All the functions of WRKLIBPDM (new command WRKLIBAMT)
All the functions of WRKOBJPDM (new command WRKOBJAMT), including FNDSTRPDM (new
command FNDSTRAMT), except for:
No option 18 to call DFU.
No option 34 to call ISDB.
No option 54 to call CMPPFM.
All the functions of WRKMBRPDM (new command WRKMBRAMT), including FNDSTRPDM (new
command FNDSTRAMT), with the following exceptions:
Option 2 (Edit) uses the new command EDTCLU, which supports only the CL, CLLE,
CLP, TXT, and CMD member types.
No option 17 to call SDA.
No option 19 to call RLU.
367
8249_AppDev.fm
No option 54 to call CMPPFM.

No option 55 to call MRGSRC.
None of the other components from ADTS are included with Rational Application
Management Toolset for i.
Application Management Toolset for i Licensing

IBM Rational Application Management Toolset for i 7.2 (5770-AMT) is licensed per processor,
for unlimited usage on that processor by any number of persons. The license is priced
according to the software tier of the machine on which Application Management Toolset for i
is used.
Like WebSphere Development Studio for i and Rational Development Studio for i, ongoing
maintenance and support costs for Application Management Toolset for i are included in the
IBM i system Software Maintenance agreement (SWMA).
Application Management Toolset for i Requirements

Hardware requirements:
IBM Rational Application Management Toolset for i V6.1 supports all the hardware models
that support IBM i 6.1 and 7.1.
Software requirements:
IBM Rational Application Management Toolset for i V6.1 supports IBM i 7.2.
Accessing Application Management Toolset for i

The main menu for Application Management Toolset for i (AMT) (Figure 9-16) can be
accessed by running STRAMT.
Application Management Toolkit (AMT)
Select one of the following:
1. Work with libraries
2. Work with objects
3. Work with members
9. Work with user-defined options
Selection or command
===>
F3=Exit
F12=Cancel
F4=Prompt
F9=Retrieve
F18=Change defaults
F10=Command entry
Figure 9-16 Main menu for Application Management Toolkit for i
9.3.7 ARCAD Pack for Rational

ARCAD Pack for Rational provides modern development enhancements to Rational Team
Concert and Rational Developer for i. Designed specifically to complement these Rational
products, ARCAD Pack provides a modern collaborative development environment,
supporting both agile and traditional methods. ARCAD Pack for Rational uses deep
368
8249_AppDev.fm
dependency analysis to provide audit, impact analysis, intelligent build and deployment
capabilities and also allows RPG code to be converted to the latest free format RPG
specifications.
ARCAD Pack for Rational helps IBM i development teams deliver high quality software faster
based on six main components:
ARCAD-Observer
ARCAD-Observer brings easy-to-use application intelligence, for maintaining and
transferring knowledge of existing systems. ARCAD-Observer references all
dependencies between applications and components down to the field and source line
level, whatever language is used. This solution provides to analyze the information flow
across processes, produce data models, perform cross-platform impact analysis, and
quickly identify business rules contained in the code. The built-in editor displays
information as graphics that can be enhanced and included in documentation.
ARCAD-Builder
ARCAD-Builder automates 100% of the build process for any type of IBM i component.
Executable code is recreated without any manual intervention and ensuring no regression.
ARCAD-Deliver
ARCAD-Deliver coordinates deployment of all platform components in a single transfer
operation. With this solution provides to manage a deployment process from a central
console and deploy any type of files to any number of target servers that run IBM i, AIX,
UNIX, Linux, and Windows operating systems.
ARCAD-Audit
ARCAD-Audit provides IBM i code audit and restructuring. ARCAD-Audit identifies such
as:
Multiple copies of the same code

Which objects are really used in production
Source without objects
Objects without source
Source with a date later than the object
Unused objects
ARCAD-Converter
ARCAD-Converter, which works as a plug-in of Rational Developer for i, supports to
convert fixed-form RPG sources to free-form RPG sources with the latest compiler specs.
This solution supports both of on-demand (statement-by- statement) and bulk conversions
to accelerate the modernization of RPG code.
CASE and 4GL support
CASE and 4GL support allows CASE/4GL such as CA 2E (Synon), JD Edwards (JDE),
LANSA and Adeliathe following environments to be managed.
For more information about ARCAD Pack for Rational, see the Modernizing IBM i Applications
from the Database up to the User Interface and Everything in Between, SG24-8185 available
at:
And also see the following website of ARCAD:
http://arcadsoftware.com/products/arcad-pack-for-rational/
369
8249_AppDev.fm
9.4 PASE
There are currently 2 news for PASE Environment
PASE now supports programs compiled for AIX 7.1
New version of OpenSSL 1.0.1g is now included in 5733-SC1, IBM Portable Utilities for i
7.2.
9.5 Ruby on Rails for i

Operably is a freely available and commercially supported port of the Ruby language. It is a
web application development framework (Rails) written in the Ruby language.
This product is available for download from the following website:
http://powerruby.com/
To learn more about PowerRuby also see the following website:
https://twitter.com/rubyonpower
9.6 Zend Server and PHP on i

PHP stands for PHP Hypertext Preprocessor. PHP is an open source scripting language that
is designed for web application development and enables simple scripting.
PHP applications are easily integrated with data in IBM DB2 for i, RPG, COBOL, and other
business applications that are running on IBM i.
PHP is used for content management, customer relationship management, database access,
e-commerce, forums, blogs, wikis, and other web-based applications.
Zend and IBM worked together to deliver Zend Solutions for IBM i, a complete PHP
development and production environment solution for the IBM i platform.
Here are the Zend Solutions for IBM i:
Zend Server Community Edition for IBM i (one year Silver Support from Zend)
Zend Server for IBM i
Zend Studio for IBM i (One year of Silver support from Zend)
Zend DBi
Tip: Use always the distribution downloaded from Zend website. It contains latest up to
date version of Zend Server Community Edition
Zend Server version 7 currently support IBM i 7.2

More about Zend products can be found on Zend web page
http://www.zend.com/en/solutions/modernize-ibm-i
Figure 9-17 shows the Zend application development and deployment architecture for IBM i.
370
8249_AppDev.fm
Figure 9-17 Zend PHP Application development and deployment architecture for IBM i
9.6.1 What is new in Zend Server 7?

Zend server provides the following new functionality:
Zend Server Z-Ray monitors requests to the Web server and displays relevant information
on Web page component in your browser including PHP functions, SQL queries, sessions
and cookie data, errors, warnings, server events, memory use, request execution time
metrics, and more.
Z-Ray, can give developer deep insight of PHP code, allowing them to inspect, debug and
optimize their pages.
With Secure Mode, administrators can provide developers safe and restricted access to
Z-Ray for pages in production applications.
9.6.2 Zend Server Community Edition for IBM i

Zend Server Community Edition (CE) is a fully tested and enhanced version of the open
source PHP. It provides the PHP runtime and is packaged to make the software installation
easier and faster with the instant PHP setup. It is enhanced to take advantage of IBM i
specific resources and capabilities.
Zend Server CE for IBM i is a lightweight version of Zend Server, and replaces Zend Core. It
offers the following features:
Preinstalled on IBM i 6.1 and IBM i 7.1 starting April 2010.
Includes extensions and a toolkit that provides the following functions:
371
8249_AppDev.fm
Enables PHP application to easily access DB2 for i data

Takes advantage of RPG and COBOL applications in IBM i
Supports for Program call, Procedure call, Data Area, Data Queue, Message Queue,
Commands, and System values
Simple to install and to use, and provides basic performance optimization.
Available at no charge to for using in development or in production, and it comes with an
initial year of Silver Support that is provided by IBM.
Zend Server is the only Zend certified and supported version of PHP for IBM i.
9.6.3 Zend Server for IBM i Version 7

Zend Server is a robust PHP production environment that helps ensure that applications
written in PHP run smoothly at all time. It is designed for IT personnel and businesses that
require commercial grade web applications in highly reliable production environments.
Zend Server replaces the Zend platform. It offers all the features that are provided in Zend
Server CE for IBM i and the following additional features:
High performance and scalability to provide customers with an improved web experience
and response time.
Delivers application uptime and reliability through enhanced PHP monitoring and
immediate problem resolution.
Includes the Java Bridge for integrating PHP application with Java application.
Includes 5250 bridge for integrating 5250 applications with PHP applications. The 5250
bridge allows running interactive IBM i based applications from a web browser.
Cloud connected Mobile Deployment
Zend Framework 2, Zend Server Gateway
PHP 5.4, PHP 5.3 are supported, PHP 5.2 is not supported
Side by side Migration of Zend Server 5.6 and 6.0
Improved User Interface, role based access
Global monitoring rules by application
Shared Memory Toolkit option improves speed 30%+
Zend Server Z-Ray monitors requests to the Web server and displays relevant information
on Web page component in your browser including PHP functions, SQL queries, sessions
and cookie data, errors, warnings, server events, memory use, request execution time
metrics, and more.
Z-Ray, can give developer deep insight of PHP code, allowing them to inspect, debug and
optimize their pages.
With Secure Mode, administrators can provide developers safe and restricted access to
Z-Ray for pages in production applications.
The following website shows a comparison between the features that are offered in Zend
Server CE for IBM i and Zend Server for IBM i:
http://www.zend.com/en/products/server/editions-ibm-i
372
8249_AppDev.fm
9.6.4 Zend Studio for IBM i V11

Zend Studio for IBM i is an industry-leading Eclipse-based PHP integrated development
environment (IDE) designed for professional developers. It includes all the development
components necessary for the full PHP application lifecycle and simplifies complex projects. It
now supports development for mobile devices as well using PHP REST XML Web Services.
Zend Studio for IBM i includes the following features and enhancements:
Enhanced to work with the integration toolkit provided with Zend Server and Zend Server
CE for IBM i
Includes a comprehensive set of editing, debugging, analysis, optimization, database, and
testing tools
Toolkit support for easy integration with earlier IBM i applications and data
Customizable and context-sensitive templates for IBM i Toolkit functions
Create / generate PHP Toolkit code quickly
Call an RPG/CL/COBOL program, run a CL command, retrieve Spooled file entries, and
access Data Area, Data Queue, and User Space.
Zend Studio allows development for mobile clients:
Web
Native i/OS (Mac)
Android
Windows Mobile
9.6.5 Zend DBi and actual PHP database support

The Zend DBi product provides MySQL implementation for IBM i. DB2 Storage Engine
enables MySQL data storage in DB2.
Zend DBi is currently supported only for IBM i. 6.1 and 7.1
Zend DBi provides support for Open Source based applications. The application uses MySQL
data commands against Zend DBi or MySQL database, the storage engine translates the
commands, and then passes to DB2 for i. With this solution there is only one database to
manage, backup, and protect. See Figure 9-18.
Figure 9-18 Zend DBi and MySQL using DB2 Storage engine
PHP now supports the following database connectivity:

Local DB support for MySQL and DB2
Remote DB support for MySQL and Oracle
373
8249_AppDev.fm
For more information about Zend products for IBM i, see the following websites:
Zend and IBM i:
http://www-03.ibm.com/systems/i/software/php/index.html
Zend Products for IBM i:
http://www.zend.com/en/solutions/modernize-ibm-i/ibm-i-products
Zend Studio:
http://www.zend.com/en/products/studio/
Zend DBi:
http://www.zend.com/products/dbi/
9.7 Mobile application development for IBM i

Mobile support is described in several chapters and sections in this book. If we speak about
mobile support we speak either about system management or mobile support in application
development tools which enables to develop mobile applications in connection with IBM i.
The following products now support mobile access application development:
RPG Open Access

XML Services
JTOpen Lite
PHP - Zend Server for IBM i, Zend Studio
IBM Connections 5.0
IBM Notes Traveler 9.0.1
IBM Mobile Database
DB2 WebQuery
Rational HATS
IBM i Mobile Access enables IBM i users to access IBM i resources from web-enabled mobile
devices in a mobile-friendly view using mobile web browser, for more information see 2.2.3,
IBM i Mobile Access on page 130.
374
8249_Misc.fm
10
Chapter 10.
IBM i server functionality

This chapter describes enhancements in several IBM i servere functionalities like:
10.1, IBM HTTP Server for i on page 376

10.2, IBM i Integrated Web Application and Web Services Server on page 378
10.3, IBM WebSphere Application Server on page 382
10.4, IBM Social Collaboration products on page 385
10.5, IBM Printing on page 385
375
8249_Misc.fm
10.1 IBM HTTP Server for i

IBM HTTP Server for i provides the facility of Web serving in IBM i using 5770-DG1 product.
The implementation of this HTTP server is based on open-source server code provided by
the Apache Software Foundation. This section explains the enhancements of IBM HTTP
Server for i in IBM i 7.2 release.
10.1.1 Licensed program requirements

These are the licensed program requirements for using IBM HTTP Server for i in IBM i 7.2:
Extended Base Directory Support (5770-SS1 Option 3).
Host Servers (5770-SS1 Option 12).
Qshell (5770-SS1 Option 30).
IBM Portable Application Solutions Environment for i (5770-SS1 Option 33).
IBM TCP/IP Connectivity Utilities for i (5770-TC1).
IBM Developer Kit for Java (5770-JV1 Option 11).
10.1.2 Upgraded to Apache 2.4

IBM HTTP server in IBM 7.2 release is upgraded from Apache 2.2 as in IBM i 7.1 to Apache
2.4. Comparing to Apache 2.2, this upgrade delivers significant core enhancements, new
features/modules, as well as configuration and access control changes. All current Apache
2.4 security vulnerability issue are also fixed in IBM i 7.2.
As IBM i 7.2 release provides the updated version of Apache, which is Apache 2.4, users are
required to consider their web applications before moving from an earlier release of IBM i to
the IBM i 7.2 release. It is recommended to see the IBM i 7.2 Memo to Users as well as IBM
developerWorks website, which summarize the HTTP server changes.
Configuration-related changes
There are some configuration-related changes in IBM i 7.2 release along with Apache 2.4.
This section will explain those changes that might require users to change their configuration
so that they can continue to use HTTP Server on IBM i 7.2.
Load balancing implementations moved to mod_proxy sub modules

All load balancing implementations have moved to individual, self-contained mod_proxy
submodules, such as: mod_lbmethod_byrequests, mod_lbmethod_bybusyness, and
mod_lbmethod_by traffic. Its default value is byrequest. Users might need to load any of
these load balancing implementation method that corresponds to the configuration used.
DefaultType no longer has any effect

The DefaultType directive no longer has effect other than to emit a warning if it is used with
any value other than none. For unknown file extensions, which are not declared in
/QIBM/UserData/HTTPA/conf/mime.types (for example, the .mbr files in QSYS file system),
HTTP server does not add a DefaultType (text/plain) in the response anymore. To display
these files correctly, users are now required to assign media types in IBM i 7.2, for example:
"AddType text/html .mbr.
376
8249_Misc.fm
Options default value is changed

The default value of directive Options was changed from All to FollowSymlinks. Users need
to adjust their configuration related to this default value change.
Module mod_disk_cache is renamed

Module mod_disk_cache is renamed to mod_cache_disk. Users need to replace LoadModule
disk_cache_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM with LoadModule
cache_disk_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM.
For more information about mod_cache_disk, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaie/rzaiemod_cache_di
sk.htm
CacheEnable directive is changed

The second parameter to CacheEnable in mod_cache matches forward proxy conent only if it
begins with correct protocol. In IBM i 7.1 and earlier version, a parameter of / matched all
content. Specifying <protocol>:// for the second parameter caches forward proxy content
only from te default port of that protocol.
In IBM i 7.2, CacheEnable disk http:// now caches HTTP forward proxy content only from
port 80. Use CacheEnable disk http://*: instead to cache http forward proxy content from
all ports.
FileETag default value is changed

FileEtag default value in Apache 2.4 is changed to MTimeSize, without INode, which exists in
Apache 2.2.
mod_dav_fs changed
The format of DavLockDB in mod_dav_fs is changed for systems with inodes. The old
DavLockDB file must be deleted on upgrade to Apache 2.4.
mod_deflate skips compressions

mod_deflate is now able to skip compression process if it knows that the size of increase
added by the compression is larger than the data to be compressed.
KeepAlive value is changed

In previous release, KeepAlive value other than Off or 0 was treated as On. In Apache 2.4,
KeepAlive only accepts value of On or Off.
mod_log_config matches whole cookie name

In previous release, ${cookie}C in mod_log_config matches any string. However, in Apache
2.4, ${cookie}C matches whole cookie names.
Syntax changes in mod_filter

FilterProvider syntax in mod_filter is changed and now uses a boolean expression to
determine whether a filter is applied.
mod_include changes
The #if expr element now uses the new expression parser. The old syntax can be
restored with the new directive SSILegacyExprParser.
An SSI* configuration directive in directory scope no longer causes all other per-directory
SSI* directives to be reset to their default values.
Chapter 10. IBM i server functionality
377
8249_Misc.fm
mod_autoindex extracts titles and descriptions

mod_autoindex is now able to extract titles and display description for .xhtml files, which are
previously ignored.
For more complete information about changes in IBM i 7.2 along with Apache 2.4, see the
IBM i 7.2 Memo to Users document at:
And for more complete information about the new Apache 2.4 modules compared to 2.2, see
the Apache website developer website at:
http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html
For more information about IBM HTTP Server for i, see the IBM HTTP Server
developerWorks at:
echnology%20Updates/page/IBM%20HTTP%20Server%20Upgrading%20to%20Apache%202.4
10.1.3 Web Admin for managing WebSphere Application Server installation

WebSphere Application Server V8.0 and later must be installed using IBM Installation
Manager. As this tool does not have any Graphical User Interface (GUI) on the IBM i Platform,
IBM Web Administration for i in IBM i 7.2 (also known as Web Admin) provides an easy-to-use
GUI for managing the installation of WebSphere Application Server.
From IBM i 7.2 Web Admin, users can easily install, uninstall, update fix packs, apply interim
fixes, and so on, by using simple wizards.
For more information about installing and managing WebSphere Application Server
installation using IBM Web Administration for i, see the IBM developerWorks at:
http://www.ibm.com/developerworks/ibmi/library/i-webSphere_spplication_server_inst
allation/
For more information about IBM HTTP Server for i, see the IBM i 7.2 Knowledge Center at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaie/rzaiemain.htm
For more information about Electronic business and Web serving in IBM i 7.2 using IBM
HTTP Server for i, see the product documentation at:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzaie/rzaie
pdf.pdf
10.2 IBM i Integrated Web Application and Web Services Server

New IBM WebSphere Application Server Liberty Profile based IBM i Integrated Web
Application Server (IAS) and IBM i Integrated Web Services Server (IWS) are introduced in
IBM i 7.2. Leveraging IBM WebSphere Application Server Liberty Profile, the benefits such as
the following are provided to IBM i Integrated Web Application Server and IBM i Integrated
Web Services Server environments:
378
8249_Misc.fm
Ability to ensure PCI Compliance by being able to obtain and apply correcting patches
against security vulnerabilities which is delivered as security updates for WebSphere web
containers
Easy to adopting new technologies such as new Java Virtual Machines and a Web
Services runtime engine
Enable to leverage common development tools, such as Rational Application Developer
(RAD), for developing applications run on IAS
10.2.1 IBM i Integrated Web Application Server

Both of IBM Light Weight Infrastructure (LWI) based IAS and IBM WebSphere Application
Server Liberty Profile based IAS are working on IBM i 7.2. The version of LWI based IAS is
8.1 and the version of Liberty Profile based IAS is 8.5.
LWI based IAS V8.1 is delivered for performing existing IAS instances purpose only, so that
you can not create new instances of LWI based IAS on IBM i 7.2. Instead you can create new
Liberty Profile based IAS V8.5 instances and you are encouraged to leverage Liberty Profile
based IAS V8.5 instead of LWI based IAS V8.1. Actually IBM provided IAS based
applications, such as DB2 Web Query for i (5733-WQX), IBM Application Runtime Expert for i
(5733-ARE), and IBM Web Administration for i (as known as Web Admin), are already moved
to Liberty Profile based IAS. Figure 10-1 shows the Create Application Server wizard in IBM
Web Administration for i in IBM i 7.1 with TR8 timed HTTP Group PTFs. In this wizard, you
can choose the version of IAS both V8.1 and V8.5. And in IBM i 7.2, you can create an IAS
V8.5 instance only as shown in Figure 10-2.
Figure 10-1 Create Application Server wizard in IBM Web Administration for i in IBM i 7.1
379
8249_Misc.fm
Figure 10-2 Create Application Server wizard in IBM Web Administration for i in IBM i 7.2
And if you have any IAS V7.1 instances and are upgrading your IBM i to 7.2, these instances
will be automatically upgraded to V8.1 instances, which is LWI based IAS, during upgrading to
IBM i 7.2.
Note: You can continue to use those IAS V8.1 instances and deploy your application on
those instances, but IBM highly recommends to migrate your applications to IAS V8.5,
Liberty Profile based instances since the LWI based runtime will be removed in a future
release. And there is no automatic upgrade from IAS V8.1 to V8.5 since the runtimes are
based on totally different technologies.
For more information about IBM i Integrated Web Application Server, see the developerWorks
at:
echnology%20Updates/page/News%20of%20Web%20Integration%20on%20IBM%20i
10.2.2 IBM i Integrated Web Services Server

IBM WebSphere Application Server Liberty Profile based IBM i Integrated Web Services
Server (IWS) is introduced in IBM i 7.2 as version 2.6. Because IWS V2.6 is powered by
JAX-RS (Java API for RESTful Web Services), IWS V2.6 supports REST services.
Figure 10-3 shows a concept of IWS V2.6 REST services. IWS V2.6 is running on IAS V8.5
and sends JSON REST packets to web service requesters.
380
8249_Misc.fm
Figure 10-3 Concept of IWS V2.6 powered by Liberty Profile and JAX-RS
As well as the relation IAS V8.5 and V8.1, IWS V1.5 is also available in IBM i 7.2, which is
LWI based Web services server. If you have any existing IWS instances that are running with
V1.3, you must upgrade those to IWS V1.5 by using the upgrade wizard that is part of the IBM
Web Administration for i GUI. The wizard is shown in the navigation bar if the server is eligible
to be upgraded.
Note: After upgrading to IWS V1.5, you can continue to use those IWS instances in IBM i
7.2, but IBM highly recommends to migrate to IWS V2.6 since the LWI based runtime and
web services will be removed in a future release.
In addition to REST support, the IWS V2.6 scripting is updated in the following ways:
The restoreWebServices.sh script is enhanced to enable the migration of web services
that are located on an IWS server V1.5 to an IWS server that is based on Liberty. Users do
not have to go through the process of reinstalling the web services manually to a new IWS
server.
Note: When you move from IWS V1.5 to the newest version of IWS, Web Services
Description Language (WSDL) include the following changes:
The schema namespace is different; only one SOAP version can be specified.
The URL endpoint will be different.
New QShell scripts, saveWebServicesServer.sh and restoreWebServicesServer.sh,
enable users to save IWS servers and restore the servers on another Power system
running IBM i. This includes the deployed web services. It ensures that the corresponding
back-end ILE programs are on the new system.
For more information about IBM i Integrated Web Services Server, see the following product
website:
http://www-03.ibm.com/systems/power/software/i/iws/index.html
And for more information about enhancements of IWS, also see the developerWorks at:
381
8249_Misc.fm
https://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/dW%20IBM%20I
ntegrated%20Web%20Services%20for%20i/page/Welcome%20to%20IBM%20Integrated%20Web%20
Services%20for%20i%20Technology%20Updates
10.3 IBM WebSphere Application Server

IBM WebSphere Application Server is the leading open standards-based application
foundation, offering accelerated delivery of innovative applications and unmatched
operational efficiency, reliability, administration, security, and control on IBM i. This section
covers the following:
Supported WebSphere Application Server on IBM i 7.2

WebSphere Application Server Liberty Core Packaging
WebSphere Application Server Liberty Profile
Installation of WebSphere Application Server to IBM i
Upgrading to IBM i 7.2
10.3.1 Supported WebSphere Application Server on IBM i 7.2

On IBM i 7.2, the following package options of WebSphere Application Server are supported:
IBM WebSphere Application Server Express V8.0/V8.5
IBM WebSphere Application Server Base V8.0/V8.5
IBM WebSphere Application Server Network Deployment V8.0/V8.5
IBM WebSphere Application Server for Developers V8.0/V8.5
IBM WebSphere Application Server Liberty Core V8.5.5
Note: IBM WebSphere Application Server V6.1 and V7.0 do not supported on IBM i 7.2. If
you have these WebSphere Application Server environments on IBM i, you also need to
migrate your WebSphere Application Server to appropriate versions when upgrading to
IBM i 7.2.
Figure 10-4 shows a high-level view of the packaging options of IBM WebSphere Application
Server for i.
382
8249_Misc.fm
Figure 10-4 WebSphere Application Server for i packaging options
Minimum maintenance level of each package options of WebSphere Application Server V8.0
that is supported on IBM i 7.2 is V8.0.0.7. And of WebSphere Application Server V8.5 is
V8.5.5.2.
For more information about support versions of IBM WebSphere Application Server, see the
IBM Support website at:
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27006921#8.0
IBM WebSphere Application Server Express for i is delivered as the part of IBM Web
Enablement for i (5770-WE2). IBM Web Enablement for i product on IBM i 7.2 includes the
following versions of IBM WebSphere Application Server Express so that you can choose the
version of IBM WebSphere Application Server Express to install on your IBM i platform as you
want:
IBM WebSphere Application Server Express for i V8.0
IBM WebSphere Application Server Express for i V8.5
10.3.2 WebSphere Application Server Liberty Core Packaging

In WebSphere Application Server V8.5.5, WebSphere Application Server Liberty Core is
newly introduced as a stand-alone package option for delivering WebSphere Application
Server Liberty Profile and it is also available as for IBM i. WebSphere Application Server
Liberty Core does not include the wider range of features that is found in the Liberty profile
shipped with the other WebSphere Application Server package options.
383
8249_Misc.fm
For more Information about WebSphere Application Server Liberty Core, see the IBM
WebSphere Application Server Liberty Core V8.5.5 Knowledge Center at:
https://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.
core.doc/ae/cwlp_core_welcome.html
10.3.3 WebSphere Application Server Liberty Profile

WebSphere Application Server Liberty Profile provides the capabilities to rapidly build and
deliver web applications that do not need the full Java EE stack. Liberty Profile is delivered
within each package options V8.5 or later. And since V8.5.5, Liberty Profile is also available
as a stand-alone offering known as WebSphere Application Server Liberty Core.
This profile is intended for use as a development or production environment for running web
applications that do not require a full Java EE stack. The Liberty profile provides enterprise
qualities of service, including security and transaction integrity.
Because a Liberty Profile server is lightweight, it can be packaged easily with applications in a
compressed file. This package can be stored, distributed to colleagues, and used to deploy
the application to a different location or to another system. It can even be embedded in the
product distribution. The Liberty profile configuration operates from a set of
built-inconfiguration defaults. You can specify only the required changes for your environment
byusing a simple XML format.
For more information about WebSphere Application Server Liberty Profile in WebSphere
Application Server V8.5.5, see the WebSphere Application Server V8.5.5 Technical Overview,
REDP-4855, available at:
http://www.redbooks.ibm.com/abstracts/redp4855.html?Open
And in IBM i 7.2 TR1 timed enhancements, IBM i Integrated Application Server and
Integrated Web Services Server become to leverage WebSphere Application Server Liberty
Profile. For more Information about the enhancements of IBM i Integrated Application Server,
see the 10.2, IBM i Integrated Web Application and Web Services Server section in this
chapter.
10.3.4 Installation of WebSphere Application Server to IBM i

In IBM i 7.2, the Web Administration for i user interface can be used for installing WebSphere
Application Server package options to IBM i. IBM Installation Manager is required for install
WebSphere Application Server package options. The new user interface of Installing
WebSphere Application Server in Web Administration for i also includes installing IBM
Installation Manager to IBM i.
For more Information about Installation of WebSphere Application Sever to IBM i, see the
10.1.3, Web Admin for managing WebSphere Application Server installation section.
10.3.5 Upgrading to IBM i 7.2

If you are currently using Application Server V7.0 and upgrading to 7.2, you need to migrate
to the WebSphere Application Server V8.0.0.8 or V8.5.5.2 products. Because migration does
not require Application Server V7.0 to be operational, migration can occur before or you
upgrade to 7.2.
384
8249_Misc.fm
For more information about migrating your existing WebSphere Application Server
environments, see the IBM i 7.2 Memo to Users document at:
10.4 IBM Social Collaboration products

Currently IBM 7.2 supports the following social collaboration products (formerly IBM Lotus
brand):
IBM Domino 9.0.1;

IBM Notes Traveler 9.0.1;
IBM Sametime 9.0; Sametime 9.0 requires HF1 to support IBM i 7.2.
IBM Enterprise Integrator 9.0.1;
Actual compatibility of IBM social collaboration products can be found in the following
document:
http://www.ibm.com/systems/resources/systems_power_ibmi_lotus_releasesupport.pdf
Note: There is of course larger set of IBM Lotus product versions which support IBM i 7.1,
but not yet 7.2. When in the future some of such products will be needed, additional check
must be done if version compatible with IBM 7.2 is already releases.
10.5 IBM Printing

10.5.1 CPYSPLF command now support PDF format
The CPYSPL command now includes the possibility to copy spool file to IFS in PDF format.
The new option *PDF for parameter WSCST has been added.
Example 10-1 Example of CPYSPLF command with *PDF option
CPYSPLF FILE(QPRINT)
TOFILE(*TOSTMF)
JOB(000172/QSECOFR/DSP01)
SPLNBR(1)
TOSTMF('/home/qprint.pdf')
WSCST(*PDF)
10.5.2 Controlling the method of sending spooled files from list panels
By using an environment variable, you can control whether spooled files are sent using the
SNDNETSPLF (SNADS) or SNDTCPSPLF (TCP/IP) command from the WRKSPLF,
WRKOUTQ, and WRKJOB OPTION(*SPLF) panels.
The default method of sending spooled files from the WRKSPLF, WRKOUTQ, and WRKJOB
OPTION(*SPLF) panels by specifying "1=Send" uses the SNDNETSPLF command. If you
would prefer to use the SNDTCPSPLF command to send spooled files from these panels, you
can do that by using the environment variable QIBM_SNDSPLF_OPT.
385
8249_Misc.fm
To change the default command for your job to be SNDTCPSPLF, enter the command:
ADDENVVAR ENVVAR(QIBM_SNDSPLF_OPT)VALUE(TCP)LEVEL(*JOB)
To change the default command for the system to be SNDTCPSPLF, enter the command:
ADDENVVAR ENVVAR(QIBM_SNDSPLF_OPT)VALUE(TCP)LEVEL(*SYS)
The environment variable name and its value must be uppercase. If the environment variable
is not found or not set to TCP, the system defaults to use the SNDNETSPLF command from
the spooled file list panels.
10.5.3 Changes to TrueType and OpenType Fonts

The TrueType fonts are delivered as option 43 to the IBM i Operating System product
5770-SS1. They are provided as stream files in the TrueType (OpenType) format.
TrueType and OpenType fonts are expected to be found in one of two integrated file system
directories:
/QIBM/ProdData/OS400/Fonts/TTFonts for IBM supplied fonts.
/QIBM/UserData/OS400/Fonts/TTFonts for user fonts.
It is possible to specify additional directories for user fonts by using environment variable
QIBM_FONT_RESOURCES_PATH. One or more directories, separated by a colon, can be
specified.
When searching for fonts, the system looks to see whether there are any paths set in the
environment variable QIBM_FONT_RESOURCES_PATH. If so, those paths are searched
first. Then the UserData path is searched, followed by the ProdData path.
The detailed table of font being provided can be found here:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzalu/rzalucontruetype.
htm
10.5.4 New bar code types for printer DDS BARCODE keyword
BARCODE DDS keyword now supports these new types of barcodes:
QR Code
Code 93
USPS Intelligent Mail
Royal Mail Red Tag
GS1 Databar
Some modifiers to formerly supported barcodes were added to the following barcodes:
UCC/EAN 128 (or GS1-128)
USPS intelligent Mail Container
GS1 ITF-14
The UCC/EAN 128 (or GS1-128) bar code can be selected by specifying the CODE128
bar-code-ID and a bar code modifier of 03 or 04.
The USPS Intelligent Mail Container bar code can be selected by specifying the CODE128
bar-code-ID and a bar code modifier of 05.
386
8249_Misc.fm
The GS1 ITF-14 bar code (Interleaved 2 of 5 with bearer bars) can be selected by specifying
the INTERL2OF5 bar-code-ID and a bar code modifier or 03 or 04.
Also Databar and Intelligent Mail barcodes can be rendered by Host Print Transform and
Transform Services (5770-TS1 - as PDF).
The detailed definition of BARCODE Keyword can be found here:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzakd/rzakdmstptbarco.h
tm
10.5.5 Common Image Support

Supporting color printing in IBM 7.2 is one of news this version brings in printing area.
Following sections describe these enhancementsin a brief only. The whole color image
support is quite a complicated area which includes IBM products like Print Services Facility
for IBM i, IBM InfoPrint Server for i, and Ricoh products as well. Refer please to:
IBM Knowledge Center for IBM i 7.2, Printing section at:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahg/rzahgprint.htm
and
RICOH website at:
http://www.ricoh.com
The AFP Consortium (AFPC) was founded in 2004 and renamed to the AFP Color
Consortium. Its members are companies which develop and imprpove the AFP Color
Management Architecture (ACMA). The consortiums present scope is the complete
Advanced Function Presentation (AFP) architecture.
Resources related to this consortium can be found at its web site:
http://afpcinc.org
10.5.6 Color Management Support added to Print Services Facility for IBM i
Print Services Facility for IBM i were enhanced to support AFP Color Management
Architecture (CMOCA).
Mechanism to print color consistently on different printers by different manufacturers was
added. Color profiles for input and output are used to adjust colors automatically at high
speed.
Requirese the AFP Resource Installer Tool to generate Resource Access Table (RAT)
10.5.7 Host Print Transform now supports color images

The AFP-to-ASCII transform is support color images when printing to color printer supporting
PCL language (for instance PCL5C). The supported images are JPG, GIF, and TIF. The
images can be references by the AFPRSC DDS keyword. Stream files can be used to
reference the the resources.
Please refer to Programming DDS for printer files publication in IBM Knowledge Center at:
387
8249_Misc.fm
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzakd/printthis.htm
See also information about Workstation Customization Object tag PRTDTASTRM using the
following link:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzalu/prtdtastrm.htm
10.5.8 AFP color and grayscale solutions

It is now possible to include color images color images or specify colors for AFP objects in
your spooled files and send them to an AFP color printer. The color images and objects print
in color, which is based on the default settings in your print server and printer.
You can do it either without explicit color management, or with it. Of course using color
management allows to print color images in exact colors, possibility to calibrate devices, like
scanners and printers, and so on. Color management solutions are now supported by RICOH
produtcs. For details go to the following page.
http://www.ricoh.com
For color and grayscale printing you can utilize the AFP Color Management Object Content
Architecture (CMOCA) You can include the AFP CMOCA resources incline in your spool file,
or you can manage and store it centrally which allows you to leverage full advantages of
CMOCA Architecture as well as to imrpove the speed of print processing.
You graphical objects may have different formats like including AFPC JPEG Subset, EPS,
GIF, IOCA, PDF, PNG, and TIFF.
For uploading data objects the AFP Resource Installed should be used. It can be also used to
upload to It can be found at:
http://rpp.ricoh-usa.com/products/software/color-manage/afp-resource-installer
388
8249bibl.fm
Related publications
The publications listed in this section are considered particularly suitable for a more detailed
discussion of the topics covered in this book.
IBM Redbooks
The following IBM Redbooks publications provide additional information about the topic in this
document. Note that some publications referenced in this list might be available in softcopy
only.
BM Power Systems SR-IOV: Technical Overview and Introduction, REDP-5065
????full title???????, SG24-xxxx
????full title???????, REDP-xxxx
????full title???????, TIPS-xxxx
You can search for, view, download or order these documents and other Redbooks,
Redpapers, Web Docs, draft and additional materials, at the following website:
ibm.com/redbooks
Other publications
These publications are also relevant as further information sources:
????full title???????, xxxx-xxxx
Online resources
These websites are also relevant as further information sources:
Description1
http://????????.???.???/
Description2
http://????????.???.???/
Description3
http://????????.???.???/
Help from IBM

IBM Support and downloads
389
8249bibl.fm
ibm.com/support
IBM Global Services
ibm.com/services
390
Back cover
IBM i 7.2 Technical Overview

with Technology Refresh Updates
Covers new functions

and enhancements
through IBM i 7.2 TR1
Easy to use
web-based system
management
Integrated
Data-Centric
approach
This IBM Redbooks publication provides a technical overview of the

features, functions, and enhancements available in IBM i 7.2, including
all the available Technology Refresh (TR) levels, which for this version
of this publication covers TR1. This publication provides a summary
and brief explanation of the many capabilities and functions in the
operating system. It also describes many of the licensed programs and
application development tools that are associated with IBM i.
The information that is provided in this book is useful for clients, IBM
Business Partners, and IBM service professionals that are involved with
planning, supporting, upgrading, and implementing IBM i 7.2 solutions.
INTERNATIONAL
TECHNICAL
SUPPORT
ORGANIZATION
BUILDING TECHNICAL
INFORMATION BASED ON
PRACTICAL EXPERIENCE
IBM Redbooks are developed
by the IBM International
Technical Support
Organization. Experts from
IBM, Customers and Partners
from around the world create
timely technical information
based on realistic scenarios.
Specific recommendations
are provided to help you
implement IT solutions more
effectively in your
environment.
For more information:

ibm.com/redbooks
SG24-8249-00
ISBN

sg248249 IBMi7.2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

sg248249 IBMi7.2

Uploaded by

Copyright:

Available Formats

Front cover

Draft Document for Review December 10, 2014 2:51 pm

IBM i 7.2 Technical Overview with

Covers new functions and enhancements

Draft Document for Review December 10, 2014 2:51 pm

International Technical Support Organization

Draft Document for Review December 10, 2014 2:51 pm

First Edition (December 2014)

Copyright International Business Machines Corporation 2014. All rights reserved.

Draft Document for Review December 10, 2014 2:51 pm

Chapter 1. Introduction to IBM i 7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Copyright IBM Corp. 2014. All rights reserved.

Draft Document for Review December 10, 2014 2:51 pm

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

3.2.5 IBM Cloud Manager with OpenStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Draft Document for Review December 10, 2014 2:51 pm

5.9 Single Sign-on for both FTP and TELNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Chapter 6. High availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7. Backup and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 8. IBM DB2 for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

8.3 Security Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9. Application development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Draft Document for Review December 10, 2014 2:51 pm

Chapter 10. IBM i server functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

Copyright IBM Corp. 2014. All rights reserved.

Draft Document for Review December 10, 2014 2:51 pm

Compare and update PTFs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

Omnifind text search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Draft Document for Review December 10, 2014 2:51 pm

2-153 SQL output viewed in IBM i Mobile Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

6-1 PowerHA SystemMirror for i Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Draft Document for Review December 10, 2014 2:51 pm

8-3 Part of Change Function Usage Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

9-8 Source member with annotations which lines were covered . . . . . . . . . . . . . . . . . . .

Draft Document for Review December 10, 2014 2:51 pm

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

Copyright IBM Corp. 2014. All rights reserved.

Draft Document for Review December 10, 2014 2:51 pm

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

Copyright IBM Corp. 2014. All rights reserved.

Draft Document for Review December 10, 2014 2:51 pm

10-1 Example of CPYSPLF command with *PDF option . . . . . . . . . . . . . . . . . . . . . . . . . 385

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

Copyright IBM Corp. 2014. All rights reserved.

Draft Document for Review December 10, 2014 2:51 pm

The following terms are trademarks of other companies:

IBM i 7.2 Technical Overview with Technology Refresh Updates

Draft Document for Review December 10, 2014 2:51 pm

Justin C. Haase is a technical manager for Sirius Computer