Ibm i Administration

Welcome to:

IBM i System Administration

Powertm with IBM i © Copyright IBM Corporation 2012 Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

7.0

Facilities IBM i

• Class hours • Breaks • Phones • Messages • Restrooms • Emergency exits • Smoking policy • Eating establishments • Cell phones and pagers • Internet access

© Copyright IBM Corporation 2012

Introducing IBM i

• Name • Title or position • Company or organization • City and state • Experience with Power Systems with IBM i • Expectations


Course objectives IBM i

After attending this course, the student should be able to: • Describe the features, functions, and benefits of the Power Systems with IBM i relevant to security • Describe the security requirements for your Power Systems with IBM i • Identify the system security features that satisfy your requirements • Describe and implement the features and facilities of the Power Systems with IBM i available to audit security • List the elements of a security plan • Describe the features, functions, and benefits of the Power Systems with IBM i relevant to availability and recovery • List the elements of a security plan and a backup and recovery plan • Describe Power Systems with IBM i problem determination and resolution techniques • Perform these activities using either a green screen 5250 emulation session (through command line entry), by using System i Navigator, or the Systems Director Navigator for IBM i © Copyright IBM Corporation 2012

Introducing e-Lab IBM i

Introduction to e-lab


IBM firewall overview (specific details next page) IBM i


Step 1: Access the Citrix system IBM i

Enter: https://elabgateway.moppssc.com

Notice the https! © Copyright IBM Corporation 2012

Step 2: Sign on to the Citrix client session IBM i

Log on with the User name and Password (unique for each student) assigned by your instructor. © Copyright IBM Corporation 2012

Step 3: Sign on to the Citrix client session IBM i

Click the icon Remote Desktop Connection


Step 4: Sign on to the Windows client IBM i

Userid: Password:

student passw0rd (notice the zero instead of of the letter o) © Copyright IBM Corporation 2012

Step 5A: Accessing the lab systems (details on next page) IBM i

• Use the Citrix desktop and directions from your instructor to access: – 5250 emulation – System i Navigator – Web browser > Systems Director Navigator for i


Step 5B: Make client window full screen IBM i

Make the Citrix/VMWare/Windows Client full screen


Hint: Use the top Start bar for Citrix client IBM i


Write down required information IBM i

• Write down the following information that you will need to know and use for the rest of the week. • First thing every morning, start the e-lab environment: – e-lab user ID ____________ (xx=your team # assigned by instructor) – e-lab pw ____________ (assigned by instructor)

• To sign on to the Power System with IBM i, make note of your: – user ID – pw

______________ (xx=your team # assigned by instructor) ______________ (is set to expire; student changes at first sign-on)

• At the end of the day, sign off and disconnect your e-lab connection. – The e-lab environment is only available during the week of class. – Optionally, you can sign on to the lab system and perform the labs in the evening (from your hotel room or from home). © Copyright IBM Corporation 2012

Words of wisdom IBM i

OL19 BRMS

BRMS

Enjoy the class! © Copyright IBM Corporation 2012

IBM i overview and concepts


7.0

Unit objectives IBM i

After completing this unit, you should be able to: • Describe the IBM Power Systems with IBM i architecture • Describe what objects are on the IBM i • Explain the syntax of IBM i control language (CL) commands • Explain the concepts of libraries, library list, and jobs • Explain the concepts of printing on the IBM i • Explain the device description and creation process


Power Systems with IBM i: Integrated by design IBM i

IBM POWER Systems with IBM i

Traditional systems

IBM i • Higher-level functions exposed to users and applications based on SLIC services • Graphical user interface • Vast range of high-level language functions (C/C++, RPG, COBOL)

Directory Backup and recovery un Comm

ication

s

Online transaction processing

Technology-independent machine interface System licensed internal code • Process control • Resource management • Integrated SQL-compliant database • Security enforcement • Network communications • File systems • Storage management • Java virtual machine (JVM) • Other primitives

Security

Relational database

Java

Sys man tems agem ent

Operating system Hardware and microcode

64-bit POWER5+, POWER6, POWER7


Technology-independent machine interface IBM i

Programs

TIMI

SLIC 64-bit RISC hardware


POWER Hypervisor IBM i

Programs i

Programs AIX 5L

Programs Linux

OF / RTAS

OF / RTAS

TIMI

SLIC

POWER Hypervisor 64-bit RISC hardware


Innovative IBM i technology IBM i


Power Systems with IBM i expand rich heritage IBM i

A technology-friendly architecture supporting continuous innovation without disruption AS/400e

iSeries

AS/400

System i


eServer i5

The IBM Power Systems family IBM i

Innovative, proven technology providing platform choice to match unique business needs

BladeCenter Simplify data center complexity.

System z The flagship for IBM Systems innovation and the heart of a highly secure, resilient and integrated infrastructure.

IBM Power Systems Install faster, maintain easier. Get the power to do more, spend less.

System x Innovation comes standard.

System Storage Connected. Protected. Complete. © Copyright IBM Corporation 2012

The Power Systems with IBM i product line IBM i

780 8-64 way

770 8-64 way

755 1-4 way

750 1-4 way

Mid-sized to large enterprises Small to mid-sized enterprises All models also support integration with System x and BladeCenter running Windows or Linux. © Copyright IBM Corporation 2012

CPU models IBM i

• System i models – Machine type (xxxx)

• 9402, 9404, 9406, Power Systems with IBM i – Model (aaa)

• • • • • • • • •

Bxx, Cxx, Dxx, Exx, Fxx, 3xx, 5xx, 6xx nnS, Sxx, 150, 170 250, 270, 7xx, 8xx i825, i830, i840, i870, i890 515, 520, 525, 550, 570, 596, POWER6 (520, 570, 595) POWER7 (710, 720, 730, 740, 750, 755, 770, 780, 795) Each with different throughput

– Capacities

• Measured by commercial processing workload (CPW) – Largest CPW is 399.200 on model 795

• Processor architecture – Speeds of up to 4.25 GHz – Cache size (level-1, 2, 3) – Parallel threads management


1995 1995 Cobra Cobra

2006 2010 POWER 7

Transistor count

4.7M

1,2B

Frequency

50 MHz

Up to 4.25 GHz

Logical partitions

None

Up to 1000

Single-level storage IBM i

Virtual address space with objects PROGRAM

DATA

PROGRAM

PROGRAM

DATA

PROGRAM

DATA

PROGRAM

DATA

DATA

DATA PROGRAM

Auxiliary storage © Copyright IBM Corporation 2012

DATA

OUTPUT QUEUE

DATA USER PROFILE

Main storage

PROGRAM

DATA

JOB QUEUE PROGRAM

DATA

LIBRARY

Power Systems with IBM i devices IBM i

Input

Process

Processing unit


Output

Sample configuration IBM i

SDLC communications line

IBM Power System (Montreal) Workstation controller Console

Display

Order entry

LAN adapter

Tape unit

Diskette unit

Ethernet

Shipping and receiving

Modem

Display

Display

Controller Paris

Display

Accounting Display

CD-ROM unit

Display

Printer

Printer

Printer

Printer © Copyright IBM Corporation 2012

Software overview IBM i

Application support Programming support IBM i Licensed internal code


Licensed internal code IBM i

Licensed internal code (LIC) is a group of programs located in storage that allow IBM i to run on different processor models.


Operating system IBM i (1 of 2) IBM i

• Operating system (5770-SS1) • Previously called OS/400 and i5/OS • Currently named IBM i (at V7R1, V6R1, and V5R4)

– Database management system • DB2 for i

– Support for applications native to other operating systems • UNIX application programming interfaces (APIs) – Provide conformity to many UNIX standards

• Portable Application Solutions Environment (PASE) – AIX-based applications

– AIX support • Guest operating system

– Integrated xSeries server • Intel-based applications

– Linux support • Guest operating system


Operating system IBM i (2 of 2) IBM i

• System resource management – Processors – Memory – Disk

• System control interface – CL support • High-level programming language

– System or user-written commands

• Integrated support for: – Security – Communications • Systems Network Architecture (SNA), Transmission Control Protocol/Internet Protocol (TCP/IP) • Windows Network Neighborhood support • HTTP/Apache and so forth

– System management • System-managed access-path protection (SMAPP) • System i Navigator – Management Central – Director Navigator for i


Programming support IBM i

Java

ILE C

ILE RPG

ILE COBOL

HATS

Rational Developer for Power Systems

WebFacing SQL


Application software IBM i

• Traditional applications – Workload • Interactive, character-based (5250 or green screen) – Interactive capacity (ICPW)

• Batch (no ongoing user interaction) – Total capacity (CPW)

– Support through specific IBM i jobs • Application users are IBM i users – More detail covered in the work management unit

• Client/server applications – Workload • Information processing – Interactive – Batch

• Database serving – Native IBM i server applications – Third-party, pre-written server applications

• Interaction with IBM i jobs – Application users might or might not be known to IBM i > For example, SAP R/3: Specific users known only to the application > For example, BaanERP: Specific users known to IBM Power Systems with IBM i


Display installed software on a system IBM i


CL command structure IBM i

Command name

CRTLIB Action

Item abbrev.

Parameter

LIB(PAYLIB) Keyword


Value

Library IBM i

Object name FILEC PROGA DSPJOB

Type *FILE *PGM *CMD

Location ## @@ %%

PROGA FILEC

DSPJOB


Object identification (1 of 2) IBM i

Library, name, type Library QSYS

Library PAYROLL

Program MASTER

File MASTER

Library OPRLIB

File MASTER


File ACCOUNTS

Object identification (2 of 2) IBM i


Simple name versus qualified name IBM i

Simple name:

PGM1

versus

Qualified name:

LIB1/PGM1 Library name


Object name

Library list IBM i

System libraries (15 maximum)

QSYS QSYS2 QHLPSYS QUSRSYS

Product libraries

QRPGLE QCBLLE

Current library

PAYLIB

User libraries (250 maximum)

*LIBL

*CURLIB

QGPL QTEMP PAYTSTLIB

One associated with every job


*USRLIBL

Your job's library list is built at sign-on IBM i

QSYSLIBL QSYS QSYS2 QHLPSYS QUSRSYS

QUSRLIBL QGPL QTEMP

QSYS QSYS2 QHLPSYS QUSRSYS

}

}

System part

}

Program product part Current library

FREDLIB

} 1

Job Descr INLLIBL QGPL QTEMP PAYLIB

}

QGPL QTEMP PAYLIB

}

User part

USER PROFILE CURLIB(FREDLIB)

2

SIGN ON CURRENT LIBRARY FREDLIB

1 The job description can override system value QUSRLIBL 2 Value entered on Sign On panel overrides value in profile © Copyright IBM Corporation 2012

Finding an object IBM i

Simple name: CALL PAY02 Qualified name: CALL PAYTSTLIB/PAY02 QSYS QCWW QCXXX

QCZZZ QCYYY

PAYTSTLIB

INQLIB PAY77

PAY99

AP60

AP55

Job's library list QSYS QSYS2 QHLPSYS QUSRSYS QRPG QCBL

PAYLIB

System libraries

Product libraries

Current library

PAYLIB AP55

PAY01

PAY02

AP05

PAY01

PAY02

PAY04

PAY05


QGPL QTEMP PAYTSTLIB INQLIB

User libraries

Types of jobs IBM i

Job: A unit of work to be done by the system User jobs Interactive System jobs Batch Spooling

Autostart Communication

Qualified job name: Consists of the following three parts: Job number User name Job name 003945 / SMITH / PRTINV © Copyright IBM Corporation 2012

Starting and ending a job IBM i

Job type

Start

End

Interactive

Sign-on

Sign off

Batch

Placed on jobq

EOJ

Autostart

Start subsystem

EOJ

Communication

Request from remote system

Same as batch or interactive

Spooling

Start writer command

End writer command


Job control summary IBM i

SBMJOB

JOBQ

BATCH OUTQ

WRITER

WRKOUTQ WRKSPLF

WRKWTR

INTERACTIVE

CALL WRKJOBQ

WRKACTJOB

WRKUSRJOB WRKSBMJOB

or System i Navigator © Copyright IBM Corporation 2012

PRINTER

Job properties (1 of 2) IBM i


Job properties (2 of 2) IBM i


What is a job description? IBM i


Job description attributes IBM i

• A job description contains a specific set of job-related attributes: – Initial library list – Which job queue to use – Scheduling priority – Routing data – Message queue severity – Output queue information – User parameter

• The attributes determine how each job is run on the system. • QDFTJOBD is a system-supplied job description in library QGPL. © Copyright IBM Corporation 2012

Message summary IBM i

• Messages – Send, display, respond, and remove – Informational, break, or inquiry

• Message queues – Allocate and change delivery mode – Break, notify, hold, and default


Basic message queue communication IBM i

PROFILE

{

DSP01

OPR01

CRTDEVDSP:

OPR01 DSP01

}

User message queue

CRTUSRPRF

Workstation message queue

CRTMSGQ:

ARDEPT

User-created message queue


QSYSOPR System supplied

System operator message queue

Which output queue? IBM i

Job description Job's process access group (PAG) Program Output to printer file

*USRPRF

( name )

OUTQ

User profile

Default output queue

OUTQ

(*WRKSTN ) name

Device description Printer file

SPOOL(*YES) OUTQ

*DEV

OUTQ

( name )

PRTDEV

(*SYSVAL name )

*JOB

( name )

System value QPRTDEV © Copyright IBM Corporation 2012

PRT01

( name )

Creating device descriptions IBM i

• Automatic: QAUTOCFG = '1' – Local workstation controllers – Local tape drives – Local diskette drives – Local printers – Local display station – Local area network

• Manual – Remote devices – Communications


Automatic configuration naming conventions IBM i

Device

*Normal

*S/36

*DEVADR

Workstation controller

CTL01

CTL01

Display stations

DSP01, DSP02 W1, W2

DSP(CPA)*

Printers

PRT01, PRT02 P1, P2

PRT(CPA)*

Diskette drive

DKT01

I1

Tape drive

TAP01

T1

Passthru device

QPADEV*

CTL01

SYSTEM VALUE: QDEVNAMING * C=Controller

P=Port

A=Device address


Additional objects required for remotes IBM i

Line

Remote workstation controller

*CTL CRTCTLRWS

Display

*DEV CRTDEVDSP

Printer

*DEV CRTDEVPRT

IBM i *LIN CRTLIN x x x


How the pieces fit together (1 of 3) IBM i

MSG Device description Device description Aut keyword AUT keyword

MSG User profile OUTQ

*WRKSTN *DEV name



User profile .

Current library . .

Initial program . .

Initial menu . .

Authorizations Special User class Password



JOBQ Job description . .

Job queue

Batch jobs awaiting execution

. .

Output queue . .

Main storage

Library list MSGQ

Messages awaiting view

User workstation © Copyright IBM Corporation 2012

OUTQ Output awaiting print

New systems management tool IBM i

• IBM Systems Director Navigator for i – New Web-based tool for managing i – Alternative to System i Navigator – Additions: • Performance Data Investigator • High Availability Solutions Manager – Automatic installation with i 6.1 and 7.1 – Plans to snap into IBM Systems Director*


How does Systems Director Navigator for i compare to System i Navigator? IBM i

• IBM Systems Director Navigator for i is intended for management of only the server where you point your web browser. (Note: In V7R1 you can select a target system.) – Management Central capabilities are not included. – You can use IBM Systems Director cross-platform products for multi-system management.

• Both are built from the same source code for consistent functionality. Panels look different when rendered on the Web console. • Single user can only sign in to one web console. – IBM Systems Director Navigator or System i Navigator URL Advisor

• Both can have functions restricted. – System i Navigator does not install functions. – Web console restricts users from specific tasks.


IBM Systems Director IBM i

See and manage physical and virtual resources across multiple systems. • Simplify platform management across server infrastructure. – Manage from a single console. – See if servers are healthy. – Monitor performance. – Maximize utilization. – Troubleshoot quickly. • Manage the life cycle of physical and virtual resources. – Keep system software up to date. – Deploy to multiple systems. © Copyright IBM Corporation 2012

Exercise: Exploring the user environment IBM i

At the end of the lab, you should be able to: • Create a library. • Create an output queue. • Create a job description. • Change your own user profile. • Change your current library. • Add/remove libraries to/from library list. • User ID: OL50xx • Password: OL50PWD – (The password is set to expire.)


Checkpoint (1 of 2) IBM i

1. True or False: The TIMI is a separately ordered software. 2. True or False: This system addresses both main storage (memory) and auxiliary storage (disk) using the same addressing scheme. 3. True or False: The LIC must be installed by the customer.


Checkpoint solutions (1 of 2) IBM i

1. True or False: The TIMI is a separately ordered software. The answer is false. 2. True or False: This system addresses both main storage (memory) and auxiliary storage (disk) using the same addressing scheme. The answer is true. 3. True or False: The LIC must be installed by the customer. The answer is false.



4. True or False: Java is not supported on this system. 5. True or False: Using a simple naming convention is the best method for locating or accessing an object on the system. 6. True or False: The new GUI that became available at V6R1 and V7R1 is Systems Director Navigator for IBM i.



4. True or False: Java is not supported on this system. The answer is false. 5. True or False: Using a simple naming convention is the best method for locating or accessing an object on the system. The answer is false. 6. True or False: The new GUI that became available at V6R1 and V7R1 is Systems Director Navigator for IBM i. The answer is true.


Unit summary IBM i

Having completed this unit, you should be able to: • Describe the IBM Power Systems with IBM I architecture • Describe what objects are on the IBM i • Explain the syntax of IBM i control language (CL) commands • Explain the concepts of libraries, library list, and jobs • Explain the concepts of printing on the IBM i • Explain the device description and creation process


Management Central overview


7.0


After completing this unit, you should be able to: • Describe the capabilities of Management Central • Create links to IBM Power Systems with IBM i • Define in Management Central the central system, endpoint systems, and system groups • Define and perform the major functions of Management Central


Topic 1: Introduction to Management Central


7.0

Command and graphical interfaces IBM i


Management Central: Basic overview (1 of 2) IBM i

• Suite of system management functions • GUI integrated into IBM i • Subset of System i Navigator • Fully integrated into Windows environment


Management Central: Basic overview (2 of 2) Firewall and Internet

IBM i

Endpoint systems

Target Central system Model

Web application server

Optional


Source

System group

Topic 2: Management Central setup


7.0

Packaging and installation IBM i

• Packaging – Server: 5770SS1 options *BASE and 0003 – Client: IBM Power System with IBM i running IBM i Access (5770-XE1)

• Client installation – Windows • • • • • •

2008 Server Windows 7 Windows Vista XP Server 2003 2000

– IBM Power System with IBM i running IBM i NetServer or CD – Custom or Full option

• TCP/IP only © Copyright IBM Corporation 2012

Basic and extended operations IBM i

• System i Navigator – – – – – – – – – – – – – – – –

Basic operations Work management Configuration and services Network Integrated server admin Security Users and groups Database File systems Backup Commands Packages and products Monitors Logical system AFP manager Application administration © Copyright IBM Corporation 2012

Configure connections IBM i

• Must create connection if none exists • First system configured automatically becomes the central system but can change at any time


Create Connection wizard (1 of 2) IBM i

User profile used on central system must exist on each endpoint system.

System to be connected © Copyright IBM Corporation 2012

Create Connection wizard (2 of 2) IBM i


Management Central server IBM i

• Integrated with other TCP/IP servers • Must be running on IBM Power System with IBM i to perform Management Central functions


Management Central properties IBM i

• Connection tuning • Security options – Require password on endpoint systems • Same as central system – Use Secure Sockets Layer (SSL)


Define central system IBM i

• • • •

First system under My Connections is default central system. This can change at any time. System to be managed must be in My Connections list. Any one of the systems in My Connections can be Management Central server.


Add endpoint systems IBM i

• Must be connected to central system using TCP/IP • Manual add shown below


Create system groups IBM i

• Create system groups by selecting endpoint systems to group together as one unit.


Advanced common functions IBM i

• Some functions are common and available to many Management Central items. – Sharing – Include and Columns options – Scheduling – Application administration – MC-pervasive


Global sharing IBM i

• Default for sharing all new tasks – Default is none

• Can be overridden at individual task level


Include and Columns options for displays IBM i

• Example of using Include option with Task Activity:

• Example of using Columns option with Task Activity command:


Management Central Scheduler IBM i

• Allows you to schedule all types of Management Central tasks • Allows you to select when you want a job to run on the system – Schedule once – Recurring schedule • Daily • Weekly • Monthly

• Default for scheduling tasks • Integrated into Management Central for the scheduling of tasks – No specific job scheduler container


Advanced Job Scheduler IBM i

• IBM licensed program product (5770-JS1) • GUI integrated into Operations Navigator • Overrides Management Central Scheduler • Becomes default scheduler • Provided as plug-in • CL commands • Calendaring • Job sequencing • Dependency scheduling • Job history/statistics • Report distribution • Pager capabilities © Copyright IBM Corporation 2012

Advanced scheduling IBM i

• View scheduled tasks – Select type of task

• Modify job scheduling – Advanced Job Scheduler • Scheduled job • Right-click job name on right panel • Select Properties • Modify scheduling on the next panel


Application Administration (1 of 3) IBM i

• Install as a component of System i Navigator • Controls access to functions • Opened system through Management Central or IBM Power System with IBM i connection



• At IBM Power System with IBM i connections: – System Director Navigator for i • All components

– Client applications • PC applications

– Host applications • Backup Recovery and Media Services (BRMS) • On demand • And so on



• At Management Central: – Commands – Packages and Products – Monitor – Users and Groups – Fixes – Inventory – System Values – Collection Services – Extreme Support


MC: Pervasive IBM i

• Wireless remote system monitoring • Devices – PDA – Web browsers – Internet phones


Topic 3: Management Central functions


7.0

Management Central functions IBM i

• Run commands • Create and distribute packages • Create, distribute, and install products • Monitor job, message, system, file, and B2B in real time • Access Collection Services (performance data collection) • Take inventory: – Track hardware configuration, software, fixes, system values, and users and groups. – Manage network and service attributes and contact information. – Compare and update system values. – Compare fixes and distribute and install missing fixes. – Synchronize date and time. – Scan for user-owned objects and users with search criteria.

• Manage users and groups and perform qualified search for users or groups. © Copyright IBM Corporation 2012

Run command (1 of 3) IBM i

• Running remote command – Create command definition – Perform command to multiple systems or groups – Schedule recurring commands – View status, job log, and output – Keep job log – Handle inquiry






Object packaging and distribution (1 of 3) IBM i

• Managing software – Create package definition • Objects – – – –

Configuration data Java applications Web files Software programs

• Integrated file system (IFS) • Post-distribution actions

– Create package snapshots – Distribute package to multiple systems or groups – Schedule recurring distributions – View status, job log, and output






Manage products IBM i

• Create and distribute a product – Create product definition – Install product on its source system – Send and install product to multiple systems or groups – Run remote command after installation – View status, job log, and output


Create products on source system IBM i

• Management Central – Definitions • Product

• Welcome wizard explains create procedure


Install products on source system IBM i

• Installation opens Welcome wizard


Send and install products IBM i

• Product must be installed (or managed) in order to: – Send and install to another system – Send and install (delayed) – Generate fixes


System monitor (1 of 4) IBM i

• Use graphical display of real-time performance data across one or more systems – One or more performance metrics • 26 metrics – Thresholds for each monitored metric • Up to two thresholds for each metric – Indicates threshold reached with ability to initiate action

• Monitor a single system from multiple PCs • Monitor multiple systems from a single PC • Determine status – Identifies monitors with triggered thresholds – Identifies whether or not monitors are running

• Distinguish between systems in graph by setting user preferences • Make changes from the graphical display • Monitor runs until you stop it (even if you are not signed on) © Copyright IBM Corporation 2012


• Each metric has defaults – Interval collection – Display time



• View graphics and detail



• Display history graph © Copyright IBM Corporation 2012

File monitor (1 of 2) IBM i

• Provides the ability to monitor: – All system logs – Selected files

• Monitor multiple systems • Define monitor based on: – Specific text strings – Specific file size – When a file is modified

• Events can be triggered when a threshold is reached: – Open event log – Open a monitor – Sound alarm – Run a command © Copyright IBM Corporation 2012

File monitor (2 of 2) IBM i


Jobs monitor (1 of 2) IBM i

• Monitor jobs – – – –

Specific jobs Job types Jobs running within a subsystem Group of jobs under a server categorization

• Define metrics – – – –

• Event logs

Job count Job status Job log message Job metric values

• Define thresholds

– Can be saved – Can be viewed – Can take actions • For active jobs

• Create monitors from: – Management Central • Monitors • Endpoint systems • System groups

– Individual system • My Connections

– Triggers : Actions – Reset : Actions


Jobs monitor (2 of 2) IBM i


Messages monitor (1 of 2) IBM i

• Track occurrence of messages • Define monitor based upon: – Message IDs – Message types – Message severities

• Take action based upon message – Send an automated response to the message – Automatically delete message – Run command that starts another job – Calling an application • Paging software

– Apply to threshold count • Trigger, reset commands • Variables © Copyright IBM Corporation 2012

Messages monitor (2 of 2) IBM i


Collection Services IBM i

• Collect performance data for future analysis – Performance Tool (5770-PT1) – Other performance report

• Start collection – On a single system – On a system group

• Display data through graph history • Copy data into database files


Collect data (1 of 2) IBM i


Collect data (2 of 2) IBM i


Display history graph IBM i


Inventory collection IBM i

• Information collected from endpoint systems • Stored on central system • Search inventory on systems or groups • Export and print – Hardware – Software – Fixes – Users and groups – System values


Select inventory to collect IBM i

• Select to collect all inventory • Select to collect specific inventory – If you select Fixes, you will automatically collect software.


Viewing the inventory list IBM i

• Must collect inventory before it is available for viewing • Viewed from endpoint systems – Information contained in database on central system


Last collected

System Values IBM i

• Manage system values across systems • Collect inventory for system values – Schedule – Export to PC file

• Compare system values on multiple target systems to those on a model system • Update system values on endpoint systems based on those of a model system – Schedule updates

• Change system values on a single system • Synchronize date and time © Copyright IBM Corporation 2012

Compare and update IBM i

• Use drop-down menu to select category – Values to compare change based on category

• Lists current values of endpoint systems • Inventory must be collected first in order to compare


Fixes functions IBM i

• Install wizard • Uninstall wizard • Clean Up wizard – Cover letters – Save files

• Compare and Update wizard • Compare and update multiple systems and groups in one operation • Schedule fix functions • All systems must be at V4R4 or higher © Copyright IBM Corporation 2012

Send and Install Fixes wizard IBM i

• Wizard guides you through process – Confirm selection of fixes – Select systems – Advanced • Send requisite fixes

– Summary – Schedule


Compare and Update wizard (1 of 3) IBM i

• Management Central – Endpoint system or system group • Right-click • Select Fixes • Select Compare and Update



• Select products – All or specific products

• Default is All products




Manage users and groups IBM i

You can manage users and groups across multiple systems. • Create user definition. • Create, edit, and delete users or groups. • Scan for owned objects across systems. • Collect and search inventory of users and groups. • Send users or groups from one system to multiple systems.


Create user definition IBM i


Reference Redbook SG24-5407 IBM i


Additional resources IBM i

• Web sites: – Navigator for IBM i homepage http://www-03.ibm.com/systems/i/software/navigator/index.html – Information Center for IBM Power Systems with IBM i http://publib.boulder.ibm.com/eserver/ibmi.html


Exercise: Management Central inventory and system values IBM i

At the end of the lab, you should be able to: • Collect the inventory on a system • View the inventory • Search the inventory • Export the inventory • Collect the system values inventory


Checkpoint IBM i

1.

True or False: Management Central is a suite of systems management functions that allows you to manage multiple systems in a TCP/IP network environment.

2.

True or False: The Management Central server must be running in order for that system to be visible in the Management Central view of systems.

3.

