TME 10 for AS/400 Endpoints Release Notes. Version 3.6

Transcription

1 TME 10 for AS/400 Endpoints Release Notes Version 3.6 September 1998

2

3 TME 10 for AS/400 Endpoints Release Notes (September 1998) Copyright Notice Copyright 1998 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, AS/400, IBM, OS/2, OS/400, RISC System/6000, Tivoli Management Environment, TME 10, TME 10 Application Development Environment, TME 10 Framework, TME 10 Enterprise Console, TME 10 Inventory, TME 10 Software Distribution, TME 10 Software Distribution AutoPack, UserLink for TME 10 Software Distribution. Microsoft, Windows, Windows NT, and the Windows 95 logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others. Notice References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli Systems or IBM s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York

4

5 TME 10 for AS/400 Endpoints Release Notes System Requirements... 2 AS/400 Hardware Requirements... 2 Disk Space Required to Install AS/400 Endpoints... 3 Disk Space Required to Install Gateway Components... 3 Disk Space Required to Install Server Components... 4 Software Requirements... 4 Required TME 10 Product Installations... 5 Optional TME 10 Product Installations... 6 Client Access/400 Installation... 6 Installation Requirements... 7 AS/400 Patch Installation Prerequisites... 7 Installation Summary Installing AS/400 Endpoints Extending the Inventory Configuration Repository Schema for PTFs Installing the TME 10 Object Packaging Utility for AS/ Installing Internationalization Support Removing Endpoint Code from AS/400 Systems Removing TME 10 Object Packaging Utility for AS/ Version 3.6 Software Defects, Limitations, and Workarounds AS/400 Endpoints TME 10 User Administration for AS/400 Endpoints TME 10 Security Management for AS/400 Endpoints TME 10 Distributed Monitoring for AS/400 Endpoints TME 10 Software Distribution for AS/400 Endpoints TME 10 Object Packaging Utility for AS/ Product Notes TME 10 User Administration for AS/400 Endpoints TME 10 for AS/400Endpoints Release Notes i

6 TME 10 Security Management for AS/400 Endpoints...28 TME 10 Software Distribution for AS/400 Endpoints...28 TME 10 Distributed Monitoring for AS/400 Endpoints...28 OS/400 System Monitoring Collection...31 OS/400 Subsystem Monitoring Collection...31 OS/400 Job Monitoring Collection...31 OS/400 Disk Monitoring Collection...39 OS/400 Object Monitoring Collection...43 OS/400 Async Monitoring Collection...43 OS/400 Bisync Monitoring Collection...44 OS/400 Ethernet Monitoring Collection...46 OS/400 Token Ring Monitoring Collection...47 OS/400 IDLC Monitoring Collection...48 OS/400 ISDN Monitoring Collection...48 OS/400 SDLC Monitoring Collection...49 OS/400 X25 Monitoring Collection...50 ii Version 3.6

7 1Release Notes With the Version 3.6 release, Tivoli Management Environment 10 (TME 10) provides support for AS/400 endpoints in the Tivoli Management Region. The TME 10 Framework and selected TME 10 applications can be configured and used to manage a wide variety of system resources on AS/400 systems in a TME 10 environment. This Release Notes document provides important information about TME 10 for AS/400 Endpoints, Version 3.6. These notes are the most current information for the product and take precedence over all other documentation. Please review these notes thoroughly before installing or using this product. These release notes include the following topics: System Requirements Installation Requirements Version 3.6 Software Defects, Limitations, and Workarounds Product Notes Tivoli frequently updates the Tivoli Customer Support home page with new information about configuring and using Tivoli products. This information includes the following: Updated versions of these release notes Updated versions of Tivoli documentation Searchable support databases Additional product patches Access to training schedules Visit the site for this information and additional customer services. After you link to and submit the customer registration form, you will be able to access these services on the Web. TME 10 for AS/400 Endpoints Release Notes 1

8 System Requirements You will notice that both Tivoli and TME 10 are used in our sales, marketing, and product information materials. These terms are interchangeable. We will be removing references to TME 10 in future product releases. System Requirements This section describes the system requirements, including software and hardware, for each of the following resources in the TME 10 environment. AS/400 Hardware Requirements All TME 10 for AS/400 Endpoints products are supported for AS/400 CISC models running OS/400 Version 3 Release 2.0, and RISC models running OS/400 Version 3 Release 7.0 or higher. You must ensure that the following communication protocols are active in order to transfer files to and from AS/400 endpoints in the Tivoli network environment: TCP/IP communications ftp services The following tables list estimated disk space required to install all server, gateway, and endpoint code needed to use TME 10 for AS/400 Endpoints products. For information about supported interpreter types for servers and gateways in the TMR environment, see the TME 10 Framework Planning and Installation Guide and the TME 10 Framework Release Notes, Version Version 3.6

