IBM Using central site distribution User Manual



iSeries

Using central site distribution to install multiple iSeries servers



iSeries

Using central site distribution to install multiple iSeries servers

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Using central site distribution to install multiple iSeries servers ..............1

What’s new for V5R1 ...............................1

Print this topic ..................................2

Central site distribution terms and concepts .......................2

Upgrading a Target Site System to PowerPC Technology .................3

Distribution methods and the process flow .......................4

Electronic distribution and installation of licensed programs ................7

Total system package option or preloaded system option .................9

Release-Level interoperability ...........................10

Fix (PTF) level of the central and target systems ....................10

Planning licensed program distribution .........................14

Before you install the central site system onto a target system ...............14

Distributing license information ..........................14

Creating the IBM licensed program distribution media or premastering tape ..........19

Copying the IBM licensed program distribution media and Licensed Internal Code .......20

Installing OS/400 and other licensed programs on a target site system ............20

Documentation for target site system ........................20

Installing a new iSeries server ...........................21

Language files for the target site system .......................21

User profiles and device configuration distribution to a target system ............22

Installing applications and restoring objects using a user-defined installation program .......24

Using the QLPUSER program ...........................24

Verifying the operation of the QLPUSER program at the target site system ..........25

Working with installation profiles ..........................26

Preparing and installing distribution media .......................43

Before creating a distribution or premastering media with GO LICPGM Menu Option 40 .....43

Using CD-ROMs for installing Licensed Internal Code ..................45

Preparing the distribution or premastering media ....................46

Installing the distribution media at the target site system .................51

Optional tasks for installing distribution media .....................52

Central site distribution cover sheet ..........................55

Distribution media stacking order ...........................55

iv iSeries: Using central site distribution to install multiple iSeries servers

Using central site distribution to install multiple iSeries servers

It is sometimes desirable to duplicate some or all of a system’s programs, including the operating system, onto another system. To do this with a minimum of effort and maximum benefits you should do some planning and consider the options available for performing a licensed program distribution. This set of pages is designed to help you with these planning decisions. Then these pages will show you a step by step procedure for implementing the duplication. The whole process includes:

v Central site distribution terms and concepts

This gives you an idea of the terms that will be used and the basic requirements for the central site

process to continue successfully, such as Release-level interoperability and the system fix (PTF) level.

You will also be introduced to some basic options such as the choices for distribution media.

v Planning licensed program distribution

This section takes you through decisions that affect the content of the licensed program distribution. You

will consider language files, distributing license information, licensed program distribution media,

Licensed Internal Code, OS/400 licensed program, manuals for target site system, and user profiles and

device configuration.

v Installing applications and restoring objects using a user-defined installation program

This section shows you how to use a program to automate some of the central site process. The

program can restore user profiles, configurations, and install applications.

v Preparing and installing distribution media

This section takes you through the final steps to install the central site system code on the target site

system. First you will get instruction on the things to do before you create a distribution or premastering

media. Then the instructions will cover installing the distribution media at the target site system,

including the use of an alternative installation device. Finally there will be a list of optional tasks for

installing distribution media.

v Central site distribution cover sheet

This cover sheet gives the people at the target site any special information they need. It is sent along

with the distribution media.

v Distribution media stacking order

This page contains a link to a 24 page PDF file that you can print out. The table gives information on

what files are needed for each application.

What’s new for V5R1

There have been a few changes to this information for V5R1.

View and print all associated documents

You can now access all the information about creating distribution media from one central location at Print this topic.

Updated list of programs that do not support secondary languages

Because these programs do not support secondary languages, you do not need to save these programs at the central site system when you want to distribute secondary languages to target site systems.

Updated the stacking order

You can use the stacking order to verify that all of the files you saved from the central site system were correctly transferred to your distribution media.

How to see what’s new or changed:

To help you see where technical changes have been made, this information uses:

v The

image to mark where new or changed information begins.

image to mark where new or changed information ends.

Print this topic

v Installing multiple iSeries servers using distribution media (about 530 KB) contains the following topics:

– Information about creating distribution media

– Planning for creating distribution media

– Creating the distribution media

v Stacking order (about 59 KB) contains the stacking order for your distribution media. Print this PDF file

to verify that you correctly transfered all of the files to the distribution media.

v Cover letter (about 3 KB) is a sample letter that contains sample instructions for the central system to

provide to the target systems for using the distribution media.

To save a PDF on your workstation for viewing or printing:

1. Open the PDF in your browser (click the link above).

2. In the menu of your browser, click File.

3. Click Save As...

4. Navigate to the directory in which you would like to save the PDF.

5. Click Save.

If you need Adobe Acrobat Reader to view or print these PDFs, you can download a copy from the Adobe

Web site

(www.adobe.com/prodindex/acrobat/readstep.html).

Central site distribution terms and concepts

The distribution of a central site system is different from the normal distribution of application programs, system control information, and data in a distributed systems network. One difference is that the distribution media the central site sends to a target system site can be either tape, CD-ROM, or DVD. Another difference is that you must attend the target site system while installing licensed programs.

These pages highlight some of techniques and considerations that are needed to develop a plan for:

v Distributing licensed programs in a distributed systems network.

v Distributing licensed programs to other systems that operate more independently.

The systems discussed in this page are the central site system and the target site system.

v Central site system. This system is licensed to receive the distribution media from IBM. In a distributed

systems network, the central site system is usually defined to be the focal point in a communications network for alerts, application design, and network management tasks.

The central site system can also distribute licensed programs to other systems that operate independently of the central site system. However, these systems depend on the central site system for distributing licensed programs.

Media created by the central site supports the following:

– Software already at V3R6 or later (runs only on PowerPC AS processors).

– Software already at V4R1 or later (runs only on PowerPC AS processors).

– Performing a CISC to RISC upgrade, where the target release is V4R2 or later.

2 iSeries: Using central site distribution to install multiple iSeries servers

– The upgrade happens to both the hardware and software in the same process.

Note: You must upgrade hardware and software at the same

time when upgrading from CISC to RISC. This is unique to CISC to RISC upgrades.

– Having the central site upgrade to PowerPC Technology and V4R3 or above, but having the target

sites remain at a previous release level with existing hardware.

You must be running on PowerPC AS hardware to create media for a target site system that you upgrade to PowerPC Technology. See Upgrading a target site system to PowerPC Technology for more details.

v Target site system. This system depends on the central site system for distribution of licensed

programs. This system is possibly unattended, and is probably not licensed to receive licensed program

media from IBM.

A target site system can be one of the following:

– Part of a distributed systems communications network.

– Operate independently of the central site system but rely on the central site for licensed program

distributions and application development and maintenance.

The distribution tasks should occur at the following times:

1. The initial distribution by the central site system

2. The distribution of fixes between releases

3. The distribution of an upgrade for IBM-supplied licensed programs

There are a number of terms, concepts, and choices you should become know about. Understanding the following topics will help in the planning stage of the Central Site Distribution process.

v Distribution methods and the process flow

This details the two distribution methods at your disposal. The flow of each process, either media (tape

or DVD) or premastered CD-ROMs, is shown.

v Electronic distribution and installation of licensed programs

This tells about options for distributing IBM licensed programs and customer applications electronically

from a central site system.

v Total system package option or preloaded system option

When you choose the total system package option or the preloaded system option for ordering a new

system, the system will come with licensed programs installed and configured hardware.

v Release-level interoperability

The central site system and the target site have compatable software releases. Interoperability is the

ability of one system to exchange data or objects with another system.

v Fix (PTF) level

Fixes are available to update licensed program code between releases. It is important that both the

central site system and target site system be at the current fix level.

Upgrading a Target Site System to PowerPC Technology

You must be running on PowerPC AS hardware to create media for a target site system that you upgrade to PowerPC Technology.

When you upgrade a target site system to an iSeries server with PowerPC Technology, you upgrade the hardware and software at the same time.