True or False: Once an IBM Power System with IBM i is defined as the central server you cannot define a different system as your central server.

4.

True or False: Endpoint systems can be added either manually or automatically.

5.

True or False: The advanced job scheduler is automatically included with every IBM Power System with IBM i that is shipped from IBM.

6.

True or False: Using Application Administration, it is possible to secure the Management Central functions.


Checkpoint solutions IBM i

1. True or False: Management Central is a suite of systems management functions that allows you to manage multiple systems in a TCP/IP network environment. The answer is true. 2. True or False: The Management Central server must be running in order for that system to be visible in the Management Central view of systems. The answer is true. 3. True or False: Once an IBM Power System with IBM i is defined as the central server you cannot define a different system as your central server. The answer is false. 4. True or False: Endpoint systems can be added either manually or automatically. The answer is true. 5. True or False: The advanced job scheduler is automatically included with every IBM Power System with IBM i that is shipped from IBM. The answer is false. 6. True or False: Using Application Administration, it is possible to secure the Management Central functions. The answer is true. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • Describe the capabilities of Management Central • Create links to IBM Power Systems with IBM i • Define in Management Central the central system, endpoint systems, and system groups • Define and perform the major functions of Management Central


Security concepts and overview


7.0


After completing this unit, you should be able to: • 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


The objectives of system security IBM i

• 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 © Copyright IBM Corporation 2012

Questions when planning for security IBM i

• As you plan security on your system and decide how much security you need, consider the following questions: – Is there a company policy or standard that requires a certain level of security? – Do the company auditors require some level of security? – How important is your system and the data on it to your business? – How important is the error protection provided by the security features? – What are your company security requirements for the future?


Physical security IBM i

System

Computer room

Keep Out

Display stations Backup tapes


Keylock security IBM i

Low

High

Manual

Normal

Automatic

Secure

Use ded service tools

Yes

No

No

No

Load system from tape

Yes

No

No

No

Change IPL source

Yes

No

No

No

IPL through switch

Yes

Yes

No

No

Remote IPL

No

Yes

Yes

No

PWRDWNSYS: Workstation

Yes

Yes

Yes

Yes

Off through power switch

Yes

No

No

No


Monitoring physical security IBM i

• Verify that the keylock switch is in SECURE or AUTO and that the key is removed. • Prevents: – Turning system off with power switch – Turning system on with power switch (SECURE only)

• If the computer is behind a door locked using 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.


System tools used to secure your system IBM i

• Security level • System values • Signing • Single sign-on enablement • User profiles • Groups profiles • Resource security • Data encryption • Security audit journal © Copyright IBM Corporation 2012

Security is always active IBM i

SIGNON: Harry MENU

AUTHORITY

PAYROLL MENU

AUTHORITY

PAYEDIT PROGRAM

AUTHORITY

PAYROLL DATA

Operational Read Execute


Checkpoint IBM i

1. True or False: The objectives of security are confidentiality, integrity, and availability. 2. Physical security includes which of the following? a. b. c. d.

Controlling access to the CPU Securing the tapes used for backup Securing the printers connected to your system All of the above

3. Which of the following is not one of the modes you can select for your system? a. b. c. d. e.

Manual Normal Automatic Secure Lockdown



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. b. c. d.

Controlling access to the CPU Securing the tapes used for backup Securing the printers connected to your system 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. b. c. d. e.

Manual Normal Automatic Secure Lockdown

The answer is lockdown. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • 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-related system values


7.0


After completing this unit, you should be able to: • List and explain the levels of security available • Describe the capability in service tools to lock out users from changing system values • List the steps to move from one security level to another • 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 an emulation • List the steps used in IBM i Navigator to manipulate system values • List the steps used in Systems Director Navigator for IBM i to manipulate system values © Copyright IBM Corporation 2012

Security components IBM i

People (users)

Objects (resources)

User profiles

Individual objects

Job descriptions

Library/directory

Group profiles

Authorization lists

System values © Copyright IBM Corporation 2012

Security-related system values IBM i

• Purpose – Used to define customized (security) characteristics on the system

• How to set – 5250 emulation • WRKSYSVAL: Work with system values • CHGSYSVAL: Directly change system values – IBM i Navigator • Configuration and Service > System Values – IBM Systems Director Navigator for i • Configuration and Service > System Values

• Authority required – Must have *SECADM and *ALLOBJ authority to change security -related system values – Can be locked with an option through dedicated service tools (DST) or system service tools (SST)


Locking system values using service tools IBM i

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. Load the initial program 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. © Copyright IBM Corporation 2012

Topic 1: Setting the level of security


7.0

QSECURITY system value IBM i

• Purpose: – Used to specify the level of security to be enforced on the system.

• How to set: – 5250 emulation: WRKSYSVAL QSECURITY – IBM i Navigator: Configuration and Service > System Values > Security > General tab – IBM Systems Director Navigator for i: Configuration and Service > System Values > Security (properties) > General tab

• Authority required: – Must have *SECADM and *ALLOBJ authority to change system values – Can be locked with an option through service tools (DST and SST)

• Journal entry: – SV © Copyright IBM Corporation 2012

QSECURITY system value: Security level IBM i

Level 50

Enhanced integrity

Level 40

System integrity

Level 30

Resource

Level 20

Password

Recommended value: Level 40


Security level 40 IBM i

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 sign-on without a user ID and password • Enhanced hardware storage protection • Default for QSECURITY system value © Copyright IBM Corporation 2012

Steps to change from level 30 to level 40 IBM i

1. Activate the security auditing function. 2. Set the QAUDLVL system value to include *AUTFAIL and *PGMFAIL. 3. Monitor the audit journal for *AUTFAIL and *PGMFAIL entries while running all of your applications at security level 30. 4. If you have any programs that were created before Version 1 Release 3, use the CHGPGM command with the FRCCRT parameter to create validation values for those programs. 5. Make corrections to any applications that are logging failures. 6. Change the QSECURITY value to 40 and perform an IPL. © Copyright IBM Corporation 2012

Security level 50 IBM i

Level 50

Enhanced integrity

Level 40

System integrity

Level 30

Resource

Level 20

Password

• QTEMP: Enhanced protection from other jobs • Parameter validation when calling system programs • Message handling restrictions between user and system programs • Internal control blocks protected from modification • Restricting user domain object types (*USRSPC, *USRIDX, and *USRQ) © Copyright IBM Corporation 2012

Steps to change to security level 50 IBM i

1. Evaluate the QALWUSRDMN system value. 2. Recompile any COBOL programs that were compiled using a pre-V2R3 compiler. 3. Recompile any S/36 environment COBOL programs that were compiled using a pre-V2R3 compiler. 4. Recompile any RPG/400 or System/38 environment RPG programs that use display files if they were compiled using a pre-V2R2 compiler. 5. Change the security value to 50, and perform an IPL.


System Values: Security (1 of 2) IBM i


System Values: Security (2 of 2) IBM i


Topic 2: Using 5250 emulation to configure system values


7.0

General security system values IBM i

• Purpose – Specify system values that control security on the system.

• How to set – WRKSYSVAL *SEC • (Work with the system values that are in the security category.)

• Authority required – User profile must have *ALLOBJ and *SECADM authority.

• Journal entry – SV


Security-related system values IBM i

• Purpose – Specify system values that relate to security on the system.

• How to set – WRKSYSVAL




Security-related restore system values IBM i

• Purpose – Controls how and which security-related objects are restored on the system.

• How to set – WRKSYSVAL *SEC




System values that apply to passwords IBM i

• Purpose – Specify system values to set requirements for the passwords users assign.





System values that control auditing IBM i

• Purpose – Specify system values to control security auditing on the system.


• Authority required – User profile must have *AUDIT authority.



Topic 3: Using IBM i Navigator to configure system values


7.0

Configuration and Service: System Values IBM i


System Values: Date and Time IBM i


System Values: Devices IBM i


System Values: Jobs > Interactive Jobs IBM i


System Values: Devices > Recovery IBM i

iSeries Five minutes inactive

CPI1126

QCPFMSG *MSGF

DSPMSG

OR

System values:

INACTMSGQ * MSGQ

QINACTITV (5) QINACTMSGQ (INACTMSGQ) INACTPGM * PGM

CRTMSGQ INACTMSGQ © Copyright IBM Corporation 2012

Jobs System Values IBM i


Security: Security Policy IBM i


Security Policy Properties: General IBM i


Security Policy Properties: Public Authority IBM i


Security Policy Properties: Objects not auditable, shared memory IBM i


Security Policy Properties: Scan IBM i


Security: Password Policy IBM i


Password Policy Properties: General IBM i


Password Policy Properties: Validation 1 IBM i


Password Policy Properties: Validation 2 IBM i


Password Policy Properties: Expiration IBM i


Change Password IBM i


Password rules for changing password IBM i

Password validation program N

Pass rules

Message

Y

QPWDVLDPGM

N

Y Validation program Message

PGM detects error?

Y © Copyright IBM Corporation 2012

N Password changed

Security: Signon Policy IBM i


Signon Policy Properties: General IBM i


Signon Policy Properties: Remote IBM i


Security: Restore Policy IBM i


Restore Policy Properties: Signatures IBM i


Restore Policy Properties: Conversion IBM i


Restore Policy Properties: Objects IBM i


Restore Policy Properties: Access Paths IBM i


Checkpoint IBM i

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.



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. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • List and explain the levels of security available • Describe the capability in service tools to lock out users from changing system values • List the steps to move from one security level to another • 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 an emulation • List the steps used in IBM i Navigator to manipulate system values • List the steps used in Systems Director Navigator for IBM i to manipulate system values © Copyright IBM Corporation 2012

User security


7.0


After completing this unit, you should be able to: • 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 • Explain the Management Central capabilities in relation to identifying users on the system • List the steps to recover a lost or forgotten password in the OS for the security office profile (QSECOFR) • List the steps to recover a lost or forgotten password in service tools for the security office profile (QSECOFR)



People (users)

Objects (resources)

User profiles

Individual objects

Job descriptions

Library/directory

Group profiles

Authorization lists


Topic 1: User profiles


7.0

Roles served by user profiles IBM i

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 – Designed to customize the system and adapt it to the user – 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 profiles IBM i

• Purpose – Used to define users and groups on the system

• How to set – 5250 emulation: • WRKUSRPRF: Create, change, and delete profiles on the system • CHGUSRAUD: Change user audit settings – IBM i Navigator: Users and Groups > All Users > Properties – IBM Systems Director Navigator for i: Users and Groups > Create Users or Change Users

• Authority required – Must at least have *SECADM authority to work with profiles – Must have *AUDIT authority to change user auditing

• Journal entry – – – – –

AD for changes to user auditing CO for creation of a user profile CP for changes to user profiles DO for deletion of a user profile ZC for changes to user profile that are not relevant to security


User profile IBM i

User information

User profile

• • • • •

Tells the system who you are

Password Password expiration level Initial menu/program User class Special authority

List of objects owned

• Static – User information

• Dynamic – List of owned objects – List of object authorizations © Copyright IBM Corporation 2012

Object authorizations

Appendix B: Default values for user profiles IBM i


New User IBM i


Create a new user: 5250 and IBM i Navigator IBM i


Create User: IBM Systems Director Navigator for I (1 of 2) IBM i


Create User: IBM Systems Director Navigator for I (2 of 2) IBM i


New User: Capabilities > Privileges IBM i


System privileges: Special authority: SPCAUT IBM i

• All object access (*ALLOBJ) – Access to all system resources

• Auditing control (*AUDIT) – Control audit system values

• Job control (*JOBCTL) – Manage output queues, job queues, and printers; change job attributes; stop subsystems; IPL

• Save/restore (*SAVSYS) – Save, restore, and free storage for all system objects

• Security administration (*SECADM) – Create, change, delete user profiles; manage OfficeVision for objects and users

• Spool control (*SPLCTL) – Manage all users' spooled files

• System configuration (*IOSYSCFG) – Change system configuration

• System service access (*SERVICE) – Display and alter service function © Copyright IBM Corporation 2012

Privilege classes IBM i

System privileges

Privilege classes Security officer

Security administrator

System operator

Programmer

User

All object access

X

20

20

20

20

Auditing control

X

Job control

X

20

X

20

Save/restore

X

20

X

20

Security administration

X

X

Spool control

X

System configuration

X

System service access

X © Copyright IBM Corporation 2012

20

New User: Capabilities > Applications IBM i


New User: Capabilities > Password and Unique Identifier IBM i


New User: Jobs > General IBM i


New User: Jobs > Session Startup IBM i


New User: Jobs > Display Session IBM i


Display Session: Limit capabilities IBM i

• The Display Session tab allows you to limit users’ capability to change their initial program, menu, current library, and attention program and prohibit them from running most Power System with IBM i commands.

Limit initial program/menu capabilities

Initial program

Initial menu

Current library

Attention program

Execute commands

Do not limit

Yes

Yes

Yes

Yes

Yes

Limit some capabilities

No

Yes

No

No

Yes

Limit capabilities

No

No

No

No

No

Note: Users can still run commands created or changed with parameter ALWLMTCPB(*YES). © Copyright IBM Corporation 2012

New User: Jobs > Output IBM i


New User: Jobs > International IBM i


New User: Groups > Group Info IBM i


New User: Personal > Name, Location, and Mail IBM i


Appendix B: IBM-supplied user profiles IBM i


User functions IBM i


Changing a user profile IBM i


Deleting a user profile IBM i


User profile: New in V7R1 IBM i


Exercise: Working with user profiles IBM i

At the end of the lab, you should be able to: • Create a user profile • Observe and verify the permissions associated with this new user profile • Test how the initial menu and limit capabilities parameters work to control and limit what a user is allowed to do at sign-on • Verify that the limit capabilities specified for this user profile are working as expected • Make changes to a user profile


Topic 2: Group profiles


7.0

More facts about group profiles IBM i

• Group profiles allow users with similar jobs to share permissions without having to share the same password. • You should choose a naming convention which makes groups easily recognizable. • You can create a group profile with no password (sign-on not allowed). • You should assign groups in order of use. • Permissions are added at the group level.


Roles served by group profiles IBM i

A group profile has several roles: – Security tool • It provides a method for organizing authorities and sharing them among users. • It is 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.


New Group IBM i


New Group: Capabilities IBM i


New Group: Networks IBM i


Group functions IBM i


Deleting a group IBM i


Exercise: Working with group profiles IBM i

At the end of the lab, you should be able to: • Test to see the messages received when you try to access an object not authorized to your profile • Add a user to a group to gain access to objects that are secured by that group profile • Test your access to objects that are authorized to a group profile • Verify that specific user-assigned authorities override authorities gained by belonging to a group profile


Topic 3: Management Central and working with profiles


7.0

Management Central: Users and groups IBM i

• Create user – Use definition • Template

– Create similar users based on the original

• Create, edit, copy, and delete users and groups – Scan for owned objects – Schedule those actions

• Send users or groups from one system to multiple systems – – – – – –

Names Passwords Security settings Authorities Enterprise Identity Mapping (EIM) Mail options

• Integrated with inventory – Schedule collection – Search – Export

Manage across multiple systems


Users and Groups functions IBM i


New User Definition IBM i

• Management Central – Definitions • User • Template to create users


New User Definition: Actions IBM i

• Specify commands to run – Call programs – Create objects for user • Libraries and so forth


User definition created IBM i

• Properties specified when creating definition – Personal – Capabilities – Job defaults and attributes

• Ability to change properties when creating user


Create user from definition IBM i

Select the systems or groups to create the user.


Direct connect: Display user data IBM i


Management Central: Display user inventory IBM i


Topic 4: Service tools security


7.0

Service tools user ID administration IBM i

• Users must authenticate themselves to access DST and SST. • The service tools user IDs are used for both SST and DST. • Starting with V5R1, the following changes were implemented: – Passwords are case sensitive and shipped expired. – All default passwords are shipped uppercase. This includes QSECOFR, 1111111111, 22222222, and QSRV. – It is now possible to create an additional 96 customized service tools user IDs. – It is recommended that individual users of DST should have their own user IDs and should maintain their own passwords. – The IBM-supplied IDs should be used only in rare circumstances.


System service tools IBM i

• Service tools user profiles – Provide better control of access to SST or DST functions

• Service tools device profiles – Provide access to functions in service tools device IDs used for LANattached Operations Console and client GUI supported by the service tools server

• Service tools security data – Reset operating system default password – Change operating system install security – View service tools security log – Save and restore service tools security data – Manage password level


Service tools user IDs in SST IBM i


Work with Service Tools User IDs IBM i


QSECOFR terminology IBM i

• Within IBM i, there are two security officer user profiles (QSECOFR). • The OS user profiles – Created with the Create User Profile (CRTUSRPRF) command. – Used to sign on to IBM i – Contains its own password

• The service tools user IDs – Created within DST through the Work with DST Environment menu options – Used to sign on to service tools (DST or SST) – Contains its own password (which is different from the OS profile)


Lost password for QSECOFR IBM i

• If the IBM i QSECOFR password is lost: – Use CHGUSRPRF to change the password for QSECOFR (requires that your user ID has *ALLOBJ and *SECADM). – Use DST Service Tools Security Data option 1 (Reset operating system default password). This will change the password to the default shipped value at the next IPL.

• If the service tools QSECOFR password is lost or disabled: – The DST password is disabled after three unsuccessful attempts to sign on. – Sign on to the OS with QSECOFR and issue the command: CHGDSTPWD *default – You can also use another service tools ID with the required authority to reset QSECOFR. – Perform a scratch install. © Copyright IBM Corporation 2012

Changing DST passwords: Manual mode procedure IBM i

• If the system is powered on: – Put the system in manual mode. – Select option 21 on the control panel, and press Enter. – Sign on to the DST sign-on screen at the system console.

• If the system is powered off: – Put the keylock to Manual position and start an attended (manual) IPL. – At the IPL or Install the System display select option 3 (Use Dedicated Service Tools (DST)). – Type in one of the DST security user IDs and passwords: • QSECOFR • QSRV • 11111111 • 22222222 © Copyright IBM Corporation 2012

Changing DST passwords: Menu navigation IBM i

• On the Use Dedicated Service Tools (DST) menu, select option 5 (Work with DST environment). • On the Work with DST Environment menu, select option 3 (Service tools user profiles). • On the Work with Service Tools User Profiles menu, select option 2 (Change Password). • Change passwords for the default user IDs: – QSECOFR – QSRV – 11111111 – 22222222

• Press F3 (Exit) to leave DST mode.


SST option 7: Allow change of security-related system values IBM i



1. True or False: User profiles are one of the security components available to implement security on the system. 2. The user profile does not contain which of the following? a. b. c. d. e. f.

Password User classification Special authorities assigned List of owned object List of authorized objects Listing of all the authorization lists where the user is included

3. The _______ special authority allows a user access to all system resources. a.*ALLOBJ b. *JOBCTL c. *SPLCTL d. *SECADM e. *SERVICE © Copyright IBM Corporation 2012


1. True or False: User profiles are one of the security components available to implement security on the system. The answer is true. 2. The user profile does not contain which of the following? a. b. c. d. e. f.

Password User classification Special authorities assigned List of owned object List of authorized objects Listing of all the authorization lists where the user is included

The answer is a listing of all the authorization lists where the user is included. 3. The *ALLOBJ special authority allows a user access to all system resources. a. b. c. d. e.

*ALLOBJ *JOBCTL *SPLCTL *SECADM *SERVICE

The answer is *ALLOBJ. © Copyright IBM Corporation 2012


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. 5. By specifying ______, 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. © Copyright IBM Corporation 2012


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. 5. By specifying limit 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 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. © Copyright IBM Corporation 2012


7. The maximum number of group profiles that a user can belong to is? a. b. c. d.

16 32 64 *NOLIMIT

8. True or False: With Management Central you can send a user profile to other systems in your network. 9. True or False: The same QSECOFR user ID and password is used to sign on to the operating system and to service tools. 10. True or False: I can recover the QSECOFR service tool profile by signing on with the IBM i QSECOFR profile and using the CHGDSTPWD command. © Copyright IBM Corporation 2012


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.

8.

True or False: With Management Central you can send a user profile to other systems in your network. The answer is true.

9.

True or False. The same QSECOFR user ID and password is used to sign on to the operating system and to service tools. The answer is false.

10. True or False. I can recover the QSECOFR service tool profile by signing on with the IBM i QSECOFR profile and using the CHGDSTPWD command. The answer is true. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • 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 • Explain the Management Central capabilities in relation to identifying users on the system • List the steps to recover a lost or forgotten password in the OS for the security office profile (QSECOFR) • List the steps to recover a lost or forgotten password in service tools for the security office profile (QSECOFR)


Resource security


7.0


After completing this unit, you should be able to: • 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 and data authority that can be assigned to an object • 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 if a user is allowed to access an object



People (users)

Objects (resources)

User profiles

Individual objects

Job descriptions

Library/directory

Group profiles

Authorization lists


Topic 1: Resource security concepts


7.0

User-owned objects IBM i

• 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 himself 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


Primary group authority IBM i

• Primary group authority is stored in the object header (good for performance). • There can be only one primary group authority per object, unlike real private authorities where there can be many per object. • The object owner cannot be the 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.


QDFTOWN IBM i

• 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 the 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, by IBM i Navigator, or IBM Systems Director for i. © Copyright IBM Corporation 2012

Where object permissions come from IBM i

• 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


Where *PUBLIC authority comes from IBM i

• 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)


Specific object permissions IBM i

• 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 © Copyright IBM Corporation 2012

Object management permissions IBM i

Permission

Definition

Operational (*OBJOPR)

Look at the description of an object and use the object as determined by the data authorities the user has. To open a file, the user must have *OBJOPR

Management (*OBJMGT)

Authorize users to the object, move or rename the object, and add members to database files. All functions defined for *OBJALTER and *OBJREF.

Existence (*OBJEXIST)

Change ownership and delete the object, free storage for the object, and perform save and restore operations for the object.

Alter (*OBJALTER)

Add, clear, initialize, and reorganize members of database files, alter and add attributes to database files, add and remove triggers, and change attributes of SQL packages.

Reference (*OBJREF)

Specify database file as the parent in a referential constraint.

Authorization list (*AUTLMGT)

Add and remove users and their authorities from an authorization list. © Copyright IBM Corporation 2012

Data permissions IBM i

Permission

Definition

Read (*READ)

Display the contents of an object, such as viewing the records in a file.

Add (*ADD)

Add entries to an object, such as adding messages to a message queue or records to a file.

Update (*UPD)

Change entries in an object, such as changing records in a file.

Delete (*DLT)

Remove entries from an object, such as removing messages from a message queue or deleting records from a file.

Execute (*EXECUTE)

Run a program or search a library or directory.

Exclude (*EXCLUDE)

Object access prevented. © Copyright IBM Corporation 2012

Commonly used permissions IBM i

Object control Operation Management Existence

X

X

Data authority Alter

Reference

Read

Add

Update

Delete

Execute

X

X

X

X

X

X

X

X

X

X

X

All

X

Change

X

X

Use

X

X

Exclude


X

Specifying specific authority for objects in the integrated file system IBM i

• *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


Topic 2: Defining resource security


7.0

Object permission: QSYS.LIB file system IBM i


Basic and Details permission displays IBM i

Basic = Commonly used permissions

Details = Object and data permission


Permission: Add and Remove IBM i


Permission: Customize IBM i


Permission: Authorization List IBM i


Change owner: Change Primary Group IBM i


Permission search order IBM i

User profile: Stop when any authority is found.

All object authority Private authority Authorization list

None found All object authority Primary group Private authority Authorization list

Group profiles: Like user profile. Repeats for each group profile and accumulates. Stops when sufficient authority is accumulated.

None found *Public: This is used when no authority is found for user or groups.

Object Authorization list Insufficient Adopted profile All object authority Private authority Authorization list

Adopted profiles: These are used when authority is insufficient.


Topic 3: Working with authorization lists


7.0

Authorization list IBM i

Name: AUTL1 Owner: USER3

LIBA

LFILEB

User authority: *PUBLIC USER1 USER2 USER4 USER5

Exclude Use Change All Change

PFILEC

*PUBLIC is on all authorization lists. © Copyright IBM Corporation 2012

PROGD

Create an authorization list IBM i


Authorization list permissions IBM i


Object secured by an authorization list IBM i


Securing an object with an authorization list IBM i


Authorization list considerations IBM i

• You cannot use an authorization list to specify authority to a user profile. • You cannot use an authorization list 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. • A user's list authority applies to all objects secured by that list.


Authorization list versus group profile IBM i

BILL WAYNE GUNNAR FRANK

Use All Use Change

FINDEPT/FILE3 LIB23 DSP05 Objects

Authorization list

BILL WAYNE GUNNAR

GROUP

Use All Change

FINDEPT/FILE3 LIB23 DSP05 Objects

FRANK Group profile © Copyright IBM Corporation 2012

Groups and AUTLs compared IBM i

Authorization lists

Groups

Authorization lists can secure multiple objects.

Groups 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 using the same list.

Different authority for different objects.

An object can be secured by only one authorization list.

An object can be authorized to many groups.


Exercise: Working with authorization lists IBM i

At the end of the lab, you should be able to: • Create an authorization list • Add a user to an authorization list and specify what authority will be assigned • Secure an object with an authorization list • Display the list of users on an authorization list • Display what objects are secured with an authorization list


Topic 4: Column-level authority


7.0

Column-level security IBM i

GRANT UPDATE (CDTLMT) ON QCUSTCDT TO OL50GRP

CUSNUM

LSTNAM

CDTLMT

938472

HENNING

5000

397267

TYRON

1000

693829

THOMAS

9999 OL5001: No update access

OL50GRP: Needs update access


Granting column-level permission IBM i

• MANAGER: Suppose OL50GRP already has specific *USE authority to QCUSTCDT. Grant OL50GRP update authority to CDTLMT: Check the Update box on CDTLMT > OL50GRP row.


Column-level security considerations IBM i

• Column-level security enforcement primarily occurs during the update operation on the file. • There is no new enforcement during open of the file. • Column-level authorities are stored in the database file object and managed by DB2 UDB. • Object authorities are stored in the user profile and managed by the system security manager.


Topic 5: Adopted authority


7.0

Adopted authority (1 of 3) IBM i

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.



• When a program created with USRPRF(*OWNER) is run, objects are accessed with the authority of the user running the program plus the program owner's authority. • Authority is in effect as long as the program that originally adopts is still in the stack. • This method temporarily gives authority to objects the user normally would not have. • Both object authorities and special authorities are adopted. • Program owner's groups are not used for adopted authority.


DSPPGM IBM i

Display Program Information Program Owner Program attribute

: : :

PGM1 OFCMGR CLP

Library

Program creation information: Program creation date/time . . . . . . . . . .: Source file . . . . . . . . . . . . . . . . . : Library . . . . . . . . . . . . . . . . . .: Source member. . . . . . . . . . . . . . . . .: Source file change date/time . . . . . . . . .: Observable information . . . . . . . . . . . . : User profile . . . . . . . . . . . . . . . . .: Use adopted authority . . . . . . . . . . . . .: Log command (CL program). . . . . . . . . . . .: Allow RTVCLSRC (CL program). . . . . . . . . . : Fix decimal data. . . . . . . . . . . . . . . :

Press Enter to continue. F3=Exit F12=Cancel


:

APP_LIB

12/23/96 SOURCE APP_SOURCE PGM1 12/23/97 *ALL *OWNER *YES *YES *YES *NO

11:41:02

11:40:58

Adopted authority (adopting a user profile) IBM i

*PGM: Owner: USRPRF USER01:

PGM1 OFCMGR (*OWNER) *OBJOPR *EXECUTE

*FILE : OFCMGR: *PUBLIC :

FILE1 *CHANGE *EXCLUDE

• USER01 can call PGM1. • USER01 has *CHANGE authority to FILE1 while running PGM1. • Granting *USE authority to PGM1 includes *OBJOPR and *EXECUTE.