9 Disk Space Required to Install AS/400 Endpoints System Requirements The following table lists the estimated disk space required to install the endpoint code for the TME 10 Endpoint for AS/400 product on an AS/400 system. Note that you only need to install the binaries for the installed OS/400 interpreter type. Product Interpreter Type Binaries TME 10 Endpoints for AS/400 os400-v3r MB os400-v3r MB Disk Space Required to Install Gateway Components The following table lists the estimated disk space required to install the endpoint methods on gateways that will connect AS/400 endpoints to the TMR environment. Product Images Binaries Catalog TME 10 User Administration for AS/400 Endpoints TME 10 Security Management for AS/400 Endpoints TME 10 Distributed Monitoring for AS/400 Endpoints TME 10 Distributed Monitoring ARM for AS400 Endpoint TME 10 Software Distribution for AS/400 Endpoints 1.74 MB 0 MB 0 MB 4.85 MB 0 MB 0 MB 5.36 MB 0 MB 0 MB 0.63 MB 0 MB 0 MB 1.02 MB 0 MB 0 MB TME 10 Inventory for AS/400 Endpoints 2.15 MB 0.07 MB 0 MB TME 10 Task Library for AS/400 Endpoint 0.06 MB 0 MB 0.12 MB TME 10 for AS/400 Endpoints Release Notes 3

10 System Requirements Disk Space Required to Install Server Components The following table lists the estimated disk space required to install the server-side components for TME 10 for AS/400 Endpoints. Product Binaries Catalog TME 10 User Administration for AS/400 Endpoints TME 10 Security Management for AS/400 Endpoints 0.69 MB 0.02 MB 0.81 MB 0.08 MB Software Requirements You can install the following TME 10 products if you plan to use them to manage your network. If so, install each product before installing TME 10 for AS/400 support which is provided as a patch in Version 3.6: TME 10 User Administration, Version 3.6 Install this product if you plan to use Tivoli to manage AS/400 user accounts across your enterprise. TME 10 Security Management, Version 3.6 Install this product if you plan to secure a wide variety of network resources, including files, directories, terminals, and OS/400 objects. TME 10 Security Management for AS/400 Endpoints incorporates OS/400 s inherent security measures with Tivoli s security profiles and audit tasks to monitor network groups, resources, roles, and system-wide policies. 4 Version 3.6

11 System Requirements TME 10 Distributed Monitoring, Version 3.6 Install this product if you plan to monitor critical system resources and performance of the AS/400 s in your network. The set of AS/400 monitoring collections provide the same monitoring capabilities as the AS/400 Performance Monitor application plus the same function found in the AS/400 Work Management APIs that are built into the OS/400 operating system. Each collection contains several monitoring sources which allow you to manage different aspects of your network, such as system resources and network protocols. TME 10 Inventory, Version 3.6 Install this product if you plan to manage AS/400 inventory.you will be able to electronically scan for AS/400 hardware and installed AS/400 products as well as for Program Temporary Fixes (PTFs) on your AS/400 s. This will help you manage your assets and track your software throughout your enterprise. Your information is tracked in a database. Tivoli supports DB2, Sybase, Oracle, and Microsoft SQL. TME 10 Software Distribution, Version 3.6 Install this product if you plan to distribute AS/400 software. Used in conjunction with TME 10 Inventory, Software Distribution enables you to manage the deployment of new software products to all of your AS/400 s. Tivoli provides the TME 10 Object Packaging Utility for AS/400 to quickly and efficiently package AS/400 objects to be distributed. Required TME 10 Product Installations You must install the following TME 10 products on your management server before installing TME 10 for AS/400: TME 10 Software Installation Service, Version 3.6 TME 10 Framework, Version 3.6 You can upgrade from TME 10 Framework, Version 3.2 by installing the TME 10 Framework Upgrade to Version 3.6 patch. TME 10 for AS/400 Endpoints Release Notes 5

12 System Requirements Optional TME 10 Product Installations Install the following TME 10 products if you plan to use them to manage your network. If so, you must install each product in your TMR before installing TME 10 for AS/400 Endpoints: TME 10 Inventory, Version 3.6, to manage AS/400 inventory. TME 10 Software Distribution, Version 3.6, to distribute AS/400 software. You can also use the TME 10 Object Packaging Utility to create AS/400-specific file package blocks (fpblocks) for distribution to AS/400 machines. Note that if you use the TME 10 Object Packaging Utility for AS/400, you must ensure that Client Access/400 is installed on the Windows 95 or WIndows NT system on which you plan to package AS/400 software applications. TME 10 User Administration, Version 3.6, to use Tivoli to manage user and group accounts using TME 10 profiles. TME 10 Distributed Monitoring, Version 3.6, to monitor critical system resources and performance of the AS/400 s in your network. TME 10 Security Management, Version 3.6 to manage the security aspects of the AS/400 s in your network from one centralized source. Client Access/400 Installation Client Access/400 must be installed and configured on the Windows 95 or Windows NT PC if you plan to use the TME 10 Object Packaging Utility for AS/400 to prepare AS/400 file packages. Install the following versions of Client Access/400: 57xx-XW1 Client Access/400 Windows Family Base 57xx-XD1 Client Access/400 Optimized for Windows where xx is related to the version of the product you are installing. For more information about installing and using Client Access/400, refer to the product documentation that accompanies the Client Access/400 product. You may download this and other AS/400 documentation from the AS/400 library of manuals available at 6 Version 3.6