Note: Systems that are running the V3R7 or Version 4 operating systems are already using PowerPC AS software. This topic does not apply to such systems.

Using central site distribution to install multiple iSeries servers 3

Note: For more information about the following upgrade methods, see the AS/400 Road Map for Changing to PowerPC Technology, SA41-5150. Each target site must be upgraded to PowerPC Technology as

described in that book.

Three methods are available to change your target site system to PowerPC Technology:

v Unload/reload method

When you use this method, you save your information to tape (unload) before the hardware upgrade process. You restore your information from tape (reload) after the hardware upgrade process.

v Replacing-a-release method

When you use this method, you prepare your data for a new disk format before the hardware upgrade process. The hardware service representative converts your disk storage during the upgrade process. You do not have to reload data.

v Side-by-side method

When you use this method, you install an entirely new system (with a PowerPC AS processor) in parallel with your existing system. Usually, you run the two systems in parallel during a transition period. When you are satisfied with object conversion and testing, you move the system with the PowerPC AS processor into production.

Many times, the parts that are required to upgrade an existing system to PowerPC AS hardware are nearly sufficient to construct a temporary, stand-alone operational system. Because of this, the Staged Upgrade Offering is available for many MES upgrades for an additional charge. IBM’s intent with the Staged Upgrade Offering is to provide enough equipment with the MES. In this way, you can construct a limited test environment at minimal additional expense. You will need to purchase or rent some additional equipment, such as disk units, tape attachment features, or a workstation controller. This equipment is used to construct a configuration that is suitable for object conversion and limited testing.

You can use the Staged Upgrade Offering with all three upgrade methods. Your marketing representative can help you determine whether the Staged Upgrade Offering is available for your configuration and whether it is appropriate for your situation. The Staged Upgrade Offering may reduce the time that your system is unavailable during the upgrade. However, careful planning and technical skills are necessary to use this offering successfully.

For more information about the Staged Upgrade Offering, see the AS/400 Road Map for Changing to PowerPC Technology, SA41-5150.

In the AS/400 Road Map for Changing to PowerPC Technology, you can find work sheets that you can use for planning upgrades. You can customize these work sheets for the needs of each target site system.

Note: In this book, the target system is a system that depends

on the central site for distribution of licensed programs. In the AS/400 Road Map for Changing to PowerPC Technology, the target system is a system that is being upgraded to PowerPC Technology.

Distribution methods and the process flow

There are two basic methods available to the central site system for distributing licensed programs.

Create the IBM licensed program distribution media at the

central site system

Central Site System Central Site System

Create tapes for premastering CD-ROM

Create distribution media at the central site system Use the qlpHandleCdState API to put job in premastering

state

4 iSeries: Using central site distribution to install multiple iSeries servers

GO LICPGM Menu Option 40

(Create a distribution media)

Distribution Tape Premastering Tape

Install Licensed Internal Code and licenced programs Use the qlpGenCdPermasteringInfo API to create

distribution set map and to return information about the

Target Site System Save the distribution set map to media

Use the qlpHandleCdState API to disable the job for

Work with your CD-ROM mastering service to plan the

Send the tape and the plan to your mastering service

Create the premastering tape

(GO LICPGM Menu Option 40)

saved files

premastering

content of your CD-ROM volumes

Get back the CD-ROM prototype

Verify the CD-ROM prototype and authorize a production

run for your distribution copies

Distribute the production run copies to target sites

Install Licensed Internal Code and licenced programs

Target Site System

Method 1 - Create the IBM licensed program distribution media at the central site system (from media tape or DVD). Install the IBM-supplied licensed program distribution media at the central site system. Then select option 40 (Create a distribution media) on the GO LICPGM (Work with Licensed Programs) menu to create a distribution media. This media is then distributed to target site systems.

Method 2 - Create tapes for premastering CD-ROM (from CD-ROM). Install the IBM-supplied licensed program distribution media at the central site system. Then select option 40 (Create a distribution media) on the GO LICPGM menu to create a tape. This tape is used as input for the CD-ROM premastering process.

