ERserver. System Manager Use. iseries. Version 5 SC

Transcription

1 ERserer iseries System Manager Use Version 5 SC

2

3 ERserer iseries System Manager Use Version 5 SC

4 Note Before using this information and the product it supports, be sure to read the information in Notices on page ix. Third Edition (August 2002) This edition replaces SC This edition applies only to reduced instruction set computer (RISC) systems. Copyright International Business Machines Corporation 1997, All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ii Notices ix Programming Interface Information x Trademarks x About System Manager Use (SC ) xiii Who should read this book xiii Conentions and terminology used in this book xiii Prerequisite and related information xiii iseries Naigator xi How to send your comments xi Summary of Changes x Chapter 1. Setting Up for System Manager Preparing to set up your serers Supporting systems at different release leels.. 4 Planning for storage space Mapping the steps for setting up Using Adanced Peer-to-Peer Networking (APPN) 7 Distributing PTFs using change management.. 8 Naming the systems in your network Using alert support Distribution using SNADS Verifying contact information Setting up a serer as a serice proider Installing Managed System Serices on a serice proider Configuring Managed System Serices Starting Managed System Serices Installing System Manager on a serice proider.. 16 Configuring System Manager on a serice proider Security considerations Setting up serice support for a serice proider.. 18 Setting the serice proider attributes Setting up the list of serice requester serers.. 19 Setting up product support Working with supported products (WRKSPTPRD command) Starting System Manager Starting Manager Serices Setting up a serer as a serice requester and a managed system Installing Managed System Serices on a serice requester Starting Managed System Serices Setting up a list of serice proiders Resoling problems Verifying the network setup Example networks iseries example network Setting up System Manager System/370 and iseries Example Network Setting up System Manager with Host System/ Chapter 2. Product packaging concepts 37 Prepackaging considerations Marketing and deliery The application enironment Maintenance Deelopment Process National language support Dynamic naming Dynamic naming restrictions Multiple releases and repackaging considerations.. 42 Packaging libraries, folders, and directories Product deelopment, testing, and usage modes.. 43 Establishing a deelopment enironment for directories Storing document library objects in auxiliary storage pools Working with database files Packaging a follow-on release Repackaging considerations Chapter 3. Packaging your products.. 47 OS/400 release considerations Product packaging restrictions Step 1: Creating a product definition Product example: Creating a product definition 50 Step 2: Creating a product load Product example: Creating a product load Packaging products that hae more than one library Packaging products that hae folders and documents Example of packaging a product by using folders 57 Packaging products that hae directories Understanding national language loads for your product Step 3: Packaging products that hae exit programs 72 Preoperation exit program Postoperation exit program Step 4: Creating message files and messages Step 5: Marking the objects for packaging Product example: Marking objects for packaging 78 Step 6: Packaging your product option Product example: Packaging your product option 82 Step 7: Saing and restoring your product Saing Your License Program Restoring your license program Step 8: Checking your product structure Product packaging summary Commonly asked product packaging questions.. 89 Copyright IBM Corp. 1997, 2002 iii