13 Installation Requirements The AS/400 reference library provides searchable online guides, AS/400 manuals and Redbooks, and other information about configuring and using AS/400 systems. Installation Requirements The following information describes AS/400-specific requirements for installing the TME 10 for AS/400 Endpoints products. See each application-specific user s guide for installation instructions and requirements for each TME 10 application. AS/400 Patch Installation Prerequisites You must satisfy the following requirements before installing the AS/400 patches: Install and configure TME 10 Framework. For information and procedures about setting up and using the Framework, see the TME 10 Framework Planning and Installation Guide. Install the TMR server and endpoint gateways with TME 10 Framework, Version 3.6. Install any optional TME 10 products on your TMR server as listed in Optional TME 10 Product Installations on page 3. The Tivoli for AS/400 CD-ROM (P/N LK3T ) contains all Tivoli products that support AS/400 systems, including the TME 10 Framework code needed on your TMR server, the endpoint code that runs on the AS/400, and code for the TME 10 applications that are supported on the AS/400. Application code will either be installed on the TMR server or the AS/400 endpoint. The Tivoli for AS/400 CD-ROM is shipped with the following Tivoli products: TME 10 Framework, Version 3.6 TME 10 Software Distribution, Version 3.6 TME 10 Inventory, Version 3.6 TME 10 Distributed Monitoring, Version 3.6 TME 10 User and Group Management, Version 3.6 TME 10 for AS/400 Endpoints Release Notes 7

14 Installation Requirements TME 10 Security Management, Version 3.6. The following directories located on the CD-ROM contain all necessary AS/400 install media to run this product: Directory PatchID Description /as4patch 3.6-TMF-0001 TME 10 Framework Gateway for AS/400 Endpoint, Version TMF ADM ADM SEC SEC-0002 TME 10 Task Library for AS/400 Endpoint, Version 3.6 TME 10 User Administration for AS/400 Endpoint, Version 3.6. This code contains the graphical user interface extensions for TME 10 User Administration. Note: Install the GUI extension only on the TMR server. Do not install on any managed node in the TMR. TME 10 User Administration Gateway for AS/400 Endpoint, Version 3.6. This code contains the methods supported by AS/400 systems. This product can be installed on any gateway that will serve AS/400 endpoints. TME 10 Security Management for AS/400 Endpoint, Version 3.6 and TME 10 Security Audit Reports for AS/400, Version 3.6. This code contains the graphical user interface extensions for TME 10 Security Management. Note: Install the GUI extension only on the TMR server. Do not install on any managed node in the TMR. TME 10 Security Management Gateway for AS/400 Endpoint, Version 3.6. This code contains the methods supported by AS/400 systems. This product can be installed on any gateway that will serve AS/400 endpoints. 8 Version 3.6

15 Installation Requirements Directory PatchID Description /as4patch 3.6-SEN-0001 TME 10 Distributed Monitoring for AS/400 Endpoint, Version 3.6. This code includes the engine and the probes code for the AS/400. Install this patch on any gateway that will serve AS/400 endpoints. 3.6-SEN COU INV-0001 TME 10 Distributed Monitoring ARM for AS400 Endpoint, Version 3.6. This code includes the Application Response Management API to monitor availability and performance transactions on AS/400 systems. Install this patch on any gateway that will serve AS/400 endpoints TME 10 Software Distribution Gateway for AS/400 Endpoint, Version 3.6. This code contains methods that are installed on the TMR gateway that run on AS/400 endpoints. TME 10 Inventory Gateway for AS/400 Endpoint, Version 3.6. This patch includes database schema scripts which are run on your database machine that are needed to customize your database for AS/400 PTF information. It also includes the AS/400 inventory methods and scanner code. Install this patch any gateway that will serve AS/400 endpoints. /obj_pack n/a TME 10 Object Packaging Utility for AS/400. Install this tool on any Windows PC on top os Client Access/400. /1tmelcf ES_os400_36 TME 10 Endpoint daemon for AS/400. Install this patch on AS/400 endpoints. /books n/a Postscript and pdf versions of TME 10 for AS/400 Endpoints User s Guide Notes: An AS/400 patch to enable Software Installations Services (SIS) is not required. TME 10 for AS/400 Endpoints Release Notes 9

16 Installation Requirements Installation Summary Donot install the 3.6-ADM-0001 and 3.6-SEC-0001 patches on managed nodes in the TMR. Installing the GUI extensions for TME 10 User Administration for AS/400 or for TME 10 Security Management for AS/400 on a managed node will corrupt the installation. When installing these patches on a Windows NT machine, if you list directory contents in a bash shell, all file and directory names appear in lowercase letters, such as tmf36002.ind. However, when installing the patch form the command line, you must specify the file name in uppercase letters, as shown in the following example command line prompt: bash$ wpatch -c D:/as4patch -i TMF36002.IND To install TME 10 Security Management for AS/400 Endpoints, you must have super and security_admin authority. The following steps outline the general installation procedures that must be completed before you install AS/400 components. AS/400-specific procedures follow the general instructions. According to the products that you plan to use to manage AS/400 endpoints, ensure that one or all of the following products are installed on your TMR server and endpoint gateways as described in the installation procedures for each product. TME 10 Software Installation Service, Version 3.6 TME 10 Framework, Version 3.6 TME 10 Inventory, Version 3.6 TME 10 Software Distribution, Version 3.6 TME 10 Distributed Monitoring, Version 3.6 TME 10 User Administration, Version 3.6 TME 10 Security Management, Version Version 3.6

17 Installation Requirements Complete the following procedure to install patches for your environment: 1. Apply each product patch to enable the AS/400 support. Tivoli strongly recommends that you use the TME 10 Software Installation Service to install all patches for TME 10 for AS/400 Endpoints. See the TME 10 Software Installation Service User s Guide for information about using this product to install AS/400 patches. 2. Customize your installation as needed. For example, you may want to complete the following installations: Install the patch for the AS/400 task library. Note that this step is useful if you are using the TME 10 Enterprise Console s AS/400 Message Adapter or AS/400 Alert Adapter. The task library helps automate actions on the AS/400 endpoint. Extend your Inventory configuration repository by running the scripts provided if you plan to scan AS/400 PTFs. Install the TME10 Object Packaging Utility for AS/400 if you plan to package AS/400 objects for later distribution using TME 10 Software Distribution. See Installing the TME 10 Object Packaging Utility for AS/400 on page 13 for an installation summary. For more information about installing the Object Packaging Utility, see the TME 10 for AS/400 Endpoints User s Guide. TME 10 for AS/400 Endpoints Release Notes 11