Note:

The distribution media that the central site distributes to a target site includes:

v The IBM Licensed Internal Code

v The OS/400 Licensed Program

v The installation profile

v The user-defined installation program

Using central site distribution to install multiple iSeries servers 5

v Other licensed programs

v User libraries

v fixes

Method 1 - Create the IBM licensed program distribution media at the central site system

This method uses option 40 (Create a distribution media) on the GO LICPGM menu to create a distribution media. You can then distribute and install the media on other systems. You can also distribute user libraries that contain applications. However, the central site system must provide the target site systems with instructions on how to install the user libraries or provide a user-defined installation program.

One advantage to this method is program temporary fix (PTF) management. You can apply fixes at the central site system before distributing the licensed programs by using this method. The licensed programs with applied fixes will be distributed when you create your distribution media.

Another advantage to this method is an installation profile. The target site system can use the automatic installation method by using an installation profile. The automatic installation method reduces the number of tasks the operator must perform during the installation at the target site system. Working with installation profiles contains information about installation profiles.

The central site system should have adequate resources, such as auxiliary storage, to handle all licensed programs needed at the target site systems. This is also true for applications that are developed at the central site system for target site systems.

Target site system resources (for example, auxiliary storage) must be sufficient to receive distributions (licensed programs and applications) from the central site system. For more information about resources

that are required for licensed program distributions, see Software Installation

Another resource consideration is a common tape exchange media such as a 1/2-inch tape cartridge, or DVD.

For the current operating system, any combination of iSeries servers that use the same type of media, can use method 1 to install IBM Licensed Internal Code at a target site system.

A hardware service representative installs the Licensed Internal Code during a CISC to RISC upgrade. However, you may be able to reduce the software installation time for a target site by creating a tape that has fixes applied to the Licensed Internal Code.

Method 2 - Create tapes for premastering CD-ROM

If you plan on distributing your software on CD-ROM, you can use these two application program interfaces (APIs) to get the required information needed for the premastering process:

v The Handle CD-ROM Premastering State (qlpHandleCdState) API is used to place your job into a

premastering state.

v The Generate CD-ROM Premastering Information (qlpGenCdPremasteringInfo) API is then used to

return information about the size of the tape files saved. It also returns information that shows which CD-ROM volume the files reside on. This API also creates the distribution set map.

For more information on APIs, see CL and APIs.

Premastering is the process of creating a tape that can be used as input to generate a CD-ROM. The tape contains the data which is used to create a CD-ROM image that can be read on a CD-ROM drive.

The qlpHandleCdState API allows you to do the following:

6 iSeries: Using central site distribution to install multiple iSeries servers

v Place your job in a premastering state. When the job is in this state, all save operations (SAVOBJ,

SAVLIB, SAVLICPGM, SAV, etc.) result in information being stored about the sizes of these tape files.

This information is then used by the Generate CD-ROM Premastering Information

(qlpGenCdPremasteringInfo) API to generate the QDSETMAP bytestream file. Also, while in this state,

the data format that is written to tape is changed slightly so it can be restored from the CD-ROM.

v Query the existing state of your job as well as optionally getting information about saves that may have

already taken place. In case you are interrupted, this lets you know where you have left off and where

to restart. As input to the qlpHandleCdState API you need to specify a distribution set map identifier.

This identifier is used to ensure that correct information is returned about the saved files.

v Take your job out of a premastering state.

Note: Ending your job also takes your job out of a premastering

state.

The qlpGenCdPremasteringInfo API allows you to do the following:

v Create a bytestream file in the root directory. This file contains information about which tape files reside

on each CD-ROM volume. The name of the file is /qlpnnnnnnnnnn where nnnnnnnnnn is the name of

the distribution set map identifier provided as an input parameter to this API. For more information, see

Saving the contents of the bytestream file.

The only valid characters for nnnnnnnnnn in the set map identifier are uppercase letters A through Z,

numeric characters 0 through 9, and underscore (_).

v Retrieve information about the files saved when the job was enabled for CD-ROM premastering by