6 Chapter 4. Packaging products for licensing Oeriew of license management Planning Ordering process changes License term strategy Type of compliance regulations to enforce Usage types Release considerations Packaging user-based priced products Defining features Adding license information License information options Creating a license key Application program interface (API) calls Requesting a use of the license Releasing a use of the license Compliance considerations Authority considerations Requesting a use of the license examples Concurrent use example Registered use example Chapter 5. Product installation, distribution, and management Saing licensed programs Installing a packaged product Aoiding library name conflicts at installation time 112 Testing an installed product Distributing your product Sending a Product Installing a remote product Product backup and recoery considerations Problem analysis for an installed product Chapter 6. Using the program temporary fix (PTF) functions Oeriew of change management on an OS/400 serice proider Work with supported products (WRKSPTPRD) command Ordering program temporary fixes (PTFs) Ordering the PTFs that you need Automatically ordering the PTFs that you need from IBM serice support Special PTF notifications Receiing program temporary fixes (PTFs) Checking for prerequisite and corequisite PTFs 122 Receiing PTFs from IBM serice support electronically Receiing PTFs from OS/400 serice proiders electronically Receiing PTFs from distribution media Working with PTF sae files PTF coer letters Working with coer letters Work with PTF commands Work with Program Temporary Fixes (WRKPTF) Command Working with assigned PTF IDs Change the PTF range Display Program Temporary Fix (DSPPTF) command Testing PTFs before distribution Releasing preiously held PTFs for distribution 132 Deleting sae files, coer letters, and on-order status Cleaning up unnecessary PTF objects Distributing PTFs Sending PTFs to another site Working with PTFs remotely Creating PTF packages Cumulatie PTF packages Chapter 7. Sericing your products using System Manager Serice information for the product owner Getting your system ready to create PTFs Creating a program temporary fix Assigning an identification name to your program temporary fixes Establishing libraries for your program temporary fixes Replacing and adding objects to your product using program temporary fixes Establishing dependencies on other PTFs Preparing PTF coer letters Searching the problem log Using program temporary fixes to change documents inside folders Using program temporary fixes to change stream files inside directories Deeloping PTF exit programs to eliminate manual operations Displaying details about a program temporary fix Applying a program temporary fix Testing PTFs Rebuilding PTFs Backup and recoery of PTF information Distributing PTFs Product user information for PTF deelopers Analyzing problems Installing PTFs Saing and restoring PTFs Cleaning up PTF information Chapter 8. Working with the Problem Log Using the problem log commands Work with Problem (WRKPRB) command Display Problems (DSPPRB) command Change Problem (CHGPRB) command Delete Problem (DLTPRB) command Working with a problem Analyzing a problem Reporting a problem Running recoery procedures for a problem Verifying a problem is corrected Answering a problem i System Manager Use V5R2

7 Sending a response for a problem Closing a problem Collecting authorized program analysis report (APAR) data Displaying authorized program analysis report (APAR) data Sae authorized program analysis report (APAR) data Delete authorized program analysis report (APAR) data Understanding problem status changes OPENED status READY status PREPARED status SENT status ANSWERED status VERIFIED status CLOSED status Status changes and operations Tracking problems Problem filtering Chapter 9. Detecting, analyzing, and reporting remote problems Detecting problems System-detected problems Application-detected problems User-detected problems Receiing problem notifications Automatic problem analysis Reporting problems detected by the system Serice requests as problem notifications Alerts as problem notifications Running remote problem analysis Starting remote problem analysis Completing problem analysis Possible causes lists Answering problems Software problems Hardware problems Reporting problems from the serice proider Problem analysis commands Work with Problem (WRKPRB) command Analyze Problem (ANZPRB) command Work with Alerts (WRKALR) command Verify Communications (VFYCMN) command 195 Verify Tape (VFYTAP) command Problem management APIs Chapter 10. Controlling operations centrally Creating a change request description Adding actiities to change request descriptions 199 Scheduling actiities Conditioning Node list or node names Standard names ersus global names Text Description Defining your own actiity types Exit program data How exit programs are called Displaying CRQ description actiity details Displaying nodes Displaying conditions End code definitions Displaying type specific data Submitting change requests What happens if the request does not run Actiity considerations Tracking submitted change requests Working with submitted change requests Combining more than one actiity into one change request description Printing the change request description Submitting the reised change request Accessing fast path distribution commands Managed systems node list (NODL) Managed system node names (CPNAME) Sending a license Supported OS/400 object types for object actiities 224 Distributing installable objects Using global names with CRQ actiities Using component names with CRQ actiities Commands associated with change requests Cleaning the change request database Using commands on remote systems Displaying output Diagnosing problems with change request processing System Manager is not started Managed System Serices is not started QSNADS subsystem is not started at the central site system SVDS distribution queue is not created Attempt to send remote command failed Appendix A. Programming and Command Reference Appendix B. Example setup and configuration of an OS/400 network using SNADS Using Systems Network Architecture distribution serices (SNADS) Creating directory entries Setting up SNADS for object distribution Verifying SNA distribution serices (SNADS) configuration Creating directory entries on the serice requester 238 Creating directory entries on the serice proider 239 Matching parameter alues for setting up the iseries serers Setting up communications on the serice proider 240 Changing the network attributes Line, controller, and deice descriptions on the serice proider SNADS definitions on the serice proider Setting up the list of serice requesters Setting up communications on the serice requester Contents