18 Installation Requirements Installing AS/400 Endpoints The TME 10 Software Installation Service (SIS) installs multiple TME 10 products on multiple systems in parallel, including AS/400 endpoints in the TMR environment. To install an AS/400 endpoint, you must select the correct interpreter type for the AS/400 machine on which you will install the Framework. Supported AS/400 interpreter types include the following: Interp Type Supported Platform os400-v3r2 For AS/400 CISC models with OS/400 at Version 3 Release 2 os400-v3r7 For AS/400 RISC models with OS/400 at Version 3 Release 7 or higher The w4inslcf.pl command is also available to install and optionally start an AS/400 endpoint daemon job on one or more AS/400 systems. Although Tivoli recommends that you use the SIS facility to install AS/400 endpoints, you must use the w4inslcf.pl command if you are installing the endpoint from a platform not yet supported by SIS. The /1tmelcf/install_sis/ directory contains the w4inslcf.pl command to install all endpoint code. Tivoli recommends that you run w4inslcf.pl from the /1tmelcf/install_sis directory. If you choose to copy and run the w4inslcf.pl command from a temporary directory, specify the path to the /1tmelcf/install_sis directory. For procedures to install an AS/400 endpoint using the w4inslcf.pl command, see the TME 10 for AS/400 Endpoints User s Guide. Extending the Inventory Configuration Repository Schema for PTFs The steps for installing database-specific scripts are documented in the TME 10 Inventory User s Guide. Refer to this manual for information about installing the configuration repository schema. Follow the appropriate steps to install the schema and then run the additional script required for AS/400 PTF support. Select the correct schema for your database from the following table and follow the 12 Version 3.6

19 Installation Requirements installation steps as the detailed in the TME 10 Inventory User s Guide: DB/2 Database Type Microsoft SQL Oracle Sybase Database Schema Script tivoli_db2_schema_as400_ptf.sql tivoli_ms_sql_schema_as400_ptf.sql tivoli_ora_schema_as400_ptf.sql tivoli_syb_schema_as400_ptf.sql Note: You must copy the appropriate script from the $BINDIR/TME/INVENTORY/SCRIPTS/RDBMS directory on the TMR server to a temporary directory on the RDBMS server. Installing the TME 10 Object Packaging Utility for AS/400 Using TME 10 Software Distribution file package technology, you can distribute and deploy software to AS/400 endpoints throughout the network. The TME 10 Object Packaging Utility for AS/400 creates AS/400-specific file packages to be used with TME 10 Software Distribution. Note: Client Access/400 must be installed and configured on the Windows 95 or Windows NT PC that you will be using to prepare AS/400 file packages. Ensure this PC is connected to the AS/400 source machine on which the software is stored. To install the TME 10 Object Packaging Utility for AS/400 on any Windows 95 or Windows NT 4.0 machine complete the following steps: 1. From the File Manager or Program Manager window, select Run... from the File menu to display the Run dialog. 2. Enter the path to the SETUP.EXE file, which resides in the X:\obj_pack directory on the CD-ROM, in the Open text field, TME 10 for AS/400 Endpoints Release Notes 13

20 Installation Requirements where X is the CD-ROM drive where the TME 10 for AS/400 CD-ROM image is inserted. 3. Press the OK button to run the setup program and display the Welcome dialog for the TME 10 Object Packaging Utility for AS/400. The setup program leads you through the TME 10 Object Packaging Utility for AS/400 installation. Use the Back, Next, or Cancel buttons to navigate through these option dialogs. The default location is automatically set to the C:\Program Files\Tivoli\ObjPackAS400\ directory. Press the Browse button to navigate through the directory structure and specify another directory if you want to set a different location. Press the Next button to continue the installation. 4. To start the Object Packaging Utility, double-click on the as4pack.exe icon from the ObjPackAS400 window or select the TME 10 Object Packaging Utility for AS/400 option from the Start -> Programs -> Tivoli menu. Installing Internationalization Support Tivoli provides the AS/400 endpoint code (AS/400 Licensed Program 1TMELCF) for the following languages. Code Primary Supported Languages 2924 English 2938 Upper case English 2928 French 2980 Brazilian Portuguese 2962 Japanese Note: If you install TME 10 for AS/400 Endpoints on a machine that supports one of the primary languages that are listed in the table, Tivoli automatically installs the AS/400 commands and help text for these commands. 14 Version 3.6

