V11.

cover

Front cover
Course Guide
Advanced System Operator Workshop
for IBM i
Course code AS27G   ERC 10.0
November 2016 edition
Notices
This information was developed for products and services offered in the US.
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, MD-NC119
Armonk, NY 10504-1785
United States of America
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 jurisdictions 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 provide in any way it believes appropriate without incurring any obligation to you.
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
actual people or business enterprises is entirely coincidental.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.
© Copyright International Business Machines Corporation 2001, 2016.
This document may not be reproduced in whole or in part without the prior written permission of IBM.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
V11.0
Contents

TOC

Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Course description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Unit 1. LPAR concepts and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
IBM Power Systems family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Virtualization technologies on Power Systems with IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
IBM PowerVM editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
IBM PowerVM features by Power8 systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
What is a partition? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Logical partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Partition characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Partition resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Logical partition resource example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
The big picture: Dynamic partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Dynamic partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Virtual I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Smarter IOAs (IOP-less) direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
LPAR summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Benefits of using partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
LPAR education . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

Unit 2. Console options and HMC overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Power with IBM i console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
HMC introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
IBM Systems hierarchy of management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
HMC and managed system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Managed system without HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Managed system without HMC different options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Power Systems management: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
HMC features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
HMC options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Available HMC model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
HMC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Capacity on demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
HMC education . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Unit 3. Basic management using HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Topic 1: Dynamic logical partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

© Copyright IBM Corp. 2001, 2016 iii

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Partition profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Processing and Memory settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
I/O adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Dynamic partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Dynamic partitioning: Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Dynamic partitioning: Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Dynamic partitioning: Physical Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Dynamic partitioning: Virtual Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Create Virtual Adapter: Ethernet Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Virtual Ethernet Adapter: General and Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Work with Communications Resources display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Topic 2: Additional useful functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Serviceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Operations: Power Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Operations: Power On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Managed system states (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Managed system states (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Topic 3: Managed server partition tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Partition task selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Partition tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Operations: Activate (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Operations: Activate (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Unit 4. IBM i Access Family overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Topic 1: Overview of IBM i Access Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
IBM i Access Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
IBM i Access for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
IBM i Access for Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Topic 2: Overview of IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
IBM Navigator for i window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
IBM Navigator for i main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Topic 3: Using IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Platform independent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Download Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Unzip the download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Run the startup program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Define the target IBM i (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Define the target IBM i (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Use Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Topic 4: Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
IBM i Access Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
A smart way to modernize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Unit 5. IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
IBM i Access Client Solutions deployment (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
IBM i Access Client Solutions deployment (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Main user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

© Copyright IBM Corp. 2001, 2016 iv

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC System Configurations (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

System Configurations (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Console configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5250 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Virtual Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Database Run SQL Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Database SQL Performance Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5250 Emulation (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
5250 Emulation (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5250 Emulation (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
5250 Session Manager (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5250 Session Manager (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Actions: Download, View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Printer Output View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Preferences: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Preferences: Local Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Preferences: Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Preferences: Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
HMC Probe Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Exercise: Print output using IBM i Access Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39

Unit 6. Security concepts and overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
The objectives of system security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Physical security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Monitoring physical security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
System tools used to secure your system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Security is always active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Review questions (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Review answers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Review questions (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Review answers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

Unit 7. System values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Security components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Topic 1: Security level system value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
QSECURITY system value: Security level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Security level 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
The comparison of the functions supported by the different levels of security . . . . . . . . . . . . . . . . . . 7-7
Locking system values using service tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Topic 2: Configure security using 5250 emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Individual system values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
System value categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Allocation category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Topic 3: Configure security using IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Configuration and Service: System Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

© Copyright IBM Corp. 2001, 2016 v

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Security category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

Date and Time category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Password rules for changing password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

Unit 8. User security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Security components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Topic 1: User profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Roles served by user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
User profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Appendix B: Default values for user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Create a new user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
New User: Capabilities > Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
System privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Privilege classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Capabilities: Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Capabilities: Password and Unique Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Capabilities: UID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
New User: Jobs > General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Jobs > Session Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Jobs > Display Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Display Session: Limit capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Jobs > Output and International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
New User: Groups > Group Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
New User: Personal > Name, Location, and Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Appendix B: IBM-supplied user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
User functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32
Changing a user profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
Deleting a user profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
Exercise: Create a user profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
Topic 2: Group profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36
Roles served by group profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37
More facts about group profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
New Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
New Group > Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40
New Group > Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41
Group functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42
Deleting a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43
Review questions (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45
Review answers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46
Review questions (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-47
Review answers (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-49

Unit 9. Resource security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Security components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Topic 1: Resource security concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
User-owned objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Primary group authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
QDFTOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

© Copyright IBM Corp. 2001, 2016 vi

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Where object permissions come from . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Where *PUBLIC authority comes from . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Object management authority (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Object management authority (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Object data authority (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Object data authority (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Object exclude authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Commonly used permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Integrated file system authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Building authority checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Topic 2: Defining resource security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Object permission: QSYS.LIB file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Basic and Details permission displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Permission: Add / Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Permission: Customize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Permission: Authorization List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
Change owner: Change primary group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Topic 3: Column-level authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Column-level security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
Granting column-level permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Column-level security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
Security - Separation of duties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
What is RCAC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
IBM Advanced Data Security for i (Boss Option 47) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Row permissions - 5250 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
Row permissions - IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
Column Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
Column Mask - IBM Navigator for i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
Exercise: Resource security and group profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40

Unit 10. Authorization lists and adopted authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Topic 1: Authorization lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
What is an authorization list? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Authorization list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Create an authorization list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Authorization list permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Object secured by an authorization list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Securing an object with an authorization list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Authorization list considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Authorization list versus group profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Groups and AUTLs compared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Building authority checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Exercise: Authorization lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Topic 2: Adopted authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Adopted authority (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Adopted authority (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Authority checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Exercise: Adopted authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22

© Copyright IBM Corp. 2001, 2016 vii

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Unit 11. Work management: Concepts and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
IBM i advanced application architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
IBM i functional components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Performance checklist: Work management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
Overview of work management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Storage management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Input, process, and output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
IBM i view: Job initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Performance tuning (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Performance tuning (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Work management objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17

Unit 12. Work management: Subsystem concepts and overview . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Topic 1: Subsystem concepts and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Subsystems (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Subsystems (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Subsystem description (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Subsystem description (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Work entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Routing entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Class information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Start subsystem (STRSBS QINTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Default subsystem configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
Topic 2: Memory pool concepts and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20
An overview of memory pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
The shared pool subtypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Why pools? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23
Main storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Storage pool characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
Specifying which pools are assigned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
Storage pool allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
Topic 3: Working with subsystems and memory pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29
Display Subsystem Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30
QINTER subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
Work with System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-33
WRKSYSSTS: Pool data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34
WRKSHRPOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-35
IBM Navigator for i: Active Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-36
IBM Navigator for i: Shared Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
Shared Pools: Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-38
General and Configuration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39
Performance and Tuning tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-40
IBM Navigator for i: WRKSYSSTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-42
General and Jobs tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43
Processors and Memory tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-44
Disk Space and Addresses tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-46
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-48
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-49
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-50

© Copyright IBM Corp. 2001, 2016 viii

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Unit 13. Work management: Job processing concepts and interactive jobs . . . . . . . . . . . . . . . 13-1
Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Topic 1: Job processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Where work is processed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Types of jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Start / End of a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Interactive job: User view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Interactive job: Programmer view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Identify the types of jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Topic 2: Interactive jobs and job tuning concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Interactive job routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
Selecting initial program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
Work management: Interactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
Pool sizes and paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Pool benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
How objects are stored on disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
How do faults affect performance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
DB versus non-DB page faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
Active Pools: Page faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21
Paging (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Paging (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
Paging of interactive jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
How does paging affect performance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
How to ensure the system has enough memory? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Pool activity level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27
IBM i activity levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28
Active Pools: Activity level/transition data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33

Unit 14. Work management: Job processing concepts of other job types. . . . . . . . . . . . . . . . . 14-1
Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Topic 1: Batch jobs and job tuning concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Batch jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Job selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Batch job routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Batch tuning: A pool for batch jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Performance runtime attributes: Timeslice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Performance runtime attributes: Run priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10
Multiple types of batch jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11
Topic 2: QSPL subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12
STRSBS QSPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Topic 3: Autostart jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Autostart jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
Topic 4: Communication jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Communication jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18
Topic 5: Prestart jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
Prestart jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21
Work management objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23
Performance tuning education . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-25
Review questions (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-27
Review answers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-28
Review questions (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-29
Review answers (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-30

© Copyright IBM Corp. 2001, 2016 ix

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-31

Unit 15. Work management: Submitting and tracking of batch jobs. . . . . . . . . . . . . . . . . . . . . . 15-1
Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Putting a job on a job queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Submitting a batch job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
Job message queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Scheduling a batch job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Putting jobs on a job queue: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Tracking jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Spooling intercept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
Printer device file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Printer and output queue defaults (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
Printer and output queue defaults (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15
Spool writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
Spooling summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-19
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20
Exercise: Work management: Job and subsystem management . . . . . . . . . . . . . . . . . . . . . . . . . . 15-21
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-22

Unit 16. Programming concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
The manual process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
The automated process: CL program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
What is a program? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Steps involved in creating a program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
What is needed to create a program? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Process for creating a CL program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12

Unit 17. CL programming concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
CL programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Commands allowed in CL programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Some familiar CL programming commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
CL commands allowed only in CL programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Command format in a CL program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Coding rules for CL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Additional coding rules for CL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
Example of coding rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
The structure of a CL program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
Declare CL variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
DCL examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
What is the purpose of SNDUSRMSG? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
SNDUSRMSG parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
SNDUSRMSG example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Using SNDUSRMSG in CL program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
GOTO and labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
If-Then ELSE (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-23
If-Then Else (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24
Relational and logical expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25
DO / ENDDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26

© Copyright IBM Corp. 2001, 2016 x

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Command prompting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-27

Selective command prompting (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29
Selective command prompting (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-30
Whoops! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-31
MONMSG example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-32
MONMSG: Monitoring for range of messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-33
Example: Control work flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-34
Example: Communicating with user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-35
Create a CL program using PDM and SEU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-36
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-37
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-38
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-39

Unit 18. CL programming using PDM and SEU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Programming Development Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
Specify source file and library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Work with Members screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Specify member name and type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Specify member entries and prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Specify entries and exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
Select compile options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Reference materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
IBM Knowledge Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
Programming education (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Programming education (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
Review questions (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-15
Review answers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16
Review questions (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
Review answers (2of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
Exercise: CL programming using PDM and SEU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20

Unit 19. Creating a menu using SDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
SDA features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Screen Design Aid menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Design Menus display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Specify Menu Functions display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Define menu image work screen (1 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Define menu image work screen (2 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Define menu image work screen (3 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Define menu image work screen (4 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
Define menu image work screen (5 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-11
Define menu image work screen (6 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Define menu image work screen (7 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
Define menu image work screen (8 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16
Define menu image work screen (9 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17
Define menu image work screen (10 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18
F10: Prompt for commands (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20
F10: Prompt for commands (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21
F13: Command area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-22
Exit SDA and create menu (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-23
Exit SDA and create menu (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-24
Notice message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-25
Sample menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26

© Copyright IBM Corp. 2001, 2016 xi

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Additional options when creating menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27

Prompted parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28
Command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29
Delete menu and all associated objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-30
Review questions (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-31
Review answers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-32
Review questions (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-33
Review answers (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-34
Exercise: Creating a menu using SDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-35
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-36

Unit 20. Tips for improved operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Topic 1: Proxy commands, using CHGCMD and CHGCMDDFT . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
Proxy commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
IBM commands and LPP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Change command: CHGCMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
CHGCMD: Where allowed to run parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
Which commands should be changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-11
Change command defaults: CHGCMDDFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-12
Changing an IBM-supplied command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-14
Example of a CL program to change commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
Topic 2: System Reply List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
What is the System Reply List? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
How the System Reply List works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18
When is the System Reply List used? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-19
System Reply List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21
Reply column of System Reply List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-23
Inquiry messages that might not need a reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
System Reply List with user entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-26
Topic 3: Attention program and DSCJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Set attention program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-28
User profile: Attention program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
Disconnect Job - DSCJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-31
Topic 4: Managing writers and printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-33
Using multiple writers for an OUTQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-34
Manage printing by spool file size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-35
Topic 5: Virtual optical image catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-37
Virtual optical image catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-38
Steps to create an optical image catalog (1 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-40
Steps to create an optical image catalog (2 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-41
Steps to create an optical image catalog (3 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-42
Steps to create an optical image catalog (4 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-43
Steps to create an optical image catalog (5 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-45
Steps to create an optical image catalog (6 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-46
Steps to create an optical image catalog (7 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-48
Steps to create an optical image catalog (8 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-49
Web address for virtual optical devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-50
Topic 6: FTP transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-51
Transfer data to and from IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-52
FTP PC-IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-53
FTP PC-IBM i name format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-54
FTP PC-IBM i transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-55
FTP IBM i - IBM i transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-56
FTP IBM i - IBM i IFS name format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-57
FTP - batch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-58

© Copyright IBM Corp. 2001, 2016 xii

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC FTP - batch mode run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-60

Topic 7: Advanced spool file management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-61
Too many files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-62
Spool file expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-63
Spool files expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-64
BRMS spool files expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-65
Delete expired spooled files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-66
Topic 8: SST/DST Advance Operator functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-67
Problem determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-68
Product activity log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-69
Log Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-70
Work with service action log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-71
Service action log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-72
Service action log entry details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-73
Check disks status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-74
Disk path status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-75
Review questions (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-76
Review answers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-77
Review questions (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-78
Review answer (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-79
Exercise: Tips for improved operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-80
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-81

Unit 21. Journaling overview and basic operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Topic 1: Journal management concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Think about your most important data file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4
Single-level storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Journal objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
Objects that can be journaled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
Display Journal Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Display Journal Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-10
F10 = Display only entry details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-12
Topic 2: Steps to implement journaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13
Implementing journaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-14
Step 1: CRTJRNRCV command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-16
Step 2: CRTJRN command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-18
Step 3a: Access path command (STRJRNAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19
Step 3b: Library command (STRJRNLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-20
Step 3c: Object command (STRJRNOBJ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-21
Step 3d: Physical file command (STRJRNPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-22
Step 3e: IFS object command (STRJRN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-24
IBM Navigator for i: Journaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-25
IBM Navigator for i start/end journaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-26
Save objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-27
Topic 3: Journal receiver considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-28
Managing the receiver chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-29
System change journal management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-31
Journal receiver chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-33
WRKJRNA command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-34
F15 = Work with Receiver Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-36
Exercise: Journal management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-38
Review questions (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-39
Review answers (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-40
Review questions (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-41
Review answers (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-42

© Copyright IBM Corp. 2001, 2016 xiii

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Contents

TOC Review questions (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-43

Review answers (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-44
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-45

Unit 22. Virtual IP versus EtherChannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Topic 1: EtherChannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
EtherChannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
EtherChannel required resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-5
EtherChannel creating line description (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
EtherChannel creating line description (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
EtherChannel creating line description (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
EtherChannel new resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-11
Topic 2: Virtual IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-12
Virtual IP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-13
Virtual IP wizard (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-14
Virtual IP wizard (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-15
Virtual IP wizard (3 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-16
Virtual IP wizard (4 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-17
Virtual IP created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-18
Virtual IP associate physical interface (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-19
Virtual IP associate physical interface (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-20
Virtual IP associate physical interface (3 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-21
Virtual IP associate physical interface (4 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-22
Virtual IP change preferred interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-23
Virtual IP 5250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-24
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-25
Review answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-26
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-27

© Copyright IBM Corp. 2001, 2016 xiv

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Trademarks

TMK

Trademarks
The reader should recognize that the following terms, which appear in the content of this training
document, are official trademarks of IBM or other companies:
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide.
The following are trademarks of International Business Machines Corporation, registered in many
jurisdictions worldwide:
Active Memory™ AIX® DB™
DB2® Domino® Express®
Integrated Language i5/OS™ Language Environment®
Environment®
Lotus® Micro-Partitioning® Notes®
Power Architecture® POWER Hypervisor™ Power Systems™
Power Systems Software™ Power® PowerVM®
POWER6® POWER7® POWER8®
Rational® Redbooks® System i®
System z®
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows 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.
VMware and the VMware “boxes” logo and design, Virtual SMP and VMotion are registered
trademarks or trademarks (the “Marks”) of VMware, Inc. in the United States and/or other
jurisdictions.
Other product and service names might be trademarks of IBM or other companies.

© Copyright IBM Corp. 2001, 2016 xv

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Course description

pref

Course description
Advanced System Operator Workshop for IBM i

Duration: 3 days

Purpose
This course is designed to enhance the skills of a IBM i System Operator. In this class, we will
explain the concept of how LPAR works and discuss the functions provided by the HMC. We will
discuss the IBM i Access Family of products in general and Access Client Solutions, specifically.
We will discuss the different types of security that you can implement in order to control who has
access to your data and what they can do with that data if they are allowed access. We will discuss
security control via system values, user and group profiles, authorization lists, and adopted
authority. This course will help you to develop additional skills in the areas of work management
and how to create a basic CL program. In the area of CL programming, we will discuss concepts of
programming, then how to create a basic CL program using the traditional application development
tools PDM and SEU. You will also learn the steps to create a menu using SDA. You will learn some
tips that you can use to help improve your IBM i operations. We will also discuss about journaling
overview and some tips which improved operator work. Finally will be discus about differences
between virtual IP and EtherChannel.

Important

This course consists of several independent modules. The modules, including the lab exercises,
stand on their own and do not depend on any other content.

Audience
This advanced course is designed for those individuals who are responsible for operating and
managing the operation of a single Power i server or a network of Power i servers.

Prerequisites
Before taking this course, a student should be able to:
• Perform basic system operations such as sending and receiving messages, working with user’s
jobs and printed output, entering commands on the system, and executing CL commands
• Describe the difference between an interactive job and a batch job
• Use the help facilities available on the system.

© Copyright IBM Corp. 2001, 2016 xvi

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Course description

pref
Objectives
• Explain the concept of how LPAR works
• Explain the functions served by the HMC
• Explain the functions of IBM i Access Client Solutions
• Explain how user versus resource security are implemented
• Explain the difference between group profiles and authorization lists
• Describe how adopted authority works
• Describe how work is managed on the system and the concepts of the performance tuning
process on the system
• Explain how Management Central can be used to manage a single system or a network of
Power i servers
• Perform the steps to create a basic CL program using both the traditional (PDM and SEU)
application development tools
• Perform the steps to create a menu using SDA
• Provide some tips on how you can improve your operations

Contents
• LPAR concepts and overview
• Console options and HMC overview
• Basic management using HMC
• IBM i Access Family overview
• IBM i Access Client Solutions
• Security concepts and overview
• System values
• User security
• Resource security
• Authorization lists and adopted authority
• Work management: Concepts and overview
• Work management: Subsystem concepts and overview
• Work management: Job processing concepts and interactive jobs
• Work management: Job processing concepts of other job types
• Work management: Submitting and tracking of batch jobs
• Programming concepts
• CL programming concepts
• CL programming using PDM and SEU

© Copyright IBM Corp. 2001, 2016 xvii

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Course description

pref • Creating a menu using SDA

• Tips for improved operation
• Journaling overview and basic operation
• Virtual IP versus EtherChannel

Curriculum relationship
• This course is part of the Power i curriculum. A system operations course, System Operator
Workshop for System i (AS24G), precedes this course.

© Copyright IBM Corp. 2001, 2016 xviii

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Agenda

pref

Agenda

Note

The following unit and exercise durations are estimates, and might not reflect every class
experience.

Day 1
(00:30) Welcome
(00:20) Unit 1: LPAR concepts and overview
(00:25) Unit 2: Console options and HMC overview
(00:10) Break
(01:15) Unit 3: Basic management using HMC
(00:30) Unit 4: IBM i Access Family overview
(00:10) Break
(00:45) Unit 5: IBM i Access Client Solutions
(00:30) Exercise 1: IBM Client Access Solutions
(00:10) Break
(00:10) Unit 6: Security concepts and overview
(00:20) Unit 7: System values
(01:00) Lunch
(00:25) Unit 8: User security, Topic 1 User profiles
(00:20) Exercise 2: Create a user profile
(00:10) Break
(00:15) Unit 8: User security, Topic 2 Group profiles
(00:30) Unit 9: Resource security

© Copyright IBM Corp. 2001, 2016 xix

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Agenda

pref
Day 2
(00:25) Exercise 3: Resource security and group profiles
(00:15) Unit 10: Authorization lists and adopted authority, Topic 1 Authorization lists
(00:20) Exercise 4: Authorization lists
(00:10) Break
(00:10) Unit 10: Authorization lists and adopted authority, Topic 2 Adopted authority
(00:10) Exercise 5: Adopting authority
(00:15) Unit 11: Work management: Concepts and overview
(00:35) Unit 12: Work management: Subsystem concepts and overview
(00:10) Break
(00:35) Unit 13: Work management: Job processing concepts and interactive jobs
(00:25) Unit 14: Work management: Job processing concepts of other job types
(01:00) Lunch
(00:20) Unit 15: Work management: Submitting and tracking of batch jobs
(00:40) Exercise 6: Work management: Job and subsystem management
(00:10) Break
(00:10) Unit 16: Programming concepts
(00:35) Unit 17: CL programming concepts
(00:20) Unit 18: CL programming using PDM and SEU
(00:45) Exercise 7: CL programming using PDM and SEU

Day 3
(00:45) Unit 19: Creating a menu using SDA
(00:30) Exercise 8: Creating a menu using SDA
(00:10) Break
(00:45) Unit 20: Tips for improved operation
(00:30) Exercise 9: Tips for improved operation
(01:00) Lunch
(00:50) Exercise 10: Transferring data using FTP
(01:00) Unit 21: Journaling overview and basic operation
(00:10) Break
(00:20) Exercise 11: Journal management
(00:45) Unit 22: Virtual IP versus EtherChannel

© Copyright IBM Corp. 2001, 2016 xx

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Unit 1. LPAR concepts and overview

Estimated time
00:20

Overview
This unit provides an overview of the concept of logical partitions.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 1-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Unit objectives
• Describe the functions of PowerVM
• Describe the concept of partitions
• List resources that are allocated to partitions
• Describe dynamic partitioning
• List some benefits of using a partition

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 1-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

IBM Power Systems family

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-2. IBM Power Systems family

The IBM Power Systems Hardware Information Center contains information about IBM i. Access
the website at the following URL: http://www.ibm.com/support/knowledgecenter/ssw_ibm_i.
Click the link for Hardware Information Center to see the web page (lower right corner on this
visual). The URL to access this website directly is:
http://www.ibm.com/support/knowledgecenter/POWER8/p8hdx/POWER8welcome.htm.

© Copyright IBM Corp. 2001, 2016 1-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Virtualization technologies on Power Systems with IBM i

• Multiple OSs
• Multiple LPARs
• Dynamic LPAR IBM i
Partitions
• Micro-Partitioning
• Virtual CPUs
• Multiple processor shared pools
• Shared dedicated processor
• IVE
• SR-IOV
• SMT
• Virtual LANs
• Virtual I/O
• IVM
• CoD, Power Enterprise Pools
• Live Partition Mobility
• HMC

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-3. Virtualization technologies on Power Systems with IBM i

The IBM System and IBM Power System technologies

The following technologies and services are the components of PowerVM, which are integrated into
the IBM Power Systems:
• POWER Hypervisor: Supports partitioning and dynamic resource movement across multiple
operating system environments.
• Multiple operating system supports: Logical partitioning allows a single server to run multiple
operating system images concurrently.
• Dynamic logical partitioning: Allows adding, moving, or deleting physical and virtual resources
of an LPAR without shut down.
• Micro-Partitioning: Enables a logical partition to be allocated a percentage of processor usage
rather than a full physical processor. Multiple virtual shared processor pools are available with
POWER6 POWER7 and POWER8 technology.
• Dedicated shared processor: Function provides the ability for partitions that normally run as
dedicated processor partitions to contribute unused processor capacity to the shared processor
pool. This support allows unneeded capacity to be donated to uncapped Micro-Partitioning
instead of being wasted as idle cycles in the dedicated partition.

© Copyright IBM Corp. 2001, 2016 1-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty
• Integrated Virtual Ethernet (IVE): Also called Host Ethernet Adapter (HEA - not supported on
Power8 servers), this is a feature that provides network connectivity to the partitions. It is
available on certain types of POWER6 and POWER7 based systems and allows partition
communication. It uses a physical Integrated Virtual Ethernet adapter and it must not be
considered as a virtual feature.
• For POWER8, you can use single root I/O virtualization (SR-IOV). This a Peripheral Component
Interconnect Express (PCIe) standard architecture that defines extensions to PCIe
specifications to enable multiple logical partitions running simultaneously within a system to
share PCIe devices. The architecture defines virtual replicas of PCI functions known as virtual
functions (VF). A Logical partition can connect directly to an SR-IOV adapter VF without going
through a virtual intermediary (VI) such as a POWER Hypervisor or Virtual I/O Server. This
ability provides for a low latency and lower CPU utilization alternative by avoiding a VI.
• Simultaneous Multithreading (SMT): On-chip hardware threads to improve resource usage.
• Virtual LAN: Provides network virtualization capabilities. It is purely firmware-based, by using
the POWER Hypervisor, and does not require the purchase of the PowerVM edition. Multiple
virtual switches can be defined with POWER6,POWER7, and POWER8 processor-based
systems.
• Virtual I/O: Allows the sharing of I/O adapters and devices between partitions.
• Integrated Virtualization Manager (IVM) provides the virtualization capabilities for the
management of a server and LPARs without using a Hardware Management Console (HMC).
• Capacity on Demand (CoD): Allows system resources, such as processors and memory, to be
activated as needed.
• Power Enterprise Pools (PEP) provide the ability to move processor and memory resources
from one server to another any time, with no physical movement of hardware, by using easy
operator commands in HMC.
• The PowerVM Enterprise edition includes the Partition Mobility virtualization feature that allows
migrating a virtualized logical partition from a source system to a target. This feature supports
Live Partition Migration without partition shutdown.
• The PowerVM Enterprise edition also includes the Active Memory sharing feature that allows
shared memory partitions to share a common shared memory pool (not supported in IBM i).
• Shared Storage Pools allow share storage across systems with possibility of cloning or moving
partitions (not supported in IBM i).
• Suspend/Resume feature allows suspend/resume client partition for releasing server
resources.
• Thin Provisioning allows better utilization of disks space in Shared Storage Pools (not
supported in IBM i).
• Most of the hardware virtualization features listed above are managed by using the HMC. IVM
allows management of some IBM Power Systems, and blades without using an HMC. IVM does
not support all of the HMC functions and has limited capabilities.

© Copyright IBM Corp. 2001, 2016 1-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

IBM PowerVM editions

Express Standard Enterprise
Features
Edition Edition Edition
Maximum VMs 3 / Server 2000 / Server 2000 / Server

VMControl, IVM*, VMControl, IVM*,

Management VMControl, IVM,
HMC HMC

Virtual I/O Server (Dual) (Dual)

Suspend/Resume

NPIV

Shared processor pools

Shared storage pools

SRIOV

Live Partition Mobility

* IVM only supports a single Virtual I/O Server

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-4. IBM PowerVM editions

PowerVM Enterprise Edition

PowerVM Enterprise Edition is offered exclusively on POWER6,POWER7/7+, and POWER8
processor-based servers and includes all the features of PowerVM Standard Edition plus two new
industry-leading capabilities called Active Memory Sharing and Live Partition Mobility.
PowerVM Standard Edition
For users ready to get the full value out of their server, IBM offers PowerVM Standard Edition
providing the most complete virtualization functionality for AIX, IBM i, and Linux operating systems
in the industry. PowerVM Standard Edition is supported on Power Systems servers and includes
features designed to allow businesses to increase system utilization, while helping to ensure that
applications continue to get the resources they need.
PowerVM Express Edition
PowerVM Express Edition is designed for users looking for an introduction to more advanced
virtualization features at a highly affordable price. With PowerVM Express Edition, users can create
up to three partitions on the server, leverage virtualized disk and optical devices VIOS, and even try
out the shared processor pool.

© Copyright IBM Corp. 2001, 2016 1-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

IBM PowerVM features by Power8 systems

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-5. IBM PowerVM features by Power8 systems

On this visual, you can see PowerVM features and editions availability depending on the Power8
systems models.

© Copyright IBM Corp. 2001, 2016 1-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

What is a partition?
• Partition:
ƒ Allocation of one system’s resources (processors, memory, I/O, and virtual
I/O) to create logically separate systems.
ƒ Each partition is an independent operating environment.

From one to many

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-6. What is a partition?

Partition
When a Power i server is subdivided into multiple, independent operating system images, those
independent operating environments are called partitions. The resources on the system are divided
up among the partitions. Applications running on a partitioned system do not have to be redesigned
for the partitioned environment.
Independent operating environment
Each partition runs its own operating system that might or might not match operating systems in
other partitions on the same system. Each partition can be started and stopped independently of
other partitions.

© Copyright IBM Corp. 2001, 2016 1-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Logical partition
• A partition is the allocation of system resources to create logically
separate systems within the same physical footprint.
• A logical partition is when the isolation is implemented with
firmware:
ƒ Although a partition might be logical, it can also be physical (resources).
ƒ It provides configuration flexibility.

SYS1 SYS2 SYS3 SYS4

1:00 10:00 11:00 12:00

Japan US Brazil UK LPARs operate

independently
ORD

IBM i Linux IBM i AIX

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-7. Logical partition

Logical partition (LPAR)

Logical partitioning is the ability to make a single system run as if it were two or more systems.
Each partition represents a division of resources in your computer system. The partitions are logical
because the division of resources is virtual and not along physical (tower) boundaries. However,
there are, configuration rules that must be followed and these are covered later in this course. For
the rest of the course, logical partitions are simply called LPARs or partitions for brevity.
Implemented in firmware
A logical partition uses firmware to logically partition the resources on a system. While there are
configuration rules, the granularity of the units of resources that can be allocated to partitions is
very flexible. You can add just a small amount memory if that is all that is needed without a
dependency on the size of the memory controller or without having to add more processors or I/O
slots that are not needed.
Firmware refers to underlying software running on a system independently from any operating
system. On Power Systems, this includes the software used by the Flexible Service Processor
(FSP) and the POWER Hypervisor.

© Copyright IBM Corp. 2001, 2016 1-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty
POWER4 and POWER5 based servers comparison
There is no concept of a primary or secondary partition for POWER5 systems.
You might have heard the phrase physical partitions from the UNIX server market that is partitions
based on physical system units, such as a system board, which contains a certain amount of
processing power and memory, and a number of I/O slots. IBM implemented logical partitions, not
physical partitions for IBM i AIX an Linux.

© Copyright IBM Corp. 2001, 2016 1-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Partition characteristics
• Each partition has its own (or have access to):
ƒ Licensed Internal Code (LIC) for IBM i or open firmware from AIX VIOS and
Linux
ƒ Operating system
ƒ Console
ƒ Load source disk or boot resources
ƒ ASPs and memory pools
ƒ Others expected in a stand-alone operating system environment:
í Problem logs
í Data (libraries, objects, and file system)
í Performance characteristics
í Language feature codes
í Network identity
í Date and time

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-8. Partition characteristics

Characteristics of a partition
The visual above illustrates how each partition is independent. As stated before, each partition runs
on its own operating system that might be IBM i (or Linux, VIOS, and AIX). The versions of the
operating system might be any valid version that is supported. Other things you would expect on
physically separate system are also separate for partitions and even independent virtual consoles.
What is the same between partitions on the same system?
Each partition shares a few physical system attributes such as the system serial number, system
model, and processor feature code with other partitions. In addition, you can choose to share other
hardware such as SAS, Fibre adapters, and serial devices among partitions.

© Copyright IBM Corp. 2001, 2016 1-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Partition resources
• The resources that are allocated to partitions are:
ƒ Load source I/O adapters and disk unit
ƒ I/O slots
í Including virtual devices (volumes from external storage)
ƒ Processing units
ƒ Memory
ƒ 5250 emulation (‘interactive’) for IBM i
ƒ Console

• Virtual resources that can be shared:

ƒ Ethernet
ƒ SCSI
ƒ Serial
ƒ Fibre Channel

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-9. Partition resources

Resources
Resources are the system components that are configured into partitions. The maximum number of
partitions is related to the total amount of resources on a system. For example, if a system has
enough resources, the upper limit of the number of partitions is 1000 on Power8 (E880) servers.
Minimum amount of resources
Each IBM i partition must be configured with at least 128 MB of memory, five hundredths of a
physical processor, and enough I/O devices to provide a load source (boot resources), have access
to a console and have the ability to load code.
I/O slots
I/O resources are allocated to partitions at the slot level. At a minimum, you must configure a
partition with enough I/O resources to include the load source disk (boot resources) and at least
access to a console.
Processing units
A dedicated processor = 1.00 processing units. Micro-Partitioning 0,05 processor unit (up to 20
micropartitions per processor).

© Copyright IBM Corp. 2001, 2016 1-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty
Memory
Memory is allocated in multiple MB segments (the smallest being 16 MB). The exact size depends
on the model and the total amount of memory on the managed server. A partition can be as small
as 254 MB or as large as all of the installed memory.
5250 CPW (IBM i partitions only) - also known as OLTP
Your system has a certain amount of interactive performance based on the type of system and the
number of processors. The 5250 emulation refers to how much the user must interact with (and
respond to prompts from) the computer. You can contrast this with batch where no user intervention
is required. Given the amount of interactive performance on your system, you need to determine
what percentage is available for each partition. The combined total of all partitions’ settings cannot
exceed 100% - of the available 5250 CPWs. This resource was known as Interactive Performance
on the POWER4 based iSeries servers.
Virtual devices
Other devices can be configured to be shared between partitions. Each partition can configure
virtual I/O slots, which can be configured with a virtual adapter instance. These virtual adapters can
be an Ethernet interface, a SCSI, serial devices, or Fibre Channel.

© Copyright IBM Corp. 2001, 2016 1-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Logical partition resource example

• Flexibility to allocate resources depending on need
LPAR1 LPAR2 LPAR 3 LPAR 4

Processors

Memory

I/O slots

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-10. Logical partition resource example

This visual above shows how a system’s resources might be divided between four partitions. With
logical partitions, resources can be allocated based on computing needs. You do not need to
allocate all resources to partitions. Some resources can remain deallocated until they are needed.

© Copyright IBM Corp. 2001, 2016 1-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

The big picture: Dynamic partitioning

Managed system *DLPAR

Processors

IBM i Linux Unassigned Mem regions

Partition 1
resources
Partition 2 I/O slots

HMC
POWER Hypervisor
Ethernet

Processors
Non-volatile RAM

Mem regions LPAR Service

allocation processor
I/O slots
tables
Ethernet

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-11. The big picture: Dynamic partitioning

The Hardware Management Console (HMC) uses its network connections to one or more servers
or frames, referred to as managed systems to perform various management functions. More details
of the HMC are covered in the next unit.

© Copyright IBM Corp. 2001, 2016 1-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Dynamic partitioning
• DLPAR allows you to add, remove, or move resources between
partitions without restarting the partitions.

• Resources include:
ƒ Processors, memory, and I/O slots that are not required
ƒ Virtual I/O

• Security and isolation between LPARs is not compromised:

ƒ A partition sees its own resources plus other available resources
ƒ Resources are reset when moved

• Applications might or might not be DLPAR-aware.

DLPAR allows you to react

to changing resource needs.
LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-12. Dynamic partitioning

Dynamic partitioning
Dynamic partitioning refers to the fact that you can “switch” resources between partitions without
shutting down the partitions. The opposite of dynamic partitioning is static partitioning, where new
configurations are only used when a partition is reactivated.
DLPAR operations do not weaken the security or isolation between LPARs. Partitions only see
resources in their own partition, as well as any potential “connectors” for additional virtual resources
that might have been configured, and any resources not currently allocated.
Resources are reset when moved from one partition to another. Processors are reinitialized,
memory regions are cleared, and adapter slots are reset.
DLPAR operations
You can add, remove, and move resources between partitions. This can be accomplished from the
HMC application or through HMC command line commands.
With virtual devices, you can add or delete them, but you cannot move them from one partition to
another. However, you can dynamically change the configuration that specifies what type of virtual
adapter it is. Other partition options that can be reconfigured dynamically are covered later in this
course.

© Copyright IBM Corp. 2001, 2016 1-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty
DLPAR resources
The resources include memory, processing units, and non-required I/O slots. A “required” slot or
adapter is one that a partition has defines as essential to its operation and is thus unavailable for
“movement” as long as the partition is operational.
For virtual devices, you can add and remove, but not move resources between partitions. These
operations will be covered in a future unit in this course.
Applications might not be DLPAR-aware
Most applications are unaware of the underlying resource specifics and that works just fine. But
some applications and utilities, particularly monitoring tools, might inhibit some DLPAR operations if
they bind to processors or pin memory. Many resource-aware applications have been rewritten in
recent years to allow DLPAR. Check with your sales representative about your application.

© Copyright IBM Corp. 2001, 2016 1-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Virtual I/O
• Each partition has virtual I/O ‘slots’.
ƒ Configurable for each partition

• Slots can have a virtual adapter instance.

ƒ Ethernet, serial, or SCSI, Fibre Channel

• Can be dynamically added or removed just like physical I/O slots:

ƒ But they cannot be dynamically moved to another partition
ƒ Configuration of what is in the slot can be redefined without a restart of the
partition

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-13. Virtual I/O

Virtual I/O adapters

Virtual I/O adapters give a partition the flexibility to use certain types of resources without requiring
that the physical hardware be present.
The following virtual I/O adapters can be created:
• Virtual Ethernet
• Virtual Serial
• Virtual SCSI
• Virtual Fibre Channel - on the virtual Fiber Channel the best performance can be achieved on
NPIV - N_Port ID Virtualization is a Fibre Channel feature whereby multiple Fibre Channel node
port (N_Port) IDs can share a single physical N_Port.
All virtual I/O adapters reside on a single virtual system. The maximum number of virtual
adapters is a field that a user can edit. This field specifies how many virtual I/O adapters can
connect to the virtual system bus.

© Copyright IBM Corp. 2001, 2016 1-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty
Virtual Ethernet
Virtual Ethernet allows for high speed (1 gigabit) inter-partition communications. For two partitions
to be able to talk they need to have a virtual Ethernet adapter that has the same port virtual LAN ID.
Having the virtual Ethernet adapter occupy the same slot is not a requirement.
Virtual Serial
Virtual serial allows for the creation of an internal point-to-point connection. This connection is
between the partition and either the HMC or another partition. An adapter is defined as either a
client adapter or a server adapter. A client adapter is used on a partition that wants to use a
resource that is provided by a server adapter.
In creating a virtual serial client adapter, the remote partition needs to be specified along with the
slot number containing the virtual serial server adapter on the remote partition. By default, the HMC
gets the console for a hosted guest partition. A pair of virtual serial adapters can be used to allow
another partition to provide console function for the hosted guest partition as well.
Virtual SCSI
Virtual SCSI allows for a partition to use storage resources that physically reside in another
partition. Storage resources include disk, tape, or optical. As with virtual serial, the server adapter
type is for use on a partition that is providing a resource while the Client adapter is used on a
partition that is using that resource. A pair of virtual SCSI adapters can be created to provide disk
access for a hosted guest partition.
Virtual Fibre Channel
A virtual Fibre Channel adapter is a virtual adapter that provides client logical partitions with a Fibre
Channel connection to a storage area network N_Port ID virtualization (NPIV) is a technology that
allows a single host bus adapter (HBA) called an “N_Port” to register multiple worldwide port names
(WWPNs) and N_Port identification numbers. This allows each virtual server to present a different
worldwide name to the storage area network (SAN), which in turn means that each virtual server
sees its own storage.

© Copyright IBM Corp. 2001, 2016 1-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Smarter IOAs (IOP-less) direction

Processor IOP IOA

Classic IOP/IOA

IOA
IOP-less Processor

• IOA technology has evolved to the point where an IOA can take over
the IOP as well as the IOA functionality.
• Smarter IOA benefits include:
ƒ Avoiding cost of IOP and PCI slot to hold IOP
ƒ Configuration flexibility including simpler LPAR I/O
• IBM i 7.2 on POWER6 does not support IOPs or IOP-based adapters.
• POWER7 or late does not support IOPs or IOP-based adapters.
LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-14. Smarter IOAs (IOP-less) direction

On the visual you can compare classic IOP/IOA and modern IOP-less adapter.

Note

Power and Power8 supports only IOP-less adapters.

© Copyright IBM Corp. 2001, 2016 1-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

LPAR summary
• No requirement for primary partition
• All LPARed servers must have an IVM or HMC
• All IBM i partitions must be at 7.1 or greater
• Simple migration process

VIOS IBM i AIX LINUX

Virtual SCSI Adapter

Power Virtual Serial Adapter
Hypervisor Virtual Fibre Channel
Virtual Ethernet

Power Systems
LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-15. LPAR summary

Note

Old IBM i version (6.1) can be used in LPARed environment (POWER6 and POWER7) but this
version is not supported now.

© Copyright IBM Corp. 2001, 2016 1-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Benefits of using partitions

• Capacity management
ƒ Flexibility to allocate resources
• Consolidation:
ƒ Consolidate hardware, floor space, software licenses, support contracts, and
in-house support/operations
ƒ Efficient use of resources
• Application isolation:
ƒ Separate workloads
ƒ Guaranteed resources
ƒ Data integrity
• Merge production and test environments
ƒ Share same hardware
• Ability to have virtual:
ƒ Ethernet
ƒ I/O devices
• Shared processors: Capped or uncapped

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-16. Benefits of using partitions

Introduction
Sometimes large symmetric multiprocessing systems are used to run several different applications.
This might be an efficient use of resources in some cases. In other cases, separate physical
computers are used to run individual applications. This page describes reasons why it might be
better to create separate partitions rather than run everything in the same operating system image
or use separate physical computers for each application.
Capacity management
You might want to use partitions to reallocate resources when the system workload changes. For
example, if at the end of each month, one partition runs CPU-intensive, batch jobs, you can
reconfigure the system monthly to take processors from another lower priority application in
another partition and “loan” them to the partition with the batch application. We see later that you
can even name these configurations using keywords, such as end-of-month to make the
reconfiguration operation easier.

© Copyright IBM Corp. 2001, 2016 1-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty
Consolidation
Using partitions gives you the ability to reallocate expensive resources and manage them all with
one interface (the HMC). You can reallocate processors, memory, or any I/O adapter (and thus
device) by reconfiguring the partitions or by using dynamic partition operations. All of the resources
are located within one server, potentially reducing the amount of floor space needed.
Application isolation
Partitioning isolates an application from others in different partitions. For example, two applications
on one SMP system could interfere with each other or compete for the same resources. One
decision support database query could bring a second, interactive application to a frustrating snail’s
pace. By separating the applications into their own partitions, they cannot interfere with each other.
Also, if one application were to hang or crash the operating system, this would not have an effect on
the other partitions. Additionally, with partitions, one server can support multiple applications that
use different time zones or that run on different operating system release levels. Partitions can also
be used to comply with application license requirements. For example, a 4-processor partition
could be created to comply with an application license that only allows for a 4-processor server.
Check the vendor’s application license requirements carefully.
Merge production and test environments
Many customers utilize smaller development systems to develop, test, and migrate applications.
These smaller systems might not be the same hardware, have the same software, devices, or
infrastructure as the “real”, production system. These issues can be largely avoided by utilizing a
partition on the same system as the production application for development and testing. This also
protects the production partition from the activities on the test partition. When the testing is
complete, the resources used for the development partition can be reallocated to the production
partition.
Partitions have an exclusive set of resources
The amount of resources allocated to a partition is generally fixed (although there are some
exceptions that can be configured). This could be a benefit or a disadvantage. On a symmetric
multiprocessor system running multiple applications within the same operating system image, there
might be greater sharing (or swapping) of resources than on a partition system where the
applications are isolated in their own partitions.
Virtual Ethernet and virtual I/O devices
On POWER servers, you can configure a virtual Ethernet connection, which acts like an Ethernet
connection, but is really a memory-to-memory connection with another partition. Virtual I/O devices
allow partitions to use physical devices (such as a console or tape drive or CD drive) that are
owned by another partition.
Shared Processors
Partitioning gives you the ability to assign less than full processors to a server. These shared
processor partitions can be either capped (capacity is limited to the number of shared processing
units assigned) or uncapped (have the capability of using more processing resources than are
assigned via processing units).

© Copyright IBM Corp. 2001, 2016 1-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

LPAR education

AS5EG: PowerVM on IBM i - I: Implementing Virtualization and LPAR

This course teaches how to implement virtualization and LPARs on a Power
system with IBM i.

AS5FG: PowerVM on IBM i - II : Advanced Topics and Performance

It teaches advanced topics and performance implementing PowerVM on IBM
i.

OL52G: Hardware Management Console (HMC) for Power Systems with IBM i
This course teaches the functions and capabilities provided by the HMC to
manage a Power system with IBM i.

http://www.ibm.com/training

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-17. LPAR education

When you attend the LPAR course, you learn the installation, configuration, and operation of the
Hardware Management Console (HMC) for Power System servers. The class begins with an
overview of HMC functions, followed by detailed information on how to install a new HMC, configure
network settings and HMC user profiles, create a connection to a managed system, and upgrade
an existing HMC. Explore the HMC’s graphical user interface (GUI) to manage System i servers.
Through online presentations and quizzes, develop the basic skills for backing up HMC and
managed system configuration data, performing HMC and microcode software maintenance, and
creating logical partitions (LPAR).

© Copyright IBM Corp. 2001, 2016 1-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Review questions
1. True or False: A partition is an independent operating
environment within a larger system.

2. A partition is a logical partition if which of the following

options are true?
a. Resource assignments are flexible.
b. Resources can be moved between partitions without a restart.
c. Partition isolation is accomplished with software (firmware).
d. All of the above.

3. True or False: PowerVM provides virtualization and the

management of resources in a consolidated, logical view.

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-18. Review questions

© Copyright IBM Corp. 2001, 2016 1-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Review answers
1. True or False: A partition is an independent operating
environment within a larger system.
The answer is true.

2. A partition is a logical partition if which of the following

options are true?
a. Resource assignments are flexible.
b. Resources can be moved between partitions without a restart.
c. Partition isolation is accomplished with software (firmware).
d. All of the above.
The answer is all of the above.

3. True or False: PowerVM provides virtualization and the

management of resources in a consolidated, logical view.
The answer is true.

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-19. Review answers

© Copyright IBM Corp. 2001, 2016 1-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 1. LPAR concepts and overview

Uempty

Unit summary
• Describe the functions of PowerVM
• Describe the concepts of partitions
• List resources that are allocated to partitions
• Describe dynamic partitioning
• List some benefits of using a partition

LPAR concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 1-20. Unit summary

The objective of the remainder of the course is to expand your knowledge on these and other
topics. A focus lies on the automation of some of your system operations activities.

© Copyright IBM Corp. 2001, 2016 1-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Unit 2. Console options and HMC

overview
Estimated time
00:25

Overview
This unit provides a review of the different options available for setting a console for the system and
overviews the concepts of the HMC.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 2-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Unit objectives
• Discuss the different consoles that can be used with Power with IBM i
• Describe the concepts of HMC
• List the different HMC models that are available
• Describe virtual HMC appliance
• Describe the differences between IVM, HMC
• Describe the different capacity on-demand options available

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 2-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Power with IBM i console

Existing available console option:

• Operation LAN console (LAN adapter required)
• 5250 interface using HMC (vHMC)

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-2. Power with IBM i console

Operations console
With Operations console, you can use one or more PCs to access and control the server and
control panel functions. This PC can be attached either locally or remotely. Operations console is
available for connectivity to an IBM i server. This PC can be directly connected by using a cable,
through a LAN with a dedicated adapter, or can be connected using the embedded Ethernet port, if
it is available on the server. With this type of connection, a single PC can serve as the console for
multiple servers.
Considerations for choosing Operations console:
You can set up Operations console to manage the IBM i operating system in a partitioned or a
non-partitioned environment.
You need a separate LAN adapter card for each partition with which you need to communicate
using Operations console. This can result in less room for other I/O adapters that you need to install
in the server. Unlike the HMC, you cannot change partition resources with Operations console.
Although Operations console uses a standard Windows PC, the HMC is a dedicated system that
cannot be changed except for service upgrades. This greatly increases the security and stability of
the HMC versus Operations console.
Operations console supports more than 40 languages.

© Copyright IBM Corp. 2001, 2016 2-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty
5250 interface using HMC or virtual HMC (VHMC):
You can connect to system using session directly on the HMC or you can use IBM i Client Solution
(or previous IBM Client Access) to set up the console session or virtual panel session.
HMC allows you connect to many partitions. You can setup a shared or dedicated connection to the
console.

© Copyright IBM Corp. 2001, 2016 2-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

HMC introduction
• Intel-based PC appliance
ƒ Required for configuration and management of partitions
í IBM Power Systems with POWER5, POWER6, POWER7, POWER8 processors

• Main HMC applications are:

ƒ Server and partition management
ƒ Licensed Internal Code maintenance:
í HMC code maintenance
Independent of managed system or operating systems
í Licensed Internal Code update for Flexible Service Processor, or FSP
ƒ HMC management:
í HMC users
í Configuration
ƒ Service applications
ƒ Power Systems HW Information Center
HMC

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-3. HMC introduction

The Hardware Maintenance Console (HMC) is a dedicated desktop or rack-mounted workstation

that provides a graphical user interface (GUI) for configuration and operating logical partitions on
LPAR-capable POWER5, POWER6, POWER7, and POWER8 servers.
An HMC is required for many functions, including logical partition (LPAR) management, capacity on
demand (CoD) management, and as a single point for service error reporting for the HMC the
service processor and - if wanted - logical partitions.
Virtual HMC appliance functionality is the same as standard HMC. VHMC required VMware or
KVM.

© Copyright IBM Corp. 2001, 2016 2-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

IBM Systems hierarchy of management

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-4. IBM Systems hierarchy of management

IBM Directory management was removed now IBM offering two management models:
1. PowerVM architecture based on Cloud Manager wit OpenStack and PowerVC and HMC/KVM
to manage server.
2. PowerVM with NovaLink Architecture this is new architecture.
With both models, you can use HMC to manage servers, partitions and their resources.
IBM Cloud Manager with OpenStack for Power Systems is an entry level cloud solution to help
organizations get up and running quickly and easily with cloud. It works with Power Systems
infrastructure, leveraging Power's enterprise security, availability, and reliability to deliver cloud
without risk. IBM Cloud Manager with OpenStack for Power Systems increases efficiency through
heterogeneous cloud management across Power Systems, System z, and x86 environments,
on-premises or off-premises, to manage private, public, or hybrid cloud infrastructure. And Cloud
Manager with OpenStack can manage PowerKVM environments directly or PowerVM
environments through PowerVC, giving customers the flexibility to leverage the choice of
hypervisors provided with Power Systems.

© Copyright IBM Corp. 2001, 2016 2-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty
PowerVM NovaLink is a software interface that is used for virtualization management. You can
install PowerVM NovaLink on a PowerVM server. PowerVM NovaLink enables highly scalable
modern cloud management and deployment of critical enterprise workloads. You can use PowerVM
NovaLink to provision large numbers of virtual machines on PowerVM servers quickly and at a
reduced cost.
PowerVM NovaLink runs in a Linux logical partition on a POWER8 processor-based server that is
virtualized by PowerVM. You can manage the server through a representational state transfer
application programming interface (REST API) or through a Command Line Interface (CLI). You
can also manage the server by using PowerVC or other OpenStack solutions. PowerVM NovaLink
is available at no additional charge for servers that are virtualized by PowerVM.
PowerVM NovaLink can be installed only on POWER8 processor-based servers.

© Copyright IBM Corp. 2001, 2016 2-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

HMC and managed system

• Graphic representation of relationships between:
ƒ HMC
ƒ Service processor
ƒ Hypervisor

Virtual Server (Partitions): When active

Hypervisor: OS-independent
Non-volatile RAM

Processors
Service
processor Virtual servers consist of different
Mem regions Virtual elements (look at colors):
Server • Processors
I/O slots
(LPAR) Managed • Memory
allocation
tables
system • I/O slots
• Some part of Hypervisor
Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-5. HMC and managed system

The HMC and service processor

The HMC provides the administrator a GUI method of managing virtual servers (partitions or
LPARs).
The Service Processor (SP) in turn provides the interface to the Hypervisor, which is operating
system and virtual server (partition) independent.
The POWER Hypervisor is the interface through which the HMC is able to control the allocation of
appropriate resources necessary for virtual servers (partitions) on a managed system.
The virtual server (partition) configuration information is recorded in the NVRAM on the managed
system.

© Copyright IBM Corp. 2001, 2016 2-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Managed system without HMC

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-6. Managed system without HMC

Advanced System Management Interface (ASMI)

If your system is not managed by a Hardware Management Console (HMC), you can connect a PC
or notebook to the server to access the Advanced System Management Interface (ASMI). You
need to configure the web browser address on the PC or notebook to match the manufacturing
default address on the server.
Depending on type of the server the default addresses could be different. Check it in the server
specification.
The web interface to the ASMI is available during all phases of system operation including the initial
program load (IPL) and run time. The ASMI is used to perform general and administrator-level
service tasks. These tasks include reading service processor error logs, reading vital product data,
setting up the service processor, and controlling the system power.

© Copyright IBM Corp. 2001, 2016 2-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Managed system without HMC different options

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-7. Managed system without HMC different options

You can manage POWER servers without an HMC. The various management options and
supported virtual machine types are:
• IVM (AIX, Linux, IBM i)
• KVM (Linux)
• Full system partition (AIX, Linux, IBM i)
KVM (Kernel-based Virtual Machine) is a popular open-source hypervisor that’s new to the
Power Systems family of servers. Both KVM and IVM are installed and run directly on the server.
Their management in scope applies only to the virtual machines running on the same server. The
remainder of this article focuses on managing POWER8 scale-out servers with an HMC.
Integrated Virtualization Manager
The Integrated Virtualization Manager (IVM), a component of PowerVM Editions, can be used to
manage your Virtual I/O Server (VIOS) and client virtual servers. The IVM provides a web-based
system management interface. The interface allows to create a partition.
Partitioning with the Integrated Virtualization Manager
In the above figure, the VIOS is in its own partition, and the client logical partitions are managed by
the VIOS logical partition. The browser on the PC connects to the IVM over a network and it (IVM)
can be used to create and managed the logical partitions.

© Copyright IBM Corp. 2001, 2016 2-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Power Systems management: Summary

Power Systems
Rack-mount
ASMI only IVM only vHMC appliance
HMC
ƒ No LPAR ƒ Entry-level LPAR ƒ “Stackable”, with ƒ Hardware+vHMC
ƒ Limited CoD controls from IVM, shared flat ƒ vHMC only –Virtual
ƒ Basic service functions based on AIX VIO panel/keyboard Machine image
Server (VIOS) drawer, well suited
ƒ Limited CoD for clusters
ƒ Limited service ƒ Full function LPAR
functions controls
ƒ Full service functions
ƒ Virtual OS consoles
ƒ Redundant HMC
optional

ASMI / TTY to FSP directly Browser to VIOS

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-8. Power Systems management: Summary

This figure summarizes the Power Systems management techniques available to administrators.
ASMI management allows limited server management and no partitions. IVM and HMC provide
more functional server management and partitions.
vHMC
Prior to HMC V8R8.4, the POWER HMC was sold only as an integrated appliance that included the
underlying hardware as well as the HMC firmware. Starting with V8R8.4, the HMC can now be
purchased as either the traditional hardware appliance (for example, model 7042-CRx) or as a
firmware only virtual machine image. The virtual HMC (vHMC) offering allows clients to use their
own hardware and server virtualization to host the IBM supplied HMC virtual appliance.

© Copyright IBM Corp. 2001, 2016 2-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

HMC features
• Integrated, custom HMC software
ƒ Graphical user interface
ƒ Commands
• Remotely accessible
• Support for multiple managed systems
• Active partitions can continue to function without an HMC
ƒ The ability to change resource configuration is lost
Rack-mount
• Redundant capability
7042-CR9
• Partition information backups
• Console for logical partitions
• HMC connection options:
ƒ Private network
ƒ Open network
Virtual HMC
• Performance management
5765-HMV
• Template management

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-9. HMC features

Management interfaces:
The HMC provides a GUI for managing the Power Systems. This GUI can be operated locally on
the HMC or from a web browser connected to the HMC over a network. While the vast majority of
work will be performed using the GUI, there are commands that can be entered directly on the HMC
and/or run through SSH connections from PCs or LPARs in the managed Power System to
automate functions such as LPAR configuration changes.
The HMC virtual appliance can be installed in your existing x86 virtualized infrastructure. The HMC
virtual appliance supports the following virtualization hypervisors:
• Kernel-based virtual machine (KVM)
• Xen
• VMware

© Copyright IBM Corp. 2001, 2016 2-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

HMC options
• Refreshed rack-mounted HMC
ƒ For POWER6 and later servers
ƒ 7042-CR9 - follow-on to CR8

• New HMC virtual appliance (vHMC)

ƒ For POWER6, POWER7, POWER8 servers
ƒ Same functionality as traditional HMC (version 8)
ƒ Runs as virtual machine on x86 server

Options for attachment to a server

One vHMC and One or two vHMCs

One or two HMCs one HMC

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-10. HMC options

Now you can mix hardware and virtual HMC in following combination:
1. Only hardware
2. Hardware and virtual
3. Only wirtual

© Copyright IBM Corp. 2001, 2016 2-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Available HMC model

• For POWER6 and later servers
• 7042-CR9 - follow-on to 7042-CR8
• Normal technology refresh
• Refreshed rack-mounted HMC
ƒ 2.4 GHz Intel Xeon Processor
ƒ 16 GB to 192 GB memory (#EM20 16 GB feature code)
í Most clients expected to use 16 GB or 32 GB for HMC
ƒ One or optionally two 500 GB SATA disk drives
í Second drive allows RAID1 mirroring protection (recommended/defaulted)
í Support any two of the eight physical hot-plug SFF bays (max 2 supported)
ƒ DVD-RAM
ƒ Four integrated Ethernet ports
ƒ Six USB ports
ƒ One PCIe slot
ƒ One or two power supplies (two recommended for hot-plug redundancy)
ƒ 1U (1 EIA)
ƒ Like CR8, does not offer an internal or external modem (or support one)

• HMC code level 8.4.0 or later

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-11. Available HMC model

HMC 7042-CR8 and 7042-CR7 are still supported but are no longer marketed.

© Copyright IBM Corp. 2001, 2016 2-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

HMC functions
• Configuration management
• Operations management
• Change management
• Problem management
• Service management

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-12. HMC functions

When you log on to the HMC you can choose which software interface to use. The HMC Classic
interface provides access to all traditional functions of the HMC and the HMC Enhanced interface
provides both redesigned and new virtualization tasks and functions.
Bellow some traditional functions:
• Configuration management
• Server and partition configuration
• Virtual I/O configuration
• Capacity on-demand management
• HMC setup and configuration
• Operations management
• GUI or command line, local, or remote
• Virtual operating system consoles
• Server partition controls
• Dynamic LPAR resource movement

© Copyright IBM Corp. 2001, 2016 2-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty
• Scheduled operations
• Change management
• Add/remove server hardware
• Check and update Licensed Internal Code on servers and on HMC itself
• Problem management
• Hardware error event collection, analysis, and correlation
• Gathering of extended debug data
• Transmission of problems to IBM
• Service management
• Guided concurrent repair procedures
• Hardware inventory collection
• Service utilities

© Copyright IBM Corp. 2001, 2016 2-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Capacity on demand
• Capacity on Demand (CoD)
ƒ Activation of processors or memory
• Capacity Upgrade on Demand (CUoD)
ƒ permanently activate one or more inactive processor cores or memory
• Trial CoD
ƒ No charge 30-day activation of processors or memory resources
• Elastic CoD
ƒ Ability to activate processor or memory resources temporarily
• Utility CoD
Add reserve
ƒ Ability to cover unpredictable, short workload spikes resources
• Power Enterprise Pool
ƒ Group of systems that can share Mobile Capacity on Demand (CoD)
processor resources and memory resources

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-13. Capacity on demand

CoD is a list of features that can be purchased. The bullets in the visual list the purchasing options
that are managed from the HMC and require a license key to activate:
• Capacity CUoD Capacity on Demand (CoD) offerings you can dynamically activate one or
more resources on your server as your business peaks dictate. You can activate inactive
processor cores or memory units that are already installed on your server on a temporary and
permanent basis. It requires a purchase agreement. Once processors or memory is added,
there is no ability to turn off the capacity.
• Trial CoD is available for 30 days at no additional cost to allow testing and emergency relief
while the customer processes the purchase of permanent CUoD resources.
• Elastic CoD (formerly referred to as On/Off CoD) allows you to temporarily activate and
deactivate processor cores and memory units to help meet the demands of business peaks.
After you request that a number of processor cores or memory units are to be made temporarily
available for a specified number of days, those processor cores and memory units are available
immediately. You can start and stop requests for Elastic CoD, and you are billed for usage at the
end of each quarter.
• Utility CoD is used when you have unpredictable, short workload spikes. Utility CoD
automatically provides additional processor capacity on a temporary basis within the shared

© Copyright IBM Corp. 2001, 2016 2-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty
processor pool. Use is measured in processor minute increments and is reported at the Utility
CoD website.
• Power Enterprise Pool is a group of systems that can share Mobile Capacity on Demand
(CoD) processor resources and memory resources.

© Copyright IBM Corp. 2001, 2016 2-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

HMC education
Hardware Management Console (HMC) for Power with IBM i
This course is designed to familiarize the student with functions of the
HMC using lecture and lab. After completing this course, you should be
able to: Install an HMC and go through the setup wizard, connect the
HMC to a managed system, create, and manage partitions manually or
with a .sysplan, manage the HMC including updating code for the HMC
and firmware in the managed system

Hardware Management Console (HMC) for Power Systems with IBM i

Course code: OL52G Skill level: Intermediate
Duration: 2.0 days

http://www.ibm.com/training
Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-14. HMC education

This course is designed to familiarize students with functions of the HMC using lecture and lab
exercises.

© Copyright IBM Corp. 2001, 2016 2-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Review questions
1. What is the component needed to configure partitions,
configure CoD, and provide access to virtual consoles?
a. FSP
b. HMC
c. POWER Hypervisor
d. NVRAM

2. True or False: One HMC can control multiple managed

systems.

3. True or False: The HMC can be used with two different

software interface classic or enhanced.

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-15. Review questions

© Copyright IBM Corp. 2001, 2016 2-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Review answers
1. What is the component needed to configure partitions, configure CoD,
and provide access to virtual consoles?
a. FSP
b. HMC
c. POWER Hypervisor
d. NVRAM
The answer is HMC.

2. True or False: One HMC can control multiple managed systems.

The answer is True.

3. True or False: The HMC can be used with two different software
interface classic or enhanced.
The answer is True.

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-16. Review answers

© Copyright IBM Corp. 2001, 2016 2-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 2. Console options and HMC overview

Uempty

Unit summary
• Discuss the different consoles that can be used with Power with IBM i
• Describe the concepts of HMC
• List the different HMC models that are available
• Describe virtual HMC appliance
• Describe the differences between IVM, HMC
• Describe the different capacity on-demand options available

Console options and HMC overview © Copyright IBM Corporation 2001, 2016

Figure 2-17. Unit summary

© Copyright IBM Corp. 2001, 2016 2-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Unit 3. Basic management using HMC

Estimated time
01:15

Overview
The intention of this unit is not to replace the HMC course, but to explain some HMC functions that
allow the operator to use advanced work management. In addition, this unit explains some
virtualization aspects, like virtual Ethernet.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 3-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Unit objectives
• Explain how to dynamically change partition parameters like CPU,
Memory, Physical and Virtual Resources
• Explain how to set up virtual Ethernet between partitions
• Explain basic servers and partitions operations

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 3-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Topic 1: Dynamic logical

partitioning

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-2. Topic 1: Dynamic logical partitioning

© Copyright IBM Corp. 2001, 2016 3-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Partition profile

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-3. Partition profile

A partition profile is a record on the Hardware Management Console that specifies a possible set
of resource allocations and activation settings for a logical partition. To activate a logical partition,
you must activate one of the partition profiles for that logical partition. The managed system uses
the partition profile to configure the resources for the logical partition.
The partition profile is a separate entity from the logical partition. Changing the partition profile
properties does not automatically change the resource allocations for an active logical partition.
Similarly, changing the resource allocations for an active logical partition does not automatically
change the properties for any partition profile.

© Copyright IBM Corp. 2001, 2016 3-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Processing and Memory settings

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-4. Processing and Memory settings

On the visual you see the typical processing unit and memory configuration. It is important to
understand the minimum desired and maximum amount of processor / memory assigned to the
partition. After the partition is IPL'ed the resources are assigned to the partition in the desired level
if available. Using dynamical logical partitioning (DLPAR) you can increase or decreased to
minimum defined in the partition profile.

© Copyright IBM Corp. 2001, 2016 3-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

I/O adapters

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-5. I/O adapters

I/O and virtual I/O adapters can be assigned to a partition as desired or required. If I/O is required,
it cannot be moved until partition is stopped.

© Copyright IBM Corp. 2001, 2016 3-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Dynamic partitioning

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-6. Dynamic partitioning

Dynamic partitioning (DLPAR) allows you to dynamically (without start stop partition) manage
resources.
Right-click the partition name and from tasks choose Dynamic Partitioning now choose:
• Processor
• Memory
• Physical / Virtual Adapters
• Host Ethernet
• Select action:
▪ Add or Remove
▪ Move
On the next slide we show all the operations on processor resources, but this same way you can
dynamically manage other resources.
If want to manage I/O resources, it must be desired for partition.
Dynamic partitioning working with active partition.
Note: If you are dynamically adding resources or are creating some adapters you must modify the
partition profile, otherwise after the IPL is partitioned you will lose added or created dynamically
resources.

© Copyright IBM Corp. 2001, 2016 3-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Dynamic partitioning: Processor

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-7. Dynamic partitioning: Processor

Right-click the partition name and from tasks chose Dynamic Partitioning > Processor > Add or
Remove.
Add/Remove Processor Resources
Use this window to add processor resources to or remove processor resources from the selected
logical partition without restarting the logical partition.
When you add processors or processing units to a logical partition dynamically, you must meet the
following conditions:
• The number of processors or processing units that you add must be less than or equal to the
available number of processors or processing units.
• The number of processors or processing units that the logical partition will have must be less
than or equal to the maximum number of processors or processing units set for the logical
partition.
• If the logical partition uses shared processors, the number of virtual processors that the logical
partition will have must be equal to or greater than the number of processing units that the
logical partition will have, and less than or equal to the maximum number of virtual processors
set for the logical partition.

© Copyright IBM Corp. 2001, 2016 3-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
When you remove processor resources from a logical partition dynamically, you must meet the
following conditions:
• The number of processors or processing units that the logical partition will have must be less
than or equal to the maximum number of processors or processing units set for the logical
partition.
• If the logical partition uses shared processors, the number of virtual processors that the logical
partition will have must be equal to or greater than the number of processing units that the
logical partition will have, and less than or equal to the maximum number of virtual processors
set for the logical partition.
Right-click the partition name and from tasks chose Dynamic Partitioning > Processor > Move.
Move Processor Resources
Use this window to move processor resources from the selected logical partition to another logical
partition without restarting either logical partition.
• You can move processors or processing units dynamically between logical partitions if the
following conditions are met:
• The number of processors or processing units that you move must be less than or equal to the
movable number of processors or processing units on the source logical partition.
• The number of processors or processing units that the destination logical partition will have
must be less than or equal to the maximum number of processors or processing units set for the
destination logical partition.
• If the source logical partition uses shared processors, the number of virtual processors that you
move must be less than or equal to the movable number of virtual processors on the source
logical partition.
• If the destination logical partition uses shared processors, the number of virtual processors that
the destination logical partition will have must be greater than or equal to the number of
processing units that the destination logical partition will have, and less than or equal to the
maximum number of virtual processors set for the logical partition.

© Copyright IBM Corp. 2001, 2016 3-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Dynamic partitioning: Memory

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-8. Dynamic partitioning: Memory

Right-click the partition name and from tasks chose Dynamic Partitioning > Memory > Add or
Remove.
Add/Remove Memory Resources
Use this window to add memory resources to or remove memory resources from the selected
logical partition without restarting the logical partition.
When you add memory or processing units to a logical partition dynamically, you must meet the
following conditions:
• The amount of the memory that you add must be less than or equal to the available memory.
• The amount of the memory that the logical partition will have must be less than or equal to the
maximum amount of the memory set for the logical partition.
Right-click the partition name and from tasks chose Dynamic Partitioning > Memory > Move.
Move Memory Resources
Use this window to move memory resources from the selected logical partition to another logical
partition without restarting either logical partition.
You can move memory dynamically between logical partitions if the following conditions are met:

© Copyright IBM Corp. 2001, 2016 3-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
• The amount of the memory that you move must be less than or equal to the movable amount of
the memory on the source logical partition.
• The amount of the memory that the destination logical partition will have must be less than or
equal to the maximum amount of the memory set for the destination logical partition.

Note

Depending on how busy the system is, removing or moving memory might not run at once. And it
might need to be repeated.

© Copyright IBM Corp. 2001, 2016 3-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Dynamic partitioning: Physical Adapters

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-9. Dynamic partitioning: Physical Adapters

When you add an I/O slot to a logical partition, the I/O adapter in that I/O slot and the devices that
are controlled by the I/O adapter can be used by the logical partition. This function is typically used
to share infrequently used devices among logical partitions by moving these devices from one
logical partition to another.
Right-click the partition name and from tasks chose Dynamic Partitioning > Physical Adapters >
Add or Remove.
Right-click another partition and from tasks chose Dynamic Partitioning > Memory > Move.

© Copyright IBM Corp. 2001, 2016 3-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Dynamic partitioning: Virtual Adapters

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-10. Dynamic partitioning: Virtual Adapters

Dynamic partitioning for virtual adapters, you can only add, create, or delete it. You can add the
following virtual adapters:
• Ethernet
• Fibre Channel
• SCSI
• Serial

Note

Before you start creating new virtual adapters check the current number of virtual adapters and
available maximum. If both values are equal, you have to change the partition profile definition.

Right-click the partition name and from tasks chose Dynamic Partitioning > Virtual Adapters >
Action > Create Virtual Adapter.
To delete the virtual adapter, select it and then chose Action > Delete.

© Copyright IBM Corp. 2001, 2016 3-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Create Virtual Adapter: Ethernet Adapter

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-11. Create Virtual Adapter: Ethernet Adapter

This course does not cover all HMC tasks, but from an Advanced Operator perspective it could be
useful to know how two partitions communicate without a physical Ethernet adapter. To do this you
can add it by dynamical creation of the Ethernet virtual adapter (if necessary you have to create it
on both partitions).
To create virtual Ethernet adapter right-click the partition name and from tasks chose Dynamic
Partitioning > Virtual Adapters > Action > Create Virtual Adapter > Ethernet Adapter.

© Copyright IBM Corp. 2001, 2016 3-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Virtual Ethernet Adapter: General and Advanced

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-12. Virtual Ethernet Adapter: General and Advanced

Create/Edit Virtual Ethernet Adapter

Use this window to enter, view, or change the properties for a virtual Ethernet adapter on this logical
partition or partition profile. Virtual Ethernet adapters can form Virtual Local Area Networks (LANs)
automatically if you specify the same virtual LAN ID for each virtual Ethernet adapter.
You can create up to 4094 virtual LANs using virtual Ethernet adapters.
Each virtual LAN is identified by a virtual LAN ID number. Virtual Ethernet adapters can
communicate with each other only if they are assigned the same virtual LAN ID number.
A Virtual Switch (VSwitch) is used to allow the virtual Ethernet adapter to route through a physical
adapter to an external network.
When you create a virtual Ethernet adapter, the managed system automatically assigns a Media
Access Control (MAC) address to the virtual Ethernet adapter. MAC addresses are used to identify
Ethernet adapters on a network. The MAC address that the managed system assigns to the virtual
Ethernet adapter is unique within the managed system. However, this MAC address is not
universally unique, and might not be unique within a network containing multiple managed systems.
Having multiple virtual Ethernet adapters with the same MAC address can cause network
problems. To resolve these problems, you can change the MAC address prefix assigned to the
POWER6 or POWER7 processor-based server using the Hardware Management Console (HMC)

© Copyright IBM Corp. 2001, 2016 3-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
chhwres command. The managed system prefix is used to build the partition virtual Ethernet MAC
addresses during partition activation.
Additionally, in specific POWER7 processor-based servers, you have the option of specifying a
complete custom MAC address instead of using one that is automatically generated by the HMC.

Note

To determine whether a POWER7 processor-based server provides the capability to customize the
whole MAC address instead of only the MAC address prefix, run the lssyscfg command using
the '-F capabilities' option. If the custom_mac_addr_capable capability is listed for the POWER7
processor-based server, then the whole MAC address can be customized for any virtual Ethernet
adapter. Otherwise, only the MAC address prefix can be changed for the virtual Ethernet adapter.

Beginning with POWER7 processor-based servers, you can use the Edit option to modify the IEEE
802.1Q Compatible adapter, Additional VLANs, and QoS priorities of the Virtual Ethernet Adapter
during dynamic logical partitioning operation.
Current settings for the Virtual Ethernet adapter are listed at the bottom of the panel. Information on
these settings can be found in the detailed help below. The Create Virtual Ethernet Adapter panel
has the following two tabs:
General
• Use this tab to enter the virtual ID, vSwitch, VLAN ID, and select the optional settings.
• You can find more detailed help on the following elements of this window:
▪ Adapter ID
- Specify the slot number to use for this virtual Ethernet adapter. The slot number is used
to identify the virtual adapter within the logical partition. (The combinations of the slot
number and the logical partition ID uniquely identify this slot within the managed
system.)
- This slot number does not refer to any physical hardware location on your system.
Therefore, you can assign slot numbers to virtual adapters in any way that makes sense
to you, provided that you follow the following guidelines:
○ You can use any slot number from 2 up to (but not including) the maximum number
of virtual adapters. (Slots 0 and 1 are reserved for system-created virtual adapters. If
the logical partition is a Virtual I/O Server logical partition, other slot numbers might
also be reserved.) For example, if the maximum number of virtual adapters is 10,
and the logical partition is not a Virtual I/O Server logical partition, you can use any
slot number from 2 to 9. By default, the system displays the lowest unused slot
number for this logical partition.
○ You cannot use a slot number that was used for any other virtual adapter on the
same logical partition.

© Copyright IBM Corp. 2001, 2016 3-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
▪ VSwitch
- Select a VSwitch from the list to which you want to connect the virtual Ethernet adapter.
You can create multiple VLAN adapters in a partition by using the virtual switches
(VSwitches). These adapters can route through different physical adapters to the
external network by using VSwitches. The VSwitch (VSwitch0) is defined by default.
▪ Port Virtual Ethernet (VLAN ID)
- Specify the ID number for the Virtual Local Area Network (LAN) to which you want to
connect this virtual Ethernet adapter. This virtual LAN ID number can be any whole
number from 1 to 4094.
▪ View Virtual Network
- Select View Virtual Network to view Virtual Switch (VSwitch) and Virtual LAN (VLAN)
configurations.
From this task, you can:
○ View existing VSwitches and their associated VLANs
○ Create a new VSwitch
- VSwitches are created using this task. VLANs are created when a partition with a VLAN
defined is activated. For more information on managing virtual networks, select Help
from the Virtual Network Management panel.
▪ Optional Settings
- Select IEEE 802.1q compatible adapter or Access external network to set these optional
settings for the virtual Ethernet adapter.
You can find more detailed help on the following elements of this page:
○ IEEE 802.1 compatible adapter
- Select this option to add this virtual Ethernet adapter to additional Virtual Local Area
Networks (LANs) as specified in the IEEE 802.1Q network standard. Selecting this
option allows you to specify additional virtual LAN IDs for the adapter.
- Not all versions of all operating systems support the IEEE 802.1Q network standard. If
the operating system does not support the IEEE 802.1Q network standard, the virtual
Ethernet adapter can connect to only one virtual LAN (as identified by VLAN ID).
- You can find this option only if Hardware Management Console (HMC) supports the
power hypervisor capability.
▪ New VLAN ID
- Specify the ID number for any additional Virtual Local Area Networks (LANs) to which
you want to connect this virtual Ethernet adapter and click Add. This virtual LAN ID
number can be any whole number from 2 to 4094. Beginning with POWER7
processor-based servers, you can specify a range of VLANs or a comma separated list
of VLANs and can modify the VLAN ID dynamically while the logical partition is active.
▪ Additional VLANs
- This option is visible when you select IEEE 802.1 compatible adapter.

© Copyright IBM Corp. 2001, 2016 3-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
- Lists the ID numbers of any additional Virtual Local Area Networks (LANs) to which the
virtual Ethernet adapter belongs. To remove the virtual Ethernet adapter from a virtual
LAN, select the virtual LAN here and click Remove.
▪ Access external network
- Indicate whether this virtual Ethernet adapter is the trunk adapter on this Virtual Local
Area Network (LAN).
- A trunk adapter is an Ethernet adapter that links its LAN to an external network. If a data
transmission on the virtual LAN is addressed to an Ethernet adapter that does not exist
on the virtual LAN, the data transmission is sent to the trunk adapter. The trunk adapter
can then forward the data transmission to an external network.
- Selecting this option will not automatically connect the virtual LAN to an external
network. You must also configure the operating system of the logical partition to forward
information to the external network.
- Not all versions of all operating systems support trunk adapters. Your operating system
might support other methods for connecting logical partitions to external networks. To
determine which method is appropriate for your situation, consult the documentation for
your operating system.
- A virtual LAN can have only one active trunk adapter at a time. You can create only one
trunk adapter for each virtual LAN on your managed system unless you are creating
redundant trunk adapters for virtual trunk adapter failover capability. If you create
redundant trunk adapters for virtual trunk adapter failover capability, you must follow
these rules when creating these adapters:
○ The virtual LAN ID in Virtual LAN ID must match for all redundant trunk adapters.
○ The trunk priority in Trunk priority must be unique for each redundant trunk adapter.
○ All of the virtual LAN IDs in Additional VLANs must match for all redundant trunk
adapters.
Advanced
Beginning with POWER7 processor-based servers, you can use this tab to configure advanced
options for your virtual Ethernet adapter. When adding a virtual Ethernet adapter to a logical
partition, you can configure a custom MAC address for the adapter and specify restrictions for
operating system-defined MAC addresses. If the managed system provides support for quality of
service, you also can specify a priority for network communications for the adapter. You can edit the
QoS priorities using the dynamic logical partitioning operation when the partition is running.
Advanced properties
▪ Default MAC Address
- The MAC address is automatically generated by the Hardware Management Console
(HMC). Beginning with POWER7 processor-based servers, you have the option of
specifying a custom MAC address. This field displays a value of auto-assigned unless
you choose to specify a custom MAC address by selecting the Override option.

© Copyright IBM Corp. 2001, 2016 3-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
▪ Override
- Select this option if you want to specify a custom MAC address for the virtual Ethernet
adapter.
▪ Custom MAC address
- If you select Override, you can specify a custom MAC address.
- The MAC address is a 12-character hexadecimal string. The valid characters are from 0
to 9 and A to F. The characters are not case-sensitive. There are two rules for MAC
addresses: Bit 1 of byte zero of the MAC addresses, for example: mask
0x010000000000, is reserved for Ethernet multicasting and must always be '0'. Bit 2 of
byte zero of the MAC addresses must always be '1', as it indicates that the MAC is a
locally administered address. For example, these virtual Ethernet MAC addresses follow
the rules: FE:00:00:00:00:00, F2:00:00:00:00.
▪ Maximum quality of service
- The QoS setting on the virtual adapter is a maximum value. It will limit the outgoing
packets to that priority by lowering any packet priority that is greater than the max, but
any lower priority packet will remain at its current priority.
- You can select one of the following values for the priority level:
1. 1 - background
2. 2 - spare
3. 0 (default) - best effort
4. 3 - excellent effort
5. 4 - controlled load
6. 5 - video (less than 100 ms latency and jitter)
7. 6 - voice (less than 10 ms latency and jitter)
8. 7 - network control
▪ MAC Address Restrictions
- You can choose the following values for any operating system-defined MAC addresses.
▪ Allow all O/S Defined MAC Addresses
- Select this option to allow any operating system-defined MAC addresses. This is the
default value.
▪ Deny all O/S Defined MAC Addresses
- This option does not allow any operating system-defined MAC address(es).
▪ Specify Allowable O/S Defined MAC Addresses
- Select this option to specify a maximum of four operating system-defined MAC
addresses that are allowed.
▪ Allowed MAC Address
- Specify a MAC address in the Allowed MAC Address field and click Add.

© Copyright IBM Corp. 2001, 2016 3-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
- This adds the address to the Allowed MAC Address(es) list. You can specify a maximum
of four MAC addresses.
- Click Remove to delete a MAC Address from the list.
▪ Virtual Station Interface
- VSI Type ID
○ Specify the type ID of the VSI profile.
▪ VSI Type Version
- Specify the version number of the VSI profile.
▪ VSI Manager ID
- Specify the ID of the VSI manager.

© Copyright IBM Corp. 2001, 2016 3-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Work with Communications Resources display

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-13. Work with Communications Resources display

Note all virtual devices have a letter in type like 268C. When you create new device check it using
WRKHDWRSC *CMN for communication devices.

© Copyright IBM Corp. 2001, 2016 3-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Topic 2: Additional useful

functions

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-14. Topic 2: Additional useful functions

© Copyright IBM Corp. 2001, 2016 3-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Serviceability

Start Control Panel Functions like

21 Dedicated Service Tools
(all available only for IBM i)

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-15. Serviceability

For each partition you can view / manage serviceable events and see Reference Codes.
Additionally when you need to run DST (dedicated service tools) you can activate it using Control
Panel function 21 (active console 5250 session is required to use this function).
From Tasks (bottom of screen) expand Serviceability > Manage Serviceable Events > Manage
Serviceable Events.
Use this window to select the criteria for the set of serviceable events you want to view. When you
finish selecting the criteria, you can view the serviceable events that match your specified criteria.
Select ALL if you do not want the results filtered.
Event criteria
Serviceable event status: Select one event status to filter the problems you want to view. You can
view Open or Closed events.
Problem Number: Select one problem number to filter the problems you want to view.

© Copyright IBM Corp. 2001, 2016 3-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
Error criteria
Reporting system MTMS: Select ALL to view all events for all reporting systems or select the
machine type-model/serial number (MTMS) of the system that reported the serviceable events that
you want to view. The list of MTMS is in the following format: TTTT-MMM/NNNNNNN, where TTTT
is the machine type, MMM is the model number, and NNNNNNN is the serial number.
Failing enclosure MTMS: Select ALL to view all units that failed or select the machine
type-model/serial number (MTMS) of a specific unit that failed and generated the serviceable
events that you want to view. This field lists only those units for which serviceable events are
available.
Reference code: Select one reference code to filter the problems you want to view. This lists only
reference codes for which serviceable events are available.
Number of days: Specify the number of days of past events to view, starting with today to filter the
problems you want to view. The range is 1, 7, 14, or 30.
Field-Replaceable Unit (FRU) criteria
Part number: Select one part number to filter the problems you want to view.
Location code: Select one location code to filter the problems you want to view.
From the Tasks (bottom of screen) expand Serviceability > Reference Code History.
Reference Code History (Partition): Use this window to view reference codes that have been
generated for the selected logical partition. Reference codes are diagnostic aids that help you
determine the source of a hardware or operating system problem.
By default, only the most recent reference codes that the logical partition has generated display on
this window. To view more reference codes, enter the number of reference codes that you want to
view into View history and click Go. The window displays that number of the latest reference codes,
with the date and time at which each reference code was generated. The window can display up to
the maximum number of reference codes stored for the logical partition.
The details displayed in the Reference Codes table are as follows:
Time stamp: This column displays the date and time at which each reference code was
generated in Coordinated Universal Time (UTC).
Code: This column displays each reference code that was generated for the logical partition.
You can click the reference code to see whether there is any additional descriptive text for the
reference code.
FRU callout: This column displays the Field Replaceable Unit (FRU) numbers for the FRUs
whose absence or failure caused each reference code to be generated.
You can select any of the reference codes in the table to more detailed information about the
reference code in the Details table. The Details table displays hexadecimal words that can
provide additional information about the problem that caused this reference code to be
generated.
From Tasks (bottom of screen) expand Serviceability > Control Panel Function.
Now you can run some Control Panel functions for example function 21 DST.

© Copyright IBM Corp. 2001, 2016 3-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Operations: Power Off

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-16. Operations: Power Off

Power Off: This task shuts down the managed system. Turning off the managed system makes all
partitions unavailable until the system is turned on again.
Normal power off: The system ends all active jobs in a controlled manner. During that time,
programs running in those jobs are allowed to perform cleanup (end-of-job processing).
Fast power off: The system ends all active jobs immediately. The programs running in those jobs
are not allowed to perform any cleanup.

Note

Powering down a server with running partitions is not recommended, shutdown all partitions first. If
you Power Off with running partitions a warning window will appear.

© Copyright IBM Corp. 2001, 2016 3-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Operations: Power On

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-17. Operations: Power On

Power On: Use the Power On task to start a managed system. You can choose from two different
options to start your managed system:
• Normal: Turns on the managed system to partition standby mode and then activates all
partitions that are marked as auto start or those partitions that were running when the system
shutdown.
• Hardware Discovery: Selecting this Power On option specifies that the HMC run the hardware
discovery process when the managed system powers on. The hardware discovery process
captures information about all I/O devices: In particular those devices not currently assigned to
partitions.

© Copyright IBM Corp. 2001, 2016 3-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Managed system states (1 of 2)

• Only service processor powered on:

ƒ No Connection
í HMC cannot locate required managed system
ƒ Pending Authentication
í Service processor password must be updated
ƒ Failed Authentication
í Service processor password is incorrect
ƒ Error
í Problem with hardware or operating system
ƒ Error - Dump in Progress
í The managed system encountered an error and is performing a system dump

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-18. Managed system states (1 of 2)

This visual lists some of the states that will be displayed on the HMC. At this point, only the four
states listed under Service Processor Powered on apply.
• No Connection: This is a cause for concern because the HMC cannot connect to the managed
system specified.
• Pending Authentication: This requires the service processor password to be updated.
• Failed Authentication: The service processor password is incorrect.
• Error: The operating system or the hardware of the managed system is experiencing errors.
• Error - Dump in Progress: The managed system encountered an error and is performing a
system dump.
After you activate the managed system and create or activate partitions, you will see the other
states (and more), which are applicable to the powered on managed system and partitions. These
will be discussed later.

© Copyright IBM Corp. 2001, 2016 3-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Managed system states (2 of 2)

• Managed system powered on:

ƒ Initializing ƒ Incomplete
ƒ Standby ƒ Recovery
ƒ Operating ƒ Service Processor Failover in Progress
ƒ Power Off ƒ Version Mismatch
ƒ Error – Terminated
ƒ On-Demand Recovery

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-19. Managed system states (2 of 2)

Initializing: The managed system is powered on and is initializing. The initialization time might vary
depending on the hardware and the partition configuration of the managed system.
Standby: The managed system is powered on using the Power on standby option. It will stay in this
state until a logical partition is activated. You can create and modify logical partitions while the
managed system is in this state.
Operating: The managed system initialized and is operational.
Error - Terminated: The managed system encountered an error and has performed a system
dump.
On Demand Recovery: The anchor card (also known as the system VPD card) on this managed
system was replaced. You must enter replacement activation codes for Capacity on Demand or
Virtualization Engine system technologies. On/Off CoD requests must be restarted
Powering Off: The managed system is powering off normally.

© Copyright IBM Corp. 2001, 2016 3-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
Incomplete: The HMC failed to get all of the necessary information from the managed system.
Refresh the internal representation of the managed system on the HMC using the Rebuild task.
The Rebuild operation does not disrupt the operation of the running server. If the rebuild is
unsuccessful, refer to the Correcting an Incomplete State for a Managed System topic in the
Managing the HMC v7 Guide publication. You can access this HMC publication and other useful
HMC documentation either in the PDF or HTML format from the Additional Resources section in the
HMC Welcome page.
Recovery: The save area in service processor is not synchronized with the HMC database.
Service Processor Failover In Progress: The primary service processor in the managed system
is performing an administrative failover and transferring system management to the secondary
service processor. This transfer is in progress.
Version Mismatch: This version of HMC is unable to manage the system. Update the HMC
Licensed Internal Code.

© Copyright IBM Corp. 2001, 2016 3-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Topic 3: Managed server

partition tasks

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-20. Topic 3: Managed server partition tasks

© Copyright IBM Corp. 2001, 2016 3-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Partition task selection

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-21. Partition task selection

To work with partitions on a server: Click the name of the managed system under the Server tab.
On the main pane you will see a partition or partitions. You must select the partition and then
perform the task.
Systems Management > Servers > click chosen server name.

© Copyright IBM Corp. 2001, 2016 3-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Partition tasks

• Multiple ways to view tasks

• Tasks are different on remote sessions versus native HMC

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-22. Partition tasks

When the partition has been selected, there are three ways to view the tasks that can be
performed. They are:
• Using the Tasks list at the top of the screen.
• Using the Tasks menu located in the bottom of the screen.
• Clicking the arrow next to the name on the selected partition.

© Copyright IBM Corp. 2001, 2016 3-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Operations: Activate (1 of 2)

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-23. Operations: Activate (1 of 2)

Right-click the partition name click Activate > Profile.

Use the Activate partition profile task to start a single logical partition. Select a profile to use when
activating the partition from the list of profiles displayed.

© Copyright IBM Corp. 2001, 2016 3-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Operations: Activate (2 of 2)

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-24. Operations: Activate (2 of 2)

You can choose to work with a terminal window or console session when the partition is activated
by selecting Open a terminal window or console session.

Note

On the remote web browser connection to the HMC, the Open a terminal window or console
session is not available for IBM i type partitions. You can use you Open console session only locally
on HMC.

To run Console 5250 remotely you have to use IBM i Access Client Solutions.
Click Advanced for more options on activating the partition.
Alternatively, you can use the Activate - Current Configuration task to quickly start multiple
logical partitions by using the current configuration information for the partitions that is available on
the hypervisor.
Advance: Use the Advanced window to set options for the logical partition that you are activating.
No VSI Profile: Select this check box to ignore the failure in configuring the VSI profile and to
continue to activate the partition.

© Copyright IBM Corp. 2001, 2016 3-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty
Keylock position: Select a keylock position. The keylock position establishes the power-on and
power-off modes allowed for the system. Possible values are:
• Do not Override: Uses the current partition setting.
• Manual: After the partition is powered on, operating the managed system in manual (attended)
mode means that an operator uses the control panel to direct the managed system for special
needs. For security reasons, it is not preferred that you set the keylock position to Manual.
• Normal: After the partition is powered on, operating the managed system in Normal
(unattended) mode during the restart operation does not require the support of an operator.
For IBM i logical partitions
IPL type: Displays the IPL type of the partition. Possible values are:
• Do not Override: Uses the current partition setting.
• IPL type A: Use IPL type A when directed for special work, such as diagnostic work.
• IPL type B: Use IPL type B for routine work.
• IPL type C: This type of IPL is reserved for hardware service representatives.
• IPL type D: Use IPL type D when directed for special work, such as installing and reloading
programs. IPL type D loads the system programs from an alternate IPL load source, such as a
tape drive or CD-ROM.
For AIX or Linux logical partitions:
Boot mode: Displays the boot mode of this partition. This field is available only for the AIX or Linux
partitions. This field is disabled, when you are installing a VIOS image on a VIOS partition. For AIX
or Linux boot mode, the possible values are:
• Do Not Override: Uses the setting in the profile user selected here.
• Normal: The logical partition starts up as normal. (This is the mode that you use to perform
most everyday tasks.)
• SMS: The logical partition boots to the System Management Services (SMS) menu.
• Diagnostic with default boot list: The logical partition boots using the default boot list that is
stored in the system firmware. This mode is normally used to boot customer diagnostics from
the CD-ROM drive. Use this boot mode to run standalone diagnostics.
• Diagnostic with stored boot list: The logical partition performs a service mode boot using the
service mode boot list saved in NVRAM. Use this boot mode to run online diagnostics.
• Open Firmware OK prompt: The logical partition boots to the open firmware prompt. This
option is used by service personnel to obtain additional debug information.
• Install Virtual I/O Server: This option is available only when the partition is a Virtual I/O Server.
When a VIOS image is being installed, this option is selected by default and the field is grayed.

© Copyright IBM Corp. 2001, 2016 3-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Review questions
1. When defining a partition’s processors, why is the minimum
number of processors important?
a. You cannot go below this number of processors while the
partition is active.
b. If the wanted number of processors is not available (but if this
minimum necessary number is), the partition will still activate.
c. Both a and b.

2. True or False: You can activate DST using HMC.

3. True or False: You cannot dynamical add Virtual Ethernet

Adapter.

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-25. Review questions

© Copyright IBM Corp. 2001, 2016 3-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Review questions
1. When defining a partition’s processors, why is the minimum
number of processors important?
a. You cannot go below this number of processors while the
partition is active.
b. If the wanted number of processors is not available (but if this
minimum necessary number is), the partition will still activate.
c. Both a and b.
The answer is both a and b. You cannot go below this number
of processors while the partition is active and if the wanted
number of processors is not available (but if this minimum
necessary number is), the partition will still activate.

2. True or False: You can activate DST using HMC.

The answer is true.

3. True or False: You cannot dynamical add Virtual Ethernet

Adapter.
The answer is False.
Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-26. Review questions

© Copyright IBM Corp. 2001, 2016 3-37

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 3. Basic management using HMC

Uempty

Unit summary
• Explain how to dynamically change partition parameters like CPU,
Memory, Physical and Virtual Resources
• Explain how to set up virtual Ethernet between partitions
• Explain basic servers and partitions operations

Basic management using HMC © Copyright IBM Corporation 2001, 2016

Figure 3-27. Unit summary

© Copyright IBM Corp. 2001, 2016 3-38

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Unit 4. IBM i Access Family overview

Estimated time
00:30

Overview
This unit describes the concepts and capabilities of the IBM i Access Family of software. It also
specifically explores one of those products - IBM i Access Client Solutions.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 4-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Unit objectives
• Describe the features and capabilities of the IBM i Access Family of
products
• Describe the installation and use of IBM i Access Client Solutions
• List reference documentation

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 4-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Topic 1: Overview of IBM i

Access Family

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-2. Topic 1: Overview of IBM i Access Family

© Copyright IBM Corp. 2001, 2016 4-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

IBM i Access Family

• IBM Access Family of Products
ƒ IBM i Access for Windows (5770XE1)
í Client Access
í
ƒ IBM i Access for Web (5770XH2)
í IBM i system hosted HTML based web product

ƒ IBM i Access Client Solutions (5733XJ1)

í Java based, platform-independent interface that runs on most operating systems
that support Java

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-3. IBM i Access Family

The IBM i Access Family of products provide easy to use, out of the box solutions for accessing
IBM i resources. These four products include alternatives for you to use to work with your business
applications and resources on IBM i. For example:
• The Windows-based solution provides more functional capabilities for the IBM i environment
than any other Windows-based product in the marketplace. Not only does it provide a very
high-function 5250 native Windows emulator, but it also provides key database access through
an easy-to-use GUI. It also provides drivers (such as ODBC, OLDB, and .NET) so that
Windows applications can access IBM i/OS resources. It also contains the System i Navigator
functions of Management Central, which is the GUI system management for IBM i.
• The web-based solution enables desktop users to connect to IBM i through their browsers.
This option requires no special software to be installed or configured on the desktop. The
desktop users can start up any browser (for example, Internet Explorer, Netscape, Firefox,
Mozilla, or Opera, and have the same look-and-feel when connecting to IBM i. Additionally, the
actual desktop operating system is completely transparent; thus allowing users with many
dissimilar desktop operating systems to connect to IBM i and see the same presentation.
• IBM i Access Client Solutions provides a Java based, platform-independent interface that runs
on most operating systems that support Java, Mac, and Windows™. This option requires a
simple “deployment” of the executable code to the workstation of choice.

© Copyright IBM Corp. 2001, 2016 4-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

IBM i Access for Windows

• Access for Windows Base (5770-XW1)
• Access for Windows (5770-XE1)

IBM does not plan to support IBM i Access for Windows on operating
systems beyond Windows 8.1.

The replacement product is IBM i Access Client Solutions, which includes

5250 emulation, data transfer, printer output, console support, and more.

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-4. IBM i Access for Windows

IBM i Access for Windows delivers TCP/IP connectivity to users running a variety of Microsoft
Windows operating systems. IBM i Access for Windows offers an all-inclusive client solution for
accessing and using resources from your Windows desktop.
It includes 5250 emulation, access to DB2 for IBM i through its Data Transfer, and utilizes IBM i
NetServer for working with the IBM i integrated file system and printers. It also has a variety of
middleware for using and developing client applications to access IBM i resources; and System i
Navigator (Management Central), the IBM i GUI, for administering your IBM i.
The use of PC5250 and Data Transfer in IBM i Access for Windows requires an IBM i Access
Family (5770-XW1) license.

© Copyright IBM Corp. 2001, 2016 4-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

IBM i Access for Web

• Access for Windows Base (5770-XW1)
• Access for Windows (5770-XH2):
ƒ Database Access
ƒ 5250 Display
ƒ IFS Access
ƒ Commands
ƒ Print Access
ƒ Job Access

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-5. IBM i Access for Web

IBM i Access for Web offers browser-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 through a web browser.
With it users can run batch commands, access the database as well as the integrated file system,
work with printers, printer output, and messages. A 5250 interface is also available.
Even though there is no code running on the workstation, IBM i Access for Web requires an IBM i
Access Family (5770-XW1) license on the target IBM i server.

© Copyright IBM Corp. 2001, 2016 4-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

IBM i Access Client Solutions

• Access for Windows Base (5770-XW1)
• Access for Windows (5733-XJ1):
ƒ Data transfer/DB access
ƒ 5250 Display emulator
ƒ Navigator for i
í Command execution
í Print Access
í Job Access

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-6. IBM i Access Client Solutions

IBM i Access Client Solutions is new to the IBM i Access Family. It offers browser-based access to
IBM i. It runs on any platform that supports Java 6.0 or later including Windows, Mac, Linux, AIX, or
IBM i systems.
With it users can create and manage 5250 emulation sessions, access and transfer data, work with
printer output and manage their jobs. Executable code is deployed to the Java supported
workstation and this code provides the function. Nothing is installed on the client. Just download,
unpack, and execute the code. The target IBM i server requires an IBM i Access Family
(5770-XW1) license.

© Copyright IBM Corp. 2001, 2016 4-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Topic 2: Overview of IBM

Navigator for i

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-7. Topic 2: Overview of IBM Navigator for i

© Copyright IBM Corp. 2001, 2016 4-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

IBM Navigator for i window

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-8. IBM Navigator for i window

Navigator for i is a web-based graphical interface for accessing and managing resources and jobs
using a web browser.
The system management tasks in Navigator for i include System Tasks, Basic operations, Work
Management, Configuration and Service, Network, Integrated Services Administration, Security,
Users and Groups, Databases, Journal Management, Performance, File Systems, Internet
Configurations, and more.
This GUI display provides an advantage to operators, administrators, and users who do not have
an extensive knowledge of control language (CL) commands.
In this example, the Basic Operations folder has been opened and a tab with those commonly used
basic operations, is displayed.

© Copyright IBM Corp. 2001, 2016 4-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

IBM Navigator for i main window

• System Tasks • Application Administration
• Basic Operations • Journal Management
• Work Management • Integrated Server Administration
• Configuration and Service
• Network
• Internet Configuration
• Security
• Users and Groups
• Database
• File Systems
• Backup
ƒ BRMS
plug-in

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-9. IBM Navigator for i main window

System Tasks include viewing system status, messages, disk status, system passwords,
application administration, and 5250 emulation.
Basic Operations allow you to easily manage lists of messages, printer output, and printers.
Work Management functions control the work done on the system. When the IBM i licensed
program is installed, it includes a work management environment that supports all interactive and
batch work. In addition, work management contains the functions you need to distribute resources
for your applications so that your system can handle your applications.
Configuration and Service provides functions to help you manage both hardware and software on
your system.
Network allows you to work with TCP/IP configuration, remote access services, networking
servers, IP policies, and integrated servers.
Internet Configuration allows you to work with the IBM i Internet configuration tasks such as
HTTP servers, Digital Certificates and more.
Security functions allow you to plan and implement security on your system.
Users and Groups displays a complete list of the users and groups on a system. You can use this
functional area to manage users and groups.

© Copyright IBM Corp. 2001, 2016 4-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty
Database is a graphical interface that you can use to perform many of your common administrative
database operations. Most of the IBM Navigator for i operations are based on Structured Query
Language (SQL), but you do not need to fully understand SQL to perform them.
File Systems are a part of IBM i that supports stream input/output and storage management
similar to personal computer and UNIX operating systems. They also provide a similar hierarchical
directory structure. Click File Systems to display a list of all IBM i file systems to which you are
authorized. You can access IBM i objects by specifying the path through the directories to the
object.
BRMS Backup, Recovery and Media Services helps you to easily manage complex saves, restores
and their media.
Application Administration allows the setting of access to functions or applications by your users.
Journal Management allows you to manage journal and journal receiver objects. A journal is an
object that records changes to files by sending information about the change to a journal receiver.
Integrated Server Administration combines the ease-of-use of a Windows, Linux, or VMware
server with the dependability and power of IBM i, giving you the flexibility to enroll and manage
users and groups, greater accessibility and protection for your data, and simplified administration.

© Copyright IBM Corp. 2001, 2016 4-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Topic 3: Using IBM i Access

Client Solutions

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-10. Topic 3: Using IBM i Access Client Solutions

© Copyright IBM Corp. 2001, 2016 4-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Platform independent
• Runs anywhere that has Java.
ƒ Java 6.0 or later

• This includes:
ƒ Windows
ƒ Mac
ƒ Linux
ƒ AIX
ƒ IBM i

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-11. Platform independent

IBM i Access Client Solutions (ACS) need only be “deployed” to any Java supported platform. To
“deploy” the product, it must first be downloaded. The download consists of zipped configuration
and executable files. Next, the downloaded code must be unpacked to the media from which it will
be run, such as a local hard drive, network shares, or a thumb drive. You are then ready to use the
product to connect to the IBM i server. The simple steps are outlined below:
a. Download the product from IBM.
b. Unzip the download to the run media.
c. Run the startup program to initiate the product.
d. Define one or more target IBM i servers.

© Copyright IBM Corp. 2001, 2016 4-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Download Access Client Solutions

http://www-03.ibm.com/systems/power/software/i/access/solutions.html

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-12. Download Access Client Solutions

On the IBM i Access Client Solutions web page, there are two different downloads of the product
available. One is called the evaluation version (70 days) to preview. It is the current product and
can be downloaded by anyone with an IBM ID and password. This is by far the easiest way to get
your hands on ACS. Just click the “Download IBM i Access Client Solutions base package” link,
key in your IBM ID and password when prompted and the download will be initiated. If you want to
extend usage you have to have license.
You can also download IBM i Access Client Solutions and the two optional platform-specific
packages which include middleware for using and developing client applications. These two
packages are:
IBM i Access Client Solutions - Windows Application Package for Windows operating systems.
Features include:
• Connectivity to DB2 for i using ODBC, .Net, and OLE DB
• Programming Toolkit for accessing IBM i system objects
• Support for TLS/SSL connections
• AFP printer driver

© Copyright IBM Corp. 2001, 2016 4-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty
IBM i Access Client Solutions - Linux Application Package for Linux operating systems.
Features include:
• Connectivity to DB2 for i using ODBC
• Full support for 64-bit ODBC data types
• TCP/IP connectivity
Base ACS product and both packages can only be download from the Entitled Software Support
(ESS) website This requires an IBM ID and password as well as an IBM customer number for the
software support.

© Copyright IBM Corp. 2001, 2016 4-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Unzip the download

Examine the Documentation and Start_Programs folders.

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-13. Unzip the download

Here are the folders and files that are unzipped to your location of choice. The Documentation
folder has GettingStarted.txt files in multiple languages. Read this document. It has detailed
information about the contents of the folders that you have unzipped as well as instructions on how
to start ACS.
The Start_Programs folder contains various platform-specific start programs for ACS. By clicking
the appropriate start program for your platform, you will initiate ACS.

© Copyright IBM Corp. 2001, 2016 4-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Run the startup program

GettingStarted.txt
Startup program

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-14. Run the startup program

The visual illustrates the section of the GettingStarted.txt file that describes the
platform-specific start programs that are available for ACS. Each start program is found in its own
folder. A double-click of this startup program initiates ACS. You might want to send a shortcut of
your startup program to your desktop to facilitate later starts.

© Copyright IBM Corp. 2001, 2016 4-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Define the target IBM i (1 of 2)

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-15. Define the target IBM i (1 of 2)

Once IBM i Access Client Solutions has been started, target systems can be defined and
connected by using 5250 emulation, Navigator for i, or data transfer. Click System Configuration
under Management tasks. The System Configuration window is displayed. Any previously defined
systems are displayed in this window. Click New to define an additional system.

© Copyright IBM Corp. 2001, 2016 4-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Define the target IBM i (2 of 2)

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-16. Define the target IBM i (2 of 2)

The Add New System window is displayed. Key the system name or IP address and a description
into the prompts on the General tab. Click the Connection tab in order to designate how password
rules are to be handled. Select use a default user name to prompt for each system or prompt for the
user name and password every time. Click the General tab in order to return. From the General
tab, click the Verify button in order to verify the server connection.

© Copyright IBM Corp. 2001, 2016 4-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Use Access Client Solutions

• Use the pull-down to select a system
• Start Navigator for i
• Start 5250 Emulation
• Manage printer output
• Start data transfer
• Run SQL
• Start Virtual Control Panel

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-17. Use Access Client Solutions

Return to the IBM i Access Client Solutions display and select a system using the pull-down. Now
ACS is ready to connect to the IBM i using the facility of choice by clicking the appropriate option.

© Copyright IBM Corp. 2001, 2016 4-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Topic 4: Reference
documentation

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-18. Topic 4: Reference documentation

© Copyright IBM Corp. 2001, 2016 4-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

IBM i Access Family

http://www-03.ibm.com/systems/power/software/i/access/index.html
IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-19. IBM i Access Family

To access this website, go to:

http://www-03.ibm.com/systems/power/software/i/access/index.html

© Copyright IBM Corp. 2001, 2016 4-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

A smart way to modernize

• MODERN-I-ZATION Blog Entries
ƒ http://iprodeveloper.com/blog/iaccess-unleashed
ƒ http://iprodeveloper.com/blog/access-client-solutions-deployment-options
ƒ http://iprodeveloper.com/blog/move-your-data-access-client-solutions
ƒ http://iprodeveloper.com/blog/access-client-solutions-migration-made-easy
ƒ http://iprodeveloper.com/blog/how-do-you-actually-get-access-client-solutions

• IBM i Technical Library

ƒ http://www.ibm.com/developerworks/ibmi/library/i-access_client_solutions/

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-20. A smart way to modernize

The URLs to access these publications are:

• http://iprodeveloper.com/blog/iaccess-unleashed
• http://iprodeveloper.com/blog/access-client-solutions-deployment-options
• http://iprodeveloper.com/blog/move-your-data-access-client-solutions
• http://iprodeveloper.com/blog/access-client-solutions-migration-made-easy
• http://iprodeveloper.com/blog/how-do-you-actually-get-access-client-solutions
• http://www.ibm.com/developerworks/ibmi/library/i-access_client_solutions/

© Copyright IBM Corp. 2001, 2016 4-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Review questions
1. True or False: IBM Navigator for i can display the system
history log.

2. True or False: IBM Navigator for i launches in a web

browser.

3. True or False: Application Administration is used to control

access to functions or applications.

4. True or False: IBM i Access Client Solutions replaced IBM i

Navigator

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-21. Review questions

© Copyright IBM Corp. 2001, 2016 4-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Review answers
1. True or False: IBM Navigator for i can display the system
history log.
The answer is true.

2. True or False: IBM Navigator for i launches in a web

browser.
The answer is true.

3. True or False: Application Administration is used to control

access to functions or applications.
The answer is true.

4. True or False: IBM i Access Client Solutions replaced IBM i

Navigator.
The answer is true.

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-22. Review answers

© Copyright IBM Corp. 2001, 2016 4-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 4. IBM i Access Family overview

Uempty

Unit summary
• Describe the features and capabilities of the IBM i Access Family of
products
• Describe the installation and use of IBM i Access Client Solutions
• List reference documentation

IBM i Access Family overview © Copyright IBM Corporation 2001, 2016

Figure 4-23. Unit summary

© Copyright IBM Corp. 2001, 2016 4-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Unit 5. IBM i Access Client Solutions

Estimated time
00:45

Overview
This unit describes the new functionality available in IBM i Access Client Solutions.

How you will check your progress

• Review questions
• Machine exercises

© Copyright IBM Corp. 2001, 2016 5-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Unit objectives
• Describe purpose IBM i Access Client Solutions
• Describe available tasks IBM i Access Client Solutions

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 5-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

IBM i Access Client Solutions deployment (1 of 2)

• IBM i Access Client Solutions is not installed to the client operating
system, on which it is deployed.
ƒ There is no installation program for the core of the product.

• Access Client Solutions Deployment

ƒ The deployment involves the client bundle being placed wherever it is to be
executed from, and determining where the product settings are going to be
stored.

• Client bundle
ƒ Contains the Java executable .jar properties file, platform-specific start
executables and JavaScript start samples, product documentation, and
licensing notices.
ƒ All that is required to be deployed is the Java executable .jar.
ƒ The rest is optional.

• No JRE distributed
ƒ IBM i Access Client Solutions does not deploy a specific JRE.
ƒ Relies on a Java 1.6 or higher JRE to be accessible on the client OS.
IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-2. IBM i Access Client Solutions deployment (1 of 2)

© Copyright IBM Corp. 2001, 2016 5-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

IBM i Access Client Solutions deployment (2 of 2)

• There are two main things that can be controlled with the IBM i Access
Client Solutions deployment
ƒ Where the product is launched from
ƒ Where the user’s configuration is stored

• Both of these locations can basically be anywhere

ƒ Local PC Operating System
ƒ Network Share File System
ƒ Portable media or USB flash drive

• They can be located in different places

ƒ Product can be launched from local PC OS, while configuration is stored on
a Network file system

• Or in the same location

ƒ Product can be launched with configuration files that are all stored on a USB
flash drive

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-3. IBM i Access Client Solutions deployment (2 of 2)

© Copyright IBM Corp. 2001, 2016 5-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Main user interface

• Provide an easy to use launchpoint for features
• Build an infrastructure that is extensible for the future

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-4. Main user interface

On the visual you can see IBM i Access Client Solutions (ACS) main screen. ACS offers many
features previously in IBM Client Access.
Features include:
• 5250 display and printer emulation based on IBM's Host-on-Demand
• 5250 Session Manager support modeled after IBM Personal Communications Session
Manager
• Multiple language support for concurrent 5250 emulation sessions on the same client
• Data Transfer similar to IBM i Access for Windows Data Transfer plus support for
OpenDocument spreadsheet (*.ods), Excel Workbook (*.xlsx), and other file formats
• Data Transfer integration with Excel and OpenOffice
• Simplified SSL Configuration
• Download and viewing of spool files
• IBM i Virtual Control Panel for LAN and HMC consoles
• 5250 emulation for LAN and HMC consoles

© Copyright IBM Corp. 2001, 2016 5-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty
• Consolidation of hardware management interface configurations, including ASMI, IVM, and
HMC
IBM i Access Client Solutions - Windows Application Package for Windows operating systems.
Features include:
• Connectivity to DB2 for i using ODBC, .Net, and OLE DB
• Programming Toolkit for accessing IBM i system objects
• Support for TLS/SSL connections
• AFP printer driver

© Copyright IBM Corp. 2001, 2016 5-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

System Configurations (1 of 2)
• Use the System Configurations panel to store connection information on
the IBM i Systems that are used.

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-5. System Configurations (1 of 2)

© Copyright IBM Corp. 2001, 2016 5-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

System Configurations (2 of 2)
Create, edit, or delete connection
information for IBM i Systems that are
used.

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-6. System Configurations (2 of 2)

To add a new system click the New button. If you want to modify a system click the Edit button.
If you want to use LAN Console use Locate Console button.
In the General and Connection tabs enter:
• System name or IP Address
• User name to connect

© Copyright IBM Corp. 2001, 2016 5-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Console configuration
• Console information is configured in the System Configuration panel
ƒ LAN Console/Virtual Control Panel
í Service host name

ƒ HMC 5250 Console

í Host name or IP address to the HMC
5250 Proxy interface
í Supports SSL
í Virtual Control Panel

ƒ Hardware Management Interfaces

í Host name or IP address
Can append a port to the name or address
x.x.x.x:port
í Description
í Examples of management interfaces
Advanced System Management
Interface (ASMI)
Integrated Virtualization Manager (IVM)
Hardware Management Console (HMC)

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-7. Console configuration

On the Console configuration tab you can also configure Virtual Control Panel by pressing
Advanced button.

© Copyright IBM Corp. 2001, 2016 5-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Console
• 5250 Console: Opens an interactive console to the current system
• Virtual Control Panel: Opens a Virtual Control Panel if LAN Console is
used for the current system
• Hardware Management Interface 1: Opens a web browser to the
management console specified for the current system

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-8. Console

© Copyright IBM Corp. 2001, 2016 5-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

5250 Console
• 5250 HMC Console

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-9. 5250 Console

Note on the 5250 Console screen you see the ‘HMC 5250 Console’ watermark.

© Copyright IBM Corp. 2001, 2016 5-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Virtual Control Panel

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-10. Virtual Control Panel

The Virtual Control Panel allows you manage control panel functionality.

© Copyright IBM Corp. 2001, 2016 5-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Database Run SQL Script

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-11. Database Run SQL Script

Run SQL Scripts is a useful tool for running SQL statements and CL commands.

© Copyright IBM Corp. 2001, 2016 5-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Database SQL Performance Center

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-12. Database SQL Performance Center

SQL Performance Center provides a set of tools to help you optimize the SQL in your database
applications.
• Analyze - Provides a summarized view of collected performance data that serves as a launch
point into deeper analysis using drill-down navigation.
• Show Statements - Links to IBM Navigator for i.
• Compare - Links to IBM Navigator for i.
• SQL Plan Cache - Links to IBM Navigator for i.

© Copyright IBM Corp. 2001, 2016 5-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

5250 Emulation (1 of 3)
• Opens an IBM 5250 Telnet session to the current system

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-13. 5250 Emulation (1 of 3)

© Copyright IBM Corp. 2001, 2016 5-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

5250 Emulation (2 of 3)
• Provides nearly identical interaction, look, and feel to the Access for
Windows PC5250 emulator

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-14. 5250 Emulation (2 of 3)

5250 Emulator starts a 5250 display session for the selected system. If a 5250 display session
profile exists for the selected system, the profile is used when starting the display session;
otherwise, a default display session profile is used.
When the 5250 display session is ended, if a profile does not exist for the system, you are
prompted to save the current settings of the display session to a 5250 display session profile. The
saved display session profile will be used the next time a 5250 display session is started for the
system. The saved 5250 display session profile can be managed using 5250 Session Manager
from the Management tasks.

© Copyright IBM Corp. 2001, 2016 5-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

5250 Emulation (3 of 3)
• IBM i Access Client Solutions 5250 Emulation sessions are saved as
.hod files.
ƒ Access for Windows PC5250 .ws files can be imported into .hod files.
ƒ .hod files can also be saved outside of the Session Manager.
í Need to set up a file association in the PC operating system to run the file and have
it open the emulator.

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-15. 5250 Emulation (3 of 3)

© Copyright IBM Corp. 2001, 2016 5-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

5250 Session Manager (1 of 2)

• 5250 Session Manager

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-16. 5250 Session Manager (1 of 2)

5250 Session Manager provides an interface to create and manage IBM i display and printer
emulator sessions. 5250 Session Manager supports:
• Creating new 5250 display session profiles
• Creating new 5250 printer session profiles
• Creating or editing multiple session batch files
• Starting a display or printer emulation session using existing session profiles
• Viewing all active 5250 display and printer emulator sessions
• Importing session profiles from IBM Personal Communications (*.ws)

© Copyright IBM Corp. 2001, 2016 5-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

5250 Session Manager (2 of 2)

• Similar to Access for Windows PC5250 Session Manager
ƒ Start a saved session
ƒ Create new display or printer session
ƒ Create a multiple session start batch file from existing saved sessions

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-17. 5250 Session Manager (2 of 2)

© Copyright IBM Corp. 2001, 2016 5-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Printer Output

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-18. Printer Output

On the left pane IBM i Access Client Solutions click Printer Output.
Printer Output - provides an interface that allows you to view files in the IBM i output queues and
also provides the capability to download these files to your client system. By default, the current
user's output files are displayed for all output queues.

© Copyright IBM Corp. 2001, 2016 5-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Actions

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-19. Actions

You can select file or files by clicking it and then right-clicking to see possible operations or use
Actions menu:
• Download Only: Download the selected files.
• Download and View: Download the selected files and then open them. The program used to
open the files is platform-dependent based on the file extension.
• View Only: Download the selected files to a temporary location and then open them. The
program used to open the files is platform-dependent based on the file extension.

© Copyright IBM Corp. 2001, 2016 5-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Actions: Download, View

View

Download

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-20. Actions: Download, View

Depending on the chosen action you can see your spool file in .pdf format or download it. You can
choose both download and open i one operation. If you have a PDF reader installed on your
workstation you can see in .pdf format if not you will see a .TXT format.

© Copyright IBM Corp. 2001, 2016 5-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Preferences

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-21. Preferences

On the Printer Output window click the Edit menu and then Preferences.
Use the Download Location option to set the location where the printer output files are downloaded.
Download to desktop: Printer output will be downloaded to the user's desktop and placed in a
folder named after the target system.
Download to a temporary location: Printer output will be downloaded into a temporary
subdirectory for the user.
Download to the product's configuration root: A subdirectory named Splf will be created below
the product's configuration root, and printer output will be downloaded there. The text area displays
the path name of this directory.
Specify a location: Printer output will be downloaded to the specified location.
Regardless of the Download Location setting, printer output is stored in a subdirectory unique to the
target system.

© Copyright IBM Corp. 2001, 2016 5-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty
The “Use PDF format if available” option is used to determine whether printer output with a *SCS or
*AFPDS device type should be converted to PDF format. If this option is enabled and the host
supports PDF transformations, then the client file is stored in PDF format with the .pdf file
extension. Otherwise, it is stored in plain text and stored with a .txt file extension. The host
supports PDF transformations if the Transform Services product (option 1) is installed and
functional.

© Copyright IBM Corp. 2001, 2016 5-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Printer Output View menu

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-22. Printer Output View menu

On the Printer Output click the View menu you can see following items:
Active Tasks Pane
From the View menu, you can enable or disable the Active Tasks Pane. This pane will display the
progress for printer output that is currently being downloaded. When the task is complete, the task
is removed from this pane.
Download Pane: From the View menu, you can enable or disable “Download Pane”. This will
display an area labeled “Downloaded Files” that shows downloaded printer output. From this pane,
you can drag and drop files to your local file system.
On the download pane you can select downloaded files and use the Open or Delete button to
manage files.
Download Directory: From the View menu, choose Download Directory. This will launch your
platform's file browser to the location of the downloaded files. For instance, on Windows operating
systems, Windows Explorer will be launched.
Set Filter
You can customize the printer output based on user and output queue.

© Copyright IBM Corp. 2001, 2016 5-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty
Options for filtering by User are:
• Current user (*CURRENT): Printer output is displayed for the current user.
• All users (*ALL): Printer output is displayed for all users.
• Select user: Printer output is displayed for the selected user.
Options for filtering by output queue are:
• All output queues (*ALL): Printer output from all output queues are shown.
• Select a specific output queue: Printer output is displayed for a specific output queue. The
output queue must be specified in “LIBRARY/FILE” format.

© Copyright IBM Corp. 2001, 2016 5-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Data Transfer

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-23. Data Transfer

Data Transfer provides an interface to help you transfer data between your client system and your
IBM i.
Data Transfer supports many common file formats, such as:
• OpenDocument Spreadsheet (*.ods)
• Excel Workbook (*.xlsx)
• Excel 97-2003 Workbook (*.xls)
• CSV (Comma delimited) (*.csv)
Data Transfer from IBM i allows you to transfer data from a file on your IBM i to a file or active
spreadsheet on your client workstation. To create a transfer request from the system, you must
specify the following options:
• System: The name of the IBM i from which you want to transfer your data. You can either select
a configured system or type the name of the system in the text box.
• File name (IBM i): Provides a space for you to enter the library, file, and optional member name
of the file from which you are transferring your data. You can either browse to find the file on
your IBM i, or type the name of the file. An example of a file name is
mylib/myfile(mymember). To browse the contents of a library, either leave the File name
field blank, or specify a library name followed by a slash character, for example: QIWS/.

© Copyright IBM Corp. 2001, 2016 5-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty
• Data Options: Clicking the Data Options button allows you to specify ways to select, group,
and order the data you transfer from the IBM i.
• Output Device: Allows you to specify what type of device your data is transferred to. You can
select to transfer data to a file or directly to a window on your display. You can also transfer data
to an active spreadsheet. When transferring data to a file or active spreadsheet, you can click
the Details button to select more options for transferring the data.
• Name: The name of the file on your workstation that will contain the data you want to retrieve
from your IBM i. You can either browse to find the file on your workstation, or type the path and
name of the file in the text box. This option is not available when using an active spreadsheet.
• Format Options: Clicking the Format Options button allows you to specify how you want your
data formatted.
• Details: Clicking the Details button allows you to specify more detailed information about the
transfer request.
• Properties: Clicking the Properties button allows you to specify more information about how
you want your data transferred. It includes options for conversions, connection information, and
how to display IBM i object names. It also allows you to set the Library List to enable browsing
for files in a set of libraries.
When you are ready to transfer your data, click the Start Transfer button.

© Copyright IBM Corp. 2001, 2016 5-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Preferences: General

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-24. Preferences: General

Use the Locale field to select the locale you want to use. The choices include all locales supported
by the installed Java virtual machine (JVM). The language will be determined by the locale value. If
the language is not available for that locale, English will be used. Locales that have an asterisk (that
is, *) after them will use English as the language.
Use the Logging level to control the types of events that are logged. Logging is used to store
information about the state of your IBM i Access Client Solutions application. This logging
information can be used by IBM Service to aid in problem determination. Log files are stored on
your system in a location, which is shown in the Local Settings tab. When more detailed logging is
enabled, more space is used in your file system. Therefore, detailed logging should only be used
when directed by IBM Service.
The logging levels are:
FINEST Detailed tracing messages and the FINE level
FINE Basic tracing messages and the CONFIG level
CONFIG Messages about configuration and the INFO level
INFO Informational messages and the WARNING level
WARNING Warning messages and the SEVERE level
SEVERE Serious failures
OFF Nothing will be logged

© Copyright IBM Corp. 2001, 2016 5-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty
The License refresh interval field allows you to specify the number of minutes to hold an IBM i
Access Family license after the license is no longer being used. Data Transfer and 5250 Emulator
require this license. The license is available when the IBM i Access Family Licensed Product
(57xx-XW1) is installed and configured on the IBM i. Obtaining a license requires logon credentials.
Increasing the license refresh interval might decrease how often you are prompted for logon
credentials, but will hold the license for a longer period of time.
When using System Configurations to configure a new system, the Use SSL for connection option
will be enabled by default when the Default communication to SSL box is checked. The Default
communication to SSL box also determines whether or not to use SSL when connecting to a
system that is not currently configured. Checking Default communication to SSl has no effect on
System Configurations which already exist.
Tool tip messages are available for some fields and are displayed when the cursor is over the field.
You can disable this function by unchecking the Enable tool tip messages box.
Information about each task on the main panel is available by either moving the cursor over the task
or by using the tab and arrow keys to navigate between groups and tasks. You can disable this
function by unchecking the Enable description panel box.
Additional tab locations and other accessibility features are enabled when the Enable accessibility
mode box is checked.

M Mac OS

To enable accessibility features like screen readers, it is necessary to download and install the Java
Access Bridge package from Oracle.

By default, the product does not attempt to force or verify that secure connections are established
in a FIPS-compliant manner. If the Client SSL must be FIPS-compliant box is checked, however,
the product will attempt to verify that the current Java Runtime Environment (JRE) is configured to
be FIPS-compliant for secure connections. FIPS compliance must be supported in the
currently-running JRE in order for the application to run in a FIPS-compliant mode.
When the Read netrc file for login information box is checked, the product will use the current
user's netrc file for determining login information. This file is located in the user's home directory,
and is named _netrc on Windows or .netrc on non-Windows operating systems. Reading of
encrypted passwords from this file is not supported. The file format is assumed to follow the
standard .netrc file format widely utilized by Linux users. Note that the use of a netrc file has
potential security implications, and it is the responsibility of the user to ensure that the file's
permissions do not allow other users to access the file.

© Copyright IBM Corp. 2001, 2016 5-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Preferences: Local Settings

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-25. Preferences: Local Settings

The settings on this tab show the location where the configuration and service log information is
kept. The Open button allows you to display the contents of that location. The Clear button will
remove the files at that location.
The Configuration Root is the root location of the configuration. There are several sub-directories
below this directory where the configuration is stored.
The Logs Directory is relative to the Configuration Root and is the location where the logs are
stored when you enable logging.
The Dumps Directory is relative to the Configuration Root and is the location where the service
logs are stored when you use Tools > Generate Service Logs from the main menu.
The Service Directory is relative to the Configuration Root and is the location where service
information is stored when you use Tools > Package Service Logs from the main menu.
The location of the Configuration Root defaults to a platform-specific path.
To change the Configuration Root location, set the com.ibm.iaccess.AcsBaseDirectory property in
the AcsConfig.properties file and restart IBM i Access Client Solutions.

© Copyright IBM Corp. 2001, 2016 5-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty
If the path to the Configuration Root does not exist, IBM i Access Client Solutions will fail to start. If
the configuration directories below the Configuration Root do not exist, they will automatically be
created.

© Copyright IBM Corp. 2001, 2016 5-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Preferences: Passwords

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-26. Preferences: Passwords

Change IBM i passwords provides an interface for changing your password on one or more IBM i
systems. In order to change the password on multiple systems at once, the current system
password must be the same. To change your password, select the system (or systems) and click
the Change Password button. You will be prompted for the old (current) password and the new
password, followed by information on whether or not the password change attempt was successful
for each system.

© Copyright IBM Corp. 2001, 2016 5-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Preferences: Printer Output

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-27. Preferences: Printer Output

Use the Download Location option to set the location where the printer output files are downloaded.
• Download to desktop: Printer output will be downloaded to the user's desktop and placed in a
folder named after the target system.
• Download to a temporary location: Printer output will be downloaded into a temporary
subdirectory for the user.
• Download to the product's configuration root: A subdirectory named Splf will be created
below the product's configuration root, and printer output will be downloaded there. The text
area displays the path name of this directory.
• Specify a location: Printer output will be downloaded to the specified location.
Regardless of the Download Location setting, printer output is stored in a subdirectory unique to the
target system.
The “Use PDF format if available” option is used to determine whether printer output with a *SCS or
*AFPDS device type should be converted to PDF format. If this option is enabled and the host
supports PDF transformations, then the client file is stored in PDF format with the .pdf file
extension. Otherwise, it is stored in plain text and stored with a .txt file extension. The host
supports PDF transformations if the Transform Services product (option 1) is installed and
functional.

© Copyright IBM Corp. 2001, 2016 5-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

HMC Probe Utility

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-28. HMC Probe Utility

The HMC Probe Utility allows you retrieve information about systems and partitions managed by
the HMC console.

© Copyright IBM Corp. 2001, 2016 5-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Exercise: Print output using IBM i Access Client

Solutions

• At the end of the exercise, you should be able to:

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-29. Exercise: Print output using IBM i Access Client Solutions

© Copyright IBM Corp. 2001, 2016 5-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Review questions
1. True or False: IBM i Access Client Solutions provides an
option that allows you to see the output that is generated by
another user.

2. Under which of the following is the Printer Output branch

found?
a. General
b. Database
c. Users and Groups
d. Management

3. Which of the following actions can be performed for a spoolfile

from the printer output?
a. Download
b. View
c. Download and View
d. All above

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-30. Review questions

© Copyright IBM Corp. 2001, 2016 5-37

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Review answers
1. True or False: IBM i Access Client Solutions provides an option
that allows you to see the output that is generated by another user.
The answer is true.

2. Under which of the following is the Printer Output branch found?

a. General
b. Database
c. Users and Groups
d. Management
The answer is General.

3. Which of the following actions can be performed for a spoolfile

from the printer output?
a. Download
b. View
c. Download and View
d. All above
The answer is All above.

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-31. Review answers

© Copyright IBM Corp. 2001, 2016 5-38

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 5. IBM i Access Client Solutions

Uempty

Unit summary
• Describe purpose IBM i Access Client Solutions
• Describe available tasks IBM i Access Client Solutions

IBM i Access Client Solutions © Copyright IBM Corporation 2001, 2016

Figure 5-32. Unit summary

© Copyright IBM Corp. 2001, 2016 5-39

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Unit 6. Security concepts and overview

Estimated time
00:10

Overview
Security on the IBM i platform is flexible enough to meet the requirements of a wide range of users
and situations. You need to understand the features and options available to have a better
understanding of what has been set up by your system administrator on your system.
In this unit, we will cover the tools at your disposal to secure your system, control what users are
allowed to do, and secure who can access the data and limit what they can do to that data. This unit
will discuss the concepts, while the following units will cover the specific details.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 6-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Unit objectives
• List and discuss the objectives of system security
• Describe what physical security entails
• Discuss what keylock security means
• List and describe the capabilities of the system tools available to secure
your system

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 6-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

The objectives of system security

• Confidentiality:
ƒ Protecting against disclosing information to unauthorized people
ƒ Restricting access to confidential information
ƒ Protecting against curious system users and outsiders

• Integrity:
ƒ Protecting against unauthorized changes to data
ƒ Restricting manipulation of data to authorized programs
ƒ Providing assurance that data is trustworthy

• Availability:
ƒ Preventing accidental changes or destruction of data
ƒ Protecting against attempts by outsiders to abuse or destroy system
resources

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-2. The objectives of system security

System security is often associated with external threats, such as hackers or business rivals.
However, protection against system accidents by authorized system users is often the greatest
benefit of a well-designed security system. In a system without good security features, pressing the
wrong key might result in deleting important information. System security can prevent this type of
accident.
The best security system functions cannot produce good results without good planning. Security
that is set up in small pieces, without planning, can be confusing. It is difficult to maintain and to
audit. Planning does not imply designing the security for every file, program, and device in
advance. It does imply establishing an overall approach to security on the system and
communicating that approach to application designers, programmers, and system users.

© Copyright IBM Corp. 2001, 2016 6-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Physical security
Computer System
Room

Ke ep
Ou t

Display
Stations
Backup Tapes

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-3. Physical security

Physical security includes protecting the system unit, system devices, and backup media from
accidental or deliberate damage. Most measures you take to ensure the physical security of your
system are external to the system.
All new Power Systems models do not have keylock however you can order keylock rack tower to
prevent server access.
In all current available Power System, you can use keylock position using Virtual Control Panel,
Key position for server/partition on the HMC session, or physical on the Power System Control
Panel to setup work running mode (Normal/Manual). You cannot secure server or partition changed
key position.

© Copyright IBM Corp. 2001, 2016 6-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Monitoring physical security

• If the computer is behind a door locked that uses an entry code, ensure
that the code is changed regularly.
• Restrict physical access to save and restore devices, such as tape units
and optical units.
• Ensure backup media is protected from damage and theft.
• Restrict access to publicly located workstations and the console.
• Restrict remote access to the 5250 console or HMC/IVM/ASMI.

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-4. Monitoring physical security

© Copyright IBM Corp. 2001, 2016 6-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

System tools used to secure your system

• Security level
• System values
• User profiles
• Groups profiles
• Object (Resource) security
• Authorization lists
• Adopted authority

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-5. System tools used to secure your system

Security level
There are five levels of security that can be set with the QSECURITY system value.
System values
Allow you to define system wide security settings and allow you to provide customization for many
characteristics of your System i.
Signing
Signing your software object is particularly important if the object has been transmitted across the
Internet or stored on media which you feel might have been modified. The digital signature can be
used to detect if the object has been altered.
Digital signatures, and their use for verification of software integrity, can be managed according to
your security policies using the Verify Object Restore (QVFYOBJRST) system value, the Check
Object Integrity (CHKOBJITG) command, and the Digital Certificate Manager tool. Additionally, you
can choose to sign your own programs (all licensed programs shipped with the system are signed).

© Copyright IBM Corp. 2001, 2016 6-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty
Single sign-on enablement
Single sign-on is an authentication process in which a user can access more than one system by
entering a single user ID and password. To enable a single sign-on environment, IBM® provides
two technologies that work together to enable users to sign in with their workstation user name and
password and be authenticated to System i platforms in the network. Network Authentication
Service (NAS) and Enterprise Identity Mapping (EIM) are the two technologies that an administrator
must configure to enable a single sign-on environment. To authenticate users to the network the
Kerberos protocol is used. A secure, centralized system, called a key distribution center,
authenticates principals (Kerberos users) to the network.
User profiles
The user profile is powerful and flexible tool used to control what the user can do and customize the
way the system appears to that user.
Groups profiles
A group profile is a special type of user profile. Rather than giving authority to each user
individually, you can use a group profile to define authority for a group of users.
Resource security
The ability to access an object is called authority. Resource security on the IBM i operating system
enables you to control object authorities by defining who can use which objects and how those
objects can be used.
You can specify detailed authorities, such as adding records or changing records. Or you can use
the system-defined subsets of authorities: *ALL, *CHANGE, *USE, and *EXCLUDE.
Files, programs, and libraries are the most common objects requiring security protection, but you
can specify authority for any object on the system.
Security audit journal
You can use security audit journals to audit the effectiveness of security on your system. The IBM i
operating system provides the ability to log selected security-related events in a security audit
journal. Several system values, user profile values, and object values control which events are
logged.

© Copyright IBM Corp. 2001, 2016 6-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Security is always active

Signon:
Mary

Menu Authority

Payroll
Authority
menu

PAYEDIT
Authority
program

Operational
Payroll Read
data
Execute

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-6. Security is always active

On the System i security has been architected from the ground up. Security is always available and
active. Based on what level of security you choose to configure and implement will determine how
secure your system will be.

© Copyright IBM Corp. 2001, 2016 6-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Review questions (1 of 2)
1. True or False: The objectives of security are confidentiality,
integrity, and availability.

2. Physical security includes which of the following?

a. Controlling access to the CPU
b. Securing the tapes used for backup
c. Securing the printers connected to your system
d. All of the above

3. Which of the following is not one of the modes you can

select for your system?
a. Manual
b. Normal
c. Automatic
d. Secure
e. Lockdown

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-7. Review questions (1 of 2)

© Copyright IBM Corp. 2001, 2016 6-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Review answers (1 of 2)
1. True or False: The objectives of security are confidentiality,
integrity, and availability.
The answer is true.

2. Physical security includes which of the following?

a. Controlling access to the CPU
b. Securing the tapes used for backup
c. Securing the printers connected to your system
d. All of the above
The answer is all of the above.

3. Which of the following is not one of the modes you can

select for your system?
a. Manual
b. Normal
c. Automatic
d. Secure
e. Lockdown
The answers are manual and normal.
Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-8. Review answers (1 of 2)

© Copyright IBM Corp. 2001, 2016 6-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Review questions (1 of 2)
4. True or False: It is not possible to disable the power button
on your system.

5. True or False: Security is always active on the System i.

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-9. Review questions (1 of 2)

© Copyright IBM Corp. 2001, 2016 6-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Review answers (1 of 2)
4. True or False: It is not possible to disable the Power button
on your system.
The answer is true.

5. True or False: Security is always active on the System i.

The answer is true.

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-10. Review answers (1 of 2)

© Copyright IBM Corp. 2001, 2016 6-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 6. Security concepts and overview

Uempty

Unit summary
• List and discuss the objectives of system security
• Describe what physical security entails
• Discuss what keylock security means
• List and describe the capabilities of the system tools available to secure
your system

Security concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 6-11. Unit summary

© Copyright IBM Corp. 2001, 2016 6-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Unit 7. System values

Estimated time
00:20

Overview
There are three components used to implement security on this system. The operating system
continually checks system values, user profiles, and an object's resource security as it receives
requests from users to determine whether that user will be allowed to access the object in question.
In this unit, we will discuss system values and how you use these to customize many
characteristics of your system. Security is an integral part of the operating system. It is not an
add-on or extra purchase feature of an application.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 7-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Unit objectives
• List and explain the levels of security available
• Describe the capability in service tools to lock out users from changing
system values
• Define the different categories of system values available
• Explain how to use security policies to set system values
• List the commands used to set system values when using a 5250
emulation session
• List the steps used in System i Navigator to manipulate system values

System values © Copyright IBM Corporation 2001, 2016

Figure 7-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 7-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Security components

People Objects
(Users) (Resources)
User Individual
Profiles Objects
Job Library/Directory
Descriptions
Authorization
Group Profiles
Lists

System Values

System values © Copyright IBM Corporation 2001, 2016

Figure 7-2. Security components

There are three components used to implement security on this system. The operating system
continually checks system values, user profiles, and objects as it receives requests from users to
determine whether that user will be allowed to access the object in question.
In this unit, we will discuss System values and how you use these to customize many
characteristics of your system.
Security is an integral part of the operating system. It is not an add-on or extra purchase feature of
an application.

© Copyright IBM Corp. 2001, 2016 7-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Topic 1: Security level system

value

System values © Copyright IBM Corporation 2001, 2016

Figure 7-3. Topic 1: Security level system value

© Copyright IBM Corp. 2001, 2016 7-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

QSECURITY system value: Security level

Level 50 Enhanced integrity

Level 40 System integrity

Level 30 Resource
Level 20 Password

Recommended value = Level 40

System values © Copyright IBM Corporation 2001, 2016

Figure 7-4. QSECURITY system value: Security level

You can choose how much security you want the system to enforce by setting the security level
(QSECURITY) system value. If you want to change the security level, use the Work with System
Values (WRKSYSVAL) command.

© Copyright IBM Corp. 2001, 2016 7-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Security level 40

Level 50 Enhanced Integrity

Level 40 System Integrity

Level 30 Resource

Level 20 Password

• Prevents use of unsupported interfaces

• Prevents use of restricted instructions
• Controls use of job descriptions on SBMJOB
• Prevents signon without a user ID and password
• Enhanced hardware storage protection
• Default for QSECURITY system value
System values © Copyright IBM Corporation 2001, 2016

Figure 7-5. Security level 40

Level 40 is referred to as system integrity security. At this level, the system itself is protected
against users. User-written programs cannot directly access the internal control blocks through
pointer manipulation.
Select System Security Level by using IBM Navigator for i panels.
• Accessing objects through unsupported interfaces. Example: Calling the command processing
program for the SIGNOFF command
• Accessing internal system structures with C/400, Pascal or Assembler
• Controls use of job descriptions on SBMJOB
• Does not allow *SBSD to allow sign on without entering User and Password
• Enables enhanced hardware storage protection, defining system information on disk as
read/write, read only, or no access
Level 20-30: Usually action allowed but logged to QAUDJRN journal.
Level 40-50: Usually action fails, and is logged to QAUDJRN journal.

© Copyright IBM Corp. 2001, 2016 7-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

The comparison of the functions supported by the different

levels of security

System values © Copyright IBM Corporation 2001, 2016

Figure 7-6. The comparison of the functions supported by the different levels of security

On the visual you can compare functions supported depending on chose security level.

© Copyright IBM Corp. 2001, 2016 7-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Locking system values using service tools

• Steps to lock/unlock using STRSST:
1. Sign on to an emulation session.
2. Enter the STRSST command.
3. Type your service tools user ID and password.
4. Select option 7 = Work with system security.
5. Select option 1 to lock or option 2 to unlock.

• Steps to lock/unlock using DST:

1. IPL system in attended mode.
2. Select option 3 = Use Dedicated Service Tools from the IPL or Install
system display.
3. Sign on to DST with your service tools user ID and password.
4. Select option 13 = Work with system security.
5. Select option 2 to lock or option 1 to unlock.

System values © Copyright IBM Corporation 2001, 2016

Figure 7-7. Locking system values using service tools

You can use system service tools (SST) or dedicated service tools (DST) to lock and unlock the
security-related system values. However, you must use DST if you are in recovery mode because
SST is not available during this mode. Otherwise, use SST to lock or unlock the security-related
system values.
You can restrict the following system values by using the lock option:
QALWJOBITP QAUTORMT QLMTDEVSSN QPWDLMTREP
QRETSVRSEC QALWOBJRST QAUTOVRT QLMTSECOFR
QPWDLVL QRMTSIGN QALWUSRDMN QCRTAUT
QMAXSGNACN QPWDMAXLEN QRMTSRVATR QAUDCTL
QCRTOBJAUD QMAXSIGN QPWDMINLEN QSCANFS
QAUDENACN QDEVRCYACN QPWDCHGBLK QPWDPOSDIF
QSCANFSCTL QAUDFRCLVL QDSPSGNINF QPWDEXPITV
QPWDRQDDGT QSECURITY QAUDLVL QDSCJOBITV
QPWDEXPWRN QPWDRQDDIF QSHRMEMCTL QAUDLVL2
QFRCCVNRST QPWDLMTAJC QPWDRULES QUSEADPAUT
QAUTOCFG QINACTMSGQ QPWDLMTCHR QPWDVLDPGM
QVFYOBJRST

© Copyright IBM Corp. 2001, 2016 7-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Topic 2: Configure security

using 5250 emulation

System values © Copyright IBM Corporation 2001, 2016

Figure 7-8. Topic 2: Configure security using 5250 emulation

© Copyright IBM Corp. 2001, 2016 7-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Individual system values

System values © Copyright IBM Corporation 2001, 2016

Figure 7-9. Individual system values

You can change system values working with individual system value name.

© Copyright IBM Corp. 2001, 2016 7-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

System value categories

System values © Copyright IBM Corporation 2001, 2016

Figure 7-10. System value categories

To work with system value you can also use the system value category like *SEC for security
system value.

© Copyright IBM Corp. 2001, 2016 7-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Allocation category

System values © Copyright IBM Corporation 2001, 2016

Figure 7-11. Allocation category

On this visual is example to work with allocation category system value. Note you can also type
name of the system value in the Position to field to allocate specified value.

© Copyright IBM Corp. 2001, 2016 7-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Topic 3: Configure security

using IBM Navigator for i

© Copyright IBM Corporation 2001, 2016

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Figure 7-12. Topic 3: Configure security using IBM Navigator for i

© Copyright IBM Corp. 2001, 2016 7-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Configuration and Service: System Values

System values © Copyright IBM Corporation 2001, 2016

Figure 7-13. Configuration and Service: System Values

Changes to the majority of the system values will take effect immediately. An IPL is required only
when changing the security level (QSECURITY) system value or the password level (QPWDLVL)
system value.
To work with system value using IBM Navigator for i you have to:
1. Log on to the system using http://<<system_name or IP address>>:2001.
2. On the left pane, expand IBM i Management (default is expanded).
3. Expand Configuration and Service.
4. Click System Value.

© Copyright IBM Corp. 2001, 2016 7-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Security category

System values © Copyright IBM Corporation 2001, 2016

Figure 7-14. Security category

The steps to follow when using IBM Navigator for i are:

1. Expand the Configuration and Service branch on the function tree.
2. Click the System Values sub branch to see the categories displayed on the right pane.
3. Right-click Security category in the right pane and chose Properties to see the panel
displayed in the lower right corner on the visual.
4. Select the level of security that is to be implemented then click OK.
5. IPL the system for this change to take effect.

© Copyright IBM Corp. 2001, 2016 7-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Date and Time category

System values © Copyright IBM Corporation 2001, 2016

Figure 7-15. Date and Time category

1. Expand the Configuration and Service branch on the function tree.

2. Click the System Values sub branch to see the categories displayed on the right pane.
3. Right-click Date and Time category in the right pane and chose Properties.
Use the Date tab to specify the current date for your system. The Date tab also specifies a leap
year adjustment that ensures that the system date is correct when a leap year occurs.
System date - The system supports dates that range from August 24, 1928 to July 6, 2053. To
change only the year, highlight the year and click the up or down arrow. To change only the month,
highlight the month and click the up or down arrow.
System value - QDAYOFWEEK, QDATE, QDAY, QMONTH, and QYEAR.
Special considerations: The system date is automatically updated when the time reaches midnight,
12:00:00 AM.

© Copyright IBM Corp. 2001, 2016 7-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty
Leap year adjustment - Adjusts the system calendar for the leap year in different calendar
systems. If your calendar year agrees with the Gregorian calendar system, select Use Gregorian
leap year adjustment. If your calendar year differs from the Gregorian, adjust the system calendar
to account for the leap year of the calendar year you are using. To make the adjustment, divide the
leap year in your calendar system by 4; then set Leap year adjustment to the value of the
remainder. For example, the Gregorian calendar year of 1984 was the year 73 in the Republic of
China. Because 73 was a leap year, you divide 73 by 4; this leaves a remainder of 1. Therefore, to
adjust the system calendar for the Republic of China, specify 1 for Leap year adjustment.
System value: QLEAPADJ.
Special considerations: Changing the leap year system value does not change the system clock
and job dates of active jobs, but it might change the date system value.
The QTIMADJ system value identifies the software used to adjust the system clock in order to keep
it synchronized with an external time source. This value should be maintained by the time
adjustment software and is intended as an aid to prevent multiple time adjustment applications from
conflicting with one another.
Time adjustment specifies whether a time maintenance application is specified to maintain the
system time and whether or not there is a time adjustment in progress. The time adjustment might
initiate from the time maintenance application or you can manually start a time adjustment.
Adjusting does not cause large jumps in time that can be experienced with setting the clock with the
Time of Day system value. Adjusting takes time to complete because it is not a single,
instantaneous change to the clock. For example, adjusting the clock by 1 second could take 10
seconds of real time to complete. Two hours forward or backward is the maximum amount of
adjustment that can be made.
System value: QTIMZON
A time zone specifies how to set your system time. You can specify a time zone for each system in
your business environment. The time zone setting specifies the offset from UTC and whether to
observe Daylight Saving Time (DST) or not. If you specify to observe Daylight Saving Time, the
system automatically updates the system time when Daylight Saving Time begins and ends. You do
not need to manually set the system time when Daylight Saving Time begins and ends.

© Copyright IBM Corp. 2001, 2016 7-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Change Password

System values © Copyright IBM Corporation 2001, 2016

Figure 7-16. Change Password

The password-composition system values are enforced only when the password is changed using
the CHGPWD command, the change password in IBM Navigator for i, the ASSIST menu option to
change a password, or the QSYCHGPW application programming interface (API). They are not
enforced when the password is set using the CRTUSRPRF or CHGUSRPRF command.
To change password from IBM Navigator for i interface use:
1. On the left pane, click the System on the function tree.
2. On the main pane, click Change Password you can here change your password or password
of another user if you have rights to do that.

© Copyright IBM Corp. 2001, 2016 7-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Password rules for changing password

Password validation program
N Pass
rules

Message Y

N
QPWDVLDPGM

Y
Validation
program

Message N
PGM
detects
error? Password
changed
Y
System values © Copyright IBM Corporation 2001, 2016

Figure 7-17. Password rules for changing password

If *REGFAC or a program name is specified in the QPWDVLDPGM system value, the system runs
one, or more programs after the new password has passed any validation tests you specify in the
password-control system values. You can use the programs to do additional checking of
user-assigned passwords before they are accepted by the system.
The topic “Using a Password Approval Program” in the book System i Security Reference
discusses the requirements of the password approval program and shows an example.

© Copyright IBM Corp. 2001, 2016 7-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Review questions
1. True or False: In order to implement security on your
system, you must install additional security software on your
system.

2. True or False: It is possible to lock out users from changing

system values.

3. True or False: One of the components available to

implement security on your system is System Values.

4. True or False: Only a security officer can change system

values.

5. True or False: The default security level shipped on the

system is Level 50.

System values © Copyright IBM Corporation 2001, 2016

Figure 7-18. Review questions

© Copyright IBM Corp. 2001, 2016 7-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Review answers
1. True or False: In order to implement security on your system,
you must install additional security software on your system.
The answer is False.

2. True or False: It is possible to lock out users from changing

system values.
The answer is True.

3. True or False: One of the components available to implement

security on your system is System Values.
The answer is True.

4. True or False: Only a security officer can change system

values.
The answer is False.

5. True or False: The default security level shipped on the system

is Level 50.
The answer is False.
System values © Copyright IBM Corporation 2001, 2016

Figure 7-19. Review answers

© Copyright IBM Corp. 2001, 2016 7-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 7. System values

Uempty

Unit summary
• List and explain the levels of security available
• Describe the capability in service tools to lock out users from changing
system values
• Define the different categories of system values available
• Explain how to use security policies to set system values
• List the commands used to set system values when using a 5250
emulation session
• List the steps used in System i Navigator to manipulate system values

System values © Copyright IBM Corporation 2001, 2016

Figure 7-20. Unit summary

© Copyright IBM Corp. 2001, 2016 7-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Unit 8. User security

Estimated time
00:40

Overview
There are three components used to implement security on the system. The operating system
continually checks system values, user profiles, and an object's resource security as it receives
requests from users to determine whether that user will be allowed to access the object in question.
In this unit, we will discuss user security. We will look at how to use user profiles to customize the
capabilities that a user will have once they are signed on to the system.

How you will check your progress

• Review questions
• Machine exercises

© Copyright IBM Corp. 2001, 2016 8-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Unit objectives
• Explain the purpose served by user profiles
• List the steps to create a user profile
• Explain the purpose served by group profiles
• List the steps to create a group profile

User security © Copyright IBM Corporation 2001, 2016

Figure 8-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 8-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Security components

People Objects
(Users) (Resources)
User Individual
Profiles Objects
Job Library/Directory
Descriptions
Authorization
Group Profiles
Lists

System Values

User security © Copyright IBM Corporation 2001, 2016

Figure 8-2. Security components

There are three components used to implement security on this system. The operating system
continually checks system values, user profiles, and objects as it receives requests from users to
determine whether that user will be allowed to access the object in question.
In this unit we will discuss User and Group Profiles and how you use these to customize the
capabilities and what authority users will have once they are signed on to the system. We will also
look at the capabilities provided by management central in relation to working with users on the
system.

© Copyright IBM Corp. 2001, 2016 8-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Topic 1: User profiles

User security © Copyright IBM Corporation 2001, 2016

Figure 8-3. Topic 1: User profiles

© Copyright IBM Corp. 2001, 2016 8-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Roles served by user profiles

• A user profile has several roles on the system:
ƒ Controls how the user signs on the system
ƒ Controls what the user is allowed to do after signing on
ƒ Establishes how the user’s actions are audited
ƒ Is designed to customize the system and adapt it to the user
ƒ Is used to identify the user’s jobs and printer output
ƒ Contains information about the objects owned by the user
ƒ Contains information about private authorities to objects
ƒ Is a management and recovery tool

User security © Copyright IBM Corporation 2001, 2016

Figure 8-4. Roles served by user profiles

A user profile has several roles on the system:

• It contains security-related information that controls how the user signs on the system, what the
user is allowed to do after signing on, and how the user’s actions are audited.
• It contains information that is designed to customize the system and adapt it to the user.
• It is a management and recovery tool for the operating system. The user profile contains
information about the objects owned by the user and all the private authorities to objects.
• The user profile name identifies the user’s jobs and printer output.

© Copyright IBM Corp. 2001, 2016 8-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

User profile

User information
User profile
Password
Tells the system
Password expiration level
who you are
Initial menu/program
User class
Special authority

List of objects Object

owned authorizations

Static User information

Dynamic List of owned objects

List of object authorizations
User security © Copyright IBM Corporation 2001, 2016

Figure 8-5. User profile

The user profile contains a list of objects owned by the user profile, a list of objects which the user
profile does not own but is otherwise authorized to access, and information about the user: current
library, initial program, initial menu, special authorities, user class, group profile, maximum storage,
and much more.
Every object on the system must have an owner. If an object does not have an owner, it might not
be used, and the RCLSTG command is typically executed in order to assign it to QDFTOWN.
Do not assign all (or nearly all) objects to only one owner profile. Profiles that own many objects
with many private authorities can become very large. To prevent impacts to either performance or
system operations, distribute ownership of objects to multiple profiles.
Avoid applications owned by IBM-supplied user profiles, such as QSECOFR or QPGMR. These
profiles can become difficult to manage because they own a large number of IBM-supplied objects.

© Copyright IBM Corp. 2001, 2016 8-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Appendix B: Default values for user profiles

User security © Copyright IBM Corporation 2001, 2016

Figure 8-6. Appendix B: Default values for user profiles

Refer to the table listed in Appendix B of the System I Security Reference manual, SC41-5302-10.
This table shows the default values that are used for all IBM-supplied user profiles and on the
Create User Profile (CRTUSRPRF) command. The parameters are sequenced in the order they
appear on the Create User Profile display.

© Copyright IBM Corp. 2001, 2016 8-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

New User
5250 interface

GUI interface

User security © Copyright IBM Corporation 2001, 2016

Figure 8-7. New User

Creating a new user profile is a function that can be done from an emulation screen or using IBM
Navigator for i.
When using an emulation session, you can directly key in the command CRTUSRPRF or you can
use option 1=Create of off the WRKUSRPRF screen.
With IBM Navigator for i
1. On the left pane click Users and Groups.
2. On the main pane click Create User.

© Copyright IBM Corp. 2001, 2016 8-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Create a new user

5250 interface

GUI interface

User security © Copyright IBM Corporation 2001, 2016

Figure 8-8. Create a new user

Specify required parameters

Password - Specifies the password for the user. The rules that determine whether a password is
valid are specified on the Password System Values dialog (expand Configuration and Service to
see System Values).
No password - No password (sign-on not allowed). If you specify no password for this user, the
user cannot sign on. The user is still functioning and programs or other users can access its
resources. For example, some IBM-supplied profiles and group profiles.
Enable user for processing - Specifies whether the user is enabled or disabled. A user that is
disabled cannot sign on to the system.
For IBM Navigator for I you have to use Capabilities link to enter additional parameters.

© Copyright IBM Corp. 2001, 2016 8-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

New User: Capabilities > Privileges

User security © Copyright IBM Corporation 2001, 2016

Figure 8-9. New User: Capabilities > Privileges

Based on their privilege class, users can be given privileges that allow certain actions on system
resources. The Capabilities Privileges dialog specifies the privileges for a user or for a group (and
the members of the group).
System privileges
Specifies the system privileges for this user or group. Privileges are required to perform certain
functions on the system. When you are working with a group, the privileges specified apply to all
users who are members of the group.

© Copyright IBM Corp. 2001, 2016 8-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

System privileges
• All object access (*ALLOBJ)
• Auditing control (*AUDIT)
• Job control (*JOBCTL)
• Save/restore (*SAVSYS)
• Security administration (*SECADM)
• Spool control (*SPLCTL)
• System configuration (*IOSYSCFG)
• System service access (*SERVICE)

User security © Copyright IBM Corporation 2001, 2016

Figure 8-10. System privileges

All object access - (*ALLOBJ) The user can access any system resource whether or not the user
has private authority.
Auditing Control - (*AUDIT) The user has authority to perform auditing functions. This authority is
granted to users who turn auditing on or off for the system and control the level of auditing on an
object or user.
Job control - (*JOBCTL) The user has authority to change, display, hold, release, cancel, and
clear all jobs running on the system or on a job queue or output queue that is operator controlled.
The user also has the authority to start writers, and to stop active subsystems. This authority is
usually granted to users who operate the system.
Save/restore - (*SAVSYS) The user has authority to save, restore, and free storage for all objects
on the system, whether or not the user has authority to the object. This authority is usually granted
to users who operate the system.
Security administration - (*SECADM) The user can create, change, or delete user profiles, if
authorized to those commands and the user profiles.
Spool control - (*SPLCTL) The user can perform all spool functions.

© Copyright IBM Corp. 2001, 2016 8-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
System configuration - (*IOSYSCFG) The user has authority to change system I/O
configurations.
System service access - (*SERVICE) The user can perform service functions.
The system security level determines what the default special privileges are for each user.

© Copyright IBM Corp. 2001, 2016 8-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Privilege classes
System Privilege Classes
Privileges
Security Security System
Programmer User
officer administrator operator

All object
X 20 20 20 20
access
Auditing
X
control

Job control X 20 X 20

Save/restore X 20 X 20 20

Security
X X
administration

Spool control X

System
X
configuration
System service
X
access

User security © Copyright IBM Corporation 2001, 2016

Figure 8-11. Privilege classes

The table shows the privilege classes available on the system. Each class has a default set of
system privileges. The authorities specified under System privileges override the default privileges
for this user or group. When you are working with a group, the privileges specified apply to all users
who are members of the group.
Choices are:
• User - The user's default privileges are save/restore and all object access for security levels 10
and 20. The user does not get any privileges at other security levels.
• Programmer - The user's default privileges are save/restore, job control, and all object access
for security levels 10 and 20. The user does not get any privileges at other security levels.
• System operator - The user's default privileges are save/restore, job control, and all object
access for security levels 10 and 20. The user's default privileges are save/restore and job
control at other security levels.
• Security administrator - The user's default privileges are save/restore, job control, security
administration, and all object access for security levels 10 and 20. The user's special authority
is security administration at other security levels.

© Copyright IBM Corp. 2001, 2016 8-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
• Security officer - The user's default privileges are all object access, save/restore, auditing
control, security administration, system configuration, system service access, job control, and
spool control.

© Copyright IBM Corp. 2001, 2016 8-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Capabilities: Applications

User security © Copyright IBM Corporation 2001, 2016

Figure 8-12. Capabilities: Applications

Using the Applications page you can identify which functions a user or group can access. Where
the access is derived from is also displayed. Access for allows you to select one of the following
categories of applications:
• IBM Navigator for i - Includes IBM Navigator for i and any plug-in extensions.
• Client Applications - Includes all client applications that provide functions on clients that can
be administered through Application Administration.
• Host Applications - Includes all applications that reside entirely on the System i and provide
functions that can be administered through Application Administration.
You can customize access for a user or group to a specific function. Where the access is derived
from is also displayed.
Access to the functions is restricted as follows:
• Default Access: Determines whether the user has Default Access to the functions when the
user or group is not explicitly allowed or denied access.
• All Object Access: Defines whether a user or group with All Object System privilege is allowed
access to the function.

© Copyright IBM Corp. 2001, 2016 8-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
• Customized Access: Users with security administration privilege can explicitly allow or deny
access of users or groups to specific functions.
There is a set of commands that can be called from a 5250 emulation session. The Work with
Function Usage (WRKFCNUSG) command shows a list of function identifiers and allows you to
change or display specified functions. There is also a CHGFCHUSG and DSPFCNUSG command
available.

© Copyright IBM Corp. 2001, 2016 8-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Capabilities: Password and Unique Identifier

User security © Copyright IBM Corporation 2001, 2016

Figure 8-13. Capabilities: Password and Unique Identifier

Requiring users to change their passwords after a specified length of time reduces the risk of an
unauthorized person accessing the system. The Capabilities – Password dialog specifies the
change interval used for the user’s password. The number of days the user’s password is valid can
be specified in the system value. Also, the number of days can be specified explicitly or the user’s
password can never expire.
Password
Specifies that the password uses the specified system value. The QPWDEXPITV (password
expiration) system value controls the number of days a password is valid.
How to manage the password:
Manage this password locally
When you select this option, the password can be managed on the local system. This is the
recommended setting. This field corresponds to the local password management (LCLPWDMGT)
parameter of the CRTUSRPRF and CHGUSRPRF commands.

© Copyright IBM Corp. 2001, 2016 8-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
Manage this password remotely
When you select this option the password will not be managed on the local system. Specifying this
value will cause the local i5/OS password to be set to *NONE. The password value specified in the
password parameter will be sent to other IBM products and options that do password
synchronization (for example, Integrated Server support). The user will not be able to change their
own password using the Change Password (CHGPWD) command. They will not be able to sign on to
the system directly.
Time limit for password changes:
Specifies the value for blocking password changes once the password has been successfully
changed.
As specified by system value
The system value is used to determine this field QPWDCHGBLK specifies that the password uses
the specified system value. The QPWDCHGBLK (Block password changes) system value controls
the password blocking.
None
Specifies that no password blocking exists for this user.
Hours after last change (1-99)
The number of hours until a password is allowed to be changed.

© Copyright IBM Corp. 2001, 2016 8-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Capabilities: UID

User security © Copyright IBM Corporation 2001, 2016

Figure 8-14. Capabilities: UID

Unique Identifier
The system uses the user identification (UID) number to identify a user and to verify the user's
authority. For most installations, the best approach is to let the system choose a unique number for
the new user's UID. However, if your system is part of a network, you might need to assign UID
numbers to match those assigned on other systems in the network. When moving files across
systems, or managing users across systems, it is very important that the UID is preserved across
systems for a specific user.
• Set the UID to a specific number - If your system is part of a network, you might need to assign
a specific UID number to match those assigned on other systems in the network. If you specify
a UID number, use a number from 1 to 4,294,967,294.
• Let each System i choose a unique number - For best results, let each system generate these
numbers. This option is available only when you are creating a new user.
• Find a unique number across all selected systems - If you are adding a new user to an endpoint
system or to multiple systems

© Copyright IBM Corp. 2001, 2016 8-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

New User: Jobs > General

User security © Copyright IBM Corporation 2001, 2016

Figure 8-15. New User: Jobs > General

Each piece of work in a system is called a job, and each job has a unique name. Jobs can have
values that determine how they are run on the system. These values can be specified for a user on
the Jobs - General dialog.
Current Library - The current library is searched before the libraries in the user portion of the
library list for any objects specified as *LIBL. If the user creates objects and specifies *CURLIB, the
objects are put in the current library.
Job Description - When a user signs on, the system looks at the workstation entry in the
subsystem description to determine what job description to use for the interactive job. If the
workstation entry specifies *USRPRF for the job description, the job description in the user profile is
used.
Home directory - Lists the path name of the home directory for this user. The home directory is the
user's initial working directory. If the home directory doesn't exist when the user signs on, the root
directory is used. If you specify a directory path name, use up to 2048 characters.

© Copyright IBM Corp. 2001, 2016 8-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Jobs > Session Startup

User security © Copyright IBM Corporation 2001, 2016

Figure 8-16. Jobs > Session Startup

Initial program
Lists the qualified name of the program called when a user signs on the system. If you are changing
this field, you can specify a program name or you can specify that no program runs initially. If you
specify a program name, use up to 10 characters. You can also specify library where the program
is.
Initial menu
Lists the qualified name of the menu displayed when the user signs on the system. If you are
changing this field, you can specify the main menu, or you can type the name of another menu to
be shown when the user signs on. You can also specify Sign off to sign the user off the system after
the initial program has run. If you specify a menu name, use up to 10 characters. You can also
specify library where the menu exists.
Display sign-on information
Indicates whether the sign-on information shows when the user signs on the system. If you are
changing this field, you can specify the system value, to display sign-on information, or to not
display it. Sign-on information includes date of last sign-on, sign-on attempts that were not valid,
and number of days before the user’s password expires if the password is due to be changed.

© Copyright IBM Corp. 2001, 2016 8-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
Number of device sessions a user can have
Indicates the number of device sessions a user can have.
As specified by system value
Specifies that the password uses the specified system value. The QLMTDEVSSN (Limit Device
Sessions) system value controls the number of device sessions.
No limit
There is no limit specified for the number of device sessions.
Device sessions (1-9)
The number of device sessions that a user can have.

© Copyright IBM Corp. 2001, 2016 8-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Jobs > Display Session

User security © Copyright IBM Corporation 2001, 2016

Figure 8-17. Jobs > Display Session

Attention Program - The Attention-key-handling program (ATNPGM) is the program that is called
when the user presses the Attention (ATTN) key during an interactive job.
Limit initial program/menu capability - Lists the limits the user has over the initial program, initial
menu, current library, and the ATTN key handling program values while signed on to an I Series
session. This value is ignored when the security level is 10. If you are changing this field, you can
specify no limit, partial limit, or full limiting of the user's capabilities where the user cannot change
the program, menu, or current library. If specific commands are limited, users cannot run them from
the command line.
In PC-Based applications, setting a user profile to LMTCPB(*YES) does not prevent the user from
running an System i command via IBM Navigator for i or Rational Development Studio for i.
Assistance level - The QASTLVL system value is used to determine the assistance level.
Keyboard buffering - The QKBDBUF system value is used.
User options - Lists the level of detail the user sees and the default function of the Page Up and
Page Down keys when the user is signed on the system. The possible values are:
• Show parameter keywords - Parameter keywords are shown instead of the possible
parameter values when a command is displayed.

© Copyright IBM Corp. 2001, 2016 8-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
• Show all details - Detailed information is shown when the user is doing display and edit
options.
• Change direction of rollkey - The actions of the Page Up and Page Down keys are reversed.
• Do not show status messages - The user sees no status messages.
• Show status messages - The user sees status messages.
• Display help on full screen - Help information is shown on full screen.
• Send message to spool file owner - A message is sent to this user's message queue when a
spooled file for this user is printed or held by the printer writer. The owner of the spool file
receives a message.

© Copyright IBM Corp. 2001, 2016 8-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Display Session: Limit capabilities

The Display Session tab allows you to limit user's capability to

change their initial program, menu, current library, and attention
program and prohibit them from running most System i commands.

Limit initial
program/menu Initial Current Attention Execute
Initial Menu
capabilities Program Library Program Commands

Do not limit Yes Yes Yes Yes Yes

Limit some
No Yes No No Yes
capabilities
Limit
No No No No No
capabilities

Users can still run commands created or changed with parameter ALWLMTCPB(*YES).

User security © Copyright IBM Corporation 2001, 2016

Figure 8-18. Display Session: Limit capabilities

The ALWLMTUSR parameter on commands and Limit Capabilities and Limit some capabilities do
not restrict a user from doing the following:
• Running commands in CL programs that are running a command as a result of taking an option
from a menu
• Running remote commands through applications, such as FTP
The commands allowed by default are: DSPMSG, DSPJOB, DSPJOBLOG, and STRPCO, SIGNOFF,
and SNDMSG.

© Copyright IBM Corp. 2001, 2016 8-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Jobs > Output and International

User security © Copyright IBM Corporation 2001, 2016

Figure 8-19. Jobs > Output and International

You can specify the printer used to print the output for this user. Spooled files are placed in an
output queue with the same name as the printer when the output queue (OUTQ) is specified as the
print device (*DEV).
The print device and output queue information from the user profile are used only if the printer file
specifies *JOB and the job description specifies *USRPRF.
You can specify the name of a message queue for a user. A message queue is an object on which
messages are placed when they are sent to a person or a program. A message queue is used
when a user sends or receives messages. If the message queue does not exist, it is created when
the profile is created or changed. The message queue is owned by the profile being created or
changed.
You can specify the language identifier, country, or region identifier to be used by the system for
the user.

© Copyright IBM Corp. 2001, 2016 8-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

New User: Groups > Group Information

User security © Copyright IBM Corporation 2001, 2016

Figure 8-20. New User: Groups > Group Information

Specifying a group profile name makes the user a member of the group profile. The group profile
can provide the user with authority to use objects for which the user does not have specific
authority. You can specify up to 16 additional groups for the user.
If the user is a member of a group, you use the owner parameter in the user profile to specify who
owns any new objects created by the user. Objects can be owned either by the user or by the user’s
first group (the value of the GRPPRF parameter). You can specify the OWNER field only if you have
specified the Group profile field.
If the user profile is a member of a group and OWNER(*USRPRF) is specified, the Group
authority field controls what authority is given to the group profile for any objects created by this
user.
Possible values for GRPAUT:
• *ALL - The group profile is given all management and data authorities to any new objects the
user creates
• *CHANGE - The group profile is given the authority to change any objects the user creates
• *USE - The group profile is given authority to view any objects the user creates

© Copyright IBM Corp. 2001, 2016 8-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
• *EXCLUDE - The group profile is specifically denied access to any new objects created by the
user
When a user creates a new object, the Group authority type parameter in the user’s profile
determines what type of authority the user’s group receives to the new GRPAUT parameters to
determine the group’s authority to a new object.
Possible values for GRPAUTTYP:
• *Private - The authority defined in the GRPAUT parameter is assigned to the group profile as a
private authority
• *PGP - The group profile defined in the GRPPRF parameter is the primary group for the newly
created object. The primary group authority for the object is the authority specified in the
GRPAUT parameter.

© Copyright IBM Corp. 2001, 2016 8-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

New User: Personal > Name, Location, and Mail

User security © Copyright IBM Corporation 2001, 2016

Figure 8-21. New User: Personal > Name, Location, and Mail

Name - More detail about user personality information

Location - phone numbers, department address, building and so on.
MAIL
Mail Service Level - Specifies the type of mailbox for the System i to use to store the user's mail.
The Mail service level value matches the type of email application that the user has.
The possible values are:
• User index
• System mailbox
• Lotus Domino
The System i places all mail for the user in the mailbox type that you specify, regardless of the
source of the mail or the type of address that the sender Specifies on the incoming mail.
Preferred address type - Specifies how System i should format the address on incoming mail for
this user. The possible choices are:
• User ID and Address - uses this addressing scheme for distributing mail.
• SMTP name - Used in an email or Internet network.

© Copyright IBM Corp. 2001, 2016 8-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
Addresses - The Personal Mail dialog shows one or more addresses the System i uses to locate
the user when email arrives. The appearance of the following fields is dependent on the Preferred
address type and the System i configurations.
The possible values are:
• User ID - For mail users with a System i user profile, the user ID is the user profile name.
• Address - Identifies the user. The address usually matches the name of the System i where the
user receives mail.
• System name - Identifies the System i where the user receives mail
• SMTP name - Specifies the user name for email in an SMTP network, including the Internet.
The system inserts the user profile name if the user is not in the System i distribution directory.
The SMTP name can be a value other than the user profile name. The SMTP name can be up
to 64 characters with no blank spaces between characters.
• Domain - Identifies the user's location within an SMTP network.

© Copyright IBM Corp. 2001, 2016 8-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Appendix B: IBM-supplied user profiles

User security © Copyright IBM Corporation 2001, 2016

Figure 8-22. Appendix B: IBM-supplied user profiles

The tables listed in Appendix B of the System I Security reference manual (SC41-5302-10) list each
IBM-supplied profile, its purpose, and any values for the profile that are different from the defaults
for IBM-supplied user profiles. This is the first of multiple tables that are listed in appendix B.
Note: IBM-supplied user profiles now include additional user profiles that are shipped with the
licensed program products. The table includes only some, but not all user profiles for licensed
program products; therefore, the list is not inclusive.
Attention:
• Password for the QSECOFR profile You must change the password for the QSECOFR profile
after you install your system. This password is the same for every System i product and poses a
security exposure until it is changed. However, Do not change any other values for
IBM-supplied user profiles. Changing these profiles can cause system functions to fail.
• Authorities for IBM-supplied profiles Use caution when removing authorities that IBM-supplied
profiles have for objects that are shipped with the operating system. Some IBM-supplied
profiles are granted private authorities to objects that are shipped with the operating system.
Removing any of these authorities can cause system functions to fail.

© Copyright IBM Corp. 2001, 2016 8-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

User functions

User security © Copyright IBM Corporation 2001, 2016

Figure 8-23. User functions

In the user list you can select the user and right-click to see available function for your user.
On the left pane click Users and Groups.
On the main pane click Users.
Select user and right-click to see pop-up menu and available functions.

© Copyright IBM Corp. 2001, 2016 8-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Changing a user profile

User security © Copyright IBM Corporation 2001, 2016

Figure 8-24. Changing a user profile

You can change a user profile using option 2 (Change) from either the Work with User Profiles
display or the Work with User Enrollment display. You can also use the Change User Profile
(CHGUSRPRF) command.
On the left pane click Users and Groups.
On the main pane click Users.
Select user and right-click to see pop-up menu and from menu select Properties.

© Copyright IBM Corp. 2001, 2016 8-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Deleting a user profile

User security © Copyright IBM Corporation 2001, 2016

Figure 8-25. Deleting a user profile

You cannot delete a user profile that owns objects. You must first delete any objects owned by the
profile or transfer ownership of those objects to another profile.
You cannot delete a user profile if it is the primary group for any objects.
When you delete a user profile, the user is removed from all distribution lists and from the system
directory.
Scan for owned objects: List the objects in the system owned by this user. The output from this is
quite interesting as it includes objects you know about as well as internal work objects the system
uses for this user while the user is active.

© Copyright IBM Corp. 2001, 2016 8-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Exercise: Create a user profile

• At the end of the exercise, you should be able to:
ƒ Use IBM Navigator for i to create a user profile

Systems to be used for class:

Name TCP/IP Address
Teach system __________ __________

User security © Copyright IBM Corporation 2001, 2016

Figure 8-26. Exercise: Create a user profile

© Copyright IBM Corp. 2001, 2016 8-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Topic 2: Group profiles

User security © Copyright IBM Corporation 2001, 2016

Figure 8-27. Topic 2: Group profiles

© Copyright IBM Corp. 2001, 2016 8-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Roles served by group profiles

• Security tool:
ƒ Provides a method for organizing authorities and sharing them among users
ƒ Used to define object or special authorities for group profiles rather than for
each individual user profile
ƒ A user can be a member of up to 16 group profiles

• Customizing tool:
ƒ A group profile can be used as a pattern for creating individual user profiles
ƒ You create group profiles in the same way that you create individual profiles
ƒ The system recognizes a group profile when you add the first member to it
ƒ The system also generates a group identification number (GID) for the profile

User security © Copyright IBM Corporation 2001, 2016

Figure 8-28. Roles served by group profiles

A group profile is a special type of user profile that provides the same authority to a group of users.
A group profile serves two purposes on the system:
• Security tool - A group profile provides a method for organizing authorities on your system and
sharing them among users. You can define object authorities or special authorities for group
profiles rather than for each individual user profile. A user can be a member of up to 16 group
profiles.
• Customizing tool - A group profile can be used as a pattern for creating individual user
profiles. Most people who are part of the same group have the same customizing needs, such
as the initial menu and the default printer. You can define these things in the group profile and
then copy the group profile to create individual user profiles.
You create group profiles in the same way that you create individual profiles. The system
recognizes a group profile when you add the first member to it. At that point, the system sets
information in the profile indicating that it is a group profile. The system also generates a group
identification number (GID) for the profile. You can also designate a profile as a group profile at the
time when you create it by specifying a value in the GID parameter.

© Copyright IBM Corp. 2001, 2016 8-37

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

More facts about group profiles

• Allows users with similar jobs to share permissions without having to
share the same password
• Should choose a naming convention which makes groups easily
recognizable
• Create with No password (signon not allowed)
• Should assign groups in order of use
• Permissions are additive at the group level

User security © Copyright IBM Corporation 2001, 2016

Figure 8-29. More facts about group profiles

© Copyright IBM Corp. 2001, 2016 8-38

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

New Group

User security © Copyright IBM Corporation 2001, 2016

Figure 8-30. New Group

To create new group:

1. On the left pane click Users and Group.
2. On the main pane click Create Group.
You can create new user group based on the existing group, or create new one not base on any.

© Copyright IBM Corp. 2001, 2016 8-39

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

New Group > Capabilities

User security © Copyright IBM Corporation 2001, 2016

Figure 8-31. New Group > Capabilities

You can add existing users to the list. Additionally you can define privileges.

© Copyright IBM Corp. 2001, 2016 8-40

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

New Group > Networks

User security © Copyright IBM Corporation 2001, 2016

Figure 8-32. New Group > Networks

The user identification (UID) and group identification (GID) numbers identify the group to the
system. For best results, let each system choose a unique number for the UID and GID of the new
group. However, if your system is part of a network, you might need to assign specific UID and GID
numbers to match those assigned on other systems in the network. When moving files across
systems or managing users across systems, it is very important that the unique identifiers are
preserved across systems for a specific group.

© Copyright IBM Corp. 2001, 2016 8-41

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Group functions

User security © Copyright IBM Corporation 2001, 2016

Figure 8-33. Group functions

To work with available group functions:

1. On the left pane click Users and Groups.
2. On the main pane click Groups.
3. Right-click the group name and on the pop-up menu you can see available functions.

© Copyright IBM Corp. 2001, 2016 8-42

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Deleting a group

User security © Copyright IBM Corporation 2001, 2016

Figure 8-34. Deleting a group

When deleting a group, you have to determine what to do if the group is the primary group of
objects. Primary group authority gives a group profile permission to an object. This permission is
stored with the object.
Groups that have system names (typically ones that start with Q like QSECOFR) cannot be
deleted.
Groups that have user members cannot be deleted.
Groups can be deleted if all owned objects and primary group objects are successfully transferred
to the specified group.
Groups can be changed if a new group name is specified to identify where to transfer ownership of
the owned objects.
Action to take if group is primary group of objects
Some objects have a form of authority known as primary group authority stored with the object. You
can select one of the following actions to take if the group you are deleting is the primary group of
any i5/OS objects:
• Do not delete group
You choose not to delete this group if it is the primary group of objects.

© Copyright IBM Corp. 2001, 2016 8-43

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty
• Remove primary group from objects
The group will be removed as the primary group for objects and deleted from the system.
• Change primary group
The group will be deleted from the system and you will select a different group as the primary
group for objects that had this group as the primary group.
Action to take if group owns objects
Specifies the action to take if the group you are deleting owns objects. Possible choices are:
• Do not delete
Select this to cancel the group delete action if the group owns objects.
• Delete objects that group owns
Select this to delete the objects that the group owns when the group is deleted.
• Transfer objects to another user
Select this to transfer ownership of objects to a different user. The objects are transferred to the
new user regardless of that user's current authority to the objects.
Scan for Owned Objects...
Click Scan for Owned Objects to scan the selected system for objects that the selected users or
groups own.

© Copyright IBM Corp. 2001, 2016 8-44

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Review questions (1 of 2)
1. True or False: User profiles are one of the security
components available to implement security on the system.

2. Which of the following is not specified in a user profile?

a. Password
b. User classification
c. Security level defined on the system
d. List of owned object

3. The (blank) special authority allows a user access to all

system resources.
a. *ALLOBJ
b. *JOBCTL
c. *SPLCTL
d. *SECADM

4. True or False: A user profile can be used to specify an initial

program to be called when the user signs on to the system.

User security © Copyright IBM Corporation 2001, 2016

Figure 8-35. Review questions (1 of 2)

© Copyright IBM Corp. 2001, 2016 8-45

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Review answers (1 of 2)
1. True or False: User profiles are one of the security components available to
implement security on the system.
The answer is true.

2. Which of the following is not specified in a user profile?

a. Password
b. User classification
c. Security level defined on the system
d. List of owned object
The answer is security level defined on the system.

3. The *ALLOBJ special authority allows a user access to all system resources.
a. *ALLOBJ
b. *JOBCTL
c. *SPLCTL
d. *SECADM
The answer is *ALLOBJ.

4. True or False: A user profile can be used to specify an initial program to be called
when the user signs on to the system.
The answer is true.
User security © Copyright IBM Corporation 2001, 2016

Figure 8-36. Review answers (1 of 2)

© Copyright IBM Corp. 2001, 2016 8-46

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Review questions (2 of 2)
5. By specifying (blank), you can keep a user from changing
which menu and which library they will sign on to from the
sign-on screen.
a. Do not limit capabilities
b. Limit some capabilities
c. Limit capabilities

6. True or False: Ideally, group profiles should be created with a

password of *NONE because you should not sign on to the
system using this group ID.

7. The maximum number of group profiles that a user can

belong to is?
a. 16
b. 32
c. 64
d. *NOLIMIT

User security © Copyright IBM Corporation 2001, 2016

Figure 8-37. Review questions (2 of 2)

© Copyright IBM Corp. 2001, 2016 8-47

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Review answers (2 of 2)
5. By specifying limit some capabilities, you can keep a user from changing
which menu and which library they will sign on to from the sign-on screen.
a. Do not limit capabilities
b. Limit some capabilities
c. Limit capabilities
The answer is limit some capabilities.

6. True or False: Ideally, group profiles should be created with a password of

*NONE because you should not sign on to the system using this group ID.
The answer is true.

7. The maximum number of group profiles that a user can belong to is?
a. 16
b. 32
c. 64
d. *NOLIMIT
The answer is 16.

User security © Copyright IBM Corporation 2001, 2016

Figure 8-38. Review answers (2 of 2)

© Copyright IBM Corp. 2001, 2016 8-48

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 8. User security

Uempty

Unit summary
• Explain the purpose served by user profiles
• List the steps to create a user profile
• Explain the purpose served by group profiles
• List the steps to create a group profile

User security © Copyright IBM Corporation 2001, 2016

Figure 8-39. Unit summary

© Copyright IBM Corp. 2001, 2016 8-49

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Unit 9. Resource security

Estimated time
00:30

Overview
There are three components used to implement security on this system. The operation system
continually checks system values, user profiles, and an object's resource security as it receives
requests from users to determine whether that user will be allowed to access the object in question.
In this unit, we will discuss resource security and how you can customize what actions a user can
perform against the data once an object is accessed.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 9-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Unit objectives
• Describe what resource security is and how it is implemented
• Explain how ownership of an object is established
• Explain the purpose served by the QDFTOWN user profile
• Explain how public authority is assigned to an object
• Explain the difference between object management authority and data
authority that can be assigned to an object
• Describe the search order used by the system to determine whether a
user is allowed to access an object
• Explain what means RCAC means and how to implement it

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 9-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Security components

People Objects
(Users) (Resources)
User Individual
Profiles Objects
Job Library/Directory
Descriptions
Authorization
Group Profiles
Lists

System Values

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-2. Security components

In this unit you can learn more about resource security.

© Copyright IBM Corp. 2001, 2016 9-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Topic 1: Resource security

concepts

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-3. Topic 1: Resource security concepts

© Copyright IBM Corp. 2001, 2016 9-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

User-owned objects
• Each object has one owner.
• The user who creates an object is assigned as the owner.
• The owner initially has all object and data permission.
• The authority can be removed, but the owner can grant any authority
back to themself at any time.
• The ownership of an object can be transferred to another user.
• It is not possible to delete a user who owns objects. Two solutions are
offered:
ƒ Transfer ownership
ƒ Delete owned objects

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-4. User-owned objects

© Copyright IBM Corp. 2001, 2016 9-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Primary group authority

• Stored in the object header: Good for performance

• Only one primary group authority per object, unlike real private
authorities where there can be many per object

• Object owner cannot be primary group for object

• When assigning a primary group:

ƒ Object created by profile with GRPAUTTYP(*PGP)
ƒ Use WRKOBJPGP or CHGOBJPGP to specify primary group object
ƒ Use CHGPGP for objects in the integrated file system

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-5. Primary group authority

© Copyright IBM Corp. 2001, 2016 9-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

QDFTOWN
• QDFTOWN is an IBM-supplied user profile used when:
ƒ An object has no owner.
ƒ The object ownership might pose security exposure.

• The object ownership is assigned to QDFTOWN in the following cases:

ƒ The owning profile becomes damaged and is deleted. The RCLSTG
command assigns ownership of objects to QDFTOWN.
ƒ An object is restored and the owner profile does not exist.
ƒ A program that needs to be created again is restored, but program creation
is not successful.
ƒ The maximum storage limit is exceeded for the user profile that owns an
authority holder that has same name as file being moved, renamed, or
whose library is being renamed.

• Consider the following recommendations:

ƒ QDFTOWN should not normally own objects.
ƒ Ownership can be transferred with the WRKOBJOWN command or by IBM
Navigator for i.
Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-6. QDFTOWN

© Copyright IBM Corp. 2001, 2016 9-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Where object permissions come from

To access or use an object, you must have the appropriate authority.
• This authority can come from:
ƒ All object access (*ALLOBJ) special authority
ƒ A private or explicit authority to the object
ƒ Authorization list
ƒ Primary group authority
ƒ Public authority (*PUBLIC)
ƒ Adopted authority

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-7. Where object permissions come from

© Copyright IBM Corp. 2001, 2016 9-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Where *PUBLIC authority comes from

Defined by the AUT parameter on the CRTxxx command.
It defaults to *LIBCRTAUT.

System values

QCRTAUT: *CHANGE
Library PAYLIB

CRTAUT: *SYSVAL

Output queue MYQUEUE

AUT(*LIBCRTAUT)

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-8. Where *PUBLIC authority comes from

Every library has a parameter called CRTAUT (create authority). This parameter determines the
default public authority for any new object that is created in that library. When you create an object,
the AUT parameter on the create command determines the public authority for the object. If the
AUT value on the create command is *LIBCRTAUT, which is the default, the public authority for the
object is set to the CRTAUT value for the library.
The QCRTAUT system value is used to determine the public authority for a newly created object if
the following conditions are met:
• The create authority (CRTAUT) for the library of the new object is set to *SYSVAL.
• The new object is created with public authority (AUT) of *LIBCRTAUT.
The default value for the QCRTAUT system value is *CHANGE. This can introduce a higher
authority level to new objects than actually needed. However, prior to V5R3, when changing this
system value to *USE or *EXCLUDE caused problems for some objects, such as automatically
created device descriptions. The default value for the AUT parameter has changed from
*LIBCRTAUT to *CHANGE on several CRT commands for line, controller and device description.

© Copyright IBM Corp. 2001, 2016 9-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Object management authority (1 of 2)

Private and public permissions consist of one or more of the following:

Specific object authorities

Object management

Operational

Management

Existence

Alter

Reference Look at the next visual

Authorization list

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-9. Object management authority (1 of 2)

On the visual you can see object management permissions.

© Copyright IBM Corp. 2001, 2016 9-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Object management authority (2 of 2)

Permission Definition
Operational Look at the description of an object and use the object as
(*OBJOPR) determined by the data authorities the user has.
To open a file, the user must have *OBJOPR.

Management Authorize users to the object, move, or rename the object,

(*OBJMGT) and add members to database files.
All functions defined for *OBJALTER and *OBJREF.

Existence Change ownership and delete the object, free storage for
(*OBJEXIST) the object, and perform save and restore operations for the
object.

Alter Add, clear, initialize, and reorganize members of database

(*OBJALTER) files, alter, and add attributes of database files, add and
remove triggers, and change attributes of SQL packages.

Reference Specify database file as the parent in a referential

(*OBJREF) constraint.

Authorization List Add and remove users and their authorities from an
(*AUTLMGT) authorization list.

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-10. Object management authority (2 of 2)

On the table you can learn what means each permission.

© Copyright IBM Corp. 2001, 2016 9-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Object data authority (1 of 2)

Private and public permissions consist of one or more of the following:

Specific object authorities

Object management Data authority

Operational Read

Management Add

Existence Update

Alter Delete
Look at the next visual
Reference Execute

Authorization list

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-11. Object data authority (1 of 2)

On the visual you can see data authority.

© Copyright IBM Corp. 2001, 2016 9-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Object data authority (2 of 2)

Permission Definition

Read Display the contents of an object, such as viewing the

(*READ) records in a file.

Add Add entries to an object, such as adding messages to a

(*ADD) message queue or records to a file.

Update Change entries in an object, such as changing records

(*UPD) in a file.

Delete Remove entries from an object, such as removing

(*DLT) messages from a message queue or deleting records
from a file.

Execute Run a program or search a library or directory.

(*EXECUTE)

Exclude Object access prevented.

(*EXCLUDE)

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-12. Object data authority (2 of 2)

On the table you can learn what means each data authority.

© Copyright IBM Corp. 2001, 2016 9-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Object exclude authority

Private and public permissions consist of one or more of the following:
Specific object authorities

Exclude

Object management Data authority

Operational Read

Management Add

Existence Update

Alter Delete

Reference Execute

Authorization list

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-13. Object exclude authority

Exclude: The user cannot access the object.

© Copyright IBM Corp. 2001, 2016 9-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Commonly used permissions

Object control Data authority

Operation Management Existence Alter Reference Read Add Update Delete Execute

All X X X X X X X X X X

Change X X X X X X

Use X X X

Exclude

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-14. Commonly used permissions

On the table you can compare Object control and Data authority depending on permission.

© Copyright IBM Corp. 2001, 2016 9-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Integrated file system authority

• *RWX: Object operational authority and all the data authorities
• *RX: Object operational authority, read, and execute
• *RW: Object operational authority, read, add, update, and delete
• *WX: Object operational authority, add, update, delete, and execute
• *R: Object operational authority and read
• *W: Object operational authority, add, update, and delete
• *X: Object operational authority and execute
• *EXCLUDE: Prevents access to object

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-15. Integrated file system authority

© Copyright IBM Corp. 2001, 2016 9-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Building authority checking

*ALLOBJ
Yes
special
authority?
User
No
profile
User specific Yes
authority?

No
Allow access
to object
Yes

Adequate Reject access

authority? No to object

Public
*PUBLIC authority

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-16. Building authority checking

On the diagram you can follow of the authority checking.

© Copyright IBM Corp. 2001, 2016 9-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Topic 2: Defining resource

security

© Copyright IBM Corporation 2001, 2016

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Figure 9-17. Topic 2: Defining resource security

© Copyright IBM Corp. 2001, 2016 9-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Object permission: QSYS.LIB file system

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-18. Object permission: QSYS.LIB file system

To work with object permission using GUI you have to:

1. On the left pane, expand Integrated File Systems.
2. Expand QSYS.LIB.
3. Click the library name where the objects are.
4. On the main pane, right-click the object name and from pop-up menu chose Permissions.

© Copyright IBM Corp. 2001, 2016 9-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Basic and Details permission displays

Basic = Commonly used permissions

Details = Object and data permission

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-19. Basic and Details permission displays

You can see objects permission in Basic view or Details view. To change view, you have to click
the arrow and chose view type and click Go.

© Copyright IBM Corp. 2001, 2016 9-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Permission: Add / Remove

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-20. Permission: Add / Remove

If you want to add another user or group permission to the object you have to click Add button and
then specify or select from the list. Confirm with OK.

© Copyright IBM Corp. 2001, 2016 9-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Permission: Customize

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-21. Permission: Customize

Use the Customize button to customize the permissions for the selected user or group.

© Copyright IBM Corp. 2001, 2016 9-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Permission: Authorization List

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-22. Permission: Authorization List

On the Authorization List dialog, you can select the authorization list that is used to secure the
object. This window is shown when the Authorization List button is selected from the Permissions
window.
Object: Specifies the path name of the object secured by the authorization list.
Type: Specifies the type of the object secured by the authorization list.
Authorization list: Select an authorization list from the menu. Click Browse to open the
Authorization list dialog and view details about the authorization list.

© Copyright IBM Corp. 2001, 2016 9-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Change owner: Change primary group

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-23. Change owner: Change primary group

Use the Primary Group dialog to select a new primary group for the object. Only one group can be
selected. The groups can be expanded so you can see which users are in the group, but a user
might not be selected. This window is shown when the Primary Group button is selected from the
Permissions window or the Edit window.

Note

Using a primary group gives you better performance. A new primary group is assigned the authority
of the old primary group.

© Copyright IBM Corp. 2001, 2016 9-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Topic 3: Column-level
authority

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-24. Topic 3: Column-level authority

© Copyright IBM Corp. 2001, 2016 9-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Column-level security
GRANT UPDATE (CDTLMT) ON QCUSTCDT TO AS27

CUSNUM LSTNAM CDTLMT

938472 HENNING 5000

397267 TYRON 1000
693829 THOMAS 9999

AS27 group: Needs

AS2701: No
Update access
Update access

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-25. Column-level security

Column-level security allows you better protect your data by more granular level.

© Copyright IBM Corp. 2001, 2016 9-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Granting column-level permission

MANAGER: Suppose AS27 group already has specific *USE authority to QCUSTCDT
Grant AS27 group update authority to CDTLMT:

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-26. Granting column-level permission

To grant authority to column you have to on Permissions window click arrow next to the Authority
view field and select Columns and press Go. After this you will see rights to the table columns.

© Copyright IBM Corp. 2001, 2016 9-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Column-level security considerations

• Column-level security enforcement primarily occurs during the update
operation on the file

• No new enforcement during open of the file

• Column-level authorities are stored in the database file object and

managed by DB2 for i

• Object authorities are stored in the user profile and managed by the
system security manager

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-27. Column-level security considerations

© Copyright IBM Corp. 2001, 2016 9-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Security - Separation of duties

Before 7.2

• Problem: Anyone who has the authority to grant privileges also has the
authority to perform operations that require those privileges.
Should the security administrator be able to
access the data within tables?

IBM i 7.2 with RCAC

• Enable the management of security, without exposing the data to be

read or modified.
• A user with security administration function usage
(QIBM_DB_SECADM) will be able to grant or revoke privileges on any
object to anyone, even if they do not have the SELECT privilege.

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-28. Security - Separation of duties

RCAC limits data access to those users who have a business “need to know”. RCAC makes it easy
to set up a rich and robust security policy that is based on roles and responsibilities.
RCAC functionality is made available through the optional, no charge feature called “IBM Advanced
Data Security for i”, also known as option 47 of IBM i 7.2.
In DB2 for i, RCAC is implemented using two different approaches that address the shortcomings
of traditional control methods and mechanisms:
• Row permissions
• Column masks
Another benefit of RCAC is that no database user is automatically exempt from the control. Users
with *ALLOBJ authority can no longer freely access all of the data in the database unless they have
the appropriate permission to do so. The ability to manage row permissions and column masks
rests with the database security administrator. The RCAC definitions, enablement, and activation
are controlled by SQL statements. Row permissions and column masks require virtually no
application changes. RCAC is based on specific rules that are transparent to existing applications
and SQL interfaces. Enforcement of your security policy does not depend on how applications or
tools access the data. RCAC also facilitates multi-tenancy, which means that several independent
customers or business units can share a single database table without being aware of one another.

© Copyright IBM Corp. 2001, 2016 9-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty
The RCAC row permission ensures that each user sees only the rows they are entitled to view
because the enforcement is handled by DB2 and not the application logic.

© Copyright IBM Corp. 2001, 2016 9-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

What is RCAC? IBM Advanced Data Security for i

(Boss option 47)
• Additional layer of data
security available with DB2 No Charge

• Complementary to table
level security
• Subsetting access to only the
required data for a task
• Controls access to a table at
the row, column, or both
• Two sets of rules
ƒ Permissions for rows
ƒ Masks for columns

• IBM Advanced Data

Security for i
ƒ No-charge feature - Option 47

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-29. What is RCAC?

RCAC is an additional layer of security and is complimentary to table level authorizations already in
DB2 LUW. RCAC will work in conjunction with authorizations already in place.
RCAC does have the ability to protect at the table row level, table column level, or both, providing a
masking of result sets to the users based on the protection in place. This is done by using rules
which are created and we will discuss this further in this presentation.
The image on the slide simply shows at a high, non-specific level, that the SSN column is masked
out (it is in green) and that a number of rows are not returned (in red) based on a row permission
defined.

© Copyright IBM Corp. 2001, 2016 9-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

IBM Advanced Data Security for i (Boss Option 47)

• Option must be installed to use:
ƒ CREATE PERMISSION and CREATE MASK (RCAC)
ƒ Open a file that has RCAC activated
• RCAC constructs exist within the table (*FILE) and get applied by SQE
• RCAC does not replace object authorization requirements
ƒ If you pass the object authorization check:
í Row permissions reduce the set of rows returned
í Column Masks limit full or partial access to sensitive column data
• RCAC is comprehensive and applies to any interface
(Native DB, SQL, RPG, APIs, and so on)
• Row Permissions are a replacement technology for Views / Logical
Files
• Only users with QIBM_DB_SECADM authority can manage RCAC

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-30. IBM Advanced Data Security for i (Boss Option 47)

© Copyright IBM Corp. 2001, 2016 9-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Row permissions - 5250 interface

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-31. Row permissions - 5250 interface

A row permission is a database object that manifests a row access control rule for a specific table.
It is essentially a search condition that describes which rows you can access. For example, a
manager can see only the rows that represent their employees.
To create row permission, you have to use SQL statement. Bellow is example how to create
permissions.
CREATE PERMISSION HR_SCHEMA.PERMISSION1_ON_EMPLOYEES
ON HR_SCHEMA.EMPLOYEES AS EMPLOYEES
FOR ROWS
WHERE ( VERIFY_GROUP_FOR_USER ( SESSION_USER , 'HR' ) = 1 )
OR ( VERIFY_GROUP_FOR_USER ( SESSION_USER , 'MGR' ) = 1
AND ( EMPLOYEES . MANAGER_OF_EMPLOYEE = SESSION_USER
OR EMPLOYEES . USER_ID = SESSION_USER ) )
OR ( VERIFY_GROUP_FOR_USER ( SESSION_USER , 'EMP' ) = 1
AND EMPLOYEES . USER_ID = SESSION_USER )
ENFORCED FOR ALL ACCESS
ENABLE ;

© Copyright IBM Corp. 2001, 2016 9-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Row permissions - IBM Navigator for i

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-32. Row permissions - IBM Navigator for i

You can also create Row permissions using IBM Navigator for i to that you have to:
1. On the left pane expand Database.
2. Expand Databases (normally system name is the database name but can be different
especially if you have IASP.
3. Expand Schemas.
4. Click your schema (library).
5. On the main pane right-click the Row Permissions link and from pop-up menu select New >
New Permissions.

© Copyright IBM Corp. 2001, 2016 9-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Column Mask

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-33. Column Mask

A column mask is a database object that manifests a column value access control rule for a specific
column in a specific table. It uses a CASE expression that describes what you see when you
access the column. For example, a teller can see only the last 4 digits of a tax identification number.
On the visual is an example of the mask creation.

© Copyright IBM Corp. 2001, 2016 9-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Column Mask - IBM Navigator for i

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-34. Column Mask - IBM Navigator for i

You can also create column masking using IBM Navigator for i to that you have to:
1. On the left pane expand Database.
2. Expand Databases (normally system name is the database name but can be different
especially if you have IASP.
3. Expand Schemas.
4. Click your schema (library).
5. On the main pane right-click the Column Masks link and from pop-up menu select New >
Column Mask.

© Copyright IBM Corp. 2001, 2016 9-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Exercise: Resource security and group profiles

• At the end of the exercise, you should be able to:
ƒ Grant a user profile permission to an object
ƒ Add a user as a member of a group profile

Systems to be used for class:

Name TCP/IP Address
Teach system __________ __________

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-35. Exercise: Resource security and group profiles

© Copyright IBM Corp. 2001, 2016 9-37

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Review questions
1. True or False: An object can be owned by multiple users on the
system.

2. True or False: The name of the primary group and its authority to
the object are stored in the object header.

3. When an object does not have an owner specified, it gets assigned

to the (blank) user profile.
a. *USER
b. *SECOFR
c. *SYSOPR
d. QDFTOWN

4. True or False: The QCRTAUT system value is used to determine

the public authority for a newly created object.

5. True or False: Read, Add, and Update are authorities that can be
specified to the object management authority for a specific object.
Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-36. Review questions

© Copyright IBM Corp. 2001, 2016 9-38

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Review answers
1. True or False: An object can be owned by multiple users on the system.
The answer is false.

2. True or False: The name of the primary group and its authority to the object are
stored in the object header.
The answer is true.

3. When an object does not have an owner specified, it gets assigned to the
QDFTOWN user profile.
a. *USER
b. *SECOFR
c. *SYSOPR
d. QDFTOWN
The answer is QDFTOWN.

4. True or False: The QCRTAUT system value is used to determine the public authority
for a newly created object.
The answer is true.

5. True or False: Read, Add, and Update are authorities that can be specified to the
object management authority for a specific object.
The answer is false.
Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-37. Review answers

© Copyright IBM Corp. 2001, 2016 9-39

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 9. Resource security

Uempty

Unit summary
• Describe what resource security is and how it is implemented
• Explain how ownership of an object is established
• Explain the purpose served by the QDFTOWN user profile
• Explain how public authority is assigned to an object
• Explain the difference between object management authority and data
authority that can be assigned to an object
• Describe the search order used by the system to determine whether a
user is allowed to access an object
• Explain what means RCAC means and how to implement it

Resource security © Copyright IBM Corporation 2001, 2016

Figure 9-38. Unit summary

© Copyright IBM Corp. 2001, 2016 9-40

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Unit 10. Authorization lists and adopted

authority
Estimated time
00:25

Overview
Authorization lists provide another way to secure an object. In this unit, we will discuss
authorization list concepts. We will look at how these are created and how to specify which list is
used to secure an object. We will also compare and contrast the function provided by user groups
versus authorization lists. Then we will take a look at how you can temporarily assign security for an
object. We will discuss how adopted authority works and the steps to implement it.

How you will check your progress

• Review questions
• Machine exercises

© Copyright IBM Corp. 2001, 2016 10-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Unit objectives
• Explain the purpose served by an authorization list
• List the steps to secure an object with an authorization list
• Describe the search order used by the system to determine whether a
user is allowed to access an object

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 10-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Topic 1: Authorization lists

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-2. Topic 1: Authorization lists

© Copyright IBM Corp. 2001, 2016 10-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

What is an authorization list?

I need to give the same

That's easy! Use an
set of authorities for
authorization list!
multiple objects.

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-3. What is an authorization list?

Purpose of the authorization list is give same set of authorities for multiple objects.

© Copyright IBM Corp. 2001, 2016 10-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Authorization list

Name: AUTL1
Owner: USER3 LIBA LFILEB

User Authority:
*PUBLIC Exclude
USER1 Use
USER2 Change
USER4 All
PROGD
USER5 Change PFILEC

*PUBLIC is on all authorization lists

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-4. Authorization list

On the visual you can see example of the authorization list. Note that each user can have different
rights. *PUBLIC is always in each list.

© Copyright IBM Corp. 2001, 2016 10-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Create an authorization list

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-5. Create an authorization list

You can create authorization list using 5250 by CRTAUTL or you can use IBM Navigator for i with
following steps:
1. On the left pane, expand Security.
2. Click Authorization Lists.
3. On the main pane click Actions and from the pop-up menu select New > Authorization List.

© Copyright IBM Corp. 2001, 2016 10-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Authorization list permissions

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-6. Authorization list permissions

You can change permission to authorization list in 5250 interface using WRKAUTL and use option 2
Change or you can use IBM Navigator for i:
1. On the left pane expand Security.
2. Click Authorization Lists.
3. On the main pane right-click the authorization list name and from pop-up list click Permissions.
4. On the list you can use Add button to add new use or group to the list.

© Copyright IBM Corp. 2001, 2016 10-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Object secured by an authorization list

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-7. Object secured by an authorization list

You can see object secured by the list by clicking the Secured Objects link.

© Copyright IBM Corp. 2001, 2016 10-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Securing an object with an authorization list

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-8. Securing an object with an authorization list

Perform the following to work with object secured by authorization list using IBM Navigator for i:
1. On the left pane expand Integrated File Systems.
2. Expand QSYS.LIB.
3. On the left pane click your library name.
4. On the main pane find the object and right-click the name. From pop-up menu select
Permissions.
5. Then click the Authorization List link to see object secured by the list.

© Copyright IBM Corp. 2001, 2016 10-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Authorization list considerations

• Cannot use to specify authority to a user profile
• Cannot use to specify authority to an authorization list
• An object can be secured by only one authorization list
• Deleting an object does not affect the list that secured it
• User's list authority applies to all objects secured by that list

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-9. Authorization list considerations

© Copyright IBM Corp. 2001, 2016 10-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Authorization list versus group profile

BILL Use
FINDEPT/FILE3
WAYNE All
LIB23
GUNNARUse DSP05
FRANK Change
Objects
Authorization List

BILL Use
GROUP FINDEPT/FILE3
WAYNE All LIB23
Change DSP05
GUNNAR
FRANK Objects

Group Profile

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-10. Authorization list versus group profile

Compare the differences between authorization lists and group profiles.

© Copyright IBM Corp. 2001, 2016 10-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Groups and AUTLs compared

Authorization lists Groups

Can secure multiple objects Can secure multiple objects

A user can be on multiple lists A user can be a member of up to 16

groups as a maximum

Users can have different authority All users in a group have the same
authority

Same authority for different objects Different authority for different

using same list objects

An object can be secured by only one An object can be authorized to many

authorization list groups

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-11. Groups and AUTLs compared

Now you can compare authorization list and group profile attributes.

© Copyright IBM Corp. 2001, 2016 10-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Building authority checking

*ALLOBJ
special authority? Yes
No
User User specific Yes
authorities?
profile No
Authorization list? Yes
See note.
No
*ALLOBJ Yes Allow access to
special authority? object
No
Group Yes
Group specific Yes
profile authority?
Adequate authority?
No Reject access
No to object
Authorization list? Yes
See note.
No
Yes
Note: Is the object secured by an
Public specific
authorities? authorization list and is the user
*PUBLIC *AUTL or group on the list?
Public authority on
authorization list

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-12. Building authority checking

The diagram shows the authority checking process.

© Copyright IBM Corp. 2001, 2016 10-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Exercise: Authorization lists

• At the end of the exercise, you should be able to:
ƒ Secure an object with an authorization list
ƒ Display the list of users on an authorization list

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-13. Exercise: Authorization lists

© Copyright IBM Corp. 2001, 2016 10-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Topic 2: Adopted authority

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-14. Topic 2: Adopted authority

© Copyright IBM Corp. 2001, 2016 10-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Adopted authority (1 of 2)

Everything you have shown me deals with

PERMANENT grants of authority.

I would like to give a user TEMPORARY access to

several objects, without a lot of grants and revokes.

What can I do? You need to use

ADOPTED
AUTHORITY.

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-15. Adopted authority (1 of 2)

Adopting authority is a way to temporary access to the objects.

© Copyright IBM Corp. 2001, 2016 10-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Adopted authority (2 of 2)
• Provides a way to temporarily grant a user authority
• Adopted authority is added to the user's authority
• Both object authorities and special authorities are adopted
• Authority is in effect as long as the program that originally adopts is still
in the stack
• Propagating authority down the call stack is dangerous, especially when
adopting a powerful profile, such as QSECOFR
• Provides the ability to restrict direct object access but allow access
using applications

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-16. Adopted authority (2 of 2)

© Copyright IBM Corp. 2001, 2016 10-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Authority checking
*ALLOBJ
special authority? Yes
No
User User specific Yes
authorities?
profile No
Authorization list? Yes
See note.
No
Allow access to
*ALLOBJ Yes object Yes
special authority?
No
Yes
Group Group specific Yes Adequate No Program
No adopt No Reject access
authority? and adequate
profile No
authority?
authority?
to object

Authorization list? Yes

See note.
No
Yes
Note: Is the object secured by
Public specific
authorities? an authorization list and is the
*PUBLIC *AUTL
user or group on the list?
Public authority
on authorization list

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-17. Authority checking

As you can see in this completed diagram, program adopted authority is the final step in authority
checking.
Adopted authority can allow a user temporary access to objects that otherwise the user is not
authorized to access.
This visual displays the completed diagram for authority checking with IBM i. Follow the logic cycle
through for the class.

© Copyright IBM Corp. 2001, 2016 10-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Exercise: Adopted authority

• At the end of the exercise, you should be able to:
ƒ Change a program to use adopted authority

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-18. Exercise: Adopted authority

© Copyright IBM Corp. 2001, 2016 10-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Review questions
1. The very first thing that a system checks when determining
whether a user is allowed to access an object is:
a. Group authority
b. Authorization list
c. Private authorities
d. All object access

2. The maximum number of authorization lists that a user can be

specified in is:
a. 16
b. 32
c. 64
d. No maximum

3. (Blank) authority is an authority that can be assigned to an object

temporarily.
a. User
b. Object
c. Resource
d. Adopted
Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-19. Review questions

© Copyright IBM Corp. 2001, 2016 10-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Review answers
1. The very first thing that a system checks when determining
whether a user is allowed to access an object is:
a. Group authority
b. Authorization list
c. Private authorities
d. All object access
The answer is All object access.

2. The maximum number of authorization lists that a user can be

specified in is:
a. 16
b. 32
c. 64
d. No maximum
The answer is No maximum.

3. Adopted authority is an authority that can be assigned to an object

temporarily.
a. User
b. Object
c. Resource
d. Adopted
The answer is Adopted.
Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-20. Review answers

© Copyright IBM Corp. 2001, 2016 10-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 10. Authorization lists and adopted authority

Uempty

Unit summary
• Explain the purpose served by an authorization list
• List the steps to secure an object with an authorization list
• Describe the search order used by the system to determine whether a
user is allowed to access an object

Authorization lists and adopted authority © Copyright IBM Corporation 2001, 2016

Figure 10-21. Unit summary

© Copyright IBM Corp. 2001, 2016 10-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Unit 11. Work management: Concepts

and overview
Estimated time
00:15

Overview
Work management is the basis for all work handled in IBM i. To control and tune the performance of
a system, you must understand how jobs are processed. This unit covers the concepts of work
management on IBM i.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 11-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Unit objectives
• List the checklist of things to consider that relate to performance
• List the IBM i functional components
• Discuss the view of an interactive job from the perspective of a user
versus a programmer
• List the IBM i objects that affect performance and job processing
• List the objects needed for processing work on IBM i

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 11-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

IBM i advanced application architecture

User
program
area

IBM i
Mach interface

System Licensed
Internal
Code

POWER Hypervisor
Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-2. IBM i advanced application architecture

There are two components to the operating system software on IBM i. This important distinction is
unique in the industry in its completeness of implementation. The two components are: System
Licensed Internal Code (SLIC) and Operating System (IBM i).
SLIC provides the TIMI, process control, resource management, integrated SQL database, security
enforcement, network communications, file systems, storage management, JVM, and other
primitives. SLIC is a hardened, high-performance layer of software at the lowest level, much like a
Unix kernel, only far more functional.
IBM i provides higher-level functions based on these services to users and to applications. IBM i
also provides a vast range of high-level languages (such as C/C++, COBOL, RPG) runtime
functions.
Object-based system
IBM i keeps all information as objects. There are hundreds of object types. Object-based design
enables a powerful, yet manageable level of system integrity, reliability, and authorization
constraints.

© Copyright IBM Corp. 2001, 2016 11-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty
All programs and operating system information, such as user profiles, database files, programs,
printer queues have their associated object types stored with the information. In the IBM i
architecture, the object type determines how the object's contained information can be used (which
methods).
Single-Level Storage
IBM i applications and the objects with which they interact all reside in a very large virtualized,
single-level storage. That is, the entire system, including the objects most other systems distinguish
as “on disk” or “in memory” are all in the single-level storage. Objects are designated as either
permanent or temporary. Permanent objects exist across system IPLs (reboots). Temporary objects
do not require such persistence. Essentially, the physical RAM on the server is a cache for this very
large, single-level storage space. Storage management, a component of SLIC, ensures that objects
which need to persist when the system is off are maintained in persistent storage. This is either
magnetic hard disk or flash memory as of this writing.
The benefit of providing a single, very large address space, in which all objects on the system
reside, is that applications need not tailor their memory usage to a specific machine configuration.
In fact, IBM i, due to the single-level storage, does not need to tailor such things as the sizes of disk
cache versus paging space. This greatly facilitates the on-demand allocation of memory among
logical partitions.
The operating system and most applications for IBM i are built on a Technology Independent
Machine Interface (TIMI) that isolates programs from differences in processor architectures, and
allows the system to
automatically capitalize on many new Power Architecture features without changes to existing
programs. For example, TIMI allows a program to use decimal floating point (DFP) on POWER5
processors (without special hardware support), and that same program automatically uses
hardware support for DFP on POWER6, POWER7, and POWER8 processors.

© Copyright IBM Corp. 2001, 2016 11-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

IBM i functional components

LIB
Object management
Work management
PGM
Storage management
JOB Database management
System resource management

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-3. IBM i functional components

The IBM i provides few functional components which make system stable and very easy to
manage.

© Copyright IBM Corp. 2001, 2016 11-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Performance checklist: Work management

• Work management
• Creating a work environment
• Special work management functions
• Shipped system objects
• System values
• Job structure
• Storage management
• System tuning

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-4. Performance checklist: Work management

Work management supports the commands and internal functions necessary to control system
operation and the daily workload on the system. In addition, work management contains the
functions that you need to distribute resources for your applications so that your system can handle
your applications.
The purpose of your system is to perform work. Work enters, work is processed, and work leaves
the system. If you think of work management in these three terms, work management will be easier
to understand. Work management describes where work enters the system, where and with what
resources work is processed, and where output from work goes.
Are you new to work management? The topic collection under the subject Introduction to work
management is designed to provide you with several different overall perspectives of work
management. In this way, you should be able to get a solid foundation in the underlying principles
of work management, regardless of your systems background

© Copyright IBM Corp. 2001, 2016 11-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Overview of work management

• Work management is responsible for initiating IBM i jobs:
ƒ Batch
ƒ Interactive
ƒ Communications
ƒ Autostart

• The performance characteristics of jobs are established by work

management when the job is initiated:
ƒ Runtime attributes
ƒ Storage pool assignments

• Job performance is a function of the relationship of runtime parameters

for each of the jobs.

• Altering job initiation from the defaults often results in better overall
system performance.

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-5. Overview of work management

Work management, manages active jobs, server jobs, job queues, subsystems, and memory.

© Copyright IBM Corp. 2001, 2016 11-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Storage management

Whatever a job needs for

processing must be in memory
before the job can use it.

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-6. Storage management

This statement is true for all computers. Because everything a job needs must be in memory in
order for the job to use it, storage management is a critical part of the system.

© Copyright IBM Corp. 2001, 2016 11-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Input, process, and output

Main
storage Output
processor
Input

Work is performed here.

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-7. Input, process, and output

Work is performed by the central processor on data in main storage.

© Copyright IBM Corp. 2001, 2016 11-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

IBM i view: Job initiation

Main storage
7
CLASS PROFILE
Priority Initial program
PROG1

6 Job description

4 QCMD
5 1

SBS
SBSD
3 monitor JOBD
2
Job
Routing description
IBM i
Routing

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-8. IBM i view: Job initiation

This visual shows job initiation steps.

The life of a simple batch job begins when you submit it to the system. The job is then sent to a job
queue where it waits to enter a subsystem where it can run. After the job moves to the subsystem it
is allocated memory in which to run. The printer output file (also called spooled files) is then sent to
the output queue to await further instruction on what to do (for example, printing). While not every
job follows this exact path, you can better understand how other work is completed on the system
by learning more about this typical job lifecycle.

© Copyright IBM Corp. 2001, 2016 11-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Performance tuning (1 of 2)
What everyone would like to have
i performance

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-9. Performance tuning (1 of 2)

In performance work, when you are tuning and optimizing an application for a system you must run
and measure performance levels on that system. Although there are some characteristics that are
shared among systems.
There is not only one parameter which can flow on performance.

© Copyright IBM Corp. 2001, 2016 11-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Performance tuning (2 of 2)
But what we do have

i performance

Subsystem Job descriptions

Activity levels System values
descriptions

Network attributes Pool sizes System

Job queues
displays

Job state
transitions
Fault rates Classes

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-10. Performance tuning (2 of 2)

Many of operating system elements can flow for performance.

© Copyright IBM Corp. 2001, 2016 11-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Work management objects

System Network
IBM i values attributes

Subsystem SBSD

Job Work
thread JOBD
entries

Routing Class
entries

Pools Program

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-11. Work management objects

Whether you are new to work management or have been using work management tools for years,
these work management concepts might be useful for you.
The structure of your system
After receiving your IBM i product, you might want to know what subsystems are included with the
system, whether you need to change any start-up programs, and what kind of user interface you
will work with.
Subsystems
The subsystem is where work is processed on the system. A subsystem is a single, predefined
operating environment through which the system coordinates the work flow and resource use. The
system can contain several subsystems, all operating independently of each other. Subsystems
manage resources.
Memory pools
A memory pool is a logical division of main memory or storage that is reserved for processing a job
or group of jobs. On your system, all main storage can be divided into logical allocations called
memory pools. By default, the system manages the transfer of data and programs into memory
pools.

© Copyright IBM Corp. 2001, 2016 11-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty
Jobs
All work done on a system is performed through jobs. Each job has a unique name within the
system. All jobs, with the exception of system jobs, run within subsystems. A job can enter the
subsystem from any of the work entries, such as a job queue entry, workstation entry,
communications entry, autostart job entry, or prestart job entry.
Job scheduling options
The job schedule function allows for time-dependent scheduling of IBM i batch jobs. You can
schedule jobs to be released from the job queue at a particular time, or you can use a job schedule
entry to submit your job to the job queue automatically at the time you specify. Job scheduling
allows you to control the date and time a batch job is submitted to or becomes eligible to start from
a job queue. This flexibility can help you as you balance the work load on your system.
Job queues
A job queue contains an ordered list of jobs waiting to be processed by a subsystem. The job queue
is the first place that a submitted batch job goes before becoming active in a subsystem. The job is
held here until a number of factors are met.
Output queues
Output queues are areas where printer output files (also called spooled files) wait to be processed
and sent to the printer. Printer output is created either by the system or by the user using a print file.
Job logs
A job log contains information related to requests entered for a job. A job log has two forms, a
pending form and a spooled form.
Job accounting
The job accounting function gathers data so that you can determine who is using your system and
what system resources they are using. It also assists you in evaluating the overall use of your
system. Job accounting is optional. You must take specific steps to set up job accounting. You can
request the system to gather job resource accounting data, printer file accounting data, or both. You
can also assign accounting codes to user profiles or specific jobs.

© Copyright IBM Corp. 2001, 2016 11-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Review questions
1. True or False: Work management supports the commands
and internal functions necessary to control system operation
and the daily workload.

2. True or False: Work management is not one of the functional

components of IBM i.

3. True or False: There is one system value used to adjust and

tune the system.

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-12. Review questions

© Copyright IBM Corp. 2001, 2016 11-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Review answers
1. True or False: Work management supports the commands
and internal functions necessary to control system operation
and the daily workload.
The answer is true.

2. True or False: Work management is not one of the functional

components of IBM i.
The answer is false.

3. True or False: There is one system value used to adjust and

tune the system.
The answer is false.

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-13. Review answers

© Copyright IBM Corp. 2001, 2016 11-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 11. Work management: Concepts and overview

Uempty

Unit summary
• List the checklist of things to consider that relate to performance
• List the IBM i functional components
• Discuss the view of an interactive job from the perspective of a user
versus a programmer
• List the IBM i objects that affect performance and job processing
• List the objects needed for processing work on IBM i

Work management: Concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 11-14. Unit summary

© Copyright IBM Corp. 2001, 2016 11-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Unit 12. Work management: Subsystem

concepts and overview
Estimated time
00:35

Overview
Work management is the basis for all work that is handled in the IBM i system. To control and tune
the performance of a system, you must understand how jobs are processed. This unit covers
interactive job processing and the relationships among the work management objects. We will also
discuss how to track jobs through the system and what the controls are for limiting the number of
jobs executing concurrently.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 12-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Unit objectives
• Describe what a subsystem is
• Describe what memory pools are
• List and describe the type of memory pools on the system
• Describe the types of work that can be run in the different memory
pools
• Explain why different types of memory pools exist
• List the commands used to display memory pool information
• Explain the information displayed on the work with system status
command display

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 12-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Topic 1: Subsystem concepts

and overview

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-2. Topic 1: Subsystem concepts and overview

© Copyright IBM Corp. 2001, 2016 12-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Subsystems (1 of 2)

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-3. Subsystems (1 of 2)

The subsystem is where work is processed on the system. A subsystem is a single, predefined
operating environment through which the system coordinates the work flow and resource use. The
system can contain several subsystems, all operating independently of each other. Subsystems
manage resources.
All jobs, with the exception of system jobs, run within subsystems. Each subsystem can run unique
operations. For instance, one subsystem can be set up to handle only interactive jobs, while
another subsystem handles only batch jobs. Subsystems can also be designed to handle many
types of work. The system allows you to decide the number of subsystems and what types of work
each subsystem handles.
The subsystem is where work is processed on the system. A subsystem is a single, predefined
operating environment through which the system coordinates the work flow and resource use. The
system can contain several subsystems, all operating independently of each other. Subsystems
manage resources.

© Copyright IBM Corp. 2001, 2016 12-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Subsystems (2 of 2)

A specialized environment for handling a certain

type of work or function, such as:

Interactive

Batch Spooling

Communications

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-4. Subsystems (2 of 2)

All jobs, with the exception of system jobs, run within subsystems. Each subsystem can run unique
operations. For instance, one subsystem can be set up to handle only interactive jobs, while
another subsystem handles only batch jobs. Subsystems can also be designed to handle many
types of work. The system allows you to decide the number of subsystems and what types of work
each subsystem handles.
The run-time characteristics of a subsystem are defined in an object called a subsystem
description. For example, if you want to permanently change the amount of work (number of jobs)
coming from a job queue into a subsystem you only need to change the job queue entry in the
subsystem description.
On the visual you can see some subsystems example like:
• Batch
• Interactive
• Spooling
• Communications
In the system there are many more.

© Copyright IBM Corp. 2001, 2016 12-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
As the number of users on the system increases, a single subsystem for a set of work is often
insufficient. By dividing your users into multiple subsystems, you gain several advantages.
Improved manageability of work You get better control over what work is running in each
subsystem. For example, for server jobs, you might want to isolate all of the database server jobs to
one subsystem, the remote command server jobs to a different subsystem, the DDM server jobs to
yet a different subsystem. Additionally, by using multiple subsystems you can isolate groups of jobs
with their own memory pools. In this way, one group does not adversely impact other jobs.
Reduced downtime impact for users For example, if every Friday afternoon you must bring the
system to the restricted state for backup purposes, you can gradually take users offline by ending
one subsystem at a time.
Improved scalability and availability By having a single subsystem do work for fewer users. The
subsystem is less busy and can be more responsive to the work requests it handles.
Improved error tolerance in interactive subsystems by spreading the work across multiple
subsystems, should a network failure occur, multiple subsystems can manage the device recovery
processing.
Improved interactive subsystem startup time You can keep the subsystem startup times shorter by
subdividing the work across multiple subsystems.
Additional options for performance tuning By using multiple subsystems you can set up the
subsystems with a small number of routing entries.

© Copyright IBM Corp. 2001, 2016 12-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Subsystem description (1 of 2)
• A subsystem description determines:
• How much work can be initiated, including the number of storage jobs
• Where that work will be performed, including main storage pools
• The sources of work for a subsystem:
ƒ Autostart jobs
ƒ Workstations
ƒ Job queues
ƒ Communication jobs

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-5. Subsystem description (1 of 2)

A subsystem description is an object that defines the environment for the jobs that run in the
subsystem. The purpose is to have the jobs run most efficiently. The subsystem description
identifier is *SBSD.
All work within a subsystem is controlled by an i program known as a subsystem monitor. All
subsystem monitors are identical, regardless of the subsystem they control or the type of jobs that
run in it.
Each subsystem monitor uses a different subsystem description in performing its control functions.
A subsystem description is an object that contains information defining the characteristics of an
operating environment which can handle a specific type of processing, such as interactive, batch,
spooling, or communication. It defines:
• How many jobs the subsystem runs in parallel
• Where and how those jobs are run
• Where the subsystem looks for jobs to run
• Which resources the subsystem uses to perform the work

© Copyright IBM Corp. 2001, 2016 12-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
A subsystem description can contain work entries (sources of work) for one or more of the
following:
• Autostart jobs
• Workstations (individual or by type)
• Job queues
• Communication jobs
A subsystem description also defines the amount of main storage that is available for jobs that are
run in the subsystem. The subsystem description is used by the subsystem monitor to establish the
environment for its jobs.
When a subsystem is started, it takes the name of the subsystem description it uses.

© Copyright IBM Corp. 2001, 2016 12-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Subsystem description (2 of 2)

Subsystem
description

POOLS( ) MAXJOBS ( ) CRTSBSD

Job queue entries ADDJOBQE

Workstation entries ADDWSE

Work
entries AUTOSTART entries ADDAJE

Communication entries ADDCMNE

PRESTART entries
ADDPJE
Routing entries
ADDRTGE
Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-6. Subsystem description (2 of 2)

Work entries identify the sources where jobs can enter a subsystem. Specific types of work entries
are used for different types of jobs. Work entries are part of the subsystem description.
The following information describes the different types of work entries and how to manage them.
There are five types of work entries; autostart job entries, communication entries, job queue entries,
prestart job entries, and workstation entries.
Autostart job entries
Autostart job entries identify the autostart jobs to start as soon as the subsystem starts. When a
subsystem starts, the system allocates several items and starts autostart and prestart jobs before it
is ready for work.
Communications entries
The communications work entry identifies to the subsystem the sources for the communications job
it processes. The job processing begins when the subsystem receives a communications program
start request from a remote system and an appropriate routing entry is found for the request.

© Copyright IBM Corp. 2001, 2016 12-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
Job queue entries
Job queue entries in a subsystem description specify from which job queues a subsystem is to
receive jobs. When the subsystem is started, the subsystem tries to allocate each job queue
defined in the subsystem job queue entries.
Prestart job entries
You define the prestart job by using a prestart job entry. A prestart job entry does not affect the
device allocation or program start request assignment.
Prestart jobs for servers
In the prestart job model there is one primary listening job, generally called the daemon job or
listener job, and multiple server jobs that process the client requests. The daemon job listens on the
port for connection requests. When a new connection is received, the daemon does some general
work, then gives the socket descriptor to a waiting prestart server job.
Workstation entries
An interactive job is a job that starts when a user signs on to a display station and ends when the
user signs off. For the job to run, the subsystem searches for the job description, which can be
specified in the workstation entry or the user profile.

© Copyright IBM Corp. 2001, 2016 12-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Work entries
Workstation entries

Type Jobd Name Jobd

*ALL *USRPRF DSP03 *USRPRF

Job queue entries PRESTART job entries

Jobq Prog Jobd

QBATCH PROG01 JOBDAPPC

AUTOSTART job entries Communication entries

Job Jobd Dev Jobd

START STARTJD *ALL *USRPRF

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-7. Work entries

An interactive job is a job that starts when a user signs on to a display station and ends when the
user signs off. For the job to run, the subsystem searches for the job description, which might be
specified in the workstation entry or the user profile.
The workstation entry guides the subsystem to prospective workstations. If a workstation is
available, the subsystem sends a sign-on screen to the display. Note: The subsystem description
for the controlling subsystem must contain a workstation entry for the console, and that entry must
be of type *SIGNON. (*SIGNON is a value for the AT parameter, specified on the Add Work Station
Entry (ADDWSE) command.) The *SIGNON value indicates that the sign-on display is shown at the
workstation when the subsystem is started. This requirement ensures that the subsystem has an
interactive device for the entry of the system and subsystem level commands. The End System
(ENDSYS) command ends the IBM i licensed program to a single session (or sign-on display) at the
console in the controlling subsystem. A subsystem description that does not contain a workstation
entry for the console cannot be started as a controlling subsystem.

© Copyright IBM Corp. 2001, 2016 12-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Routing entries

SEQNBR CMPVAL CLASS PGM POOL ID

10 QCMDB QBATCH QCMD 1

50 QCMDI QINTER QCMD 2

9999 *ANY QBATCH QCMD 1

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-8. Routing entries

The routing entry identifies the main storage subsystem pool to use, the controlling program to run
(typically the system-supplied program QCMD), and additional run-time information (stored in the
class object). Routing entries are stored in the subsystem description.
A routing entry can be likened to a single entry in a shopping mall directory. Customers that cannot
find the store they need can use a directory to help send them in the right direction. The same is
true on your system. Routing entries guide the job to the correct place. Routing entries in a
subsystem description specify the program to be called to control a routing step for a job running in
the subsystem, which memory pool the job uses, and from which class to get the run-time
attributes. Routing data identifies a routing entry for the job to use. Together, routing entries and
routing data provide information about starting a job in a subsystem.
Routing entries consist of these parts; the subsystem description, class, comparison data,
maximum active routing steps, memory pool ID, program to call, thread resources affinity,
resources affinity group, and the sequence number.

© Copyright IBM Corp. 2001, 2016 12-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
Class
Job run-time attributes are contained in the class object that is specified in the (CLS) parameter in
the routing entry. If a job consists of multiple routing steps, the class used by each subsequent
routing step is specified in the routing entry used to start the routing step. If the class does not exist
when the routing entry is added, a library qualifier must be specified because the qualified class
name is kept in the subsystem description.
Comparison data
The comparison value (CMPVAL) parameter of the routing entry specifies data that is compared with
routing data to determine which routing entry to use. (The routing entry also specifies the starting
position for the comparison.) The routing data is compared with the comparison value of each
routing entry in sequence number order until a match is found. The sequence number contained in
a routing entry defines the order in which the routing entries are scanned and can be used as the
identifier of the routing entry.
Maximum active routing steps
The maximum active routing steps (MAXACT) parameter of the routing entry specifies the maximum
number of routing steps (jobs) that can be active at the same time through this routing entry.
Memory pool ID
The memory pool ID (POOLID) parameter of the routing entry specifies the pool identifier of the
storage pool in which the program runs. The pool identifier specified here relates to the storage
pools in the subsystem description.

© Copyright IBM Corp. 2001, 2016 12-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Class information

QBATCH QINTER

Run priority 50 20

Time slice 5000 ms 2000 ms

Purge *NO *YES

Wait time 120 sec 30 sec

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-9. Class information

Job run-time attributes are contained in the class object that is specified in the (CLS) parameter in
the routing entry. If a job consists of multiple routing steps, the class used by each subsequent
routing step is specified in the routing entry used to start the routing step. If the class does not exist
when the routing entry is added, a library qualifier must be specified because the qualified class
name is kept in the subsystem description.
Run-time attributes that are included in a routing entry class are:
• Run priority (RUNPTY) The run priority is a value ranging from 1 (highest priority) through 99
(lowest priority) that represents the priority at which the job competes for the processing unit
relative to other jobs that are active at the same time. For multi-threaded jobs, the run priority is
also the highest run priority allowed for any thread within the job. Individual threads within the
job might have a lower priority.
• Time slice (TIMESLICE) This is the time slice establishes the amount of time needed by a
thread in a job to accomplish a meaningful amount of processing. At the end of the time slice,
the thread might be put in an inactive state so that other threads can become active in the
storage pool.

© Copyright IBM Corp. 2001, 2016 12-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
• Default wait time (DFTWAIT) This specifies the default maximum time (in seconds) that a
thread in the job waits for a system instruction, such as the LOCK machine interface (MI)
instruction to acquire a resource. This default wait time is used when a wait time is not
otherwise specified for a given situation. Normally, this is the amount of time the system user
might be willing to wait for the system before the request is ended. If the wait time for any one
instruction is exceeded, an error message can be displayed or it can be automatically handled
by a Monitor Message (MONMSG) command.
• Maximum CPU time (CPUTIME) This specifies the maximum processing unit time (in
milliseconds) that the job can use. If the job consists of multiple routing steps, each routing step
is allowed to use this amount of processing unit time. If the maximum time is exceeded, the job
is held.
• Maximum temporary storage (MAXTMPSTG) This specifies the maximum amount of temporary
(auxiliary) storage that the job can use. If the job consists of multiple routing steps, this is the
maximum temporary storage that the routing step can use. This temporary storage is used for
storage required by the program itself and by implicitly created internal system objects used to
support the job. It does not include storage in the QTEMP library. If the maximum temporary
storage is exceeded, the job is held. This parameter does not apply to the use of permanent
storage, which is controlled through the user profile.
• Maximum threads (MAXTHD) This specifies the maximum number of threads that a job using
this class can run with at any time. If multiple threads are initiated simultaneously, this value can
be exceeded. If this maximum value is exceeded, the excess threads will be allowed to run to
their normal completion. Initiation of additional threads will be inhibited until the maximum
number of threads in the job drops below this maximum value.
• Text description (TEXT) This specifies the text that briefly describes the object. This is an
attribute of the class object when it is created, but it is not a run-time attribute for a job.
• Authority (AUT) This specifies the authority you are giving to users who do not have specific
authority for the object, who is not on an authorization list, and whose group profile or
supplemental group profiles do not have specific authority for the object. This is an attribute of
the class object when it is created, but it is not a run-time attribute for a job.

© Copyright IBM Corp. 2001, 2016 12-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Start subsystem (STRSBS QINTER)

Subsystem QSYS/QINTER
monitor subsystem description Main storage
program
Attributes
Sign-On Display File *INTERACT
(QSYS/QDISGNON)
MAXJOBS(*NOMAX)
Storage Pools
ID Storage
1 *BASE *BASE
2 *INTERACT
LWS1
User
Password
*MACHINE
3180 Work Station Entry
User Work Station Names
Password LWS1

3197 Work Station Types

User *ALL
Password
Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-10. Start subsystem (STRSBS QINTER)

When a subsystem starts, the system allocates several items and starts autostart and prestart jobs
before the subsystem is ready for work.
The subsystem description is used to determine how items are allocated. The following list
represents the sequence of events that occur when the subsystem starts:
• Request to start subsystem is issued. The Start Subsystem (STRSBS) command is issued.
Key startup information is located in the subsystem description.
• Memory pools are allocated. Memory is allocated to the pools defined in the subsystem
description. The memory that is allocated to each defined pool is taken from the Base memory
pool. The system does not allocate memory to a pool if the amount of memory available to the
Base storage pool is less than the minimum size specified by the Base memory pool minimum
size system value QBASPOOL. If the system cannot allocate all of the requested memory, it
allocates as much memory as is available and allocates all the other as memory becomes
available.
• Prestart jobs are started. This information comes from the prestart job entries.
• Autostart jobs are started. This information comes from the autostart jobs entries.

© Copyright IBM Corp. 2001, 2016 12-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
• Display stations are allocated (sign-on displays are up). If there are workstation entries and
the device is varied on and has not been allocated by any other subsystem, the subsystem can
allocate it and display the sign-on display. If the device is varied on and has been allocated by
another subsystem and is at the sign-on display (the sign-on display was displayed before the
second subsystem was started), a second subsystem can allocate the device from the first
subsystem and display the sign-on display. If the device is not varied on, the subsystem cannot
allocate it. The system arbiter (QSYSARB) and the QCMNARB jobs hold locks on all varied-off
devices. Workstation entries provide the information about what devices to check for allocation.
Note: For virtual display devices, the sign-on display is shown when the device becomes fully
varied on. This happens when a user connects to the IBM i using that device description
(assuming the connection request does not carry the data that is used to bypass the sign-on
display processing). A device can be taken from a pool of previously created device
descriptions and varied on as part of that connection processing, or a device can be created
and varied on. At a subsystem start, the subsystem pends a lock for any of the previously
created device descriptions that the subsystem wants.
• Job queues are allocated. The subsystem will not be able to allocate a job queue if it is
already allocated to another active subsystem. This information comes from the job queue
entries.
• Communications devices are allocated. Requests are sent to the QLUS (LU services)
system job, which handles device allocation for all communications devices. This information
comes from the communication entries.
The environment is ready for work.

© Copyright IBM Corp. 2001, 2016 12-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Default subsystem configurations

• IPL starts only the subsystem named in QCTLSBSD system value.
• Environment as shipped (Default) - QCTLSBSD = QBASE
Autostart job
QBASE QSPL Spooling
Console, Interactive, Batch, Communications
QSYSWRK System initiated functions
QSERVER File server
QUSRWRK User initiated functions
• Complex environment - QCTLSBSD = QCTL
Autostart job
QCTL QINTER Interactive
Console
QBATCH Batch
QSYSWRK
QSPL Spooling
System functions
QUSRWRK QCMN Communication

System functions QSERVER File server

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-11. Default subsystem configurations

IBM ships predefined subsystem descriptions that can be used to provide the environments needed
on most systems.
The default subsystem configuration consists of a controlling subsystem called QBASE, a system
function subsystem called QSYSWRK, and a spooling subsystem called QSPL. In this
environment, all jobs on the system except for some system jobs and spooling jobs that are run
under the control of the QBASE subsystem. Certain system jobs run under the control of
QSYSWRK. Spooling jobs run under the control of the QSPL subsystem.
A more complex subsystem configuration is also provided and can be used instead of the default
QBASE/QSPL configuration. It consists of:
• QCTL The controlling subsystem
• QSYSWRK Which runs certain System jobs initiated by the OS
• QUSRWRK Was instituted in V5.1 and it is used by the system for system jobs
that are user-oriented
• QINTER The subsystem for interactive jobs
• QBATCH The subsystem for batch jobs
• QSPL The subsystem for spooling

© Copyright IBM Corp. 2001, 2016 12-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
• CMN The subsystem used for communicating jobs
• QSERVER The subsystem used for file serving jobs
• QHTTPSVR The subsystem used for Web server jobs and programs
IBM ships several predefined subsystem descriptions. A system can be implemented through the
use of these shipped subsystems. It is also possible for a system implementer to implement a
system by creating brand new subsystem descriptions.
When it is shipped, every system has QBASE as its controlling subsystem; the controlling
subsystem is the only one started by i during IPL. QBASE is set up to handle all types of work on
the system (which includes the console, interactive jobs, batch jobs, and communication jobs),
except some system functions and spooling. In this environment, the QSYSWRK subsystem is
responsible for some system functions and the QSPL subsystem is responsible for all spooling jobs
(output to printers).
A more complex environment is also shipped and can be used instead of the default QBASE/QSPL
environment described above. This environment is used if there are a lot of different types of jobs
running on a System i.
The system value, QCTLSBSD (controlling subsystem) controls which subsystem configuration is
used.
IBM provides other subsystems, such as QSNADS, which supports jobs controlling the functions of
the SNADS network and IBM-supplied transaction programs, such as document interchange and
object distribution.
These subsystems are started and ended when the functions they support are started and ended.

© Copyright IBM Corp. 2001, 2016 12-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Topic 2: Memory pool

concepts and overview

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-12. Topic 2: Memory pool concepts and overview

© Copyright IBM Corp. 2001, 2016 12-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

An overview of memory pools

• Main storage is divided into memory pools:

• Shared pool:
ƒ A pool in which multiple subsystems can run jobs
ƒ Maximum of 64 shared pools on the system
• Private pool:
ƒ A pool in which a single subsystem can run jobs
ƒ Is assigned a size and activity level when the subsystem is created

• The activity level of a pool is the number of jobs that can have main
storage at the same time.

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-13. An overview of memory pools

A memory pool is a logical division of main memory or storage that is reserved for processing a job
or group of jobs. On your system, all main storage can be divided into logical allocations called
memory pools. By default, the system manages the transfer of data and programs into memory
pools.
The memory pool from which user jobs get their memory is always the same pool that limits their
activity level. (The activity level of a memory pool is the number of threads that can be active at
same time in a memory pool.) Exceptions to this are system jobs (such as Scpf, Qsysarb, and Qlus)
that get their memory from the Base pool but use the machine pool activity level. Additionally,
subsystem monitors get their memory from the first subsystem description pool, but it uses the
machine pool activity level. This allows a subsystem monitor to always be able to run regardless of
the activity level setting.

© Copyright IBM Corp. 2001, 2016 12-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

The shared pool subtypes

• Main storage is divided into memory pools:
• Specialized shared pools:
ƒ *MACHINE (machine pool)
ƒ *BASE (base pool)
• General shared pools:
ƒ *INTERACT
ƒ *SPOOL
ƒ *SHRPOOL1 - *SHRPOOL60

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-14. The shared pool subtypes

© Copyright IBM Corp. 2001, 2016 12-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Why pools?

Main storage (memory)

Only Interactive Interactive Interactive
interactive program program program
jobs
Pool

Interactive Interactive
program program
Share

Pool Batch program

Only
batch
jobs Batch program
Pool

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-15. Why pools?

You can control how much work can be done in a subsystem by controlling the number and size of
the pools. The greater the size of the pools in a subsystem, the more work can be done in that
subsystem.
Using shared memory pools allows the system to distribute jobs for interactive users across
multiple subsystems while still allowing their jobs to run in the same memory pool.
Multiple pools in a subsystem help you to control the jobs' competition for system resources. The
advantages of having multiple pools in a subsystem are that you can separate the amount of work
done and the response time for these jobs. For example, during the day you might want interactive
jobs to run with good response time. For better efficiency, you can make the interactive pool larger.
At night, you might be running many batch jobs, so you make the batch pool larger.
Note: Although tuning and managing your system can help the efficiency of the flow of work through
your system, it cannot account for inadequate hardware resources. Consider a hardware upgrade if
the demands of your workload are significant.

© Copyright IBM Corp. 2001, 2016 12-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Main storage pools

*SPOOL POOL (4)

*INTERACT POOL (3)

*BASE POOL (2)

*MACHINE POOL (1)

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-16. Main storage pools

On the system, all main storage can be divided into logical allocations called memory pools. All
memory pools in a system are either private or shared. There are private memory pools, shared
memory pools, and special shared memory pools. As many as 64 memory pools, in any
combination of private and shared pools, can be active at the same time.
Private memory pools
Private memory pools (also known as user-defined memory pools) contain a specific amount of
main storage that can be used by a single subsystem to run jobs. These pools cannot be shared by
multiple subsystems. They are identified in IBM® Navigator for i by the subsystem name. You can
have as many as 62 private memory pools allocated for use in active subsystems.
Shared memory pools
Shared pools are either special or general; the Machine pool and Base pool are considered special
shared pools, and all other shared pools are considered general shared pools. You can specify 63
of the 64 shared memory pools that are defined on the system for use when creating subsystem
descriptions (the machine pool is reserved for system use).

© Copyright IBM Corp. 2001, 2016 12-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
Special shared pools (*MACHINE and *BASE)
*MACHINE The Machine memory pool is used for highly shared Machine and operating system
programs. It is identified as Machine in IBM Navigator for i. The Machine memory pool provides
storage for tasks the system must run that do not require your attention. The size for this memory
pool is specified in the Machine memory pool size system value (QMCHPOOL). No user jobs run in
this memory pool. (On the Work with System Status display (WRKSYSSTS), the Machine memory
pool appears as system pool identifier 1.)
*BASE The Base memory pool, identified as Base in IBM Navigator for i, contains all unassigned
main storage on the system, (all main storage that is not required by another memory pool). The
Base pool contains storage that can be shared by many subsystems. The Base memory pool is
used for batch work and miscellaneous system functions. The Base memory pool minimum size
(QBASPOOL) system value specifies the minimum size of the Base memory pool. The activity level
for this memory pool is specified in the Base memory pool maximum eligible threads
(QBASACTLVL) system value. (On the Work with System Status display (WRKSYSSTS), the Base
memory pool appears as system pool identifier 2.)
General shared pools
General shared pools are pools of main storage that multiple subsystems can use at the same
time. On the character-based interface, they are identified as follows:
• *INTERACT is the interactive storage pool used for interactive jobs.
• *SPOOL is the storage pool used for spool writers.
• *SHRPOOL1 through *SHRPOOL60 are storage pools that you can use for your own use.
In IBM Navigator for i, the general shared pools are identified as Interactive, Spool, and Shared 1 -
Shared 60.

© Copyright IBM Corp. 2001, 2016 12-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Storage pool characteristics

• Logical areas of main storage for jobs:
• There are two types of pools: private and shared.
• The system can have up to 64 active storage pools.
• A subsystem can have up to 10 defined storage pools.
• Pool size determines the amount of storage.
• Memory is allocated in noncontiguous pages.
• Memory is reallocated when the *NOSTG parameter is used.
• Paging is restricted to each pool.
• Activity levels determine the number of job threads in a memory pool.

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-17. Storage pool characteristics

© Copyright IBM Corp. 2001, 2016 12-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Specifying which pools are assigned

• Private
CRTSBSD ABC POOLS((1 1600 3) (2 2000 5))

• Shared
Specialized: *MACHINE *BASE
General: *INTERACT *SPOOL *SHRPOOL1...*SHRPOOL60

CRTSBSD DEF POOLS((1 *BASE) (2 *INTERACT) (*SHRPOOL1))

CRTSBSD GHI POOLS((1 *BASE) (2 *INTERACT)

(3 *SHRPOOL1) (4 2000 5))

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-18. Specifying which pools are assigned

You can assign pools when you are creating or changing subsystems description.

© Copyright IBM Corp. 2001, 2016 12-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Storage pool allocation

When creating a subsystem, storage pools must be specified:
CRTSBSD QINTER POOLS((1 *BASE) (2 *INTERACT))
MAXJOBS(*NOMAX)
Pool sizes can be changed while the subsystem is active:
CHGSHRPOOL POOL(*INTERACT) SIZE(2100) ACTLVL(6)
Before After

*SPOOL *SPOOL

QINTER
*INTERACT (1800) *INTERACT (2100)
POOL 2

QINTER
*BASE *BASE
POOL 1

*MACHINE POOL *MACHINE POOL

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-19. Storage pool allocation

When creating a subsystem, storage pools must be specified:

CRTSBSD QINTER POOLS((1 *BASE) (2 *INTERACT)) MAXJOBS(*NOMAX)
Pool sizes can be changed while the subsystem is active:
CHGSHRPOOL POOL(*INTERACT) SIZE(2100) ACTLVL(6)

© Copyright IBM Corp. 2001, 2016 12-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Topic 3: Working with

subsystems and memory
pools

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-20. Topic 3: Working with subsystems and memory pools

© Copyright IBM Corp. 2001, 2016 12-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Display Subsystem Description

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-21. Display Subsystem Description

To display subsystem description you can use the DSPSBSD command. Look at the option 1
Operational attributes.

© Copyright IBM Corp. 2001, 2016 12-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

QINTER subsystem
Operational attributes

Maximum jobs in subsystem *NOMAX

Sign-on display file QSYS/QDSIGNON

Pool definitions

Pool Storage
ID size (KB)

1 *BASE

2 *INTERACT

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-22. QINTER subsystem

Subsystem description attributes are common overall system attributes. When you create a
subsystem, the first step is to define the subsystem attributes.
Subsystem attributes include:
• The name of the subsystem description and the library where it is stored.
• All of the memory pool definitions that this subsystem uses A subsystem definition can have a
maximum of 10 memory pool definitions specified. Included in the subsystem definition are:
▪ Pool definition identifier: This is the identifier inside the subsystem description, of the
storage pool definition.
▪ Size: This is the size of the storage pool expressed in KB (1K=1024 bytes) multiples and is
the amount of main storage that the pool can use.
▪ Activity level: This is the maximum number of threads that can run at the same time in the
pool.
The maximum number of jobs that can be active in the subsystem at the same time.
A text description of the subsystem description.
The name and library of the sign-on display file that is used to show sign-on displays at work
stations that are allocated to the subsystem.

© Copyright IBM Corp. 2001, 2016 12-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
A subsystem library name that you can use if you want to specify a library that should be entered
ahead of other libraries in the system portion of the library list. (This parameter allows you to use a
secondary language library.)
Also included in the subsystem description is information about authority levels to the subsystem.
This information is kept by Security and is not stored with the other attributes of the subsystem
description. You can view the subsystem description authority by using the Display Object Authority
(DSPOBJAUT) command.

© Copyright IBM Corp. 2001, 2016 12-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Work with System Status

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-23. Work with System Status

The pool sizes and usage you can see using WRKSYSSTS command.

© Copyright IBM Corp. 2001, 2016 12-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

WRKSYSSTS: Pool data

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-24. WRKSYSSTS: Pool data

By pressing F11 function key you can change the view and see memory pool names.
Pagination option
The paging option associated with the pool. The paging option determines whether the system
should dynamically adjust the paging characteristics of the storage pool for optimum performance.
The following are the possible paging option values:
*FIXED
The system does not dynamically adjust the paging characteristics of the storage pool; it uses
system-default values.
*CALC
The system dynamically adjusts the paging characteristics of the storage pool for optimum
performance.
USRDFN
The system does not dynamically adjust the paging characteristics of the storage pool. It uses
values that have been defined through an application programming interface (API).

© Copyright IBM Corp. 2001, 2016 12-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

WRKSHRPOOL

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-25. WRKSHRPOOL

To work with all memory pool you can use command WRKSHRPOOL.

© Copyright IBM Corp. 2001, 2016 12-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

IBM Navigator for i: Active Pools

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-26. IBM Navigator for i: Active Pools

To work with Active Pools using IBM Navigator for i you have to:
1. Open web browser http://<system name or IP address>:2001.
2. Log on to the IBM Navigator for i.
3. On the left pane, expand Work Management.
4. Click Active Memory Pools link.
As you see that the shows information is similar like when you use WRKSYSSTS command. IBM
Navigator for i offering system status details you will see later on this unit.

© Copyright IBM Corp. 2001, 2016 12-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

IBM Navigator for i: Shared Pools

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-27. IBM Navigator for i: Shared Pools

To work with Shared Memory Pools using IBM Navigator for i you have to:
1. Open web browser http://<system name or IP address>:2001.
2. Log on to the IBM Navigator for i.
3. On the left pane, expand Work Management.
4. Under Active Memory Pools link expand All Tasks.
5. Expand Memory Pools.
6. Click Shared Memory Pools.
On the screen, you will be see all shared pools active and inactive it is similar to WRKSHRPOOL
command.

© Copyright IBM Corp. 2001, 2016 12-37

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Shared Pools: Properties

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-28. Shared Pools: Properties

To see shared memory pool properties select pool name and right-click on. From the pop-up menu,
select Properties.

© Copyright IBM Corp. 2001, 2016 12-38

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

General and Configuration tab

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-29. General and Configuration tab

Use the General tab to view and change attributes of a memory pool.
Use the Configuration tab to view and change configuration values for a memory pool.
You can find information about:
• Size
• Activity level
• Paging option

© Copyright IBM Corp. 2001, 2016 12-39

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Performance and Tuning tab

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-30. Performance and Tuning tab

Use the Performance tab to view performance statistics for an active memory pool.
You can see information about following parameters:
• State transitions per minute
• Database faults per second
• Database pages per second
• Non-database faults per second
• Non-database pages per second
Performance tuning is a way to adjust the performance of the system. There are many options for
tuning your system.
Each system environment is unique, requiring you to observe performance and make adjustments
that are best for your environment.
You can make performance adjustments to your system in the following ways:
• Automatic performance adjustments: You can choose to set up the system to make
performance adjustment automatically. When new systems are shipped, they are configured to
adjust automatically.

© Copyright IBM Corp. 2001, 2016 12-40

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
• Manual performance adjustments: Some users have much more experience and knowledge
about IBM i work management functions and applications. You might want to perform additional
tuning by manually setting specific values such as pool size, and activity level.
• Customized performance adjustments: You can set values that control how the performance
tuner operates and then let the system make the performance adjustments automatically.

© Copyright IBM Corp. 2001, 2016 12-41

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

IBM Navigator for i: WRKSYSSTS

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-31. IBM Navigator for i: WRKSYSSTS

To work with System status using IBM Navigator for i you have to:
1. Open web browser http://<system name or IP address>:2001.
2. Log on to the IBM Navigator for i.
3. On the left pane, expand System.
4. Click System Status link.
When the System Status dialog opens, it displays statistical information about your system for that
instant in time. The exception is the CPU usage field, which displays a cumulative average during
the time displayed in the Elapsed time field.

© Copyright IBM Corp. 2001, 2016 12-42

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

General and Jobs tab

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-32. General and Jobs tab

Use the General tab to view high level system status values that show the current status of the
system, such as elapsed CPU usage, total and active jobs in the system, permanent and temporary
addresses used, total disk space, and system disk pool capacity and usage.
You can find information about the following elements on this window:
• CPU usage (elapsed)
• Jobs
• Addresses used
• Total disk space
• System disk pool
• System Resources Health Indicators
Use the Jobs tab to view the number of total, maximum, and active jobs and threads running on the
system.
You can find information about the following elements on this window:
• Jobs
• Threads
• Active Jobs
• Jobs System Values

© Copyright IBM Corp. 2001, 2016 12-43

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Processors and Memory tab

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-33. Processors and Memory tab

Use the Processors tab to view the elapsed CPU usage and the number of processors in the
system.
You can find information about:
• CPU usage (elapsed)
• Type of processors
• Processing power
• Virtual processors
• Interactive performance
• Shared processor pool usage (elapsed)
• Uncapped CPU capacity pool usage (elapsed)
• CPU Health Indicators

© Copyright IBM Corp. 2001, 2016 12-44

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Note

Fields that do not apply to your system are not shown.

Use the Memory tab to view the amount of memory on the system. You can also access the Active
Memory Pools window.
You can find information about:
• Total memory
• Active Memory Pools
• Active Memory Pools

© Copyright IBM Corp. 2001, 2016 12-45

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Disk Space and Addresses tab

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-34. Disk Space and Addresses tab

Use the Disk Space tab to view the amount of disk space on the system. You can also access the
Temporary Storage Details window, the Disk Pools window and the Storage System Values
window from this tab.
You can find information about:
• Total disk space
• System disk pool
• Temporary storage used
• Temporary Storage Details
• Disk Status
• Disk Pools
• Storage System Values
• Disk Health Indicators
Use the Addresses tab to view information about address use on the system. When a permanent
or temporary address is created on the system, it is assigned an address by disk storage
management. The system uses this address to correlate references to the object with disk storage.

© Copyright IBM Corp. 2001, 2016 12-46

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty
It is important to regularly monitor the percentage of addresses used on your system. If the rate at
which addresses are being used will cause you to reach 100% during the planned lifetime of the
system or if address usage reaches 90% (critical limit), you should call your IBM software service
representative.
You can find information about:
• Addresses used
• Large addresses used (256 MB)
• Very large addresses used (4 GB)

© Copyright IBM Corp. 2001, 2016 12-47

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Review questions
1. True or False: A private memory pool is a pool in which
multiple subsystems can run jobs.

2. In which pool does the LIC and operating system functions

run?
a. *MACHINE
b. *BASE
c. *INTERACT
d. *SPOOL

3. True or False: The recommendation is to allow interactive

and batch programs to run in the same pool.

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-35. Review questions

© Copyright IBM Corp. 2001, 2016 12-48

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Review answers
1. True or False: A private memory pool is a pool in which
multiple subsystems can run jobs.
The answer is False.

2. In which pool does the LIC and operating system functions

run?
a. *MACHINE
b. *BASE
c. *INTERACT
d. *SPOOL
The answer is *MACHINE.

3. True or False: The recommendation is to allow interactive

and batch programs to run in the same pool.
The answer is False.

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-36. Review answers

© Copyright IBM Corp. 2001, 2016 12-49

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 12. Work management: Subsystem concepts and overview

Uempty

Unit summary
• Describe what a subsystem is
• Describe what memory pools are
• List and describe the type of memory pools on the system
• Describe the types of work that can be run in the different memory
pools
• Explain why different types of memory pools exist
• List the commands used to display memory pool information
• Explain the information displayed on the work with system status
command display

Work management: Subsystem concepts and overview © Copyright IBM Corporation 2001, 2016

Figure 12-37. Unit summary

© Copyright IBM Corp. 2001, 2016 12-50

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Unit 13. Work management: Job

processing concepts and
interactive jobs
Estimated time
00:35

Overview
Work management is the basis for all work that is handled in the IBM i system. To control and tune
the performance of a system, you must understand how jobs are processed. This unit covers
interactive, batch and spool job processing, and the relationships among the work management
objects. We will also discuss how to track jobs through the system and what the controls are for
limiting the number of jobs executing concurrently.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 13-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Unit objectives
• Explain where work is processed on the system
• Explain the difference between a job and a thread
• List the types of system and users jobs that can be run on the system
• Explain when the different types of jobs start and end
• Explain the interactive job routing process
• Explain how paging works on the system
• Explain the different types of faults that can happen

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 13-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Topic 1: Job processing

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-2. Topic 1: Job processing

© Copyright IBM Corp. 2001, 2016 13-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Where work is processed

IBM i

SBS ABC SBS DEF

Job Routing Step
Thread 1 Job Routing Step
Job Thread 1
Routing Step
Thread 1 Thread 2
Thread 3

SBS XYZ Job

Job Routing Step Routing Step
Thread 1 Thread 1

Job Routing Step

Thread 1

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-3. Where work is processed

Depending on the job parameters each job can run in different subsystems using one or more
threads.

© Copyright IBM Corp. 2001, 2016 13-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Types of jobs
System jobs User jobs

Spooling
Interactive

Subsystem
monitor Batch

System
functions Autostart

Communication

Prestart

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-4. Types of jobs

Generally all jobs can be divided into System Jobs and User Jobs.
• System jobs:
• Spooling
• Subsystem monitoring
• System functions
• User jobs:
• Batch
• Interactive
• Autostart
• Communication
• Prestart

© Copyright IBM Corp. 2001, 2016 13-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Start / End of a job

Job Starts Ends *
Interactive Sign-on SIGNOFF
Batch Released from jobq End of requested command
Autostart Start of subsystem End of program in routing
entry or cmd in request data

Communication Request from remote End program in start

system request

Prestart Start of subsystem ENDPJ End of subsystem

or Start Prestart Job command

Spooling Start Reader or End Reader or

Writer command Writer command

* Unprinted spooled files for jobs that have ended are still managed by the system. This is reflected in the
"Jobs in system" values from WRKSYSSTS.

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-5. Start / End of a job

You can compare different start end actions for different jobs types.

© Copyright IBM Corp. 2001, 2016 13-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Interactive job: User view

IBM i
Database

Application
program

Reports

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-6. Interactive job: User view

An interactive job starts when you sign on to the system or transfer to a secondary or group job.
The interactive job ends when you sign off. Working from a display station, you interact with the
system by issuing commands, by using function keys, and running programs and applications. In
interactive jobs users communicate with operating system or applications (input data read results or
messages) using workstation.
The result of interactive job can be send to the display or to the output (outq and print or outq and
change to PDF, email, or stay in outq as a spool file).
The user see only input filed can put some value or run command/program and received result.

© Copyright IBM Corp. 2001, 2016 13-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Interactive job: Programmer view

Main storage Database

Description
PROG 1
Data
CALL
Output
queue

PRTF
DSPF
PROG 2 Printer file
Display DEVD
file
Printer
device
description

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-7. Interactive job: Programmer view

Programmer view is different than simple user. Programmer can manage what and how will be
displayed creating/changing display file. Programmer can manage data flow and manage
application logic. Programmer can have impact on the database (files structure, views indexes, and
so on). Similar to the display file, programmer can modeling printer file and produce different
printout for different functions or programs.

© Copyright IBM Corp. 2001, 2016 13-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Identify the types of jobs

1 2 3
Enter :: SBMJOB PAY01 :: STRSBS SPECIAL
User ID
Password Subsystem
description

Program PAY01 Program

QSYSOPR Startup
JOBQ
4 5

System System
A B
Others?
?
JOB

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-8. Identify the types of jobs

On the visual you see different jobs and for each of these jobs a different requirement. Each job
types have different characteristic and might have an impact on performance.

© Copyright IBM Corp. 2001, 2016 13-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Topic 2: Interactive jobs and

job tuning concepts

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-9. Topic 2: Interactive jobs and job tuning concepts

© Copyright IBM Corp. 2001, 2016 13-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Interactive job routing

QINTER
subsystem description

Attributes
Storage Pools MAXJOBS(*NOMAX)
ID Storage Job description
1 *BASESign-on Display File USERLIB/USERJOBD
2 *INTERACT (QSYS/QDSIGNON)
User Name
Job Queue
Work Station Entry Job Priority
User Work Station JobDescription Output Priority
Password LWS1 *USRPRF Routing Data (QCMDI)
Request Data
Routing Entry Initial Library List
SEQNBR CMPVAL PGM Class Pool More . . . .
50 QCMDI QCMD QINTER 2
CLASS
User profile = XYZ QSYS/QCMD QGPL/QINTER

PASSWORD = XXXXXX USERPGM Run

INLPGM = USERLIB/USERPGM Priority
JOBD = USERLIB/USERJOBD *INTERACT

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-10. Interactive job routing

To determine the best approach for a particular job, you must first determine which program should
control the routing step.
Using QSYS/CMD for interactive jobs - benefits
The IBM-supplied command processor QSYS/QCMD gives the greatest flexibility in terms of
making functions available to workstation users. Using QCMD to control the routing step gives you
the following benefits: The attention program is activated if it is specified in the user profile.
The initial program that is specified in the user profile is called.
The initial menu that is specified in the user profile is called.
The user is placed in System/36 environment as it is specified in the user profile.
In addition, the default using QCMD brings you to the Main menu where you can enter commands
directly, including the CALL command, which is used to call user-written functions. Menu options
with online help are provided to give easy access to system functions. Also provided are command
selection menus, quick access to index search, and the command entry function (called by CALL
QCMD). The command entry functions are intended primarily for programmers and operators who
require the full range of functions available through the direct use of commands.

© Copyright IBM Corp. 2001, 2016 13-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty
Calling a user program directly for interactive jobs - benefits
Your programs can be directly called to control the routing steps for interactive jobs. These
programs can be designed to give a more specialized access to functions needed by your
workstation users than the IBM-supplied programs give. In addition, because your programs are
tailored for specific functions, they should typically require even less system resource to support
their running than the IBM-supplied programs. You might also want to provide functions such as an
initial program and initial menu.
After you have determined which program controls the routing step, you must determine whether
routing is to be based on the workstation from which the job was started, or on the user (user
profile) who signed on.
Routing based on the workstation is accomplished using the routing data that is specified in the job
description that is associated with the workstation entry or profile for the device. Routing based on
a user can be done using the initial program that is specified in the user profile or the job description
in the user profile mapping to a routing entry other than QCMD.

© Copyright IBM Corp. 2001, 2016 13-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Selecting initial program

*USRPRF 1) Sign-on *SBSD
Workstation Entry
2b) JOBD *USRPRF
JOBD
? 2a) JOBD
Name

JOB DESCRIPTION

3) RTGDTA
Routing Entry

4) CMPVAL
INLPGM 5b) PGM
QSYS/QCMD 5) PGM
INLMNU
?
5a) Appl.
5c) INLPGM Other Pgm
or
INLMNU
Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-11. Selecting initial program

Initial program uses

Initial programs can interact with workstations to get input values from a workstation user. When an
initial program is called, it cannot receive parameter values. An initial program can be used in one
of two ways. To establish an initial environment for the user entering commands. For example, the
library list can be changed or print files and message files can be overridden. When an initial
program completes its function and returns to QSYS/QCMD, the initial menu is displayed.
As the controlling program for the job. If the initial program does not return to QSYS/QCMD, it
becomes the controlling program for the routing step. The initial menu is not displayed. The user
can only request those functions available through the initial program. For example, a menu can be
displayed with specific application options. The user can only perform the functions on the menu.
One example of such an option is sign off. If the SIGNOFF command is run, the job ends and the
system Main menu is never displayed. If you use this approach, consider using the user profile
option INLMNU to ensure that no menu is displayed.
An initial program can be written so that when a return is issued, it either does or does not return to
QSYS/QCMD. If the initial program returns to QSYS/QCMD, the initial menu is displayed.

© Copyright IBM Corp. 2001, 2016 13-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Work management: Interactive

• Interactive users might not all use the same applications.

• Some users might require page protection for faster service:

ƒ Telephone sales
ƒ Customer representatives
ƒ Face-to-face customer interactions

• Separate pools will protect pages and provide better performance for
the more important users’ jobs:
ƒ By default, all interactive users run in the same pool
ƒ Work management and standard security functions can be used to provide
different pools to different users

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-12. Work management: Interactive

A interactive job is started when a person signs on to a workstation.

© Copyright IBM Corp. 2001, 2016 13-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Pool sizes and paging

• Each storage pool holds information needed by the jobs that are
running in the pool.
• Information needed by one or more jobs that are not in main storage
must be read into main storage.
• If the job that requested the page waits for the operation to complete
before continuing, the operation is called a synchronous I/O.
• Most synchronous I/O operations are called page faults or faults.
• By using the Work with System Status (WRKSYSSTS) display or the
IBM Navigator for i screens, you can observe the performance
characteristics of the system.

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-13. Pool sizes and paging

© Copyright IBM Corp. 2001, 2016 13-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Pool benefits
• You can control work done in a subsystem by controlling the number
and size of pools. The greater the pool size, the more work can be done
in a subsystem.

• Shared storage pools allow the system to distribute storage

requirements of interactive jobs across multiple subsystems, still
allowing them to run in the same storage pool.

• Multiple pools can separate the amount of work done and influence the
response time for jobs.

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-14. Pool benefits

You can control how much work can be done in a subsystem by controlling the number and the size
of the pools. The greater the size of the pools in a subsystem, the more work can be done in it.
Using shared storage pools allows the system to distribute the storage requirements of interactive
users across multiple subsystems, still allowing their jobs to run in the same storage pool.
Multiple pools in a subsystem help you control the competition between jobs for system resources.
The advantage of having multiple pools in a subsystem is that you can separate the amount of work
that is done, and influence the response time for these jobs. For example, during the day you might
want interactive jobs running with a good response time. For better efficiency, you can make the
interactive pool larger. At night, you might be running many batch jobs, so you could make the
batch pool larger.
Do not divide the work too much because that makes it more difficult to tune and manage the
environment.

© Copyright IBM Corp. 2001, 2016 13-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Pages
The system moves what it needs or thinks it will need into memory.

Memory (Main storage)

*INTERACT Disk (Auxiliary storage)

P3 P4 G1 G2 G3 G4

P1 P2 P3 P4 P5 P6
Program
*PGM
F6 F7

F1 F2 F3 F4 F5 F6 F7 F8
File
P5
*FILE

G1 G2 G3 G4 G5
Process
G5 access group
F8
(PAG)

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-15. Pages

The system moves objects that it needs from auxiliary storage to main storage in storage pool
pages. This is normal system activity that occurs all the time. The entire object that a job needs
does not have to be in memory for the job to use it. Only those pages of the object that the job
currently needs for processing must be in memory.
A page fault occurs when a page that is referred to by an active program is not in main storage. On
a RISC machine, one page is 4096 bytes. Too many page faults impact performance.
There is a lot of information that a job needs in memory in order for it to function. We are familiar
with some of the objects it needs, and unfamiliar with others such as the Process Access Group
(PAG). A PAG is a group of job-related objects that can be paged out of storage in a single
operation when a job (process) enters or leaves a long wait.

© Copyright IBM Corp. 2001, 2016 13-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

How objects are stored on disk

Objects are not stored contiguously on disk.

A A

A A

When the system needs an object, or part of an object, it might have

to read it from more than one disk.

Internal pointers logically link together the whole object.

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-16. How objects are stored on disk

Objects stored on auxiliary storage are not stored contiguously. This is sometimes called scatter
loading. Bringing an object into memory might take reads from several disks.

© Copyright IBM Corp. 2001, 2016 13-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

How do faults affect performance?

The more faults,

...the more disk I/Os

...the higher the CPU use

...the longer the response time

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-17. How do faults affect performance?

The more page faults occur, the more times a job has to go to the disk to retrieve data. This can
have a negative effect, not just on this job, but on others that are waiting for data from the disk.

© Copyright IBM Corp. 2001, 2016 13-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

DB versus non-DB page faults

• Database page faults occur when the following are needed but are not
in memory:
ƒ Database data
ƒ Access paths (the logical organization of data in a database file)

• Non-database page faults occur when the following are needed but are
not in memory:
ƒ Program code
ƒ Job information
ƒ Data queue information

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-18. DB versus non-DB page faults

There are two types of page faults: Database and non-database (NDB).
• Database page faults occur when a file or part of a file, or an access path, is needed but is not
in memory.
• NDB page faults occur when objects such as programs (*PGM) or data queues (*DTAQ) are
needed in memory.

© Copyright IBM Corp. 2001, 2016 13-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Active Pools: Page faults

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-19. Active Pools: Page faults

The system keeps track of database and non-database page faults. Both figures are the number of
faults per second. The database category includes pages containing database data or access
paths. The non-database category includes pages other than database pages. At the top of the
window, the elapsed time is shown. Use F5 or select Options > Refresh to update the statistics.
Non-database Faults: This value indicates the number of times per second that a page (other than
data) was requested but was not in main storage.
Non-database Pages: The rate per second that pages (other than data) are read into main storage.
Current size: The amount of main storage available for pages that are needed. When requests are
made for pages, the pool that is to contain the page will be specified.
To work with Active Pools using IBM Navigator for i, you have to:
1. Open web browser http://<system name or IP address>:2001.
2. Log on to the IBM Navigator for i.
3. On the left pane, expand Work Management.
4. Click Active Memory Pools link.
In 5250 use WRSSYSSTS command.

© Copyright IBM Corp. 2001, 2016 13-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Paging (1 of 2)

JOB1 Needs
Memory = fixed size
9 pages
J1 J1 J1 J1

J2 J2
JOB2 Needs
J2 J1 J2 J1
11 pages
J1 J1 J2 J2

J2 J1 J2 J2

JOB3 Needs J2 J2
10 pages

There are not enough pages for JOB3 to be contained in memory.

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-20. Paging (1 of 2)

When a page is brought into memory, it might not stay in memory for as long as it is needed. This
occurs when more jobs try to run than those that can fit in memory.
• Jobs J1 and J2 are in memory.
• Job J3 needs memory but there are not enough pages for it to fit in memory with the other two
jobs.
• Job J3 needs to steal pages that are in use by the other jobs.

© Copyright IBM Corp. 2001, 2016 13-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Paging (2 of 2)

Memory Disk
J1 J1 J1 J3

J2 J2 J3 J3

J2 J3 J2 J3 J1 J1 J1 J1

J1 J3 J2 J2
J2 J2

J3 J1 J2 J2

J3 J3 J2 J3

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-21. Paging (2 of 2)

What happens to a page depends on how it has been handled:

• If it has not been changed or recently used, the page can be stolen.
• If it has been changed but has not been used recently, it is written to disk before it is stolen.
• If it has been stolen, it must be returned to memory before it can be re-used.
In order for the job J3 to be loaded into memory, several pages of job J1 and job J2 are moved to
disk.
In order for job J3 to fit into memory, it must take pages from job J1 or job J2, or both. Stolen pages
are written to disk. When J1 or J2 needs those pages again, the system must redo work that it has
already done to bring them back into memory. The system must repage. When J1 or J2 needs
additional pages in memory, it too will probably have to steal pages from other jobs that are running.
Because there is not enough room for all jobs to fit into memory at the same time, jobs will continue
to steal pages from each other, and the system will have to do a lot of repaging to keep up with the
requirements of a job.

© Copyright IBM Corp. 2001, 2016 13-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Paging of interactive jobs

CUST NO.___________
NAME______________
ADDRESS___________
CITY/ST_____________

ENTER

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-22. Paging of interactive jobs

Not all interactive jobs require pages of memory at the same time.
A job that is waiting for a user to press Enter does not need its pages in memory. Only when the
user presses Enter does the job need its pages in memory again.
A job really needs its pages in memory only when it requires processing. While a user is typing in
data, there is no need for a job to keep its pages in memory. By writing the pages of memory to disk
for jobs that do not currently need their pages in memory, the operating system makes it easier for
other jobs to read their needed pages into memory.

© Copyright IBM Corp. 2001, 2016 13-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

How does paging affect performance?

The more paging,

...the more disk I/Os

...the higher the CPU use

...the longer the response time

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-23. How does paging affect performance?

Page swapping is a normal activity, but you want to minimize it. Avoid having too many jobs
compete for the same pool of memory.
Keeping page swapping to a minimum improves performance.

© Copyright IBM Corp. 2001, 2016 13-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

How to ensure the system has enough memory?

Goal

The goal is to have enough memory so that once a job brings the pages
it needs into memory, it is able to use them before they are stolen by
another job.

Methodology
Either increase the amount of memory, or reduce the number of jobs
competing for it.

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-24. How to ensure the system has enough memory?

One of the methods to be sure that the system has enough memory is increase the amount of the
memory or reduce the number of jobs competing for it.

© Copyright IBM Corp. 2001, 2016 13-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Pool activity level

The pool activity level is the maximum number of threads that can be
active in a fixed amount of memory at any one time.

Memory (Activity level = 9)

T1 T3 T4 T6
T5 T2 T1 T3
Ineligible
T4 T6 T7 T8 queue
T7 T5 T9 T2 Thread 10

T8 T7 T9 T1

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-25. Pool activity level

The activity level of a storage pool is the number of threads that can be active at the same time in
a storage pool. A thread is an independent unit of dispatchable work. Each job has at least one
thread, the initial thread.
What happens if the activity level is nine and a tenth thread needs pages in memory? It goes to an
ineligible queue, where the system keeps track of those threads waiting for an activity level.
If a job needs memory but all the jobs that can compete for memory are active, the maximum
number being determined by the activity level, the thread must wait until another thread leaves its
activity level. This technique avoids a lot of repaging (thrashing) and reduces the total time that is
required by all threads.
An activity level does not affect the number of jobs that can be active in a system at one time.

© Copyright IBM Corp. 2001, 2016 13-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

IBM i activity levels

Job 2 Job 3 … Job 29 Job 30

Activity
levels Yes
full
Ineligible
No queue

Main storage

Job 1 Job 8 Job 27 Job16

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-26. IBM i activity levels

Storage pool uses something called activity levels to control the maximum number of threads that
can be active in a fixed amount of memory at any given time.

© Copyright IBM Corp. 2001, 2016 13-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Active Pools: Activity level/transition data

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-27. Active Pools: Activity level/transition data

Memory Pool Activity Level

Maximum eligible threads: The maximum number of threads that can run in the memory pool
at the same time. For the base pool, the system value for the base memory pool activity level
(QBASACTLVL) is set.
When more threads are started than can run (current ineligible threads) at the same time
because of the activity level controls, the excess threads have to wait to use the processing unit
(normally this wait is short). The memory pool activity level lets you limit the amount of main
memory contention in the various memory pools in your subsystems.
The number of threads running (current threads) refers to the number of threads that are
eligible to compete for the processor and that count against the activity level for a memory pool.
In this sense, active threads do not include threads that are waiting for input, for a message, for
a device to be allocated, or for a file to be opened. Active threads do not include threads that
are ineligible (threads that are ready to run but where the memory pool activity level is at its
maximum).

© Copyright IBM Corp. 2001, 2016 13-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty
State Transitions per Minute
Active -> Wait: The rate, in transitions per minute, at which threads move from an active to a
waiting condition. The thread no longer needs an activity level. Usually, this transition
represents the system beginning its wait for the user to press Enter or a function key.
Wait -> Ineligible: The rate, in transitions per minute, at which threads move from a waiting to
an ineligible condition. This usually means that a user pressed Enter or a function key and that
there was no available activity level.
Active -> Ineligible: The rate, in transitions per minute, at which threads move from an active
to an ineligible condition. The thread exceeded its time slice in an activity level.
Paging option
Determines whether the system should dynamically adjust the paging characteristics of the
memory pool for optimum performance. Possible values are:
▪ Fixed: The system does not dynamically adjust the paging characteristics of the memory
pool. It uses system-default values.
▪ Calculated: The system dynamically adjusts the paging characteristics of the memory pool
for optimum performance.
▪ User-defined value set via API: The system does not dynamically adjust the paging
characteristics of the memory pool. Rather, it uses values that have been defined through
an application programming interface (API).
It is possible that a system operator would be asked by a performance person to adjust the paging
value. To provide an understanding of the function, you might explain that not all jobs use memory
or disk in the same way. For instance, some BATCH jobs do very little I/O, while others are always
reading and writing to disk. The formula that the system regularly uses to determine where to store
new data can give one of these jobs better performance than the other. When the value for the
Paging Option is *FIXED, the system uses a standard formula; when the value is set to *CALC, the
system varies how it manages the space for a job which might give a job improved throughput;
when the value is set to *USRDFN, the system uses values identified in an application
programming interface (API) to adjust the paging characteristics. The value should not be altered
until someone with a solid performance background has analyzed the system and determined that
a change should be made to this value.

© Copyright IBM Corp. 2001, 2016 13-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Review questions
1. A (blank) is an independent unit of dispatchable work.
a. Job
b. Routing step
c. Thread
d. Work station entry

2. Which of the following is not considered a user job?

a. Autostart
b. Batch
c. Interactive
d. Spool

3. An (blank) job is associated with a subsystem and that starts

when the subsystem is started.
a. Interactive
b. Autostart
c. Prestart
d. Spooling

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-28. Review questions

© Copyright IBM Corp. 2001, 2016 13-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Review answers
1. A thread is an independent unit of dispatchable work.
a. Job
b. Routing step
c. Thread
d. Work station entry
The answer is thread.

2. Which of the following is not considered a user job?

a. Autostart
b. Batch
c. Interactive
d. Spool
The answer is spool.

3. An autostart job is associated that starts when the subsystem is

started.
a. Interactive
b. Autostart
c. Prestart
d. Spooling
The answer is autostart.
Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-29. Review answers

© Copyright IBM Corp. 2001, 2016 13-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 13. Work management: Job processing concepts and interactive jobs

Uempty

Unit summary
• Explain where work is processed on the system
• Explain the difference between a job and a thread
• List the types of system and users jobs that can be run on the system
• Explain when the different types of jobs start and end
• Explain the interactive job routing process
• Explain how paging works on the system
• Explain the different types of faults that can happen

Work management: Job processing concepts and interactive jobs © Copyright IBM Corporation 2001, 2016

Figure 13-30. Unit summary

© Copyright IBM Corp. 2001, 2016 13-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Unit 14. Work management: Job

processing concepts of other job
types
Estimated time
00:25

Overview
Work management is the basis for all work that is handled in the IBM i system. To control and tune
the performance of a system, you must understand how jobs are processed. This unit covers the
other types of job processing (batch and spool job, autostart, communication, and prestart) and the
relationships among the work management objects. We will also discuss how to track jobs through
the system.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 14-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Unit objectives
• Explain where work is processed on the system
• Explain the function provided by the MAXACT attribute in a job queue
• Explain the function provided by the MAXPTYn attribute in a job queue
• Explain the batch job routing process
• Explain the function served by the timeslice attribute
• Explain the function served by the runpriority attribute

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 14-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Topic 1: Batch jobs and job

tuning concepts

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-2. Topic 1: Batch jobs and job tuning concepts

© Copyright IBM Corp. 2001, 2016 14-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Batch jobs

Subsystem QSYS/QBATCH
Monitor Subsystem Description Main Storage
Program
Attributes

Maxjobs(*NOMAX)
Storage Pools
*INTERACT
ID Storage
1 *BASE

QBATCH
*BASE

Job Queue Entry

Job Queue Max Act *MACHINE

JOBQ QGPL/QBATCH 1

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-3. Batch jobs

A batch job is a predefined group of processing actions submitted to the system to be performed
with little or no interaction between the user and the system. Jobs that do not require user
interaction to run can be processed as batch jobs. A batch job typically is a low priority job and can
require a special system environment in which to run.
Batch jobs run in the system background, freeing the user who submitted the job to do other work.
Several batch jobs can be active at the same time.
Batch jobs can be started when a user:
• Causes a job to be placed in a job queue
• Issues a communication program start request
• Starts a subsystem with a prestart job
• Uses the spawn() API
When a user submits a batch job, the job gathers information from several system objects before it
is placed on a job queue.
1. A user submits a job.

© Copyright IBM Corp. 2001, 2016 14-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty
2. The job searches for job attributes. If the job attributes are not found on the Submit Job
(SBMJOB) command, the job looks in the job description (specified on the SBMJOB command),
the current user's user profile, and the currently active job (the job issuing the SBMJOB
command). Note: Similar to interactive job initiation, you can specify in the job description to
use the user profile. The user profile can specify to use a system value to find certain job
attributes.
3. Once the job has all of its attributes, it resides on the job queue.
4. When the subsystem is ready to handle a job, it looks for jobs in the job queues (those that the
subsystem has allocated).
5. Then, like interactive job processing, the subsystem checks the job description for the routing
data.
6. The subsystem uses the routing data to find a routing entry. The routing entry provides
information about which pool the job uses, which routing program is used, and from which class
the job gets its run-time attributes.
7. After this information is obtained, the routing program is run. If you use QCMD, QCMD carries
out the SBMJOB command. It runs the command specified on the CMD or RQSDTA parameter.

© Copyright IBM Corp. 2001, 2016 14-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Job selection
Job queue entries in subsystem description

JOBQ ` JOBQA JOBQB JOBQC

SEQNBR 1O 20 30
MAXACT *NOMAX 1 1
MAXPTY1 *NOMAX *NOMAX *NOMAX
. : : :
MAXPTY9 : :

JOB 2 JOB 4 JOB 5

JOB 1 JOB 3

Jobs 1 to 5 have equal priority.

Which jobs run concurrently if the subsystem description has:

MAXJOBS = 2

? MAXJOBS = 3
MAXJOBS = 4
MAXJOBS = *NOMAX
Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-4. Job selection

For a batch jobs the most important parameter is maximum concurent jobs running at the same
time in a job queue. The parameter is set for job queue (MAXACT).

© Copyright IBM Corp. 2001, 2016 14-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Batch job routing

SBMJOB CMD(CALL PRPROC) RTGDTA(QCMDB) JOB(PAY) JOBQ(QBATCH)

1) QBATCH
Subsystem
Subsystem Description
Monitor PAY JOBQ
Program Max Jobs - *NOMAX QBATCH
Job Queue Entry

2) Job Queue Max Act Max Pty(n)

QBATCH 1 *NOMAX

Routing Entry
SEQNBR CMPVAL PGM CLASS POOL
9999 *ANY QCMD QBATCH 1

4) CLASS
3) QGPL/QBATCH

Run Priority 6)
CALL PRPROC
5)
QSYS/QCMD
*BASE JOB MSGQ
PAY
7) PRPROC

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-5. Batch job routing

The subsystem uses the routing data to find a routing entry. The routing entry provides information
about which pool the job uses, which routing program is used, and from which class the job gets its
run-time attributes. After this information is obtained, the routing program is run. If you use QCMD,
QCMD carries out the SBMJOB command. It runs the command specified on the CMD or RQSDTA
parameter

© Copyright IBM Corp. 2001, 2016 14-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Batch tuning: A pool for batch jobs

• By default, batch jobs are submitted to the QBATCH JOBQ.
• QBATCH will initiate the jobs from the QBATCH JOBQ.
• Batch jobs will run in *BASE.
• Some potential problems:
ƒ *BASE contains a lot of different jobs:
í Monitors
í Servers
í Routers
í And so on
ƒ Batch jobs are the lowest priority jobs in *BASE.
ƒ TSE (Time Slice End) jobs might make the situation worse.

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-6. Batch tuning: A pool for batch jobs

QBatch is the Batch Subsystem job queue. The QBATCH jobq exist in QGPL library.

© Copyright IBM Corp. 2001, 2016 14-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Performance runtime attributes: Timeslice

• Timeslice indicates the amount of uninterrupted CPU time a job can use
during a single turn in an activity level:
ƒ Jobs are interrupted only by long waits (record locks or display waits)
ƒ TIMESLICE resets at each interrupt
• If timeslice is exceeded and a job with the same priority is waiting, the
system will:
ƒ Interrupt the job
ƒ Remove the job from main storage
• In addition, more frequent interrupts called Internal Timeslice will
interrupt the job but will not remove it from main storage
• Batch jobs usually exceed timeslice many times while interactive jobs
do not exceed timeslice very often
• Default timeslice is five seconds for batch jobs, two seconds for
interactive jobs

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-7. Performance runtime attributes: Timeslice

Time slice (TIMESLICE)

Specifies the maximum amount of processor time (in milliseconds) given to each thread in a job
using this class before other threads in a job or other jobs are given the opportunity to fun. The time
slice establishes the amount of time needed by a thread in a job to accomplish a meaningful
amount of processing. At the end of the time slice, the thread might be put in an inactive state so
that other threads can become active in the storage pool.
2000
A maximum run time of 2000 milliseconds is allocated to each thread each time it is allowed to
process.
0-9999999
Specify the maximum amount of time (in milliseconds) that each thread in a job using this class
can have to run when it is given processing time.
Note: Although you can specify a value of less than 8, the system takes a minimum of 8
milliseconds to run a process. If you display a job’s run attributes, the time slice value is never
less than 8.

© Copyright IBM Corp. 2001, 2016 14-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Performance runtime attributes: Run priority

• Run priority (RUNPTY) is used to determine the order in which jobs are
chosen to use a processor.
• RUNPTY for batch jobs defaults to 50.
• RUNPTY for interactive jobs defaults to 20.
• The system determines which jobs use a processor by either of two
methods:
ƒ Fixed priority
ƒ Dynamic priority (the system default)
• When available, the system will try to assign a job to use the processor.
This is a function called task dispatching.

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-8. Performance runtime attributes: Run priority

Run priority (RUNPTY)

Specifies the run priority of jobs that use the class. Run priority is a value ranging from 1 (highest
priority) through 99 (lowest priority) that represents the priority at which the job competes for the
processing unit relative to other jobs that are active at the same time. For multi-threaded jobs, the
run priority is also the highest run priority allowed for any thread within the job. Individual threads
within the job might have a lower priority.
This value represents the relative, not absolute, importance of the job. For example, a job with a run
priority of 25 is not twice as important as one with a run priority of 50.
50
Jobs that use this class have a run priority of 50.
1-99
Specify the run priority of jobs this class.

© Copyright IBM Corp. 2001, 2016 14-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Multiple types of batch jobs

• There are three general types of batch jobs:
ƒ Production batch job submitted by the system operator:
í Process a lot of data
í Run for a long time
ƒ Programming job submitted by a batch programmer:
í Process very little data
í Run for a long time
í For example, a program compile
ƒ User batch job submitted by production users:
í Processing characteristics are unpredictable
í Run time is unpredictable
• Running these different styles of jobs in the same storage pool might
not work well.
• Running different batch job types in different storage pools:
í Protects pages
í Reduces I/O
í Improve run time

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-9. Multiple types of batch jobs

Batch jobs can be submitted by the system operator, programmers, and other users.

© Copyright IBM Corp. 2001, 2016 14-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Topic 2: QSPL subsystem

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-10. Topic 2: QSPL subsystem

© Copyright IBM Corp. 2001, 2016 14-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

STRSBS QSPL
QSYS/QSPL
1) Subsystem subsystem description Main storage
monitor
program Attributes
*SPOOL
Maxjobs *NOMAX
2) Storage Pools

ID Storage
*INTERACT
1 *BASE
(3)
2 *SPOOL

QSPL
*BASE

Job Queue Entry

Job Queue Max Act *MACHINE

QGPL/QSPL *NOMAX
JOBQ

Note: Spool job routing is identical to batch

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-11. STRSBS QSPL

The job routing for QSPL is identical to that of batch.

When the QSPL subsystem start two memory pools will be use *SPOOL and *BASE.
A reader job is a spooled input job, and a writer job is a spooled output job.
Reader A reader job reads batch job streams from database files, and places the jobs on a job
queue. The reader job is part of input spooling and is an IBM-supplied program. Writer A writer job
writes records from printer output files (also called spooled files) to a printer. The writer job is an
IBM-supplied program, started in the spooling subsystem where it selects files from the output
queue to be printed.

© Copyright IBM Corp. 2001, 2016 14-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Topic 3: Autostart jobs

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-12. Topic 3: Autostart jobs

© Copyright IBM Corp. 2001, 2016 14-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Autostart jobs
QBATCH
1) Subsystem Subsystem description Main storage
monitor
program
Job Attributes
description *SPOOL
startup Maxjobs *NOMAX
Storage Pools

ID Storage *INTERACT
User name 1 *BASE
Job queue
Job priority
Output priority
*BASE
Routing data QCMDI
Request data 2) Autostart job entry
4) CALL START 3)
Initial library list
*MACHINE
More . . . Job description
STARTUP

Program

START

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-13. Autostart jobs

Autostart jobs
An autostart job is a batch job doing repetitive work, one-time initialization work that is associated
with a particular subsystem, initializes functions for an application, or provides centralized service
functions for other jobs in the same subsystem. An autostart job in the controlling subsystem can be
used to start other subsystems (as does the IBM-supplied controlling subsystem). The autostart
jobs associated with a subsystem are automatically started each time the subsystem is started.
To add an autostart job entry to the subsystem description, use the Add Autostart Job Entry
(ADDAJE) command. When the subsystem starts the autostart job, it uses the job description
specified in the autostart job entry to determine the routing data (RTGDTA) and tries to match that
to the compare value in the routing entries defined in the subsystem description. When a match is
found, other information in the routing entry is used to establish the work environment for the job
such as the class that will be used and the program that will be run. When the program name in the
routing entry is QCMD, the command processing program will look for the request data or
command (RQSDTA) on the job message queue. The request data is found in the job description for
the autostart job entry.

© Copyright IBM Corp. 2001, 2016 14-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty
If more than one autostart job is specified for a subsystem, all autostart jobs are started
immediately rather than one followed by another. If the value specified for the maximum jobs in
subsystem (MAXJOBS) is exceeded, no other jobs can be started in the subsystem until enough
autostart jobs have completed so that the number of jobs running is below the maximum jobs.
The job description that is used for an autostart job is specified using the Add Autostart Job Entry
(ADDAJE) command. When the subsystem is started, the job operates under the user profile name
in the specified job description. You can not specify the job description which contains
USER(*RQD). Because the autostart job operates under the user profile that is specified by the job
description, you need to control who is allowed to change the job description.

© Copyright IBM Corp. 2001, 2016 14-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Topic 4: Communication jobs

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-14. Topic 4: Communication jobs

© Copyright IBM Corp. 2001, 2016 14-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Communication jobs
QCMN
Subsystem
subsystem description
monitor Main storage
program
Attributes
*SPOOL
Maxjobs *NOMAX
Storage Pools
Communications
network
ID Storage *INTERACT
1 *BASE

Line
*BASE
Control Communications entry
Unit

Dev Jobd
Device
*ALL *USRPRF
*MACHINE

Mode

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-15. Communication jobs

A communications job is a batch job that is started by a program start request from a remote
system. Job processing involves a communication request and appropriate specifications.
For a communications batch job to run on an IBM® i system, a subsystem description containing a
work entry for communications jobs must exist on the system. The communications work entry
identifies to the subsystem the sources for the communications job it processes. The job
processing begins when the subsystem receives a communications program start request from a
remote system and an appropriate routing entry is found for the request.
Routing data for communication jobs
Job routing of communications jobs is determined by the program start request that is received
from the remote system. When a program start request is processed on the target system, a
fixed-length data stream that is used as routing data is created. Position 25 of the routing data
always contains PGMEVOKE for communications requests. Subsystem routing entries that specify
a compare value of PGMEVOKE in position 29 typically have *RTGDTA as the program name. This
means that the program name specified in the routing data (from the remote system's program start
request) is the program to run.
If a special processing environment is required for certain communications jobs, you can add an
additional routing entry to the subsystem description, specifying a compare value whose starting
position is 37. This compare value should contain the program name for the program start request.

© Copyright IBM Corp. 2001, 2016 14-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty
The routing entry must have a sequence number lower than the routing entry that uses
PGMEVOKE as the compare value. This method allows certain communications jobs to run with a
different class or pool specification.
Security
The security on the system controls who can use communications devices as well as who can
access the commands used with the associated device descriptions. You should consider
additional security measures when writing and running application programs on both remote and
target systems.
Job description for communication jobs
The job description used for communications jobs is specified on the Add Communications Entry
(ADDCMNE) command. The user specified on this job description is ignored. The system gets the
user name for communications jobs from the program start request. If the program start request
does not specify a user name, the system uses the default user value from the communications
entry. To ensure a greater degree of system security, include user information about the program
start request rather than specifying a default user in the communications work entry.

© Copyright IBM Corp. 2001, 2016 14-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Topic 5: Prestart jobs

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-16. Topic 5: Prestart jobs

© Copyright IBM Corp. 2001, 2016 14-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Prestart jobs
Subsystem QBATCH
monitor subsystem description Main storage
program Attributes
Prestart job entry *SPOOL
Maxjobs *NOMAX
attributes
Storage Pools
Subsystem description
ID Storage *INTERACT
Program name
1 *BASE
User profile
Job name
Job description *BASE
Start jobs
Initial # jobs Prestart job entry
Max # prog. requests *MACHINE
Pool ID
Class

Job
Program

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-17. Prestart jobs

A prestart job is a batch job that starts running before a work request is received. The prestart jobs
are started before any other types of jobs in a subsystem. Prestart jobs are different from other jobs
because they use prestart job entries (part of the subsystem description) to determine which
program, class, and storage pool to use when they are started.
Within a prestart job entry, you must specify attributes that the subsystem uses to create and
manage a pool of prestart jobs. Use prestart jobs to reduce the amount of time required to handle a
work request. Two types of prestart jobs exist. Each type handles different types of requests. Before
a job waits for its first request, it will be shown as Prestart only because the system does not know
yet what type of requests the job will handle. Prestart communications The job is a communications
batch job that starts running before a remote system sends a program start request. Prestart batch
The job is a batch job that starts before a work request is received.
A prestart job starts before a work request is received, either when the subsystem starts or as a
result of the Start Prestart Jobs (STRPJ) command. Prestart jobs start from a prestart job entry
(PJE) in the subsystem description. The prestart job entry specifies attributes such as what
program to run in the prestart job, the user profile under which the prestart job starts running, the
job description, the class used to specify the run-time attributes of the job, and the memory pool in
which the prestart job runs.

© Copyright IBM Corp. 2001, 2016 14-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty
Prestart jobs can start and initialize themselves before a work request is received. This reduces the
amount of time required to handle the requests. Prestart jobs provide the ability to initialize once
and handle many requests so that a new job is not needed for every request. Many client/server
applications use prestart jobs to handle the requests for the client user. Having a job ready to go
makes the performance better in this situation because the prestart job can start processing the
request for the user immediately.

Note

The value specified for the maximum number of jobs in the subsystem can prevent prestart jobs
from starting. If the maximum number of jobs in the subsystem is exceeded, no prestart jobs can be
started. When enough jobs have completed so that the number of jobs running is below the
maximum number of jobs in the subsystem, prestart jobs in the subsystem can start.

© Copyright IBM Corp. 2001, 2016 14-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Work management objects

IBM i

Subsystem SBSD

Work
Job
entries JOBD
thread
Routing
entries Class

Program
Pools

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-18. Work management objects

Whether you are new to work management or have been using work management tools for years,
these work management concepts might be useful for you.
The structure of your system
After receiving your IBM i product, you might want to know what subsystems are included with the
system, whether you need to change any start-up programs, and what kind of user interface you
will work with.
Subsystems
The subsystem is where work is processed on the system. A subsystem is a single, predefined
operating environment through which the system coordinates the work flow and resource use. The
system can contain several subsystems, all operating independently of each other. Subsystems
manage resources.
Memory pools
A memory pool is a logical division of main memory or storage that is reserved for processing a job
or group of jobs. On your system, all main storage can be divided into logical allocations called
memory pools. By default, the system manages the transfer of data and programs into memory
pools.

© Copyright IBM Corp. 2001, 2016 14-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty
Jobs
All work done on a system is performed through jobs. Each job has a unique name within the
system. All jobs, with the exception of system jobs, run within subsystems. A job can enter the
subsystem from any of the work entries, such as a job queue entry, workstation entry,
communications entry, autostart job entry, or prestart job entry.
Job scheduling options
The job schedule function allows for time-dependent scheduling of IBM i batch jobs. You can
schedule jobs to be released from the job queue at a particular time, or you can use a job schedule
entry to submit your job to the job queue automatically at the time you specify. Job scheduling
allows you to control the date and time a batch job is submitted to or becomes eligible to start from
a job queue. This flexibility can help you as you balance the work load on your system.
Job queues
A job queue contains an ordered list of jobs waiting to be processed by a subsystem. The job queue
is the first place that a submitted batch job goes before becoming active in a subsystem. The job is
held here until a number of factors are met.
Output queues
Output queues are areas where printer output files (also called spooled files) wait to be processed
and sent to the printer. Printer output is created either by the system or by the user using a print file.
Job logs
A job log contains information related to requests entered for a job. A job log has two forms, a
pending form and a spooled form.
Job accounting
The job accounting function gathers data so that you can determine who is using your system and
what system resources they are using. It also assists you in evaluating the overall use of your
system. Job accounting is optional. You must take specific steps to set up job accounting. You can
request the system to gather job resource accounting data, printer file accounting data, or both. You
can also assign accounting codes to user profiles or specific jobs.

© Copyright IBM Corp. 2001, 2016 14-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Performance tuning education

IBM i Performance Tuning - I: IBM i Structure, Tailoring and Basic Tuning

Course code: OL23G Skill level: Intermediate
Delivery type: Classroom Duration: 2.0 days

IBM i Performance Tuning - II: Advanced Analysis and Capacity Tuning

Course code: OL66G Skill level: Intermediate
Delivery type: Classroom Duration: 2.0 days

http://www.ibm.com/training

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-19. Performance tuning education

IBM i Performance Tuning - I: IBM i Structure, Tailoring and Basic Tuning

Course code: OL23G
This classroom course of two days explains how to balance the workload on the IBM i system to
ensure optimum performance. Specifically, this course explains how to manage workloads,
measure system performance, and tune the operating system to meet processing requirements.
Hands-on exercises give you the opportunity to use the system functions that are available for
controlling workload and tuning system performance. Evaluation criteria presented in this course
are based on the latest information available from IBM development labs.
IBM i Performance Tuning - II: Advanced Analysis and Capacity Tuning
Course code: OL66G
This course will help you to better understand the techniques of performance analysis and capacity
planning on systems and partitions running IBM i and develop an appreciation of how IBM i
operates and interfaces with applications. This course is expected to build skills to better manage
performance and capacity on systems and partitions running IBM i.
The course explains IBM i concepts, including the Technology Independent Machine Interface
(TIMI), main storage pools, auxiliary storage pools, management of jobs, threads, and tasks, job
run-time structure, performance monitoring, data collection, and analysis of performance data.

© Copyright IBM Corp. 2001, 2016 14-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty
This 4-day course includes hands-on activities using performance data from IBM i systems to help
the student appreciate the concepts discussed. This course is designed for those running Power
Systems on IBM i. While it includes i 7.2 content, it is suitable for those currently using prior
versions of IBM i.
The first day of class (units 1-6) focuses on teaching the performance management process, the
performance considerations of key hardware components and virtualization options, and tuning
options to help optimize performance. During these lectures, students should gain an appreciation
of the unique storage management and work management components in the IBM i architecture
and how these components need to be managed for optimal performance.
Days 2-4 of the class focus on the tools and techniques to monitor, analyze, and plan for
performance of Power Systems with IBM i and Logical partitions (LPARs).
The primary analysis tool that will be used is the Performance Data Investigator (PDI) which is
included with IBM Navigator for i. PDI is also used with IBM Systems Workload Estimator (WLE) for
capacity planning activities.

© Copyright IBM Corp. 2001, 2016 14-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Review questions (1 of 2)
1. The (blank) specifies the maximum number of jobs that can
be concurrently active from a job queue.
A. SEQNBR
B. MAXACT
C. MAXPTYn
D. MAXJOBS

2. The (blank) can limit the number of jobs of a specific priority

that can be released at one time from the job queue.
A. SEQNBR
B. MAXACT
C. MAXPTYn
D. MAXJOBS

3. True or False: Timeslice indicates the amount of

uninterrupted CPU time a job can use during a single turn in
an activity level.

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-20. Review questions (1 of 2)

© Copyright IBM Corp. 2001, 2016 14-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Review answers (1 of 2)
1. The MAXACT specifies the maximum number of jobs that can be
concurrently active from a job queue.
a. SEQNBR
b. MAXACT
c. MAXPTYn
d. MAXJOBS
The answer is MAXACT.

2. The MAXPTYn can limit the number of jobs of a specific priority that
can be released at one time from the job queue.
a. SEQNBR
b. MAXACT
c. MAXPTYn
d. MAXJOBS
The answer is MAXPTYn.

3. True or False. Timeslice indicates the amount of uninterrupted

CPU time a job can use during a single turn in an activity level.
The answer is true.
Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-21. Review answers (1 of 2)

© Copyright IBM Corp. 2001, 2016 14-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Review questions (2 of 2)
4. True or False: Run priority is used to determine the order in
which jobs are chosen to use a processor.

5. True or False: Autostart jobs can only run on specific

subsystems.

6. True or False: The job routing for QSPL is identical to that of

batch.

7. Which of the following is the supplied subsystem used to run

communication jobs?
a. QINTER
b. QBATCH
c. QBATCH
d. QCMN

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-22. Review questions (2 of 2)

© Copyright IBM Corp. 2001, 2016 14-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Review answers (2 of 2)
4. True or False: Run priority is used to determine the order in which
jobs are chosen to use a processor.
The answer is true.

5. True or False: Autostart jobs can only run on specific subsystems.

The answer is false.

6. True or False: The job routing for QSPL is identical to that of batch.
The answer is true.

7. Which of the following is the supplied subsystem used to run

communication jobs?
a. QINTER
b. QBATCH
c. QBATCH
d. QCMN
The answer is QCMN.

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-23. Review answers (2 of 2)

© Copyright IBM Corp. 2001, 2016 14-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 14. Work management: Job processing concepts of other job types

Uempty

Unit summary
• Explain where work is processed on the system
• Explain the function provided by the MAXACT attribute in a job queue
• Explain the function provided by the MAXPTYn attribute in a job queue
• Explain the batch job routing process
• Explain the function served by the timeslice attribute
• Explain the function served by the runpriority attribute

Work management: Job processing concepts of other job types © Copyright IBM Corporation 2001, 2016

Figure 14-24. Unit summary

© Copyright IBM Corp. 2001, 2016 14-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Unit 15. Work management: Submitting

and tracking of batch jobs
Estimated time
00:20

Overview
This unit will discuss batch processing and spooling. We will look at the ways to submit batch jobs
and how to track these jobs as they go through the system. The spooling readers and writers are
system batch jobs which are used by interactive and jobs when they generate print output. We are
going to discuss how spooling interfaces with the user's job and how to control readers and writers.

How you will check your progress

• Review questions
• Machine exercises

© Copyright IBM Corp. 2001, 2016 15-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Unit objectives
• Describe what command is used to submit a job to run in batch mode
• Explain the process on the system when a job is submitted to run in
batch
• Explain how to schedule a batch job
• List and explain the commands you can use to track jobs on the system
• Explain how data management intercepts output generated by a
program
• Explain the function of a printer device file
• Explain the decision process used by the system to determine where to
send your output

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 15-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Putting a job on a job queue

SBMJOB CMD(Command to run)
+ PARAMETERS BELOW

DEFAULT TO DEFAULT TO OTHER DEFAULTS

*CURRENT *JOBD

PRTDEV SCDDATE JOB JOBD(*USRPRF)

OUTQ SCDTIME JOBQ RTGDTA(QCMDB)
USER SBMFOR JOBPTY RQSDTA(*CMD)
PRTTXT SRTSEQ OUTPTY DSPSBMJOB(*YES)
SYSLIBL LANGID LOG MSGQ(*USRPRF)
CURLIB CNTRYID LOGCLPGM CPYENVVAR(*NO)
INLLIBL CCSID INQMSGRPY
HOLD
DATE
SWS
JOBMSGQMX
JOBMSGQFL
ALWMLTTHD

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-2. Putting a job on a job queue

The Submit Job (SBMJOB) command allows a job that is running to submit another job to a job
queue to be run later as a batch job. Only one element of request data can be placed on the new
job's message queue. The request data can be a CL command if the routing entry used for the job
specifies a CL command processing program (such as the IBM-supplied QCMD program).

© Copyright IBM Corp. 2001, 2016 15-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Submitting a batch job

SBMJOB CMD(CALL PGMY) JOB(JOBY) JOBQ(QBATCH) RTGDTA(QCMDB)
MONITOR
JOB QUEUE QBATCH SUBSYSTEM
PGM
BATCH

JOBQ POOL
JOBY QBATCH *BASE

Routing Entries
RTGDTA=
QCMDB SEQNBR CMPVAL PGM CLS MAXACT POOLID

10 QCMDB QCMD QBATCH *NOMAX 1

*BASE JOB MESSAGE

QUEUE - JOBY
QCMD CALL PGMY QCMD
Executes
PGMY
Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-3. Submitting a batch job

Since batch jobs are typically low priority jobs that require a special system environment in which to
run (such as running at night) they are placed in batch job queues. In the job queue, the batch job
receives a run-time schedule and a priority. To submit a job to a batch job queue, you use the
character-based interface and one of two commands.
Command: Submit Job (SBMJOB)
Command: Submit Database Job (SBMDBJOB)
The difference in these commands is the source of the job:
The SBMJOB command submits a job to a batch job queue by specifying a job description and by
specifying a CL command or request data, or specifying routing data to run a program. If you want
to run a single CL command in a batch job, use the CMD parameter on SBMJOB, which does
syntax checking and allows prompting.
The SBMDBJOB command can be used to submit a job to a batch job queue from a database file.
For these jobs, the job description comes from the BCHJOB statement in the input stream.

© Copyright IBM Corp. 2001, 2016 15-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty
Inline data files
An inline data file is a data file that is included as part of a batch job when the job is read by a
reader or a submit jobs command. You use SBMDBJOB or STRDBRDR to queue a CL batch stream
(stream of CL commands to be run). That CL batch stream can include data to be placed into inline
data files (temporary files). When the job ends, the inline data files are deleted.
Considerations for opening inline data files
You need to consider these elements when you open inline date files.

1+1 2 Example

In the following example, the SBMJOB command submits a job named WSYS, using the job
description QBATCH, to the job queue QBATCH. The CMD parameter gives the CL command that
will run in the job. SBMJOB JOBD(QBATCH) JOB(WSYS) JOBQ(QBATCH) CMD(WRKSYSSTS)
Note: If you get a message that the job was not submitted, you can display the job log spooled file
to find errors. Use the WRKJOB command. Specify the job that was not scheduled, select option 4
for spooled files. Display the job log spooled file to find the errors.

A user submits a job.

The job searches for job attributes. If the job attributes are not found on the Submit Job (SBMJOB)
command, the job looks in the job description (specified on the SBMJOB command).
Once the job has all of its attributes, it resides on the job queue.
When the subsystem is ready to handle a job, it looks for jobs in the job queues (those that the
subsystem has allocated).
Then, like interactive job processing, the subsystem checks the job description for the routing data.
The subsystem uses the routing data to find a routing entry.
The routing entry provides information about which pool the job uses, which routing program is
used, and from which class the job gets its run-time attributes.
After this information is obtained, the routing program is run. If you use QCMD, QCMD carries out
the SBMJOB command. It runs the command specified on the CMD or RQSDTA parameters user
profile, and the currently active job (the job issuing the SBMJOB command).

© Copyright IBM Corp. 2001, 2016 15-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Job message queue

SBMJOB CMD(CALL PGMY) JOB(JOBY)
Uses:
– Diagnostic messages
– Program termination messages
– Commands

JOBY

JOBQ CALL
PGMY

Allocated automatically by the system

Job Msg Queue

Same name as job = JOBY
Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-4. Job message queue

The job message queue is the same as the job.

© Copyright IBM Corp. 2001, 2016 15-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Scheduling a batch job

SBMJOB SCDDATE( ) SCDTIME( )
or
ADDJOBSCDE . . .

Add an entry to the Job Schedule Object QDFTJOBSCD in QUSRSYS

WRKJOBSCDE
ADD... CHG...
HLD... RLS...
RMV...

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-5. Scheduling a batch job

You can schedule a job to run using the Advanced Job Scheduler, by using the IBM® Navigator for
i Job Properties window, or by changing the job schedule entry via the character-based interface
5250. In the 5250 interface, you can run WRKJOBSCDE command or ADDJOBSCDE you can also use
SBMJOB with SCDDATE( ) SCDTIME( ).
To schedule a job using IBM® Navigator for i, use the following instructions:
• Expand Work Management > Job Queues > Active Job Queues or All Job Queues > The
job queue that contains your job.
• Right-click the job and click Properties.
• On the Job Properties window, click the Job Queues tab.
To schedule the job, use the options that are located under “When to make job available to run”.
The IBM Advanced Job Scheduler for i (5770-JS1) licensed program is a powerful scheduler that
allows unattended job processing 24 hours a day, 7 days a week. This scheduling tool provides
more calendar features and offers greater control over scheduled events than the base scheduler.
You can also view job completion history and manage notification of a job's status.

© Copyright IBM Corp. 2001, 2016 15-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Putting jobs on a job queue: Summary

ADDJOBSCDE QINTER Subsystem

Job Schedule Object

Interactive Jobs
entry . . . Workstation
entry . . .
Pool 2 *INTERACT
SBMJOB
Batch Jobs

JOBA Pool1
JOBB *BASE
JOBC

JOBQ

QSPL Subsystem

Writers
*SPOOL

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-6. Putting jobs on a job queue: Summary

On the diagram you can see the process of putting job to job queue.

© Copyright IBM Corp. 2001, 2016 15-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Tracking jobs
QINTER Subsystem
WRKJOBSCDE
Job Schedule Object Workstation
Interactive Jobs
entry . . .
entry . . . WRKJOB
WRKSBMJOB *INTERACT
WRKACTJOB Batch Jobs
WRKUSRJOB
WRKSBS *BASE
JOBA
JOBB
JOBC

JOBQ
WRKJOBQ

QSPL Subsystem

Writers
*SPOOL

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-7. Tracking jobs

There are a lot of commands to control the job. From commands like WRKJOBSCDE, which allows
you to prepare a job, through the command which allows you to control a job when it is running, to
the commands which help you control output.

© Copyright IBM Corp. 2001, 2016 15-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Spooling intercept

Program

Device File

QPRINT

Data
SPOOL(*YES) Spooling
Management
Intercept

QPRINT Print
Spooled Data
OUTQ File

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-8. Spooling intercept

Spooling functions are performed by the system without requiring any special operations by the
program that creates the output. When a program opens a printer file, the operating system
determines whether the output is to be spooled by looking at the printer file SPOOL parameter.
When a printer file specifying spooling is opened, the spooled file containing the output of the
program (data to be printed) is placed on the appropriate output queue in the system. A spooled file
can be made available for printing when the printer file is opened, when the printer file is closed, or
at the end of the job. This is done by specifying a particular value on the schedule parameter.
*IMMED makes the spooled file available to the writer as soon as the program is opened.
*FILEEND makes the spooled file available to the writer as soon as the file is closed. *JOBEND
makes the spooled file available to the writer as soon as the job is complete.
This process of spooling prevents a potential job limitation imposed by the availability or speed of
the printer devices. That is, the system can process application programs that generate printed
output much faster than printers can print the output.
By spooling (that is, sending the output to output queues to await printing), the system does not
have to wait until the printing for that application program is complete before it can start processing
the next application program.

© Copyright IBM Corp. 2001, 2016 15-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty
Spooling is especially important in a multiple-user environment where the number of jobs running
often exceeds the number of available printer devices. Using spooling, output can be easily
redirected from one output queue to another or from one printer to another.

© Copyright IBM Corp. 2001, 2016 15-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Printer device file

Program
Writes to file QPRINT

Device file from CRTPRTF command

QPRINT
QPRINT
SPOOL = (*YES)
OUTQ = (*JOB) OUTQ
FORMTYPE = (*STD)
COPIES = (1)
SCHEDULE = (*FILEEND)
SAVE = (*NO)
DEV = (*JOB)

More . . .

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-9. Printer device file

When spooled files are created, the spooled file name is typically the same as the name of the
printer file that was used to create it. For example, if the Print key is pressed, the spooled file is
called QSYSPRT because QSYSPRT is the printer file used by the Print key operation.
There are several ways in which the spooled file can have a different name:
1. The Override with Printer File (OVRPRTF) command was used and a name was specified in the
SPLFNAME parameter. For example, typing the following command:
OVRPRTF QSYSPRT SPLFNAME(REPORT1) causes the name of the spooled file to be
REPORT1 instead of QSYSPRT.
2. The OVRPRTF command was used and a different printer file is specified in the TOFILE
parameter. For example, typing the following command:
OVRPRTF QSYSPRT TOFILE(PRTF2) causes the spooled file to be called PRTF2 (the name
of the printer file specified in the TOFILE parameter of the OVRPRTF command).
Some IBM applications might create spooled files that have names different from the printer files
used to create them. Users have no control over spooled file names in this situation.

© Copyright IBM Corp. 2001, 2016 15-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Printer and output queue defaults (1 of 2)

Printer Device File
OUTQ (*JOB)
DEV (*JOB) At job initiation, this
Job Description search process
determines the default
OUTQ (*USRPRF)
PRTDEV (*USRPRF) output queue for the
job.
User Profile
OUTQ (*WRKSTN)
PRTDEV (*WRKSTN)

Device Description
PRTDEV (*SYSVAL)
OUTQ (*DEV)

System Value
QPRTDEV (PRTO1)

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-10. Printer and output queue defaults (1 of 2)

When a printer is configured to the system, the system automatically creates the printer's default
output queue in library QUSRSYS. The output queue is given a text description of 'Default output
queue for printer xxxxxxxxxx', where xxxxxxxxxx is the name assigned to the printer during
configuration. The printer name is specified in the device description (DEVD) parameter.
The AUT parameter for the output queue is assigned the same value as that specified by the AUT
parameter for the printer device description. All other parameters are assigned their default values.
Use the Change Command Default (CHGCMDDFT) command to change the default values used
when creating output queues with the CRTOUTQ command.
The default output queue for a printer is owned by the user who created the printer device
description. In the case of automatic configuration, both the printer and the output queue are owned
by the system profile QPGMR.
The system is shipped with the defaults set to use the default output queue for the system printer as
the default output queue for all spooled output. The system printer is defined by the Default printer
(QPRTDEV) system value.
When a spooled file is created by opening a printer file and the output queue specified for the file
cannot be found, the system attempts to place the spooled file on output queue QPRINT in library
QGPL. If for any reason the spooled file cannot be placed on output queue QPRINT, an error
message is sent and the output is not spooled.

© Copyright IBM Corp. 2001, 2016 15-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty
When job starts first will be taken defaults from printer file after from job description and user profile
and in the end from the device description and system value.

© Copyright IBM Corp. 2001, 2016 15-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Printer and output queue defaults (2 of 2)

QINTER Subsystem

Interactive Jobs
Workstation

*INTERACT

Batch Jobs

JOBA
*BASE QPRINT
JOBB
JOBC WRKOUTQ

OUTQ
WRKJOB
JOBQ
WRKSPLF
QSPL Subsystem
WRKSPLFA

Writers Spooled
*SPOOL Files

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-11. Printer and output queue defaults (2 of 2)

By default each job which want to print something sends data to default outq QPRINT. You can
control the whole process using these commands:
WRKJOB
WRKOUTQ
WRKSPLF
WRKSPLFA

© Copyright IBM Corp. 2001, 2016 15-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Spool writers
QINTER Subsystem

Interactive Jobs

*INTERACT

Batch Jobs QPRINT

*BASE OUTQ

Spooled
Files

QSPL Subsystem

WRKWTR
Writers
*SPOOL

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-12. Spool writers

The spooled file subsystem, QSPL, is used for processing the printer writer programs and must be
active when printer writer programs are active. The spooled file subsystem and the individual
printer writer programs can be controlled from jobs that run in other subsystems. The Start Printer
Writer (STRPRTWTR) command submits writer jobs to the job queue of the spooled file subsystem.
Requests for writer jobs are placed on the QSPL job queue, and the next entry on the QSPL job
queue is selected to run if:
• The number of active jobs is less than the QSPL subsystem attribute of MAXJOBS.
• The number of active jobs from the QSPL job queue is less than the MAXACT attribute for the
job queue.
A writer is an IBM i program that takes spooled files from an output queue and produces them on
an output device. The spooled files that have been placed on a particular output queue remain
stored in the system until a writer is started to the output queue.
The writer takes spooled files one at a time from the output queue, based on their priority. The
writer processes a spooled file only if its entry on the output queue indicates that it has a ready
(RDY) status. You can display the status of a particular spooled file using the Work with Output
Queue (WRKOUTQ) command.

© Copyright IBM Corp. 2001, 2016 15-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty
If the spooled file has a ready status, the writer takes the entry from the output queue and prints the
specified job or file separators or both, followed by the output data in the file. If the spooled file does
not have a ready status, the writer leaves the entry on the output queue and goes on to the next
entry. In most cases the writer continues to process spooled files (preceded by job and file
separators) until all files with a ready status have been taken from the output queue.
The AUTOEND parameter on the start writer commands determines whether the writer continues to
wait for new spooled files to become available to be written, end after processing one file, or end
after all spooled files that have a ready status have been taken from the output queue.

© Copyright IBM Corp. 2001, 2016 15-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Spooling summary
Job queues:
• Any number of job queues is allowed.
• Ordered by job queue sequence number.
• IBM shipped queues use sequence number.
• More than one job queue can be activated in a subsystem.
• Any job queue can be fed at any time.

Output queues:
• Any number of output queues is allowed.
• One output queue can be active to up to 10 printers at a given time.
• Any output queue can be fed at any time by any program executing in
the system.

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-13. Spooling summary

Job queues:
• Any number of job queues is allowed.
• Ordered by job queue sequence number.
• IBM shipped queues use sequence number.
• More than one job queue can be activated in a subsystem.
• Any job queue can be fed at any time.
Output queues:
• Any number of output queues is allowed.
• One output queue can be active to up to 10 printers at a given time.
• Any output queue can be fed at any time by any program executing in the system.

© Copyright IBM Corp. 2001, 2016 15-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Review questions
1. True or False: The submit job command is used to run an
interactive job.

2. Which of the following objects is checked first by work

management when the system is trying to determine where to
send your output?
a. User profile
b. System value
c. Printer device file
d. Job description

3. True or False: The submit job command allows you to specify

a schedule date and time for a job.

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-14. Review questions

© Copyright IBM Corp. 2001, 2016 15-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Review answers
1. True or False: The submit job command is used to run an
interactive job.
The answer is False.

2. Which of the following objects is checked first by work

management when the system is trying to determine where to
send your output?
a. User profile
b. System value
c. Printer device file
d. Job description
The answer is Printer device file.

3. True or False: The submit job command allows you to specify

a schedule date and time for a job.
The answer is True.

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-15. Review answers

© Copyright IBM Corp. 2001, 2016 15-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Exercise: Work management: Job and subsystem

management

• At the end of the exercise, you should be able to:

ƒ Use system commands to determine job status and job definition
ƒ Use system commands to locate and work with jobs on the system
ƒ Use system commands to determine the relationship between
active subsystems and allocated main storage
ƒ Use system commands to submit batch work to the system and
track it through completion

Systems to be used for class:

Name TCP/IP Address
Teach system __________ __________

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-16. Exercise: Work management: Job and subsystem management

© Copyright IBM Corp. 2001, 2016 15-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 15. Work management: Submitting and tracking of batch jobs

Uempty

Unit summary
• Describe what command is used to submit a job to run in batch mode
• Explain the process on the system when a job is submitted to run in
batch
• Explain how to schedule a batch job
• List and explain the commands you can use to track jobs on the system
• Explain how data management intercepts output generated by a
program
• Explain the function of a printer device file
• Explain the decision process used by the system to determine where to
send your output

Work management: Submitting and tracking of batch jobs © Copyright IBM Corporation 2001, 2016

Figure 15-17. Unit summary

© Copyright IBM Corp. 2001, 2016 15-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

Unit 16. Programming concepts

Estimated time
00:10

Overview
This unit is provided to teach the students how to write a simple Control Language (CL) program. In
this unit, we will discuss the concepts of programming.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 16-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

Unit objectives
• Discuss the concepts behind programming
• Explain the steps involved in creating a program

Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 16-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

The manual process

To back up a journal receiver, the following steps are required:

1. INZTAP Prepare the tape for the SAVOBJ

command.

2. CHGJRN Create a new journal receiver

and begin journaling to it.

3. SAVOBJ Save the detached journal

receiver.

4. DLTJRNRCV Delete the saved journal

receiver from the system.

Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-2. The manual process

You can create a program to perform the needed steps in the sequence you specify. The name of
the CL program will be MIDDAY.
Here is an example of a series of steps an operator would want to automate. You might never have
heard of journaling or of a journal receiver, but the steps will still look logical. Rather than going into
detail on each CL command concentrate on the process of grouping together a series of CL
commands that must be run each day.
Ask the instructor about explanation of a journal receiver as an object that holds a copy of each
record changed in a file. Journaling makes it possible to recover a file up to the last record
processed rather than to the last file backup. At noon, this company plans to set up a new receiver
for the afternoon work and to back up the receiver used in the morning.
These are a series of CL commands that a system operator enters on a daily basis to back up a
journal receiver in the middle of the day. The operator enters these same CL commands in the
same sequence every day. Wouldn't it be nice, then, to place those commands in a program that
executed the commands in the proper sequence?

© Copyright IBM Corp. 2001, 2016 16-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

The automated process: CL program

Instead of typing the four

INZTAP
commands, create a CL program.
CHGJRN
SAVOBJ
This program’s name is MIDDAY.
DLTJRNRCV

Program name = MIDDAY

Object type = *PGM Whenever you need to
execute the commands in
the program. You enter:
CALL MIDDAY

Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-3. The automated process: CL program

Because the commands are placed in a program called MIDDAY, operators now needs only to
CALL the MIDDAY program.
When they do this, the four commands will be executed in the correct sequence.

© Copyright IBM Corp. 2001, 2016 16-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

What is a program?

A program definition
is a sequence of
instructions that a
computer can
interpret and run.

Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-4. What is a program?

You might also add that the instructions should be organized in a detailed and logical sequence.
Next, we will look at the steps involved in creating a program.

© Copyright IBM Corp. 2001, 2016 16-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

Steps involved in creating a program

The basic steps are as follows:

1. Design a 2. Type it into 3. Change the

program. the system. program into a
form the
system can
use.

Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-5. Steps involved in creating a program

The steps to create a program are as follows:

1. Someone in the organization identifies the need for a program and the program is written.
2. The program, that is; its source code, is entered (keyed) into the system.
3. The source code is compiled and in the process is changed into an object type (either *PGM or
*MODULE) that the system can process.
Creating a CL program is easy.
• First, someone identifies an idea for a program and the program is written. During this step, as
the problem is analyzed, it might change.
▪ For example, a problem that first appeared simple can become complex. This will cause the
program to change.
• Second, the program is typed into the system by using a programming language.
• Third, after it is keyed into the system, it needs to be translated into something the system can
understand. Fourth, the program must be thoroughly tested.
In the original program model (OPM), output from the compiler is identified to the system as object
type *PGM. In the Integrated Language Environment (ILE), the output from the compiler is
identified to the system as object type *MODULE.

© Copyright IBM Corp. 2001, 2016 16-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

What is needed to create a program?

The following are needed to create a program:

Knowledge of a programming language

PDM and SEU: Traditional green screen tool

ƒ A compiler for the language in which your program is written

IBM Rational Developer for i - PC-based graphical tools

ƒ Includes the compilers

Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-6. What is needed to create a program?

The following are needed to create a program:

• Knowledge of a programming language. Here are a couple of examples:
▪ CL commands
▪ RPG
▪ COBOL
• SEU is the traditional tool used to create and change source and print members, and to copy
records into a member from another member or spooled file.
• IBM RD for i is a better toolset with more functions.
• A compiler for the language in which your program is written.
A compiler is a program that translates programming language into machine language that can
be used by the system.
IBM Rational Developer for i is an integrated development environment (IDE) built on the Eclipse
platform. Designed for creating and maintaining applications on IBM i systems, it resides on the
developer’s desktop, supporting development in both host-connected and disconnected modes.

© Copyright IBM Corp. 2001, 2016 16-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty
The three editions of IBM Rational Developer for i represent the evolutions of products previously
marketed under the following names: IBM Rational Developer for Power Systems Software RPG
and COBOL Tools for i, IBM Rational Developer for Power Systems Software Power Tools for i, and
IBM Rational Developer for i for SOA Construction.

© Copyright IBM Corp. 2001, 2016 16-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

Process for creating a CL program

1. Create a source physical file
QCLSRC

2. Add member and edit source Object Type

*FILE
3. Create program PGM
Member INZTAP . . .
CHGJRN . . .
MIDDAY SAVOBJ . . .
4. Call the program DLTJRNRCV . . .
ENDPGM

More source
members can be
added.
MIDDAY
Object Type
*PGM
Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-7. Process for creating a CL program

A source physical file contains the uncompiled program source statements. A source physical file
contains one or more source members. Each source member contains the source for one program
or object.
Generally, the source physical file name reflects the type of source that it contains. For example
QCLSRC for CL programs, QRPGSRC for RPG programs, QDDSSRC for a DDS file source, and
so on. You can have multiple QCLSRC files (in different libraries) each containing the source for CL
programs for one library or one application.

© Copyright IBM Corp. 2001, 2016 16-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

Review questions
1. True or False: Tasks or operations that are repetitive in
nature are prime candidates for a CL program.

2. True or False: Creating a CL program requires that you

know either RPG or COBOL.

3. True or False: You can only create one source physical file
on your system.

4. Which of the following source physical files is used to store

RPG programs?
A. QCLSRC
B. QCBLSRC
C. QRPGSRC
D. QDDSSRC

Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-8. Review questions

© Copyright IBM Corp. 2001, 2016 16-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

Review answers
1. True or False: Tasks or operations that are repetitive in
nature are prime candidates for a CL program.
The answer is True.

2. True or False: Creating a CL program requires that you know

either RPG or COBOL.
The answer is False.

3. True or False: You can only create one source physical file
on your system.
The answer is False.

4. Which of the following source physical files is used to store

RPG programs?
a. QCLSRC
b. QCBLSRC
c. QRPGSRC
d. QDDSSRC
The answer is QRPGSRC.
Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-9. Review answers

© Copyright IBM Corp. 2001, 2016 16-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 16. Programming concepts

Uempty

Unit summary
• Discuss the concepts behind programming
• Explain the steps involved in creating a program

Programming concepts © Copyright IBM Corporation 2001, 2016

Figure 16-10. Unit summary

© Copyright IBM Corp. 2001, 2016 16-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Unit 17. CL programming concepts

Estimated time
00:35

Overview
This unit is provided to teach the students how to write a simple Control Language (CL) program. In
this unit, we will discuss some of the basics of CL programming.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 17-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Unit objectives
• Discuss the basic statement required in a CL program
• Discuss the basic structure of a CL program
• Explain some of the basic coding rules for a CL program
• Explain how to communicate between a user and the CL program
• Explain how to set up prompting for some of the CL commands or
parameters

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 17-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

CL programs
• Are compiled into executable code
• Can control work flow
• Can perform logical operations
• Can communicate with the user
• Can allocate required resources

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-2. CL programs

A couple of facts about CL programs:

• Because they are compiled into executable code, they process faster than CL commands,
which are not compiled.
• They can control work flow and make logical decisions.
• They can communicate with users to inform them, or to acquire information that is needed.
• They can reserve resources so that they are available when they are actually needed.
There are several different types of programs.
• A control language (CL) program is a program that is created from source statements consisting
entirely of control language commands. IBM i supports two types of programs.
• An ILE program is a program written in an Integrated Language Environment (ILE)-conforming
high-level language. ILE programs are IBM I objects that contain one or more modules.
Modules cannot be run until they are bound into programs. These programs must have a
program entry procedure. The CL compiler generates a program entry procedure in each
module it creates. A single-module ILE program can be created using the Create Bound CL
Program (CRTBNDCL) command. The Create Program (CRTPGM) command can be used to
create an ILE program that contains module objects generated by different ILE compilers,
including ILE CL.

© Copyright IBM Corp. 2001, 2016 17-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty
• An OPM CL program is a program that conforms to the original program model (OPM). OPM CL
programs are objects that result from compiling source using the Create CL Program
(CRTCLPGM) command.

© Copyright IBM Corp. 2001, 2016 17-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Commands allowed in CL programs

• Thousands of CL commands are shipped with the system

• Most CL commands are allowed in CL programs

GOTO SAVLIB VRYCFG SAVOBJ

SNDMSG CHKOBJ STRPRTWTR DSPMSG

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-3. Commands allowed in CL programs

Thousands of CL commands are shipped as part of the base operating system and optionally
installable parts of the base operating system.
Other CL commands are shipped with licensed program products (LPPs). For example:
• The Start Performance Tools (STRPFRT) command is shipped with Performance Tools.
• The Work with Saved Objects Using BRM (WRKOBJBRM) command is shipped with Backup,
Recovery, and Media Services (BRMS).

© Copyright IBM Corp. 2001, 2016 17-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Some familiar CL programming commands

The following are examples of commands that can be used in CL
programming:
• CALL • SAVLIB
• CHKOBJ • SAVOBJ
• CHKTAP • SNDMSG
• CRTSAVF • SNDBRKMSG
• DSPMSG • STRPRTWTR
• RSTLIB • WRKOUTQ
• RSTOBJ • WRKWTR

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-4. Some familiar CL programming commands

You have probably used all of these commands by entering them on a command line or executing
them by using a menu option. All of these commands can be used in a CL program. In fact, most
other commands can be used in a CL program as well.
• CALL (Call Program) -SAVLIB (Save Library)
• CHKOBJ (Check Object) - SAVOBJ (Save Object)
• CHKTAP (Check Tape) - SNDMSG (Send Message)
• CRTSAVF (Create Save File) - SNDBRKMSG (Send Break Message)
• DSPMSG (Display Message) - STRPRTWTR (Start Print Writer)
• RSTLIB (Restore Library) - WRKOUTQ (Work Out Queue)
• RSTOBJ (Restore Object) - WRKWTR (Work Writer)

© Copyright IBM Corp. 2001, 2016 17-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

CL commands allowed only in CL programs

The following are commands that can only be used in CL
programming:

DO
PGM ENDDO
ENDPGM
IF
ELSE

GOTO
DCL Label

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-5. CL commands allowed only in CL programs

There are some CL commands which can only be executed from within a CL program. You might
not be familiar with these commands because they cannot be executed from a command line. This
visual shows some of these commands. Notice the grouping to used to indicate that these two
commands work in conjunction with each other.
• PGM (Program) ENDPGM (End Program)
• DCL (Declare Variable, File)
• IF (If) ELSE (Else)
• DO (Do) ENDDO (End Do)
• GOTO (Go To) Label

© Copyright IBM Corp. 2001, 2016 17-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Command format
SAVLIB + Command prompting

F4

Free format--keyword
SAVLIB LIB(AS2700) DEV(TAP01) ENDOPT(*UNLOAD)

Free format--positional
SAVLIB AS2700 TAP01 *UNLOAD SAVLIB LIB(AS2700)

Command name Keyword Value

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-6. Command format

There are three ways you can enter a command that is not part of a CL program:
Command Prompting
If you need help entering the parameters for a command, you can request that a display be shown
that is tailored to the command name. The display prompts for the parameters.
You can request command prompting either by pressing F4 after you type just the command name,
or you can type a question mark immediately preceding the command name and press Enter.
Free format method - Keyword format
In the keyword format method you enter the command name followed by a keyword followed by the
appropriate value for the keyword. You can enter the keywords in any order. You must be familiar
with the commands and their parameters to use this method.
Free format method - Positional format
This method requires that you be very familiar with the keywords and their parameters. In this
method, you enter the command name followed by the parameters in the exact order that IBM i
expects them to be. The order in which the values are entered is of utmost importance.

© Copyright IBM Corp. 2001, 2016 17-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Command format in a CL program

• Keyword
CLRLIB LIB(AS2700)

or

• Positional
CLRLIB AS2700

• Label
LABEL: CLRLIB LIB(AS2700)

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-7. Command format in a CL program

When you enter a command in a CL program, the command format is the same as when you enter
the command on a command line. One addition is that you can add is a label to allow you to identify
a command or a specific record within the program. This label can be used for branching when
using conditional logic.
The only addition to the format that the students already know is the optional LABEL: parameter.
• A label identifies the statement in the procedure to which processing is directed by the GOTO
command.
• To use a GOTO command, the command you are branching to must have a label.
• The label in this example is LABEL.
• A label can have as many as 10 characters and must be immediately followed by a colon, but
blanks can occur between the label and the command name.

© Copyright IBM Corp. 2001, 2016 17-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Coding rules for CL commands

Coding rules for CL commands
Name Definition Example
Blank Separates parts of a command SAVLIB LIB(AS2700) DEV(TAP01)
(command name, and its
parameters)

Parentheses ( ) Separate keywords and values SAVLIB LIB(AS2700) DEV(TAP01)

Slash / Connects parts of a qualified name WRKOBJ AS2700/MIDDAY

or path name or
'Dir1/Dir2/Dir3/ObjA'

Single apostrophe Indicates the beginning and end of a SNDMSG MSG ('Program completed') TOUSR(QPGMR)
' ' quoted character string (a constant)

Indicates the absence of a positional

*N parameter SAVLIB AS2703 TAP01 *N *N AS2700

IBM-defined values that have

Predefined values predefined uses in CL and are SAVLIB LIB(*ALLUSR) DEV(*SAVF)
reserved in OS/400. They begin
with an asterisk (*).

Contains one or more characters

Generic name that are the first group of characters SAVLIB LIB(AS27*) DEV(TAP01)
in the names of several objects. An
asterisk (*) means the following
characters can be anything.

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-8. Coding rules for CL commands

When typing in the entire command (that is, without prompting) there are certain rules that apply.
This visual shows some of these rules.
This visual shows coding rules with which you should be familiar.
Since most new operators enter command parameters via prompting, these rules might not be
familiar to you.

© Copyright IBM Corp. 2001, 2016 17-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Additional coding rules for CL commands

Additional coding rules for CL commands
Name Syntax Definition
Beginning and end /* */ Indicate the beginning and end of a comment line
comment

Variable name &xxx Used to store and update data and to receive parameters; it
must begin with an ampersand (&)

Colon : Ends a command label

Coding rules for CL programs in SEU

Name Syntax Definition
Plus sign or minus + When a command is longer than one record, indicates that a
sign - command is continued on the next record

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-9. Additional coding rules for CL commands

Here are some additional rules for coding CL programs.

• Comments should be used to document your program.
• Variables give you a great deal of flexibility. They will be covered in detail later in this unit.

© Copyright IBM Corp. 2001, 2016 17-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Example of coding rules

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-10. Example of coding rules

This example CL program shows:

• A comment
• Declaring a display file that has formats and variables
• IF conditional tests
• A label (START) which is used to control logical flow of the program (to reiteratively loop
through the program)

© Copyright IBM Corp. 2001, 2016 17-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

The structure of a CL program

Description Program statement
Start of program PGM (optional)
COPYRIGHT (optional)

Declare file and variables DCLF (maximum of five)

DCL
DCL

Program-level MONMSG
monitor messages MONMSG

IF
IBM commands ELSE

COMMAND
Command-level MONMSG
monitor messages MONMSG

and/or
User commands

End of program ENDPGM (optional)

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-11. The structure of a CL program

A CL program has a clear structure.

• It always begins with the Program (PGM) command and ends with the End Program (ENDPGM)
command.
• The declaration section (DCL or DCLF) allows you to set up variables for use within the body of
the program.
• It is followed by the CL commands that make up the program.
• It should always end with an End program (ENDPGM).

© Copyright IBM Corp. 2001, 2016 17-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Declare CL variable
DCL VAR(&NAME) TYPE( ) LEN( ) VALUE( )

TYPE( ) LEN( ) VALUE( )

*DEC default (15 5)

default (0)
(1 to 15 digits) max (15 9)

*INT or *UINT default (4)

default (0)
(2 or 4 bytes) max (4)

*CHAR default (32)

default ('b')
(1 to 9999 chars) max (9999)
default (1)
*LGL default ('0')
max (1)

Examples:

DCL &A *LGL VALUE('1')

DCL VAR(&B) TYPE(*CHAR) LEN(5) VALUE('ABCD')
DCL &C *DEC (6 2) 543.21
CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-12. Declare CL variable

Character variables are just one type of variable that you can declare. They are used to store and
update data within a program. Their value is assigned or changed while the program is running.
This visual shows the Declare (DCL) command parameters. Following is an explanation of these
parameters:
• VAR (Variable): Specifies the name of the CL variable being declared. The variable name must
begin with an ampersand (&).
• TYPE (Type): Specifies the type of variable. In the example shown on the visual you are
learning how to declare a character (*CHAR) variable.
• LEN (Length): Specifies the number of characters that the value in this CL variable can have.
The minimum, maximum and default values are shown on the visual.
• VALUE (Value): Specifies the initial value assigned to the CL variable when it is declared in the
program. If no value is specified, a character variable is set to blanks.
A character variable can be used to hold a user's response to an inquiry message so that it can be
tested. We will see this in the upcoming examples.

© Copyright IBM Corp. 2001, 2016 17-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

DCL examples

• DCL VAR(&WEEKEND) TYPE(*CHAR) LEN(8)

• DCL &X *CHAR 1 /* Y=YES, N=NO */

• DCL &FROM TYPE(*CHAR) LEN(6) VALUE('JAN')

• DCL &TO *CHAR LEN(6)

• DCL &FILNAM *CHAR VALUE(FILEA)

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-13. DCL examples

The DCL command must include:

• The variable name
• The type of variable
• The length of the variable data
• An initial or default value for the variable is optional
The following is an explanation of the DCL commands shown on the visual:
DCL VAR(&WEEKEND) TYPE(*CHAR) LEN(8)
This command declares a CL variable named &WEEKEND that contains a character value that is 8
characters in length. The initial value of &WEEKEND is blanks.
DCL &X *CHAR 1 /* Y=YES, N=NO */
This command declares a CL variable named &X that contains a character value that is one
character in length. The value for &X is Y or N.
DCL &FROM TYPE(*CHAR) LEN(6) VALUE('JAN')
This command declares a CL variable named *FROM that contains a character value that is 6
characters in length. The initial value for *FROM is JAN.

© Copyright IBM Corp. 2001, 2016 17-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty
DCL &TO *CHAR LEN(6)
This command declares a CL variable named &TO that contains a character value that is 6
characters in length. The initial value of &TO is blanks.
DCL &FILNAM *CHAR VALUE(FILEA)
This command declares a CL variable named FILNAM whose initial value is FILEA. Because the
value contains 5 characters, and the LEN parameter is not specified, the length of the variable is
also 5 characters.

© Copyright IBM Corp. 2001, 2016 17-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

What is the purpose of SNDUSRMSG?

Which library
do you want
to save?

Reply________

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-14. What is the purpose of SNDUSRMSG?

The Send User Message (SNDUSRMSG) command is used by a program to:

• Send a message to a message queue
• And optionally, receive a reply to that message
There is a need to communicate with an end user. One way to communicate with an end user is by
using the SNDUSRMSG (Send User Message) command. It can be used within a program to send a
message to a user and, for an inquiry message, receive the user's reply.

© Copyright IBM Corp. 2001, 2016 17-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

SNDUSRMSG parameters
MSG ('message-text')

VALUES *NONE
allowable-values (20-max)

DFT ('default-reply-value')

MSGTYPE *INQ
*INFO

TOUSR *SYSOPR
*REQUESTER
user-profile-name

TOMSGQ *
*SYSOPR
*EXT
message-queue-name

MSGRPY (&CL - variable-name)

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-15. SNDUSRMSG parameters

This is a partial list of the SNDUSRMSG command parameters:

• MSG: The message text enclosed in apostrophes.
• VALUES: A list of valid replies (maximum of 20) to an inquiry message sent by this command. If
the reply to the inquiry message does not match one of the specified values, an error message
is sent to the reply's sender and the inquiry message is sent again. This value is valid only when
a value is specified for the MSGRPY parameter. This parameter is valid only if MSGTYPE (*INQ)
is specified.
• DFT (Default reply): Specifies the value used as the reply to an inquiry message (sent by this
command) if the inquiry message is sent to a message queue that is in default delivery mode,
or if, for any other reason, the default reply is sent. The value specified here as the default reply
does not have to match an entry in the list of valid replies specified in the VALUES parameter.
• MSGTYPE (Message type): Specifies the type of message sent. Only inquiry and informational
messages can be specified.
• TOUSR (To user profile): Specifies that the message is sent to the message queue specified in
the user profile for the user named on this parameter. This parameter cannot be used if
TOMSGQ is specified.

© Copyright IBM Corp. 2001, 2016 17-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty
• TOMSGQ (To message queue): Specifies the qualified name of the message queue to which
the message is sent. If ‘*’ is specified for an interactive job, the message is sent to the external
message queue (*EXT), while for a batch job, the message is sent to the system operator's
message queue (QSYS/QSYSOPR).
• MSGRPY (Message reply): Specifies the CL character variable (of up to 132 characters) that
contains the reply received in response to an inquiry message. This parameter is valid only if
MSGTYPE(*INQ) is specified. If the reply is longer than the variable, it is truncated; if it shorter,
it is padded to the right with blanks.

© Copyright IBM Corp. 2001, 2016 17-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

SNDUSRMSG example

SNDUSRMSG

• MSG('WHICH LIBRARY DO YOU WANT TO SAVE?')

• VALUES(APLIB PAYROLL ORDENTRY)

• MSGRPY(&LIB)

Question: How and where is &LIB defined?

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-16. SNDUSRMSG example

This visual shows an example of the SNDUSRMSG command. Review the parameters that are used.
Ask which message queue will receive the message.
Ask how and where is &LIB defined.
• &LIB is defined in a Declare (DCL) command earlier in the CL program.

© Copyright IBM Corp. 2001, 2016 17-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Using SNDUSRMSG in CL program

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-17. Using SNDUSRMSG in CL program

Notice all the places where the variable name &LIB appears.
• First, it is declared (DCL).
• Then, it holds the reply to the message.
• Then, it is used to identify which library should be saved.
Notice that when a command is longer than one line you can use a plus sign (+) to indicate
continuation of the command on the next line.
This visual shows the SNDUSRMSG used in a CL program.
• This program sends a message to the user and tests for the user's reply.
• The reply is used to decide which library is to be saved.
• When the library is saved, a message is sent to the user that called the program.

© Copyright IBM Corp. 2001, 2016 17-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

GOTO and labels

The GOTO command allows unconditional branching

within the CL program.

PGM

GOTO CMDLBL(DAYEND)

DAYEND:

ENDPGM

Branching is to the label of another command.

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-18. GOTO and labels

The GOTO command allows unconditional branching within a CL program. The branching is always
to a LABEL.
After the branch to the labeled statement, processing begins at that statement and continues in
consecutive sequence. It does not return to the GOTO command unless specifically directed back by
another instruction.
The GOTO command has one parameter which contains the label of the statement branched to.
A label can have a maximum of 10 characters and must be immediately followed by a colon. Blanks
can occur between the label and command name.

© Copyright IBM Corp. 2001, 2016 17-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

If-Then ELSE (1 of 2)

relational
IF COND( or logical ) THEN (command)
expression

ELSE CMD (command)

THEN parameter or ELSE command

is optional

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-19. If-Then ELSE (1 of 2)

Examples:
IF COND(&X='Y') THEN(GOTO SAVEFILE)
IF COND(&YREND *NE '1231') THEN(GOTO MTHEND)
IF (&TIME>170000) RLSJOBQ NIGHTTIME
The IF command is used to state a condition that, if true, specifies some statement in the program
to run. The command includes an expression, which is tested (true or false), and a THEN parameter
that specifies the action to be taken if the expression is true. Following is the format of the
command:
IF COND(logical-expression) THEN(CL command)
The IF command allows conditional processing within CL programs. If the IF condition is true, the
CL command or group of commands specified within the THEN parameter is executed. If it is false,
the CL command or group of commands is not executed.
Review the examples of IF commands at the bottom of the visual. Both COND and THEN are
keywords on the command which can be omitted. The last example on the visual shows these
keywords omitted.
Embedded IF commands can be used in a CL program.

© Copyright IBM Corp. 2001, 2016 17-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

If-Then Else (2 of 2)
• ELSE CMD(CL-COMMAND)
ƒ Used with an IF command
ƒ Processed only if the preceding IF command is false
ƒ Examples

IF (&X='Y') (CALL WEEKEND)

ELSE CMD(CALL MONTHEND)

IF (&INZ='OK') (INZTAP TAP01 CHECK(*NO))

ELSE DO
CRTSAVF DLY01
SAVLIB XYZ *SAVF SAVF(DLY01)
CALL PROGA
ENDDO

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-20. If-Then Else (2 of 2)

The IF command can specify activity to be done if the condition is TRUE.

The ELSE command can be used with the IF command to specify a command or commands that
should be processed if the associated IF command is false.
Each ELSE command must have an associated IF command.
The real usefulness of the ELSE command is shown when it is combined with DO groups as shown
on the last example on the visual.
If processing is dependent on a condition being false, then use the ELSE command immediately
after an IF command (or ENDDO if DO was specified for the THEN parameter).
If more than one command needs to be processed for the false condition, the DO can be specified
with the ELSE command.
Nested IF commands can be used in a CL program.

© Copyright IBM Corp. 2001, 2016 17-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Relational and logical expressions

• Expression: (Operand Operator Operand)
• Result of a relational or logical expression: '1' True or '0' False
• Operands: Constant, Variable, and Another Expression
Operators Description
< *LT Less than
= *EQ Equal to
> *GT Greater than
<= *LE Less than or equal to
and *AND (&)
< *NL Not less than
> *NG Not greater than
or *OR (|)
>= *GE Greater than or equal to
= *NE Not equal to
& *AND True if both operands are '1'
| *OR True if both or either operand is '1'
*NOT
CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-21. Relational and logical expressions

The IF command uses these relational operators to make its comparisons. The relational operators
can become complex statements if they are linked by AND (*AND (&)) or *OR (|).
This visual shows the valid relational operators that can be used within an IF command. Review the
examples at the bottom of the visual. Notice the complex tests that can be performed.

© Copyright IBM Corp. 2001, 2016 17-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

DO / ENDDO
DO/ENDDO allows processing of multiple CL commands
if the logical expression of an IF* is true.

IF (&X='YES') THEN(DO)
CRTSAVF
SAVOBJ
ENDDO

*We will see later that DO/ENDDO can be associated with

additional commands.

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-22. DO / ENDDO

The DO command allows you to process a group of commands together. The group is all of the
commands between the DO command and the next ENDDO command.
Processing of the group of commands is usually conditioned on the evaluation of an associated
command, such as the IF command.
• If the evaluation of the command is true, then the DO group is processed.
• If the expression is not true, then processing starts after the ENDDO command.
Sometimes when a condition is true, you want to process more than one CL command.
• If so, then for the THEN parameter specify DO. The DO command says that if the condition is
true, process all the subsequent commands in sequence up to the ENDDO command.
• If, however, the condition is false, do not process the THEN command, but continue processing
at the statement following the ENDDO.
DO groups can be nested within other DO groups. There can be a maximum of 10 levels of nesting.

© Copyright IBM Corp. 2001, 2016 17-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Command prompting
?SNDMSG TOUSR(*SYSOPR)
? PRECEDING COMMAND CAUSES ENTIRE COMMAND TO BE PROMPTED

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-23. Command prompting

A question mark (?) preceding a command causes the entire command to be prompted at
execution time.
• All parameters will be displayed.
• Only parameters which do not have specified values can be entered.
F10 will allow the user to see and change the additional command parameters.
Within a CL program that is designed to run interactively, you can include simple command
prompting to enhance the flexibility of the program.
Using the question mark (?) character, you can control whether a prompt display is shown, as well
as control which fields of the prompt the user can modify. In effect, you are allowing the user of the
program to change the CL command as the program runs. The user will see the same prompted
command parameters that they would see when keying a command after pressing F4 (Prompt).
Prompting at execution time can be done in two ways.
• If the ? precedes the command name then all parameters will be prompted except those that
are specifically coded and these can not be changed. This gives your user great flexibility but
still allows you to control some of the parameters.
• To prevent a parameter from being changed, simply fix a value for it in the program.

© Copyright IBM Corp. 2001, 2016 17-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty
• If you do not want the user to see that parameter, put ?- immediately in front of its keyword.
If you want a more controlled prompting, where the user does not need to be prompted for every
parameter, then do not place the ? in front of the command. Instead, put it selectively in front of
keywords that need to be changed. The following visuals illustrate both methods.
This visual shows an example of command processing.
• Notice that TOUSR has a specified value so this parameter is protected on the display and
cannot be changed.
• Notice as well, that the user can press F10 to view additional parameters which can be
changed.

© Copyright IBM Corp. 2001, 2016 17-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Selective command prompting (1 of 2)

?SNDMSG ?-TOUSR(*SYSOPR)
?- preceding a parameter will omit that parameter from the display

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-24. Selective command prompting (1 of 2)

To omit parameters from the prompt display, use "?-".

The user can press F10 to view additional parameters, but the parameter marked with "?-" will not
be displayed.
"?-" preceding a parameter in a command that is being prompted means that the parameter will not
be displayed.
Notice again that the user is able to press F10 to see additional parameters. The only parameter
the user will not see is the coded parameter is the TOUSR parameter. This means that the user is
free to make this an informational or inquiry message, which is probably just what is needed.

© Copyright IBM Corp. 2001, 2016 17-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Selective command prompting (2 of 2)

Allows prompting and entering of selected parameters
Preceding parameter
?* Show parameter Cannot change parameter
?? Show parameter Can change parameter

SAVLIB ??LIB(APLIB) ?*DEV(TAP01) ENDOPT(*UNLOAD)

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-25. Selective command prompting (2 of 2)

Without the "?" in front of the command, only those parameters you mark with "?" or "??" will be
displayed. F10 is not available for the additional parameters. Therefore, all other parameters will
use the defaults.
Notice that in this example the "?" is not in front of the command.
• This is controlled prompting.
• The LIB parameter will be prompted and can be changed.
• The DEV parameter will be shown on the prompt screen but cannot be changed.
• The ENDOPT parameter has been coded with a value and will not be seen nor can it be
changed.
What is important is that the user will not be able to press F10 to get additional prompting for other
parameters. All other parameters will use the defaults.

© Copyright IBM Corp. 2001, 2016 17-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Whoops!

Does this look

familiar?
Would you like
to avoid this?

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-26. Whoops!

You can use the Monitor Message (MONMSG) command to:

• Intercept messages sent to the program
• Direct the program what to do next
There might be occasions when a CL program cannot successfully execute some or all of the
commands contained within the program. When this happens the program stops executing and a
program error, such as the one shown on the visual, will appear. The error message number is
shown on the display.
No matter how well designed and written a CL program is there will be times when a program
cannot execute all of the commands within the program. This results in a program error.
The MONMSG command allows the program to monitor for escape, notify, and status messages and
take responsibility for handling the situation. It cannot detect diagnostic or completion messages.

© Copyright IBM Corp. 2001, 2016 17-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

MONMSG example

Let us try to clear a save file that might or might not already exist. If
it does not exist, create it.

CLRSAVF FILE(APSAVF)
MONMSG MSGID(CPF9812) EXEC(CRTSAVF FILE(APSAVF))

MSGID CPF9812 File filename In library, library name not found.

For MSGIDs, see online help for each command.

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-27. MONMSG example

The MONMSG command has the following parameters:

• MSGID (Message ID): Specifies the message identifiers of up to 50 escape, notify, or status
messages you want to monitor for.
• CMPDTA (Compare Data): Specifies the comparison data that is used to determine whether the
monitored message (having one of the specified message identifiers) received on the program's
message queue is acted on by this command. The message data specified in the MSGDTA
parameter of the Send Program Message (SNDPGMMSG) command is compared with this
comparison data. If the first part (up through the first 28 characters, or less) of the message's
substitution values match the comparison data specified, the action specified in the EXEC
parameter of this command is taken. The action is also taken if no comparison data is specified.
• EXEC (Execute): Specifies the CL command (and its parameters) to be processed when a
monitored message sent to the program's message queue meets the conditions specified in
this command.

© Copyright IBM Corp. 2001, 2016 17-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

MONMSG: Monitoring for range of messages

• MONMSG MSGID(CPF0000)
ƒ Monitors for all messages beginning with ‘CPF’

• MONMSG MSGID(CPF3400)
ƒ Monitors for messages beginning with ‘CPF34’

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-28. MONMSG: Monitoring for range of messages

You can monitor for a range of messages, instead of for specific messages. This visual shows two
examples of monitoring for a range of messages.

© Copyright IBM Corp. 2001, 2016 17-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Example: Control work flow

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-29. Example: Control work flow

This program runs a typical series of commands that a system operator might have to perform:
1. First, it initializes a tape on device TAP01.
2. Then, it saves the libraries PAYROLL and APLIB to the device TAP01 and it unloads the tape.
3. Lastly, it calls the program PAYENDDAY.
Having these commands in a program ensures that no matter who runs the program for end of day,
the same commands are always run and in the correct order.
This and the next visual can be used to summarize the ideas taught in this unit.
This visual shows an example of a simple program an operator can run. Work flow is controlled by
the sequence of the CL commands.

© Copyright IBM Corp. 2001, 2016 17-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Example: Communicating with user

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-30. Example: Communicating with user

Adding the variable and the SNDUSRMSG command allows the program and the user to
communicate.
This program includes many of the programming techniques discussed in this unit.
The program will continue to loop and perform the INZTAP command until the user decides to stop.
After the tapes are initialized, the SAVLIB command executes and when it is done, a message is
sent to the workstation.

© Copyright IBM Corp. 2001, 2016 17-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Create a CL program using PDM and SEU

Enter
CL source

Syntax
Using RD for i checking
or SEU *FILE
QCLSRC
Listing
source
of source
file
code Create CL program
and errors CRTCLPGM
(Compile CL source) PROGA
PROGB
*PGM PROGC
Program
object
Test CL
program by
User steps executing
Data paths

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-31. Create a CL program using PDM and SEU

The command used to create the source physical file that will be used to store all CL programs is:
CRTSRCPF FILE(QCLSRC).
You enter the source code for a CL program by using Programming Development Manager (PDM)
and Source Entry Utility (SEU) or by using Rational Developer for i editor.

© Copyright IBM Corp. 2001, 2016 17-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Review questions
1. True or False: All CL commands are available to be used from a
command line or within a CL program.

2. In a CL program, a comment statement will always begin and end with

which of the following?
a. ( )
b. +
c. /* */
d. &

3. True or False: A CL program should always start with a PGM

command and end with an ENDPGM command.

4. Which of the following is used within a CL program to monitor for a

specific message?
a. MONITOR
b. PGMLST
c. MONMSG
d. SNDMSG
CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-32. Review questions

© Copyright IBM Corp. 2001, 2016 17-37

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Review answers
1. True or False: All CL commands are available to be used from a command line or
within a CL program.
The answer is False.

2. In a CL program, a comment statement will always begin and end with which of the
following?
a. ( )
b. +
c. /* */
d. &
The answer is /* */.

3. True or False: A CL program should always start with a PGM command and end with
an ENDPGM command.
The answer is True.

4. Which of the following is used within a CL program to monitor for a specific message?
a. MONITOR
b. PGMLST
c. MONMSG
d. SNDMSG
The answer is MONMSG.
CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-33. Review answers

© Copyright IBM Corp. 2001, 2016 17-38

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 17. CL programming concepts

Uempty

Unit summary
• Discuss the basic statement required in a CL program
• Discuss the basic structure of a CL program
• Explain some of the basic coding rules for a CL program
• Explain how to communicate between a user and the CL program
• Explain how to set up prompting for some of the CL commands or
parameters

CL programming concepts © Copyright IBM Corporation 2001, 2016

Figure 17-34. Unit summary

© Copyright IBM Corp. 2001, 2016 17-39

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Unit 18. CL programming using PDM and

SEU
Estimated time
00:20

Overview
This unit is provided to teach the students how to write a simple Control Language (CL) program. In
this unit, the students will learn how to use the traditional application development tools used from a
green screen 5250 emulation session. Specifically, you will be using Programming Development
Manager (PDM) and Source Entry Utility (SEU). The lecture materials will then be reinforced with a
lab exercise.

How you will check your progress

• Review questions
• Machine exercises

© Copyright IBM Corp. 2001, 2016 18-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Unit objectives
• Use PDM and SEU to create a CL program
• Use prompting for CL program statements
• Perform the steps to compile a CL program

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 18-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Programming Development Manager

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-2. Programming Development Manager

Programming Development Manager (PDM), Source Entry Utility (SEU) and Screen Design Aid
(SDA) are part of the IBM Application Development Tool Set (ADTS) for System i which is a
licensed program. Being a licensed program means this software might or might not be installed on
the customer system.
Rational Developer for i allows users to perform the same functions as in PDM, SEU, and SDA by
using a Windows interface.
The Start PDM (STRPDM) command starts the programming development manager. From the
Programming Development Manager (PDM) menu, you can work with libraries, objects,
members, and user-defined options.
Because source code is typed into members of a source physical file, select option 3 (Work with
members).
The role of PDM is to create a productive working environment. It does so by making it easy to use
the functions of the system while letting the user look at the objects and members in it.
Option 1 is for users looking for the ‘big picture’. Taking this option lets them see all or some of the
libraries. If users decide to choose this option, they will be able to save a whole library, delete a
whole library, and so on.

© Copyright IBM Corp. 2001, 2016 18-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty
Option 2 is for users who need to work with finished goods, the objects of the system. When this
option is chosen, users see the objects in a particular library and can save an individual object,
delete an object, and so forth.
Option 3 is for users interested in the development of source code. If they choose this option, they
are able to delete a source program, copy a source program, and so forth.
Option 9 is not covered in this unit. It allows users to add more functions to PDM.
Since we are going to enter a source program, let’s select option 3.

© Copyright IBM Corp. 2001, 2016 18-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Specify source file and library

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-3. Specify source file and library

On this page you will first need to specify the name of the library that contains the source file.
The second value to specify is the name of the source file where your program will be stored.
Optionally you can specify the name and type for a member that already exists. To display or make
changes.

© Copyright IBM Corp. 2001, 2016 18-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Work with Members screen

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-4. Work with Members screen

This screen will display the name of the source file and the name of the library where this file is
stored in the upper left of the screen.
The screen will display any members that already exist as well as the type of member. Even though
it is possible to store all different types of members within one source file, the standard is to create
a source specific to the type of members it will contain.
There are several options that can be performed against an existing member. Use the F23 key to
display additional options that can be performed.
Press the F6 = Create key to display the screen capture on the next page that is used to create a
new member.
This screen can be reached also using WRKMBRPDM command.

© Copyright IBM Corp. 2001, 2016 18-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Specify member name and type

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-5. Specify member name and type

On this page you will specify the name and type of member to be created.
The system will perform syntax checking based on the type of member specified on this page.
It is also recommended that you fill in something meaningful and descriptive every time that you
create a new member.

© Copyright IBM Corp. 2001, 2016 18-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Specify member entries and prompt

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-6. Specify member entries and prompt

On this screen you can either:

a. Enter and prompt one command at a time.
b. If you know all the CL commands that need to be entered, then you can enter all of them as
in the example.
Once a CL command has been entered then you can use the F4 prompt key on each line or
command so the system can assist with the parameters as displayed in the lower right part of the
display.

© Copyright IBM Corp. 2001, 2016 18-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Specify entries and exits

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-7. Specify entries and exits

After you enter all commands you can exit with save option. To do that press F3 key and press
Enter.

© Copyright IBM Corp. 2001, 2016 18-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Select compile options

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-8. Select compile options

To compile program type option 14 Compile next to member name and press F4 to see parameters
prompt screen. You can specify the name of the program (default is same as member name),
library where program will be created.
If you set Replace program * YES if program exist in library will be replaced.

© Copyright IBM Corp. 2001, 2016 18-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Reference materials

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-9. Reference materials

© Copyright IBM Corp. 2001, 2016 18-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

IBM Knowledge Center

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-10. IBM Knowledge Center

The website can be reached at the following address:

http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rbam6/rbam6clmain.htm

© Copyright IBM Corp. 2001, 2016 18-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Programming education (1 of 2)

Control Language Programming Workshop for IBM i

Course code: OL20G Skill level: Intermediate

Delivery type: Classroom Duration: 4.0 days

IBM i Programming Facilities Workshop

Course code: U5AS527G Skill level: Intermediate

Delivery type: Classroom Duration: 2.0 days

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-11. Programming education (1 of 2)

OL20G
Learn to write easy to use and efficient control language (CL) programs which can be used to
perform a variety of system and application control functions. You are taught to write basic and
intermediate level, interactive, and batch CL programs, user commands, and CL programs that
function as user tools (programs that use the output of display commands as input).
You will learn to write Control Language (CL) programs which can be used to perform a variety of
system and application control functions. You will be taught to write basic and intermediate level
interactive and batch CL programs as well as programs that function as user tools (programs that
use the output of display commands as input).
U5AS527G
Gain an introduction to IBM i features and programming facilities, including: Rational Developer for
IBM i (LPEX Editor, Remote Systems Explorer (RSE), Screen Designer and Report Designer
Programming Development Manager (PDM) Source Entry Utility (SEU) Control Language (CL)
Access for Windows and IBM i Navigator Interactive SQL Also covered, but with less emphasis:
Screen Design Aid (SDA) Data File Utility (DFU) Web Query/Query for IBM i Hands-on machine
exercises give you the opportunity to use and experiment with these facilities.

© Copyright IBM Corp. 2001, 2016 18-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Programming education (2 of 2)

RPG IV Programming Fundamentals Workshop for IBM i

Course code: Code AS06G Skill level: Intermediate

Delivery type: Classroom Duration: 4.0 days

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-12. Programming education (2 of 2)

AS06G
RPG IV Programming Fundamentals Workshop for IBM i (AS06G) teaches the basics of the IBM i
RPG IV programming language. It is the first of two courses that should be attended in sequence.
This course is a comprehensive exposure to the basic features and functions of RPG IV for Version
7. It does not introduce either information processing or programming in general. Students who are
new to programming should attend other courses that are offered by local technical colleges or
self-study methods.
This course is designed to enable a trained programmer to develop and maintain simple RPG IV
programs written using the latest features and techniques available in the Version 7 compiler.

© Copyright IBM Corp. 2001, 2016 18-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Review questions (1 of 2)
1. True or False: PDM, SEU and SDA are all part of the IBM
Application Development ToolSet (ADTS).

2. In order to key a new CL program, which of the following

PDM options is best?
a. Work with libraries
b. Work with objects
c. Work with members
d. Work with user-defined options

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-13. Review questions (1 of 2)

© Copyright IBM Corp. 2001, 2016 18-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Review answers (1 of 2)
1. True or False. PDM, SEU and SDA are all part of the IBM
Application Development ToolSet (ADTS).
The answer is True.

2. In order to key a new CL program, which of the following PDM

options is best?
a. Work with libraries
b. Work with objects
c. Work with members
d. Work with user-defined options
The answer is Work with members.

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-14. Review answers (1 of 2)

© Copyright IBM Corp. 2001, 2016 18-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Review questions (2 of 2)
3. True or False: PDM option 16 is used to compile a CL
program.

4. Which of the following function keys is used to create a new

member in your source file?
a. F5
b. F6
c. F10
d. F23

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-15. Review questions (2 of 2)

© Copyright IBM Corp. 2001, 2016 18-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Review answers (2of 2)

3. True or False: PDM option 16 is used to compile a CL
program.
The answer is false.

4. Which of the following function keys is used to create a new

member in your source file?
a. F5
b. F6
c. F10
d. F23
The answer is F6.

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-16. Review answers (2of 2)

© Copyright IBM Corp. 2001, 2016 18-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Exercise: CL programming using PDM and SEU

• At the end of the exercise, you should be able to:
ƒ Start Programming Development Manager (PDM)
ƒ Start and use Source Entry Utility (SEU)
ƒ Create a basic CL program
ƒ Perform the steps to compile a CL program

Systems to be used for class:

Name TCP/IP Address
Teach system __________ __________

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-17. Exercise: CL programming using PDM and SEU

© Copyright IBM Corp. 2001, 2016 18-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 18. CL programming using PDM and SEU

Uempty

Unit summary
• Use PDM and SEU to create a CL program
• Use prompting for CL program statements
• Perform the steps to compile a CL program

CL programming using PDM and SEU © Copyright IBM Corporation 2001, 2016

Figure 18-18. Unit summary

© Copyright IBM Corp. 2001, 2016 18-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Unit 19. Creating a menu using SDA

Estimated time
00:45

Overview
This unit will teach students how to create a menu using Screen Design Aid (SDA).

How you will check your progress

• Review questions
• Machine exercises

© Copyright IBM Corp. 2001, 2016 19-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Unit objectives
• Start SDA
• Explain the steps necessary to create a menu using SDA
• Explain the available options to customize your menu

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 19-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

SDA features
• SDA offers the following functionality:
• Design or modify displays which are used in high-level language
programs.
• Create or modify menus.
• Create or modify help information for displays and menus.
• Test displays without the need of the high-level program which uses it.
• With SDA you can develop menus and displays in an interactive
manner by answering questions:
ƒ Fill-in-the-blank
ƒ Yes/no

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-2. SDA features

SDA can be used to design:

• Screens which can be used with programs
• Menus
• Help screens for displays and menus
In this unit, we will concentrate only on menus. You start with a list of options to be included in a
menu. Each of these options runs a command or a CL program or an application program.
This visual shows all the functions that can be performed with SDA, including some of the
ease-of-use features. This topic only addresses menu creation.
Mention to the students that SDA is part of the IBM Application Development ToolSet (ADTS) for
System i which is a licensed program. This means that this licensed program can not be installed
on their system.
Mention Rational Developer for Power Systems Software with the screen Designer Tool is the GUI
tool that is available to design screens to be used with HLL (high-level language) programs. But
there really is no GUI tool available to design menus.
The presentation assumes that the students know what a menu is and how to execute a CL
command.
This sample menu, MYMENU, is the menu that will be created with SDA in the following visuals.

© Copyright IBM Corp. 2001, 2016 19-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Screen Design Aid menu

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-3. Screen Design Aid menu

The Start Screen Design Aid (STRSDA) command is used to start SDA.
SDA allows you to easily create menus to run commands or programs.
STRSDA begins an SDA session. To bypass this display, you could enter STRSDA 2.

© Copyright IBM Corp. 2001, 2016 19-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Design Menus display

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-4. Design Menus display

Just as with CL programs, the source for menus is stored in a source physical file.
Standard practice calls for a menu source file to be created for storing all menus created on a
system. The naming convention is for the menu source file to be name QMNUSRC. The command
used to create this source file is CRTSRCPF.
In the Menu field, enter the name for the menu that you will be creating.

© Copyright IBM Corp. 2001, 2016 19-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Specify Menu Functions display

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-5. Specify Menu Functions display

Make sure the Work with menu image and commands field is set to Y.
Notice also that you can design help for your menus.
Note the message at the bottom of the screen. SDA is now starting to create the menu MYMENU.

© Copyright IBM Corp. 2001, 2016 19-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (1 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-6. Define menu image work screen (1 of 10)

Type the text you want for your menu options directly onto this display.
Avoid using keys which delete and insert characters (field exit, insert and delete). Rather, use the
left, right, up, and down arrow keys (the cursor movement keys) to position the cursor. The reason
is that the data in the display is created like one long field, starting with row 1, column 1 and ending
with row 24, column 80.
This is the work screen. On this display you type what you want the menu to look like.

© Copyright IBM Corp. 2001, 2016 19-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (2 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-7. Define menu image work screen (2 of 10)

To delete something, type a “d” in the attribute byte (the byte preceding the text) and press Enter.
In the class example we will delete the title that is created by default to replace it with a different
title.

© Copyright IBM Corp. 2001, 2016 19-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (3 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-8. Define menu image work screen (3 of 10)

The text has been deleted.

© Copyright IBM Corp. 2001, 2016 19-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (4 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-9. Define menu image work screen (4 of 10)

When typing new text enclose phrases that are to be treated as a unit in quotation marks.
This makes moving and defining attributes simple.

© Copyright IBM Corp. 2001, 2016 19-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (5 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-10. Define menu image work screen (5 of 10)

When Enter is pressed, the quotation marks disappear. Now the entire string of text is treated as a
whole.

© Copyright IBM Corp. 2001, 2016 19-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (6 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-11. Define menu image work screen (6 of 10)

The text for the title should be centered, so type AC into the attribute byte and overlay the first
character of the field, General Backup Menu.
• Lines 1 through 20 are the menu body.
• When you create a new menu, the menu name and the title are on line 1.
• The menu outline on lines 3 to 18 are all SDA defaults. These can be changed or deleted.
• Lines 19 and 20 can be used if the display function keys prompt is set to *NO on the Create
Menu display.
• The first position (line 01, column 01) is reserved by SDA as an attribute position. You cannot
place anything in this position. To use special editing attributes or color attributes against a
constant on line 01, column 02, you must first shift the constant right.
Reposition fields on the work screen by using their attribute position.
The attribute position is the space directly in front of the field. Press F19 to go to the attribute
position of the previous field. Press F18 to go to the attribute position of the next field.

© Copyright IBM Corp. 2001, 2016 19-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty
Choose from the following methods and press Enter:
• Centering a field: Type AC in the attribute position of the field to move the field to the center of
the same row.
If a field starts and ends on different rows, then the field will be centered on the row where
the field starts.
• Moving a field -, =: Type - in the attribute position of the field and type = where you want the
field to appear.
• Copying a field -, ==: Type - in the attribute position of the field and type == where you want a
copy of the field to appear.
• Moving a block of fields -, -, =: Type - in the upper left corner of the block of fields. Type - in the
lower right corner of the block of fields so the - is one character beyond the longest field in the
block. Type = where you want the group of fields to be moved to.
If any fields partially or completely overlap, a field that overlaps is not moved.
• Copying a block of fields -, -,==: Type - in the upper left corner of the block of fields. Type - in
the lower right corner of the block of fields so the - is one character beyond the longest field in
the block. Type == where you want a copy of the group of fields to appear.
If any fields partially or completely overlap, a field that overlaps is not copied.
• Shifting a field <<<, >>>: Type <<< in the position preceding the field (the attribute byte of the
field), or type >>> after the field (over the ending attribute byte), to shift the field left or right as
far as the signs extend. You can type as many > or < as you want, and you can shift more than
one field at a time on the work screen.
• Shifting single- and multiple-choice selection fields: Single-choice and multiple-choice selection
fields occupy a rectangle on the work screen. The size of the rectangle is determined by the
length of the choice with the most characters and the last choice in the list. You can press F20
to make the rectangle visible. The ending attribute is in the lower right corner of the rectangle.
To shift all the fields within the rectangle to the right, type >>> over the ending attribute byte. To
shift all the fields within the rectangle to the left, type <<< in the position preceding the field (the
attribute byte of the field).

© Copyright IBM Corp. 2001, 2016 19-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (7 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-12. Define menu image work screen (7 of 10)

The text for the title should now be centered. Now you can further customize your menu.
Adding Constants
Surround a constant that contains blanks or special characters with single quotation marks to
define it as a single constant.
You can add or change constants in the menu body by using the following editing rules:
• Type a constant. A blank character ends the constant.
• Surround several constants with single quotation marks to redefine them as one constant.
• Use a double quotation mark to end one constant and start a new constant while taking up only
one position.
The original constant must be surrounded by single quotation marks.
• Type *DATE to create a field that shows the current session date.
• Type *TIME to create a field that shows the system time.
• To add the user name, type *USER. To add the system name, type *SYSNAME.
• Type +M(nn) to create a message constant field of length nn.

© Copyright IBM Corp. 2001, 2016 19-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty
You will be prompted for the message identifier and the message file from which the first nn
characters of test are to be extracted.
• Type a question mark (?) in the attribute position of the message constant to look at or change
the message identifier and the message file.
The following examples illustrate constant fields:
'xxx"yyY' Defines two constant fields.
'xxx yyy zzz' Combines three constant fields into one field.
+MMM or +(M3) The Define Message Constant display appears.

© Copyright IBM Corp. 2001, 2016 19-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (8 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-13. Define menu image work screen (8 of 10)

Notice that the date and time field have now been processed and this is the format that will be used
to display that data.

© Copyright IBM Corp. 2001, 2016 19-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (9 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-14. Define menu image work screen (9 of 10)

The next step is to type the text for each of the menu options. Note how each text option is
enclosed within quotes.
When done press Enter to see the screen on the next page.
This visual shows the completed work with menu display.
F20 on this display shows the full field length in reverse image, important if the field has beginning
or trailing blanks. You need to know where they are located if you need to delete or write over any
of the menu items.
It is time to enter the commands that the options will execute.
We will first work with F10 (Work with commands).

© Copyright IBM Corp. 2001, 2016 19-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Define menu image work screen (10 of 10)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-15. Define menu image work screen (10 of 10)

Notice the quotes are gone, each of the menu options is saved as a single text field. The text for
option 1 is one next field. The text for option 2 is another text field, and so on.
Once you are satisfied with the look of the menu, you can begin to add some personality or
character to the menu by further customizing it.
Adding or Removing Attributes and Colors
To add or remove display attributes or colors on the Design Image work screen, type one of
following commands in the position preceding the field (the attribute byte of the field).
You can use either uppercase or lowercase for your commands, but if your remove attribute
command is the same as the first letter of the field, your command must be in the opposite case. If,
for example, the field name is Allowance and you want to remove all its attributes, you should type
-a instead of -A in the attribute position.
Command Command
AddRemoveAttributeAddRemoveColor
H -H High intensityCB-CBBlue
R -R Reverse imageCG-CGGreen
S -S Column separatorsCP-CPPink

© Copyright IBM Corp. 2001, 2016 19-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty
B -B Blink CR -CR Red
N -N NondisplayCT -CT Turquoise
U -U UnderscoreCW-CW White
-A Remove all attributes-CARemove all colors
You can carry out the above operations by typing an asterisk (*) in the position preceding the field
(the attribute byte of the field), pressing Enter, and working with the field keyword displays that
appear.
The quotes are now gone. It is time to customize the menu by adding color or other attributes to the
menu text.
When you are done customizing the menu then press either
• The F10 = Work with commands key
• The F13 = command area key
To see the visual on the next page.

© Copyright IBM Corp. 2001, 2016 19-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

F10: Prompt for commands (1 of 2)

F4 = Prompt

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-16. F10: Prompt for commands (1 of 2)

Both prompting and help are available for command and/or parameters within SDA and works the
same as it does from the command line or within SEU for a CL program.
You can code up to 99 different options. Prompting is active in SDA while entering commands.

© Copyright IBM Corp. 2001, 2016 19-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

F10: Prompt for commands (2 of 2)

Page
Down

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-17. F10: Prompt for commands (2 of 2)

SDA will accept up to 99 command options.

When you are finished typing or prompting for commands, press Enter, then press F3.
This visual shows the commands for option 1, 2, 3, 5, 7, 9 and 10. You need to use the Page Down
(Roll Up) key to enter the commands for options 9 and 10.

© Copyright IBM Corp. 2001, 2016 19-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

F13: Command area

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-18. F13: Command area

The ‘F13 = Command area’ allows you to enter commands while viewing the menu options.
Commands are entered one at a time. Use the Page Up and Page Down keys to scroll through the
commands. You can enter a command and press F4 to prompt for the command. The F1 help key
is also available.
The Position to field positions you to the menu option you specify.
F13 returns you to the image display with the function key options again shown.
This visual shows a command in the command area.
The "??" works the same way as when it is in a CL program. That parameter will be prompted for
when option 1 is selected from the menu.
Show the students how the Page Up and Page Down and F4 (Prompt) keys work. To return from
the command area, press F13 again.

© Copyright IBM Corp. 2001, 2016 19-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Exit SDA and create menu (1 of 2)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-19. Exit SDA and create menu (1 of 2)

Press F3 to exit SDA and the Specify Menu Functions display appears.
You can return to the menu work display or work with menu help, if necessary.
Press F3 to continue exiting SDA.

© Copyright IBM Corp. 2001, 2016 19-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Exit SDA and create menu (2 of 2)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-20. Exit SDA and create menu (2 of 2)

The Exit SDA Menus display appears. Here you are promoted for whether the source should be
saved and if you want to create (compile) the menu objects.
Note the two members shown at the upper right of this display.
• DDS member, MYMENU, is where the image or the display screen source is stored. When it is
compiled it produces an object type *DSPF.
• Commands member MYMENUQQ is where the commands are stored. Once it is compiled it is
an object type *MSGF.
Verify the library where the source is to be stored as well as the library where compiled object is to
be stored.
Press Enter to finish creating your menu.
This visual shows the Exit SDA Menus display. Do not forget to add text.
• Point out the DDS member MYMENU (executable object, type *DSPF).
• The commands member MYMENUQQ (executable object, type *MSGF).

© Copyright IBM Corp. 2001, 2016 19-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Notice message

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-21. Notice message

Use the F3 = Exit to return to the initial SDA menu.

Pressing F3 one more time will return you to where you were when you entered the STRSDA
command.

© Copyright IBM Corp. 2001, 2016 19-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Sample menu

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-22. Sample menu

To display the menu you just created GO AS2700/MYMENU.

This visual shows the sample menu, MYMENU.

© Copyright IBM Corp. 2001, 2016 19-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Additional options when creating menu

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-23. Additional options when creating menu

The Prompt for parameters field on the Exit SDA menus display allows you to make some other
decisions about how your menu will appear and run when you change the ‘N’ to ‘Y’.
Change this parameter to Y to see the screen on the next page.
Resume visual presentation here. Some additional options when creating a menu.

© Copyright IBM Corp. 2001, 2016 19-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Prompted parameters

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-24. Prompted parameters

Here you can determine whether you want the users of the menu to have access to a command
line (Command line parameter) or function keys (Display function keys parameter). Function keys
(F keys) are active even if their description does not appear in the display.

© Copyright IBM Corp. 2001, 2016 19-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Command line

*LONG
===> __________________________________________________________
_______________________________________________________________
F3=Exit F4=Prompt F9=Retrieve F12=Cancel
F13=Information Assistant F16=AS/400 main menu

*SHORT
Selection or command
===> __________________________________________________________
F3=Exit F4=Prompt F9=Retrieve F12=Cancel
F13=Information Assistant F16=AS/400 main menu

*NONE
Selection or command
____
F3=Exit F12=Cancel
F13=Information Assistant F16=AS/400 main menu

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-25. Command line

*Long: 153 bytes

*Short: 73 bytes
*None: 4 - byte option field

© Copyright IBM Corp. 2001, 2016 19-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Delete menu and all associated objects

• Delete menu object/reference objects
ƒ DLTMNU MENU(LIBRARY/NAME) DLTREFOBJ(*DSPF *MSGF)

• Delete two source members

ƒ RMVM FILE(LIBRARY/SOURCE-FILE) MBR(MENU-NAME)
ƒ RMVM FILE(LIBRARY/SOURCE-FILE) MBR(MENU-NAMEQQ)

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-26. Delete menu and all associated objects

To completely delete all parts of a menu including the source, delete the menu object by name and
its reference objects, a *DSPF and a *MSGF. From the source file QMNUSRC, you remove two
members: one with the menu name and another with the menu name and 'QQ' appended.

© Copyright IBM Corp. 2001, 2016 19-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Review questions (1 of 2)
1. True or False: The tool used to create a menu is Menu
Design Aid.

2. Which of the following source physical files is the file

traditionally used to save menu objects?
a. QRPGSRC
b. QCLSRC
c. QMNUSRC
d. QCBLSRC

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-27. Review questions (1 of 2)

© Copyright IBM Corp. 2001, 2016 19-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Review answers (1 of 2)
1. True or False: The tool used to create a menu is Menu
Design Aid.
The answer is False.

2. Which of the following source physical files is the file

traditionally used to save menu objects?
a. QRPGSRC
b. QCLSRC
c. QMNUSRC
d. QCBLSRC
The answer is QMNUSRC.

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-28. Review answers (1 of 2)

© Copyright IBM Corp. 2001, 2016 19-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Review questions (2 of 2)
3. True or False: Command prompting is available when
entering commands in an SDA menu.

4. Which of the following attributes is used to center text in

SDA?
a. CB
b. H
c. R
d. AC

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-29. Review questions (2 of 2)

© Copyright IBM Corp. 2001, 2016 19-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Review answers (2 of 2)
3. True or False. Command prompting is available when
entering commands in an SDA menu.
The answer is True.

4. Which of the following attributes is used to center text in

SDA?
a. CB
b. H
c. R
d. AC
The answer is AC.

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-30. Review answers (2 of 2)

© Copyright IBM Corp. 2001, 2016 19-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Exercise: Creating a menu using SDA

• At the end of the exercise, you should be able to:
ƒ Start SDA
ƒ Perform the steps to create a menu using SDA
ƒ Create a menu that runs commands and CL programs
ƒ Customize your menu

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-31. Exercise: Creating a menu using SDA

© Copyright IBM Corp. 2001, 2016 19-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 19. Creating a menu using SDA

Uempty

Unit summary
• Start SDA
• Explain the steps necessary to create a menu using SDA
• Explain the available options to customize your menu

Creating a menu using SDA © Copyright IBM Corporation 2001, 2016

Figure 19-32. Unit summary

© Copyright IBM Corp. 2001, 2016 19-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Unit 20. Tips for improved operation

Estimated time
01:30

Overview
This unit will cover ways to change defaults, make the system easier for the users, and make
operations more streamlined for the system operator and otherwise improve system operations.

How you will check your progress

• Review questions
• Machine exercises

© Copyright IBM Corp. 2001, 2016 20-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Unit objectives
• Create a user-defined proxy command
• Change how a command is used
• Permanently change a command's defaults
• Explain how to use the System Reply List to automatically reply to
messages
• Explain how to leave a job temporarily through the attention key or how
to disconnect a job
• Use printers efficiently through printer load balancing
• Describe the process of creating a virtual optical device to use when
performing a software upgrade or installing PTFs
• Describe how perform FTP transfer included batch mode
• Explain some SST/DST function to diagnostic problems

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-1. Unit objectives

The tools that will be covered in this unit to achieve these objectives are:
• CRTPRXCMD: Create proxy (shortcuts) to target commands
• CHGCMD: Change how a command is used
• CHGCMDDFT: Permanently change a command's defaults
• System Reply List: Use the System Reply List to reply to messages
• QUSRTOOL: Tools available from QUSRTOOL library
• Set Attention Program: How to leave a job temporarily
• DSCJOB: How to disconnect a job
• CRTDEVOPT: Create virtual optical device as a tool to upgrade software or install PTF’s that
were downloaded electronically
• Printer Load Balancing: Using printers more efficiently

© Copyright IBM Corp. 2001, 2016 20-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Topic 1: Proxy commands,

using CHGCMD and
CHGCMDDFT

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-2. Topic 1: Proxy commands, using CHGCMD and CHGCMDDFT

© Copyright IBM Corp. 2001, 2016 20-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Proxy commands
• Instead of duplicating a command, you can now create a shortcut to a
target command:
ƒ Use the Create Proxy Command (CRTPRXCMD) to create the proxy.
ƒ Requires a command name (the new proxy command) and a target
command (the original command)
ƒ Optional parameters include a text description (TEXT), authority (AUT), and a
replace command (REPLACE) option.
• Specifying a proxy command for the TGTCMD parameter is allowed.
• When creating a proxy command, you do not specify the command
definition source.
• Does not contain any parameter information, prompt control
information, or interparameter dependency information.
• Use Display Command (DSPCMD) to determine whether a command is a
proxy or if it is an original command.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-3. Proxy commands

Proxy commands are used to create shortcuts to target commands. A proxy command differs from
a typical IBM i command in its ability to run a target command, rather than a command processing
program.
• Use the Create Proxy Command (CRTPRXCMD) to create a proxy command.
• Create Proxy Command (CRTPRXCMD) requires a Command name (CMD) and a Target
command (TGTCMD).
• Optional parameters include a Text description (TEXT), Authority (AUT) and a Replace
command (REPLACE) option. For example, to create a proxy command that has a target
command of QSYS/DSPJOB, enter the following command:
▪CRTPRXCMD CMD(MYLIB/PCMD1) TGTCMD(QSYS/DSPJOB) TEXT(‘dspjob proxy’)
• Specifying a proxy command for the TGTCMD parameter is allowed.
▪ A proxy “chain” can be up to 5 proxy commands in length, ending with a 6th non-proxy
command.
▪ Running a proxy command with a chain of more than 5 proxy commands will cause a
CPD0196 error “Number of chained proxy commands exceeds 5.”
• When you create a proxy command, you do not specify command definition source.

© Copyright IBM Corp. 2001, 2016 20-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
• A proxy command does not contain any parameter information, prompt control information, or
interparameter dependency information. When a proxy command is used, all of that information
is inherited from the target command defined in the proxy command. You specify all the same
parameters for the proxy command that you would for the target command.
Use the Change Proxy Command (CHGPRXCMD) command to change a proxy command or the
Delete Command (DLTCMD) command to delete a proxy command.
To run or process a command that is “resolved to” using a proxy chain, the user must have the
correct authority for that command and library, as well as *USE authority for each of the proxy
commands (and libraries) in the chain.
Determine whether the QSYS command is a proxy command. You can do this interactively using
the Display Command (DSPCMD) command or programmatically by using the Retrieve Command
Information (QCDRCMDI) API.
Since proxy commands run other commands, attempting to register an exit program for a proxy
command is not allowed, and will cause the error message CPF019A to be issued. When a proxy
command is run, and the non-proxy command that it resolves to has a registered exit program, the
proxy chain that was followed will be placed in the RTVC0100 or CHGC0100 returned format data.

© Copyright IBM Corp. 2001, 2016 20-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

IBM commands and LPP commands

• IBM OS commands are stored in the QSYS library.
• Some LPPs include their own commands:
ƒ A proxy command is created in QSYS pointing to the target command in the
LPP library.
• The system uses the security in place for the LPP (the target) command
when you prompt or run the proxy command:
ƒ Running CHGCMD or CHGCMDDFT to a proxy will alter the original command.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-4. IBM commands and LPP commands

The command (*CMD) objects of most licensed program products (LPPs) and all options of IBM i
that ship commands in a product library (other than QSYS) are copied to the QSYS library when the
LPP or OS option is installed.
Proxy commands are created in the system library QSYS. A proxy command is a *CMD object that
points to a target command. When the proxy *CMD is prompted or run, the operating system uses
the target command.
Attempts to prompt or run the proxy command in QSYS will check the authority of the target
command in the product library. Therefore, you should grant private authorities for the command
only to the regular command in the product library.
Some of the IBM commands in QSYS could be proxy commands. If you duplicate any of these
commands from QSYS into another library by using the Create Duplicate Object (CRTDUPOBJ)
command, your duplicate commands might be proxy commands.
When using the CHGCMD and CHGCMDDFT on a proxy command, the actual command changed will
be the command that is the target of the proxy. For LPP proxy commands in QSYS, if you change
the proxy command by using CHGCMD or CHGCMDDFT, you will change the target command in the
LPP library.

© Copyright IBM Corp. 2001, 2016 20-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
If you want CHGCMDDFT and CHGCMD to affect only the duplicate that you create, then do the
following:
• Determine whether the QSYS command is a proxy command. You can do this interactively using
the Display Command (DSPCMD) command or programmatically by using the Retrieve
Command Information (QCDRCMDI) API.
▪ If it is not a proxy command, use CRTDUPOBJ to duplicate it.
▪ If it is proxy command, use DSPCMD or QCDRCMDI to determine the target of the proxy
command, and duplicate the target command instead of duplicating the proxy command in
QSYS.
If an exit program had been previously registered for the copy of a licensed program command in
the QSYS library, the exit program will not be run for the proxy command that replaced it when. You
will need to register your exit program against the original command in the product library. For
example, if you had an exit program registered for the QIBM_QCA_CHG_COMMAND exit point for
the Create SQL ILE RPG Object (CRTSQLRPGI) command in QSYS, you will need to register your
exit program for the original command in the QSQL library.

© Copyright IBM Corp. 2001, 2016 20-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Change command: CHGCMD

Why?
Memory

Interactive Prog1

Create a program
interactively

Interactive Prog2

Waiting for memory

Interactive
Prog3
Prog4
Prog5

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-5. Change command: CHGCMD

Would not it be nice to keep users from disrupting the system by running interactive jobs that
should only be run in batch? Operations like compilations that run interactively and intensive
queries can negatively affect the response time of true interactive jobs.
The Change Command (CHGCMD) can be used to change the attributes of a command. It can be
used to specify for example:
• In what environments the command can be processed
• What current library and product library should be used when the command is executed
The user must have object management authority for the command that is being changed.
Although this example deals with specifying the operating environment, other parameters of
CHGCMD include:
• The mode: production, debug, or service
• The current library
• The product library
• Whether to allow limited capability users to run
• The help panel group

© Copyright IBM Corp. 2001, 2016 20-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
Remember in the work management topic how interactive jobs (or threads) shared memory
(paging)? Does a batch job ever reach a point where it can go into a long wait? Probably not. A
batch job does not share memory fairly with interactive jobs. Look at the jobs in the queue waiting
for memory. Ask how the additional wait time for the interactive jobs affects their response time.

© Copyright IBM Corp. 2001, 2016 20-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

CHGCMD: Where allowed to run parameter

ALLOW

• Specifies where the command can be processed.

(Some choices)
*ALL In a batch input stream, in a CL program, in a REXX
procedure, in a CL ILE module, or when processed
interactively. Can also be passed to system program
QCMDEXC (or QCAEXEC) for processing.
*BATCH In a batch input stream, external to a compiled CL
program.
*INTERACT Interactively, external to a compiled CL program.
*BPGM In a compiled CL program that is called from batch
entry.
*IPGM In a compiled CL program that is called from an
interactive entry.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-6. CHGCMD: Where allowed to run parameter

Other options include:

• *BREXX: The REXX procedure runs in a batch job.
• *IREXX: The command can be used in a REXX procedure run in an interactive job.
• *EXEC: The command can be used as a parameter on the CALL command and be passed as a
character string to the system program QCMDEXC (or QCAEXEC) for processing. If *EXEC is
specified, either *BATCH or *INTERACT must also be specified.
• *BMOD: The command can be used in a batch CL ILE program only.
• *IMOD: The command can be used in an interactive CL ILE program only.
• *SAME: The environment does not change.
You can change a command with the CHGCMD command and only allow it to process under certain
situations.
All of the available options for this parameter are listed on this page. They begin and in visual and
continue in the student notes.
Verify that you are making changes to an ‘original’ command. If you make a change to a proxy
command, then the original command is what will be changed.

© Copyright IBM Corp. 2001, 2016 20-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Which commands should be changed

• Commands that create programs should not be run
interactively:

CHGCMD CMD(CRTxxxPGM) ALLOW(*BATCH *BPGM)

CBL
CL
DFU
JVA
RPG
And so on…

• Commands that create files or commands should not

be run interactively:
CRTLF
CRTPF
CHGCMD CMD CRTPRTF ALLOW(*BATCH *BPGM)
CRTDSPF
CRTCMD
Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-7. Which commands should be changed

The Change Command (CHGCMD) command changes the attributes of a command definition. This
command gives you the ability to specify a different command processing program to process the
command. You can also change the type of operating environment (production, debug, or service)
in which the command can be processed, and the text description of the command. CL programs
that use the command being changed by the Change Command (CHGCMD) command do not
have to be created again. The Change Command (CHGCMD) command does not change the
parameter descriptions or validity checking information in the command definition object.
Listed in the visual are some of the create program commands, those commands that compile a
program, which you might not want to allow to run interactively on your system. Any of the
commands that are used to compile programs or any commands that are used to run batch type
programs are prime candidates to be changed. All of these commands should be changed so that
they cannot be run interactively.
Any other commands that create objects on your system while probably not as resource intensive
as the program compile commands should also run in batch mode.
Verify that you are making changes to an ‘original’ command. If you make a change to a proxy
command, then the original command is what will be changed.

© Copyright IBM Corp. 2001, 2016 20-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Change command defaults: CHGCMDDFT

SAVLIB LIB( ) SAVOBJ OBJ( )

DEV( ) LIB( )
DEV( )

PRECHK(*NO)
ACCPTH(*SYSVAL) PRECHK(*NO)
ACCPTH(*SYSVAL)

Make an educated decision on what the defaults should be for:

PRECHK
ACCPTH

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-8. Change command defaults: CHGCMDDFT

CHGCMDDFT permanently changes the default value of a command parameter. Requirements:

• The parameter must have an existing default value.
• The new default value must be valid for the parameter.
Object pre-check (PRECHK) - Specifies whether the save operation for a library ends if any of the
following are true:
• The objects do not exist
• The library or the objects were previously found to be damaged
• The library or the objects are locked by another job
• The requester of the save operation does not have authority for the library or to save the
objects.
The valid values that can be specified for this parameter are:
• *NO - The save operation for a library continues, saving only those objects that can be saved.
• *YES - If, after all specified objects are checked, one or more objects cannot be saved, the save
operation for a library ends before any data is written. If multiple libraries are specified, the save
operation continues with the next library.

© Copyright IBM Corp. 2001, 2016 20-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
Save access paths (ACCPTH) - Specifies whether the logical file access paths that are dependent
on the physical files being saved are also saved. The access paths are saved only in the case of
the following:
• All members on which the access paths are built are included in this save operation.
• The access paths are not invalid or damaged at the time of the save.
The system checks to ensure the integrity of the access paths. Any discrepancies found by the
system will result in the access paths being rebuilt.
The valid values that can be specified for this parameter are:
• *SYSVAL - The QSAVACCPTH system value determines whether to save the logical file access
paths that are dependent on the physical files that are being saved.
• *NO - Only those objects specified on the command are saved. No logical file access paths are
saved.
• *YES - The specified physical files and all eligible logical file access paths over them are saved.
QSAVACCPTH - Help
System Value QSAVACCPTH - Save access paths. This system value specifies whether the logical
file access paths that are dependent on the physical files being saved are also saved when
ACCPTH(*SYSVAL) is specified on a save command. A change to this system value takes effect at
the start of the next save operation. The shipped value is 1 = Save access paths.
The defaults for the parameters (prechk and accpth) is what is displayed on the visual.
Saving Access Paths
• The default for this parameter is to use the QSAVACCPTH system value. If this system value is
set to YES, then all access paths on the system will be saved.
• The alternative is to control this at the command level. If the system value is set to NO, then at
run time you can determine whether you want to save access paths or not. This will put both the
control and the responsibility in the operators hands!
Verify that you are making changes to an ‘original’ command. If you make a change to a proxy
command, then the original command is what will be changed.

© Copyright IBM Corp. 2001, 2016 20-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Changing an IBM-supplied command

• Recommendations for changing an IBM-supplied command:
ƒ Do not change the original command.
ƒ Verify that you are copying the original not a proxy.
ƒ Use CRTDUPOBJ to create a duplicate of the command in a user library
í CRTDUPOBJ OBJ (command) FROMLIB (QSYS) OBJTYPE (*CMD) TOLIB (user
library)
ƒ Change the command by using CHGCMD or CHGCMDDFT.
ƒ Test.
ƒ Change the system portion of the library list to move the user library before
QSYS.
í CHGSYSLIBL USRQSYS
í CHGSYSVAL QSYSLIBL ('USRQSYS QSYS...')

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-9. Changing an IBM-supplied command

It is recommended that you do not change the original IBM-supplied command. Instead, duplicate it
and change your copy.
The format of the command is as follows:
CHGCMDDFT CMD(LIBRARY/COMMAND) NEWDFT('PARAMETER(NEW DEFAULT)')
The following is an example of two ways to run CHGCMDDFT for multiple parameters in the same
command. You could run the command twice to change the two defaults:
CHGCMDDFT CMD(USRQSYS/SAVLIB) NEWDFT('PRECHK(*YES)')
CHGCMDDFT CMD(USRQSYS/SAVLIB) NEWDFT('ACCPTH(*YES)')
Or you could combine these two commands into a single command:
CHGCMDDFT CMD(USRQSYS/SAVOBJ) NEWDFT('PRECHK(*YES) ACCPTH(*YES)')
Some OS functions that use IBM commands can specify a library in which to locate the command,
rather than the library list.

© Copyright IBM Corp. 2001, 2016 20-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Example of a CL program to change commands

PGM

DLTCMD USRQSYS/SIGNOFF

CRTDUPOBJ OBJ(SIGNOFF) FROMLIB(QSYS) OBJTYPE(*CMD) +

TOLIB(USRQSYS)

CHGCMDDFT CMD(USRQSYS/SIGNOFF) NEWDFT('LOG(*LIST)')

Repeat DLTCMD, CRTDUPOBJ and CHGCMDDFT for each command you want
changed

ENDPGM

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-10. Example of a CL program to change commands

When installing a new release of a licensed program, the system will replace all IBM-supplied
commands. A new release might cause changed commands not to function properly.
We suggest by using a CL program to change IBM-supplied commands. This will allow you to
recreate the changed commands after installing a new version or a new release of the OS.
This technique applies to commands changed by using the CHGCMD / CHGCMDFT commands as
well as changes made to other system objects, such as subsystem descriptions and job
descriptions. A CL program allows you to track the changes and recreate them after installing the
new release.
Why is it important to keep track of changes made to IBM-supplied commands?
All changes will be made to an ‘original’ command and not to a proxy.
In this case we are creating duplicate commands to keep a copy of the original command (with its
original settings) on the system as a backup. Users will be instructed to use the new duplicated,
customized command.
Because new releases replace the IBM commands, you might want to make your changes to the
commands via a program. Then when installing a new release on the system, you will only need to
rerun the program to recreate the commands.

© Copyright IBM Corp. 2001, 2016 20-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Topic 2: System Reply List

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-11. Topic 2: System Reply List

© Copyright IBM Corp. 2001, 2016 20-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

What is the System Reply List?

This is a system-wide list of

replies that can be
automatically sent in response
to inquiry messages.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-12. What is the System Reply List?

There is one System Reply List on the system.

© Copyright IBM Corp. 2001, 2016 20-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

How the System Reply List works

DSP25 QSYSOPR
SEND *INQ
MESSAGE ABC1234
TO SYSTEM OPERATOR'S 1 MESSAGE ABC1234

MESSAGE QUEUE
REPLY: RIGHT

INQMSGRPY(*SYSRPYL)

3
REPLY *MSGQ 2
System Reply List
MESSAGE ABC1234
MESSAGE ID REPLY
REPLY: RIGHT
ABC1234 RIGHT

The system operator does not respond to

the message. The System Reply List does
this instead.

*MSGQ
Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-13. How the System Reply List works

This visual is an example of how a message called ABC1234 will be answered if the job is using the
System Reply List (INQMSGRPY (*SYSRPYL)).
1. The user job sends a message to the system operator message queue.
2. The message is found on the System Reply List with a reply value of 'RIGHT'.
3. The reply 'RIGHT' is sent with no action by the system operator.
This is a pictorial demonstration of what happens when inquiry messages of a job are responded to
via the System Reply List.
• The interactive job has the job attribute INQMSGRPY(*SYSRPYL).
• Therefore any inquiry message that this job sends, is responded to by the System Reply List.
1. DSP25 sends an inquiry message to the system operator message queue.
2. The system operator does not enter the reply;
3. the reply is entered from the System Reply List.
4. The message queue which receives the reply like it always has.

© Copyright IBM Corp. 2001, 2016 20-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

When is the System Reply List used?

For jobs with the following attribute:
Inquiry message reply . . . . . INQMSGRPY(*SYSRPYL)

How the inquiry message reply attribute is specified:

Interactive jobs *JOBD

CHGJOB

Batch jobs *JOBD

CHGJOB
SBMJOB

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-14. When is the System Reply List used?

The job description can specify whether to use the System Reply List. Both CRTJOBD and CHGJOBD
have the parameter INQMSGRPY with possible values as follows:
• *RQD: A reply is required for any predefined inquiry message that is issued by a job that uses
this job description.
• *DFT: The default message reply is used to answer any predefined inquiry messages issued
during running of a job that uses this job description. The default reply is either defined in the
message description or is the default system reply.
• *SYSRPYL: The System Reply List is checked to determine whether an entry matches the
message identifier and optional compare value for any inquiry message issued by a job that
uses this job description. If a match occurs, the reply value in that reply list entry is used. If no
entry exists for that message, a reply is required.
Use the INQMSGRPY parameter to override the job description value on the CHGJOB or SBMJOB
command.
At job initiation time it is the job description that determines the value for INQMSGRPY.
Print jobs run in the QSPL subsystem and have characteristics similar to batch jobs.

© Copyright IBM Corp. 2001, 2016 20-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
There are additional job descriptions for print writers:
• QSPLAFPW: Advanced Function Printing Writer
• QSPLRMTW: Remote Spooling Writers
• QSPLSTRWTR: Auto start Remote Spooling Writers
All of these job descriptions have the INQMSGRPY (*SYSRPYL) attribute.
The INQMSGRPY parameters determine whether the *INQ messages for a job uses the System
Reply List.
You can specify that:
• Inquiry messages need to be answered in the usual manner
• A default reply is issued
• If certain conditions are met, an answer is issued to the inquiry based on those conditions and
the reply specified in the System Reply List

© Copyright IBM Corp. 2001, 2016 20-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

System Reply List

WRKRPYLE

Sequence Message Compare Compare

Opt Reply Dump
Number ID Value Start

_____ 10 CPA0700 D *YES *NONE

_____ 20 RPG0000 D *YES *NONE
_____ 30 CBE0000 D *YES *NONE
_____ 40 PLI0000 D *YES *NONE

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-15. System Reply List

IBM ships the System Reply List with these initial entries defined. For the system to use these
entries, you must specify *SYSRPL for the inquiry message reply attribute for the job.
These entries indicate that a reply of ‘D’ is to be sent and a job dump is to be taken if the message
• CPA0700-CPA0799
• RPG0000-RPG9999
• CBE0000-CBE9999
• PLI0000-PLI9999 (which indicate a program failure) is sent by a job using the System Reply
List.
The Work with System Reply List Entries (WRKRPYLE) command can be used to display or print
all the reply entries currently in the system message reply list. The System Reply List contains
replies that are automatically sent in response to inquiry messages.
The following information is shown for each reply in the System Reply List:
• Sequence number: The number that is used to specify the search order of the entries in the
reply list.
• Message ID: The identifier of an inquiry message for which automatic system action is to be
taken.

© Copyright IBM Corp. 2001, 2016 20-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
• Reply: The default reply to the inquiry message is sent (*DFT) or a specific reply to the inquiry
message is required (*RQD) or a character string (the character string to be sent as the reply to
the inquiry message).
• Dump indication: The job that sent the inquiry message is not dumped (*NO) or the job that sent
the inquiry message is dumped before control is returned to it (*YES).
• Compare value: The character string that is compared with the message data of the inquiry
message.
• Compare start position: A position in the message data of the inquiry message at which the
comparison with the Compare Value starts.
From this display the user can add, change, or remove individual reply list entries.
The reply list is only used when an inquiry message is sent by a job that has the inquiry message
reply attribute of the System Reply List specified (*SYSRPYL is specified on the INQMSGRPY
parameter). The INQMSGRPY attribute can be changed with the CHGJOB command.
The user can add reply list entries with the Add Reply List Entry (ADDRPYLE) command. Specific
attributes of a reply list entry can be changed with the Change Reply List Entry (CHGRPYLE)
command. Each reply list entry remains in the list until it is removed by the Remove Reply List Entry
(RMVRPYLE) command.

© Copyright IBM Corp. 2001, 2016 20-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Reply column of System Reply List

RPY('Message-reply') Character string sent as reply

RPY(*RQD) Requires an explicit reply

RPY(*DFT) Default reply of the inquiry message

To determine valid and default replies of an inquiry message

DSPMSGD RANGE(MESSAGE ID)

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-16. Reply column of System Reply List

By displaying the message description for IBM-supplied messages, using the Display Message
Description (DSPMSGD) command, you can see all of the valid replies.
• *DFT specifies that the default reply is issued, or any of the other valid replies can be specified.
• *RQD means that a reply is required from the user, and causes the message to act as though
the reply list was not in effect.
The default message file in which the system looks for the specified message ID is QCPFMSG.
Program products such as RPG and COBOL have their own message files, such as QRPGMSGE
and QCBLMSGE.

© Copyright IBM Corp. 2001, 2016 20-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Inquiry messages that might not need a reply

Add messages to the System Reply List

CPA4002

Verify alignment on printer PRT01 (I G N R E C)

ADDRPYLE SEQNBR(100) MSGID(CPA4002) CMPDTA('ACCTPRT' 21) RPY(*RQD)
ADDRPYLE SEQNBR(110) MSGID(CPA4002) RPY(*DFT)

CPA3387

Device PRT01 not available (C R)

ADDRPYLE SEQNBR(120) MSGID(CPA3387) RPY(*DFT)

CPA3394

Load form type '*STD' device PRT01 writer PRT01 (G B I H R C)

ADDRPYLE SEQNBR(130) MSGID(CPA3394) CMPDTA('PRT01' 41) RPY(I)
ADDRPYLE SEQNBR(140) MSGID(CPA3394) RPY(*RQD)
Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-17. Inquiry messages that might not need a reply

To have the System Reply List reply to printer messages CPA4002, CPA3387, and CPA3394, you
add them to the System Reply List. The compare value allows you to vary the response, in this
case, by printer.
• For message CPA4002, suppose alignment is only an issue for the printer in the accounting
department, printer ACCTPRT, where preprinted forms are used and which are changed
frequently. These reply list entries will direct the system to send the default reply (I) to all
printers except ACCTPRT. The specific entry for printer ACCTPRT must be before the general
entry. Once a match is found, entries further down the list are not considered.
• For message CPA3387, this entry directs the system to always send a cancel reply if a print
device is not available.
• For message CPA3394, suppose that load form type messages are generally important to you
and you want the user to have to answer them, but for printer PRT01 the paper type is never
changed and you want to print regardless on what is loaded. These entries will handle this
policy. The specific entry must be before the general entry. Once a match occurs, entries further
down the list are not considered.
At job initiation time it is the job description that determines the value for INQMSGRPY.
Print jobs run in the QSPL subsystem and have characteristics similar to batch jobs.

© Copyright IBM Corp. 2001, 2016 20-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
These printer messages can annoy a system operator, especially if they occur for a printer that
always has the same type of paper loaded and stays aligned. So, these messages would be ideal
candidates to have the system respond to these automatically.
An easy way to find out the message ID for a message is to place the cursor on the message and
press F1. The message ID field will be in the upper left corner of the display.
For a message to be automatically responded to via the System Reply List, the message must first
be added to the System Reply List with the wanted reply.

© Copyright IBM Corp. 2001, 2016 20-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

System Reply List with user entries

Sequence Compare Compare

Number Message ID Reply Dump Value Start

10 CPA0700 D *YES *NONE

20 RPG0000 D *YES *NONE
30 CBE0000 D *YES *NONE
40 PLI0000 D *YES *NONE
100 CPA4002 *RQD *NO ACCTPRT 21
110 CPA4002 *DFT *NO
120 CPA3387 *DFT *NO
130 CPA3394 I *NO PRT01 41
140 CPA3394 *RQD *NO

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-18. System Reply List with user entries

Here is the System Reply List in which the entries have been added for the printer messages.

© Copyright IBM Corp. 2001, 2016 20-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Topic 3: Attention program

and DSCJOB

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-19. Topic 3: Attention program and DSCJOB

© Copyright IBM Corp. 2001, 2016 20-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Set attention program

Attention key

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-20. Set attention program

The Attention key can be pressed to:

• Interrupt the current program
• Run another program or use a menu
• Return the user to the first program exactly where the user left it
This differs from using the System Request key which
• Allows the user to sign on to an entirely different job
• Do any function for which they are authorized, just as though they were signing on at the
beginning of the day
The Attention key calls a specified program within the current program. Use the system value
QATNPGM (Attention program) to specify the default program for the system. You can specify one
of the following:
• *ASSIST: The Operational Assistant Main menu is displayed when the Attention key is
pressed.
• *NONE: No attention program is called when the Attention key is pressed.
• Program name/library: The name of the attention program/library to call when the Attention
key is pressed.

© Copyright IBM Corp. 2001, 2016 20-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

User profile: Attention program

ATNPGM(PROGRAM-NAME)

Attention key

The program specified in this parameter in the user’s

profile, is called when the Attention key is pressed.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-21. User profile: Attention program

One of the parameters in a user profile is the Attention program (ATNPGM) parameter. The possible
values for this parameter are:
• *SYSVAL: Calls the program specified in the System Value QATNPGM.
• *ASSIST: This is a special value that calls the Operational Assistant Main menu. It allows the
user to execute options from this menu as though they had used GO ASSIST, but without
having to end their current task or use the command line to do so. *ASSIST could also be the
value of QATNPGM, if you would like it to be the default for the system
• *NONE: No initial attention program is specified for this user.
• Program-name: This is the name of the program called when the Attention key is pressed. This
could be a special CL program, a menu of options for this user, or it could be an application
program written specifically to do Attention key handling.
The value in the user profile can be overridden by the SETATNPGM command. Generally this
command is used within a CL program.

© Copyright IBM Corp. 2001, 2016 20-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
An experienced programmer should be involved when specifying anything other than *SYSVAL,
*ASSIST, or *NONE in a user profile or when naming a specific program in the system value
QATNPGM. Because the attention program runs within the interrupted program, there are special
considerations. See the Work Management manual for more information on using the SETATNPGM
command to override the value in the user profile on a job or application basis and on defining a
program as an attention-key-handling program.

© Copyright IBM Corp. 2001, 2016 20-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Disconnect Job - DSCJOB

Executive
payroll
top secret

Time for lunch

(DSCJOB)

Sign on
User:_______
Password:
Return to work.
Sign on to same
workstation with
same password. Executive
payroll
top secret

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-22. Disconnect Job - DSCJOB

The Disconnect Job (DSCJOB) command is not an end of job. It is a command that is valid only for
interactive jobs. It allows the interactive user to disconnect a job from a workstation and return to a
sign-on display. At the next sign-on to the same workstation with the same user profile, the
interactive job reconnects to the workstation exactly where it was prior to DSCJOB.
The system value QDSCJOBITV (Time value before disconnected job ends) indicates the length of
time in minutes, that an interactive job can be disconnected before it is ended by the system. The
values allowed are:
• Five through 1440:The number of minutes that the system waits before ending a disconnected
job.
• The default value for this parameter is 240 minutes.
• *NONE: The system will not automatically end a disconnected job.
This visual shows conceptually how DSCJOB works. DSCJOB takes less system resource than
signing off and then signing back on. However, the DSCJOB job is tracked by the system.
Another interactive job can be started on the device under a different user name.
The DSCJOB command can also be run by selecting option 13 = Disconnect on the Work with User
Jobs display.

© Copyright IBM Corp. 2001, 2016 20-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
Some considerations when using DSCJOB:
• A TCP/IP TELNET job can be disconnected if the session is using a named device description.
You can create a named device description using one of the following ways:
▪ Network Stations with the DISPLAY NAME parameter
▪ System i Access support with the workstation ID function
▪ TCP/IP TELNET Device Initialization exit point to specify a workstation name
• All jobs will be disconnected for group jobs. When they are connected again, you return to the
place where the disconnect was issued. If the last active group job ends before you connect
again you return to the next group job.
• All disconnected jobs in the subsystem end when the subsystem ends.
• If a subsystem is ending, the DSCJOB command cannot be issued in any of the jobs in the
subsystem.
• Disconnected jobs that have not exceeded the QDSCJOBITV value, end when the subsystem
is ended or when an IPL occurs.

© Copyright IBM Corp. 2001, 2016 20-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Topic 4: Managing writers and

printing

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-23. Topic 4: Managing writers and printing

© Copyright IBM Corp. 2001, 2016 20-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Using multiple writers for an OUTQ

Max 10 writers per OUTQ

*READY to next printer

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-24. Using multiple writers for an OUTQ

Some implementation considerations for multiple writers to an output queue:

• Up to 10 print writers can be active to an output queue at one time.
• For local writers, each will specify a printer device (PRTDEV).
• For remote writers, the output queue parameters will determine whether, where, and how spool
files are to be sent.
• Writers get spooled files in the order the writers are started.
• Each waits for a file with *READY status.
• If there is an attribute mismatch (AFPDS data to SCS or ASCII printer or forms type), the status
is changed to *HELD.
• For a remote writer, status is changed to *SENDING until sent; then it will either be deleted or
saved depending on SAVE parameter.

© Copyright IBM Corp. 2001, 2016 20-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Manage printing by spool file size

Maximum 15 pages
12:00 to 13:00

CRTOUTQ, CHGOUTQ
(MAXPAGES (100 0800 1700)
(15 1200 1300)
(500 0000 2400))

Maximum 500 pages

Maximum 100 pages
00:00 to 24:00
8:00 to 17:00
(could say 17:00 to 08:00)

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-25. Manage printing by spool file size

You could schedule your printing such that the following guidelines apply:
▪ No more than 100 pages printed from 8:00 to 17:00
▪ No more than 15 pages printed from noon to 13:00
▪ Never print more than 500 pages without explicit operator control
In order to do so, you can implement the following:
• MAXPAGES parameter on output queue commands (CRTOUTQ, CHGOUTQ):
▪ Maximum pages allowed in time range
▪ Start time
▪ Stop time
• Up to five sets or iterations of this parameter is allowed
▪ Ranges can overlap for maximum flexibility
▪ Smallest maximum has priority
• Status: *DEFERRED

© Copyright IBM Corp. 2001, 2016 20-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
▪ Spool files greater than maximum will be assigned *DEFERRED status until the ending time
expires.
▪ When maximum time expires, spool file set to *READY status.
Deferred (DFR) spooled file status can change:
• When a writer is started for an output queue, it will calculate the maximum spooled file size for
the current time and change any RDY files which exceed the limit to DFR. Any spooled files
which are added to the output queue (created or moved) after a writer is started for the queue,
will have a status of DFR if the file exceeds the current limit. When the system time-of-day
changes such that a new maximum spooled file size is to take effect, the writer will go through
the output queue again and update RDY files to DFR, or DFR to RDY, depending on the new
limit and the size of the particular spooled file. When the writer is ended, all DFR spooled files
will return to RDY.
• When time ranges for the maximum spooled file size overlap, the smaller of the number of
pages values will be used. For example, assume that there were two time ranges of
08:00:00-16:00:00 and 12:00:00-12:30:00, with number of pages 40 and 10, respectively. The
largest spooled file that would print from 8:00 a.m. to 12:00 p.m. would be 40 pages, the largest
file that would print from 12:00 p.m. to 12:30 p.m. would be 10 pages, and the largest file that
would print from 12:30 p.m. to 4:00 p.m. would be 40 pages.
If a file is *DEFERRED, it is not *HELD, and therefore cannot be *RELEASED. A file can be
*DEFERRED and then changed to *HELD. Then, when *RELEASED, it will either change to
*READ or *DEFERRED status, depending on the MAXPAGES limit in effect at that time.

© Copyright IBM Corp. 2001, 2016 20-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Topic 5: Virtual optical image

catalog

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-26. Topic 5: Virtual optical image catalog

© Copyright IBM Corp. 2001, 2016 20-37

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Virtual optical image catalog

• Can be used to perform the following:
ƒ Install or upgrade to the next version / release of the OS
ƒ Perform a software upgrade
ƒ Install PTFs (fixes)
ƒ Install a single LPP
ƒ Distribute programs
ƒ Perform backups
ƒ Create distribution media for central site support
ƒ Create save LIC media

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-27. Virtual optical image catalog

You can also use a tape image catalog and a virtual tape device to install PTFs or to install single
licensed programs. However you cannot use a virtual tape device to install or upgrade to an OS
release.
Image catalog requirements:
• An image catalog upgrade works like a D-mode IPL without a console during the installation of
Licensed Internal Code (LIC). Reference codes are used to display the status.
• Installations done by using image catalogs requires an OS command line to initiate the
installation.
• Image files cannot reside in an independent auxiliary storage pool (iASP). An installation cannot
be performed from an (iASP).
• To perform an installation using image catalogs, you must have at least 1074 MB of free storage
on the load-source disk unit.
You can use virtual optical media to save images directly to system disk units for convenience,
flexibility, and in some cases improved performance.

© Copyright IBM Corp. 2001, 2016 20-38

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
Virtual optical is beneficial for unattended saves because it eliminates media errors that could halt
an unattended save.
If you do not allocate enough space in the image catalog to save the intended information, virtual
optical will use the autoload feature to create additional images with the same capacity as the last
image you loaded, provided the disk storage is available.

© Copyright IBM Corp. 2001, 2016 20-39

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Steps to create an optical image catalog (1 of 8)

1. Create a virtual CD device.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-28. Steps to create an optical image catalog (1 of 8)

These steps show how you create an image catalog and an image catalog entry, add an image
catalog entry, and load the image catalog in preparation of performing an OS software upgrade.
The specific steps to use a virtual optical device are:
1. Create a virtual optical device. Once it has been created this device can be reused so it is not
necessary to recreate every time this is needed.
To create a device description, enter the following command:
CRTDEVOPT DEVD(virtual-device-name) RSRCNAME(*VRT) ONLINE(*YES)
TEXT(text-description)

© Copyright IBM Corp. 2001, 2016 20-40

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Steps to create an optical image catalog (2 of 8)

2. Vary on this virtual optical device.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-29. Steps to create an optical image catalog (2 of 8)

2. Vary on the virtual optical device. Enter the following:

VRYCFG CFGOBJ(virtual-device-name) CFGTYPE(*DEV) STATUS(*ON)

© Copyright IBM Corp. 2001, 2016 20-41

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Steps to create an optical image catalog (3 of 8)

3. Create an image catalog.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-30. Steps to create an optical image catalog (3 of 8)

3. Create an image catalog. Create an image catalog for the licensed programs that you want to
install. The Create Image Catalog (CRTIMGCLG) command associates an image catalog with a
target directory where the optical image files are loaded.
CRTIMGCLG IMGCLG(catalog-name) DIR(catalog-path) CRTDIR(*YES)
TEXT(text-description

Note

Specify CRTDIR(*YES) only if the directory specified in the DIR parameter does not exist.

© Copyright IBM Corp. 2001, 2016 20-42

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Steps to create an optical image catalog (4 of 8)

4. Add the downloaded image file to the image catalog.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-31. Steps to create an optical image catalog (4 of 8)

4. Add an image catalog entry. Add an image catalog entry for each physical media or optical
image file that you have. You need to repeat this step for each volume of media. You should add
the physical media or optical image files in the same order as if you were going to install from
them. Start with the first media in the list and continue until all the media are loaded.
You can add the entries from either an optical device or from an existing optical image file.
Select one of the following ways:
From an image file:
▪ (This is the fastest way.) To add an image entry to an image catalog from an
integrated-file-system file that is already in the image catalog directory, enter the following:
ADDIMGCLGE IMGCLG(catalog-name) FROMFILE(file-name) TOFILE(*fromfile)
TEXT(text-description)
▪ To add an image catalog entry to an image catalog from an existing integrated-file-system
optical image file from a directory other than the image catalog directory, enter the following:
ADDIMGCLGE IMGCLG(catalog-name)
FROMFILE(/directory-name/directory-name/file-name) TOFILE(file-name or
*FROMFILE) TEXT(text-description)

© Copyright IBM Corp. 2001, 2016 20-43

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
From a physical device:
▪ To add an image catalog entry to an image catalog from a physical optical media using
optical device named OPT01, enter the following:
ADDIMGCLGE IMGCLG(catalog-name) FROMDEV(OPT01) TOFILE(file-name or *GEN)
TEXT(text-description)
Note: To generate a name for the TOFILE parameter, specify *GEN. To generate a text
description from the media, specify *GEN.

© Copyright IBM Corp. 2001, 2016 20-44

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Steps to create an optical image catalog (5 of 8)

5. Load the image catalog.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-32. Steps to create an optical image catalog (5 of 8)

5. Load the image catalog. This step associates the virtual optical device to the image catalog.
Only one image catalog at a time can be associated with a specific virtual optical device. To
load the image catalog, type the following command:
LODIMGCLG IMGCLG(catalog-name) DEV(virtual-device-name) OPTION(*LOAD)
You can also use the WRKIMGCLG command.

© Copyright IBM Corp. 2001, 2016 20-45

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Steps to create an optical image catalog (6 of 8)

6. Verify that the images are in the correct order.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-33. Steps to create an optical image catalog (6 of 8)

6. Verify that the images are in the correct order

Attention

If you are here because you are performing the steps in Preselecting the licensed programs to
install, do not perform this step at this time. You are directed to perform this step later.

• If you are preparing for an upgrade, you need to verify that the required media for an upgrade
exist and are sorted in the correct sequence. You also need to verify that your software
agreements have been accepted, that you have enough storage on the load source, and that
you have enough reserved storage for the Licensed Internal Code.
• Enter the following command:
VFYIMGCLG IMGCLG(catalog-name) TYPE(*UPGRADE) SORT(*YES)
• To verify that images are added. An additional method would be to enter the following:
WRKIMGCLGE IMGCLG(catalog-name)

© Copyright IBM Corp. 2001, 2016 20-46

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
• Then press PF7 to prompt for the VFYIMGCLG command. Enter *UPGRADE for the type and
*YES for the sort field.
• The system puts the images in the correct order. (If you are not successful, refer to Image
catalog recovery.) By default, the volume with the lowest index is mounted. Then all the other
volumes are loaded. To see the order of the images, use the Work with Image Catalog Entries
(WRKIMGCLGE) command:
WRKIMGCLGE IMGCLG(catalog-name) After completing these steps, your image catalog
is ready for use.

© Copyright IBM Corp. 2001, 2016 20-47

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Steps to create an optical image catalog (7 of 8)

7. Verify the status of ready.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-34. Steps to create an optical image catalog (7 of 8)

You can check the status by using the WRKIMGCLG command.

© Copyright IBM Corp. 2001, 2016 20-48

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Steps to create an optical image catalog (8 of 8)

8. Load the PTFs.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-35. Steps to create an optical image catalog (8 of 8)

To load PTF's you have to:

1. Run Go PTF.
2. From menu choose option 8 Install program temporary fix package.
3. Enter the Optical image name and confirm with Enter.

© Copyright IBM Corp. 2001, 2016 20-49

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Web address for virtual optical devices

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-36. Web address for virtual optical devices

The URL to display the web page in the visual is:

http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzam4/rzam4virtual.htm
When a save is complete to virtual optical:
• You can transfer it to physical media at any time and not interfere with system operations.
• You also have the capability to send the stream files from the virtual optical save to another
system by using FTP.
• If you have multiply systems your strategy could be to save each system to virtual optical and
then FTP the stream files to a single system where the save to physical media could take place.
• You can save the virtual images to tape in optical format or you can use the Duplicate Optical
(DUPOPT) command to save the image to optical media.
Note: In a disaster recovery situation:
• You must have physical media of the Licensed Internal Code and the operating system to begin
your recovery.
• If you have saved to virtual optical as part of your disaster protection strategy, you must then
save your Licensed Internal Code and operating system to physical media from the virtual
images.
• You must also have access to all of your user data either on a remote system or on physical
media.

© Copyright IBM Corp. 2001, 2016 20-50

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Topic 6: FTP transfer

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-37. Topic 6: FTP transfer

© Copyright IBM Corp. 2001, 2016 20-51

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Transfer data to and from IBM i

FTP in/out
FTP in/out

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-38. Transfer data to and from IBM i

There are a few methods to transfer data to and from IBM i partition. One of them is FTP (File
Transfer Protocol). Transfer data using FTP is easy but depending on the environment it might
required a different syntax.

© Copyright IBM Corp. 2001, 2016 20-52

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

FTP PC-IBM i

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-39. FTP PC-IBM i

If you want to transfer data to or from IBM i on the workstation open command line Start > Run >
type CMD end press Enter.
In the pop-up window type: ftp <<system name or IP address>> and press Enter.
If need help type ftp /? and press Enter.
Once connected to the partition enter your IBM i user name and password to logon.
Depending on the data you transfer you can chose different mode in most case it is binary mode
(the binary mode transmits all 8 bits per byte and thus provides less chance of a transmission error
and must be used to transmit files other than ASCII files) for example to transfer PTF’s package you
have to use binary mode.
On the command line type bin and press Enter.
By default, FTP (File Transfer Protocol) uses the traditional IBM i file naming conventions -
Libraries, which contain Files, which in turn contain Members. This is also known as the *LIB
Naming Format, and looks like the following: Libraryname/Filename.Membername.

© Copyright IBM Corp. 2001, 2016 20-53

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

FTP PC-IBM i name format

Default Naming
Format NAMEFMT 0

IFS Naming Format

NAMEFMT 1

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-40. FTP PC-IBM i name format

By default, FTP (File Transfer Protocol) uses the traditional IBM i file naming conventions -
Libraries, which contain Files, which in turn contain Members. This is also known as the *LIB
Naming Format, and looks like the following: Libraryname/Filename.Membername.
When you type DIR command, you will be see your current library if you do not have specified
library in your profile by default it will be QGPL.
If you want to work with object in IFS you have to change naming format to IBM i Integrated File
System Naming Format. This looks much more like a UNIX or Personal Computer Directory
system. We must use this Naming Format known as *PATH or 'NAMEFMT 1' to access files in the
Integrated File System, the document library services QDLS folders, QOPT optical files, or to send
save files.
To change format type cd/.
A lot of ftp clients offer a graphical interface where you can easy change the naming format.

© Copyright IBM Corp. 2001, 2016 20-54

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

FTP PC-IBM i transfer

Sending command
put

Downloading command
get

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-41. FTP PC-IBM i transfer

By default, FTP (File Transfer Protocol) uses the traditional IBM i file naming conventions -
Libraries, which contain Files, which in turn contain Members. This is also known as the *LIB
Naming Format, and looks like the following: Libraryname/Filename.Membername.
When you type DIR command you will be see your current library if you don’t have specified library
in your profile by default it will be QGPL.
If you want to work with object in IFS you have to change naming format to IBM i Integrated File
System Naming Format. This looks much more like a UNIX or Personal Computer Directory
system. We must use this Naming Format known as *PATH or 'NAMEFMT 1' to access files in the
Integrated File System, the document library services QDLS folders, QOPT optical files, or to send
save files.
To change format type cd/.
A lot of ftp clients offer a graphical interface where you can easy change the naming format.
To send something you have to use command put or mput (for group of files. To download you
have to use get command or mget (for group of files).
To close ftp session type quit and press Enter.

© Copyright IBM Corp. 2001, 2016 20-55

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

FTP IBM i - IBM i transfer

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-42. FTP IBM i - IBM i transfer

Transfer between two IBM i partitions is similar to PC-IBM i transfer. You have to type in the
command line command ftp <<system name or IP address>> and press Enter.
After you enter the user name and password you will be connected to remote system (default) in
QGPL library using default name format.

© Copyright IBM Corp. 2001, 2016 20-56

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

FTP IBM i - IBM i IFS name format

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-43. FTP IBM i - IBM i IFS name format

To change name format use command namefmt 1 If you wan to back to IBM i library name
convention use namefmt 0.
To end ftp session type quit and press Enter or press F3 function key and type 1 Yes and confirm
with Enter.

© Copyright IBM Corp. 2001, 2016 20-57

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

FTP - batch mode

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-44. FTP - batch mode

It is possible to ftp something to a few systems by using a batch job.

To prepare ftp batch you have to create a simple CL pgm, where you declare file in this example
INPUTFILE with IP addresses of systems or systems name if your system can resolved the names.
In the physical file exist field SYSTEM_IP where are IP addresses (or system names).
Example:
PGM
DCLF FILE(AS2700/INPUTFILE)
DCL VAR(&NAME) TYPE(*CHAR) LEN(8)
LOOP:
RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(END))
CHGVAR VAR(&NAME) VALUE(&SYSTEM_IP)

OVRDBF FILE(INPUT) TOFILE(AS2700/QCLSRC) MBR(FTP_REQ)

© Copyright IBM Corp. 2001, 2016 20-58

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty
OVRDBF FILE(OUTPUT) TOFILE(AS2700/QCLSRC) MBR(FTP_RES)
FTP RMTSYS(&NAME)
GOTO CMDLBL(LOOP)
END:
ENDPGM
When you create it compile to CL program.
In program you work with two file members.
First is an input member where you have to type the user password, name format, binary mode and
what do you want transfer.
Example:
USER PASSWORD
BIN
NA 0
PUT AS2700/CUSTMASTER AS2700/CUSTMASTER
QUIT
However the member is in QCLSRC file but type must be TXT and do not try to compile it.
Second member is an output which receive messages from ftp server here you can find any errors
during connection or transfer. In the member you can find this same information when you try
connect to any system interactive.

© Copyright IBM Corp. 2001, 2016 20-59

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

FTP - batch mode run

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-45. FTP - batch mode run

To start ftp transferring call the program ftp_auto and see result in the ftp_res member in the
QCLSRC file.
Of course you can connect to any operating system not only IBM i.

© Copyright IBM Corp. 2001, 2016 20-60

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Topic 7: Advanced spool file

management

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-46. Topic 7: Advanced spool file management

© Copyright IBM Corp. 2001, 2016 20-61

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Too many files

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-47. Too many files

A large number of spooled files are generated every day, some of them are important some not and
can be deleted by a simple clear outq.

© Copyright IBM Corp. 2001, 2016 20-62

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Spool file expiration

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-48. Spool file expiration

For each spool file you can set an expiration. To set the expiration: Select the spool file. Select
option 2 Change press the F10 function key. PGDWN and find Expiration date for file (EXPDATE
keyword).
Of course this is good for one or many files.
You can also use:
Change Spooled File Attributes (CHGSPLFA) command or by taking Option 8 (Attributes) from the
Work with Spooled Files (WRKSPLF) or Work with Output Queue (WRKOUTQ) commands. For
example:
CHGSPLFA FILE(QPRTLIBL) JOB(*) SPLNBR(1) EXPDATE(*DAYS) DAYS(30)
CHGSPLFA FILE(QPRTLIBL) JOB(*) SPLNBR(1) EXPDATE(*NONE)

© Copyright IBM Corp. 2001, 2016 20-63

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Spool files expiration

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-49. Spool files expiration

For multiple files the better method might be:

Create Printer File (CRTPRTF), Change Printer File (CHGPRTF) and Override with Printer File
(OVRPRTF) commands. For example:
CRTPRTF FILE(library/printer-file) EXPDATE(*DAYS) DAYS(30)
CHGPRTF FILE(QPJOBLOG) EXPDATE(*DAYS) DAYS(30)
OVRPRTF FILE(QPJOBLOG) EXPDATE(*DAYS) DAYS(30) OVRSCOPE(*JOB)
All created spool files will have expiration data.

© Copyright IBM Corp. 2001, 2016 20-64

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

BRMS spool files expiration

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-50. BRMS spool files expiration

If you using BRMS (Backup and Recovery Media Solution) you can setup expiration of saved spool
files. To do that you have to create or change (use WRKLBRM command) the Spooled File List which
will be added to Control Group. On the Create/Change Spooled File List enter which spool file will
be saved and press F11 function key to setup spool file expiration.
There are two available values:
*SAVDAT
The number of days specified in the Expiration field is added to the start date of the save
operation.
*CRTDAT
The number of days specified in the Expiration field is added to the creation date for each
spool file.

© Copyright IBM Corp. 2001, 2016 20-65

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Delete expired spooled files

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-51. Delete expired spooled files

After expiration is set for a spool file you can use the DLTEXPSPLF command to delete expired
spooled files.
You can also to do this with:
SBMJOB CMD(DLTEXPSPLF ASPGRP(*ALL)) JOB(DLTEXPSPLF)
ADDJOBSCDE JOB(DLTEXPSPLF) CMD(DLTEXPSPLF ASPGRP(*ALL)) FRQ(*WEEKLY)
SCDDATE(*NONE) SCDDAY(*ALL) SCDTIME(010000)
JOBQ(QSYS/QSYSNOMAX)
TEXT('Delete expired SPLFs on a weekly basis')
The Delete Expired Spooled Files (DLTEXPSPLF) command removes expired spooled files on the
system or the auxiliary storage pool (ASP) group specified by the user. A spooled file expires at
23:59:59, system local time on the date specified in the Expiration date for file (EXPDATE)
spooled file attribute.

© Copyright IBM Corp. 2001, 2016 20-66

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Topic 8: SST/DST Advance

Operator functionality

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-52. Topic 8: SST/DST Advance Operator functionality

© Copyright IBM Corp. 2001, 2016 20-67

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Problem determination

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-53. Problem determination

For simple problem reporting you can use two tools Product Activity Log (PAL) and Work with
service action log (SAL). To use this tool on the command line type STRSST (Start Service Tools)
and press Enter.
On the SST menu chose option 1 Start a service tool and then again option 1 Product activity log.

© Copyright IBM Corp. 2001, 2016 20-68

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Product activity log

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-54. Product activity log

Chose Option 1 Analyze log.

On the select subsystem data you can select all logs or logs for specific group. You can also set the
date/time scope.
Define report option depending on your or service requirements.

© Copyright IBM Corp. 2001, 2016 20-69

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Log Analysis Report

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-55. Log Analysis Report

If you chose report output on the display you can work with existing problems.

© Copyright IBM Corp. 2001, 2016 20-70

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Work with service action log

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-56. Work with service action log

To Work with service action log (SAL) from the SST menu select option 1 Start service log. Then
select option 7 Hardware service manager and chose option 6 Work with service action log.

© Copyright IBM Corp. 2001, 2016 20-71

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Service action log

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-57. Service action log

From the action log you can also chose data and time. On the report list you can display, close
entry, or delete closed entry.

© Copyright IBM Corp. 2001, 2016 20-72

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Service action log entry details

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-58. Service action log entry details

On the display detail you can analyze the problem.

© Copyright IBM Corp. 2001, 2016 20-73

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Check disks status

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-59. Check disks status

Using SST you can analyze of the disk health status. Because now is the trend to move to external
disks. The external this are present to the system with multipath connection. It is very important to
verify all path are in proper state. Internal disks presented by modern SAS adapter will show on the
system more than one access path to the disks. Work with disks you have to select from SST menu
option 3 Work with disk units option 1 Display disk configuration. Here you can analyze more disks
health information one them is path status. To work with path status chose option 9 Display disk
path status.

© Copyright IBM Corp. 2001, 2016 20-74

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Disk path status

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-60. Disk path status

Depending on the configuration you can see all path Active or mix Active Passive (often in SAS
disks).

© Copyright IBM Corp. 2001, 2016 20-75

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Review questions (1 of 2)
1. True or False: A proxy command is the same as a
duplicated command.

2. A maximum of up to (blank) print writers can be active to an

output queue at one time.
a. 1
b. 5
c. 10
d. 32

3. True or False: A job that is disconnected will remain on the

system indefinitely.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-61. Review questions (1 of 2)

© Copyright IBM Corp. 2001, 2016 20-76

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Review answers (1 of 2)
1. True or False. A proxy command is the same as a duplicated
command.
The answer is False.

2. A maximum of up to 10 print writers can be active to an

output queue at one time.
a. 1
b. 5
c. 10
d. 32
The answer is 10.

3. True or False. A job that is disconnected will remain on the

system indefinitely.
The answer is False.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-62. Review answers (1 of 2)

© Copyright IBM Corp. 2001, 2016 20-77

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Review questions (2 of 2)
4. An optical image catalog can be used to:
a. Upgrade to the next version or release of OS
b. Install PTFs
c. Install an LPP
d. All of the above

5. True or False: Batch FTP mode is not available on IBM i.

6. True or False: You can delete expired spooled file in IBM i.

7. True or False: You cannot check status of the disk path.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-63. Review questions (2 of 2)

© Copyright IBM Corp. 2001, 2016 20-78

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Review answer (2 of 2)
4. An optical image catalog can be used to:
a. Upgrade to the next version or release of OS
b. Install PTFs
c. Install an LPP
d. All of the above
The answer is All of the above.

5. True or False: Batch FTP mode is not available on IBM i.

The answer is False.

6. True or False: You can delete expired spooled file in IBM i.

The answer is True.

7. True or False: You cannot check status of the disk path.

The answer is False.

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-64. Review answer (2 of 2)

© Copyright IBM Corp. 2001, 2016 20-79

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Exercise: Tips for improved operations

• At the end of the exercise, you should be able to:
ƒ Use CHGCMDDFT and CHGCMD to tailor commands to your
operating environment
ƒ Use CRTPRXCMD to create a proxy command
ƒ Display messages and determine the default reply

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-65. Exercise: Tips for improved operations

© Copyright IBM Corp. 2001, 2016 20-80

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 20. Tips for improved operation

Uempty

Unit summary
• Create a user-defined proxy command
• Change how a command is used
• Permanently change a command's defaults
• Explain how to use the System Reply List to automatically reply to
messages
• Explain how to leave a job temporarily through the attention key or how
to disconnect a job
• Use printers efficiently through printer load balancing
• Describe the process of creating a virtual optical device to use when
performing a software upgrade or installing PTFs
• Describe how perform FTP transfer included batch mode
• Explain some SST/DST function to diagnostic problems

Tips for improved operation © Copyright IBM Corporation 2001, 2016

Figure 20-66. Unit summary

This unit has covered ways to change defaults, make the system easier for the users, and make
operations more streamlined for the system operator as well as otherwise improve system
operations.

© Copyright IBM Corp. 2001, 2016 20-81

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Unit 21. Journaling overview and basic

operation
Estimated time
01:00

Overview
Journal management is a very valuable and powerful tool which is an integral part of the operating
system. When used properly as part of a comprehensive recovery plan, it significantly improves the
ability of the administrator to recover from many types of job and system failures.

How you will check your progress

• Review questions
• Machine exercises

© Copyright IBM Corp. 2001, 2016 21-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Unit objectives
• Describe how journal management can be used to recover data lost
during a failure
• Implement journal management on your IBM Power System with IBM i
as part of a comprehensive recovery plan
• List the advantages and considerations of journal management

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-1. Unit objectives

© Copyright IBM Corp. 2001, 2016 21-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Topic 1: Journal management

concepts

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-2. Topic 1: Journal management concepts

© Copyright IBM Corp. 2001, 2016 21-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Think about your most important data file

Data file

• What if it disappeared?
• How would you get it back?
ƒ RSTOBJ
ƒ Rekey all data from last save plus data since last save
• How much time would it take?
• Do you need to shorten the recovery time for data files?

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-3. Think about your most important data file

© Copyright IBM Corp. 2001, 2016 21-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Single-level storage
ON

OFF

Volatile storage
Main memory N S

*PGM Magnetic storage Or solid state

disk drives disk drives
Delete
Update
Write 1
2
*JRNRCV
*JRN
Buffer Disk File A File A File A
I/O
3 4

Data file
scatter loading
Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-4. Single-level storage

Journal management enables you to recover the changes to an object that have occurred since the
object was last saved. You can also use journal management to provide an audit trail or to help
replicate an object. You use a journal to define what objects you want to protect with journal
management. The system keeps a record of changes you make to objects that are journaled and of
other events that occur on the system.
1. Journal management intercepts the database record (add, update, or delete).
2. Journal entry is forced to the journal receiver on a disk with a force ratio of one.
3. The database record is given to database data management.
4. The database record is written to disk
FRCRATIO(*NONE) is recommended for journaled files.
Information in volatile storage, also called main memory, gets destroyed while information on disk is
still there.
A file is a very complex object and a journal is a very simple object, so force write ratio uses more
disk arm movement than journaling. With journaling, CPU power is not the issue, disk space, and
disk I/O are. This topic also shows how to manage that disk space and I/O.

© Copyright IBM Corp. 2001, 2016 21-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
Updates to database pages are made in main storage. When the update is complete and journaling
has been implemented, journal management writes the updated record to the receiver on disk. The
physical file on disk is updated asynchronously when the system page out task is invoked at a later
time. In addition to a copy of the updated data record, the journal entry contains information about
the user, the time, the program, the file, and so on, for which the entry was made.

© Copyright IBM Corp. 2001, 2016 21-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Journal objects
Journaling data flow

PGMX PGMY

Object A Object B Object B Object C

change change change change

Journal
receiver

Object A change
Object B change
Object B change
Obj. A Obj. B Obj. C

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-5. Journal objects

The system keeps a record of changes you make to objects that are journaled and of other events
that occur on the system. These records are called journal entries. You can also write journal
entries for events that you want to record, or for objects other than the object that you want to
protect with journaling.
Contents of a journal entry:
• Information identifying the type of change
• Information identifying the record that was changed
• After image of the record
• Before image of the record (optional) (this is a separate journal entry)
• Information identifying the job, the user, the time of change, and so forth
• Information that identifies whether the file was opened, closed, reorganized, cleared, or saved
• The journal identifier of the object
A very important point here is the fact that journaling is done by file, not by program. This means no
programming changes need be made. More important, journaling records all activity on the files
being journaled no matter where or when the activity takes place, now or in the future, such as
adding, deleting, or renaming a file member.

© Copyright IBM Corp. 2001, 2016 21-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Objects that can be journaled

• Ability to record changes into a journal of:
ƒ Access paths
ƒ Libraries
ƒ Objects
í Data area (*DTAARA)
í Data queue (*DTAQ)
ƒ Database physical files (*PF)
ƒ IFS objects
í Stream files (*STMF)
í Directories (*DIR)
í Symbolic link (*SYMLNK)
ƒ Note: IFS objects must be in the root (/), QOpensys, user-defined file
system

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-6. Objects that can be journaled

© Copyright IBM Corp. 2001, 2016 21-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Display Journal Entries

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-7. Display Journal Entries

The Display Journal (DSPJRN) command allows you to convert journal entries (contained in one or
more receivers) into a form suitable for external representation. Output of the command can be
displayed or printed with the job's spooled printer output or directed to a database output file. If the
database output file exists, records can either replace or be added to the current data in the
indicated file member. The system creates the specified database file and member if they do not
exist. Database files created by the system have a standard format. A warning message is sent and
the records are truncated if any of the entries are longer than the specified maximum record length
of the output files.
The Display Journal display shows a list of the journal entries that you requested to be displayed.
Only basic information about the journal entry is shown on this display. From this display, you can
request to see all of the information for a specific journal entry.
To see all of the information for a specific journal entry, type 5 next to the journal entries that you
want more information about, and press Enter.

© Copyright IBM Corp. 2001, 2016 21-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Display Journal Entry

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-8. Display Journal Entry

The Display Journal Entry (option 5) display shows all of the information about a specific journal
entry. The journal entry shown is one that you requested on the Display Journal display.
Sequence - The journal sequence number
The sequence number is initially 1. Each journal entry is sequentially numbered without any breaks
until the Change Journal (CHGHRN) command resets the sequence number. However, when journal
entries are converted and displayed, there can be breaks in the sequence numbers. The system
uses some journal entries only internally and combines some entries into one during conversion.
Incomplete data
Indicates whether this entry has entry-specific data which is not being displayed for one of the
following reasons.
• The length of the entry-specific data exceeds 32,766 bytes.
• The entry is associated with a database file that has one or more fields of data type BLOB (binary
large object), CLOB (character large object), or DBCLOB (double-byte character large object)
The possible values are:
• No - This entry has all possible data
• Yes - This entry has incomplete data

© Copyright IBM Corp. 2001, 2016 21-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
The data which is not visible through this interface can only be accessed by using the Retrieve
Journal Entries (QjoRetreiveJournalEntries) API or by specifying ENTFMT (*TYPEPTR) on the
RCVJRNE command.
Entry-specific data
This is additional information about the entry. The contents of this field are dependent on the kind of
journal entry. If there is no entry-specific data for the kind of entry being shown, the message No
Entry specific data is shown in this field. The information shown in this field is not formatted. For
a description of the format of the entry-specific data, see the IBM Power Systems with IBM
Knowledge Center.

© Copyright IBM Corp. 2001, 2016 21-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

F10 = Display only entry details

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-9. F10 = Display only entry details

The Display Journal Entry Details display shows only the detail entry data for a specific journal
entry. The journal entry shown is one that you requested on the Display Journal display.
If you see More... on the lower right side of your display, there is more information to view. Press
Page Down (or Roll Up) to move toward the end of the information. Press Page Up (or Roll Down)
to move toward the beginning of the information.

© Copyright IBM Corp. 2001, 2016 21-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Topic 2: Steps to implement

journaling

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-10. Topic 2: Steps to implement journaling

© Copyright IBM Corp. 2001, 2016 21-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Implementing journaling
• For example: Implementation of object journaling
1. Create the journal receiver.
CRTJRNRCV JRNRCV( )

2. Create the journal.

CRTJRN JRN( ) JRNRCV( )

3. Start journaling for selected objects.

STRJRNOBJ OBJ( ) JRN( )

4. Save the objects.

• That is it!

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-11. Implementing journaling

The Create Journal Receiver (CRTJRNRCV) command creates a journal receiver. Once a journal
receiver is attached to a journal (with the Create Journal (CRTJRN) or Change Journal (CHGJRN)
command), journal entries can be placed in it. A preferred auxiliary storage pool (ASP), and a
storage space threshold value can be specified for the journal receiver.
The Create Journal (CRTJRN) command creates a journal as a local journal with the specified
attributes, and attaches the specified journal receiver to the journal. Once a journal is created,
object changes can be journaled to it or user entries can be sent to it. The journal state of the
created journal is *ACTIVE.
The different types of objects that can be journaled and the commands that you will use are:
• Start to Journal an Access Path (STRJRNAP) command is used to start journaling the access
paths for all members of a database file to a specified journal. Any new member that is later
added to the file also has its access path journaled.
• Start to Journal a Library (STRJRNLIB) command is used to start journaling changes (made to a
library or list of libraries) to a specific journal, and optionally to start journaling changes to
objects within the library or list of libraries. Objects created in, moved into, or restored into a
journaled library can be automatically journaled to the same journal the library is journaled to.

© Copyright IBM Corp. 2001, 2016 21-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
• Start to Journal an Object (STRJRNOBJ) command is used to start journaling changes (made to
an object or list of objects) to a specific journal. The object types which are supported through
this interface are Data Areas (*DTAARA) and Data Queues (*DTAQ).
• Start to Journal a Physical File (STRJRNPF) command is used to start journaling changes made
to a specific database physical file to a specific journal. Changes in new members added to the
file are also journaled.
• Start to Journal IFS Objects (STRJRN) command is used to start journaling changes (made to an
object or list of objects) to a specific journal. The object types which are supported through this
interface are Stream Files (*STMF), Directories (*DIR), and Symbolic Links (*SYMLNK). Only
objects of type *STMF, *DIR, or *SYMLNK that are in the “root” (/), QOpenSys, and user-defined file
systems are supported.
For more information about the possible journal entries which can be sent, see the Journal
management topic collection in the IBM Knowledge Center at:
http://www.ibm.com/support/knowledgecenter. Search for “journal entry finder”.
The commands follow this visual.
When you start journaling for a physical file, the system assigns a unique journal identifier (JID) to
every member. The JID is part of every journal entry for the file. The JID is used to associate the
journal entry with the file. If a file is saved before journaling is started, it does not have a JID. If the
file is restored, it does not have a JID. It is critical to save a journaled file every time a member has
been added to it.

© Copyright IBM Corp. 2001, 2016 21-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Step 1: CRTJRNRCV command

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-12. Step 1: CRTJRNRCV command

It is recommended that the journal receiver name should be unique for your system, not unique
within a library. If you have two journal receivers with the same name in different libraries and they
both become damaged, RCLSTG renames both journal receivers when they are placed in the QRCL
library.
The Create Journal Receiver (CRTJRNRCV) command creates a journal receiver. Once a journal
receiver is attached to a journal (with the Create Journal (CRTJRN) or Change Journal (CHGJRN)
command), journal entries can be placed in it. A preferred auxiliary storage pool (ASP), and a
storage space threshold value can be specified for the journal receiver.
Restrictions
• A Journal receiver cannot be created in library QTEMP.
• This command cannot be used to create a journal receiver for a remote journal.
• If the library to contain the journal receiver is on an independent ASP, then ASP(*LIBASP) must
be specified.
Setting the threshold is very important for managing journaling disk space. More on this in later
visuals. You must set the stage now however.

© Copyright IBM Corp. 2001, 2016 21-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
It is recommended that the journal receiver name be unique for your entire system and not just
unique within a library. If you have two journal receivers with the same name in different libraries
and they both become damaged, RCLSTG renames both journal receivers when they are placed in
the QRCL library.
The ASP parameter determines in which auxiliary pool to place the journal receiver.

© Copyright IBM Corp. 2001, 2016 21-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Step 2: CRTJRN command

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-13. Step 2: CRTJRN command

The Create Journal (CRTJRN) command creates a journal as a local journal with the specified
attributes, and attaches the specified journal receivers to the journal. Once a journal is created,
object changes can be journaled to it or user entries can be sent to it. The journal state of the
created journal is *ACTIVE.
Restrictions
1. A journal cannot be created in the library QTEMP.
2. The specified journal receivers must be created before the running of this command and they
must be empty. That is, the receivers must not have been previously attached to a journal or
have been in the process of being attached to a journal.
3. This command cannot be used to create a remote journal. See the Add Remote Journal
(QjoAddRemoteJournal) API in the IBM Power Systems with IBM i Information Center
(Programming -> APIs).
4. If the library to contain the journal is on an independent ASP, then the journal receiver specified
must be located on an independent ASP that is in the same ASP group as the journal's library.
Likewise, if the library to contain the journal is not on an independent ASP, then the journal
receiver specified cannot be located on an independent ASP.
5. If the library to contain the journal is on an independent ASP, then ASP(*LIBASP) must be
specified.

© Copyright IBM Corp. 2001, 2016 21-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Step 3a: Access path command (STRJRNAP)

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-14. Step 3a: Access path command (STRJRNAP)

The Start Journal Access Path (STRJRNAP) command is used to start journaling the access paths for
all members of a database file to a specified journal. Any new member that is later added to the file
also has its access path journaled.
If a physical file is specified, journaling can be started for its access paths. When access path
journaling is started for a physical file, only the access paths for the physical file members are
journaled. Journaling for any logical file access paths is started only when access path journaling is
started for the logical file.
The journal entries created after running this command cannot be used in any apply or remove
journaled changes operation. These entries are used only to recover the access path without
rebuilding it after an abnormal system operation ending.
If you do not want the overhead of managing the access path journaling yourself, consider taking
advantage of the system-managed access-path protection support SMAPP which will be covered
later in this unit.

© Copyright IBM Corp. 2001, 2016 21-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Step 3b: Library command (STRJRNLIB)

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-15. Step 3b: Library command (STRJRNLIB)

The Start Journal Library (STRJRNLIB) command is used to start journaling changes (made to a
library or list of libraries) to a specific journal, and optionally to start journaling changes to objects
within the library or list of libraries. Objects created in, moved into, or restored into a journaled
library can be automatically journaled to the same journal the library is journaled to.
After journaling begins for the object, the user should save the journaled object to preserve its
journal attribute information. Also, the object must be saved because, for example, journaled
changes cannot be applied to a version of the object that was saved before journaling was in effect.
Objects created, moved, or restored into the library that is eligible for journaling can automatically
start journaling to the same journal as the library. Which objects inherit the journal state of the
library and what journaling attributes they start journaling with are determined by the inherit
journaling attributes of the library.

© Copyright IBM Corp. 2001, 2016 21-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Step 3c: Object command (STRJRNOBJ)

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-16. Step 3c: Object command (STRJRNOBJ)

The Start Journal Object (STRJRNOBJ) command is used to start journaling changes (made to an
object or list of objects) to a specific journal. The object types which are supported through this
interface are Data Areas (*DTAARA) and Data Queues (*DTAQ).
Additionally, the user can specify that only the after image or both the before and the after images
of an object of type *DTAARA be journaled. Before images are necessary to remove journaled
changes by using the Remove Journaled Changes (RMVJRNCHG) command.
After journaling begins for the object, the user should save the journaled object to preserve its
journal attribute information. Also, the object must be saved because, for example, journaled
changes cannot be applied to a version of the object that was saved before journaling was in effect.

© Copyright IBM Corp. 2001, 2016 21-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Step 3d: Physical file command (STRJRNPF)

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-17. Step 3d: Physical file command (STRJRNPF)

The Start Journal Physical File (STRJRNPF) command is used to start journaling changes made to a
specific database physical file to a specific journal. Changes in new members added to the file are
also journaled.
The user can specify that only the after image or both the before and after images of records in the
journaled physical file be journaled. Before images are necessary to remove journaled changes by
using the Remove Journaled Changes (RMVJRNCHG) command. In addition, the system will
automatically capture the before images for a database file if the file is opened under commitment
control.
After journaling begins for the file, and after any new members are added to the file, the user should
run the Save Changed Object (SAVCHGOBJ) command with OBJTYPE(*FILE) and OBJJRN(*YES)
specified. The file must be saved because journaled changes cannot be applied to a version of the
file that was saved before journaling was in effect.
When the file being journaled is a distributed file, the STRJRNPF command is also distributed, if
journaling was successfully started locally. Even if the distribution request fails, the local file
remains journaled.
Up to 50 files can be specified per command.

© Copyright IBM Corp. 2001, 2016 21-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
There is no limit, other than a practical one, to the number of files that can be journaled to a single
journal.
From a security point of view, omitting the file opens and closes could be dangerous because if a
program opened a file for read only, no entry would be recorded in the journal receiver.
IMAGES(*BOTH) is recommended. It allows backout recovery (RMVJRNCHG). However, it takes
more space.
OMTJRNE(*OPNCLO) is not recommended. You cannot use the journal to audit who opened a file.
You cannot apply entries to open and close boundaries by using the TOJOBO and TOJOBC
parameters.

© Copyright IBM Corp. 2001, 2016 21-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Step 3e: IFS object command (STRJRN)

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-18. Step 3e: IFS object command (STRJRN)

The Start Journal (STRJRN) command is used to start journaling changes (made to an object or list
of objects) to a specific journal. The object types which are supported through this interface are
Stream Files (*STMF), Directories (*DIR), and Symbolic Links (*SYMLNK). Only objects of type *STMF,
*DIR or *SYMLNK that are in the “root” (/), QOpenSys, and user-defined file systems are supported.
The user can specify that only the after image or both the before and the after images of an object
of type *DTAARA be journaled. Before images are necessary to remove journaled changes by using
the Remove Journaled Changes (RMVJRNCHG) command.
After journaling begins for the object, the user should save the journaled object to preserve its
journal attribute information. Also, the object must be saved because, for example, journaled
changes cannot be applied to a version of the object that was saved before journaling was in effect.

© Copyright IBM Corp. 2001, 2016 21-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

IBM Navigator for i: Journaling

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-19. IBM Navigator for i: Journaling

On the IBM Navigator for i you can manage journals and journal receivers.
To manage journals on the IBM Navigator for i welcome page on the left pane click Journal
Management then on the main pane you will be see the Journal Management window.
The welcome page provides links to the most commonly used Journal Management tasks. There
are links to manage journal and receiver and a button which allows you to set database and library.
You can also manage journaling from the database perspective.
1. On the left pane, expand Database then expand Databases.
2. Expand your database (could be system name).
3. Click Schemas and from the Actions menu chose Select Schema to Display.
4. On the left pane, expand Schemas and find yours and click it.
5. On the main pane, you will be see all your schema objects icon. There will be also journal and
journal receivers.

© Copyright IBM Corp. 2001, 2016 21-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

IBM Navigator for i start/end journaling

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-20. IBM Navigator for i start/end journaling

To start journaling right-click the object and chose Journaling from pop-up menu.

© Copyright IBM Corp. 2001, 2016 21-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Save objects
• When?
ƒ Immediately after STRJRNxx or if a new member is added to the file

• Why?
ƒ Checkpoint for recovery (F/MS journal entry)
í Restore damaged object
í Apply journaled changes from *LASTSAVE

• Must have the system assigned journal identifier (JID)

in every saved member used for recovery after a restore.

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-21. Save objects

When you start journaling for a physical file, the system assigns a unique journal identifier (JID) to
every member. The JID is part of every journal entry for the file.
The JID is used to associate the journal entry with the file. If a file is saved before journaling is
started, it does not have a JID, and if the file is restored it does not have a JID.
It is critical to save a journaled file every time a member has been added to it.
The whole idea of journaling is to recover data files. Because of this, it is important to fix a point in
the journal receiver so the recovery starts in the proper place. What better place than when the file
was last saved?
When you start journaling for a physical byte, the system assigns a unique journal identifier (JID) to
every member. The JID is part of every journal entry for the file. The JID is used to associate the
journal entry with the file. If a file is saved before journaling is started, it does not have a JID, and if
the file is restored, it does not have a JID. It is critical to save a journaled file every time a member
has been added to it.

© Copyright IBM Corp. 2001, 2016 21-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Topic 3: Journal receiver

considerations

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-22. Topic 3: Journal receiver considerations

© Copyright IBM Corp. 2001, 2016 21-28

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Managing the receiver chain

CHGJRN JRN(name) JRNRCV(*GEN) MNGRCV(*USER)

SEQOPT(*CONT or*RESET)

*PGM

RCV0001
Old
receiver
RCV0002
Current
receiver
*File

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-23. Managing the receiver chain

The Change Journal (CHGJRN) command changes the journal receiver, the journal message queue,
the manage receiver attribute, the delete receiver attribute, the receiver size options, the journal
state, allowing minimized entry-specific data, journal caching, the journal receiver's threshold, the
journal object limit, the journal recovery count, or the text associated with the specified journal. The
command allows one journal receiver to be attached to the specified journal. This replaces the
previously attached journal receiver. The newly attached journal receiver begins receiving journal
entries for the journal immediately.
The sequence numbering of journal entries can be reset when the receiver is changed. If the
sequencing is not reset, an informational message is sent indicating the first sequence number in
the newly attached receiver.
The Manage receivers (MNGRCV) parameter is used to specify how the changing of journal receivers
(detaching the currently attached journal receiver and attaching a new journal receiver) is
managed. You can specify a value for the MNGRCV parameter for both the CRTJRN and the CHGJRN
commands.

© Copyright IBM Corp. 2001, 2016 21-29

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
For this parameter you can specify:
*USER
The user manages the changing of journal receivers by issuing the Change Journal (CHGJRN)
command to attach new receivers and detach old receivers.
*SYSTEM
• The system manages the changing of journal receivers. This function is called system
change-journal management.
• When an attached journal receiver reaches its size threshold, the system detaches the attached
journal receivers and creates and attaches new journal receivers. Message CPF7020 is sent to
the journal message queue when the journal receivers are detached.
• Additionally, during an initial program load (IPL), the system performs a CHGJRN command to
create and attach new journal receivers and to reset the journal sequence number of journals
that are not needed for commitment control recovery for that IPL.
• Also, the system attempts to perform a CHGJRN command to reset the sequence numbers when
the journal receiver's sequence number exceeds 2,147,000,000.

© Copyright IBM Corp. 2001, 2016 21-30

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

System change journal management

• CRTJRN ... MNGRCV(*SYSTEM)
ƒ Threshold: Receiver changed automatically and message sent
ƒ IPL: Receiver changed automatically with sequence number reset

• CRTJRN ... MNGRCV(*SYSTEM) DLTRCV(*YES)

ƒ Detached receiver automatically deleted as soon as it is not needed for
recovering access paths or rolling back uncommitted changes
ƒ Caution: Journal receivers deleted automatically and without sending the
usual inquiry message that it has not been saved

• DLTRCV(*YES) uses
ƒ Journaling for commitment control or explicit access path protection
ƒ Journal receiver is being replicated through remote journal

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-24. System change journal management

The Manage receivers (MNGRCV) parameter is used to specify how the changing of journal receivers
(detaching the currently attached journal receivers and attaching new journal receivers) is
managed. The possible values are *USER or *SYSTEM.
The Delete receivers (DLTRCV) parameter is used to specify whether the system deletes journal
receivers when they are no longer needed or leaves them on the system for the user to delete after
they have been detached by system change-journal management or by a user-issued CHGJRN
command.

Note

This parameter can be specified only if MNGRCV(*SYSTEM) is specified.

The possible values are:

*NO
The journal receivers are not deleted by the system. It is underlined because it is the default value
for this parameter.

© Copyright IBM Corp. 2001, 2016 21-31

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
*YES
The journal receivers are deleted by the system.
When the journal has the DLTRCV(*YES) attribute, the following conditions can prevent the system
from deleting the receiver. When one of these conditions occurs, the system sends message
CPI70E6 to the journal message queue, and then retries the delete operation every 10 minutes
until the operation is successful.
• A lock conflict occurs for either the journal receiver or its journal.
• An exit program that was registered by way of the QIBM_QJO_DLT_JRNRCV exit point indicates
that a receiver is not eligible for deletion.
• A journal has remote journals associated with it and one or more of the associated remote
journals do not yet have full copies of this receiver.
Use automatic deletion of journal receivers with care if you use save-while-active operations to
save objects before they reach a commitment boundary. Ensure that you save the journal receivers
before the system deletes them. If an object is saved before it reaches a commitment boundary it
can have partial transactions. To avoid data loss, you must have access to the journal receivers that
were attached during the save-while-active operation when you restore the objects with partial
transactions.

© Copyright IBM Corp. 2001, 2016 21-32

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Journal receiver chain

J PR RCV0006

RCV0007
J NR RCV0008

J PR RCV0007

RCV0008
J NR RCV0009

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-25. Journal receiver chain

The PR and NR entries are automatically added when a receiver is created or changed. They are
used by the system to make recovery seamless across a journal receiver chain.
PR stands for previous receiver.
NR stands for next receiver.

© Copyright IBM Corp. 2001, 2016 21-33

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

WRKJRNA command

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-26. WRKJRNA command

The Work with Journal Attributes display shows the current attributes of this journal and the names
of the journal receivers that are currently attached to this journal, if any.
You can use function keys to display lists of objects associated with this journal. You can request
the following lists:
• F13 - Files journaled to this journal
• F14 - Access paths journaled to this journal
• F15 - Receivers that have been used or are being used by this journal
• F16 - Remote journal information
Some of these lists or options are not available when working with an internal system journal
(*INTSYSJRN for JRN).
The type of journal, the possible values are:
• *LOCAL - A local journal
• *REMOTE - A remote journal

© Copyright IBM Corp. 2001, 2016 21-34

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
Journal state
The journal state describes an attribute for a journal. The attribute value can be *ACTIVE, *INACTIVE
(remote journal only), or *STANDBY (local journal only). For a local journal, *ACTIVE indicates that
journal entries are currently allowed to be deposited into the journal. *STANDBY indicates that most
journal entries are not deposited.
The state of the journal, the possible values are:
• *ACTIVE: If this is a local journal, this means journal entries can be deposited to this journal. If
this is a remote journal, this means journal entries can be received from a source journal.
• *INACTIVE: If this is a local journal, this means journal entries cannot be deposited to this
journal, unless they have been designated as journal entries which must be deposited. See the
'Journal Entry Information' IBM Knowledge Center for the journal entry designations. If this is a
remote journal, this means journal entries cannot be received from a source journal.
• *FAILED: If this is a remote journal, this means journal entries cannot be received from a source
journal due to a remote journal function failure, such as a communication line failure. Before
inactivating the remote journal by issuing the Change Remote Journal (CHGRMTJRN) or the
Change Journal (CHGJRN) command or by calling the Change Journal State
(QjoChangeJournalState) API, you might want to receive, retrieve, or display any unconfirmed
entries from the journal.
• *STANDBY: This is the state of a local journal after the Change Journal (CHGJRN) command
specifying JRNSTATE(*STANDBY) is used to not allow deposits into the local journal. The local
journal can also be in *STANDBY state after an IPL if the local journal is in *STANDBY state when
the system ends. Objects journaled to the local journal can be restored or changed, but most
journal entries are not deposited until the journal state for the local journal is again changed to
*ACTIVE. This can be performed by using the Change Journal (CHGJRN) command specifying
JRNSTATE(*ACTIVE).
• This value does not apply to local journals.

© Copyright IBM Corp. 2001, 2016 21-35

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

F15 = Work with Receiver Directory

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-27. F15 = Work with Receiver Directory

The Work with Receiver Directory display shows a list of all journal receivers that are associated
with this journal, if any. You can reach this screen by pressing function key F15 Work with receiver
directory. The list of receivers is ordered from the oldest (first attached) at the top of the list, to the
newest (currently attached) at the bottom of the list.
You can make selections on the list to:
• 8 - Display the attributes of the selected receivers
• 4 - Delete the selected receivers
Number column
A number is associated with a journal receiver and assigned by the system which is relative to all
other receivers in the receiver directory at a given time. The first 2 digits identify the journal chain
number and the last 3 digits identify the receiver number within the chain.
A chain identifies a group of receivers that are contiguous allowing the system to process entries
across receivers within the same chain.
The chain number starts with zero and is incremented sequentially each time a new chain is
needed. New chains are started when a damaged receiver is recovered by restoring a partial
version.

© Copyright IBM Corp. 2001, 2016 21-36

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty
Status column
The status of the receiver can be one of the following:
ATTACHED: The receiver is currently attached to the journal.
ONLINE: The receiver is online. The receiver has not been saved and it has been detached from
the journal.
SAVED: The receiver was saved after it was detached. The receiver storage was not freed when it
was saved.
FREED: The receiver was saved after it was detached. The receiver storage was freed when it was
saved.
PARTIAL: The receiver status is partial for one of the following reasons:
• It was restored from a version that was saved while it was attached to the journal. Additional
journal entries might have been written that were not restored.
• It was one of a pair of dual receivers, and it was found damaged while attached to the journal.
The receiver has since been detached. This receiver is considered partial because additional
journal entries might have been written to the dual receiver.
• It is associated with a remote journal and it does not contain all the journal entries that are in the
associated journal receiver attached to the source journal.
DELETED: The receiver has been deleted. This status is shown after option 4 (Delete) completes.
If you refresh (F5) the list, deleted receivers are removed from the list.

© Copyright IBM Corp. 2001, 2016 21-37

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Exercise: Journal management

• At the end of the lab, you should be able to:
ƒ Create journal
ƒ Display journaled objects
ƒ Change journal receiver

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-28. Exercise: Journal management

© Copyright IBM Corp. 2001, 2016 21-38

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Review questions (1 of 3)
1. Which of the following is not a valid object that can be
journaled?
a. Database files
b. Data area
c. Data queue
d. Root folders

2. A (blank) is a program that intercepts activity to an object

that is being journaled.
a. Journal
b. Journal receiver
c. Trigger
d. Referential constraint

3. What is the first object that needs to be created when you

start journaling?
a. Journal audit trail
b. Journal receiver
c. Journal
d. Journal access path

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-29. Review questions (1 of 3)

© Copyright IBM Corp. 2001, 2016 21-39

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Review answers (1 of 3)
1. Which of the following is not a valid object that can be journaled?
a.Database files
b.Data area
c.Data queue
d.Root folders
The answer is root folders.

2. A journal is a program that intercepts activity to an object that is being

journaled.
a.Journal
b.Journal receiver
c.Trigger
d.Referential constraint
The answer is journal.

3. What is the first object that needs to be created when you start
journaling?
a.Journal audit trail
b.Journal receiver
c.Journal
d.Journal access path
The answer is journal receiver.
Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-30. Review answers (1 of 3)

© Copyright IBM Corp. 2001, 2016 21-40

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Review questions (2 of 3)
4. Which object contains the images and details of the objects
that are being journaled?
a. Journal audit trail
b. Journal receiver
c. Journal
d. Journal access path

5. What is the command used to create the journal?

a. CRTJRN
b. CRTJRNRCV
c. STRJRNAP
d. STRJRNPF

6. True or False: The management of journal receivers is

something that must be done by the database administrator.

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-31. Review questions (2 of 3)

© Copyright IBM Corp. 2001, 2016 21-41

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Review answers (2 of 3)
4. Which object contains the images and details of the objects that are being
journaled?
a. Journal audit trail
b. Journal receiver
c. Journal
d. Journal access path
The answer is journal receiver.

5. What is the command used to create the journal?

a. CRTJRN
b. CRTJRNRCV
c. STRJRNAP
d. STRJRNPF
The answer is CRTJRN.

6. True or False: The management of journal receivers is something that must

be done by the database administrator.
The answer is false.

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-32. Review answers (2 of 3)

© Copyright IBM Corp. 2001, 2016 21-42

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Review questions (3 of 3)
7. The (blank) command is used to see the attributes
associated with your journal.
a. WRKJRN
b. CRTJRN
c. DSPJRNA
d. WRKJRNA

8. What command is used to review the details of objects being

journaled?
a. WRKJRN
b. DSPJRN
c. WRKJRNA
d. DSPJRNA

9. True or False: When displaying journal information, you can

specify to only show transactions performed by a specific
program.

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-33. Review questions (3 of 3)

© Copyright IBM Corp. 2001, 2016 21-43

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Review answers (3 of 3)
7. The WRKJRNA command is used to see the attributes associated with
your journal.
a. WRKJRN
b. CRTJRN
c. DSPJRNA
d. WRKJRNA
The answer is WRKJRNA.

8. What command is used to review the details of objects being

journaled?
a. WRKJRN
b. DSPJRN
c. WRKJRNA
d. DSPJRNA
The answer is DSPJRN.

9. True or False: When displaying journal information, you can specify to

only show transactions performed by a specific program.
The answer is true.
Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-34. Review answers (3 of 3)

© Copyright IBM Corp. 2001, 2016 21-44

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 21. Journaling overview and basic operation

Uempty

Unit summary
• Describe how journal management can be used to recover data lost
during a failure
• Implement journal management on your IBM Power System with IBM i
as part of a comprehensive recovery plan
• List the advantages and considerations of journal management

Journaling overview and basic operation © Copyright IBM Corporation 2001, 2016

Figure 21-35. Unit summary

© Copyright IBM Corp. 2001, 2016 21-45

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Unit 22. Virtual IP versus EtherChannel

Estimated time
00:45

Overview
There are few methods to communicate IBM i system with network in this unit shows two of them
Virtual IP and EtherChannel. However, intention of this unit is not teach how make configuration the
process is shown. But the main target is understood how the configurations works.

How you will check your progress

• Review questions

© Copyright IBM Corp. 2001, 2016 22-1

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Unit objectives
• Explain EtherChannel and Virtual IP differences
• Explain how works EtherChannel
• Explain how works Virtual IP
• Be able to manage both solutions

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-1. Unit objectives

There are few methods to communicate IBM i system with network in this unit shows two of them
Virtual IP and EtherChannel. However, intention of this unit is not teach how make configuration the
process is shown. But the main target is understood how the configurations works.

© Copyright IBM Corp. 2001, 2016 22-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Topic 1: EtherChannel

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-2. Topic 1: EtherChannel

© Copyright IBM Corp. 2001, 2016 22-3

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

EtherChannel

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-3. EtherChannel

Link aggregation, which is defined by the Institute of Electrical and Electronics Engineers (IEEE) as
802.3ad or 802.1ax, provides both redundancy and performance advantages. When properly
implemented, link aggregation can both increase the resiliency of your system to network failures
and provide a significant performance benefit. This tip refers to the technology as aggregation;
however, it is also known as EtherChannel, teaming, or trunking.

© Copyright IBM Corp. 2001, 2016 22-4

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

EtherChannel required resources

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-4. EtherChannel required resources

Before you create an aggregate line description, select the Ethernet resources to be aggregated.
Up to eight ports can be aggregated in one line description.
None of the ports can be in use by another line description, LAN console, or remote support.
Virtual Ethernet ports (type 268C) are not supported in an aggregate line description.
A Host Ethernet Adapter (HEA) logical port, native SR-IOV logical port, or virtual NIC (VNIC) port is
only supported if it is the only logical port on its corresponding physical port, and if the aggregate
line uses the Link Aggregation Control Protocol (LACP) by specifying *LNKAGG in the Aggregate
Policy (AGGPCY) for the line description. Any other configuration can prevent the link partner from
detecting faults, causing lost packets.
All of the ports must support full duplex and the preferred line speed. Each port must support 1
Gbps or higher, even if that is not the preferred line speed.
All of the ports must be connected to the same link partner (switch).
If you use static aggregation (*ETHCHL), all of the corresponding ports on the link partner must be
configured in a common static aggregation. If you use LACP (*LNKAGG), configure all of the
corresponding ports on the link partner with LACP and share a common key.

© Copyright IBM Corp. 2001, 2016 22-5

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty
IBM i Link Aggregation supports static aggregation (*ETHCHL) with any link partner, and supports
LACP (*LNKAGG) with Cisco and IBM Networking switches. Other LACP-capable link partners
might work, but are not officially supported.

© Copyright IBM Corp. 2001, 2016 22-6

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

EtherChannel creating line description (1 of 3)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-5. EtherChannel creating line description (1 of 3)

Use the WRKLIND command to work with all line description then press function key F6 to create
new one. Enter the line name and type *ELAN.

© Copyright IBM Corp. 2001, 2016 22-7

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

EtherChannel creating line description (2 of 3)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-6. EtherChannel creating line description (2 of 3)

An aggregated line description is created by using the Create Line Desc (Ethernet) (CRTLINETH)
command.
The following parameters are relevant to aggregation: Resource Name (RSRCNAME): set to new
special value *AGG to indicate aggregation.
Duplex (DUPLEX): Half duplex is not supported.
Aggregated Resource List (AGGRSCL): up to eight Ethernet port resource names (starting with
CMN) with the restrictions laid out in Preparing to Create an Aggregate Line Description.
Aggregate Policy (AGGPCY): This parameter is split into two elements. The Standard controls any
negotiation that is done with the link partner, and requires specific configuration with the link
partner, as described under *ETHCHL and *LNKAGG. The Policy type describes the process for
deciding what port is used for each outgoing Ethernet frame; this type can have performance
implications.
Choosing *ETHCHL as the Standard uses static aggregation, which performs no negotiation with
the link partner. The link partner must also be configured for static aggregation. The Ethernet ports
in the Aggregated Resource List (AGGRSCL) and the set of ports that are configured at the link
partner should correspond exactly. If they do not, then some Ethernet packets might not get to the
correct destination. There are several opportunities for error: Having ports in AGGRSCL that are

© Copyright IBM Corp. 2001, 2016 22-8

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty
connected to a different link partner or to the wrong ports in the correct link partner, or having ports
that are selected in the link partner's aggregate that are connected to ports not in AGGRSCL.
Setting the Standard as *LNKAGG forces use of the Link Aggregation Control Protocol (LACP) as
described in the IEEE 802.3ad standard. This negotiation detects the identity of the link partner for
each Ethernet port in the Aggregated Resource List (AGGRSCL). This Standard requires that the
link partner to enable LACP with common identification information on all ports that are connected
to ports in AGGRSCL. In order for a port to aggregate and be used for Ethernet traffic, its partner
port must respond to the LACP negotiation, and the response must match the identifying
information to all other aggregated ports. The aggregation panel in Display Line Description
(DSPLIND) shows the aggregation status of each port, and the status helps describe why any other
ports are not aggregated.
The round-robin (*RNDRBN) is only accepted if Standard is *ETHCHL, and it directly forces each
batch of outgoing packets to use the next available port, ensuring that all ports are used in
near-equal fashion. However, that creates risk that packets can be delivered out of order, and
out-of-order delivery within a TCP connection causes retransmissions and large delays. Use this
option only if that is not a concern.
The remaining policy types could all be called hash modes, and they describe what data within a
packet is used to determine which Ethernet port is used for each outgoing frame. All of the hash
modes force a specific TCP connection to stay single-threaded on a specific Ethernet port to avoid
the out-of-order delivery problem. They differ in how much packet data is used to decide which port
to use. The best network usage comes from configurations that split outgoing traffic roughly equally
among the ports in the Aggregated Resource List (AGGRSCL). As more packet data is used, the
system can do more to spread unrelated traffic among the ports. However, using more packet data
also forces some additional processing and cache usage for each outgoing packet.
The *DFT hash mode uses the least amount of data, looking only at the destination IP address (or
MAC for non-IP frames). This mode uses little processor, but spreads evenly only if traffic is running
too many different IP addresses at the same time (as for a busy server).
The *SRCPORT, *DESTPORT, and *SRCDESTP hash modes also look at the source and
destination TCP or UDP port numbers (if present) for each outgoing packet. This evaluation incurs
more per-packet processing, but is better able to split unrelated traffic among multiple Ethernet
ports, like parallel file transfers to the same remote host. If host processor is not known to be a
constraint, *SRCDESTP is likely the best choice for most systems.
To create a static two-port aggregate that uses as much packet data as possible to spread outgoing
traffic, use the following example:
CRTLINETH LIND(ETHAGG) RSRCNAME(*AGG) AGGPCY(*ETHCHL *SRCDESTP) AGGRSCL(CMN02
CMN03)

© Copyright IBM Corp. 2001, 2016 22-9

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

EtherChannel creating line description (3 of 3)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-7. EtherChannel creating line description (3 of 3)

After line VARY ON you can check the status of physical resources. On the Work with Line
Description screen use option 5 and press Enter seven times to see status of each physical
adapter.

© Copyright IBM Corp. 2001, 2016 22-10

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

EtherChannel new resources

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-8. EtherChannel new resources

A non-aggregate line description cannot be changed to an aggregate line description, nor can an
aggregate be changed later into a non-aggregate. The AGGPCY and AGGRSCL parameters can be
changed by the Change Line Desc (Ethernet) (CHGLINETH) command, but the line description
must be varied off.
When the line description is varied on, the configuration is verified and all of the resources are
activated and establish link with the partner. If the system detects any configuration errors, the line
description does not vary on successfully. Any ports that fail to establish link when varying on are
not aggregated until the line description is varied off and back on.
After the line description is varied on, the aggregation status of each resource can be viewed on a
new panel from the Display Line Description (DSPLIND) command. The DSPLIND command can
be used to monitor for any links that are not operational.
On systems with support for link aggregation, resources with type 6B26 are displayed on the Work
with Communication Resources panel. This panel can be displayed by using the Work with
Hardware Resources (WRKHDWRSC) command and the Type (TYPE) parameter of *CMN. When an
aggregate line description is varied on for the first time, a new Comm Port resource with type 6B26
might be added. When an aggregate line description is deleted, one of the Comm Port resources
might be removed. All resources with type 6B26 are invalid for configuration by line descriptions or
for LAN console or remote support. When an aggregate line description is deleted, a resource with
type 6B26 might no longer be displayed on the Work with Communication Resources panel.

© Copyright IBM Corp. 2001, 2016 22-11

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Topic 2: Virtual IP

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-9. Topic 2: Virtual IP

© Copyright IBM Corp. 2001, 2016 22-12

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP resources

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-10. Virtual IP resources

Easier way create and manage Virtual IP is using IBM Navigator for i:
Before you start make sure you have two Ethernet adapters (virtual / physical) and created two
interfaces on it.
To create Virtual Interface by using IBM Navigator for i do:
• On the left pane, expand Network.
• Then, expand TCP/IP Configuration and IPv4.
• Click the IPv4 Interfaces.
• On the main pane click Actions and from the pop-up menu select New Interface and Virtual
IP.
A virtual IP interface defines a single IP address that can be used to redirect TCP/IP traffic to other
interfaces or networks.
Virtual IP interfaces are useful for TCP/IP load balancing, network address translation (NAT), frame
relay multi-access, and unnumbered networks.
The wizard will take you through the steps that are needed to configure a TCP/IP interface.

© Copyright IBM Corp. 2001, 2016 22-13

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP wizard (1 of 4)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-11. Virtual IP wizard (1 of 4)

On the wizard welcome page click Next.

© Copyright IBM Corp. 2001, 2016 22-14

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP wizard (2 of 4)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-12. Virtual IP wizard (2 of 4)

Enter Virtual IP address. The virtual IP address must be on the same subnet as the physical
interfaces.

© Copyright IBM Corp. 2001, 2016 22-15

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP wizard (3 of 4)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-13. Virtual IP wizard (3 of 4)

Depending on the requirements setup startup options and click Next.

© Copyright IBM Corp. 2001, 2016 22-16

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP wizard (4 of 4)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-14. Virtual IP wizard (4 of 4)

Review summary and confirm creation with Finish. After you can test the interface if you want to or
go on by click OK.

© Copyright IBM Corp. 2001, 2016 22-17

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP created

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-15. Virtual IP created

Now your Virtual IP interface is created but before it is ready it needs some more work.

© Copyright IBM Corp. 2001, 2016 22-18

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP associate physical interface (1 of 4)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-16. Virtual IP associate physical interface (1 of 4)

You have to assign physical interfaces to your Virtual IP. To do that on the virtual IP interface
right-click and chose Properties.

© Copyright IBM Corp. 2001, 2016 22-19

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP associate physical interface (2 of 4)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-17. Virtual IP associate physical interface (2 of 4)

On the properties click Advanced tab and in the Proxy ARP field chose Preferred interface and
click OK.

© Copyright IBM Corp. 2001, 2016 22-20

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP associate physical interface (3 of 4)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-18. Virtual IP associate physical interface (3 of 4)

On this screen you can select Available interfaces (left side) and use the Add button to add
interfaces to manage. Use the Move Up or Move Down button to select which one will be
preferred.

© Copyright IBM Corp. 2001, 2016 22-21

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP associate physical interface (4 of 4)

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-19. Virtual IP associate physical interface (4 of 4)

After you setup the preferred IP (on the previous screen) physical address and confirm your choice
by pressing the OK button, you will see the interfaces list preferred physical IP address (associated
interface) for your virtual IP address.

© Copyright IBM Corp. 2001, 2016 22-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP change preferred interface

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-20. Virtual IP change preferred interface

If preferred interface fails or stops the virtual IP interface will automatically switch to spare IP
address. After the preferred interface is repaired or restarted the virtual IP interface will switch back
to the preferred interface.

© Copyright IBM Corp. 2001, 2016 22-23

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Virtual IP 5250

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-21. Virtual IP 5250

The same can be done with 5250:

ADDTCPIFC INTNETADR('192.168.1.10') LIND(ETHV1) SUBNETMASK('255.255.255.0')
ADDTCPIFC INTNETADR('192.168.1.11') LIND(ETHV2) SUBNETMASK('255.255.255.0')
ADDTCPIFC INTNETADR('192.168.1.200') LIND(*VIRTUALIP)
SUBNETMASK('255.255.255.255')
CHGTCPIFC INTNETADR('192.168.1.200') PREFIFC('192.168.1.10' '192.168.1.11‚)

© Copyright IBM Corp. 2001, 2016 22-24

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Review questions
1. True or False: Virtual Ethernet adapter can be used to create
EtherChannel.

2. True or False: Virtual IP can be created on both interface

IBM Navigator for i and 5250 interface.

3. True or False: When preferred interface in Virtual IP failed or

stopped you need manually change the preferred interface.

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-22. Review questions

© Copyright IBM Corp. 2001, 2016 22-25

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Review answers
1. True or False: Virtual Ethernet adapter can be used to
create EtherChannel.
The answer is false.

2. True or False Virtual IP can be created on both interface

IBM Navigator for i and 5250 interface.
The answer is true.

3. True or False: When preferred interface in Virtual IP failed or

stopped you need manually change the preferred interface
The answer is false.

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-23. Review answers

© Copyright IBM Corp. 2001, 2016 22-26

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0
Unit 22. Virtual IP versus EtherChannel

Uempty

Unit summary
• Explain EtherChannel and Virtual IP differences
• Explain how works EtherChannel
• Explain how works Virtual IP
• Be able to manage both solutions

Virtual IP versus EtherChannel © Copyright IBM Corporation 2001, 2016

Figure 22-24. Unit summary

© Copyright IBM Corp. 2001, 2016 22-27

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.0

backpg

© Copyright International Business Machines Corporation 2001, 2016.