Enterprise PL/I for z/OS编程指南

需积分: 9 107 浏览量更新于2024-08-02 收藏 5.62MB PDF 举报

"《PLI编程指南》是IBM发布的一本针对z/OS操作系统的Enterprise PL/I编程指南，版本为3 Release 8，出版日期为2008年10月。这本书适用于5655-H31产品级别及其后续版本。IBM建议用户确保使用与所用产品级别相匹配的正确版本的指南。该指南可通过IBM代表或当地IBM分支办公室订购，不在此地址库存。读者可以书后提供的表格提供反馈，若表格丢失，可以直接将评论发送至IBM公司指定地址。当用户向IBM提供信息时，即授予IBM非独家使用权，IBM可自由使用或分发这些信息，而无需对用户提供任何义务。该指南的版权归属于IBM公司，始于1999年，更新至2008年，特别适用于美国政府用户。" 在《PLI编程指南》中，你可以找到关于Enterprise PL/I编程的详细知识。PL/I，全称为Procedure Language/Interactive，是一种高级过程编程语言，专为IBM大型机系统如z/OS设计。这个版本的编程指南为第十版，涵盖了如何使用Enterprise PL/I进行系统开发、程序设计和优化的各种主题。 1. **基础概念**：指南会介绍PL/I语言的基本元素，包括变量声明、数据类型、控制结构（如循环和条件语句）、函数和过程等。 2. **输入/输出操作**：PL/I支持多种I/O操作，如文件处理、系统调用和设备交互，指南会详细阐述如何在程序中实现这些操作。 3. **并发与多线程**：由于z/OS是多任务操作系统，指南会涉及如何在PL/I程序中实现并发处理，包括进程控制和同步机制。 4. **错误处理和调试**：书中会讲解PL/I的异常处理机制以及如何调试代码，帮助开发者诊断和修复问题。 5. **内存管理**：PL/I的内存模型和动态内存分配方法也会被详细讨论，帮助程序员有效地管理程序资源。 6. **性能优化**：针对z/OS平台，指南可能会提供一些优化代码执行速度和降低系统资源消耗的策略。 7. **与操作系统集成**：由于是为z/OS设计，指南将涵盖如何利用PL/I与操作系统接口，调用系统服务，进行系统编程。 8. **最佳实践和案例研究**：书中可能包含实际编程中的最佳实践，以及真实场景的案例分析，帮助开发者理解PL/I在实际工作中的应用。 9. **版本更新**：由于指南提及了3 Release 8之后的后续版本，因此可能还会涉及新特性、改动和向后兼容性问题。 10. **文档更新与支持**：IBM通常会通过技术新闻简报提供最新版本的信息，指南中可能会指导用户如何获取这些更新和支持。《PLI编程指南》是学习和精通Enterprise PL/I编程的宝贵资源，对于在z/OS环境下工作的开发者来说，是不可或缺的参考资料。

The following tables show you how to use the publications you receive with

Enterprise PL/I and Language Environment. You’ll want to know information

about both your compiler and run-time environment. For the complete titles and

order numbers of these and other related publications, see “Bibliography” on page

473.

PL/I information

Table 1. How to use Enterprise PL/I publications

To... Use...

Evaluate Enterprise PL/I Fact Sheet

Understand warranty information Licensed Programming Specifications

Plan for and install Enterprise PL/I Enterprise PL/I Program Directory

Understand compiler and run-time changes and

adapt programs to Enterprise PL/I and Language

Environment

Compiler and Run-Time Migration Guide

Prepare and test your programs and get details on

compiler options

Programming Guide

Get details on PL/I syntax and specifications of

language elements

Language Reference

Diagnose compiler problems and report them to

IBM

Diagnosis Guide

Get details on compile-time messages Compile-Time Messages and Codes

Language Environment information

Table 2. How to use z/OS Language Environment publications

To... Use...

Evaluate Language Environment Concepts Guide

Plan for Language Environment Concepts Guide

Run-Time Application Migration Guide

Install Language Environment on z/OS z/OS Program Directory

Customize Language Environment on z/OS Customization

Understand Language Environment program

models and concepts

Concepts Guide

Programming Guide

Find syntax for Language Environment run-time

options and callable services

Programming Reference

Develop applications that run with Language

Environment

Programming Guide and your language

Programming Guide

Debug applications that run with Language

Environment, get details on run-time messages,

diagnose problems with Language Environment

Debugging Guide and Run-Time Messages

Develop interlanguage communication (ILC)

applications

Writing Interlanguage Applications

Migrate applications to Language Environment Run-Time Application Migration Guide and the

migration guide for each Language

Environment-enabled language

Notation conventions used in this book

This book uses the conventions, diagramming techniques, and notation described

in “Conventions used” on page xv and “How to read the notational symbols” on