21 Installation Requirements However, if you install the TME 10 for AS/400 Endpoints product on a machine on which the primary language is different from the listed languages, Tivoli creates a language-specific library for each listed language, such as QTME2924 for English, QTME2938 for Upper case English, and so on. You must change your system library list to add the specific language, such as QTME29xx, before executing Tivoli commands. If the primary language is set to any of the listed languages on the AS/400 system, you can install a secondary language by running the following command: w4instlcf.pl -g gateway_name -N xxxx endpoint_name where xxxx is the code of the supported language that you wish to install, such as 2928 if you are installing support for French. Removing Endpoint Code from AS/400 Systems To remove the TME 10 endpoint code from AS/400 clients, complete the following steps: 1. Stop all Tivoli jobs or any other jobs that are started by Tivoli applications and are running on the endpoint. Note: Endpoint processes can include the lcfd daemon process as well as any jobs started by TME 10 applications. For example, you must stop the Distributed Monitoring engine and any monitor processes running on the endpoint. 2. Delete the license program by entering the following command: DLTLICPGM LICPGM(1TMELCF) TME 10 for AS/400 Endpoints Release Notes 15

22 Installation Requirements 3. Execute the following WRKOBJOWN commands on each Tivoli user account to display all objects owned by the specified user: WRKOBJOWN USRPRF(QTIVUSER) WRKOBJOWN USRPRF(QTIVROOT) WRKOBJOWN USRPRF(QTIVOLI) 4. The WRKOBJOWN command lists all objects that belong to a user. To prevent any listed object from being deleted, you must change the ownership of that object by selecting option 9 for the object from the Work with Objects by Owner window. Repeat this step for each object that you wish to save. 5. Delete the user account names by specifying the *DLT option to delete all objects owned by a user. The DLTUSRPRF commands must be entered in the following order: DLTUSRPRF USRPRF(QTIVUSER) OWNOBJOPT(*DLT) DLTUSRPRF USRPRF(QTIVROOT) OWNOBJOPT(*DLT) DLTUSRPRF USRPRF(QTIVOLI) OWNOBJOPT(*DLT) Notes: If you delete QTIVOLI before deleting other user accounts, some objects may not be deleted, and you may have problems reinstalling the TME 10 endpoint code in the AS/ Delete all files and subdirectories under the /QIBM/UserData/Tivoli/lcf directory. 7. Execute the following command: WRKLNK OBJ( /tmp ) DSPOPT(*ALL) 16 Version 3.6

23 Version 3.6 Software Defects, Limitations, and Workarounds Removing TME 10 Object Packaging Utility for AS/400 Complete the following steps to remove the TME 10 Object Packaging Utility for AS/400 from your Windows PC: 1. From the Start menu, select the Control Panel option from the Settings menu item to display the Control Panel window. 2. Double-click on the Add/Remove Programs icon to display the Add/Remove Programs Properties window. 3. From the Install/Uninstall property sheet, select TME 10 Object Packaging Utility for AS/400 from the scrolling list and press the Add/Remove button. 4. A Confirm File Deletion window is displayed. Confirm the removal operation by selecting Yes to proceed with the deletion or No to cancel. An Uninstall shield removes the product from the Windows PC if you select Yes. 5. Select the OK button when the uninstall is complete to return to the Add/Remove Programs Properties window. 6. Select the OK button on the Add/Remove Programs Properties window to complete the uninstall procedure. Version 3.6 Software Defects, Limitations, and Workarounds This section describes known defects and limitations in this release of TME 10 for AS/400 Endpoints. Defects are categorized by application component and are listed by their defect number and description. Where applicable and known, suggested workarounds are identified. For each defect a tracking number is assigned. TME 10 for AS/400 Endpoints Release Notes 17

24 Version 3.6 Software Defects, Limitations, and Workarounds AS/400 Endpoints 1. TME 10 Software Installation Service (SIS) or the w4inslcf.pl command fail to install an AS/400 endpoint if objects belong to QDFTOWN. PR WORKAROUND: Ensure that the Tivoli IFS home directory (/QIBM/UserData/Tivoli/lcf) and product library (QTMELCF) belong to the QTIVOLI user account, or that they are deleted from the systems before you reinstall the endpoint code on the AS/400 system. 2. For task execution, by default batch job scripts run under the QPGMR user account. PR WORKAROUND: Create a job description in which the user ID is set to the desired user and the batch job is changed to use the JOBD() parameter, as in the following example: //BCHJOB JOB(TEST) JOBD(MYLIB/MYJOBD) JOBQ(*JOBD) 3. Configuration path option for the STRTMEEPT command is ignored. PR The wadminep command cannot be used to upgrade the endpoint label variable. PR AS/400 Tasks Vary_Configuration command line is case sensitive. PR WORKAROUND: Use upper case characters for parameter information in the task. 6. The STRTMEEPT command may display the following extraneous log message that should be ignored: File file_name in library_name not a save file. PR The w4inslcf.pl command forces the use of the g option to install AS/400 endpoints. PR WORKAROUND: Specify a login interface IP address with the g parameter, as in the following example: w4inslcf.pl -v -g gateway_name+port endpoint_name 18 Version 3.6