Adopted authority example IBM i

Authorities during program execution

Call stack PGM1 Owner: OFCMGR User profile: *OWNER

User plus OFCMGR

PGM2 Owner: QSECOFR User profile: *OWNER

User plus OFCMGR plus QSECOFR

PGM3 Owner: QPGMR User profile: *USER PGM4 Owner: OFCMGR User profile: *OWNER Use adopted AUT: *NO © Copyright IBM Corporation 2012

User plus OFCMGR plus QSECOFR

User plus OFCMGR


Security considerations CALL PROG1

CHGLIB CALL PROG1

M. HONEST

A. CROOK CROOK

HONEST PROG1

PROG2 PROG2


SECURE FILE

Adopted authority considerations (1 of 2) IBM i

• Adopted authority is added to the user's authority. • Adopted profile's special and private authorities are used. • Adopted profile's group is not used. • Public authority that adopted profile would have is not used. • Program interruptions suspend adoption. – – – –

Debug TFRGRPJOB System request Break message program

• Audit: DSPPGMADP, DSPPGM, DSPSRVPGM • Programs always created with USEADPAUT(*YES). © Copyright IBM Corporation 2012

Adopted authority considerations (2 of 2) IBM i

• This provides a way to temporarily grant a user authority. • Should perform only the function the user does not have authority to do and return. • Propagating authority down the call stack is dangerous, especially when adopting a powerful profile, such as QSECOFR. • You should library-qualify calls made to programs that adopt. • You should secure programs that adopt. • This provides the ability to restrict direct object access but allow access through applications.


Authority checking (1 of 2) IBM i

Sufficient

Fast path for object authority

Authorized

Insufficient

Insufficient

User’s authority: Exit this box immediately when any authority is found. *ALLOBJ? Is owner and has some authority? Fast path for user authority? Private authority? Authorization list?

Sufficient Authorized

No authority found Group’s authority: Exit this box immediately for this group when any authority is found. Insufficient

*ALLOBJ? Is owner and has some authority? ADDITIVE Primary group (if group is primary group) Authority? ADDITIVE Private authority? ADDITIVE Authorization list? ADDITIVE


(Repeat above if more groups.) No authority found

Public authority If *PUBLIC=*AUTL, get public from authorization list. Otherwise use public authority stored with object. Insufficient Adopt © Copyright IBM Corporation 2012


Authority checking (2 of 2) IBM i

Adopt No Does program adopt? Yes Program OWNER'S AUTHORITY. Exit this box immediately when any authority is found. Sufficient

*ALLOBJ? Is owner and has some authority? ADDITIVE Yes

Authorized

Insufficient Current program: USEADPAUT(*YES) More programs in stack? Next program. No Does program adopt? Yes

No

Program OWNER'S AUTHORITY. Exit this box immediately when any authority is found. Private and primary group authority? ADDITIVE Authorization list? ADDITIVE Insufficient Yes

Current program: USEADPAUT(*YES) More programs in stack? Next program. No Access denied © Copyright IBM Corporation 2012

Sufficient

Authorized

Fast path for object authority IBM i

• Using information stored with the object, authorize access if all of the following are true: – No private authorities – Not secured by an authorization list – Owner authority sufficient – Primary group (if one exists) authority sufficient – Public authority sufficient

• Otherwise, return to calling flowchart with Insufficient.


Security example (1 of 3) IBM i

DEPT03

*AUTL: LISTA

Owned objects: X, Z, PGM3 X: *ALL Z: *ALL PGM3: *ALL

ANN: *ALL CATHY: *EXCLUDE DEPT03: *USE *PUBLIC: *USE

CATHY

DAVID

ANN

X: *USE Group: DEPT03

Z: *USE Group: DEPT03

X: *ALL

BILL

PGM1

PGM2

PGM3

Needs *CHANGE to X USRPRF(*USER) *PUBLIC: *USE

Needs *CHANGE to Y USRPRF(*USER) *PUBLIC: *USE

Needs *CHANGE to Z USRPRF(*USER) *PUBLIC: *USE Owner: DEPT03

File X

File Y

File Z

*PUBLIC: *USE Owner: DEPT03

Auth List: LISTA *PUBLIC: *AUTL

*PUBLIC: *CHANGE Owner: DEPT03



a. Is the user authorized to run the program and access the file without a security message? b. What authority did the user get for files X, Y, and Z? c. From where did the user get his/her authority? d. How would the following change the table: – CHGPGM PGM(PGM3) USRPRF(*OWNER)

PGM1 - X

PGM2 - Y

PGM3 - Z

d. PGM3-Z USRPRF(*OWNER)

Ann

a. b. c.

_________________ _________________ _________________

__________________ __________________ __________________

__________________ __________________ __________________

_________________ _________________ _________________

Bill

a. b. c.

_________________ _________________ _________________

__________________ __________________ __________________

__________________ __________________ __________________

_________________ _________________ _________________

Cathy

a. b. c.

_________________ _________________ _________________

__________________ __________________ __________________

__________________ __________________ __________________

_________________ _________________ _________________

David

a. b. c.

_________________ _________________ _________________

__________________ __________________ __________________

__________________ __________________ __________________

_________________ _________________ _________________



a. b. c. d.

Is the user authorized to run the program without a security message? What authority did the user get for files X, Y, and Z? From where did the user get his/her authority? How would the following change the table: –

CHGPGM PGM(PGM3) USRPRF(*OWNER)

PGM1 - X a.

Ann

Bill

Cathy

David

PGM2 - Y

PGM3 - Z

d. PGM3-Z USRPRF(*OWNER)

b.

Yes *ALL

Yes *ALL

Yes *CHANGE

c.

User-Private

User-*AUTL

*PUBLIC-Object

a. b.

No *USE

No *USE

Yes *CHANGE

c.

*PUBLIC-Object

*PUBLIC-*AUTL

*PUBLIC-Object

a. b.

No *USE

No *EXCLUDE

Yes *ALL

c.

User-Private

User-*AUTL

Group-Specific

a. b.

Yes *ALL

No *USE

Yes *ALL

c.

Group-Specific

No *USE Group-*AUTL

User-Private

Adopted DEPT03


Same

Same

Same

Exercise: Working with object authority and adopted authority IBM i

At the end of the lab, you should be able to: • Assign permission to objects • Assign authority to a profile by referencing another profile • Perform the necessary steps to delete a user profile



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 ______ user profile. a. b. c. d.

*USER *SECOFR *SYSOPR 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. © Copyright IBM Corporation 2012


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. b. c. d.

*USER *SECOFR *SYSOPR 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. © Copyright IBM Corporation 2012


6. True or False: OBJOPR, OBJMGT, and OBJEXIST are authorities that can be specified to the data authority for a specific object. 7. The very first thing that a system checks when determining if a user is allowed to access an object is: a. Group authority b. Authorization list c. Private authorities d. All object access

8. The maximum number of authorization lists that a user can be specified in is: a. 16 b. 32 c. 64 d. No maximum © Copyright IBM Corporation 2012


6. True or False: OBJOPR, OBJMGT, and OBJEXIST are authorities that can be specified to the data authority for a specific object. The answer is false. 7. The very first thing that a system checks when determining if a user is allowed to access an object is: a. b. c. d.

Group authority Authorization list Private authorities All object access

The answer is all object access.

8. The maximum number of authorization lists that a user can be specified in is: a. b. c. d.

16 32 64 No maximum

The answer is no maximum. © Copyright IBM Corporation 2012


9. _______ authority is an authority that can be assigned to an object temporarily. a. b. c. d.

User Object Resource Adopted

10. True or False: Applications that utilize calls to programs that adopt authority should library-qualify those calls.



9. Adopted authority is an authority that can be assigned to an object temporarily. a. b. c. d.

User Object Resource Adopted

The answer is adopted.

10. True or False: Applications that utilize calls to programs that adopt authority should library-qualify those calls. The answer is true. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • 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 and data authority that can be assigned to an object • 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 if a user is allowed to access an object


Security auditing


7.0


After completing this unit, you should be able to: • List and discuss the types of security-related activities that you can monitor on your system • List the different levels of security auditing that you can implement • Explain why implementing auditing is an ongoing process • List and configure the commands and system values used to implement security auditing • Explain the steps required to implement the different types of security auditing


Audit: Why and how? IBM i

• Why? – Keep system at planned security level

• How? – Implement at any security level or – Use system functions • DSPUSRPRF • DSPOBJAUT • DSPPGMADP


Auditing: Some events to monitor IBM i

• Save/restore information • Authorization failures • References to objects through interfaces not supported • Deleted objects • Security related functions • Action auditing information


Levels of auditing IBM i

• The levels of auditing that can be implemented include: – System-wide auditing – Auditing by specific user – Auditing by specific object – Auditing by network intrusion – Combination of the above


Examine your strategy IBM i

• Security strategies tend to become less effective over time. Some of the things that can change are: – Operating system updates – New products – Procedural changes – New user profiles – Changing roles – Terminations and resignations – New and changed objects – Deleted objects – Changes to system values and network attributes


An effective strategy IBM i

• Used to define security requirements • Endorsed by management • Communicated to employees • Enforceable • Periodically reexamined


Event monitoring IBM i

• Tools used to monitor events: – History log (QHST) – Security audit journal – Critical database files: Journal

• Events you might want to monitor include: – Invalid sign-on attempts – Authority failures – Access of or changes to critical files


Using the history log IBM i

• The history log is used to monitor for: – Start and completion of jobs – Device status messages – System operator messages and responses – Failed sign-on attempts

• To display the contents: – DSPLOG

LOG(QHST)

• To display a specific message range: – DSPLOG

LOG(QHST)

MSGID(CPF2200)


Steps to implement auditing IBM i

CRTJRNRCV CRTJRN

JRNRCV(SECRCV1)

JRN(QSYS/QAUDJRN)

LIB(USRLIB) JRNRCV(SECRCV1)

CHGSYSVAL

SYSVAL(QAUDLVL QAUDLVL2) VALUE(*NONE) (or one or some of the values on the next page)

CHGSYSVAL

SYSVAL(QAUDCTL) VALUE(*NONE) (*OBJAUD


*AUDLVL *NOQTEMP)

Values for the QAUDLVL and QAUDLVL2 IBM i

*NONE *NOTAVL *AUDLVL2 *ATNEVT *AUTFAIL *CREATE *DELETE *JOBBAS *JOBCHGUSR *JOBDTA *NETBAS *NETCLU *NETCMN

*NETFAIL *NETSCK *OBJMGT *OFCSRV *OPTICAL *PGMADP *PGMFAIL *PRTDTA *SAVRST *SECCFG *SECDIRSRV *SECIPC *SECNAS © Copyright IBM Corporation 2012

*SECRUN *SECCKD *SECURITY *SECVFY *SECLDL *SERVICE *SPLFDTA *SYSMGT

Security: Auditing policy (1 of 3) IBM i






Audit journal entries IBM i

Journal code

Entry type

T T

AF CA

All authority failures Changes to object authority (authorization list or object)

T

CP

Create, change, delete, display, restore of user profiles

T

DO

All delete operations on the system

T

DS

T

JD

DST security officer password reset Changes to the USER parameter of a job description

T

NA

Changes to network attributes

T

OW

T

PA

T

PW

Changes to object ownership Changes to programs (CHGPGM) that will now adopt the owner's authority Passwords used that are not valid

T

RA

Restore of objects when authority changes

T

RJ

Restore of job descriptions that contain user profile names

T

RO

Restore of objects when ownership information changes

T

RP

Restore of programs that adopt their owner's authority

T

RU

Restore of authority for user profiles

T

SE

Changes to subsystem routing

T

SV

Changes to system value

U

Operation description

User-specified, user-created entry © Copyright IBM Corporation 2012

Audit-related files and messages IBM i

Physical file name

QASYAFJE

Journal entry code

AF

Message ID

Description

CP12246 CP12247 CP12248 CP12249

Authority violation Domain violation Submit job violation Default sign-on

CP12250

CRC failure

CP12251

Password not valid

CP12252

User ID not valid

QASYPWJE

PW

QASYPWJE

CA

CP12252

Authority change

QASYOWJE

DW

CP12254

Ownership change

QASYPAJE

PA

CP12255

Change program to adopt

QASYSVJE

SV

CP12256

System value change

QASYNAJE

NA

CP12257

Network attribute changes

QASYRPJE

NA

CP12258

Restore of programs that adopt

QASYRJJE

RJ

CP12259

Restore of job description that contains a user profile name

QASYROJE

RO

CP12260

Restore of object owner changes

QASYRAJE

RA

CP12261

Restore of object and authority changes

QASYRUJE

RU

CP12262

Restore of authority for user

QASYDOJE

DO

CP12263

Delete of object

QASYJDJE

JD

CP12264

Job description change to specify user name

QASYSEJE

RC

CP12265

Routing entry changed

QASYCPJE

CP

CP12266

User profile changed

QASYDSJE

DS

CP12267

Request to change DST QSECOFR password


Action auditing for a specific user IBM i

• Use CHGUSRAUD to set the AUDLVL for a selected user profile. CHGUSRAUD USRPRF(ADM01)

AUDLVL(*SAVRST *CMD *DELETE*SPLFDTA)


Action auditing for a specific object IBM i

• Values from the user profile parameter OBJAUD, system value QAUDCTL, and the object work together to control object auditing. • Use CHGOBJAUD to specify auditing actions on objects – – – –

*NONE *USRPRF *CHANGE *ALL

CHGOBJAUD OBJ(ADM01/CUSMSI) OBJTYPE(*FILE) OBJAUD(*USRPRF)

• Use CHGUSRAUD to set the OBJAUD values in selected user profile – – – –

*SAME *NONE *CHANGE *ALL

CHGUSRAUD

USRPRF(ADM01)

OBJAUD(*CHANGE)


User: Capabilities > Auditing IBM i


Printing or viewing audit journal entries IBM i

• You have the following options for working with audit journal entries: – Use DSPJRN to view and print entries – Output DSPJRN to disk • • • •

User program QUERY/400 Query manager SQL


DSPJRN to view a specific entry IBM i

Display Journal Entry Object . . . . . . . . : Member . . . . . . . . . : Code . . . . . . . . . . : Type . . . . . . . . . . :

Library . . . . . . : Sequence. . . . . . : 32488 T - Audit trail entry DO - Delete object

Entry specific data Column *...+....1....+....2....+....3....+....4....+....5 00001 'QBATCHJOBD QGPL *JOBD

Press Enter to continue. F3=Exit F6=Display only entry specific data F10=Display only entry details F12=Cancel F24=More keys


DSPJRN to view > F10 IBM i

Display Journal Entry Details Journal.......: Sequence.......:

QAUDJRN 32488

Code..........: Type...........:

T - Audit trail entry DO - Delete object

Object.........: Member.........: Date...........: Count/RRN.......:

22/09/94 0

Job............: User profile......: Commit cycle ID..:

Library .......: QSYS

Library.........: Flag...........: Time............: Program.........:

0 13:42:36 CLRLIB_PGM

012462/BAD_PGMR/QPADEV0048 BAD_PGMR Ref Constraint...: No 0 Trigger........: No

Press Enter to continue. F3=Exit

F10=Display entry F12=Cancel F14=Display previous entry F15=Display only entry specific data


Output DSPJRN to disk > print IBM i

DSPJRN JRN(QSYS/QAUDJRN)

+

ENTTYP(AF)

+

OUTPUT(*OUTFILE)

+

OUTFILFMT(*TYPE5)

+

OUTFILE(QTEMP/your_file)

• The format of your_file will be QASYAFJ5. • Use QUERY or your own program for further analysis.


Consider journaling critical files IBM i

• Offers both *BEFORE and *AFTER imaging • Tracks changes by job, date, time, and user profile • Journal receiver entries cannot be modified, even by QSECOFR • Journal receivers can be saved


Checkpoint IBM i

1. True or False: Security auditing is implemented to keep a system at a planned security level. 2. Which of the following is not one of the levels of security auditing that can be implemented on the system? a. b. c. d.

System wide Specific user Specific object Configuration changes

3. True or False: An effective security strategy does not require that it be endorsed by management.



1. True or False: Security auditing is implemented to keep a system at a planned security level. The answer is true. 2. Which of the following is not one of the levels of security auditing that can be implemented on the system? a. b. c. d.

System wide Specific user Specific object Configuration changes

The answer is configuration changes. 3. True or False: An effective security strategy does not require that it be endorsed by management. The answer is false. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • List and discuss the types of security-related activities that you can monitor on your system • List the different levels of security auditing that you can implement • Explain why implementing auditing is an ongoing process • List and configure the commands and system values used to implement security auditing • Explain the steps required to implement the different types of security auditing


Designing security


7.0


After completing this unit, you should be able to: • List some recommendations for security design • Discuss the concept of implementing library security • Discuss some design guidelines to keep in mind when implementing menu security • Describe the process used by the system for sign-on processing • Explain the functions provided by the System Request screen and how to secure this screen or the screen options • Discuss the concepts of implementing object security • List and discuss the commands used to back up and recover security information • Describe the security tools that are available to assist you with the implementation of security © Copyright IBM Corporation 2012

Designing security IBM i

• Most people use a combination of the following methods to secure their system: – Library security – Menu security – Object security – File security – Adopted security – Command security

• Using combinations of – Users – Groups – Authorization lists


Overall recommendation for security design IBM i

• Keep the design as simple as possible. • Use resource security along with the other methods available to protect information. • Secure only those objects that require securing. • Move from general to specific authority. • Determine what should be the default *PUBLIC authority, and implement it with the CRTAUT parameter. • Avoid private authorities that are less than public authority. • Use authorization lists to secure group objects with the same security requirements. © Copyright IBM Corporation 2012

Planning and setting up system security guide IBM i

• Security

http://publib.boulder.ibm.com/eserver/ibmi.html

– Planning and setting up system security • PDF file: Planning and setting up system security © Copyright IBM Corporation 2012

Topic 1: Library security


7.0

Library security IBM i

• Library security is effective only if these rules are followed: – Libraries contain objects with similar security requirements. – Access is granted or restricted at the library level. – Typically, users that have access to the library have access to all the objects in the library (through *PUBLIC authority). – Users are not allowed to add new objects to restricted libraries. – Secure your library lists and any commands used to change them. – This might not be granular enough, especially for sensitive objects.


Topic 2: Menu security


7.0

Menu security: Design guidelines IBM i

• Do not provide a command line on menus designed for restricted users. • Avoid having functions with different security requirements on the same menu. • Make sure that the set of menus provides all the necessary links between menus. • Provide access to a few system functions. • Provide access to decision-support tools from menus. • Consider controlling access to the System Request screen. • For users allowed to run a single function, avoid menus entirely and specify an initial program. © Copyright IBM Corporation 2012

User profile session startup: Menu security IBM i

• Confine users to a menu interface. – Initial program

(program-name)

– Initial menu

Sign off

- Or – Initial program

No initial program

– Initial menu

(menu-name)

– Limit initial program or menu capabilities Limit capabilities

• Do not provide command line. © Copyright IBM Corporation 2012

Menu security: Sign-on processing IBM i


Sign-on processing (1 of 2) IBM i

No

Valid user/password?

Error message

Yes No

Authorized to device?

Error message

Yes Yes

Program/menu/lib exceed capability?

Error message

No

Program keyed?

No

INLPGM in profile? Yes

Yes

Call INLPGM

Call keyed program A © Copyright IBM Corporation 2012

Sign-on processing (2 of 2) IBM i

A

Menu keyed?

No

Yes

* SIGNOFF in Display keyed menu

profile? No

Display profile menu


Yes

Sign off user

System Request screen security IBM i

• To prevent specific users from seeing the System Request screen, specify the following: GRTOBJAUT OBJ(QSYS/QGMNSYSR) OBJTYPE(*PNLGRP) USER(USERA) AUT(*EXCLUDE) © Copyright IBM Corporation 2012

System Request screen: A secondary job IBM i

Job A

1

3

5

Job B

Sign-on Process System Request 2

Sign-on Process System Request

4

Resume processing Sign off

Resume processing System Request

Resume processing Sign off


Restricting the use of System Request screen options IBM i

Option

Command

1

Transfer Secondary Job (TFRSECJOB)

2

End Request (ENDRQS)

3

Display Job (DSBJOB)

4

Display Message (DSPMSG)

5

Send Message (SNDMSG)

6

Display Message (DSPMSG)

80

Disconnect Job (DSCJOB)

90

Sign Off (SIGNOFF)

• Any of the options can be restricted by removing public authority to the associated command. For example: GRTOBJAUT OBJ(TFRSECJOB) OBJTYPE(*CMD) USER(*PUBLIC) AUT(*EXCLUDE) © Copyright IBM Corporation 2012

Topic 3: Object security


7.0

Object security IBM i

• Access is granted or restricted at the individual object level. • This is the most secure method. • This method provides the most granularity. • It can also be the most complex to set up. • It can have performance impacts both at run time and at backup and restore time.


Command security IBM i

• Change the authority to specific commands. • User needs *USE authority in order to run a command. • Change the default values for commands.


Appendix C: Secured commands IBM i


System-defined authorities for files and programs IBM i

*USE authority

*CHANGE authority

*ALL authority

*EXCLUDE 1 authority

Operations allowed for files

View information in the file.

View, change, and delete records in the file.

Create and delete the file. Add, change, and delete the records in the file. Authorize others to use the file.

None.

Operations not allowed for files

Change or delete any information in the file. Delete the file.

Delete or clear the entire file.

None.

Any access to the file.

Operations allowed for programs

Run the program.

Change the description of the program.

Create, change, and delete the program. Authorize others to use the program.

None.

Operations not allowed for programs

Change or delete the program.

Change or delete the program.

Change the owner of the program, if the program adopts authority.

Any access to the program.

¹) *EXCLUDE overrides any authorities that you grant to the public or through a group profile. © Copyright IBM Corporation 2012

System-defined authorities for libraries IBM i

Operations allowed for libraries

Operations not allowed for libraries

*USE authority

*CHANGE authority

*ALL authority

*EXCLUDE 1 authority

• For objects in the library, any operation allowed by the authority to the specific object. • For the library, view descriptive information.

• For objects in the library, any operation allowed by the authority to the specific object. • Add new objects to the library. • Change the library description.

• Everything allowed with change authority. • Delete the library. • Authorize others to the library.

None.

• Add new objects to the library. • Change the library description. • Delete the library.

Delete the library.

None.

Any access to the library.

¹) *EXCLUDE overrides any authorities that you grant to the public or through a group profile. © Copyright IBM Corporation 2012

How library authority and object authority work together IBM i

Object type

Operations

Object authority needed

Library authority needed

File

Change data

*CHANGE

*EXECUTE

File

Delete the file

*OBJOPR, *OBJEXIST

*EXECUTE

File

Create the file

None

*EXECUTE, *ADD

Program

Run the program

*USE

*EXECUTE, *OBJOPR

Program

Recompile the program

*OBJEXIST, *OBJMGR, *READ

*ADD, *READ

Program

Delete the program

*OBJEXIST

*EXECUTE


Securing physical versus logical files (1 of 2) IBM i

Logical

files

CUSTINFO

CUSTCRDT

CUSTSLS

Name Address Credit limit Sales

Name Address Credit limit

Name Address Sales

Physical Files – CUSTMAST Name

Address

Credit Limit

Sales To Date


Securing physical versus logical files (2 of 2) IBM i

• To use logical files as a security tool: – Grant all data authorities to the underlying physical files. – Revoke *OBJOPR from the physical files. This prevents users from accessing the physical files directly. – Grant the appropriate data authorities to logical files. Revoke any authorities you do not want. – Grant *OBJOPR to the logical files.


Create Output Queue: Security attributes beyond resource security IBM i


Authority required to perform printing functions IBM i

Printing function

DSPDTA

AUTCHK

Output queue authority

Special authority

Any *YES

*READ

None *JOBCTL

Any *YES

*READ Any

None *JOBCTL

OPRCTL

Add spooled files to queue.

Any Any

Any

View list of spooled files (WRKOUTQ command).

Any Any

Any

*YES *NO *NO

Any *DTAAUT

Any

*READ

None

Any

*CHANGE

None

*Owner

Owner3

*YES

Any

Any *YES

Any

None *JOBCTL

*NO

Any

*YES

Any

*JOBCTL

*Owner

Any

Any

Any

Any

Change, delete, hold, and release spooled file (CHGSPLFA, DLTSPLF, HLDSPLF, RLSSPLF).

Any

*DTAAUT

Any

*CHANGE

None

Any

*OWNER

Owner

Any

Any

Any *YES

Any

None *JOBCTL

Change, clear, hold, and release output queue (CHGOUTQ, CLROUTQ, HLDOUTQ, RLSOUTQ).

Any

*DTAAUT

Any

*CHANGE

None

Any

*OWNER

Owner

Any

Any

Any *YES

None *JOBCTL

Start a writer for the queue (STRPRTWTR, STRRMTWTR)

Any

*DTAAUT Any

Any *YES

*CHANGE

Any

Display, copy, or send spooled files (DSPSPLF, CPYSPLF, SNDNETSPLF, SNDTCPSPLF).

Any

Any


Any

Any

Any

None *JOBCTL

Limit access to program function IBM i

• You have the ability to secure a portion of an application program. • This is implemented through IBM i Navigator Application Administration or Users and Groups. • Blocks of application code must be registered. • Application code calls an API to check security for the user before it calls the code block.


Authority to workstation (1 of 2) IBM i

• QLMTSECOFR = 1 means *ALLOBJ and *SERVICE users are limited to specific devices. • QSECOFR, QSRV, and y can always sign on at the console. • The QCONSOLE system value is used to determine which device is console. Determine user's authority to Workstation.

*CHANGE or greater

Is QSECURITY => 30?

No

Yes Less than *CHANGE

Does user have *ALLOBJ or *SERVICE?

Sign-on fails.

No

Yes Is QLMTSECOFR = 1?

No

A Allow sign-on. © Copyright IBM Corporation 2012

Authority to workstation (2 of 2) IBM i

A Less than *CHANGE

Test user's authority to workstation. No authority

Less than *CHANGE

Test groups' authority to workstation. No authority

Yes

Does user have *SERVICE but not *ALLOBJ? No

No

Does QSECOFR have *CHANGE or greater? Yes

Sign-on fails.

Allow sign-on. © Copyright IBM Corporation 2012

*CHANGE or greater

*CHANGE or greater

Data encryption IBM i

• Disk encryption protects: – Data transmission to and from the disk drive – Data transmission in the cross site mirroring environment – Data in the case of theft of the disk drive

• DB2 column encryption (since i 7.1) – Enhanced data security

• Tape encryption – Software – Hardware


Topic 4: Security save and restore considerations


7.0

Restricting save and restore operations IBM i

• You can control the ability to save and restore objects in several ways: – Restrict physical access to save and restore devices. • Physical tape units • Optical units

– Restrict authority to the device descriptions objects for the save and restore devices (and the commands used to create these). – Restrict authority to use the save and restore commands. – Only give *SAVSYS special authority to trusted users.


Backup and recovery of security information IBM i


Authority information saved with an object IBM i

• Public authority • Owner name • Owner’s authority to object • Primary group name • Primary group’s authority to object • Authorization list name • Field level authorities • Object auditing value • Whether any private authority exists • Whether any private authority is less than public • Private authorities for the object, if PVTAUT(*YES) is specified on the SAVxxx command © Copyright IBM Corporation 2012

Other authority information that is saved IBM i

• Authority information saved with authorization list: – Normal authority information stored with any object, such as the public authority, owner, and primary group

• Authority information saved with user profile: – User profile attributes shown on the Create User Profile display – Other application information associated with the user profile, for example: • Server authentication entries • User application information entries that are added using the Update User Application Information (QsyUpdateUserApplicationInfo) API.

• Authority table saved associated with user profile: – One record for each private authority of the user profile, including usage settings for registered functions