page xvii to illustrate PL/I and non-PL/I programming syntax.

xiv Enterprise PL/I for z/OS Programming Guide

Conventions used

Some of the programming syntax in this book uses type fonts to denote different

elements:

v Items shown in UPPERCASE letters indicate key elements that must be typed

exactly as shown.

v Items shown in lowercase letters indicate user-supplied variables for which you

must substitute appropriate names or values. The variables begin with a letter

and can include hyphens, numbers, or the underscore character (_).

v The term digit indicates that a digit (0 through 9) should be substituted.

v The term do-group indicates that a do-group should be substituted.

v Underlined items indicate default options.

v Examples are shown in monocase type.

v Unless otherwise indicated, separate repeatable items from each other by one or

more blanks.

Note:

Any symbols shown that are not purely notational, as described in “How to

read the notational symbols” on page xvii, are part of the programming

syntax itself.

For an example of programming syntax that follows these conventions, see

“Example of notation” on page xviii.

How to read the syntax notation

The following rules apply to the syntax diagrams used in this book:

Arrow symbols

Read the syntax diagrams from left to right, from top to bottom, following

the path of the line.

─── Indicates the beginning of a statement.

─── Indicates that the statement syntax is continued on the next line.

─── Indicates that a statement is continued from the previous line.

─── Indicates the end of a statement.

Diagrams

of syntactical units other than complete statements start with the

─── symbol and end with the ─── symbol.

Conventions

v Keywords, their allowable synonyms, and reserved parameters, appear

in uppercase for MVS and OS/2

platforms, and lowercase for UNIX

platforms. These items must be entered exactly as shown.

v Variables appear in lowercase italics (for example, column-name). They

represent user-defined parameters or suboptions.

v When entering commands, separate parameters and keywords by at

least one blank if there is no intervening punctuation.

v Enter punctuation marks (slashes, commas, periods, parentheses,

quotation marks, equal signs) and numbers exactly as given.

v Footnotes are shown by a number in parentheses, for example, (1).

v A  symbol indicates one blank position.

Required

items

Required items appear on the horizontal line (the main path).

Introduction xv

v Items separated by a single vertical bar, |, are alternative items. You can select

only one of the group of items separated by single vertical bars. (Double vertical

bars, ||, specify a concatenation operation, not alternative items. See the PL/I

Language Reference for more information on double vertical bars.)

v Anything enclosed in brackets, [ ], is optional. If the items are vertically stacked

within the brackets, you can specify only one item.

v An ellipsis, ..., indicates that multiple entries of the type immediately preceding

the ellipsis are allowed.

Example of notation

The following example of PL/I syntax illustrates the notational symbols described

In “How to read the notational symbols” on page xvii:

DCL file-reference FILE STREAM

{INPUT | OUTPUT [PRINT]}

ENVIRONMENT(option ...);

Interpret this example as follows:

v You must spell and enter the first line as shown, except for file-reference, for

which you must substitute the name of the file you are referencing.

v In the second line, you can specify INPUT or OUTPUT, but not both. If you

specify OUTPUT, you can optionally specify PRINT as well. If you do not

specify either alternative, INPUT takes effect by default.

v You must enter and spell the last line as shown (including the parentheses and

semicolon), except for option ..., for which you must substitute one or more

options separated from each other by one or more blanks.

Enhancements in this release

This release provides the following functional enhancements described in this and

the other IBM PL/I books.

Performance improvements

v The ARCH(8) and TUNE(8) options provide exploitation of the z/HE

instructions.

v The HGPR option supports using 64-bit registers in 32-bit code.

v The GOFF option supports generation of GOFF objects.

v The PFPO instruction will be exploited in conversions between differing float

formats.

v SRSTU will be used in code generated for UTF-16 INDEX.

v MVCLE will be used in code generated for the LEFT built-in function.

v Calls to null internal procedures will now be completely removed.

Usability enhancements

v PLISAXC provides for access to the XML System Services parser via a SAX

interface.

v The INCDIR option is supported under batch.

v The LISTVIEW option now provides the support previously provided by the

AFTERMACRO etc suboptions of TEST.

v The NOLAXENTRY suboption of the RULES option allows for the flagging of

unprototyped ENTRYs.

xviii Enterprise PL/I for z/OS Programming Guide

剩余535页未读，继续阅读

seansunwork

粉丝: 0
资源: 15

Enterprise PL/I for z/OS编程指南

PLI Programming Guide(OS390).

IBM PL1语言编程指导（Enterprise PLI for zOS Programming Guide.pdf）

verilog的pli

vcs的pli故障注入

vcs+user+guide+2018 pdf

Verilog PLI

verdi pli.a 什么文件

在使用 +loadpli1 选项时，如何指定 PLI 程序的名称和路径

pli认知能力测试题库

verilog PLI

最新资源