25 Version 3.6 Software Defects, Limitations, and Workarounds TME 10 User Administration for AS/400 Endpoints 8. OS/400 passwords can only be 10 characters long. If a password is entered in the Common Password field, it is distributed as the AS/400 password. If that password is more than 10 characters long, there is no validation policy on the server that will catch the error. The creation or modification of the user on the AS/400 will fail at distribution time. PR The OS400_PassW attribute is marked as a controlled attribute via the wchgusrprop -c command, which means that a native OS/400 user account password will not be overwritten by a Tivoli user profile unless the OS400_PassW is explicitly changed. PR WORKAROUND: Change the OS400_PassW attribute from the TME 10 desktop, or run the wchgusrprop -c command on the Tivoli user profile after a populate operation, as follows: wchgusrprop OS400_PassW 10. Creating two or more profile records with different common_login names but with the same OS400_Login name and distributing this profile to an AS/400 endpoint causes only the first user account to be created and overwritten by the repeated OS400_Login name. PR The installation script for the 3.6-ADM-0001 patch to install GUI extensions for TME 10 User Administration for AS/400 exits if it encounters errors while adding the new OS400 attributes and dialogs. PR WORKAROUND: Check the add_os400_properties.output file in the /tmp directory for descriptions of any errors that may have occurred during installation. Tivoli recommends that you back up the TMR database before installing the 3.6-ADM-0001 patch. If you do encounter problems when installing this patch, such as corrupted profiles that the installation script cannot update using waddprop, restore the TMR database, check the add_os400_properties.output file to solve installation problems, back up the TMR database, and reinstall. TME 10 for AS/400 Endpoints Release Notes 19

26 Version 3.6 Software Defects, Limitations, and Workarounds 12. After installing the 3.6-ADM-0001 patch to install TME 10 User Administration for AS/400 Endpoints, records from any profile that was created prior to the installation of this patch cannot be copied. Attempts to copy the record will result in an error that states that the profile can not longer be changed. PR WORKAROUND: Provide values for the OS400 attributes to avoid assigning an empty string to the attribute. Also, you can modify the OS400V validation policy scripts to check validation first. Include the following code segment at the start of the script: if [ $1 = ] then echo TRUE fi 13. The validation policy for attribute OS400_Locale will fail when user profiles are populated from AS/400 endpoints running OS/400 V3R2M0 because Locale is not a valid attribute for OS/400 user profiles on V3R2M0. PR WORKAROUND: From the TME 10 User Administration profile, change the type of validation policy for attribute OS400_Locale to NONE. After the population is complete, enter the following command on the management server command line: wputpolm -v args=\$os400_locale \ OS400_Locale $bindir_path/os400v_ifs_path TME 10 Security Management for AS/400 Endpoints 14. When populating resource records for IFS stream files, the resource type is shown as IFS directory. PR WORKAROUND: None required, since the populated resource record can be distributed without affecting the operation of Security Management. However, you can add a new record that duplicates the information in the populated record in which the resource type is correctly set to Stream File, and then delete the populated record. 20 Version 3.6

27 Version 3.6 Software Defects, Limitations, and Workarounds 15. Populate of a resource record fails with an invalid ResAudit value, and the record is not added to the database. This only occurs for a resource in which success and failure auditing is activated. PR WORKAROUND: Temporarily turn off validation for ResAudit, populate and edit the record, and then enable the success and failure auditing. Ensure that the validation for ResAudit is re-enabled after you have edited this record. 16. Profile distribution fails if an invalid group name exists in Role records. PR WORKAROUND: Delete the current role record and create a new one. 17. Cannot create or edit a system policy record from the command line that specifies a value for the OS4Lockout attribute of the format x,y,z. PR WORKAROUND: Set the last two values for OS4Lockout to 0 and Forever when creating a record from the command line. 18. When editing a resource record from the Resource Record Properties window, deselecting all Access Rights checkboxes in the Resource Default Access window generates an error. PR WORKAROUND: Delete the resource record and recreate it, after which the default access permissions for this resource record are set to None. 19. When restricting access to a resource for a role to a specific date and time, or restricting a login time for a group, jobs are submitted on the AS/400 endpoint under job queue QBATCH to grant and revoke resource access and logins. Depending on the AS/400 configuration, the QBATCH job queue may be configured to only run one job at a time, and thus the grant and revoke of resource access or logins may not occur for a group as expected. PR TME 10 for AS/400 Endpoints Release Notes 21

28 Version 3.6 Software Defects, Limitations, and Workarounds WORKAROUND: On the AS/400 endpoint, enter the following command: DSPSBSD SBSD(QBATCH) Select option 6 from the menu. In the Job Queue column, locate QBATCH. The number of allowed active jobs for the QBATCH job queue is located in the Max Active column. To increase the maximum number of active jobs allowed for the QBATCH job queue, enter the following command CHGJOBQE SBS(*LIBL/QBATCH) JOBQ(*LIBL/QBATCH) MAXACT(x) where x is the maximum number of active jobs allowed. Alternately, you can enter *NOMAX to specify no maximum. 20. When adding users to groups and a TME 10 user created by TME 10 User Administration is specified as a member, the TME 10 user is not added to the group profile on the AS/400 endpoint. PR When profiles with very large numbers of records are distributed to AS/400 endpoints, an endpoint timeout may occur. This problem can also occur when setting default access on all objects of a certain object type in system policies. PR WORKAROUND: On the gateway system, enter the following TME 10 Framework command: wgateway gateway_name set_session_timeout timeout_value to increase the amount of time that the gateway allows the endpoint to execute the AS/400 endpoint methods. Note that this increases the amount of time that all methods are allowed to run in for all platforms. 22. After populating resource records from an AS/400 endpoint, the records will not be distributed to any AS/400 endpoint upon profile distribution. PR WORKAROUND: For each populated resource, edit the resource record and save it. The record will then be distributed upon the next profile distribution. 22 Version 3.6