using the qlpHandleCdState API. This information includes:

– The tape file name.

– The corresponding CD-ROM file name.

– The CD-ROM volume it is placed on.

– The volume serial position in this set of CD-ROMs.

Electronic distribution and installation of licensed programs

IBM licensed programs and customer applications can be distributed and installed electronically from a central site system. There are two options available.

You can use Management Central if you are running on a TCP/IP network instead of a SNA network. Management Central is a part of Operations Navigator.

You can also use the System Manager/400 licensed program provides centralized services for software distribution and installation on other systems in SNA and TCP/IP networks. To receive licensed programs and applications electronically from the central site system, both the central site system and the target site system must have the latest release level of the Managed System Services/400 licensed program installed.

Note: The Managed System Services/400 licensed program

cannot be installed remotely on the target site system from the central site system.

The benefits in using electronic distribution from the central site system are:

v Fewer errors because distribution and installation plans can be created, reviewed, and tested before

sending updates to the managed system sites.

v Reduced operation costs because the central site system tracks job status.

Installation methods

Using central site distribution to install multiple iSeries servers 7

The basic methods for installing the distribution media at the target site system are:

v Automatic installation

Automatic installation means that the operator at the target site system simply loads distribution media as prompted.

v Manual installation

When manual installation is used, the operator at the target site system must perform several tasks to install the system with the distribution media.

v Alternative installation device

Using the new Alternative installation device support, the system continues the operation with media in the Alternative installation device.

Automatic installation in the central site process

Note: If you are performing a CISC to RISC upgrade, do not use

the automatic installation method.

Automatic installation means that the operator at the target site system simply loads distribution media as prompted.

Note: If you are using a tape device instead of the optical device

optimized for CD-ROM or DVD, you should verify that the tape unit is varied on. Also, verify that the tape device is allocated to your system.

When you perform an automatic installation at the target site system, you read the values that control the installation from an installation profile on the distribution media. When you perform an automatic installation, the primary language you use on the distribution media is the same as the primary language that you load.

Using an installation profile to install media containing licensed programs, fixes (PTFs), and application programs has the following advantages:

v Operator interaction during the installation is reduced to mounting media as prompted.

v Allows the central site planner to create customized installation profiles to control the installation at the

target site system.

v Provides the capability to restart after a failure, including bypassing parts of the installation that were

successful.

v Reduces or eliminates messages during the installation.

v Allows the central site planner to install applications or further customize the system after a successful

installation using a user-defined installation program.

Automatic installation can be used to install distribution media that was created by either of the two methods previously described.

If Method 1 - Create the IBM licensed program distribution media at the central site system - is used, then you must create an installation profile. Working with installation profiles contains information about installation profiles.

Manual installation in the central site process

Note: If you are performing a CISC to RISC upgrade, use the

manual installation method.

8 iSeries: Using central site distribution to install multiple iSeries servers

When manual installation is used, the operator at the target site system must perform several tasks to install the system with the distribution media. Displays are presented that allow the operator to customize the installation. The manual process allows you to change the default install options. This includes:

v Restoring language objects

v Job and output queue options

v Restore options:

– System information

– Edit descriptions

– Job descriptions

– Subsystem descriptions

– Message reply list

Use the manual installation process if you are doing any of the following installation procedures:

v Performing a CISC to RISC upgrade

v Adding storage

v Installing additional licensed programs that are not on the distribution media

For more information about installing your new release, see Software Installation

Alternative installation device in the central site process

A function introduced in V4R1M0 allowed you to perform installation procedures and recovery procedures by using a combination of devices. Prior to this, you had to attach devices to the first system bus before you could perform these types of activities. (The first system bus connects to the service processor IOP. Typically we attach the optical device or tape devices that are used for installations to this location.) With the release of V4R1, you could now use a combination of devices that are attached on the first system bus and on additional buses. This function is still available in the current operating system. The Alternative installation device does not attach to the first system bus.