• Function registration information saved with QUSEXRGOBJ object: – The function registration information saved by saving the QUSEXRGOBJ *EXITRG object in QUSRSYS


Restoring programs with restricted instructions IBM i

• Validation value stored with program and checked when restored. • Restore actions for invalid programs: – Re-create program – Entry in QAUDJRN – Message in job log – Ownership to QDFTOWN – Revoke authority

• QSECURITY (40 or 50) and ALWOBJDIF affect restore actions.


Topic 5: Security tools


7.0

Security tools IBM i

• Additional IBM i commands to help you manage security: – Available through • Individual command • SECTOOLS menu (commands run interactively) • SECBATCH menu (report commands submitted or scheduled)

– Work with profiles (SECTOOLS) • • • •

Disable users during specified periods Delete or disable a user on a specific date Disable profile after certain inactivity period Analyze profile for default passwords

– Work with auditing (SECTOOLS) • One-step setup • Display auditing system values

– Security reports (SECTOOLS and SECBATCH) © Copyright IBM Corporation 2012

Security Tools (1 of 4) IBM i








Security Wizard IBM i


Security Wizard simulation (1 of 10) IBM i




















Checkpoint IBM i

1. True or False: It is recommended that you only secure those objects that require securing. 2. True or False: Access to objects cannot be specified at the library level. 3. True or False: It is possible to control whether a user has access to a command line. 4. True or False: You cannot limit access to the System Request screen. 5. True or False: You can define ASP encryption through 5250 interface. 6. The most granular security that you can specify is: a. b. c. d.

Library User Object Program level © Copyright IBM Corporation 2012


1. True or False: It is recommended that you only secure those objects that require securing. The answer is true. 2. True or False: Access to objects cannot be specified at the library level. The answer is false. 3. True or False: It is possible to control whether a user has access to a command line. The answer is true. 4. True or False: You cannot limit access to the System Request screen. The answer is false. 5. True or False: You can define ASP encryption through 5250 interface. The answer is false. 6. The most granular security that you can specify is: a. b. c. d.

Library User Object Program level

The answer is object. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • List some recommendations for security design • Discuss the concept of implementing library security • Discuss some design guidelines to keep in mind when implementing menu security • Describe the process used by the system for sign-on processing • Explain the functions provided by the System Request screen and how to secure this screen or the screen options • Discuss the concepts of implementing object security • List and discuss the commands used to back up and recover security information • Describe the security tools that are available to assist you with the implementation of security © Copyright IBM Corporation 2012

The Model 7310-CR2: • Intel XEON-based rack-mounted workstation – 1U tall – Mounts in a 19-inch system rack • 1 GB of a system memory • 40 GB minimum hard disk • DVD-RAM for backup • One integrated serial port • One graphics port • Two integrated 10/100/1000 Mbps Ethernet ports • Three PCI slots • Integrated diskette drive

The Model 7310-CR3: • Intel XEON-based rack-mounted workstation – 1U tall – Mounts in a 19-inch system rack • 1 GB of a system memory • 80 GB Serial ATA HDD • DVD-RAM for backup • One integrated serial port • One graphics port • Two integrated 10/100/1000 Mbps Ethernet ports • Three PCI slots • Chargeable external diskette drive if needed

The Model 7310-C03: • Intel Pentium desktop workstation • 1 GB of system memory • 40 GB minimum hard disk • DVD-RAM for backup • Two integrated serial ports • One graphics port • One integrated 10/100/1000 Mbps Ethernet • Six USB ports • Two PCI slots • Integrated diskette drive

The Model 7310-C03: • Intel Pentium desktop workstation • 1 GB of system memory • 40 GB minimum HDD • DVD-RAM for backup • Two integrated serial ports • One graphics port • One integrated 10/100/1000 Mbps Ethernet • Six USB ports • Two PCI slots • Two PCI-Express slots (for future use) • Integrated diskette drive

IBM Power Systems with IBM i: Availability overview


7.0


After completing this unit, you should be able to: • Explain the concept of availability • Describe the different types of failures that can occur • Describe hardware and software availability features • Explain the concept of logical partitioning (LPAR) • List some of the reasons to implement LPAR • Explain the functions served by a Hardware Management Console (HMC) • Explain the concept of clustering • List the different types of clustering that can be implemented • Explain the different ways an xSeries can be integrated with the IBM Power Systems with IBM i • Describe the consequences for a company if the IBM Power Systems with IBM i are not available to perform normal business © Copyright IBM Corporation 2012

Topic 1: Availability concepts and overview


7.0

Availability concepts IBM i

• Concepts to know and understand that are associated with availability: – Business continuity – Disaster recovery – High availability – Backup window – An unplanned outage – High availability solutions – A cluster


Estimating the value of availability IBM i

• To estimate the value of your information services, follow these steps: – Develop a list of the major services and solutions that your system provides. – Assess how much it costs when these services are unavailable. – Look at direct costs versus indirect costs. – Consider tangible costs versus intangible costs. – Analyze fixed costs versus variable costs.


What is an acceptable downtime? IBM i


Types of outages IBM i

IBM Power System with IBM i 24x365. No time for downtime © Copyright IBM Corporation 2012

Failure types (1 of 2) IBM i

• Disk failure – Usually data on failed unit lost – Recover an ASP of failed unit

• System failure (hardware failure other than disk) – Usually causes abnormal end – Possible problems: • • • •

Files partially updated Access paths incomplete Damage to objects in use Relationships between files might be partially validated

– Long IPL


Failure types (2 of 2) IBM i

• Power failure – Can cause abnormal end – Same problems as system failure

• Program or user error – Incorrect (damaged) data – Correct data or restore files

• Complete system loss – Natural disasters, such as fire and flood


IBM Power Systems with IBM i hardware features (1 of 5) IBM i

Power subsystem – Redundant power supplies – Dual line cords – Redundant cooling fans – Dedicated UPS monitoring interface



Disk subsystem – RAID 5 / RAID 6 protection – Mirroring protection – Concurrent maintenance – Add disk concurrently



I/O subsystem – Hot pluggable PCI cards – Dynamic hardware resource reallocation (Vary cmd) – Redundant HSL loops – IOP reset



Memory – Chipkill technology – Error detection and correction – Memory scrubbing



Hardware service – Automatic failure notification


IBM Power Systems with IBM i software features (1 of 6) IBM i

IBM i and system software availability feature: – Journaling • • • • • •

Tables (files) Data areas Data queues IFS (stream files) Remote journaling SMAPP

– Commitment control



IBM i and system software availability feature: – ASPs, iASPs – HSM – Automated storage management – Online disk balancing



IBM i and system software availability feature: – Save-while-active – Save changed objects – Parallel save and restore • Multiple object • Multiple tape drives

– BRMS: Backup and recovery and tape automation – Online Domino backup



IBM i and system software availability feature: – Virtual IP • Route fault tolerance • Inbound/outbound • Load balancing



IBM i and system software availability feature: – No interfaces to OS kernel • Highly virus resistant • Security auditing



• IBM i and system software availability feature – Immediate PTF apply – No IPL required


Topic 2: LPAR and HMC concepts and overview


7.0

PowerVM virtualization IBM i

• PowerVM – PowerVm Express – PowerVm Standard Edition – PowerVM Enterprise Edition

• POWER Hypervisor – Firmware sitting between hosted Operating Systems and server hardware • Controls hardware I/O and management for partitions

– Always installed and activated • Regardless of configuration

• • • •

Dynamic Logical Partitioning Shared processor pools Micro-partitioning Integrated Virtualization Manager – Combines partition management and Virtual I/O Server (VIOS) • VIOS allows sharing of physical resources amongst multiple partitions

– Managed from a single point of control (IVM partition) • Does not require a Hardware Management Console (HMC) © Copyright IBM Corporation 2012

What is logical partitioning? IBM i

To independent partitions

IBM power-based servers running IBM i

Partition 1

Partition 2

Partition 3

From a single footprint

• Up to a maximum of 254 LPARs • Max depends on which POWER technology is installed (POWER4 versus POWER5, POWER6, and POWER7 up to 1000 LPARs) © Copyright IBM Corporation 2012

Allocating resources on an LPAR system IBM i

Whole processors

Dedicated processors LPAR1

1

LPAR2

2

Shared processor pool LPAR 3

3.33

Partial processors

LPAR4

0.85

0.82 Processors

Virtual Ethernet

Memory Dynamic reallocation

I/O adapters

Common resources

I/O devices


Partition resources IBM i

• The resources that are allocated to partitions are: – Load source IOP and disk unit – I/O slots • Including virtual devices

– Processing units – Memory – 5250 emulation (‘interactive’) for IBM i – Console

• Virtual resources that can be shared: – Ethernet – SCSI – Serial © Copyright IBM Corporation 2012

Power Systems and operating systems IBM i

IBM i

TIMI

Linux

Open firmware

SLIC POWER Hypervisor

Power Systems hardware


AIX 5L

Open firmware

POWER Hypervisor functions IBM i

• The POWER Hypervisor is firmware that provides: – Virtual memory management • Controls internal operations and I/O access • Manages memory

– Virtual hardware support: Processors, Ethernet, SCSI, serial, and virtual OptiConnect – Security and isolation between partitions • Partitions are allowed access only to resources that are allocated to them (enforced by the POWER Hypervisor).

LPAR 1

LPAR 2

LPAR 3

LPAR 4

POWER Hypervisor System hardware (memory, processors, devices) © Copyright IBM Corporation 2012

Security and isolation barriers, the POWER Hypervisor is independent of any OS

Software licensing IBM i

• Licensing – Is per operating system – Is based on processing power or is user-based for some entry-level servers – Is affected by partial processor feature

• Third-party application provider licenses might differ Other software Operating systems IBM i, Linux, AIX 5L IBM hardware © Copyright IBM Corporation 2012

Why would I use logical partitions? IBM i

• Mixed production and test environments • Server consolidation • Diverse workloads • Departmental systems • Different system names, languages, and time zones • Need to support interactive and e-business intelligence workloads • Mixed operating systems – IBM i (different versions) – AIX 5L – Linux © Copyright IBM Corporation 2012

Partition Partition Partition

LPAR allows for consolidation IBM i

• From many smaller systems to one (or fewer) smaller systems – Smaller footprint – Save on IT real estate – Resource allocation flexibility

Tape

• Time-share common resources – Tape – CD/DVD – Communications adapters

CD

• Global consolidation – Independent partition time zones – Multiple national languages

• Operating systems flexibility

Partition-1 Japan

Partition-2 USA

– Choice of operating system – Application selection flexibility

• Systems landscape

O RGRESS O RDEMEP O

IBM i 7.1

– Development, test, production, and so on © Copyright IBM Corporation 2012

Partition-3 Partition-4 Argentina UK

AIX

IBM i 6.1

Linux

How does LPAR work on POWER5, 6, and 7? IBM i

On these systems, the interface has been moved to the HMC. – Includes the POWER Hypervisor – Improves fault tolerance and lowers partition management costs – No longer uses a primary partition – Supports IBM i, AIX 5L, and Linux – Supports up to 254 partitions (up to 1000 with POWER7) – Provides automatic processor balancing with shared uncapped partitions


How does LPAR work on POWER4? IBM i IBM powerbased servers running IBM i

Independent logical partitions CPW

Partition LPAR 2

Processor

=

Processor memory

IBM i LS UNIT 1

Memory

Workload interactive

Partition LPAR 1

Disks

IBM i

CPW

=

Processor memory

IBM i LS UNIT 1

Logically dividing system resources

IBM i

CPW

Primary Hypervisor Workstations Communication lines Tape drives Other hardware resources

=

Processor memory

LS UNIT 1

Available alternate IPL device for each LPAR © Copyright IBM Corporation 2012

HMC and SDMC appliances IBM i

• Intel-based PC appliance – Required for configuration and management of partitions – Available for POWER5, POWER6, and POWER7 systems

• Main HMC/SDMC applications are: – Server and partition management – Licensed internal code maintenance • HMC/SDMC code maintenance – Independent of managed system or operating systems

• Licensed internal code update flexible service processor (FSP)

– HMC management • HMC/SDMC users • Configuration HMC

– Service applications – System manager security


HMC/SDMC and managed system IBM i

Graphic representation of relationships between: – HMC/SDMC – Service processor – Hypervisor

SDMC

Virtual Server (Partitions): When active

Non-volatile RAM

Hypervisor: OS-independent

Service processor

Processors Mem regions I/O slots

Virtual Server (LPAR) allocation tables

Managed system © Copyright IBM Corporation 2012

Virtual servers consist of different elements (look at colors): •Processors •Memory •I/O slots •Some part of Hypervisor

Managed system without HMC/SDMC IBM i


Power Systems management: Summary IBM i

Power Systems ASMI only  No LPAR  Limited CoD  Basic service functions

ASMI / TTY to FSP directly

IVM only

Desktop HMC

 Entry-level LPAR controls from IVM, based on AIX VIO Server (VIOS)  Limited CoD  Limited service functions

 Basic desktop, worldwide support, long production cycle  Full function LPAR controls  Full service functions  Virtual OS consoles  Redundant HMC optional

Browser to VIOS © Copyright IBM Corporation 2012

Rack-mount HMC  “Stackable”, with shared flat panel/keyboard drawer, well suited for clusters  Full function LPAR controls  Full service functions  Virtual OS consoles  Redundant HMC optional

Hardware Management Console IBM i

• For POWER5, POWER6, and POWER7 systems, the Hardware Management Console (HMC) is required for: – Virtual console windows for partitions – LPAR configuration and operation management – Capacity on demand (CoD) management – Service tools

• PC-based console – Closed custom appliance – Connects to service processor over a private or open network


HMC appliance IBM i

• Integrated, custom HMC software – Provides GUI interface – Is a set of special HMC commands • Remotely accessible • Support for *multiple managed systems – Up to 64 managed systems -- 254 partitions • Active partitions that can continue to function without an HMC

Desktop 7310-C04

– The ability to change resource configuration is lost • Redundant capability Desktop Rack-mount • HMC connection options 7042-C06 7310-CR3 – Private network 7042-CR6 – Open network * 64 if small tier servers; 32 if large tier servers © Copyright IBM Corporation 2012

HMC 7310 models IBM i

• 7310-C06 (desktop)

• 7310-CR3 (rack-mounted)

– Intel Pentium processor (3 GHz)

– Intel XEON processor (3 GHz)

– 1 GB of system memory


– 40 GB minimum hard disk

– 40 GB minimum hard disk

– DVD-RAM for backup

– DVD-RAM for backup

– Two integrated serial ports

– One integrated serial port

– One graphics port


– One integrated 10/100/1000 Mbps Ethernet port

– Two integrated 10/100/1000

– Six USB ports

– Three USB ports

– Two PCI slots

– Two PCI slots

– Mbps Ethernet ports


HMC 7042 models IBM i

• 7042-C06 (desktop)

• 7042-CR6 (rack-mounted)

– Dual-core Intel Xeon 3050, 2 MB cache, 2.13 GHz processor, and 1066 MHz front-side bus

– Dual-core Intel Xeon 5130, 4 MB cache, 2.00 GHz, and 1333 MHz front-side bus


– 80 GB HDD

– 80 GB HDD

– DVD-RAM media: 4.7 GB single-sided DVD-RAM, type 2 media

– DVD-RAM media: 4.7 GB single-sided DVD-RAM, type 2 media


– External modem

– Modem

– One integrated serial port

– Two integrated serial ports

– Two video ports


– Two integrated dual 10/100/1000 Mbps Ethernet ports

– One integrated 10/100/1000 Mbps Ethernet port

– Four USB ports, two front and two rear

– Six USB ports, two front and four rear

– One PCI-x with 133 MHz riser

– Three 32-bit PCI slots

– Optional external USB diskette drive

– Integrated diskette drive


HMC interface IBM i


HMC user interfaces and access IBM i

• Local GUI (on HMC) – Starts automatically whenever the HMC is started (browser-based since HMC V7) – Requires user log in prior to access

• Remote GUI (on network PC) – Uses an installable stand-alone remote client application (WebSM client) • Windows (NT, XP) or Linux • Downloadable as an installable application directly from the HMC through web browser

– Also supported from one HMC to another or from AIX 5L – Can be SSL secured through public/private key files • Generate on the HMC, and transfer to client systems

• Local command line (on HMC) – Launched from a right-click menu option on the HMC desktop – Restricted to a set of supported HMC commands

• Remote command line (on network PC) – Accessed through encryption-protected Secure Shell (SSH) – Can set up and exchange key files to avoid password prompts • Very useful for automation and scripting without human intervention © Copyright IBM Corporation 2012

Remote access to the HMC (browser-based since V7) IBM i


The big picture recap IBM i

Managed system IBM i

Unassigned resources

Linux Partition 2

Partition 1

Ethernet

Non-volatile RAM

POWER Hypervisor

Service Processor

Processors Memory I/O Slots

Ethernet LPAR allocation tables


HMC

Advanced HMC features IBM i

• Dynamic resource allocation • Advanced processor concepts • Virtual I/O • Capacity on demand


Dynamic partitioning IBM i

• Dynamic partitioning (DLPAR) is the ability to add, remove, or move resources between partitions without restarting the partitions. • Resources: – 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. © Copyright IBM Corporation 2012

How DLPAR works IBM i

HMC command

HMC

Partition B

Partition A

POWER Hypervisor © Copyright IBM Corporation 2012

Processor concepts IBM i

LPAR

LPAR

LPAR

Virtual Shared Dedicated Inactive (CoD) Deconfigured

Physical (installed)


Micro-partitioning IBM i

• Time-sliced sub-processor allocations are dispatched according to demand and entitled capacity. Physical processors

P

P

P

P

Shared processing pool © Copyright IBM Corporation 2012

t=0

Partition 1 Partition 2 Partition 3 Partition 4 Partition 5 Partition 6 Partition 7

Virtual I/O IBM i

• Each partition has virtual I/O slots. – This is configurable for each partition.

• Slots can have a virtual adapter instance. – This can be Ethernet, serial, or SCSI.

• It can be dynamically added or removed just like physical I/O slots. – It cannot be dynamically moved to another partition. – The configuration of what is in the slot can be redefined without a restart of the partition.


Virtual I/O example IBM i

Client partition Virtual Ethernet

Server partition

Virtual switch

Virtual Ethernet

POWER Hypervisor Client adapter DMA buffer

Virtual SCSI

Physical Ethernet

Proxy ARP

Physical network

Virtual Disk

NWSD Server adapter

Device mapping

SCSI, SSA, FC physical or logical disks © Copyright IBM Corporation 2012

Capacity on demand IBM i

• Capacity Upgrade on Demand (CUoD) – Permanent activation of processors or memory

• Trial CoD – No charge 30-day activation of processors or memory resources

• On/off CoD – Ability to activate processor or memory resources temporarily Add reserve resources

• Reserve CoD – Processors only – Prepaid for certain number of days


Partitioning concepts summary IBM i

Part#1

Usei IBM

Part#2

Part#3

Part#5

Part#4

Part#6

thisIBM layout for all your i IBMdrawing i AIX 5Lneeds IBM i Linux

Part#7-11 LAN IBM i

PPPPPP PPPPPP MMMMM AAAAAA

PPPP PPP MMMM AAAAA

P MMM AAA

MMM AAAA

M AA

MM AAA

IBM i Kernel

IBM i Kernel

Linux Kernel

IBM i Kernel

AIX 5L Kernel

IBM i Kernel

OptiConnect

P

PPPPPP

Virtual Ethernet

POWER Hypervisor


M M M M M A A

Virtual LAN Virtual I/O O S

O O S S

O O S S

O S S

O O S S

LPAR configuration process IBM i

1

Gather partition requirements through existing data or modeling.

2

Plan resources for partitions (SPT).

3

Set up HMC.

4 Power on and set up managed system. 5 Create and configure partitions. 6 Activate partitions and install operation systems. 7 Configure and test service applications. © Copyright IBM Corporation 2012

Where can I find more information on LPAR? IBM i

• Education: – AS530/OV530: Logical Partitioning (LPAR) on IBM Power Systems with IBM i

• Available links and manuals: – http://www-03.ibm.com/systems/power/software/i/virtualization.html – http://publib.boulder.ibm.com/eserver/ibmi.html

• www.redbooks.com: – SG24-6251: LPAR Configuration and Management – SG24-6209: Capacity Planning for Logical Partitioning


Topic 3: Clustering


7.0

Clustering: What is a cluster? IBM i

• A cluster is a collection of interconnected complete computers, used as a single, unified computing resource. • Some of the attributes of a cluster are: – High availability/continuous availability – Simplified single system management – Scalability/flexibility – High-speed interconnect communications – Shared resources – Workload balancing – Single system image


Types of clusters (1 of 4) IBM i

• Separate servers – Each system has a copy of the disks. – Data is replicated from a source system to one or more target systems. – Local access to the data for updates is only available at the source system. – Servers can be in different locations to withstand single site disaster. © Copyright IBM Corporation 2012

Replicated objects


• Switchable DASD – Disk drives can be switched from one system to another. – Local access to the data is only available from the owning system. – There is a single set of disk drives for all systems. – It is not necessary to replicate data between systems that can own the switchable devices. – This is susceptible to site disaster.


IASP


• Cross site mirrors – Each system has a copy of the disks. – Disk writes are replicated by the IBM Power System with IBM i operating system from one location to another. – Only the production copy is available for use. – Servers can be in different locations to withstand single site disaster.

Mirrored disk writes IASP1


IASP1


• System storage copy services through Peer-toPeer Remote Copy (PPRC) – Each system has a copy of the disks. – Disk writes are replicated by IBM TotalStorage from source disks to target disks. – Only the source copy is available for use. – Servers can be in different locations to withstand single site disaster.


IASP1

PPRC disk writes

IASP1

Elements of a cluster (1 of 5) IBM i

Cluster Administrative domain

Cluster node

CRG A

CRG A

Device domain CRG C CRG B

CRG B

CRG C

Recovery domain Cluster resources (for example, switched disk with IASP)


Cluster resource group



Cluster node CRG A

CRG A


CRG B

CRG C






Cluster node

CRG A

CRG A


CRG B

CRG C

Recovery domain

Cluster resource group Cluster resources (for example, switched disk with IASP)




Cluster node

CRG A

CRG A


CRG B

CRG C

Recovery domain

Cluster resource group Cluster resources (for example, switched disk with IASP)




Cluster node

CRG A

CRG A


CRG B

CRG C




Clustering: Backup example IBM i

Example 1 HABP Replication

Production system

Example 2

Backup of production data available for backups, queries, business intelligence, and so forth

HABP Replication

Order entry Backup of warehouse and distribution data available for fail-over and backups

Backup system

Warehouse and distribution Backup of order entry data available for failover and backups © Copyright IBM Corporation 2012

Clustering: Topology example IBM i

Up to 128 nodes - local and remote Dual hub OptiConnect

LAN

170

170

530

740

750

750 H U B

520

H U B

720

T1 WAN

750

T1 WAN

520

520

Ethernet LAN 520

LPAR 520

ATM WAN 520

520


Where can I find more information on clustering? IBM i

• Education: – AS541/OV541: IBM Power HA for i, Clustering and Independent Disk Pools Implementation

• Available links and manuals: – IBM i Cluster Technology – http://publib.boulder.ibm.com/eserver/ibmi.html

• www.redbooks.ibm.com: – SG24-7994: PowerHA SystemMirror for IBM i Cookbook


Topic 4: Integration of IXA/IXS/xSeries server


7.0

IBM Power System with IBM i and Windows servers IBM i

• IBM Power Systems with IBM i

IBM power-based servers running IBM i

– Enterprise-wide support • • • • • •

Commercial applications Database Reliability Availability Scalability And others

External LAN

• Microsoft Windows servers – Windows NT Server 4.0 – Windows 2000 Server and Advanced Server – Windows 2003 Standard, Enterprise, and web editions – Red Hat Enterprise Linux 3.0 AS or ES Edition


Windows server

Benefits of IBM Power Systems with IBM i/ Windows server integration IBM i

• Server management – Management IBM i and Windows servers

• User administration

IBM Power System with IBM i

– IBM i users, groups, passwords synchronized with Windows

• Virtual Ethernet – Communicate more securely over 1 Gbps virtual Ethernet connections

• Dynamic virtual storage

Windows server on Integrated xSeries Server

– Up to 31 TB per Windows server

• Backups – Consolidate IBM i and Windows backups

• Testing – Logical servers allow testing with the production image and hardware

External LAN

• Hot spare – Easily switch production environment to another server

• Improve Windows server uptime and stability – Update IBM Power System with IBM i device drivers automatically from IBM Power Systems with IBM i

• Reduce total cost of ownership – IBM Power Systems with IBM i warranty and maintenance cover integrated xSeries servers © Copyright IBM Corporation 2012

Windows server

What are we integrating? IBM i

• Windows server applications – Infrastructure servers • • • •

File/print servers Web servers Firewall Others

– Application servers • Exchange/SQL server, and so on

• Thin client environment – Citrix metaframe – Run heavy Windows client application on server; send user interface to the client

• Complementary applications – Client/server applications © Copyright IBM Corporation 2012

Integrated xSeries server: I/O device sharing IBM i

Communications

Disk

Tape drive CD drive


ed rat g e Int eries xS rver Se

Communications

Typical IXS installation IBM i

IBM Power Systems with IBM i disk drives IBM Power Systems with IBM i IBM Power Systems with IBM i

IBM i Console


IXA xSeries adapter: Disk access IBM i

Disks

xSeries

IBM Power System with IBM i High-speed link for disk access

Systems management and power control

Integrated xSeries Adapter

• IXA attaches n-way IBM xSeries servers to IBM Power Systems with IBM i – xSeries server models supported – http://www-03.ibm.com/systmes/i/advantages/integratedserver/ixa/ servermodels/index.html

• Retains features and value of Integrated xSeries server – Uses IBM i storage consolidation and systems management – Has processors, memory, and ServerProven adapters but no disk drives

• Complementary application support • Server consolidation © Copyright IBM Corporation 2012

Shared devices IBM i

Devices on IBM Power System with IBM i

DASD IBM Power System with IBM i

Tape drive

CD-ROM drive © Copyright IBM Corporation 2012

xSeries

IBM Power Systems with IBM i SAN for Windows servers IBM i

Windows servers

• IBM Power Systems with IBM i SAN for multiple Windows servers. – SAN: Storage, fabric, and management

• Consolidation provides simplified management. • Consistent hardware and device drivers can improve Windows stability.


Microsoft Cluster Service IBM i

• Shared drive cluster – Dynamically switch storage spaces between Windows servers – Up to four IXS or IXA server nodes per cluster

C D IXS or IXA

– Planned or unplanned outages

• Requirements

– Microsoft .Net Enterprise for fournode support* * Planned for fourth quarter 2002, dependent on Microsoft delivery © Copyright IBM Corporation 2012

D IXS or IXA

Mail DB IXS or IXA C D

– Windows 2000 Advanced Server for two-node support

C

File Web

– Sixteen new 1 MB to 64 GB shared storage spaces

• Availability improvements

Microsoft Cluster

IXS or IXA

App 1-16 shared storage spaces

C D IBM i

Environment flexibility IBM i

• One IXS/IXA can quickly support different operating environments. – Test Windows service packs during nonproduction times. – Test different Windows server products. – Give developers their own server for off hours work. – Test an application in a number of environments. – Recover a failed server.

Storage space

NWSD NWSD

Windows Server

Windows Server SP n-1

NWSD

Windows Server

NWSD

Windows Server SP n

NWSD: Network server description


Hot spare IBM i

• This is the solution for planned and unplanned xSeries server outages. • Link NWSD to hot spare. – IXS/IXA

• Boot Windows server. • xSeries servers need to have the same configuration. One IXS/IXA can be a hot spare backup. NWSD


Windows Server

NWSD

Windows Server

NWSD

Windows Server SPn

Solution for planned and unplanned IBM Power Systems with IBM i server outages IBM i

Disk tower

A

HSL loop

Integrated xSeries server

