Are you looking for PL/I documentation across different releases? Do you want to access PL/I documentation of both the HTML and PDF format?
The PL/I library pages now provide the following types of PL/I documentation in one central location:
HTML documentation URL
Start visiting the following PL/I library pages:
Peter Elderon from the IBM compiler development team will be presenting on what's new in Enterprise PL/I for z/OS at SHARE in Anaheim, March 9 to 14.
15284: PL/I - What's New
Register for SHARE in Anaheim today!
Check out all the information about the latest release of Enterprise PL/I for z/OS. You can get a summary of the release as well as all the announcement details.
See what's new with Enterprise PL/I for z/OS, V4.4 including enhancements to leverage the latest z/OS. For all the details about the Enterprise PL/I for z/OS, V4.4 announcement, see here.
Modified on by Crystal4545
ALLOCATE is a storage control built-in function, which allocates storage of the specified size in the heap. You can also use ALLOCATE to allocate the specified size in the specified area.
When you specify ALLOCATE(n), ALLOCATE allocates storage of size n in heap storage and returns the pointer to the allocated storage. If necessary, n is converted to REAL FIXED BINARY(31,0). If the requested amount of storage is not available, the STORAGE condition is raised.
The ALLOCATE built-in function now has the AREA reference as a new optional argument. When you specify ALLOCATE(n, x), the specified number of bytes n is allocated within that area. The number is rounded up to a multiple of 8. If there is insufficient space within the specified area, the AREA condition is
For more information, see Built-in functions, pseudovariables, and subroutines.
Modified on by Crystal4545
The PL/I workstation compiler supports the following interfaces to other products:
1. Using the sort program
The compiler provides an interface called PLISRTx (x = A, B, C, or D) that allows you to make use of the IBM-supplied Sort programs. To use the Sort program you must include the correct PL/I statements in your source program and specify the correct data sets in your JCL.
2. Interlanguage Communication between PL/I and C
The Interlanguage Communication (ILC) between PL/I and C is supported. You can write PL/I code that either calls or is called by C.
3. Interfacing with Java
The Java Native Interface (JNI) is the Java interface to native programming languages and is part of the Java Development Kits. By writing programs that use
the JNI, you ensure that your code is portable across many platforms. The JNI allows Java code that runs within a Java Virtual Machine (JVM) to operate
with applications and libraries written in other languages, such as PL/I. In addition, the Invocation API allows you to embed a Java Virtual Machine into your
native PL/I applications.
For more information, see "Using interfaces to other products".
Today, IBM announced Enterprise PL/I for z/OS V4.4 and z/OS XL C/C++ 2.1.
At SHARE in Boston, being held August 11-16, Visda Vokshoori , from the IBM compiler development team, will present the following sessions about these latest PL/I and C/C++ compilers for z/OS.
Session 13789: What's New in Enterprise PL/I and C/C++ will discuss all of the new features of the new compiler versions.
Enterprise PL/I for z/OS 4.4 features discussed will include:
Improved performance of PL/I applications
Improved exploitation of zEC12 and zBC12 hardware
New optimization features (e.g. improve code for UTF-16; improve code generation for Decimal-Floating-Point Zoned-Conversion Facility…)
4X improvement in listing generation time
Improved Middleware support
Better error messages when compiling SQL programs
New features to support IMS
Sparse arrays, XML cleaning and normalization; base 64 encoding/decoding
Significantly reduced size of IMS convertor, allowing more convertors to run in same addressing space
Support for the latest IBM Middleware: CICS, DB2 and IMS
UTF 16 PICTURE support
New program diagnostics features
Increase programmer productivity and application modernization
Session 13790: Make Your PL/I and C/C++ Code Fly With the Right Compiler Options will discuss how to best leverage the compiler options available to you in order to generate the best performing code. The session will answer questions such as:
· What does ARCH(n)/TUNE(n) do for/to my compiled code?
· What can HGPR, FLOAT( AFP ), COMPACT do to improve the code generated by the compiler?
· What coding techniques can benefit from higher arch levels?
· What happens to my code when I turn optimization on?
· What optimization level can get me the sweet spot between compile time and run time performance?
· What other options can affect application performance?
Register for SHARE in Boston here!
Enterprise PL/I for z/OS has consistently delivered innovations to help developers maintain and create applications optimized for deployment on IBM System z servers. Like COBOL, PL/I also focuses on delivering new features to improve performance, productivity, and modernization of proven, business critical applications. IBM has delivered a new release of the PL/I compiler every year since 1999 on System z. The announcement of Enterprise PL/I for z/OS V4.4 has kept this streak alive and reaffirms IBM's commitment to PL/I on System z.
Enterprise PL/I for z/OS V4.4 fully exploits System z architecture, including the latest zEC12 and zBC12 servers. It also supports the new z/OS V2.1 operation environment. With this latest release, you can take advantage of new optimization features to improve application performance and reduce operating cost. You will also notice a 4X improvement in listing generation time, and improved program diagnostics, especially for programs that work with SQL. If you are an IMS user, you will be able to take advantage of new features to improve performance (e.g. Sparse arrays, XML cleaning and normalization; base 64 encoding and decoding). The size of the IMS convertor has also been significantly reduced, allowing more convertors to run in the same addressing space.
Enterprise PL/I for z/OS V4.4 is scheduled to GA on Sept. 6, 2013. For more information, visit http://www-03.ibm.com/software/products/us/en/plizos
At times, it is useful to be able to tailor the compiler to meet the needs of your organization. For example, you might want to suppress certain messages or alter the severity of others. You might want to perform a specific function with each compilation, such as logging statistical information about the compilation into a file.
A compiler user exit handles this type of functions. With PL/I, you can write your own user exit or use the exit provided with the product, either 'as is' or slightly modified depending on what you want to do with it.
IBM supplies you with the sample compiler user exit, IBMUEXIT, which filters messages for you. It monitors messages and, based on the message number that you specify, suppresses the message or changes the severity of the message.
There are several files that comprise IBMUEXIT:
Contains the PL/I source code.
Executable load module for IBMUEXIT.PLI that can be FETCHed. In order to build this file, issue the following commands from the AIX command line:
pli -e ibmuexit
Control file that specifies filtering of messages.
The PLI source file is provided for your information and modification. The INF control file contains the message numbers that should be monitored, and tells IBMUEXIT what actions to take for them. The executable module reads the INF control file, and either ignores the message or changes its severity.
Author: Carol Hu
Check out all
the information about the latest release of Enterprise PL/I for z/OS.
You can get a summary of the release as well as all the announcement
See what's new with Enterprise PL/I for z/OS, V4.3 including enhancements to
leverage the latest z/OS. For all the details about the Enterprise
PL/I for z/OS, V4.3 announcement, see IBM Enterprise PL/I for z/OS V4.3 delivers performance improvements and usability enhancements. (Author: Stella Zhou, Carol Hu)
Interested in finding
out what PL/I support is available for the latest IBM zEnterprise® EC12
I recommend the following article published in IBMSystems magazine's latest
Mainframe Extra eNewsletter:
Hope you'll find it useful.
PL/I Compilers are now live on the Request for Enhancement (RFE)
Community. It is a great place where you can collaborate with
development teams and other product users. Our development team will
review your RFE and provide status updates throughout its lifecycle.
Here is links to the Community : PL/I RFE
Looking forward to hearing from you.
Check out this demo showing how to code PL/I to interface with AIX. Using the Power systems sandbox, you can try PL/I for AIX and create a network application in PL/I.
In the previous blog entry we showed how Character Large Objects (CLOBs)
can be manipulated with LOB locators. In this blog we will discuss
the use of LOB file references.
LOB file reference variables are also very useful when working with
LOBs. The are used to import or export data between a LOB column and
an external file outside the DB2 system.
The benefits of using LOB file reference variables are that they:
- use less CPU time than moving LOB data with a host variable
because the movement of the data would not be overlapped with
any DB2 processing or network transfer time.
- use less application storage because the LOB data is moved
directly from DB2 to a file and is not materialized in the
The pliclob sample program uses LOB file references to
create a new, trimmed down version of the resume in an external file.
In the pliclob sample program the host variable hv_clob_file is
declared as a LOB file reference.
The file name field of the LOB file reference is set to the fully
qualified file name and the file name length is set to its length.
For this example the 'overwrite' flag is set so any existing file
will be overwritten. These and other options are described fully
in the DB2 publication 'Application programming for SQL'.
Next the SQL VALUES statement is used to concatenate the resume name
and work history sections of the resume directly into the LOB file
You can see this in the following code sample, extracted from the
pliclob sample program.
dcl hv_clob_file sql type is clob_file;
name_string = '/SYSTEM/tmp/pliclob2.txt';
hv_clob_file.sql_lob_file_name_len = length(name_string);
hv_clob_file.sql_lob_file_name = name_string;
hv_clob_file.sql_lob_file_options = ior(sql_file_overwrite);
values ( substr(:hv_loc_resume,:start_resume,
Now go and have some LOB fun yourself!
To see all of these techniques in context, please
refer to the pliclob sample program.
This blog entry is the first of two articles that will provide some guidance on how to work
with DB2 large objects (LOBs) in PL/I. They both refer to the 'pliclob.pli' file in the PL/I Cafe 'Files'
section for samples of actual code.
One way to use LOB data from a DB2 table is to declare a host variable
large enough to hold all of the LOB data. This requires your program to
allocate large amounts of storage and requires DB2 to move large amounts
of data. This can be inefficient or impractical.
Or you can use LOB locators and LOB file references to manipulate the data
while it still resides in the data base.
LOB Locators are used to avoid materialization of the LOB data and all
the underlying requirements associated with it.
The benefits of using LOB locators are:
- saving storage when manipulating LOBs with LOB locators
- manipulating data without retrieving it from the data base
- avoiding the use of large amounts of storage to hold the LOB
- avoiding the time and resource expenditures for moving large
pieces of data thereby improving performance.
LOB locators are especially useful:
- when you only need a small part of a LOB
- when you don't have enough memory for the entire LOB
- when performance is important
- in a client/server environment to avoid moving data over the
network from one system to another
Look at the pliclob sample program in the 'Files' section of the
PL/I Cafe for some ideas on how to manipulate CLOBs in a PL/I and
For example, the pliclob sample program uses LOB locators to identify
and manipulate sections of the character large object (CLOB) resume
found in the DB2 V10 table dsn8a10.emp_photo_resume.
In the following code sample, extracted from the pliclob sample program,
the LOB locator 'hv_loc_resume' is set to the location of the resume of
the employee number 'hv_empno' in the emp_photo_resume table. Next the
start_resume host variable is set to the beginning of the 'Resume:'
section of the resume.
dcl hv_loc_resume sql type is clob_locator;
select resume into :hv_loc_resume
where empno = :hv_empno;
set :start_resume = (posstr(:hv_loc_resume, 'Resume:'));
From here it is possible to start manipulating the resume data while
the resume is still resident in the data base. For greater detail,
refer to the pliclob sample program.
Join our experts, Ray Jones, Vice President, IBM System z® Software, and Kevin Stoodley, IBM Fellow and CTO for Enterprise Modernization Tools, Compilers and Security, to learn how IBM’s latest compilers, middleware and tools can help you stay on the technology curve. In this complimentary webcast, Ray and Kevin will discuss best practices and approaches to plan and execute a successful compiler migration, alongside CICS®, IMS™ and DB2® upgrades. They will also go over IBM’s strategy for compilers and tools on System z to help you better plan your overall development and upgrade efforts.
Register online right now
Register now for this webcast by logging onto
Join us after the webcast for a live question-and-answer session. The webcast will also be available for replay after the event.