8 Changing the network attributes for a serice requester Line, controller, and deice descriptions on serice requesters SNADS definitions on the serice requester Setting up the serice requester for OS/400 serice proider support Setting up the list of serice proiders Creating a user profile for remote problem analysis Granting object authority on the serice requester Changing system alues on the serice requester Setting up another serice requester Example work sheet Appendix C. Examples of problem situations General assumptions about attributes Alert reported a system-detected problem Serice request reported a system-detected problem User-detected performance problem PTF order and distribution Detailed examples of problem situations Hardware serice request report User-detected performance problem Application-detected field alue problem Alert reported printer problem Send PTF Order (SNDPTFORD) from a serice requester When things do not work correctly Problem records not created when alerts are receied Problem records not created when serice requests are receied Cannot find messages on the serice proider 273 PTFs not sent PTFs sent but neer arrie PTF applied by serice proider does not sole the problem Takes a long time to add product support by using Work with Supported Products command. 275 Cannot do remote problem analysis Serice requester is not entitled Appendix D. Example product exit programs Appendix E. System Manager APIs and exit programs Change Request APIs Add Change Management Actiity (QNSADDCM) API Authorities and Locks Required Parameter Group Optional Parameter Group Usage Notes Error Messages Send Change Request Message (QNSSNDCM) API 303 Authorities and Locks Required Parameter Group Error Messages Update Status (QNSUPDST) API Authorities and Locks Required Parameter Group Error Messages Add Actiity Exit Program Required Parameter Group Notes Error Messages Change Actiity Exit Program Required Parameter Group Error Messages Display Actiity Exit Program Required Parameter Group Error Messages Run Actiity Exit Program Required Parameter Group Error Messages Action Value List Parameter Descriptions Other APIs Used with Products Appendix F. Commands shipped with public authority *Exclude Appendix G. Authority required for objects used by commands Appendix H. Authority to System Manager commands and APIs Appendix I. User profile database file 355 User profile database logical file (QASVNUP) Appendix J. QSVSM user profile default alues Bibliography Bibliography Systems Management Software Management Communications and Network Planning System Operation National Language Support iseries Access information NetView Distribution Information Backup and Recoery Security Information Index i System Manager Use V5R2

9 Figures 1. Map of Commands for Setting Up System Manager An iseries Network with System Manager Installed Two iseries Networks Serice Proiders Network Attributes for Alert Support Serice Proider Attributes SYSA1 and SYSA2 Network Attributes for Alerts A System/370 or System/390 with an iseries Network Serice Proiders Network Attributes for Alert Support Creating a Product Example, Step Product Example, Step Packaging a Product with Folders Packaging a Product with Directories Product Objects for a Product Installed on Two Systems Product Example, Step Product Example, Step Defining Features Using the CRTPRDDFN and CRTPRDLOD Commands Adding License Information Application Program Interface (API) Calls IBM Query Output Operations Aailable for a Problem in OPENED Status Operations Aailable for a Problem in READY Status Operations Aailable for a Problem in PREPARED Status Operations Aailable for a Problem in SENT Status Operations Aailable for a Problem in ANSWERED Status Operations Aailable for a Problem in VERIFIED Status Communications Flow for Problem Management Central Site System and Managed Systems Send SMG Object (SNDSMGOBJ) An Example OS/400 Network Matching Command Parameter Values Communications Flow for Alert Reported Problem Serice Request Reported System-Detected Problem A User-Detected Performance Problem A Send PTF Order and Distribution Operations for System-Detected Hardware Problem Operations for a User-Detected Performance Problem Operations for a Printer Problem Operations to Send a PTF Order and Distribution Example of Action Value List Copyright IBM Corp. 1997, 2002 ii