NWSD

NWSD

IASP storage spaces Windows server #1 C:,D:,E:,F: Windows server #2 C:,D:,E:,F:

B

HSL loop

NWSD

Integrated xSeries server

NWSD

Windows, applications, and data

• Support for Windows disks in independent ASP – Server A is running with IXS A and direct attached xSeries server A. – Take IBM Power System with IBM i A offline. The disk tower switches to IBM Powerbased servers running IBM i B. Manually link NWSDs to B resource names; then reboot Windows servers. Windows servers are back online on B. – xSeries servers need to have the same configuration. © Copyright IBM Corporation 2012

For more information IBM i

• IBM Power System with IBM i Windows Integration web site: – http://www-03.ibm.com/systems/i/advantages/integratedserver/ • Product information • Service information (PTFs) • Library

• IBM Power System with IBM i InfoCenter: – http://publib.boulder.ibm.com/eserver/ibmi.html • Articles on Windows Servers on the IXS/IXA • Select: Network Operating Systems....Windows server on IBM Power Systems with IBM i

• Redbooks: www.redbooks.ibm.com – SG24-6056: Consolidating Windows 2000 Servers in iSeries – SG24-6222: Direct Attach xSeries for the IBM eServer iSeries Server: A Guide to Implementing xSeries Servers in iSeries – SG24-2164: AS/400 - Implementing Windows NT on the Integrated Netfinity Server © Copyright IBM Corporation 2012

Topic 5: Additional topics


7.0

Alternate installation device IBM i

• Without – Installation and recovery from the devices attached to the first system bus (connected to service processor IOP)

• With – Installation and recovery from devices attached to the first system bus, only enough LIC to perform an IPL with IPL-type D – Continues using media in an alternate installation device, such as: • SAVSYS tapes • User-created distribution tapes with LIC and possibly operating system, licensed programs, and data

– Might improve performance


Uninterruptible power supply IBM i

• Benefits – Continue operations during brief power interruption – Provide orderly shutdown and avoid lengthy recovery (IPL) 11

12

1

10

2 3

9 4

8 7

Without: Objects might be damaged; recovery time might be significant. © Copyright IBM Corporation 2012

6

5

UPS: System values IBM i

QUPSMSGQ

QUPSDLYTIM

QPWRRSTIPL

QSYSOPR

*CALC

'1' The system determines when to save main storage and power down.

Messages related to uninterruptible power supply

QSYSOPR message queue

Timer


If utility power is restored, should the system automatically IPL?

Power System with IBM i

UPS: When power fails IBM i

• The UPS/battery power is used. • The system checks QUPSDLYTIM QUPSMSGQ. • The operator or program executes PWRDWNSYS. • At QUPSDLYTIM, the IBM Power System with IBM i initiates QUICK POWER DOWN.

180 Special


UPS: Time line of QUPSDLYTIM function IBM i

Utility power goes off

Time UPS can run Actions by operator or program:

Run

PWRDWNSYS

Save of main storage controlled shutdown

Safety margin

Safety margin

QUPSDLYTIM

Time

UPS active

QUPSDLYTIM time-out


Controlled shutdown completes

UPS: Power loss controlled shutdown IBM i

• Utility power lost • UPS and QUPSDLYTIM expires • Jobs signaled to end at next instruction boundary • Main storage written to disk (while running on UPS) • System powered off • Utility power returns • IPL is normal for LIC, abnormal for IBM i


UPS: Power handling program IBM i

• Must allocate message queue in QUPSMSGQ • Can operate under uninterruptible power supply • Take actions: – Send messages to users. – End batch jobs and subsystems. – Change system values. – Issue PWRDWNSYS before the system goes into a power loss controlled shutdown.


Availability: Dual systems IBM i

• For installations with high-availability requirements: Redundant systems, redundant data • Requires two systems: One primary, and one backup • Database changes sent to backup system through the journal receiver • User program updates backup database from the journal receiver



1. True or False: Whenever there is a disk failure on the system, this will force a full recovery of all data. 2. Which of the following is a hardware availability function designed to protect data from loss due to two disk unit failures or because of damage to two disks? a. RAID 5 b. RAID 6 c. Mirroring d. Concurrent maintenance support 3. Which of the following provides a means to save an object while the system remains active and users are working with the data? a. Parallel save b. Save of all user data c. Save changed objects d. Save-while-active



1. True or False: Whenever there is a disk failure on the system, this will force a full recovery of all data. The answer is false. 2. Which of the following is a hardware availability function designed to protect data from loss due to two disk unit failures or because of damage to two disks? a. b. c. d.

RAID 5 RAID 6 Mirroring Concurrent maintenance support

The answer is RAID 6. 3. Which of the following provides a means to save an object while the system remains active and users are working with the data? a. b. c. d.

Parallel save Save of all user data Save changed objects Save-while-active

The answer is save-while-active. © Copyright IBM Corporation 2012


4. The maximum number of partitions supported on POWER4-based hardware is _____. The maximum number of partitions supported on POWER5 and POWER6-based hardware is ____ . The maximum number of partitions supported on POWER7-based hardware is _____. a. POWER4 = 32 POWER5 and POWER6 = 254 POWER7=1000 b. POWER4 = 64 POWER5 and POWER6 = 128 POWER7=512 c. POWER4 = 128 POWER5 and POWER6 = 64 POWER7=254 d. POWER4 = 254 POWER5 and POWER6 = 32 POWER7=128 e. POWER4, 5, and 6 support the same number of partitions, but POWER7 supports 1000. 5. Which of the following are resources that can be allocated to an LPAR? Select all that apply. a. Only whole processors b. Memory c. I/O adapters d. Disk drives e. Operating system software 6. Which of the following is not supported in an IBM Power System with IBM i partition? a. AIX b. Linux c. IBM i d. Windows server software



4.

The maximum number of partitions supported on POWER4-based hardware is 32. The maximum number of partitions supported on POWER5 and POWER6-based hardware is 254. The maximum number of partitions supported on POWER7-based hardware is 1000. a. POWER4 = 32 POWER5 and POWER6 = 254 POWER7 = 1000 b. POWER4 = 64 POWER5 and POWER6 = 128 POWER7=512 c. POWER4 = 128 POWER5 and POWER6 = 64 POWER7=254 d. POWER4 = 254 POWER5 and POWER6 = 32 POWER7=128 e. POWER4, 5, and 6 support the same number of partitions, but POWER7 supports 1000. The answer is POWER4 = 32, POWER5 and POWER6 = 254, and POWER7 = 1000.

5.

Which of the following are resources that can be allocated to an LPAR? Select all that apply. a. Only whole processors b. Memory c. I/O adapters d. Disk drives e. Operating system software The answers are memory, I/O adapters, and disk drives.

6.

Which of the following is not supported in an IBM Power System with IBM i partition? a. AIX b. Linux c. IBM i d. Windows server software The answer is Windows server software.



7.

True or False: Each LPAR requires a separate license from IBM for the OS installed in that LPAR.

8.

Which of the following is one of the supported type of clusters that can be set up?

a. b. c. d. e.

9.

Separate servers Switchable DASD Cross site mirrors System storage copy services Hot site immediate switchover

A ____ is a system or partition that is in a cluster. a. b. c. d.

Separate server Switchable DASD server Cross site mirror Cluster node

10. Which of the following cannot be shared on an IBM Power System with IBM i and integrated xSeries server? a. b. c. d.

Tape drive DASD Memory CD-ROM drive © Copyright IBM Corporation 2012


7.

True or False: Each LPAR requires a separate license from IBM for the OS installed in that LPAR. The answer is false.

8.

Which of the following is one of the supported type of clusters that can be set up? a. Separate servers b. Switchable DASD c. Cross site mirrors d. System storage copy services e. Hot site immediate switchover The answer is hot site immediate switchover.

9.

A cluster node is a system or partition that is in a cluster. a. Separate server b. Switchable DASD server c. Cross site mirror d. Cluster node The answer is cluster node.

10.

Which of the following cannot be shared on an IBM Power System with IBM i and integrated xSeries server? a. Tape drive b. DASD c. Memory d. CD-ROM drive The answer is memory. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • Explain the concept of availability • Describe the different types of failures that can occur • Describe hardware and software availability features • Explain the concept of logical partitioning (LPAR) • List some of the reasons to implement LPAR • Explain the functions served by a Hardware Management Console (HMC) • Explain the concept of clustering • List the different types of clustering that can be implemented • Explain the different ways an xSeries can be integrated with the IBM Power System with IBM i • Describe the consequences for a company if the IBM Power System with IBM i are not available to perform normal business © Copyright IBM Corporation 2012

Disk management


7.0


After completing this unit, you should be able to: • Explain the concept of disk pools • List the different types of auxiliary storage pools (ASPs) that can be configured • Explain some of the benefits of implementing the different types of ASPs • Explain the concepts of device parity and mirrored protection • Explain the difference between RAID-5 and RAID-6 protection • Describe the different levels at which mirrored protection can be implemented • Describe how to find the correct procedure for disk configuration and recovery • Describe the disk unit functions of IBM i Navigator • Describe the effects of an abnormal system end and the recovery procedure © Copyright IBM Corporation 2012

Topic 1: Concepts and overview of auxiliary storage pools


7.0

Types of disk pools (1 of 2) IBM i

System

User

Basic

Independent

Secondary Secondary

Primary © Copyright IBM Corporation 2012

UDFS

Types of disk pools (2 of 2) IBM i

• System ASP – ASP# 1 – IBM i operating system

• Basic – ASP# 2-32 – Also known as user or dependent ASPs

• Independent (IASP) – ASP# 33-255 – User-defined file system (UDFS) (V5R1) – Primary (QSYS.LIB objects) (V5R2 and up) • Secondary

• Disk pool, IASP, and database can be used interchangeably


Disk pool groups IBM i

• Made up of: – A primary disk pool – Zero or more secondary disk pools

• Groups logically connect disk pools – Vary them on and off together – Switch them together

The system database is referred to as *SYSBAS. System ASP

Basic 2-32

iASP# 33-255

• Share the same database – Similar as system ASP and basic ASPs – For example:

Pool groups for multiple databases UDFS

• Primary independent ASP for libraries and database files • Secondary independent ASP for journals and journal receivers

Primary

Primary

Secondary

Primary

Secondary

• Do not overflow – If a disk pool fills, no more data can be added, but the system keeps running.


Secondary

System auxiliary storage pool IBM i

Logically one container SYSTEM ASP (ASP1)

Customer

Master file

• Disk failure – What is lost? – What needs to be restored? – How long will it take? © Copyright IBM Corporation 2012

ASP benefits IBM i

• Data protection – Isolate effects of a disk failure

• Improved performance – High use objects – Separate files and journal receivers

• Separate by availability and recovery requirements – Different disk protection techniques by ASP – Different target recovery times for recovering access paths


System ASP (ASP1) IBM i

• Automatically created • Load source (unit one) and all units not in user ASPs • System objects and objects not in user ASPs • Abnormal end if full – Threshold percent: QSYSOPR Message – QSTGLOWLMT:

Low limit of available storage

– QSTGLOWACN:

Action when QSTGLOWLMT reached

• QSYSOPR message or critical message • Call registered (ADDEXITPGM) exit programs • ENDSYS or PWRDWNSYS

• If ASP1 lost, addressability of objects in user ASPs lost – RCLSTG or restore entire system – If RCLSTG, QDFTOWN will own all objects © Copyright IBM Corporation 2012

IBM Power Systems with IBM i Navigator: Storage System Values IBM i


User ASPs (ASP2-ASP32) IBM i

• Library user ASP (preferred type) – Library or folder in ASP first – Most object types allowed

• Non-library user ASP – Only journals, journal receivers, and save files – Library in system ASP1

• Overflows to ASP1 if filled up – Threshold percent: QSYSOPR message – Protection lost; recovery actions required


Additional ASP considerations IBM i

• Objects exist within an ASP. • They are logical group of units, not a physical grouping or hardware function. • Additional disk units might be required. • Should be protected by device parity protection or mirrored protection. • Journals and their files must be in the same ASP. • Physical files and dependent logical files must be in the same ASP. • They can contain SQL schemas. • Configuring and setting threshold requires DST/SST.


Sample configuration IBM i

• ASP 1: (System ASP) • ASP 2: Libraries with save files • ASP 3: Libraries with journal receivers • ASP 4: Libraries with database files and journals • ASP 5: Document library with folders and documents


Benefits of independent disk pools IBM i

• Single-system environment – – – – – –

Isolate low-use data with ability to bring online only when needed. Reduce system start time. Manage save/restore by independent disk pool. Reclaim storage by independent disk pool. Divide data between multiple databases. Isolate data associated with specific applications or associated with specific groups of users. – Consolidate data on small systems to independent disk pools on a larger system, for example, in the case of multiple branch offices. – Perform application maintenance that does not affect entire system.

• Multisystem clustered environment – Keep data available to an application even in the event of a single system outage, either scheduled or unscheduled. – Eliminate the process of replicating data from one system to another. – In some situations, isolate disk unit failures within the independent disk pool. – Achieve high availability and scalability. © Copyright IBM Corporation 2012

IASPs in a single system environment IBM i


IASPs in a multisystem environment IBM i

Server B

Server A Dev CRG 1

Server C

Dev CRG 1 Dev CRG 2

Server D

Dev CRG 2

Switchable towers

Drives Drives

Drives Drives

IASP A1

Device domain


IASP A2

IASP A4 IASP B3

Topic 2: Concepts and overview of device parity protection: RAID-5 and RAID-6


7.0

Device parity protection (1 of 2) IBM i

How can I keep the system running while the drive is being replaced and data rebuilt?


Implement device parity protection (RAID-5 and RAID-6).

Device parity protection (2 of 2) IBM i

PS1

PS1

DS1

DS1

DS2

PS2

DS2

DS2

DS3

DS3

PS3

DS3

DS4

DS4

DS4

PS4

Rebuild PS = Parity sector DS = Data sector © Copyright IBM Corporation 2012

RAID-5 and RAID-6 IBM i

RAID-5

RAID-6

Protection

One additional disk drive per RAID array

Two additional disk drives per RAID array

Minimum size array

Three disks

Four disks

Maximum size array

18 disks

18 disks

Supporting disk IOAs

#5709/5726/5727/5728 (CEC), #5703, #2757/5581, #2780/5580, #5737/0648, #4778, and so forth

#5737/0648/5776

Supporting IBM i

Lots of releases

V5R3 or later

Performance implication

Known

Similar to 5703 running RAID-5


Device parity protection benefits IBM i

• Lost data is automatically reconstructed after a disk failure. • System continues to run after one disk failure with RAID-5 or after up to two disk failures with RAID-6 protection. • Failed disk units can be replaced without stopping the system. • It reduces the number of damaged objects when disks fail. • One or two disk units of capacity stores parity data in parity set.


Device parity protection on input/output adapters IBM i

• It provides high availability through device parity protection for disk units capable of device parity protection. • When parity is started, the IOAs create parity sets. • A parity set can only tolerate one or two disk failures. • Additional disks can be included into a parity set after it is started. • All devices in a parity set must be the same capacity. • Starting at V5R2 and later IOA, you have the ability to choose how you want the parity set to be optimized.


Device parity protection limitations IBM i

• RAID-5 – Single disk unit failures • Performance decrease during data reconstruction

– Multiple unit failures (more than one) • System becomes unusable • ASP data must be restored

• RAID-6 – Two disk unit failures • Performance decrease during data reconstruction

– Multiple unit failures (more than two) • System becomes unusable • ASP data must be restored

• BUS, IOP, IOA failures – System outages might result

• Restore operations might take longer • Might decrease performance • Not supported for load source attached to a 6502 or 6512 IOP or to older type units without the high availability option © Copyright IBM Corporation 2012

New disk protection IBM i

RAID-5

Good

RAID-5 plus write cache protection

RAID-6 plus write cache protection

BETTER Better

Best

(but exposed cache) This protects against single disk drive failure (per array).

This protects against single disk drive failure (per array).

This protects against two disk drive failures (per array).

It also protects against extended outage due to loss of write cache.

It also protects against extended outage due to loss of write cache.


Topic 3: Concepts and overview of mirrored protection


7.0

Mirrored protection: Introduction IBM i

Is there anything that could make the system even more available? Implement mirrored protection!


Mirroring definitions IBM i

• Without mirroring, one unit equals one actuator

I/O Adapter

Unit 1

Unit 2

Unit 3

Unit 4

• With mirroring one unit equals two actuators (a mirrored pair)

I/O Adapter

Unit 1

Unit 2 © Copyright IBM Corporation 2012

Mirrored protection: Benefits and considerations IBM i

• Benefits – Disk units (and data) duplicated – Continue to run, without restore, after disk failure – Concurrent or deferred maintenance – Better performance than device parity protection – Easy and fast to start and stop

• Considerations – Continue to run after multiple disk failures but not both units in mirrored pair – Synchronization after replacing failed disk affects performance – Possible increased IPL time after abnormal end to synchronize data – Additional hardware


Disk-level mirrored protection IBM i

Bus

Input/output processor

I/O Adapter (IOA)

Disk unit

Disk unit © Copyright IBM Corporation 2012

IOA-level mirrored protection IBM i

Bus

IOP

I/O Adapter

I/O Adapter

Disk unit


IOP-level mirrored protection IBM i

Bus

IOP

IOP

I/O Adapter

I/O Adapter

Disk unit

Disk unit


Bus-level mirrored protection IBM i

Bus1

Bus2

IOP

IOP

I/O Adapter

I/O Adapter

Disk unit


Remote DASD mirroring IBM i

• Can mirror LSU, other DASD, or both • System cannot IPL from remote bus • Provides bus-level protection • Note: Fiber optics distance limitations apply:

Mirror Mirror DASD LSU

Bus 2

– 500 meters for high speed bus (1063 Mbps) – 200 meters for low speed bus (266 Mbps)

MFIOP Bus 1

Remote location SEU

DASD Bus 3 LSU = Load Source Unit SEU = System Expansion Unit

SEU

LSU


Advantages and disadvantages of remote mirroring IBM i

• Advantages – IOP-level or bus-level protection for the load source – Protection against site disaster

• Disadvantages – Only able to IPL from one DASD of the load source mirrored pair – If IPL load source fails • Cannot dump main storage • Cannot use CPM


Mirroring performance IBM i

• There is equal or better performance for reads. • There is a slight decrease in performance for writes. • IPL after abnormal end might be longer if synchronization is necessary. • You will notice a decrease in performance while mirroring is first being started and while a failed disk is being replaced. • Machine pool: Increase size approximately 12 KB per GB of mirrored storage. • Maintain ratio of disk units to I/O processors. © Copyright IBM Corporation 2012

Concurrent maintenance IBM i

• Replace or repair failing hardware while the system runs. • Mirroring level <----> level of concurrent maintenance. • SST: Disk support tools are available. • ECS is available to report a problem. • Some repairs require active units to be suspended. – You can choose to defer maintenance.

• Some repairs require the system to be powered off (deferred maintenance). © Copyright IBM Corporation 2012

Mirrored protection planning IBM i

• Decide which ASP or ASPs to protect. • Determine disk storage capacity requirements. • Determine the level of protection you want for each mirrored ASP. • Determine the extra hardware you need for mirrored protection. • Determine the extra hardware you need for performance. • Order your hardware. • Plan the installation of your system and the configuration of new units. • Install the new hardware. © Copyright IBM Corporation 2012

Mirrored failure scenario IBM i

• Storage management detects unrecoverable disk failure. • System does not shut down. • Protection is lost only on that mirrored pair. • Storage management suspends failing device of mirrored pair. • Message is sent to QSYSOPR. • Repair or replace failing device. • Mirroring is resumed automatically for replaced units. • If necessary, resume mirrored protection for repaired or suspended units. © Copyright IBM Corporation 2012

Mirroring versus device parity protection IBM i

Availability

Performance

Cost

1

Mirrored protection

Mirrored protection (*see note)

Device parity protection

2



Mirrored protection


Comparison of disk protection tools IBM i


Mirrored protection

Protect from data loss due to disk-related hardware failure

Yes

Yes

See note 2

See note 2

Maintain availability

Yes

Yes

No

Yes4

Help with disk unit recovery

Yes

Yes

Yes4

Yes2

Maintain availability when disk IOA fails

No

Yes1

No

No2

Maintain availability when disk I/O processor fails

No

Yes1

No

No5

Maintain availability when disk I/O bus fails

No

Yes1

No

No5

Site disaster protection

No

Yes3

No

No5

Ability to switch data between systems

No

No

No

Yes

What is needed?


User ASPs

Independent disk pool

Full disk protection IBM i

• System remains operational with no data loss for one disk (RAID-5) or two disk (RAID-6) failures. • Use device parity protection for hardware that is capable. • Use mirrored protection for all ASPs. • Assign user ASPs as desired. – Performance – Backup requirements


Partial disk protection: Multiple ASPs IBM i

• Divide critical application and data into different ASPs. – Critical: ASP1 (load source, security, configuration, library addresses) – Critical business applications – Critical: ASPs with journal receivers – Not critical: ASPs with infrequently changing data (history data, programs)

• Protect critical ASPs with device parity protection and mirrored protection. • The system continues to run for single disk failure in protected ASP. • With an unprotected disk failure: – System might become unusable and abnormally end – Possible long recovery – Must restore data in ASP with failed disk © Copyright IBM Corporation 2012

Cross-site mirroring (XSM) IBM i


Cross-site mirroring: General IBM i

• Independent from local DASD protection – Unprotected, RAID-5/RAID-6, and mirroring possible

• Mirrored IASP size and where to start – No need for the same size – Start configuration from server owning smallest size IASP – Swap roles when still empty as required – Threshold value

• Good housekeeping required – Changes of user dependent objects in *sysbas – XSM in combination with high availability business partner software

• All pools in a disk pool group switch together • Planning required – Example: Bounded IP routes © Copyright IBM Corporation 2012

Cross-site mirroring considerations IBM i

• Dependencies – IASP state synchronized automatically • Example: Production is available; mirrored copy is varied on.

– No concurrent operations or data access on mirrored copy when varied on – IBM Power System with IBM i Navigator shows pending

• Recovery time out – Time before XSM suspends – Consider redundant communication paths

• Performance – – – –

Input/Output intensive work Read to write ratio Asynchronous compared to synchronous Main storage

• Consequences of detaching and attaching a mirrored IASP copy – Resynchronization time depends on size and on communication bandwidth. – Most environments are not suitable for backup to tape operation. – Create a different device description before using a detached mirrored copy. © Copyright IBM Corporation 2012

Topic 4: Disk configuration and recovery


7.0

Disk configuration and protection procedures Tr an sfe rD AS D Tr an sfe ro bje cts Th re sh old

St ar

t/s

top

sp ac e

DA SD

Ca lcu lat e

Ad d/ re m ov e

Co nf igu re

DA SD

IBM i

Mirrored protection Disk compression Device parity protection

ASPs LPARs

Backup and Recovery manual Select appropriate checklist #1 1 2 3 4

#2 1 .2

. .


#3 1 2

. . .

...

Recovery of disk failure or disk errors (1 of 2)

1

Backup and Recovery manual Select Disk recovery checklist #1 1 2 3 4

#2 1 2


...

fu l? es s su cc

Pu m p

on fig ur ed ?

AS

Ps c

pr ot ec tio n?

M

irr or ed

pa rit y

De v

W hic

h

ice

un it

fa ile d?

pr ot ec tio n?

IBM i

Recovery of disk failure or disk errors (2 of 2)

Pr oc ed ur e

Al lA SP sb

ein g

re co ve re d? us ed to sa SA ve da re VCH ce ta G O ive BJ rs to s or ap j ply ourn al ? W he th ro the ug r t o h m rec en u over op tio ns

IBM i

Backup and Recovery manual Select checklist to recover user data

2

#1 1 2 3 4

#2 1 2


...

DASD management IBM i

• Application administration required: Service tools server DST authority for: – Complete DASD management – DST support (subset) – View and add disk units – Disk balancing – Create and manage ASPs and disk units – Create and manage independent ASPs (disk pools equal private pools) – Compression © Copyright IBM Corporation 2012

Application administration: Disk units IBM i


Steps to allow Navigator users to access DST IBM i

• While in IPL – DST mode or in run time DST mode: – Sign on to Service Tools Security. – Define additional service tools user profiles. – By default a profile is created with no privileges. (Grant those privileges that will be assigned to this user.)

• Add the following Service Table entry: ADDSRVTBLE SERVICE('as-sts') PORT(3000) PROTOCOL('tcp') TEXT('Service Tools Service') ALIAS('AS-STS') – End TCP (ENDTCP), and then start TCP (STRTCP). © Copyright IBM Corporation 2012

Disk unit management: Sign-on IBM i

• The Navigator disk management user must have application administration and disk management authorization. • The Navigator disk management user must have service tools user profile/authority.


Disk properties: General IBM i


Disk properties: Status and Capacity IBM i

• Status: Activity, Protection, Percent busy, and so on • Capacity: Total capacity, Used space, and Percent used


Disk properties: Physical Location IBM i


Adding Disk Units IBM i


Add Disk Unit wizard (1 of 8) IBM i

• The Welcome page explains the tasks that the wizard helps you with. – – – –

Add disk units to an existing disk pool. Create a new disk pool and add disk units to it. Include nonconfigured disk units in a device parity set. Start device parity protection.



• Choose disk storage pool – This page displays the disk pools that are currently defined on the system. • You can add a disk unit to one of these disk pools, or you can click New Disk Pool to create a new disk pool.

– When you click Next, you can select from a list of available disk units.



• Add to Disk Pool: Mirrored disk pairs – This page displays a list of available disk pairs that can be added to a mirrored set.



• Select the disk unit to be added at this time, and click Add. – Add to Disk Pool: Single disks for RAID



• Disk balancing – Choosing Yes, balance disk pools moves data so that each disk unit in the disk pool has an equal percentage of used and unused space*.

* Subset of functions is available through STRASPBAL command. © Copyright IBM Corporation 2012


• Continue Adding – Selecting No, I am done adding Disk Units takes you to the summary screen. – Selecting Yes, I want to add Disk Units to a Disk Pool brings you back to the add disk screen.



• Summary – This page displays the complete configuration and reflects all of your choices so far.



• Add Disk Unit Status – This window displays the progress of each operation you have selected.


Disk pool: Graphical view IBM i

• Manage Disk Units Graphical View by: – All Disk Units – Disk Pools – I/O Processor – Parity Set – Mirrored Pairs – Nonconfigured Disk Units – Active Disk Units – Empty Slots – Print Disk configuration – All valid sides of the Tower Tool Tip


Disk pool properties: General IBM i


Disk pool properties: Threshold and Capacity IBM i


Disk pool properties: Balance / Trace IBM i


New Disk Pool wizard (1 of 2) IBM i


New Disk Pool wizard (2 of 2) IBM i

• Use the New Disk Pool dialog to select the basic numerical identifier for your new disk pool from a list of all available numerical identifiers.


Independent disk pools (1 of 2) IBM i

• Need IOP and disk devices unassigned to system ASP or existing user/independent ASP on node one. • Assign a meaningful name.


Independent disk pools (2 of 2) IBM i

• Let the wizard find the available disk devices. • Add the devices to the pool. • Specify balancing, compression, and protection (RAID or mirroring).


Topic 5: Abnormal system end


7.0

Abnormal system end IBM i

• Causes of an abnormal end: – Power failure – Disk failure – Failure of critical IBM i program

• What might not have been finished: – Changed pages written to auxiliary storage – Closing of files and access paths – End of programs at natural points


Restart after abnormal end IBM i

• Actions taken by the system: – – – – –

Close files that were in use. Rebuild access paths that were open. Verify file constraints. Generate disk configuration error report if disks are inaccessible. For serious software problems, prompt to copy main storage dump.

• Normal IPL: – System determines when to rebuild and verify.

