Deep dive into RPG free-form

Barbara Morris
IBM

© 2017 IBM Corporation

1
A fully-free RPG program, starting in column 1

**free
ctl-opt bnddir('ACCRCV');
First line has **FREE
dcl-f custfile usage(*update);
dcl-ds custDs likerec(custRec); All free-form statements
dcl-f report printer;
No fixed-form allowed
read custfile custDs;
dow not %eof;
if dueDate > %date(); // overdue?
sendOverdueNotice ();
write reportFmt;
exec sql insert :name, :duedate into
mylib/myfile;
endif;
read custfile custDs;
enddo;
inlr = '1';

dcl-proc sendOverdueNotice;
/copy invoices
sendInvoice (custDs : IS_OVERDUE);
end-proc;

© 2017 IBM Corporation

2
Fully free-form RPG

PTFs for 7.1 and 7.2 provide the ability to code free-form RPG starting in column 1 and going
to the end of the line.
There is no practical limit on the length of a source line.

• CRTSRCPF has a limit of 32766

• IFS files have no limit

© 2017 IBM Corporation

3 3
Fully free-form RPG – how long should your lines be?

Various style-guides for other languages recommend a maximum line length of 80, 132, 120
etc.

The “80” comes from IBM punch cards.

Google [maximum length of a code line] to see some of discussions about line length.

If you create your RPG source files with RCDLEN(112), then that gives you 100 characters,
which is probably ideal.

© 2017 IBM Corporation

4 4
Fully free-form RPG – source must start with **FREE

Any source member that contains

fully-free code must have **FREE in
column 1 of the first line of the source.

**FREE
ctl-opt main(greeting);

dcl-proc greeting;
dsply ‘Hello’;
end-proc;

© 2017 IBM Corporation

5 5
 Fully free-form RPG

• All code in a **FREE source member must be free-form. If you need any fixed-form code,
you can put it in a /COPY file

• Source lines must not begin with ** unless they are the special directives for compile-time
data, file-translation, or alternate collating sequence.

• /FREE and /END-FREE are not allowed in a **FREE source member

© 2017 IBM Corporation

6 6
Fully free-form RPG – copy files

• Each copy file has its own source mode

• A copy file is always assumed to have column-limited source mode unless it has **FREE
in line 1

© 2017 IBM Corporation

7 7
Fully free-form RPG – RDI

RDI V9.5 already supports fully-free RPG code

© 2017 IBM Corporation

8 8
 Fully free-form RPG – Embedded SQL

The SQL precompiler supports fully-free RPG code

**FREE
dcl-s greeting char(10);

exec sql set :greeting = 'Hello';

dsply greeting;
return;

© 2017 IBM Corporation

9 9
What is wrong with fixed-form code?

Most programmers today have never seen fixed form code

When they see RPG code like this, it looks like gibberish
H bnddir('ACCRCV') dftactgrp(*no)
Fcustfile if e disk
Freports o e printer

Here's what happens when a non-RPG programmer tries to

make a change
H bnddir('ACCRCV')
Fcustfile if e disk
Freport o e printer
RNF0289E Entry contains data that is not valid; only valid data is used.
RNF2013E The Device entry is not PRINTER, DISK, SEQ, WORKSTN or SPECIAL;
defaults to DISK.
RNF2003E The File Type is not I, O, U, or C; defaults to O if File
Designation is blank, otherwise to I.
RNF2005E The Sequence entry is not blank, A, or D; defaults to blank.
... more error messages

© 2017 IBM Corporation

10
RPG is still not 100% free

There are still some areas where RPG is not yet free

 I specs and O specs must still be coded in fixed-form

• I and O specs are considered deprecated by many RPG programmers in
favor of externally-described files

 Code related to the RPG cycle must be coded in fixed-form

• The cycle is considered deprecated by many RPG programmers in favor of
using SQL for scenarios where the cycle formerly shone

© 2017 IBM Corporation