If you use this function, the system uses existing support (a device on the first system bus). This support is to install or recover enough of the Licensed Internal Code required to perform an IPL with IPL-type D.

Note: We require a Licensed Internal code CD-ROM for this

part.

There are some specific install and recovery implications for Models 600 and 620 when you use an Alternative installation device.

Using the new Alternative installation device support, the system continues the operation with media in the Alternative installation device. This new function supports installation and recovery from tape media. Examples of these are SAVSYS tapes or distribution tapes which you created, that contain Licensed Internal Code and may contain the operating system, licensed programs, and data.

Some models, that typically have 3590 tape devices attached, may see a performance improvement when using an Alternative installation device for save operations.

Total system package option or preloaded system option

IBM provides the Total System Package (TSP) option or the preloaded system option for ordering a new system. When you receive these options, they come with licensed programs installed and configured hardware.

Using central site distribution to install multiple iSeries servers 9

Total System Package systems and preloaded systems are licensed to receive their own IBM distribution media and fixes. Licensed program distribution need not be a part of central site system activity.

Distributing applications and system control information can be done through communications in a distributed systems network or by

Release-Level interoperability

It is the responsibility of the central site to ensure that the central site and the target site have compatable software releases. This is especially important if you want to have objects and data interchange between systems.

Note: You can see the installed release of licensed programs by

using option 10 (Display licensed programs) on the Work with Licensed Programs menu. This displays the release of licensed programs that were initially shipped with an operating system release or modification level. Use the Display Software Resources (DSPSFWRSC) command to see the release of licensed programs not initially shipped with an operating system release or modification. You can also use this command to see what Program Request for Price Quotations (PRPQs) and licensed program offerings (LPOs) are installed on the system.

Interoperability is the ability of one system to exchange data or objects with another system. The exchange can be performed electronically or by physical media (such as tape). Either system may initiate the exchange.

An iSeries server interoperates with another iSeries server when exchanging data or when saving and restoring objects.

For more information on saving objects to a system running a previous release, see the chapter on

release-to-release support in Backup and Recovery

Exchanging data between different release levels

The source system (the system that sends the information) and the system that receives the information must be within the supported release levels. If the source system is at the current release level, the system receiving information can be at V3R2M0 or any level of Version 4 operating system.

Saving and restoring objects between different release levels

Objects that are interoperable must be saved by specifying either a specific release level or *PRV for the value of the target release (TGTRLS) parameter.

For more information on saving objects to a system running a previous release, see Backup and Recovery

Licensed programs can be saved and restored similar to other objects as long as the release level is compatible with the operating system release level. For more information about compatible levels of

licensed programs, refer to Licensed Program Information section in Software Installation

Fix (PTF) level of the central and target systems

IBM periodically makes fixes available to update licensed program code between releases. For information on avaliable fixes, see Managing fixes with Management Central.

10 iSeries: Using central site distribution to install multiple iSeries servers

For detailed information about working with fixes and Licensed Internal Code fixes, see ″Working with Program Temporary Fixes″ in the Basic System Operation, Administration, and Problem Handling, SC41-5206. The page, Central site system distribution of fixes, pertains to central site system management and the distribution of fixes. This information is intended to supplement the Basic System Operation, Administration, and Problem Handling book.

Depending on the licensing option you are using, fixes are available to the central site system or to target site systems in two ways:

v Corrective service

– On media accompanied by a cover letter that describes the contents of the media

– From the service support system by way of electronic customer support

v Preventive service

– Cumulative PTF media

It is the responsibility of the central site system to control the PTF level of the target site systems.

Fixes (PTFs) for Network Interoperability

To exchange objects in a network between systems running V3R2M0 or any Version 4 operating system, and systems running earlier releases, apply fixes to the earlier systems. You cannot restore objects to earlier systems until you apply fixes to the earlier systems. You can avoid a delay by ordering the needed fixes and applying them now to the systems that will remain at earlier release levels.

For the systems that remain at the V3R2M0 release level, you will need to order and apply PTF SF33467. This will enable exchanging data between V3R2M0 systems and current systems. You will receive several corequisite fixes when you order any of the fixes shown. These are needed for the following:

v Restoration of save files

v Database objects

v Journal receivers

v Program objects

v Objects that are associated with byte stream files:

– Document objects (*DOC)

– Stream File objects (*STMF)

– Symbolic Link objects (*SYMLNK)

Central site system distribution of fixes

The central site system planner should coordinate the PTF levels of the central site system and the target site system. This ensures that all systems are at the same level. See Managing fixes with Management Central for information on obtaining and applying fixes. The central site system planner should also verify correct system operation before the fixes are distributed to target site systems. To coordinate the PTF level of the target site systems, one of the following methods can be used:

v Apply fixes at the central site system. Distribution media is created at the central site system using the

GO LICPGM menu option 40 (Create a distribution tape). This media is installed at the target site

system, replacing Licensed Internal Code Copy A and Copy B and installs licensed programs at the

central site system PTF level. This method can be used for first installation, upgrade installation, or

distribution of cumulative packages. The advantages of this approach are:

– No special PTF installation instructions are needed at the target site system.

– The target site system will be at the same PTF and release levels as the central site system.

v Distribute fixes to target site systems. If the central site system distributes individual or cumulative fixes

to target site systems, the central site system must provide instructions on installing the fixes. It must

also keep a record of the target site system PTF level.

Using central site distribution to install multiple iSeries servers 11

The different methods of distributing fixes to target site systems are shown in the following illustration.

First Installa tion or Upgrade

IBM CD-ROM Distribution Media

Central Site

System

LPs Installed

with

PTFs Applied

Create Distribution Media

Individual PTFs

SAVF by way of electronic

CD-ROM PTF Media

or CPYPTF or CPYPTF

Central Site

System

Load and Apply

Object Distribution or SNDPTF

customer support

S A V F

Cumulative PTF Package

Central Site

System

Load and Apply

Create Distribution Media

CD-ROM PTF Media

S A V F

Ta il or ed

Ta pe

Load and Apply

RV2Q628-1

Central Site Distribution

Ta pe

Central Site CD-ROM Distribution Media

Ta rg e t S i t e

System

LPs Installed

with

PTFs Applied

Ta il or ed

Ta pe

Ta rg e t S i t e

System

Load and Apply

Central Distribution Media

CD-ROM Distribution Media

Central Site System Installa tion Instructions

LPs Installed

PTFs Applied

Ta il or ed PTF Installati on Instructions

or or

Ta rg e t S i t e

System

with

The numbers at the beginning of the following paragraphs correspond to the reverse image numbers on the previous illustration.

(1)

12 iSeries: Using central site distribution to install multiple iSeries servers

First installation or upgrade installation of licensed programs and fixes at the central site system using the

AS/400 Road Map for Changing to PowerPC Technology, SA41-5150, and Software Installation

The PTF cumulative package is shipped with the IBM CD-ROM distribution media as a separate CD-ROM. You should load and apply these fixes, using the PTF Shipping Information Letter, before you create your distribution media. This ensures you distribute the latest level of the licensed programs and that all target site systems at the same release level have the same fixes applied. If fixes are applied at the central site system, the target site system does not have to apply fixes.

Fix considerations for an upgrade installation at the central site system are the same as first installation. The central site system should apply the fixes that come with the release so the latest PTF level is on the central site system distribution media.

(2)

Individual fixes ordered and received at the central site system.

Individual fixes may be installed between releases, either at the central site system or target site systems. To control the PTF level of target site systems, you should use the Display PTF (DSPPTF) command. This ensures the central site system is aware of the PTF level of target site systems.

An individual PTF save file can be distributed to the target site system by doing one of the following:

v Using the object distribution command Send Network File (SNDNETF).

v Copying the PTF save file to media using the Copy Program Temporary Fix (CPYPTF) command.

Note:

The SNDNETF command can only be used if SNA Distribution Services (SNADS) is active on both the central site system and the target site system.

You can also distribute fixes electronically using the Send PTF (SNDPTF) command. This command is part of the System Management/400 licensed program.