• Attended IPL (refer to Backup and Recovery manual for specific procedure): – Edit Rebuild of Access Paths display. – Edit Check Pending Constraints display.

• Recover from damaged objects and unreadable sectors (see Backup and Recovery manual for specific procedures). © Copyright IBM Corporation 2012

Edit Rebuild of Access Paths IBM i


Edit Check Pending Constraints IBM i



1. True or False: The terms disk pool and IASP are terms that are not interchangeable. 2. The maximum number of basic ASPs you can create is ____, and the maximum number of IASPs you can create is ____. a. b. c. d. e.

32 and 255 64 and 128 128 and 64 255 and 32 The number is the same for both

3. ________ is a hardware function that protects data from being lost because of one disk unit failure or damage to the disk drive. a. b. c. d.

Mirroring RAID-5 RAID-6 IASPs © Copyright IBM Corporation 2012


1. True or False: The terms disk pool and IASP are terms that are not interchangeable. The answer is false. 2. The maximum number of basic ASPs you can create is 32, and the maximum number of IASPs you can create is 255. a. 32 and 255 b. 64 and 128 c. 128 and 64 d. 255 and 32 e. The number is the same for both The answers are 32 and 255. 3. RAID-5 is a hardware function that protects data from being lost because of one disk unit failure or damage to the disk drive. a. Mirroring b. RAID-5 c. RAID-6 d. IASPs The answer is RAID-5. © Copyright IBM Corporation 2012


4.

______ is a type of disk protection that is implemented through software. a. RAID-5 b. RAID-6 c. Mirroring d. ASPs

5.

Mirroring can be implemented at which of the following levels? a. Disk b. IOA c. IOP d. Bus e. All of the above

6.

True or False: The ability to access and manage disk units is a function that is automatically available when you install IBM i Navigator.



4. Mirroring is a type of disk protection that is implemented through software.

a. b. c. d.

RAID-5 RAID-6 Mirroring ASPs

The answer is mirroring. 5. Mirroring can be implemented at which of the following levels?

a. b. c. d. e.

Disk IOA IOP Bus All of the above

The answer is all of the above. 6. True or False: The ability to access and manage disk units is a function that is automatically available when you install IBM i Navigator. The answer is false.



7. True or False: The OS security officer user ID and password are different from the service tools security officer user ID and password. 8. Which of the following is not usually the cause of an abnormal system end? a. Power failure b. Disk failure c. User error d. Failure of critical IBM i program 9. True or False: During a normal IPL, after there has been an abnormal end, the system determines which access paths need to be rebuilt. 10. True or False: During an attended IPL, after there has been an abnormal end, the user is not presented with any options for rebuilding access paths.



7. True or False: The OS security officer user ID and password are different from the service tools security officer user ID and password. The answer is true. 8. Which of the following is not usually the cause of an abnormal system end? a. b. c. d.

Power failure Disk failure User error Failure of critical IBM i program

The answer is user error. 9. True or False: During a normal IPL, after there has been an abnormal end, the system determines which access paths need to be rebuilt. The answer is true. 10. True or False: During an attended IPL, after there has been an abnormal end, the user is not presented with any options for rebuilding access paths. The answer is false. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • Explain the concept of disk pools • List the different types of auxiliary storage pools (ASPs) that can be configured • Explain some of the benefits of implementing the different types of ASPs • Explain the concepts of device parity and mirrored protection • Explain the difference between RAID-5 and RAID-6 protection • Describe the different levels at which mirrored protection can be implemented • Describe how to find the correct procedure for disk configuration and recovery • Describe the disk unit functions of the IBM i Navigator • Describe the effects of an abnormal system end and the recovery procedure © Copyright IBM Corporation 2012

Backup and recovery strategy using save/restore


7.0


After completing this unit, you should be able to: • List the different types of failures that can occur on the system • List the different media types that can be used for backup of your data • Perform the steps required to set up and use a virtual tape drive • Explain which commands are used to save which types of data • Explain the difference between the SAVSYS and SAVSYSINF command • Identify the procedures used to save and restore different types of system information


Topic 1: Overview of the save/restore capabilities


7.0

How important is save/restore? IBM i

It is the foundation on which your disaster recovery plan is built. Your company

Disaster recovery plan

Disaster recovery plan

Save/restore


Uses for the save and restore capabilities IBM i

• Recover from program or system failure. • Save system storage. • Exchange information between systems. • Store infrequently used objects offline. • Note: Normally, objects are frequently saved and infrequently restored.


Failures that can occur IBM i

• Six general types: – Disk failure – System failure – Power failure – Program failure – Human error – Complete system loss

• Objective: Get your applications back online as soon as possible.


Topic 2: Media used to back up your system


7.0

Managing tapes IBM i

• Tape management – Rotating tapes – Naming and labeling tapes – Preparing tapes and tape drives – Verifying tapes – Storing tapes – Monitoring tapes for errors


Tape and tape library system IBM i

• Various sizes and capacities are available. – ½ inch, ¼ inch, and 8 mm – Data compression/compaction (selected models)

• Support for parallel tape operations is: – Available on systems that are at V4R4 and higher – Available through a set of APIs (since V5R4) – Supported as a part of standard operations in Backup Recovery and Media Services (BRMS) – Allows use of more than one media device simultaneously

• Two categories of hardware are available. – Automated tape devices: Automatic cartridge loader and tape libraries • Combination of hardware and software • Allows for storing, cataloging, and loading tapes • Supported by Backup Recovery and Media Services (BRMS)

– Single tape devices


Tape library: Operating modes IBM i

• Most tape library devices support three basic modes of operation: – Manual mode • When a tape library is in this mode, it behaves like a stand-alone tape device, and all cartridges must be manually loaded. Refer to Using a Tape Resource as a Stand-alone Device for more information on using a tape library as a stand-alone device.

– Automatic cartridge loader mode • In this mode, the tape library behaves like a stand-alone tape device with an automatic cartridge loader. When a cartridge is unloaded, the next cartridge is automatically loaded until all cartridges have been used.

– Library mode • When a tape library is in this mode, tape automation is available (also known as random mode).


IBM i Navigator: Manage tapes and tape libraries IBM i

Right-click


IBM Systems Director Navigator for i: Manage tapes and tape libraries (1 of 3) IBM i






Devices: Tapes and tape libraries IBM i

WRKCFGSTS

WRKMLBSTS


INZTAP: Initialize Tape IBM i


Virtual tape support IBM i

• Key advantages – Supported on all save/restore commands, virtual I/O, and APIs (except SAVSTG) – Can be faster than saving directly to tape – Eliminates the following save file limitations – Eliminates media error limitations – Once checkpoint is reached, saves can be restarted – Duplicate saves to media (DUPTAP or DUPMEDBRM) – On-site and off-site storage


Virtual tape implementation IBM i

CRTIMGCLG

ADDIMGCLGE

(3)

(4)

LODIMGCLG

(5) CRTDEVTAP

(1) WRKCFGSTS

(2)


Create a virtual tape device description (1 of 2) IBM i

• Create with the CRTDEVTAP command • Can change existing device description to become a virtual tape device


Create a virtual tape device description (2 of 2) IBM i

• Create with IBM i Navigator


Create the image catalog for virtual tape support IBM i

• CRTIMGCLG command • Create using System i Navigator


Create image catalog through System i Navigator IBM i


Create new virtual volume using WRKIMGCLG command or ADDIMGCLGE command IBM i


System i Navigator: Create new virtual volume IBM i


LODIMGCLG command (using WRKIMGCLG) IBM i


Load Image Catalog (using IBM i Navigator) IBM i


Virtual tape actions by IBM Systems Director Navigator for i (1 of 2) IBM i


Virtual tape actions by IBM Systems Director Navigator for i (2 of 2) IBM i


Optical storage IBM i

• Optical device – CD-ROM or DVD-ROM drive – Optical media libraries

• Virtual optical storage – Ability to duplicate to physical media – Save cumulative PTF record – Save to virtual optical • • • • • • •

Create a virtual optical device Vary on the device Create an image catalog Add a new image catalog entry Load the image catalog Initialize the new volume Run the save command © Copyright IBM Corporation 2012

Exercise: Media devices and virtual tape IBM i

At the end of the lab, you should be able to: • Issue the commands to display what backup devices are recognized by the OS • Perform the steps necessary to create and load virtual tapes to be prepared for a save operation • Note: The student user ID and password has changed. Specifics are in the student notes and in the lab exercise.


Topic 3: Save operations


7.0

SAV commands and menu options IBM i Commands

Options from Save menu

22

Licensed Internal Code i5/OS objects is QSYS

User profiles 23 Private authorities

SAVSYS

SAVSECDTA

Configuration objects

SAVCFG

IBM-supplied directories

SAV

SAVSTG (see notes)

i5/OS optional libraries

21

QHLPSYS

QUSRTOOL

Licensed program libraries QRPG

QCBL

Qxxxxx

IBM libraries with user data QGPL QUSRSYS QS36F #Library

SAVLIB *IBM SAVLIB *NONSYS SAVLIB *ALLUSR

All user libraries 23

Documents and folders Distribution objects User objects in directories © Copyright IBM Corporation 2012

SAVDLO

SAV

Save menu (second screen) IBM i


SAVE option 21: Entire system IBM i

ENDSBS SBS(*ALL) OPTION(*IMMED) CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK OR *NOTIFY) SAVSYS SAVLIB LIB(*NONSYS) ACCPTH(*YES) SAVDLO DLO(*ALL) SAVFLR(*ANY) SAV DEV( ' /QSYS.LIB/TAPxx. DEVD' ) OBJ( ( ' / *' ) ( ' /QSYS.LIB' *OMIT) ( ' /QDLS' *OMIT) ) (1) UPDHST(*YES) STRSBS SBSD (controlling subsystem) Where xx is the name of the tape drive.


SAVE option 22: System data only IBM i

ENDSBS SBS(*ALL) OPTION(*IMMED) CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK OR *NOTIFY) SAVSYS SAVLIB LIB(*IBM) ACCPTH(*YES) SAVDLO DLO(*ALL) SAVFLR(*ANY) SAV DEV( ' /QSYS.LIB/TAPxx. DEVD' ) OBJ( ( ' / QIBM/ProdData' ) ( ' /QOpenSys/QIBM/ProdData‘ ) ) UPDHST(*YES) STRSBS SBSD (controlling subsystem) Where xx is the name of the tape drive.


SAVE option 23: All user data IBM i

ENDSBS SBS(*ALL) OPTION(*IMMED) CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK OR *NOTIFY) SAVSECDTA SAVCFG SAVLIB LIB(*ALLUSR) ACCPTH(*YES) SAVDLO DLO(*ALL) SAVFLR(*ANY) SAV DEV( ' /QSYS.LIB/TAPxx. DEVD' ) OBJ( ( ' / *' ) ( ' /QSYS.LIB' *OMIT) ( ' /QDLS' *OMIT) ) (1) ( ' /QIBM/ProdData' *OMIT ) ( ' /QOpenSys/QIBM/ProdData' *OMIT) ) UPDHST(*YES) STRSBS SBSD (controlling subsystem) Where xx is the name of the tape drive. © Copyright IBM Corporation 2012

How the system performs save processing IBM i

Start Preprocessing Build save list for library LIBA.

Post processing Copy the objects in library LIBA to tape.

Build save list for library LIBB. Copy the objects in library LIBB to tape. Build save list for library LIBC. Copy the objects in library LIBC to tape. Build save list for library LIBD. Copy the objects in library LIBD to tape.


Where to perform the save to? IBM i

Disk

Tape Physical or virtual =

Optical drive =

Disk

DEV(tape names)

DEV(OPTxx)

SAVLIB SAVFDTA(*YES) SAVSAVFDTA SNDNETF

Save file: DEV(*SAVF) SAVF(name)


Tape

SAVLIB: Save Library IBM i


SAVOBJ: Save Object IBM i


SAVCHGOBJ: Save Changed Objects IBM i


Backing up spooled file data IBM i

• Save/restore of spooled files – Support was added to the OS at V5R4. – There is a new SPLFDTA parameter on save/restore commands. – Preserves spooled file data, spooled file identity, and attributes. • • • • •

Spooled file name Spooled file number Creation date and time Fully qualified job name Job system name

– Attributes might not be preserved. • • • • •

System 36 identifier Output queue name/library (restored to different output queue/library) ASP (output queue on different ASP) New expiration date (restore occurs after expiration date) New save/restore attributes of spooled file © Copyright IBM Corporation 2012

File systems: Save commands IBM i

Save commands

File system Root

(/)

SAV

QSYS..LIB (Library)

SAVSYS, SAVCFG, SAVSECDTA, SAVLIB, SAVOBJ SAVCHGOBJ, SAV

QDLS (Document library services)

SAVDLO SAV

QOpenSys (Open systems)

SAV

QNetware (Novell NetWare)

SAV

User-defined file System (/dev QASPxx/)

SAV

(Other file systems)

SAV © Copyright IBM Corporation 2012

SAVSYSINF command IBM i

• Performs a partial save of data saved by save system (SAVSYS) command • Cumulative save since last SAVSYS • Restricted state note required • Saves: – Selected objects in library QSYS – System reply list entries – Certain system values – Service attributes – Network attributes – Environment variables – Certain PTFs


SAVSYSINF command considerations IBM i

• Base SAVSYS required – SAVSYSINF not a replacement for SAVSYS

• *ALLOBJ or *SAVSYS special authority required • Cannot be used for: – Restoring to another existing system – System upgrades or migrations

• Intended for customers who: – Cannot bring system to restricted state for SAVSYS – Cannot take downtime for SAVSYS

• PTF save files must remain on system until next SAVSYS – Do not run Delete Program Temporary Fix (DLTPTF) command unless • Right before SAVSYS • Right after SAVSYS – Installing PTFS default is not to restore save files • Change system default CPYPTF(*YES) or CHGSRVA command or • Use CPYPTF(*YES) in INSPTF command consistently

• System recovery – SAVSYS and SAVSYSINF need to be recovered – RSTSYSINF additional step per backup and recovery checklists – Increases time and complexity © Copyright IBM Corporation 2012

SAVSYSINF backup strategy IBM i

• After base SAVSYS, perform the following commands to save system changes: – SAVLIB LIB(*IBM) – SAV OBJ(('/QIBM/ProdData')('/QOpenSys/QIBM/ProdData')) UPDHST(*YES) – SAVSYSINF

• The following are commands used to save user data: – – – – –