10 iii System Manager Use V5R2

11 Notices This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other locations. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user s responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation 500 Columbus Aenue Thornwood, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your area or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other location where such proisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are proided for conenience only and do not in any manner sere as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created Copyright IBM Corp. 1997, 2002 ix

12 programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Software Interoperability Coordinator 3605 Highway 52 N Rochester, MN U.S.A. Such information may be aailable, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement or any equialent agreement between us. All statements regarding IBM s future direction or intent are subject to change or withdrawal without notice, and represent goals and objecties only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on arious operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of deeloping, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of deeloping, using, marketing, or distributing application programs conforming to IBM s application programming interfaces. Programming Interface Information This publication is intended to help you to complete systems management tasks. This publication documents General-Use Programming Interface and Associated Guidance Information proided by System Manager for iseries licensed program. General-Use programming interfaces allow the customer to write programs that obtain the serices of System Manager for iseries licensed program. Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other locations, or both: Adanced Function Printing Adanced Peer-to-Peer Networking Adanced 36 AFP x System Manager Use V5R2

13 AIX AnyNet Application System/400 APPN AS/400 AS/400e C/400 e (logo) iseries iseries 400 IBM NetView Operating System/2 Operating System/400 Operational Assistant OS/2 OS/400 PS/2 Redbooks RISC System/6000 RS/6000 SAA SystemView System/36 System/370 System/38 System/390 Systems Application Architecture S/370 S/390 WebSphere 400 Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other locations, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other locations, or both. UNIX is a registered trademark of The Open Group in the United States and other locations. Other company, product, and serice names may be trademarks or serice marks of others. Notices xi

14 xii System Manager Use V5R2

15 About System Manager Use (SC ) Who should read this book This book proides a description of how to: Set up and manage a network of systems including application software management, data distribution, centralized operations, and centralized problem management. Package and manage your own products. This book assumes that you hae installed your systems and configured your network using Adanced Peer-to-Peer Networking (APPN). It is also assumed that you hae installed the System Manager licensed program on each appropriate system in your network. This book is intended for the following groups of users: Application deelopers who want to package and manage their own products in the same manner IBM products are managed. Central site network operators responsible for planning and maintaining a network of IBM serers. An understanding of communications configuration, APPN, and Systems Network Architecture distribution serices (SNADS) is assumed. Conentions and terminology used in this book This book refers to packaging a product as the process of conerting your application into a product that contains hierarchical structures. Packaging allows your product to exist in library, folder, or directory structures. Product home directories and product directories are new for the directory types to which you are packaging your product. Prerequisite and related information Use the iseries Information Center as your starting point for looking up iseries and AS/400e technical information. You can access the Information Center two ways: From the following Web site: From CD-ROMs that ship with your Operating System/400 order: iseries Information Center, SK3T This package also includes the PDF ersions of iseries manuals, iseries Information Center: Supplemental Manuals, SK3T , which replaces the Softcopy Library CD-ROM. The iseries Information Center contains adisors and important topics such as Jaa, TCP/IP, Web sering, secured networks, logical partitions, clustering, CL commands, and system application programming interfaces (APIs). It also includes links to related IBM Redbooks and Internet links to other IBM Web sites such as the Technical Studio and the IBM home page. With eery new hardware order, you receie the iseries Setup and Operations CD-ROM, SK3T This CD-ROM contains IBM Eserer iseries Access for Copyright IBM Corp. 1997, 2002 xiii