(3)

Cumulative PTF packages ordered and received from IBM for central site system.

Instructions for installing PTF cumulative packages at the central site system are included with the cumulative PTF package. To distribute a cumulative package to target site systems:

v Use the Copy PTF (CPYPTF) command to duplicate the PTF package and the printed instructions.

Then send them to the target site system locations for attended installing.

v If you decide to create a tailored media, tailor it to include only the selected items you want to distribute.

How to tailor a fixes media is discussed in Distributing fixes to remote systems.

The tailored fixes media can be distributed to target site systems by doing one of the following:

– Sending the media to the target locations.

– Distributing the media through your distributed system network as save files.

v Load and apply the package at the central site system. Then use option 40 (Create a distribution media)

on the GO LICPGM menu to distribute the licensed programs with fixes applied to target site systems.

v If the central site system received fixes on media and wants to distribute the fixes using object

distribution, use the Copy PTF (CPYPTF) command to copy the fixes to a save file. For more

information about handling fixes, see Distributing fixes to remote systems.

Using central site distribution to install multiple iSeries servers 13

Planning licensed program distribution

There are a number of things to consider when planning a central site distribution. Some concerns about whether or not objects with security-sensitive attributes can be restored are addressed in Before you install the central site system onto a target system.

License considerations and handling of such programs is covered in:

v Distributing license information

This section tells you about distributing license information for products that use the OS/400 license management function.

v Creating the IBM licensed program distribution media or premastering tape

This section explains how to create a distribution media at the central site system. There are also instructions for creating a tape for premastering the CD-ROM. You will also select which installation profile to use and which licensed programs and OS/400 optional programs to put on your distribution media.

v Copying the IBM licensed program distribution media and Licensed Internal Code

This section explains how to duplicate both tape and optical media and how to copy Licensed Internal Code.

v Installing OS/400 and other licensed programs on a target site system

This section explains how to distribute all or part of OS/400 and other licensed programs.

Besides license concerns, you will have to consider:

v Manuals for target site system

Each new system comes with users and service manuals. This lets you know which manuals need to be ordered for each target system.

v Installing a new iSeries server

If the target system or central system is new, this explains what to expect.

v Language files for the target site system

This explains what to do in order to copy the primary and secondary language files onto the distribution media so you can install them at your target site systems.

v User profiles and device configuration distribution to a target system

This page gives you all the references to set up the user profiles and device configuration from the central site system for use on the target site system.

Before you install the central site system onto a target system

The Allow Object Restore (QALWOBJRST) system value specifies whether or not objects with security-sensitive attributes can be restored. It is important to set the value to *ALL before performing the following system attributes:

v Installing a new release of OS/400

v Installing new licensed programs

v Applying fixes

v Recovering the system

So that these activities do not fail, set the value of QALWOBJRST to *ALL. To ensure System Security, return the QALWOBJRST value to your normal setting after completing the system

Distributing license information

License information can be distributed for products that use the OS/400 license management function. IBM supplies usage limit information for only the central site system. The central site must then determine the usage limits for each target site system and do one of the following:

v Load the usage limit information on the media that is given to each target site.

14 iSeries: Using central site distribution to install multiple iSeries servers

+ 44 hidden pages

IBM Using central site distribution User Manual

Contents

Using central site distribution to install multiple iSeries servers

Print this topic

Central site distribution terms and concepts

Upgrading a Target Site System to PowerPC Technology

Distribution methods and the process flow

Method 1 - Create the IBM licensed program distribution media at the central site system

Method 2 - Create tapes for premastering CD-ROM

Electronic distribution and installation of licensed programs

Automatic installation in the central site process

Manual installation in the central site process

Alternative installation device in the central site process

Total system package option or preloaded system option

Release-Level interoperability

Exchanging data between different release levels

Saving and restoring objects between different release levels

Fix (PTF) level of the central and target systems

Central site system distribution of fixes

Planning licensed program distribution

Before you install the central site system onto a target system

Distributing license information