11
What does an all-free RPG mean?

 Fewer "secret codes" to remember ("E in column 19 means

externally-described")

 Indented code is more maintainable

 Better token-colorization in the RDI editor, allowing programmers to

have the same look-and-feel for RPG code as for other languages like
Java or PHP

 New programmers will only have to learn how to use RPG, without
having to struggle with how it is coded

© 2017 IBM Corporation

12
Removal of many frustrations

 /FREE and /END-FREE in every procedure

 Two lines for many definitions in fixed-form

D getNextCustomer...
D pr

vs
dcl-pr getNextCustomer;

 Insufficient room in D-spec keywords for long strings

D HSSFCellStyle c
D 'org.apache.poi.hssf.-
D usermodel.HSSFCellStyle'

vs
dcl-c HSSFCellStyle 'org.apache.poi.hssf.usermodel.HSSFCellStyle';

© 2017 IBM Corporation

13
More information

Documentation
- The ILE RPG Reference in the 7.2 and 7.3 Knowledge Center
has all the information about free-form. The free-form
information applies to both 7.1.

RPG Café wiki page with PTF information:

https://ibm.biz/rpgcafe_fullyfree_rpg

© 2017 IBM Corporation

14
Conversion

 RDI free-form conversion does not do any

conversion from H F D P to free-form.

 ARCAD has a product that converts H F D C and P

specs to fully-free-form.

 Linoma's conversion tool converts H F D C and P

specs to fully-free-form.

© 2017 IBM Corporation

15
The details

Let's look at the details

• General features
• Control (H)
• File declaration (F)
• Data declaration (D)
• Procedure (P)

© 2017 IBM Corporation

16
Some general features

The new statements all

• Start with an "opcode"

• End with a semicolon

Just like calculation statements in RPG:

if duedate > today;

sendAngryLetter (customer);
endif;

© 2017 IBM Corporation

17
Some general features

Unlike free-form calculations, can have /IF,

/ELSEIF, /ELSE, /ENDIF within a statement
dcl-s salary
/if defined(large_vals)
packed(13 : 3)
/else
packed(7 : 3)
/endif
;

© 2017 IBM Corporation

18
Some general features

Can mix fixed-form and free-form without /FREE

and /END-FREE

Example: Defining the TAG for SQL "whenever"

exec sql whenever sqlerror goto err;

...
return;
C err tag
ok = *off;
reportSqlError ();

© 2017 IBM Corporation

19
Control statements

CTL-OPT (Control Option) statement

• Start with CTL-OPT

• Zero or more keywords
• End with semicolon
ctl-opt option(*srcstmt : *nodebugio)
dftactgrp(*no);

© 2017 IBM Corporation

20
Control statements

• Can have multiple CTL-OPT statements

• The rules about not repeating keywords apply
across all statements

ctl-opt; // no keywords
ctl-opt option(*srcstmt : *nodebugio)
dftactgrp(*no); // two keywords
H datfmt(*iso) text('My Program')
ctl-opt alwnull(*usrctl); // free again

© 2017 IBM Corporation

21
Control statements

One little enhancement for free-form H:

If there is at least one free-form control statement,

you don't need DFTACTGRP(*NO) if you have
one of the ACTGRP, BNDDIR, or STGMDL
keywords

© 2017 IBM Corporation

22
File statements

DCL-F (Declare file) statement

• Start with DCL-F
• File name
• Keywords
• End with semicolon

© 2017 IBM Corporation

23
File statements

• Only full-procedural and output – no cycle, RAF or

table files

• The name can be longer than 10 as long as there's

an EXTFILE keyword (and an EXTDESC keyword
if externally-described)

dcl-f year_end_report printer

oflind(overflow)
extdesc('YERPT')
extfile(*extdesc);

© 2017 IBM Corporation

24
File statements – the device

Device keyword or LIKEFILE must be the first

keyword
DISK, PRINTER, SEQ, SPECIAL, WORKSTN
• Defaults to DISK

Externally-described: *EXT (default)

Program-described: record-length

dcl-f orders; // defaults to DISK(*EXT)

dcl-f qprint printer(132);
dcl-f screen workstn; // defaults to *EXT

© 2017 IBM Corporation

25
File statements – the usage

USAGE keyword
*INPUT, *OUTPUT, *UPDATE, *DELETE

Equivalent of fixed-form File Type (I, O, U, C) and

File-Addition

Default for USAGE depends on the device

dcl-f orders disk; // *INPUT

dcl-f report printer; // *OUTPUT
dcl-f screens workstn; // *INPUT : *OUTPUT

• SEQ and SPECIAL default to USAGE(*INPUT)

© 2017 IBM Corporation

26
File statements – the usage

Some usage values imply other values

*UPDATE implies *INPUT
*DELETE implies *UPDATE and *INPUT

// USAGE(*INPUT : *UPDATE)
dcl-f orders disk usage(*update);

// USAGE(*INPUT : *UPDATE : *DELETE)

dcl-f arrears disk usage(*delete);

Can specify implied values explicitly too

dcl-f orders disk usage(*update : *input);

© 2017 IBM Corporation

27
File statements – the usage

If you specify the USAGE keyword, the defaults are

not considered

// output only
dcl-f f1 disk usage(*output);

// input and output

dcl-f f2 disk usage(*input : *output);

© 2017 IBM Corporation

28
File statements – difference for *DELETE

In fixed form, U enables update and delete

In free form, *UPDATE does not enable delete

• *DELETE must be coded explicitly

© 2017 IBM Corporation

29
File statements – Keyed files

For externally-described files, KEYED keyword

dcl-f orders disk keyed;

For program-described files, KEYED(*CHAR:len)

dcl-f generic disk(2000) keyed(*CHAR:100);

© 2017 IBM Corporation

30
File statements – Program-described keyed files

Only character keys supported for program-

described

For other types, use a data structure

dcl-f generic disk(2000) keyed(*CHAR:7);

dcl-ds key len(7) qualified;

item_num packed(12);
end-ds;

key.item_num = 14;
chain key generic;

© 2017 IBM Corporation

31
File statements

F specs can be mixed with D specs (even in fixed

form)

Group related items together

dcl-f orders
usage (*update : *output) keyed;
dcl-ds orders_dsi
likerec (ordersR:*input);
dcl-ds orders_dso
likerec (ordersR:*output);
dcl-s num_orders int(10);

dcl-f report printer;

dcl-ds report_ds
likerec (reportR:*output);
© 2017 IBM Corporation
32
File statements

Named constants can be used for file keywords

dcl-c YEAR_END_RPT_FILE 'YERPT';

dcl-f year_end_report printer
oflind(overflow)
extdesc(YEAR_END_RPT_FILE)
extfile(*extdesc);
dcl-ds report_ds
extname(YEAR_END_RPT_FILE:*output);

© 2017 IBM Corporation

33
Data definition statements

• Start with DCL-x

• Item name – can be *N if not named
• Keywords
• End with semicolon

dcl-s name like(other_name);

© 2017 IBM Corporation

34
Standalone fields

The first keyword must be a data-type keyword.

dcl-s salary packed(9:2) inz(0);

If you are using the LIKE keyword, it doesn't have to

be first.

dcl-s annual_salary inz(0)

like(salary : +2);

© 2017 IBM Corporation

35
Data-type keywords

Some data-type keywords match the Data-Type

entry exactly
CHAR, INT, POINTER ...

Some merge the Data-Type entry with another

keyword
VARCHAR = A + VARYING
DATE = D + DATFMT
OBJECT = O + CLASS

© 2017 IBM Corporation

36
Data-type keywords – String data types

Fixed length:
• CHAR(characters)
• GRAPH(characters)
• UCS2(characters)

Varying length
• VARCHAR(characters)
• VARGRAPH(characters)
• VARUCS2(characters)

Varying length with specific prefix-size

• VARCHAR(characters : 4)
• VARGRAPH(characters : 4)
• VARUCS2(characters : 4)

Indicator
• IND

© 2017 IBM Corporation

37
Data-type keywords – Numeric data types

Decimal types with default zero decimal postions:

• PACKED(digits)
• ZONED(digits)
• BINDEC(digits) ("BINDEC" is explained on the next slide)

Decimal types with specific decimal positions

• PACKED(digits : decimals)
• ZONED(digits : decimals)
• BINDEC(digits : decimals)

Integer, unsigned, float

• INT(digits)
• UNS(digits)
• FLOAT(bytes)

© 2017 IBM Corporation

38
BINDEC keyword – reduce confusion over RPG's "binary" type

RPG's "binary" type is a decimal type stored in

binary form, not a "true binary".
D binfld S 9B 3
• Values between -999999.999 and 999999.999

RPG programmers see "binary" in API documention

and think they should code B in their RPG
programs

Non-RPG programmers see "binary" as the RPG

data type, and think it means true binary
• When they want an 4 byte binary, they code 4B
which is a 2-byte binary with 4 digits

© 2017 IBM Corporation

39
Other data types
Date, time, timestamp with default format
• DATE
• TIME
• TIMESTAMP

Date, time
• DATE(*YMD-)
• TIME(*HMS:)

Pointer and procedure pointer

• POINTER
• POINTER(*PROC)

Object
• OBJECT(*JAVA : CLASS) (parameters not needed for the prototype
of a constructor)
© 2017 IBM Corporation
40
Tip for remembering the data-type keywords

If there is a related built-in function, the data-type

keyword has the same name:

%CHAR - CHAR and VARCHAR

%GRAPH - GRAPH and VARGRAPH
%UCS2 - UCS2 and VARUCS2
%DATE - DATE
%TIME - TIME
%TIMESTAMP - TIMESTAMP
%INT - INT
%UNS - UNS
%FLOAT - FLOAT

Exception: %DEC. The decimal data types are

PACKED, ZONED, BINDEC.

© 2017 IBM Corporation

41
Data structures

Data-structures end the subfield list with END-DS

• not used for LIKEDS or LIKEREC data structures

END-DS is optionally followed by the DS name

dcl-ds info;
name varchar(25);
price packed(4 : 2);
end-ds info;

If no subfields, code END-DS on the DCL-DS line

dcl-ds prt_ds len(132) end-ds;

© 2017 IBM Corporation

42
Data structures

END-DS is not used if LIKEREC or LIKEDS is used

(because you can't code additional subfields)

dcl-ds info likeds(info_t);

dcl-ds custInDs likerec(custrec : *input);

END-DS is needed for an externally-described DS

dcl-ds custDs extname('CUSTFILE') end-ds;

© 2017 IBM Corporation

43
Subfields

Subfields officially start with the DCL-SUBF opcode

The opcode is optional unless the name is the same

as a free-form opcode

dcl-ds info;
name char(25);
dcl-subf select int(10);
end-ds info;

DCL-SUBF must be used because "select" is an

opcode supported in free-form

Same as the rule for EVAL and CALLP

name = 'Sally';
eval select = 5;

© 2017 IBM Corporation

44
Subfields

The POS keyword replaces

• From-and-to positions
• OVERLAY(dsname)
D info DS
D sub1 25 34A
D sub2 D OVERLAY(info:100)
D sub3 5P 2 OVERLAY(info)

dcl-ds info;
sub1 char(10) pos(25);
sub2 date pos(100);
sub3 packed(5 : 2) pos(1);
end-ds info;

© 2017 IBM Corporation

45
Subfields

Free-form OVERLAY only overlays subfields

• No free-form equivalent for OVERLAY(ds:*NEXT)
• OVERLAY(ds:*NEXT) means "after all previous subfields"
which is the same as not having the OVERLAY keyword at all
• SUB3 starts at position 101, after all previous subfields.
D info DS
D sub1 1 100A
D sub2 11 20A
D sub3 5A OVERLAY(info:*next)
Equivalent:
dcl-ds info;
sub1 char(100) pos(1); // 1-100
sub2 char(10) pos(11); // 11-20
sub3 char(5); // 101-105

© 2017 IBM Corporation

46
PSDS and INFDS

Use the PSDS keyword to define a program-status

data structure.
Use values like *STATUS to define the special PSDS
or INFDS subfields.

dcl-ds sds PSDS;

moduleStatus *STATUS;
end-ds;

dcl-f myfile INFDS(myfileInfds);

dcl-ds myfileInfds PSDS;

myfileStatus *STATUS;
end-ds;

© 2017 IBM Corporation

47
Prototypes and procedure interfaces

Prototypes and procedure interfaces are similar

Bonus feature:
dcl-pr qcmdexc extpgm;
EXTPGM parameter
cmd char(3000);
is optional
cmd_len packed(15 : 5);
end-pr;

dcl-pr init end-pr; // no parameters

dcl-pr init;
end-pr; // can be a separate statement

dcl-pi *n varchar(25); // name not needed

id int(10);
end-pi;

© 2017 IBM Corporation

48
*DCLCASE for external procedure names

A common bug:
 EXTPROC is needed for the mixed-case name
 The programmer uses copy-paste and forgets one change
D Qc3EncryptData...
D pr extproc('Qc3EncryptData')
D Qc3DecryptData...
D pr extproc('Qc3EncryptData')

Use *DCLCASE to avoid retyping the name:

dcl-pr Qc3EncryptData extproc(*dclcase);
dcl-pr Qc3DecryptData extproc(*dclcase);

 Less error prone when coding

 Easier for code reviewers to see that it's correct

© 2017 IBM Corporation

49
Parameters

Parameters officially start with DCL-PARM

DCL-PARM is optional. Same rule as for subfields

dcl-pr proc;
name char(25) const;
dcl-parm clear ind value;
end-pr;

© 2017 IBM Corporation

50
Procedure statements

Begin a procedure
• DCL-PROC
• Procedure name
• Keywords
• End with semicolon

dcl-proc myProc export;

End a procedure
• END-PROC
• Optional procedure name
• End with semicolon

end-proc myProc;
or
end-proc;
© 2017 IBM Corporation
51
Procedure example

dcl-proc getCurUser export;

dcl-pi *n char(10) end-pi;

dcl-s curUser char(10) inz(*user);

return curUser;
end-proc;

• The PI uses the place-holder *N for the name

• END-PI is specified as a keyword at the end of the
DCL-PI statement

© 2017 IBM Corporation

52
Can use named constants for keywords

dcl-c SYS_NAME_LEN 10;

dcl-ds sys_obj qualified;

obj char(SYS_NAME_LEN);
lib char(SYS_NAME_LEN);
end-ds;

© 2017 IBM Corporation

53
Can use named constants for keywords

In fixed form, some keywords allow literals to be specified

without quotes: DTAARA, EXTNAME, EXTFLD

What data area is used for fld1?

D fld1 S 10A DTAARA(dta1)

What about fld2?

D dta2 C 'MYLIB/DTAARA2'
D fld2 S 10A DTAARA(dta2)

© 2017 IBM Corporation

54
DTAARA keyword difference

In free-form, an unquoted name is always a variable or

named constant
D dta1 C 'MYLIB/DTAARA1'

D fld1a S 10A DTAARA(dta1)

*LIBL/DTA1
dcl-s fld1b char(10) dtaara('DTA1');

dcl-s fld1c char(10) dtaara(dta1); MYLIB/DTAARA1

D fld2a S 10A DTAARA(*VAR:nameFld)

Value of nameFld
dcl-s fld2b char(10) dtaara(nameFld);

© 2017 IBM Corporation

55
Gotchas

- Update does not imply delete

- END-DS, END-PR, END-PI needed at the end of a
subfield or parameter list (even when there are no
subfields or parameters)
- Keywords like DTAARA and EXTNAME that
assume unquoted names are named constants or
variables

(These have already been discussed)

© 2017 IBM Corporation

56
Another gotcha

If you are in the habit of using ellipsis at the end of D

and P spec names
P customerName...
P S 50A
That will not work for free-form declarations
dcl-s customerName...
char(50);
The name is customerNamechar, and "(50)" is found
where the compiler expects to find the data type.
dcl-s customerName
char(50);

© 2017 IBM Corporation

57
Colorization in RDI

Much more control for colorizing your code

Here is some code with the default colors

© 2017 IBM Corporation

58
Navigate to the color preferences

 Window > Preferences

 Search for ILE RPG
 Click on Parser Styles

© 2017 IBM Corporation

59
You can change the code to work with

 In the code section, I like to paste in a bit of my

own code at the top

© 2017 IBM Corporation

60
Choose which style you want to change

 Then click on the code you want to change the

color for
 The top section will automatically position to the
relevant style

© 2017 IBM Corporation

61
Customize your colors

 Choose the color you want

 It will automatically be colored in the code section
so you can see the effect it has

© 2017 IBM Corporation

62
Another way to choose the style

 For most free-form code, the styles are listed

together
 You can select them one-by-one, adjusting the
colors

© 2017 IBM Corporation

63
Here's how I like it

 The non-free-form styles I had to change were

Operation and Numeric

© 2017 IBM Corporation

64
Summary

We had two goals when designing the new

free-form syntax:
• Easy for non-RPG programmers to learn

• Easy for existing RPG programmers to learn

We have a few years of evidence that we

have indeed accomplished those goals!

© 2017 IBM Corporation

65
 www.ibm.com/software/rational

© Copyright IBM Corporation 2011. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any
kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor
shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the
use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates
and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to
future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the
International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

© 2017 IBM Corporation

66
 Special notices
This document was developed for IBM offerings in the United States as of the date of publication. IBM may not make these offerings available in
other countries, and the information is subject to change without notice. Consult your local IBM business contact for information on the IBM
offerings available in your area.
Information in this document concerning non-IBM products was obtained from the suppliers of these products or other public sources. Questions
on the capabilities of non-IBM products should be addressed to the suppliers of those products.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give
you any license to these patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY
10504-1785 USA.
All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives
only.
The information contained in this document has not been submitted to any formal IBM test and is provided "AS IS" with no warranties or
guarantees either expressed or implied.
All examples cited or described in this document are presented as illustrations of the manner in which some IBM products can be used and the
results that may be achieved. Actual environmental costs and performance characteristics will vary depending on individual client configurations
and conditions.
IBM Global Financing offerings are provided through IBM Credit Corporation in the United States and other IBM subsidiaries and divisions
worldwide to qualified commercial and government clients. Rates are based on a client's credit rating, financing terms, offering type, equipment
type and options, and may vary by country. Other restrictions may apply. Rates and offerings are subject to change, extension or withdrawal
without notice.
IBM is not responsible for printing errors in this document that result in pricing or information inaccuracies.
All prices shown are IBM's United States suggested list prices and are subject to change without notice; reseller prices may vary.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
Any performance data contained in this document was determined in a controlled environment. Actual results may vary significantly and are
dependent on many factors including system hardware configuration and software design and configuration. Some measurements quoted in this
document may have been made on development-level systems. There is no guarantee these measurements will be the same on generally-
available systems. Some measurements quoted in this document may have been estimated through extrapolation. Users of this document
should verify the applicable data for their specific environment.

Revised September 26, 2006

© 2017 IBM Corporation

67
Special notices (cont.)
IBM, the IBM logo, ibm.com AIX, AIX (logo), AIX 5L, AIX 6 (logo), AS/400, BladeCenter, Blue Gene, ClusterProven, DB2, ESCON, i5/OS, i5/OS (logo), IBM Business
Partner (logo), IntelliStation, LoadLeveler, Lotus, Lotus Notes, Notes, Operating System/400, OS/400, PartnerLink, PartnerWorld, PowerPC, pSeries, Rational, RISC
System/6000, RS/6000, THINK, Tivoli, Tivoli (logo), Tivoli Management Environment, WebSphere, xSeries, z/OS, zSeries, Active Memory, Balanced Warehouse,
CacheFlow, Cool Blue, IBM Systems Director VMControl, pureScale, TurboCore, Chiphopper, Cloudscape, DB2 Universal Database, DS4000, DS6000, DS8000,
EnergyScale, Enterprise Workload Manager, General Parallel File System, , GPFS, HACMP, HACMP/6000, HASM, IBM Systems Director Active Energy Manager,
iSeries, Micro-Partitioning, POWER, PowerExecutive, PowerVM, PowerVM (logo), PowerHA, Power Architecture, Power Everywhere, Power Family, POWER Hypervisor,
Power Systems, Power Systems (logo), Power Systems Software, Power Systems Software (logo), POWER2, POWER3, POWER4, POWER4+, POWER5, POWER5+,
POWER6, POWER6+, POWER7, System i, System p, System p5, System Storage, System z, TME 10, Workload Partitions Manager and X-Architecture are trademarks
or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are
marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. 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 full list of U.S. trademarks owned by IBM may be found at: http://www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or
other countries.
AltiVec is a trademark of Freescale Semiconductor, Inc.
AMD Opteron is a trademark of Advanced Micro Devices, Inc.
InfiniBand, InfiniBand Trade Association and the InfiniBand design marks are trademarks and/or service marks of the InfiniBand Trade Association.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered
trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries or both.
Microsoft, Windows and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries or both.
NetBench is a registered trademark of Ziff Davis Media in the United States, other countries or both.
SPECint, SPECfp, SPECjbb, SPECweb, SPECjAppServer, SPEC OMP, SPECviewperf, SPECapc, SPEChpc, SPECjvm, SPECmail, SPECimap and SPECsfs are
trademarks of the Standard Performance Evaluation Corp (SPEC).
The Power Architecture and Power.org wordmarks and the Power and Power.org logos and related marks are trademarks and service marks licensed by Power.org.
TPC-C and TPC-H are trademarks of the Transaction Performance Processing Council (TPPC).
UNIX is a registered trademark of The Open Group in the United States, other countries or both.

Other company, product and service names may be trademarks or service marks of others.
Revised December 2, 2010

© 2017 IBM Corporation

68