16 Windows and the EZ-Setup wizard. iseries Access offers a powerful set of client and serer capabilities for connecting PCs to iseries serers. The EZ-Setup wizard automates many of the iseries setup tasks. For related information, see the Bibliography on page 371. iseries Naigator IBM iseries Naigator is a powerful graphical interface for managing your iseries and AS/400e serers. iseries Naigator functionality includes system naigation, configuration, planning capabilities, and online help to guide you through your tasks. iseries Naigator makes operation and administration of the serer easier and more productie and is the only user interface to the new, adanced features of the OS/400 operating system. It also includes Management Central for managing multiple serers from a central system. How to send your comments For more information on iseries Naigator, see the iseries Information Center. Your feedback is important in helping to proide the most accurate and high-quality information. If you hae any comments about this book or any other iseries documentation, fill out the readers comment form at the back of this book. If you prefer to send comments by mail, use the readers comment form with the address that is printed on the back. If you are mailing a readers comment form from a location other than the United States, you can gie the form to the local IBM branch office or IBM representatie for postage-paid mailing. If you prefer to send comments by FAX, use either of the following numbers: United States, Canada, and Puerto Rico: Other countries or regions: If you prefer to send comments electronically, use one of these addresses: Comments on books: RCHCLERK@us.ibm.com Comments on the iseries Information Center: RCHINFOC@us.ibm.com Be sure to include the following: The name of the book or iseries Information Center topic. The publication number of a book. The page number or topic of a book to which your comment applies. xi System Manager Use V5R2