SAVSECDTA SAVCFG SAVLIB LIB(*ALLUSR) SAVDLO DLO(*ALL) FLR(*ANY) SAV OBJ(('/*') (*/QSYS.LIB' *OMIT) ('/QDLS' *OMIT)) UPHST(*YES)

• Here is an example SAVSYSINF command to save file: – SAVSYSINF DEV(*SAVF) SAVE(QGPL/SAVF) CLEAR(*ALL) OUTPUT(*OUTFILE) OUTFILE(QGPL/OUPUT) © Copyright IBM Corporation 2012

Parameter: Save-while-active IBM i

• Can be used with the following commands: – SAV • Save the integrated file system (IFS)

– SAVLIB • Save one library or multiple libraries

– SAVOBJ • Save one object or multiple objects

– SAVCHGOBJ • Save changed object

– SAVDLO • Save document library object (folders)


Save-while-active parameters IBM i


Save-outage time IBM i

• The save-while-active function allows you to: – Reduce your save-outage time • End the applications • Restart when the checkpoint is done • No additional recovery procedure for restore

– Eliminate your save-outage time • • • •

Not waiting to end the applications Protect objects with journaling and commitment control More complex and longer recovery procedure for restore SAVACTWAIT parameter specifies three wait time elements: – Object locks – Commit record changes – Commit object changes

• Saving with partial transactions or without waiting for commitment boundaries: SAVACTWAIT(30 *NOCMTBDY 30) © Copyright IBM Corporation 2012

Checkpoint processing IBM i


SAVF: Saving using a save file IBM i

RSTOBJ

*FILE CUSTMAST *file Attr.PF

SFxx *file Attr.SAVF

SAVOBJ DEV(*SAVF) SAVF(SFxx)

CUSTMAST

SAVSAVFDTA SAVF(SFxx) DEV(TAP01)

CUSTMAST

Once you have saved to save media: CLRSAVF FILE(SAVE-FILE-NAME)


CUSTMAST

SAVF: Save File Commands IBM i


Miscellaneous SAV commands IBM i

• Save IFS objects (SAV) command • Save Document Library Object (SAVDLO) command • Save Storage (SAVSTG) command


Using Operational Assistant IBM i

• GO ASSIST – Select 11 (Customize your system, users, and devices). – Select 5 (Backup tasks).


IBM i Navigator: Backup policies IBM i


Automatic default backups IBM i

Daily

Weekly

Monthly

Back up all user libraries.

Back up all user libraries.

Back up folders selected on backup list.

Back up all folders.

Back up all folders. Back up security data. Back up configuration data.

Back up all user directories.



Back up changes to user libraries selected on backup list.


Backup policies: General IBM i


Backup policies: What IBM i


Backup policies: When IBM i


Backup policies: Where IBM i


IBM i Navigator summary IBM i

• Allows you to perform daily, weekly, or monthly backups • Provides the ability to display and change properties of the three IBM-supplied system backup sets • Not intended for complex save/restore strategies • Provides support for individual tape drives, tape library systems, and virtual tape drives


IBM i Navigator BRMS options IBM i


IBM Systems Director Navigator for i BRMS options IBM i


Save tips and hints IBM i

• Determining what has been saved • Determining what has not been saved • Determining when an object was last saved • Damaged objects • Paralleled tape saves


Topic 4: Restore operations


7.0

Relationship between save and restore commands IBM i

Save

Restore

SAVSECDTA

RSTUSRPRF RSTAUT

SAVCFG SAVSYS

RSTCFG Restore Licensed Internal Code (see chapter 10 of Backup and Recovery) Restore operating system (see chapter 11 of Backup and Recovery)

RSTUSRPRF RSTCFG RSTAUT SAVDLO

RSTDLO

SAV SAVSYSINF

RST RSTSYSINF © Copyright IBM Corporation 2012

Restore overview IBM i

Restore

Parts of the system menu Licensed Internal Code i5/OS objects in QSYS

Procedure for restoring Option on install Licensed Internal Code (LIC) screen IPL or install the system menu

User profiles

RSTUSRPRF

Configuration objects

RSTCFG

IBM-supplied directories

RST

23 22

21

23

i5/OS optional libraries QHLPSYS QUSRTOOL Licensed program libraries QRPG QCBL Qxxxxx

RSTLIB *IBM

IBM libraries with user data QGPL QUSRSYS QS36F #LIBRARY User libraries LIBA LIBB LIBC LIBxxx

RSTLIB *ALLUSR

RSTLIB *NONSYS

Filed documents and folders Distribution objects

RSTDLO

User objects in directories

RST

Saved changes in libraries, documents, and directories

RSTLIB, RSTOBJ, RSTDLO, RST

Journaled changes

APYJRNCHG

All Private authorities © Copyright IBM Corporation 2012

RSTAUT

Restore menu (1 of 3) IBM i


RESTORE option 21: System and user data IBM i

ENDSBS SBS(*ALL) OPTION(*IMMED) RSTUSRPRF USRPRF(*ALL) RSTCFG OBJ(*ALL) RSTLIB SAVLIB(*NONSYS) RSTDLO DLO(*ALL) SAVFLR(*ANY) RST DEV( ' /QSYS.LIB/TAPxx. DEVD' ) OBJ( ( ' / *' ) ( ' /QSYS.LIB' *OMIT) ( ' /QDLS' *OMIT) ) RSTAUT STRSBS SBSD (controlling subsystem) Where xx is the name of the tape drive.




RESTORE option 22: System data only IBM i

ENDSBS SBS(*ALL) OPTION(*IMMED) RSTUSRPRF USRPRF(*ALL) RSTCFG OBJ(*ALL) RSTLIB SAVLIB(*IBM) RST DEV( ' /QSYS.LIB/TAPxx. DEVD' ) OBJ( ( ' /QIBM/ProdData ' ) ( ' /QOpenSys/QIBM/ProdData ' )) STRSBS SBSD (controlling subsystem) Where xx is the name of the tape drive.


RESTORE option 23: All user data IBM i

ENDSBS SBS(*ALL) OPTION(*IMMED) RSTUSRPRF USRPRF(*ALL) RSTCFG OBJ(*ALL) RSTLIB SAVLIB(*ALLUSR) RSTDLO DLO(*ALL) SAVFLR(*ANY) RST DEV( ' /QSYS.LIB/TAPxx.DEVD ' ) OBJ( ( ' / * ' ) ( ' /QSYS.LIB' *OMIT) ( ' /QDLS ' *OMIT) ( ' /QIBM/ProdData ' *OMIT) ( ' /QOpenSys/QIBM/ProdData' *OMIT)) RSTAUT USRPRF(*ALL) STRSBS SBSD (controlling subsystem)

Where xx is the name of the tape drive.




What happens when you restore data? IBM i

• What happens depends on: – Whether the object already exists on the system – The ALWOBJDIF parameter setting – Whether the object was saved on another system


Sequence for restoring data IBM i

• Restore object sequence – Journals before journaled files – Journals before journaled receivers – Physical files before logical files


Putting your system in a restricted state IBM i

• Sign off all users • Enable notification • End all subsystems


Recovery from an unsuccessful restore IBM i

• Restore operation failures – Restore operation error Or – Restore operation interrupted


Special considerations IBM i

• Recovering LIC • Restoring the operating system • Starting the system after it ends abnormally • Reclaiming storage • Parallel restore operations


Exercise: Save/restore IBM i

At the end of the lab, you should be able to: • Use the SAVLIB command and explain what the precheck parameter is used to control • Perform the save of your team library using both the *Yes and the *No in the PRECHK parameter • Perform a save using a virtual tape drive


Topic 5: LPAR save/restore considerations


7.0

Logical partitions: Overview IBM i

• Logical partitioning is the ability to make a server run as if it were two or more independent servers. • Benefits: – Consolidating servers – Sharing resources – Maintaining independent servers – Creating a mixed production and test environment – Merging production and test environments – Running integrated clusters

• Tools: – HMC – Integrated Virtualization Manager (supported only on specific server models) – Virtual Partition Manager © Copyright IBM Corporation 2012

HMC: Backup IBM i


HMC: Restore IBM i


LPAR save considerations IBM i

• Each partition behaves functionally like a single system or individual system. • Each LPAR must be saved individually. • LPAR configuration data cannot be saved using save commands. – Since POWER5, LPAR configuration data is maintained at the HMC. – Reference: Recovering your system (SC41-5304), including procedures for LPAR systems. – (POWER4 systems are no longer covered in this course.)


Saving LPARs: Considerations IBM i

• Each LPAR behaves as an individual stand-alone system, including LIC and operating system (SAVSYS). • You can perform saves of different partitions on the same system at the same time. – Assuming each partition has the resources, such as an available tape drive. – You could set up and use a virtual tape drive.


First partition

Second partition

LPAR restoring: Considerations IBM i

• The saved data off of a partition can be restored to: – Same partition on the same system – Another partition on the same system – Another partition on another system – A non-partitioned system


Restore for LPARs IBM i

• Restore is done on a partition-by-partition basis. – There is no system-wide restore option for all LPARs.

• Restoring multiple partitions can be done in parallel. – This is assuming necessary devices (for example, tape drives) are available.

• Recovery for LPARs is a two-stage process: – Step 1: Recover the partition (at HMC, be sure to activate the correct profile). – Step 2: Restore the system and user data for each LPAR.


D: IPL of partition from HMC IBM i


Topic 6: Backup/recovery for Windows servers


7.0

Backup methods IBM i

• IBM i centric backups

• Windows centric backups

– Full system

– Directory/file level

– Complete Windows server

– Methods:

– Network storage space – File-level backup – File level through network storage spaces – Methods:

• Windows Backup Utility • Tivoli Storage Manager • Veritas Backup Exec V8.0 build 3311 and earlier • Computer Associates Arcserv 2000

• IBM i save/restore commands • BRMS


Save method comparison IBM i

Save method

Originated on

Relative speed

SAVF capability

System

IBM i

Fast

80-100 GB/hr

Server

IBM i

Fast

80-100 GB/hr

Network storage space

IBM i

Fast

80-100 GB/hr

Directory/file

IBM i

Medium

8-30 GB/hr

Directory/file

Windows

Medium

8-30 GB/hr (online backup)

• The performance results for your system will vary, depending on the configuration of your IBM i server and the load on the system. See: http://www- 1.ibm.com/servers/eserver/iseries/windowsintegration/savbackupperf.html


Backup considerations IBM i

• Objects to save • Available tape drives • Formatting tapes • Saving to SAVF • Required state of the network server description (NWSD)


Objects to save IBM i

• Configuration objects – NWSD – LIND

• Predefined network server storage spaces (C: and D:) • User data and applications – User-defined network server storage spaces (E: through Z:)

• Server message queue • IBM i-based Windows server code • PC-based Windows server code


Network storage spaces backup IBM i

• • • •

Windows disks C: to Z: NWSD must be varied off before the save Full System i backup or SAV command – ASP use alters the parameters on the commands – That is, SAV DEV('/QSYS.LIB/WINBACKUP.LIB/MYSAVF.FILE') OBJ('/QFPNWSSTG/1') © Copyright IBM Corporation 2012

Device sharing IBM i

Disk drives

CD-ROM drive

IXA

CD-ROM drive Tape drives

IXS © Copyright IBM Corporation 2012

Allocate a tape device to a Windows server IBM i

• From IBM i: – Vary off the device. – Command entry: • WRKCFGSTS *DEV *TAP

– IBM i Navigator: • Make Unavailable

• From Windows: – Lock the device.


Reallocate a tape device to the IBM i IBM i

• From Windows: – Unlock the device.

• From IBM i: – Vary on the device. – IBM i Navigator: • Make Available

– Command entry: • WRKCFGSTS *DEV *TAP © Copyright IBM Corporation 2012

Backup and restore IBM i

Object name

Object location

Object type

Object content

Save command

NWSD, LINK

QSYS

Communication objects

iSeries descriptions for Windows server

SAVCFG

D:

/QFPNWSSTG

Predefined network server storage spaces *

Windows server boot and system drive

SAV

E: to Z: User specified

/QFPNWSSTG

User storage spaces *

User data and applications

SAV

MSGQ User specified

User specified

Server message queue

Messages from Windows server

SAVOBJ

QNTAP

QSYS

Library

iSeries-based integration code

SAVLIB

NTAP plus subdirectories

/QIBM/ProdDa ta/NTAP/*

IFS directory

PC-based integration code

SAV

C:

*ASP use alters the parameters on the save commands. © Copyright IBM Corporation 2012

Displaying status of a Windows server IBM i

Or issue WRKCFGSTS *NWS.


Starting a Windows server (1 of 2) IBM i

• IBM i – Vary on the NWSD – System i Navigator Start option or – WRKCFGSTS *NWS, option 1

• Windows console – Cannot vary on the NWSD from here


Starting a Windows server (2 of 2) IBM i

Or issue WRKCFGSTS *NWS. © Copyright IBM Corporation 2012

Shutting down a Windows server IBM i

• System i: – Vary off NWSD. • Navigator Shut Down option or • Shut Down and Restart option or • WRKCFGSTS *NWS, option 2

– Must be restarted from System i side.

• Windows console: – Start > Shut Down > Restart option is fine for IXS or IXA – Start > Shut Down > Shut Down is not fine for IXA (breaks high speed link connection). It is fine for IXS. – Neither option varies off the NWSD. – Restart from console or System i.

• Always shut down Windows server before the system enters restricted state. © Copyright IBM Corporation 2012


1. True or False: Ideally, objects on your system should be saved frequently, while they are only restored infrequently.

2. Which of the following is not one of the supported basic modes of operation for a tape library? a. b. c. d.

Manual mode Virtual mode Automatic cartridge loader mode Library mode

3. The command used to manage the status of your tape devices is _____. a. WRKMLBSTS b. WRKTAPSTS c. WRKCFGSTS d. MNGTAPSTS

4. The command used to manage the status of your tape library devices is _____. a. WRKMLBSTS b. WRKTAPSTS c. WRKCFGSTS d. MNGTAPSTS © Copyright IBM Corporation 2012


1.

True or False: Ideally, objects on your system should be saved frequently, while they are only restored infrequently. The answer is true.

2.

Which of the following is not one of the supported basic modes of operation for a tape library? a. Manual mode b. Virtual mode c. Automatic cartridge loader mode d. Library mode The answer is virtual mode.

3.

The command used to manage the status of your tape devices is WRKCFGSTS. a. WRKMLBSTS b. WRKTAPSTS c. WRKCFGSTS d. MNGTAPSTS The answer is WRKCFGSTS.

4.

The command used to manage the status of your tape library devices is WRKMLBSTS. a. WRKMLBSTS b. WRKTAPSTS c. WRKCFGSTS d. MNGTAPSTS The answer is WRKMLBSTS. © Copyright IBM Corporation 2012


5. True or False: The SAVCHGOBJ command does not require that any other command has been previously used if this command is used in your save strategy. 6. True or False: The SAVSYSINF command is the new command that is a replacement for the SAVSYS command. 7. The command parameter that allows you to save data while users are still working with that data is _____. a. ACTDTA b. SYSDTA c. ACTSAV d. SAVACT © Copyright IBM Corporation 2012


5. True or False: The SAVCHGOBJ command does not require that any other command has been previously used if this command is used in your save strategy. The answer is false. 6. True or False: The SAVSYSINF command is the new command that is a replacement for the SAVSYS command. The answer is false. 7. The command parameter that allows you to save data while users are still working with that data is SAVACT. a. b. c. d.

ACTDTA SYSDTA ACTSAV SAVACT

The answer is SAVACT. © Copyright IBM Corporation 2012


8. True or False: The Restore menu option 21 will perform a direct opposite of the Save menu option 21. Restore option 21 will restore the entire system. 9. True or False: It is possible to save all of the user data across all of the LPARs on a system using one single command. 10. True or False: You can use either IBM i or Windows server utilities or a combination of both to manage backups of integrated xSeries servers.



8. True or False: The Restore menu option 21 will perform a direct opposite of the Save menu option 21. Restore option 21 will restore the entire system. The answer is false. 9. True or False: It is possible to save all of the user data across all of the LPARs on a system using one single command. The answer is false. 10. True or False: You can use either IBM i or Windows server utilities or a combination of both to manage backups of integrated xSeries servers. The answer is true.


Unit summary IBM i

Having completed this unit, you should be able to: • List the different types of failures that can occur on the system • List the different media types that can be used for backup of your data • Perform the steps required to set up and use a virtual tape drive • Explain which commands are used to save which types of data • Explain the difference between the SAVSYS and SAVSYSINF command • Identify the procedures used to save and restore different types of system information


Journal management


7.0


After completing this unit, you should be able to: • 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 • List the advantages and considerations of journaling access paths • Describe remote journaling and how it can be used to replicate data or to implement a hot backup environment on a remote system


Topic 1: Journal management concepts


7.0

Think about your most important data file IBM i

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? © Copyright IBM Corporation 2012

Single-level storage IBM i

ON

OFF

Volatile storage Main memory

N

Magnetic storage disk drives

*PGM Delete Update Write

S

1

Or solid state disk drives

2 *JRNRCV

*JRN Buffer

Disk I/O

3

4

File A


File A

Data file scatter loading

File A

Journal objects IBM i

Journaling data flow PGMX Object A change

PGMY Object B change

Object B change

Object C change

Journal receiver Object A change Object B change Object B change Obj. A

Obj. B


Obj. C

Objects that can be journaled IBM i

• 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


Display Journal Entries IBM i


Display Journal Entry IBM i


F10 = Display only entry details IBM i


Topic 2: Steps to implement journaling


7.0

Implementing journaling IBM i

•

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! © Copyright IBM Corporation 2012

)

Step 1: CRTJRNRCV command IBM i


Step 2: CRTJRN command IBM i


Step 3a: Access path command (STRJRNAP) IBM i


Step 3b: Library command (STRJRNLIB) IBM i


Step 3c: Object command (STRJRNOBJ) IBM i


Step 3d: Physical file command (STRJRNPF) IBM i


Step 3e: IFS object command (STRJRN) IBM i


IBM System i Navigator: Start journaling IBM i


Save objects IBM i

• 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.


Topic 3: Journal receiver considerations


7.0

Managing the receiver chain IBM i

CHGJRN JRN(name)

JRNRCV(*GEN) MNGRCV(*USER) SEQOPT(*CONT or*RESET)

*PGM

RCV0001 Old receiver RCV0002 Current receiver *File


System change journal management IBM i

• 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 © Copyright IBM Corporation 2012

Journal receiver chain IBM i

J

PR

RCV0006

RCV0007 J

NR

RCV0008

J

PR

RCV0007

RCV0008 J

NR

RCV0009


WRKJRNA command IBM i


F15 = Work with Receiver Directory IBM i


Topic 4: Determining the recovery points


7.0

Determine the best recovery points IBM i

DSPJRN *JRN

FILE(names) RCVRNG Start(*CURRENT/name) End(name/*CURRENT)

*CURRENT RCV00010 RCV0009 RCV0008

FROMENT(*FIRST/seq#) TOENT(*LAST/seq#)


Receiver saved to tape

Display Journal (1 of 5) IBM i










Journal codes IBM i

Selected entry classifications Journal code

Type

Description

J

PR Previous receiver NR Next receiver RS Receiver saved __________________________________________ F

R

U

JM MS SS

Journaling started Member saved Save-while-active group saved

OP CL PT UB UP DL

File opened File closed Record added Image before update Image after update Record deleted

XX

User entry


Recovery point example (1 of 2) IBM i


Recovery point example (2 of 2) IBM i


User-generated entries IBM i


Command to send a user entry IBM i


Topic 5: Performing a recovery


7.0

Work with Journals IBM i


Forward recovery IBM i

• Issue WRKJRN. • Select option 2 (Forward recovery). • Select option 2 (Apply journaled changes) (all PFs to recover). – System deletes dependent LFs. – System deletes PFs to be recovered. – Prompts restore of PFs and allocates *EXCL until recovery complete. – Prompts for restore of LFs. – APYJRNCHG prompted with FROMENT(*LASTSAVE) and TOENT(*LASTRST). – Prompts for receivers not online.


Select option 2 to start forward recovery IBM i


Authority prompt IBM i


Forward recovery object type IBM i


Work with Forward Recovery for Files IBM i


Backout recovery IBM i

• Issue WRKJRN. • Select option 3 (Backout recovery). • Select option 2 (Remove journaled changes). – RMVJRNCHG prompted – Prompts for restore of receivers not online


Select option 3 to start backout recovery IBM i


Authority prompt IBM i


Backward recovery object type IBM i


Work with Backout Recovery for Files IBM i


APYJRNCHG command (forward recovery) IBM i

JRN:

name

FILE:

*LIBL

*CURLIB

name/*ALL

RCVRNG:

Start:

Name

*LASTSAVE *CURRENT

End:

Name

*CURRENT

FROMENT:

*LASTSAVE number

*FIRST

TOENT:

*LASTRST number

*LAST

TOTIME:

Date

Time

TOJOBO:

job-name

TOJOBC:

job-name

CMTBDY:

*NO

OBJERROPT:

*YES

*CONTINUE *END © Copyright IBM Corporation 2012

name

RMVJRNCHG command (backout recovery) IBM i

JRN:

name

FILE:

*LIBL

RCVRNG:

Start:

name *CURLIB/name *ALL *CURRENT

End:

name name

FROMENT:

*LAST number *LASTSAVE

TOENT:

*FIRST number

TOJOBO:

job-name

CMTBDY:

*NO

OBJERROPT:

*YES

*CONTINUE

*END


Operations that cause incomplete recovery IBM i

Code

Type

Operation

APYJRNCHG

RMVJRNCHG

F

AY

Journal changes applied

Ends

Ends

F

CR

Member-cleared

Cleared

Ends

F

EJ

End journaling

Ends

Ignores

F

IU

File not synchronized

Ends

Ends

F

JM

Start journaling member

Ignores

Ends

F

MD

Member deleted

Ignores

Ends

F

MF

SAVxx

Ends

Ends

F

MO

Member changed

Ends

Ends

F

MR

Member restored

Ends

Ends

F

RC

Journaled changes removed

Ends

Ends

F

RG

Member reorganized

Ignore

Ends

F

SA

Start APYJRNCHG

Ends

Ends

F

SR

Start RMVJRNCHG

Ends

Ends

STG(*FREE)

Examine count/RRN and flag of F/AY or F/RC. © Copyright IBM Corporation 2012

Illogical conditions that stop APYJRNCHG or RMVJRNCHG IBM i

• Attempts to do the following: – To add a record to an existing relative record number – To add a record beyond the next record position after the end of the file – To add a record that has a duplicate key – To delete a deleted record – To update a nonexistent record

• Examine count/RRN and flag of F/AY or F/RC


Topic 6: Additional journaling topics


7.0

SAVCHGOBJ: Journaling considerations (1 of 3) IBM i

SAVCHGOBJ....OBJJRN(*NO) Weekly SAVIB LIB(LIBA LIBB)

Daily CHGJRN JRN(name) JRNRCV(*GEN) SAVCHGOBJ OBJ(*ALL) LIB(LIBA LIBB)

OBJJRN(*NO)

LIBA FILEA FILEB FILEC

Changes occur to FILEA on Tuesday.

JRNA

RCVR0001 FILEA RCVR0001

FILEA LIBB

FILEA

RCVR0001

RCVR0002 RCVR0003

RCVR0002

RCVR0001 RCVR0002 RCVR0003

Monday

Tuesday

Wednesday


Thursday


SAVCHGOBJ....OBJJRN(*YES) Weekly SAVIB LIB(LIBA LIBB)

Daily CHGJRN JRN(name) JRNRCV(*GEN) SAVCHGOBJ OBJ(*ALL) LIB(LIBA LIBB)

OBJJRN(*YES)

LIBA FILEA FILEB FILEC

Changes occur to FILEB on Wednesday.

Changes occur to FILEA on Tuesday.

JRNA

FILEA FILEB

LIBB RCVR0001 RCVR0002 RCVR0003

Monday

FILEA

FILEA FILEB

RCVR0001 RCVR0001

RCVR0001

Tuesday

RCVR0002

Wednesday


RCVR0002 RCVR0003

Thursday


• Forward recovery after data loss on Friday: 1. Load SAVLIB tape 2. RSTLIB 3. Load SAVCHGOBJ tape for Thursday 4. RSTOBJ OBJ(*ALL) 5. APYJRNCHG 6. Rekey data since Thursday's SAVCHGOBJ tape


Which files should be journaled? IBM i

• How much does the file change? • How difficult would it be to reconstruct file changes? • How critical is the file? • How does the file relate to other files? – All files in an application – All files in a referential constraint network – All files affected by trigger programs

• Not source files


How should files be assigned to journals? IBM i

• One journal: Simple management and recovery • Application's files in same journal simplifies recovery • Backup, security, or auditing requirements


Should journal receivers be in a user ASP? IBM i

• System ASP: Operating system and user objects • Library user ASP (library is first object in ASP) – *JRN must be in a library ASP with a journaled file – *JRNRCV can be in different ASP

• Non-library user ASP (not recommended) – First object in ASP is a journal, journal receiver, or save file ASP1 System ASP

*LIB CUSTLIB *FILE *FILE

ASP2 User ASP Library user ASP

*LIB LIBJRNB *JRN JRNB

ASP3 User ASP Non-library user ASP

*JRNRCV JRCVB *SAVF ORDSAV

*LIB LIBJRNA *JRNRCV JRCVA *JRN JRNA *LIB SAVFLIB © Copyright IBM Corporation 2012

Restore considerations IBM i

• Recommended restore sequence (automatic if all in the same library): 1. Journals 2. Physical files 3. Logical files 4. Journal receivers

• RSTLIB LIB(name): All objects within library restored in correct sequence • RSTLIB LIB(*NONSYS

*ALLUSR)

– Libraries restored in alphabetic sequence


Other journal considerations IBM i

• Before images: – Backout recovery is possible. – Deleted records can be recovered. – CMPJRNIMG is more meaningful.

• Journaled files should have FRCRATIO(*NONE) • *JRNRCV spread across 10 fastest disk arms in ASP • Size of journal receivers: – Access path journaled also? STRJRNPF IMAGES(*AFTER *BOTH) OMTJRNE(*NONE *OPNCLO) CRTJRN RCVSIZOPT(*RMVINTENT *MINFIXLEN)


File journaling summary IBM i

Recovers damaged data file member

11

12

1

10

2 3

9 8

4 7

6

5

Decreases time required to do backup

Provides audit trail 15

Provides activity reporting

Aids debugging © Copyright IBM Corporation 2012

Exercise: Journal management IBM i

At the end of the lab, you should be able to: • Create • Add • Secure


Topic 7: Remote journaling


7.0

Remote journal IBM i

• Journal entries transported to a duplicate receiver on a backup server running IBM i • Used to replicate data remotely or provide a hot backup site • IBM i operating system base support • Transport done below machine interface for better performance


Remote journal: Hot backup IBM i

Primary (local) system

JRN and JRNRCVs

JRN and JRNRCVs


DB operation

Call to RCVJRNE Receive exit program . and . . apply jobs Processing........ R C V J Communications R transport N E

Applications

DB files

Backup (remote) system

DB files

Remote journal benefits IBM i

• Less disk writes on the source system than prior support • Less CPU overhead than prior support on the source system • DB images can be sent to target machine in real time • High availability (24x7) • Shift saving JRN receivers to the target machine • No lost transactions • Faster switch-back © Copyright IBM Corporation 2012

How to add a remote journal (1 of 6) IBM i












Remote journal APIs IBM i

• ADDRMTJRN: Add Remote Journal (QjoAddRemoteJournal API) – Establishes and associates a remote journal on a target system with a journal on a source system

• CHGRMTJRN: Change Journal State (QjoChangeJournalState API) – Changes the journal state for local and remote journals

• RMVRMTJRN: Remove Remote Journal (QjoRemoveRemoteJournal API) – Disassociates a remote journal on a target system from a journal on a source system

• Retrieve Journal Information (QjoRetrieveJournalInformation API) – Retrieves the attributes of a journal including the receiver directory, journaled files, and remote journals

• Retrieve Journal Receiver Information (QjoRtvJrnReceiverInformation API) – Retrieves the attributes of a journal receiver


New in V7R1 IBM i


Topic 8: Access path protection


7.0

Introduction to access path journaling IBM i

How can I significantly reduce the time needed to IPL following an abnormal system end? That is easy! Implement

access path journaling or use system managed access path protection.


Access path protection IBM i

• What is the benefit? – Reduces IPL time after abnormal end

• How? – By journaling access paths

• What does the user have to do? – Very little

• What does it cost? – Some CPU performance and some DASD space


Access path's contribution to IPL time IBM i

• Abnormal end of system can leave an access path unusable. • Access path is made usable no later than when file is opened. • Protected access paths are: – Recovered quickly through journal during or after IPL

• Unprotected access paths: – DB files have a RECOVER attribute • RECOVER(*NO): Rebuild when opened • RECOVER(*AFTIPL): IPL, and then rebuild • RECOVER(*IPL) – Rebuild during IPL – Valid only if file has MAINT *IMMED or *DLY, not *REBLD

– During IPL, RECOVER attribute changeable on Override Access Path Recovery display


Edit Rebuild of Access Paths: EDTRBDAP command IBM i


Explicit access path journaling (protection) IBM i

• You decide which access paths to protect. • Underlying physical files must be journaled. • STRJRNAP for file with the access path. • Access path and file use same journal. • Encoded vector access paths are not eligible.


System-managed access-path protection IBM i

• Reduces IPL time after abnormal end • User sets target recovery time • Automatic: – Determines which access paths to journal – Adjusts for system hardware and file changes – Files not journaled: Uses internal journal and receiver – Files already journaled: Uses same journal and receiver

• Will not duplicate protection if access path already journaled


SMAPP performance and auxiliary storage use IBM i

• Low target recovery time has greater impact on performance • Asynchronous writes, which do not directly affect response time for a transaction • Specify target recovery times either for entire system or ASPs, but not both • Storage space for journal receivers: – System manages internal receiver space. – Internal receivers are more condensed (less space). – Uses existing receiver if file is already being journaled. RCVSIZOPT(*RMVINTENT) saves space at a small performance cost – It can be turned off.

• Increased disk activity • Usually small impact on CPU © Copyright IBM Corporation 2012

Edit Recovery for Access Paths (EDTRCYAP) IBM i


New panel in V7R1 IBM i

• Using the F16=Display details function from the Display Recovery for Access Paths (DSPRCYAP) screen or the Edit Recovery for Access Paths (EDTRCYAP) screen (see figure) shows the internal threshold used by SMAPP.

• This panel was added in V7R1. All access paths with estimated rebuild times greater than the internal threshold are protected by SMAPP. © Copyright IBM Corporation 2012

SMAPP contribution to system performance (1 of 2) IBM i

• SMAPP has some effect on the overall system performance. • The lower the target recovery time you specify for access paths, the greater this effect might be. • Typically, the effect is not very noticeable, unless the processor is nearing its capacity.


SMAPP contribution to system performance (2 of 2) IBM i

• Another situation that might cause an increase in processor consumption is when local journals are placed in standby state, and large access paths, built over files journaled to the local journal, are modified.


SMAPP summary IBM i

• Automatic • Not much DASD consumed • Not much performance overhead • Does not miss any files • Needs no special setup; no ASPs required • No special hardware • Covers broad spectrum of outage causes • Substantial IPL/recovery time reductions



1. Which of the following is not a valid object that can be journaled? a. b. c. d.

Database files Data area Data queue Root folders

2. A ______ is a program that intercepts activity to an object that is being journaled. a. b. c. d.

Journal Journal receiver Trigger Referential constraint

3. What is the first object that needs to be created when you start journaling? a. b. c. d.

Journal audit trail Journal receiver Journal Journal access path © Copyright IBM Corporation 2012


1. Which of the following is not a valid object that can be journaled? a. b. c. d.

Database files Data area Data queue Root folders

The answer is root folders. 2. A journal is a program that intercepts activity to an object that is being journaled. a. b. c. d.

Journal Journal receiver Trigger Referential constraint

The answer is journal. 3. What is the first object that needs to be created when you start journaling? a. b. c. d.

Journal audit trail Journal receiver Journal Journal access path

The answer is journal receiver. © Copyright IBM Corporation 2012


4. Which object contains the images and details of the objects that are being journaled? a. b. c. d.


5. What is the command used to create the journal? a. b. c. d.

CRTJRN CRTJRNRCV STRJRNAP STRJRNPF

6. True or False: The management of journal receivers is something that must be done by the database administrator. © Copyright IBM Corporation 2012


4.

Which object contains the images and details of the objects that are being journaled? a. b. c. d.


The answer is journal receiver. 5.

What is the command used to create the journal? a. b. c. d.

CRTJRN CRTJRNRCV STRJRNAP 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. © Copyright IBM Corporation 2012


7.

The _____ 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.

10. True or False: User-generated entries get placed into a journal receiver when the user selects an option to generate a system message. © Copyright IBM Corporation 2012


7.

The WRKJRNA command is used to see the attributes associated with your journal. a. b. c. d.

WRKJRN CRTJRN DSPJRNA WRKJRNA

The answer is WRKJRNA. 8.

What command is used to review the details of objects being journaled? a. b. c. d.

WRKJRN DSPJRN WRKJRNA 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.

10. True or False: User-generated entries get placed into a journal receiver when the user selects an option to generate a system message. The answer is false. © Copyright IBM Corporation 2012


11. True or False: When a bad batch of transactions is performed against an object being journaled, the only way to bring that object back to a good point is to restore that object off of your backup media and rekey a good batch of records. 12. True or False: When performing a forward recovery, the system assists you with the recovery of journaled objects by prompting you with the missing object name. 13. True or False: Journaling and saving changed objects are two recovery methods that cannot be used together or at the same time with the same objects. 14. Which of the following is the command used to save those objects that have changed since the last time that object was changed. a. b. c. d.

SAVLIBCHG SAVOBJCHG SAVCHGOBJ SAVCHGLIB © Copyright IBM Corporation 2012


11. True or False: When a bad batch of transactions is performed against an object being journaled, the only way to bring that object back to a good point is to restore that object off of your backup media and rekey a good batch of records. The answer is false. 12. True or False: When performing a forward recovery, the system assists you with the recovery of journaled objects by prompting you with the missing object name. The answer is true. 13. True or False: Journaling and saving changed objects are two recovery methods that cannot be used together or at the same time with the same objects. The answer is false. 14. Which of the following is the command used to save those objects that have changed since the last time that object was changed. a. b. c. d.

SAVLIBCHG SAVOBJCHG SAVCHGOBJ SAVCHGLIB

The answer is SAVCHGOBJ. © Copyright IBM Corporation 2012


15. True or False: Objects that have a high change volume are prime candidates that should be journaled. 16. True or False: For the best performance on your system, it is better to have just one journal for all of the objects being journaled on the system. 17. True or False: Journaled files must be in the same library ASP as the journaled file. 18. True or False: The following are all valid transport mechanisms for remote journaling: OptiConnect, TCP/IP, SNA, and ATM. © Copyright IBM Corporation 2012


15. True or False: Objects that have a high change volume are prime candidates that should be journaled. The answer is true. 16. True or False: For the best performance on your system, it is better to have just one journal for all of the objects being journaled on the system. The answer is true. 17. True or False: Journaled files must be in the same library ASP as the journaled file. The answer is false. 18. True or False: The following are all valid transport mechanisms for remote journaling: OptiConnect, TCP/IP, SNA, and ATM. The answer is true. © Copyright IBM Corporation 2012


19. True or False: Remote journaling cannot be set up through IBM System i Navigator. 20. True or False: Access path protection will cut down on the amount of time it takes a system to IPL after an abnormal system end. 21. True or False: Journaling can also be used to protect access paths. 22. True or False: At IPL time, the system will show you a screen that lists all of those objects whose access paths are being protected (journaled) and have already been recovered (basically, a screen to show you what has already be recovered).



19. True or False: Remote journaling cannot be set up through IBM System i Navigator. The answer is false. 20. True or False: Access path protection will cut down on the amount of time it takes a system to IPL after an abnormal system end. The answer is true. 21. True or False: Journaling can also be used to protect access paths. The answer is true. 22. True or False: At IPL time, the system will show you a screen that lists all of those objects whose access paths are being protected (journaled) and have already been recovered (basically, a screen to show you what has already be recovered). The answer is false. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • 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 • List the advantages and considerations of journaling access paths • Describe remote journaling and how it can be used to replicate data or to implement a hot backup environment on a remote system


Commitment control overview


7.0


After completing this unit, you should be able to: • Describe the functions and considerations of commitment control • Describe how to implement commitment control


What is commitment control? IBM i

• Commitment control is a function that ensures integrity. – It allows you to define and process a group of changes to resources, such as database files or tables, as a transaction. – It ensures that either the entire group of individual changes occur on all systems that participate or that none of the changes occur.


Why commitment control? IBM i

• Suppose the following: – An application's database files are being journaled. – Multiple users are entering transactions involving multiple files. – The system ends abnormally.

• Performing a recovery through APYJRNCHG or RMVJRNCHG might present the situation where there might not be a recovery point in which the application files reflect only whole transactions. • The solution is commitment control.


Complex transactions with multiple users IBM i

Display journal entries Sequence 20 21 22 23 24 25 26 27 28 29 30

?

Code R R R R R R R R R F F

Type UP UP UP UP UP UP UP UP UP CL CL

Object ITEM ITEM DETAIL DETAIL ITEM ITEM ITEM DETAIL DETAIL ITEM DETAIL

Library ADMCTL ADMCTL ADMCTL ADMCTL ADMCTL ADMCTL ADMCTL ADMCTL ADMCTL ADMCTL ADMCTL

Job W1 W333 W333 W1 W1 W22 W333 W22 W333 W22 W22

Time 10:21:15 10:26:17 10:27:19 10:27:23 10:27:40 10:28:35 10:28:45 10:29:12 10:30:24 10:32:34 10:32:39

What is the recovery point? 28: Leaves 24 unfinished 23: Omits complete transactions for W22 and W333 © Copyright IBM Corporation 2012

Functions of commitment control IBM i

• Allows a transaction to be defined • Ensures that incomplete transactions are rolled back if a job or the system ends abnormally • Permits rollback by individual user • Provides information for the restart of an application in the event of a job or system failure


Commitment control: Overview IBM i

Sign On Journal Entries

CALL

Commit cycle

Commitment definition

JOB

C BC . . . . . . . . . . . . . STRCMTCTL

F OP . . . . . . . . . . . . . . . . .OPEN FILES C SC . . . . . . . . . . . . . . . . .READ ITEM READ DETAIL R UB Record Before . . . . . . . . . .UPDATE ITEM R UP Record After R UB Record Before . . . . . . . . . .UPDATE DETAIL R UP Record After C CM Commit Identification . . . . . .COMMIT Commit Identification F CL . . . . . . . . . . . . . . . . .CLOSE FILES C EC . . . . . . . . . . . . . ENDCMTCTL SIGNOFF


Rollback event IBM i

• Uncommitted changes exist and: – Normal or abnormal end of job or system – ENDCMTCTL run • Batch job • Interactive job and RB is the response to message: CPA8350 “ENDCMTCTL requested with changes pending (RB

– HLL rollback operation


C

CM)”

Previous example with commitment control IBM i

Complete

Sequence 20 21 22 23 24 25 26 27 28 29 30 31

Code C R R C R R R R C C R R

Type SC UB UP SC UB UP UB UP CM SC UB UP

Object

Library

ITEM Before ITEM After

ADMCTL ADMCTL

ITEM Before ITEM After DETAIL Before DETAIL After

ADMCTL ADMCTL ADMCTL ADMCTL

ITEM Before ITEM After

ADMCTL ADMCTL

Job W1 W1 W1 W333 W333 W333 W333 W333 W333 W22 W22 W22

Time 10:21:15 10:21:15 10:21:55 10:26:17 10:26:17 10:27:19 10:27:23 10:27:40 10:28:35 10:28:45 10:29:12 10:30:24

W22 W22 W22 W1 W1 W1

12:20:00 12:21:15 12:21:18 12:21:30 12:21:40 12:21:45 12:21:55

Rollback event 32 33 34 35 36 37 38

J R R C R R C

IA UR BR RB UR BR RB

ITEM After ITEM Before

ADMCTL ADMCTL

ITEM After ITEM Before

ADMCTL ADMCTL


Commitment control requirements IBM i

• In order to implement commitment control the following conditions must be met: – All database files under commitment control must be journaled. – *BOTH images (automatic for files opened under commitment control). – Job must issue the STRCMTCTL and the ENDCMTCTL commands. – Programs must open files for commitment control. – Program must issue COMMIT operation.


Start Commitment Control (STRCMTCTL) IBM i


Record lock-level parameter IBM i

• STRCMTCTL

LCKLVL (

)

– *CHG: Record adds, updates, and deletes are protected from changes by other jobs until commit or rollback. – *CS: Changed and retrieved records are protected from changes by other jobs. Retrieved records that are not changed are protected only until they are released or a different record from the same file is retrieved. – *ALL: Changed and retrieved records are protected until commit or rollback.


Notify object parameter IBM i

• STRCMTCTL

NFYOBJ(object

object-type)

– Programmer can provide information for a restart after an abnormal end. – Specify either *FILE, *DTAARA, or *MSGQ to identify the last successful transaction (commit) if commit definition ends abnormally. – Commit identification can identify last successful transaction. • Character data specified on HLL (CL, RPG, PL/1, or C) commit operation • Entry specific data of commit (C/CM) journal entry

– This is an optional parameter.


When is the notify object updated? IBM i

• At least one successful commit and any of the following conditions: – Abnormal job end or an abnormal system end • Rollback occurs if there are uncommitted changes.

– Normal EOJ and uncommitted changes exist • Rollback also occurs in this case.

– ENDCMTCTL with uncommitted changes • Batch job, the changes are rolled back. • Interactive job gets CPA8350 ENDCMTCTL requested with changes pending (RB C CM), and response RB or CM is taken. For CM response, the commit identifier is entered on the prompt display.


Commitment control implementation IBM i

• Identify the application that will use commitment control. • Journal all of the physical files used by this application. • Modify the application programs. – Files used by the application must now be opened for commit. – The application must be updated to define logical transaction boundaries. – Use rollback if desired.

• Modify CL programs to include STRCMTCTL and ENDCMTCTL.


Two-phase commit: Overview IBM i

1. Prepare wave 2. Vote 3. Committed wave or rollback


Commitment control: Considerations IBM i

• After failure, applications are at transaction boundaries. • Records are locked longer. – If possible, keep transactions small.

• Control language programs must be modified to include STRCMTCTL and ENDCMTCTL. • Application programs must be modified. – Open files for commitment control. – Add commit operation at end of transactions. – You can use notify object to automate restart.

• More journal entries will be generated. © Copyright IBM Corporation 2012

Enhancements to database savepoints IBM i

Transaction Begin trans

A

B

Rollback to Savepoint B

COMMIT: End trans

Timeline

Flight reservation

Hotel reservation

Savepoint A

Automobile reservation

Savepoint B


IASP considerations for commitment control IBM i

• You should be aware of the following considerations for commitment definitions when you use independent disk pools: – QRECOVERY library – Set ASP group – Default journal – IPL and vary off – Remote database


XA transaction support for commitment control IBM i

• DB2 UDB for IBM i can participate in X/Open global transactions. • There are five components to the DTP model. – Application program (AP) – Transaction manager (TM) – Resource manager (RM) – Communications resource manager (CRM) – Communication protocol

• IBM i Navigator supports the management of XA transactions as global transactions.


IBM i Navigator: Support for commitment control (1 of 6) IBM i





The General properties information



The Details properties information



The Commitment Options properties information



Resource status for transaction

Jobs for transaction

The Commitment Options properties information © Copyright IBM Corporation 2012

Exercise: Commitment control IBM i

Commitment control: Lab exercise © Copyright IBM Corporation 2012

Checkpoint IBM i

1. True or False: Programming changes must be made to an application in order to implement commitment control. 2. True or False: Commitment control requires that journaling be implemented for the objects that are used by this application. 3. True or False: Commitment control allows you to recover only those transactions that are considered a whole or complete transaction.



1. True or False: Programming changes must be made to an application in order to implement commitment control. The answer is true. 2. True or False: Commitment control requires that journaling be implemented for the objects that are used by this application. The answer is true. 3. True or False: Commitment control allows you to recover only those transactions that are considered a whole or complete transaction. The answer is false. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • Describe the functions and considerations of commitment control • Describe how to implement commitment control


Backup and recovery planning


7.0


After completing this unit, you should be able to: • Compare the availability options that are available and their impact on the recovery process • Describe simple, medium, and complex save strategies • Describe a disaster recovery plan


Topic 1: The environment


7.0

Balance costs of backup and recovery IBM i

Cost of implementing availability features and backing up

Cost of failure multiplied by probability of failure


Can your business still function? IBM i

IBM i


Backup and recovery plan evaluation IBM i

Point 1 Known point (last save)

Recovery timeline: Activity occurs on system

Point 2 Failure occurs Hardware repair or IPL Point 3 Hardware available Information is restored from backup Point 4 System recovered to known point 1 Point 5 System recovered to failure point 2

Transactions from point 1 to point 2 are recovered

Business activity from failure point 2 to recovery point 5 is recovered

Point 6 System is current

1. Can your plan complete each step? 2. How long will it take to complete each step? © Copyright IBM Corporation 2012

What to save and how often? IBM i

• Frequent changes = save frequently (daily): – Security information – Configuration objects in QSYS – QGPL, QUSRSYS (IBM supplied libraries with user data) – User libraries – Folders and documents – Distributions – Directories

• Infrequent changes = Save infrequently (weekly): – System: LIC, QSYS, QHLPSYS, QUSRTOOL – Licensed program libraries (RPG, COBOL, and so on), folders, directories


Save window/save strategy IBM i

• Save window – System and data at known point – Not changing for period of time Save window

Save strategy

8 - 12 hours with no system activity

Simple

4 - 6 hours with no system activity

Medium

0 – minimal down time

Complex


Simple save strategy IBM i

• Save everything nightly. – Issue GO SAVE; then select option 21 (Entire system).

Or • Save everything once per week and save all user data nightly. – Issue GO SAVE; then select option 23 (All user data).


Medium save strategy IBM i

Weekly: Daily:

Save everything weekly. Save all user data mid-week.

Daily:

Or Save journal receivers.

Daily:

Daily:

Or Save changed objects (SAVCHGOBJ, SAVDLO, SAV). Or Save groups of libraries, folders, and directories (simplified with BACKUP menu).


Complex save strategy IBM i

• Complex save strategy: – This is similar to a medium save strategy. – Daily saves might be at specific times. – Save-while-active might be necessary. • Available on SAVLIB, SAVOBJ, SAVCHGOBJ, SAVDLO, SAV


Availability options IBM i

Attribute

Physical file journaling

Mirrored protection


Data loss after single disk failure

Minimal loss to file data if good backups are available

None of the data is lost

None of the data is lost

Recovery time after single disk failure

Potentially many hours

None to a few hours

None to a few hours

Performance impact

Minimal to significant

Minimal

Minimal

Minimal

Careful planning

Careful planning

Significant

Minimal

Minimal

Setup complexity and time

Minimal

Minimal

Minimal

Operational and management complexity

Average

Minimal

Minimal

Possibly more disk and separate ASPs

Double the disk; possibly more controllers and IOPs

One or two disk units per parity set

Planning complexity: - Hardware - Software

Additional hardware


Availability options by failure type: Recovery time IBM i

Has this relative impact on the recovery time for these failure types:

This save or availability option: DASD

System

Power loss

Program failure

Save operations

+

+

+

+

File journaling

++

++

++

+

Access path protection

++

++

++

Uninterruptible power supply

Site loss +

+++

User ASPs

++


+++

Mirrored protection

+++

Dual systems

+++

+


++

Availability options by failure type: Frequency IBM i

Has this relative impact on the frequency of failures that cause a recovery for these failure types: This save or availability option: DASD

System

Power loss

Program failure

Site loss

Save operations File journaling Access path protection Uninterruptible power supply

+

User ASPs Device parity protection

+

Mirrored protection

++

Dual systems

+

+


+

Topic 2: Creating a disaster recovery plan


7.0

Disaster recovery plan: Major goals IBM i

• Minimize interruptions to normal operations. • Limit extent of disruption and damage. • Minimize economic impact of the interruption. • Establish alternative means of operation in advance. • Train staff with emergency procedures. • Provide smooth and rapid restoration of service.


Disaster recovery plan IBM i

• Personnel – Data processing – Organizational chart – Positions, address, telephone number, email address

• Application profile: How critical, when it runs, manufacturer • Inventory profile: Manufacturer, description, model, serial number, owner, cost • Information services backup procedures – IBM i – Personal computers

• Disaster recovery procedures – – – – –

• • • • •

Emergency response procedures to protect lives and limit damage Backup operational procedures to conduct essential tasks Recovery and restoration of data processing system Disaster action checklist (before beginning recovery) Recovery start up procedures (notify people and outside companies involved)

Recovery plan at mobile site Recovery plan at hot site Restoring entire system Plan and start to rebuild data processing site Test the disaster recovery plan © Copyright IBM Corporation 2012

Checkpoint IBM i

1. True or False: Information that changes frequently is something that should be saved on a weekly basis. 2. True or False: The LIC and all of the Q libraries should be saved on a daily basis. 3. Which of the following is not one of the save strategies that was covered in the lecture? a. b. c. d.

Simple Medium Full Complex



1. True or False: Information that changes frequently is something that should be saved on a weekly basis. The answer is false. 2. True or False: The LIC and all of the Q libraries should be saved on a daily basis. The answer is false. 3. Which of the following is not one of the save strategies that was covered in the lecture? a. Simple b. Medium c. Full d. Complex The answer is full.


Unit summary IBM i

Having completed this unit, you should be able to: • Compare the availability options that are available and their impact on the recovery process • Describe simple, medium, and complex save strategies • Describe a disaster recovery plan


Problem determination


7.0


After completing this unit, you should be able to: • Display IBM Power Systems with IBM i information and identify problem jobs • Change values that affect system performance and problem handling • Schedule functions that avoid system problems


Topic 1: Problem determination concepts


7.0

Problem determination IBM i

• Where can I look? • What can I do?


Problem determination process IBM i

• Problem determination has two components: – Problem determination (PD) – Problem source identification (PSI)

• Problem determination: – Identifying the problem – Identifying the effects of this problem

• Problem source identification: – Identifying what has caused the problem

• Often called PD / PSI © Copyright IBM Corporation 2012

Classification of symptoms IBM i

• There are two classifications of symptoms: – External symptoms • • • •

Incorrect output Messages Wait Loop

– Internal symptoms • • • •

Record messages Determine if one job is in a loop or is the entire system Determine if the wait is at a job level or the system level Determine if the problem is isolated within a job environment or between jobs


Problem solving tools IBM i

IBM Syste ms Director Navigato r for i

YSCN P C R ST OB WRKJ OG L JOB TJOB C WRKA

WRKS Y DSPL SSTS O G Q DSPM S G Q HST S Y SO PR

WRKP RB

IBM Power Systems with IBM i toolbox © Copyright IBM Corporation 2012

SG24-8253: Diagnostic tools Redbook IBM i


Topic 2: Problem determination using 5250 emulation


7.0

Work with Active Jobs command IBM i


Work with Active Jobs screen IBM i


Work with Job IBM i


Option 3: Display Job Run Attributes IBM i


Option 10: Job log or DSPJOBLOG IBM i


Ending a job IBM i


End Job Abnormal IBM i


Display system operator messages IBM i


History log IBM i

• System history – Automatically logs system activity • Job information (start/stop times) • Component failures • Critical IBM Power Systems with IBM information – Storage thresholds

• Information written to a system log – QHST • Multiple physical files QHST


Problem analysis: History log IBM i

QHST *MSGQ

DSPLOG

• Collection of messages summarizing system activity: – IBM Power Systems with IBM i information

QHSTyydddn QHSTLOGSIZ

– Job information – Device status changes – System operator messages 'A LOG VERSION'

– PTF activity © Copyright IBM Corporation 2012

DSPLOG IBM i

QHST: Log of all system messages


DSPLOG QHST IBM i


Saving and deleting history logs IBM i


Copy screen IBM i

I need some assistance.

STRCPYSCN

Remote assistance or problem determination


Let me see what is happening on your workstation.

Topic 3: Problem determination using IBM i Navigator


7.0

Active Jobs: Details IBM i


Active Jobs: Job Log IBM i


Active Jobs: Elapsed Performance Statistics IBM i


Job properties: General IBM i


Job properties: Performance and Printer Output IBM i


Job properties: Messages and Job Log IBM i


Job properties: Server and Security IBM i


Job properties: Date/Time and International IBM i


Job properties: Threads, Resources, and Other IBM i


End a job IBM i


End Job Abnormal IBM i


Active Pools: Performance statistics IBM i


System operator messages (1 of 2) IBM i


System operator messages (2 of 2) IBM i


Topic 4: Using the power off switch


7.0

Why use the power switch? IBM i

If I have to shut down the system abnormally, what can I do to reduce the time for the next IPL?

Shut down using the power switch or power push button.


Power down initiation using power push button or power switch IBM i

• This operation ends: – All interrupted MI instructions completed – Power off follows – Next IPL longer than normal

• If not completed in 30 minutes, you should use system problem handling procedures.


What can I do to help minimize problems? IBM i

• You can: – Recognize normal versus abnormal. • System performance • Job mix

– Get rid of unneeded objects. • Clean up your system


Topic 5: System cleanup


7.0

Cleaning up your system IBM i

• Temporary libraries deleted • Work control blocks compressed (QTOTJOB) • Unused addresses made available • Subsystem job logs closed • New job logs created

The tasks performed during an IPL result in a more efficient system.


Automatic cleanup (Operational Assistant) IBM i


Tailoring automatic cleanup (1 of 3) IBM i

Automatic cleanup

Manual cleanup

Messages • User message queues • Workstation message queues • System operator message queue

Messages • All other queues

Printer output • Output queue QEZJOBLOG (job logs) • Output queue QEZDEBUG (service and program dumps)

Printer output • All other output queues

Journals • DIA files journal • DSNX journal • Problem databases journal • Performance adjustment journal • Job accounting journal • OSI Message Services/400 journal • Managed System Service/400 journal • Application Enabler OFC files journal • Application program driver files journal • SNMP journal

Journals • Security journal • All user journals



Automatic cleanup

Manual cleanup

• Application Development Manager Transactions journal • Project logs journal • Work order request journal • QMSD job journal Other system objects • History log • Problem log and files • Alerts database • PTF save files • Reclaim temporary storage used by temporarily decompressed objects

Objects created by applications or users • Database files (delete if no longer needed) • Database files (reorganize) • Programs (for example, Query/400)



• RTVCLSRC – PGM(QSYS/QEZUSRCLNP) SRCFILE(SOURCE-LIB/SOURCEFILE)

• STRPDM – Use SEU to code additional functions.

• Compile QEZUSRCLNP and store it in a library. – The library you store it in should precede QSYS in the library list. Now: Your version of QEZUSRCLNP will be automatically run by the system.


Reorganize file IBM i

• This frees storage used by deleted records; it can also sequence a file more efficiently. • If a file is journaled, back it up immediately after it is reorganized. DSPFD

RGZPFM

FILE(Name)

TYPE(*MBRLIST)

MEMBER

SIZE_ _ _ _ _ _ _ _RECORDS

BROCHPF

12493824

FILE(Name)

45712

MBR(Name)


DELETED RECORDS 5981

KEYFILE(File Member)

Reorganize file or table IBM i


Clear Save File (CRLSAVF) IBM i

• Saving using a save file: *FILE

*SAVF SAVSAVFDTA SAVOBJ

CUSTMAST

CUSTMAST

Wasted space on system

CLRSAVF FILE(SAVE-FILE-NAME)


CUSTMAST

Reclaim Storage (RCLSTG) IBM i

• Unexpected failure can cause unusual conditions. – Objects not correctly updated (damaged) – User profiles might contain incorrect information about object ownership

• Consider running RCLSTS when: – WRKSYSSTS--High percentage of auxiliary storage used – Unusual things exist when you: • Work with object description • Work with user profiles

– Starting system • Message received not enough storage

– Have not run RCLSTG in quite a while


RCLSTG command IBM i


After running RCLSTG IBM i

• Directory QReclaim (root file system objects only) • Library QRCL – Examine after running RCLSTG – DSPLIB QRCL

• Take appropriate action – Delete unusable objects – Move objects – Grant authority – Transfer ownership – Copy data to rebuild files


Web sites for more information IBM i

• IBM i Information Center – http://publib.boulder.ibm.com/eserver/?topic=/rzahg/icmain.htm


Exercise: Problem determination IBM i

Problem determination: Lab exercise © Copyright IBM Corporation 2012


1. True or False: The process of finding out exactly what is the problem is problem source identification. 2. The two classifications of problem symptoms are: a. b. c. d.

Messages External symptoms SRC Internal symptoms

3. The command to work with all of the active jobs on the IBM Power System with IBM i is: a. WRKJOB b. WRKACTJOB c. WRKSBMJOB d. WRKSPLJOB

4. True or False: When displaying your job’s run attributes, you can select the F9 key to change your job. 5. True or False: If your job has not ended after five minutes, you can submit the ENDJOBABN command. © Copyright IBM Corporation 2012


1. True or False: The process of finding out exactly what is the problem is problem source identification. The answer is false. 2. The two classifications of problem symptoms are: a. b. c. d.

Messages External symptoms SRC Internal symptoms

The answers are external symptoms and internal symptoms. 3. The command to work with all of the active jobs on the IBM Power System with IBM i is: a. b. c. d.

WRKJOB WRKACTJOB WRKSBMJOB WRKSPLJOB

The answer is WRKACTJOB. 4. True or False: When displaying your job’s run attributes you can select the F9 key to change your job. The answer is true. 5. True or False: If your job has not ended after five minutes, you can submit the ENDJOBABN command. The answer is false. © Copyright IBM Corporation 2012


6. True or False: Choosing the Active Jobs branch in IBM i Navigator is equivalent to using the WRKACTJOB command on the green screen. 7. True or False: Only the system operator can make changes to a user’s job. 8. True or False: The preferred method to shut down an IBM Power System with IBM i is to use the power switch. 9. True or False: The CLEANUP program will always run automatically on your system at midnight. 10. True or False: A programmer can update the CLEANUP program to perform whatever user activities the programmer decides to add. © Copyright IBM Corporation 2012


6. True or False: Choosing the Active Jobs branch in IBM i Navigator is equivalent to using the WRKACTJOB command on the green screen. The answer is true. 7. True or False: Only the system operator can make changes to a user’s job. The answer is false. 8. True or False: The preferred method to shut down an IBM Power System with IBM i is to use the power switch. The answer is false. 9. True or False: The CLEANUP program will always run automatically on your system at midnight. The answer is false. 10. True or False: A programmer can update the CLEANUP program to perform whatever user activities the programmer decides to add. The answer is true. © Copyright IBM Corporation 2012

Unit summary IBM i

Having completed this unit, you should be able to: • Display IBM Power System with IBM i information and identify problem jobs • Change values that affect system performance and problem handling • Schedule functions that avoid system problems


Introduction to Backup Recovery and Media Services


7.0


After completing this unit, you should be able to: • Describe the features and functions provided by BRMS • List the different software that makes up the BRMS product • Discuss the benefits of using the WRKMEDBRM command • Discuss the benefits of using the WRKMEDIBRM command • Discuss the benefits of using backup control groups to do your backups • Describe the functions supported for BRMS by IBM i Navigator


Topic 1: Overview of BRMS functions and features


7.0

Backup Recovery and Media Services (1 of 4) IBM i

• Licenses Functions

IBM i 7.1 5770BR1

i5/OS V6R1 5761BR1

i5/OS V5R4 5722BR1

Backup and recovery Media and device management Reporting

*Base

*Base

*Base

Networking

1

1

1

Archive and retrieval HSM Media library management BRMS user-defined system name Tape library status tool Software encryption HA support for I-ASPs in a BRMS network

2

2

2



• Primary functions: – Backup and recovery (license *BASE option) – Networking (license option 1) – Archive and retrieve (license option 2) – Hierarchical storage management (license option 2)



• Features – Graphical interfaces – Tailored save operations – Lotus server online and incremental saves – Enhanced save-while-active functions – Parallel save and restore support – Network feature – Media and device management – Step-by-step disaster recovery



• The required software is: (7.1 is 5770, V6 is 5761, V5 is 5722) – 5770-SS1 Option 18: Media and storage extensions • Optional feature of IBM i that provides tape interface routines • One-time charge

– 5770-BR1 BRMS • Tier-priced by CPU size; three separate pieces: – *Base: Product – Option 1: Networking – Option 2: Advanced functions (archive / retrieval / HSM)

• The BRMS licensed program product – Supports: • All IBM i tape devices and tape media and save file • Virtual tape and optical media

– Uses standard menus, commands, and help text as well as GUIs – Uses native IBM i save commands in the background •

Tapes readable by any system

• Runs in a single or networked (multisystem) environment © Copyright IBM Corporation 2012

BRMS: Restrictions IBM i

• Restrictions – Tape volumes (physical and virtual) must have a unique volume ID. – There is no support for: • Diskette • Unlabelled or nonstandard labeled tapes

– It does not support SAVSTG, CPYTOTAP, or CPYFRMTAP natively. – It cannot run on the same system as other tape management software.


Supported tape systems IBM i


FlashCopy support: Overview IBM i


BRMS main menu (GO BRMS) IBM i


Media management (WRKMEDBRM) (1 of 2) IBM i

• The WRKMEDBRM command: – Tracks contents of each tape – Protects tapes against overwriting – Manages tape moves to and from offsite locations – Logs tape usage and error rates – Duplicates tapes and manages pairs – Manages tape sets – Manages parallel sets

• Use option 13 to invoke the WRKMEDIBRM command.


Media management (WRKMEDBRM) (2 of 2) IBM i


Media information (WRKMEDIBRM) (1 of 2) IBM i

• The WRKMEDIBRM command: – Tracks data that has been saved – Is sortable – Allows quick and easy restores – Can view down to object/member detail if proper level of detail has been saved

• Type of save is shown. • F11 shows if any objects were missed during the save. – Displays any errors that might have been logged

• Use option 6 to invoke the WRKMEDBRM command.


Media information (WRKMEDIBRM) (2 of 2) IBM i


Backup control groups (1 of 2) IBM i

• Describes the backup – What to backup: libraries, objects, folders, spool files, objects in directories, special values – Full or cumulative – Save-while-active

• Controls backups – – – –

Subsystems to end, job queues to hold, users to sign off Which media to select Use save files Use virtual tape

• Tracks success of backup – BRMS log shows all backup activity – Backup activity report shows all items saved and missed – Save strategy exceptions shows libs never backed up

• Facilitates parallel saves © Copyright IBM Corporation 2012

Backup control groups (2 of 2) IBM i


Recovery IBM i

• Recovering a few objects: – The user selects objects from a list of saved items. – BRMS provides mount messages as required. – There is an online progress report.

• Recovering a large number of objects or whole system: – The volume summary report lists volumes needed. – The recovery analysis report lists steps required. – BRMS manages the recovery.


Recovery with WRKMEDIBRM IBM i

• WRKMEDIBRM with 7 (Restore object) – When you select option 7, the subsequent screens should guide you through the rest of the restore. © Copyright IBM Corporation 2012

Archive (1 of 4) IBM i

• Archive – Locate and list objects that have not been used recently. – Move these objects to tape and erase from disk. – This frees up disk space.

• Retrieval – Restore objects back to disk when needed. – For *FILE, IFS, and DLO objects, BRMS optionally should auto-recall when touched by a user, provided that they are archived with STG(*FREE).








Advanced functions: HSM (1 of 2) IBM i

• Hierarchical storage management (HSM) (migration) • Allows migration of data among expensive and fast disks to less expensive and slower disks – Through user ASPS – Automatically using control groups – Manually using STRMGRBRM command

• Eventually to tape through archive


Advanced functions: HSM (2 of 2) IBM i

• Only libraries, root folders, and spool files are eligible for migration. • Specify criteria for objects to migrate. • *DEMOTE or *PROMOTE through the hierarchy chain of user ASPs one storage level at a time. © Copyright IBM Corporation 2012

TSM application client to BRMS IBM i


Topic 2: Overview of IBM i Navigator and BRMS


7.0

IBM i Navigator IBM i

• If BRMS is installed on the system, the BRMS plug-in is available. • If BRMS is not installed on the system, the BRMS plug-in is not available.


BRMS GUI V6R1 IBM i

• IBM i Navigator and IBM Systems Service Director for i: – – – – –

Ability to create and manage media policies (was hidden in previous releases) Support for DVD, CD-ROM, optical libraries, and virtual optical devices Support for file or object level backup of Linux or Windows guests OS Backup and archive policies renamed as backup and archive control groups Ability to manage and select media policies from the Backup Control Group and Archive Control Group wizards and from the Properties page – Backup and archive control groups properties support for: • Restoring and saving private authorities • Disk pools and generic libraries • Software encryption, including tape libraries and stand-alone tapes

– Ability to balance media ownership to match the required number of media needed by systems within the BRMS network (network systems must be running V6R1 i5/OS or later) – Ability to exempt media from save operations


BRMS GUI IBM i 7.1 IBM i

• IBM i Navigator and IBM Systems Service Director for i: – Support for the IBM Systems Director Web browser environment – Scheduling support for IBM Systems Director Navigator for i Web browser environment – High availability independent ASPs enhancement – Enhanced current email function to support multiple email addresses – Enhanced BRMS log filter to provide option to filter on control groups – BRMS maintenance feature in backup policy now allows the user to run movement, expire partial volume sets, and reorganize BRMS database files


BRMS functions by release IBM i


BRMS and GUI FAQs IBM i


Topic 3: Additional reference material


7.0

BRMS Internet home page IBM i


BRMS: Product Information link IBM i


Publications IBM i

• Refer to these publications for more information: – Backup Recovery Media Services • IBM i 7.1 SC41-5345-07 • V6R1

SC41-5345-06

• V5R4

SC41-5345-05

– A Practical Approach to Managing BRMS for OS/400 • SG24-4840-01 (Redbook)

– Redpiece (REDP0508) • Info on online Domino, SAP, TSM, and so on • www.redbooks.ibm.com

– Automated Tape Library Planning and Management • SC41-5309

– OS/400 Backup and Recovery • IBM i 7.1 SC41-5304-10 (Systems management: Recovering your system) • V6R1

SC41-5304-09

• V5R4

SC41-5304-08 © Copyright IBM Corporation 2012

Additional Internet sites IBM i

• IBM i Navigator – http://www-03.ibm.com/servers/eserver/iseries/navigator/

• Storage Web site (tape) – http://www-03.ibm.com/servers/eserver/iseries/hardware/storage/

• IBM i Network – http://www.systeminetwork.com/ • Backup basics and BRMS chapters • System i Magazine backup and recovery FAQs • Commonly asked backup and recovery questions

• IBM i Information Center – http://publib.boulder.ibm.com/iseries/


Where can I get education? IBM i

• Education – AS28/OV28

Backup, Recovery and Media Services (BRMS) for IBM i



1. True or False: If you only need to save and restore your data, you only need to install the *Base BRMS software. 2. True or False: In order to do software encryption as part of your save, you would need to install BRMS Option 1: Networking software. 3. True or False: BRMS requires that all of the volumes that it is going to manage must have a unique volume ID. 4. True or False: BRMS will work systems that are part of an SAN. 5. True or False: BRMS provides support to do backup and recovery as well as archive and retrieval.



1.

True or False: If you only need to save and restore your data, you only need to install the *Base BRMS software. The answer is true.

2.

True or False: In order to do software encryption as part of your save, you would need to install BRMS Option 1: Networking software. The answer is false.

3.

True or False: BRMS requires that all of the volumes that it is going to manage must have a unique volume ID. The answer is true.

4.

True or False: BRMS will work systems that are part of an SAN. The answer is true.

5.

True or False: BRMS provides support to do backup and recovery as well as archive and retrieval. The answer is true. © Copyright IBM Corporation 2012


6. True or False: BRMS gets installed as a default for IBM i Navigator. 7. True or False: IBM i Navigator will have a different look and feel depending on what version and release is installed. 8. True or False: The BRMS home page has useful links to help you learn how to use this software to its maximum potential.



6. True or False: BRMS gets installed as a default for IBM i Navigator. The answer is false. 7. True or False: IBM i Navigator will have a different look and feel depending on what version and release is installed. The answer is true. 8. True or False: The BRMS home page has useful links to help you learn how to use this software to its maximum potential. The answer is true.


Unit summary IBM i

Having completed this unit, you should be able to: • Describe the features and functions provided by BRMS • List the different software that makes up the BRMS product • Discuss the benefits of using the WRKMEDBRM command • Discuss the benefits of using the WRKMEDIBRM command • Discuss the benefits of using backup control groups to do your backups • Describe the functions supported for BRMS by IBM i Navigator


Ibm i Administration

Recommend Documents