29 Version 3.6 Software Defects, Limitations, and Workarounds 23. When specifying to populate a LIBRARY resource type from an AS/400 endpoint, the format of the resource name must be entered in the following form: /QSYS.LIB/library-name.LIB/. The LIBRARY resource will not be populated if the trailing backslash (/) is not included in the name. PR When distributing a profile that contains STREAM_FILE type resources that are defined with a wildcard character, such as /usr/testlib/* or /usr/testlib/abc*, both STREAM_FILE and DIRECTORY (subdirectories) resource types in the specified directory will have their access permissions or auditing values, or both, changed as dictated by the profile. PR WORKAROUND: Do not create resource records for STREAM_FILE type resources that contain wildcard characters. Instead, create a resource record for each individual resource, such as /usr/testlib/abc After distributing a profile to schedule resource authorizations, if resource role permissions are manually set to a higher authorization, for example from *USE to *CHANGE or from *CHANGE to *ALL, then these permissions are not reset to the correct authorization level until the permissions are revoked by the scheduled job. PR WORKAROUND: If you are manually changing permissions, you must reset authorization levels. 26. AS/400 DEVICE_DESCRIPTION resource types can only exist in library QSYS not in user libraries. Distributing profiles that contains system policy records that sets default access to all objects of a resource type only modifies AS/400 resources that exist in user libraries. Therefore, a distribution of a profile that contains system policy records that sets default access for DEVICE_DESCRIPTION resource types will have no effect on AS/400 endpoints. PR Specifying default access to LIBRARY resource types in a system policy will not change the permissions for any libraries on AS/400 endpoints. PR TME 10 for AS/400 Endpoints Release Notes 23

30 Version 3.6 Software Defects, Limitations, and Workarounds WORKAROUND: Create a resource record for each individual LIBRARY resource, and set access permissions for each resource record. 28. A distribution failure occurs when trying to modify an allocated resource on an AS/400 endpoint. Each subsequent distribution will fail until the resource is deallocated. This may occur when specifying default access to all FILE resource types in a system policy, depending on the AS/400 endpoint configuration. PR WORKAROUND: Deallocate the object specified on the AS/400 endpoint using the DLCOBJ command and redistribute the profile. TME 10 Distributed Monitoring for AS/400 Endpoints 29. An ARM daemon job fails to restart if the job is terminated suddenly or incorrectly. The ARM daemon may terminate unexpectedly if the job is ended via the ENDJOB command, the QSYSWRK subsystem is ended, or the system is restarted (IPL or reboot). The files in /tmp are not deleted, and the ARM job cannot start a new client daemon job. PR WORKAROUND: Use the WRKLNK command to delete the following files to restart a new ARM client daemon job: /tmp/arm*, /tmp/asx*, /tmp/asx*. 30. Executables or dependencies downloaded from the gateway to the endpoint may not be deleted from the endpoint when it is removed from the TMR. For example, the QTMELCFDM library and its objects, which are installed by TME 10 Distributed Monitoring for AS/400 Endpoints, are not deleted when the endpoint is removed from the TMR. PR WORKAROUND: Follows steps outlined in Removing Endpoint Code from AS/400 Systems on page 15 to properly delete libraries and objects from the AS/400 system. 24 Version 3.6

31 Version 3.6 Software Defects, Limitations, and Workarounds TME 10 Software Distribution for AS/400 Endpoints 31. Configuration programs and input files may not be properly installed in the destination directory or library when the install_progs keyword is set to y. PR Messages resulting from configuration program failures may not contain enough information to easily identify the problem. PR TME 10 Object Packaging Utility for AS/ When creating a file package block (fpblock) with the TME 10 Object Packaging Utility for AS/400, the Object Packaging Utility hangs if the network connection is terminated between the AS/400 system and the Windows PC on which you are creating the fpblock. PR WORKAROUND: Close the Object Packaging Utility, reestablish the network connection through Client Access/400, and recreate the file package block. 34. Because Client Access/400 is not supported on Windows NT, Version 3.5.1machines, you cannot use TME 10 Object Packaging Utility for AS/400 on these systems. However, installing the TME 10 Object Packaging Utility for AS/400 on a Windows NT system does not result in an appropriate error message. PR The TME 10 Object Packaging Utility for AS/400 icon is not removed when the Object Packaging Utility is deleted. The user must delete the icon manually through Windows Explorer. PR TME 10 for AS/400 Endpoints Release Notes 25

32 Product Notes Product Notes This section contains important information that you should consider while using the product. This information is provided to supplement information in the TME 10 for AS/400 Endpoints User s Guide. TME 10 User Administration for AS/400 Endpoints 1. You must not install the graphical user interface extensions for TME 10 for User Administration for AS/400 Endpoints on managed nodes in the TMR (Patch ID 3.6-ADM-0001). 2. You can install the TME 10 User Administration Gateway for AS/400 on any gateway that will serve AS/400 endpoints (Patch ID 3.6-ADM-0002). 3. The TME 10 User Administration graphical user interface does not contain OS/400 specific help panels. 4. When populating a user profile from an AS/400 endpoint, TME 10 User Administration sets the OS400_PassW attribute to the same as value as the OS400_Login attribute. Take this setting into consideration when distributing the user profile to systems that do not allow passwords to match login names. 5. The OS400 validation policies are designed to not allow an empty-string as a valid value for an attribute. This can cause problems when working with records that were created before the installation of the 3.6-ADM-0001 patch, especially when copying or moving these existing records into another profile. Generally, validation polices are run during a copy or move operation when the record is put in the destination profile, however, validation policies fail because of empty string OS400 attributes do not pass validation policy. The workaround to this problem is to provide values for the OS400 attributes or to disable validation policy in the destination profile. The stock default and validation polices can be found in the $BINDIR/TME/USERPROFILE directory. For a complete list of files associated with the install, use the ls *OS400*.You can use these files to customize your environment when necessary. 26 Version 3.6

33 Product Notes 6. Using the wchgusrprop -c command can cause excessive memory consumption by the oserv during profile distributions. For example, distributing a Tivoli user profile in which 75 OS400_PassW attributes are changed will mostly likely cause the oserv process to consume excessive system resources. This memory can be released by restarting the oserv with the odadmin reexec command. 7. In the TME 10 for AS/400 Endpoints User s Guide, the table given in the AS/400-Specific Account Information on page 3-6 describes AS/400 attributes in conjunction with the corresponding parameter name and its valid values. Note that the Parameter Name and Values column lists the parameter name as the first entry in the column and then provides valid values for the attributes in a Tivoli user profile The table format should be read as illustrated in the following example table: AS/400 attribute Parameter Name Valid Attribute Values Description OS400_Accounting_Code ACGCDE *BLANK Assigns 15 blanks to accounting code code A user defined code of up to 15 characters. OS400_Assist_Level ASTLVL *SYSVAL *BASIC *INTERMED Specifies the accounting code, if any, to be associated with this user profile. Specifies level of help information to be supplied for this user profile. *ADVANCED TME 10 for AS/400 Endpoints Release Notes 27

34 Product Notes TME 10 Security Management for AS/400 Endpoints 1. You must not install the graphical user interface extensions for TME 10 for Security Management for AS/400 Endpoints on managed nodes in the TMR (Patch ID 3.6-SEC-0001). 2. You can install the TME 10 Security Management Gateway for AS/400 on any gateway that will serve AS/400 endpoints (Patch ID 3.6-SEC-0002). 3. The TME 10 User Administration graphical user interface does not contain OS/400 specific help panels. TME 10 Software Distribution for AS/400 Endpoints 1. When specifying a destination path in the Destination Directory Path field on the File Package Properties dialog, enter the full path to which to distribute the file package on OS/400 subscribers. The destination path can be an integrated file system (IFS) or QSYS path name on the AS/400. However, the path name must always be specified in IFS format for example, /QSYS.LIB/library_name.LIB/. Note that the file name is not specified in this path. 2. The names of files being distributed to /QSYS libraries must be valid OS/400 object names. TME 10 Distributed Monitoring for AS/400 Endpoints 1. The TME 10 Distributed Monitoring ARM for AS400 Endpoint provides the Application Response Management API to monitor availability and performance transactions on AS/400 systems. To use the ARM APIs, you must create the application and call the ARM APIs as described in the TME 10 Distributed Monitoring ARM Agents User s Guide. The following procedure briefly describes how to create and use the program application on the AS/400 system. Follow these steps to use the ARM APIs: a. Install the ARM patch in your gateway using the TME 10 Software Installation Service (SIS), the TME 10 desktop, or the wpatch command. 28 Version 3.6

35 Product Notes b. From the ARM directory, install the binary files from the gateway on to the AS/400 endpoint by executing the following commands from the TMR server command line: cd $BINDIR/../arm_bundle/bin/generic arminst.ep as400endpoint.mydom.com $BINDIR/../arm_bundle c. Start the ARM server with the following command: warmcmd srvstart -f /tmp/myarm.log d. Start the ARM client on the AS/400 with the following command. CALL QTMELCFDM/WARMCMD ( clntstart -h srv_host_name.domain.com ) You can also start the client from the task library provided with ARM. e. Check the status of ARM by running the following command on the AS/400: CALL QTMELCFDM/WARMCMD ( clntstatus ) f. Bind the AS/400 application with the ARM service program. The TME 10 Distributed Monitoring ARM Agents User s Guide describes the location of the header file in the source directory. You can use the arm.h header file in the application program when compiling with ILE/C in the AS/400. When using this header file, you must move the file to your development AS/400. You can also use the VisualAge C++ cross-compiler for AS/400. g. To bind the program, you must bind it to the ARM service program, as in the following example: CRTPGM PGM(MYLIB/MYPGM) BNDSRVPGM(QTMELCFDM/LIBARM) h. Start the collections. The sample program provided in the TME 10 Distributed Monitoring ARM Agents User s Guide has spaces for the application name. Using spaces as demonstrated may fail if you try to start the collection from TME 10 for AS/400 Endpoints Release Notes 29

36 Product Notes the task provided with the patch. Tivoli recommends that you start the collection using the callable program from the AS/400, such as: CALL QTMELCFDM/WARMCMD ( startcoll -a ARM_sample -t Simple_transaction_1 -u * -i 240 -f ) CALL QTMELCFDM/WARMCMD ( startcoll -a ARM sample program -t Long_transaction_1 -u * -i 240 -f ) i. Run your application that uses ARM APIs with the following command: CALL MYLIB/MYPGM j. To stop the ARM client from the AS/400 system, enter the following command from the client: CALL QTMELCFDM/WARMCMD ( clntstop ) k. To stop the ARM server, enter the following command from the TMR server: warmcmd srvstop 2. The OS/400 Distributed Monitoring communication probes only return statistics about the SNA traffic over the requested line. 3. The following OS/400 Distributed Monitoring tables have been revised since the TME 10 for AS/400 Endpoints User s Guide was published. Use the following table to replace the corresponding tables listed in Chapter 5 of the TME 10 for AS/400 Endpoints User's Guide. 30 Version 3.6