17 Summary of Changes Here is what has changed since V5R1: CL command descriptions and syntax diagrams moed to Information Center ( The chapters and appendixes that documented the System Manager GUI function were remoed. In V5R1 the password parameter changed to allow an increase in the password length from 10 to 128 characters for the following System Manager commands: Add Command Change Request Actiity (ADDCMDCRQA) Change Command Change Request Actiity (CHGCMDCRQA) Run System Manager Command (RUNSMGCMD) If the iseries serer is running with a password leel of 2 or 3, the password coming from the source iseries serer will not be known on the target system. The OS/400 licensed program and iseries Naigator proide support that allows you to manage PTF groups (or fix groups). At this time, the System Manager licensed program does not support PTF groups. The QALWOBJRST system alue enables security-sensitie objects to be restored during a PTF install when you specify *ALWPTF. Copyright IBM Corp. 1997, 2002 x

18 xi System Manager Use V5R2

19 Chapter 1. Setting Up for System Manager This chapter proides information and procedures to help you set up System Manager on the serers in your network. With the System Manager licensed program, you can organize systems management tasks to suit your business needs. The needs of your business change, sometimes sooner than you expect. To respond to business changes effectiely, your serers must change too. Managing your serers, at first glance, might seem like just another time-consuming job. But the systems management inestment pays off soon in the form of an efficient serer. It is efficient because changes are planned and managed. This means you can control operations from one site, a central site, within a network. Using operations management products, being in control of serers no longer means that you hae to be at those serers; you can control many operations on many serers from one place. Centralized control of operations also enables better tracking of functions performed on the serer. Products that manage OS/400 operations centrally include: System Manager for iseries (5722-SM1) Managed System Serices for iseries (5722-MG1) A central site system is the system in the network that controls network operations. From the central site system, skilled operators control the other serers in the network. These other serers are called managed systems. A managed system is a system that is managed by operators at the central site. The serice proider is a central site system that handles all the problems for the network. The serice requester is any system in the network that has a problem and requires serice. An OS/400 business computing system with the System Manager licensed program installed has the ability to be a serice proider for a group of serice requesters in a network. More than one OS/400 serice proider may be in a network. For System Manager serice proiders to manage resources, they must interact with a set of serice requesters. A serice requester is a system with a program or equipment problem that requires and asks for problem-handling support from another system in the network that is acting as a serice proider. To request serice from an OS/400 serice proider, a system must be defined on the serice proider as a serice requester. An iseries serer is a serice requester wheneer the operator or the system sends an alert, a serice request, or a PTF order. Preparing to set up your serers Before you set up System Manager, you need to erify that you hae enough disk storage space to store the PTF sae files you need to proide serice and support, that communications are properly set up, and that the contact information on each system in the network is current. The following sections describe the aspects of software release leel compatibility, storage space, and communications that you need to consider. Copyright IBM Corp. 1997,

20 Before you set up System Manager, you need to look at the characteristics of your serer and your network. The following items that you need to consider are described in the chapters of this book. It is assumed that you hae installed the System Manager licensed program before you begin using the procedures for setting it up. See Installing System Manager on a serice proider on page 16 for additional information about installing the System Manager program. You need Managed System Serices installed at the central site system to use the distribution and installation functions. See Installing Managed System Serices on a serice requester on page 26 for additional information about installing the Managed System Serices program. A serice proider must be running the same or higher release leel of the Operating System/400 program as the serice requesters. This enables the serice proider to proide support for serice requesters running at the same release leel or a preious release leel. Verify that the appropriate release leel is supported. Ealuate the storage requirements Consider what is necessary to use Adanced Peer-to-Peer Networking (APPN ). System Manager is dependent on the use of the Adanced Peer-to-Peer Networking (APPN) function for its serice proider and serice requester support. Using the AnyNet support proided in OS/400, System Manager can perform software distribution and installation in TCP/IP networks as well. Configure the central site system Managed system attributes and configuration alues that affect the entire operation of the managed system must be specified before you begin using Managed System Serices. The central site system and all systems in the network must install the Managed System Serices licensed program to allow communication within the network. Determine how your network uses alert support Another aspect of problem management you should look at before you set up System Manager is whether or not you are currently using OS/400 alert support. Alerts are records sent to a focal point to identify a problem or an impending problem. Set up your network to use Systems Network Architecture distribution serices (SNADS) System Manager uses SNADS to distribute software and to control software installation. System Manager is dependent on some SNADS requirements. A SystemView Distribution Serices (*SVDS) distribution queue is needed on the central site system for each managed system that is supported. This queue is created automatically when the managed system is added as a serice requester. If you do not configure a managed system as a serice requester, then a queue will need to be added manually using the Add Distribution Queue (ADDDSTQ) command. You use the SystemView Distribution Serices to send and receie distributions to managed systems in a network from a central site system. Each managed system should be defined as if it was directly connected to a central site system either logically or physically. Configuring supporting products The Work with Supported Products (WRKSPTPRD) command allows you to specify the list of products, product options, and language features for which you are willing to process serice requests and PTF orders. Using the OS/400 2 System Manager Use V5R2

21 program a serice proider can proide support only for certain releases. You can use the Release (RLS) parameter to specify the release with which you want to work. As new products are purchased and installed by your serice requesters, you must use this command on your serice proiders to indicate if they will support (supply serice for) this new product. This is also true as new release leels of products or product options are installed by your serice requesters. It is a good idea to run this command as new licensed programs are installed to ensure product support for your network of systems is current and correct. Also, if you want to be able to receie PTFs at your serice proiders, the products they are associated with must be either installed or supported. Verify the contact information The final preparation before you set up System Manager is to erify both your local contact information and the contact information on the remote serers in your network. Contact information is included in a problem record when you send a serice request or PTF order. Contact information is used by the serice proider (or IBM serice support) to identify the source of the request. The contact information includes the name, mailing address, and telephone number of the person to contact at your location when a problem occurs. You can also use the Work with Contact Information (WRKCNTINF) command on the OS/400 system. See Verifying contact information on page 14 for more information. Verify that System Manager is ready to use by using Send Serice Request (SNDSRVRQS) command with the *TEST parameter to erify that the systems are set up correctly. Verify that Managed System Serices is configured on the managed systems in your network. An iseries serer, acting as a serice requester only, does not need to hae System Manager installed to request serice from an OS/400 serice proider. Howeer, both systems must be properly configured for communications, using Adanced Peer-to-Peer Networking (APPN) and SNADS, and be set up so that the serice proider can effectiely use the functions proided by the System Manager licensed program. Additional preparation information for setting up your systems using SNADS is in Appendix B, Example setup and configuration of an OS/400 network using SNADS on page 235. System Manager is a user-based priced product. With System Manager a user is a remote serer that is managed. These include remote iseries serers, remote serers such as RISC System/6000 serers, and remote workstations such as PS/2 s. For more information about user-based priced products, see Chapter 4, Packaging products for licensing on page 93. Table 1 shows the products required for each task you want to do. Table 1. Required OS/400 Products by Task Task Package applications into products OS/400 Products Required Central Site System Managed System System Manager Managed System Serices X Managed System Serices Chapter 1. Setting Up for System Manager 3

22 Table 1. Required OS/400 Products by Task (continued) Task OS/400 Products Required Central Site System Managed System System Manager Managed System Serices X X Managed System Serices Report problems Track problems Analyze problems on X managed systems Distribute PTFs X X X Distribute products X X X Prepare products and package installable objects for distribution X 1 X 1 Distribute files X X X Install products X X X Load and apply PTFs X X X Run programs on X X X managed systems Perform IPL to X X X managed systems Run commands on X X X managed systems Install installable X X X objects Uninstall installable X X X objects Distribute license X X X keys Note: 1 Managed System Serices can be on either the central site system or the managed system. Supporting systems at different release leels If you are upgrading your systems to the current release of the Operating System/400 program and installing System Manager, you may need to do some backup and recoery procedures on the serice proider, both before and after the installation of the new release. See the Software Installation book for more complete information about upgrading the systems in your network and installing the System Manager licensed program. System Manager allows a serice proider to perform problem management and change management tasks for serice requesters that are running either the current or a preious release of the OS/400 program. The exception to this is a change in the modification leel of the operating system. Table 2 on page 5 shows the release leel requirements supported by serice proiders for the OS/400 licensed program. The serice and support for the serice 4 System Manager Use V5R2

23 requester is proided by an System Manager serice proider running a certain release of System Manager. Table 2. Serice Proider Release Support Table Serice Proider Release Leel V4 R4 M0 V4 R5M0 V5 R1 M0 V5 R2 M0 V4 R4 M0 X X X X V4 R5 M0 X X X X V5 R1 M0 X X X X V5 R2 M0 X X X X Note: X = Releases that are supported = Releases that are not supported Note: If your serer is the serice proider and you intend to support serers running both the current and preious releases of the OS/400 program, your serer must be at the highest release leel of all the serers in the network. To control the network efficiently, it is suggested that you use Managed System Serices with System Manager. When you configure the managed systems that hae Managed System Serices installed, you use configuration alues that affect the entire operation of the managed system. These alues specify: Whether to accept or reject actiities receied from the central site system. The security program that is run to determine which actiities to accept, which user profile to use when processing actiities, and which authorization list to use to secure distribution repository objects. The default user profile to use when processing actiities. The time-out alues for jobs waiting to process actiities. Whether to send intermediate responses to the central site system. The prefix tokens that specify how automatic global-to-local name mapping should be done. The remote command attributes such as: Remote command security program Maximum return data Delete spooled file Remote command key The user profile on the central site system that has authorization to the user profile database may be able to iew user profile information for user profiles that he or she does not hae authority to iew on the actual systems where the user profile resides. To ensure proper security, you hae the capability to encode passwords when working with user profiles. You can use a journal to monitor changes to the file, if you are concerned about changes to the user profile database. A distribution queue of type *SVDS is required for each central site system from which the managed system will receie requests. Chapter 1. Setting Up for System Manager 5

24 Planning for storage space System Manager assumes you will store program temporary fix (PTF) sae files on the serice proider. These files must be kept for a period of time to proide effectie serice. Adequate disk space is required to store the PTF sae files. The best way to minimize the amount of disk space used by PTF sae files is to be sure all the systems in your network hae applied the latest cumulatie PTF package before setting up System Manager. Doing this assures you that all your systems hae the most current leel of software installed and lessens the number of PTFs you need to order for correctie maintenance. If you follow this recommendation, you should allow approximately 20MB of disk storage for the anticipated IBM PTF sae files for a single release. You must also anticipate the amount of disk storage required for fixes (PTFs) for application software. If you do not apply the latest cumulatie PTF package to all the serers in your network, you may require more than this amount of disk space. See Oeriew of change management on an OS/400 serice proider on page 115 for more information about cumulatie PTF packages and change management strategy. If you hae a large number of serice requesters for which you intend to proide support, the serice proider problem log and alert log can become large. Periodic maintenance, such as closing and deleting problems and deleting alerts, is necessary to consere storage. To clear the disk space, you need to either use the cleanup functions aailable with the Operational Assistant function (type GO MANAGESYS on any command line), or you can periodically reorganize the physical files that are associated with the problem and alert logs. For more information about problem log maintenance, see Delete Problem (DLTPRB) command on page 162. For more information about alert log maintenance, see Maintaining the alert log on page 12. Mapping the steps for setting up The map of commands shown in Figure 1 on page 7 is an oeriew showing the commands you may use when preparing for and setting up System Manager. Follow steps 1 through 4 to set up communications and alert support. These topics are coered in depth in the Information Center: APPN support, which is aailable in the Networking topic. Alerts support, which is aailable in the Networking topic. Follow steps 5 through 9 to set up System Manager. The step numbers are noted in reerse image in the text with the corresponding procedure. An example of the commands and displays used to set up an OS/400 network and the System Manager licensed program is proided in Appendix B, Example setup and configuration of an OS/400 network using SNADS on page 235. Throughout this chapter, references are made to this example so that you can look at the procedures in a network enironment as you set up your systems. 6 System Manager Use V5R2

25 Figure 1. Map of Commands for Setting Up System Manager Using Adanced Peer-to-Peer Networking (APPN) System Manager is dependent on the use of the Adanced Peer-to-Peer Networking (APPN) function for its serice proider and serice requester support. APPN proides data communications support that routes data in a network between two or more systems that do not need to be adjacent. For a system to proide effectie serice, connectiity between the serice proider and serice requesters in the network must be possible using APPN. If the serice proider is going to run remote problem analysis and distribute PTFs to a serice requester, the serice proider must be able to call the serice requester. Chapter 1. Setting Up for System Manager 7

26 Before you begin setting up a system as a serice proider, you should check some of the characteristics of the system and the network. Because the use of APPN is assumed, you need to hae appropriate line and controller descriptions according to the communications protocol you are using. See Line, controller, and deice descriptions on the serice proider on page 241 and Line, controller, and deice descriptions on serice requesters on page 248 for examples of setting up communications in an iseries network. For more information on setting up these descriptions, see the Networking topic in the Information Center for the following information units: APPN Communications configuration ISDN support LAN, Frame-relay, and ATM support X.25 network support You may also need to update the network attributes and possibly the APPN remote configuration list that is associated with your system. These checks correspond with step 1, in Figure 1 on page 7. The APPN mode #INTER is used for communications between a serice requester and a serice proider, specifically for sending serice requests and performing remote problem analysis. The APPN mode #INTER is shipped with the iseries serer and must be configured on all the systems in the network. If your iseries serer communicates through a network control program (NCP), you must add #INTER to the network control program log mode table. Note: It is recommended that you use line descriptions other than the ones shipped for communications with IBM serice support (QESLINE) and IBM Marketing support (QTILINE) for communications between the serice proider and the serice requesters. You should create separate communications objects (line, controller, and deice descriptions) een if the same physical line will be used. For switched line configurations, you must ary on the communications line and controller before sending a serice request from a serice requester to a serice proider. Distributing PTFs using change management Once your system is configured, you should decide how to handle PTFs. You can use the fast path commands to distribute PTFs or create a change request description to do seeral operations and schedule them at specific times. For more details about the commands, see Accessing fast path distribution commands on page 219. For more details about using a change request description, see Chapter 10, Controlling operations centrally on page 197. With the System Manager licensed program, you can send program temporary fixes (PTFs) to managed systems and retriee PTFs from the managed systems. You also hae the option to apply, remoe, and delete remote PTFs. Naming the systems in your network To simplify management of your network, you should follow a naming pattern for the names of systems, network IDs, control points, and locations. Looking at the topology of your network can help with this. To aoid confusion when trying to identify which system or system description you are working with, use the same 8 System Manager Use V5R2