AS400 Release Notes - IBMpublib.boulder.ibm.com/tividd/td/as400/as400-361rn/en_US/PDF/as40… ·...

TME 10 for AS/400 EndpointsRelease NotesVersion 3.6.1April 1999

TME 10 AS/400 Endpoints Release Notes (April 1999)

Copyright NoticeCopyright © 1998, 1999 by Tivoli Systems, an IBM Company, including this documentation and allsoftware. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreementor Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication maybe reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, orotherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permissionto make hardcopy or other reproductions of any machine-readable documentation for your own use,provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights undercopyright are granted without prior written permission of Tivoli Systems. The document is not intended forproduction and is furnished “as is” without warranty of any kind.All warranties on this document arehereby 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 ordisclosure 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 ApplicationDevelopment Environment, TME 10 Framework, TME 10 Enterprise Console, TME 10 SoftwareDistribution, TME 10 Software Distribution AutoPack, UserLink for TME 10 Software Distribution, TME10 Inventory, and TME 10 Software Installation Service.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks ofMicrosoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively throughX/Open Company Limited.

ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks or registered trademarks of IntelCorporation in the United States and other countries.

Other company, product, and service names mentioned in this document may be trademarks orservicemarks of others.

NoticesReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply thatthey will be available in all countries in which Tivoli Systems or IBM operates. Any reference to theseproducts, programs, or services is not intended to imply that only Tivoli Systems or IBM products,programs, or services can be used. Subject to Tivoli System’s or IBM’s valid intellectual property or otherlegally protectable right, any functionally equivalent product, program, or service can be used instead of thereferenced product, program, or service. The evaluation and verification of operation in conjunction withother products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of theuser.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue,Thornwood, New York 10594-1785, U.S.A.

TME 10 AS/400 for Endpoints Release Notes i

TME 10 for AS/400 EndpointsRelease Notes

New Features in Version 3.6.1............................................................................... 2

System Requirements............................................................................................. 3

Hardware Requirements ................................................................................ 3

Tivoli Software Requirements....................................................................... 5

Installation Requirements ...................................................................................... 5

The AS/400 Patches on the Compact Disc.................................................... 5

Installation Summary ............................................................................................. 9

Installing AS/400 Endpoints ................................................................................ 10

Installing with TME 10 Software Installation Service................................ 10

Installing with the w4inslcf.pl Script .......................................................... 11

Installing Internationalization Support........................................................ 11

Starting the Endpoint after IPL ............................................................................ 12

Extending the Inventory Configuration Repository Schema for PTFs................ 13

Object Packaging Utility for AS/400................................................................... 14

Installing the Object Packaging Utility ....................................................... 14

Uninstalling the TME 10 Object Packaging Utility .................................... 15

Removing the Endpoint from AS/400 Systems ................................................... 15

AS/400 Endpoints ................................................................................................ 17

Version 3.6.1 Defects, Limitations, and Workarounds ............................... 17

Defects Fixed in Version 3.6.1.................................................................... 19

Distributed Monitoring for AS/400 Endpoints .................................................... 20

Document Changes Since Version 3.6 ........................................................ 20

Version 3.6.1 Defects, Workarounds, and Limitations ............................... 23

Defect Fixed in Version 3.6.1 ..................................................................... 23

Inventory for AS/400 Endpoints .......................................................................... 23

Installation Notes......................................................................................... 24

Security Management for AS/400 Endpoints ...................................................... 24

Installation Notes......................................................................................... 24

ii Version 3.6.1

Document Changes Since Version 3.6.........................................................24

Version 3.6.1 Defects, Limitations, and Workarounds................................25

Defects Fixed in Version 3.6.1.....................................................................26

Software Distribution for AS/400 Endpoints........................................................27




User Administration for AS/400 Endpoints..........................................................30

Installation Notes .........................................................................................30




Changes to Reference Information .......................................................................32

w4inslcf.pl ............................................................................................................32

TME 10 AS/400 for Endpoints Release Notes 1

1Release Notes

This Release Notes document provides important information aboutTME 10 for AS/400 Endpoints, Version 3.6.1. These notes are the mostcurrent information for the product and take precedence over previousdocumentation.

Please review these notes thoroughly before installing or using thisproduct.

These release notes include the following topics:

■ New features in Version 3.6.1

■ System requirements

■ Installation requirements

■ Version 3.6.1 software defects, limitations, and workarounds

■ Defect fixed in Version 3.6.1

■ Installation and document change notes

Tivoli frequently updates the Tivoli Customer Support home page withnew information about configuring and using Tivoli products. Thisinformation 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 thewww.support.tivoli.com/news site for this information andadditional customer services. After you link to and submit the customerregistration form, you will be able to access these services on the Web.

New Features in Version 3.6.1

2 Version 3.6.1

Note: You will notice that both Tivoli and TME 10 are used in oursales, marketing, and product information materials. Theseterms are interchangeable. We will be removing references toTME 10 in future product releases.

New Features in Version 3.6.1This section briefly describes changes and enhancements made since therelease of TME 10 for AS/400 Endpoints, Version 3.6.

■ AS/400 now includes support for the Informix database thatextends the Inventory configuration repository for scanningprogram temporary fixes (PTFs).

■ TME 10 Inventory performance is enhanced, which includes areduction in the amount of time required to read MIF files.

■ TME 10 Software Distribution for AS/400 endpoints now createsa job ID for the process that runs on the AS/400 endpoint to handlea distribution. This information is written to the log file specifiedby the file package. The job ID allows you to locate all messages(error and informational) related to the distribution from the pointof view of the endpoint.

■ The validation policies for TME 10 User Administration forAS/400 now allow the value for AS/400 attributes to be NULL.

■ TME 10 Distributed Monitoring job monitors now acceptUNIX-style regular expressions for the job name, user, andnumber. The monitor selects the first job that matches theexpression. When a response is triggered, it will contain the name,user, and number of the job that was used.

■ This product is translated into five additional languages: German,Italian, Korean, Simplified Chinese, and Spanish. For informationon the languages this product is translated into, refer to “InstallingInternationalization Support,” on page 11.

■ The patches provided in this maintenance release can be installedstand-alone or can be installed as upgrades to the patches providedin TME 10 for AS.400 Endpoints, Version 3.6.

System Requirements


■ The documentation for TME 10 for AS400 Endpoints isrepackaged for the Version 3.6.1 release. The PostScript and PDFversions (English only) are in the/booksdirectory on the compactdisc.

System RequirementsThis section describes the system requirements, including software andhardware, for each of the following resources in the Tivoli environment.

Hardware RequirementsAll TME 10 for AS/400 Endpoints products are supported for AS/400CISC models running OS/400 V3R2 and RISC models running OS/400V3R7 or higher. You must ensure that the following communicationprotocols are active to transfer files to and from AS/400 endpoints in theTivoli network environment:

■ TCP/IP communications

■ ftp services

For information about supported interpreter types for TMR servers andendpoint gateways, refer to theTME 10 Framework Planning andInstallation Guideand theTME 10 Framework Release Notes, Version3.6.1.

Disk Space Required to Install AS/400 Endpoints

The following table lists the estimated disk space required to install theTME 10 product-specific endpoint code for AS/400 endpoints. Youonly need to install the binaries for the installed OS/400 interpreter type.

Product Interpreter Type Binaries

TME 10 for AS/400 Endpoints os400-v3r2 3.20 MB

os400-v3r7 4.40 MB

System Requirements

4 Version 3.6.1

Disk Space Required to Install Gateway Components

The following table lists the estimated disk space required to install theendpoint methods on gateways that will connect AS/400 endpoints inthe Tivoli environment.

Disk Space Required to Install Server Components

The following table lists the estimated disk space required to install theserver components for TME 10 for AS/400 Endpoints.

Product Binaries

TME 10 User Administration for AS/400 Endpoints 1.74 MB

TME 10 Security Management for AS/400 Endpoints 4.85 MB

TME 10 Distributed Monitoring for AS/400 Endpoints 5.36 MB

TME 10 Distributed Monitoring ARM for AS/400 Endpoints 0.63 MB

TME 10 Software Distribution for AS/400 Endpoints 1.02 MB

TME 10 Inventory for AS/400 Endpoints 5.29 MB

TME 10 Task Library for AS/400 Endpoints 0.18 MB

Product Binaries Catalog

TME 10 User Administration forAS/400 Endpoints

0.73 MB 0.02 MB

TME 10 Security Management forAS/400 Endpoints

1.17 MB 0.08 MB

TME 10 Inventory for AS/400 Endpoints 0.013 MB 0 MB

Installation Requirements


Tivoli Software RequirementsYou mustinstall the following Tivoli products on your TMR server andendpoint gateways before installing support for AS/400 endpoints:

■ TME 10 Framework, Version 3.6.1

■ TME 10 Software Installation Service, Version 3.6.1

Optionally, you can install the following Tivoli products if you plan touse them to manage AS/400 objects. If you plan to use any of them,install each base product and any applicable maintenance release orpatch before installing its AS/400 support.

■ TME 10 Distributed Monitoring, Version 3.6.1

■ TME 10 Inventory, Version 3.6.1

■ TME 10 Security Management, Version 3.6.1

■ TME 10 Software Distribution, Version 3.6.1

■ TME 10 User Administration, Version 3.6.1

Installation RequirementsThe following information describes AS/400-specific requirements forinstalling the TME 10 for AS/400 Endpoints patches. Refer to the userguide for each Tivoli product for detailed installation instructions andrequirements.

The AS/400 Patches on the Compact DiscThe TME 10 for AS/400 Endpoints compact disc includes the AS/400endpoint, the AS/400 patches for each supported Tivoli product, theObject Packaging Utility (for Software Distribution), and updateddocumentation (English only). The supplied patches are installed on theTMR server or the endpoint gateway.

The following directories are on the AS/400 for Endpoints compact disc:

■ /as4patch

■ /1tmelcf

■ /obj_pack

■ /books


6 Version 3.6.1

The patches provided with TME 10 for AS/400 Endpoints,Version 3.6.1 supersede those provided with TME 10 for AS/400Endpoints, Version 3.6. The AS/400 patches can be installedstand-alone or can be installed as an upgrade to the Version 3.6 patches.

Notes:

• No AS/400 patch is required to enable TME 10 SoftwareInstallation Service.

• When installing on a Windows NT system, if you list directorycontents in abash shell, all file and directory names mightappear in lowercase letters, such astmf36002.ind. However,when installing the patch from the command line, youmustspecify the file name in uppercase letters, as shown in thefollowing example:

bash$ wpatch -c D:/as4patch -i TMF36002.IND

The as4patch Directory

The/as4patch directory contains the following AS/400 patches:

3.6.1-ADM-0001TME 10 User Administration for AS/400 Endpoints, Version 3.6.1

Contains the User Administration graphical user interfaceextensions to be installed on the TMR server to support AS/400endpoints.

Note: Install this patchonly on the TMR server. Installing thispatch on a managed node will corrupt the installation.

3.6.1-ADM-0002TME 10 User Administration Gateway for AS/400 Endpoints,Version 3.6.1

Contains the User Administration methods to be installed on theendpoint gateway to support AS/400 endpoints.

3.6.1-COU-0001TME 10 Software Distribution Gateway for AS/400 Endpoints,Version 3.6.1

Contains the Software Distribution methods to be installed on theendpoint gateway to support AS/400 endpoints.



3.6.1-DMN-0001TME 10 Distributed Monitoring for AS/400 Endpoints,Version 3.6.1

Contains the Distributed Monitoring engine and probes to beinstalled on the endpoint gateway to support AS/400 endpoints.

3.6.1-DMN-0002TME 10 Distributed Monitoring ARM for AS/400 Endpoints,Version 3.6.1

Contains the Application Response Management (ARM) agent to beinstalled on the endpoint gateway to monitor availability andperformance transactions for supported AS/400 endpoints.

3.6.1-INV-0001TME 10 Inventory Server Scripts for AS/400 Endpoints,Version 3.6.1

Contains the Inventory server and database schema scripts to beinstalled on the TMR server for customizing your configurationrepository for AS/400 PTF information.


3.6.1-INV-0002TME 10 Inventory Gateway for AS/400 Endpoints, Version 3.6.1

Contains the Inventory methods to be installed on the endpointgateway to support AS/400 endpoints.

3.6.1-SEC-0001TME 10 Security Management for AS/400 Endpoints, Version 3.6.1

Contains the Security Management graphical user interfaceextensions to be installed on the TMR server to support AS/400endpoints. To install, you needsuper andsecurity_adminauthorities.


3.6.1-SEC-0002TME 10 Security Management Gateway for AS/400 Endpoints,Version 3.6.1


8 Version 3.6.1

Contains the Security Management methods to be installed on theendpoint gateway to support AS/400 endpoints.

3.6.1-TMF-0001TME 10 Framework Gateway for AS/400 Endpoints, Version 3.6.1

Contains the Framework methods to be installed on the endpointgateway to support AS/400 endpoints.

3.6-TMF-0002TME 10 Task Library for AS/400 Endpoints, Version 3.6

Contains the Framework task library to support AS/400 endpoints.

Note: This is the same patch provided with Version 3.6.

The 1tmelcf Directory

The/1tmelcf directory contains the code used by Tivoli SoftwareInstallation Service (SIS) or thew4inslcf.pl script to install an endpointon an AS/400 system. The contents of this directory is not installed onthe TMR server or endpoint gateway. SIS and thew4inslcf.pl script usethe contents of this directory when installing the endpoint. For SIS, theimage in this directory is imported into the Installation Repository.

The obj_pack Directory

The/obj_pack directory contains the TME 10 Object Packaging Utilityfor AS/400. Install this tool on any Windows PC where ClientAccess/400 is installed. This utility is used only with TME 10 SoftwareDistribution for AS/400.

The books Directory

The/books directory contains updated PostScript and PDF versions oftheTME 10 AS/400 Endpoints User’s Guide, Version 3.6. The AS/400documentation was updated since its original publication. This versionis current with the Version 3.6.1 release.

Installation Summary


Installation SummaryTo be able to use the AS/400 endpoint and Tivoli products in a networkenvironment, youmust perform the following procedure:

1. Install or upgrade your TMR server and endpoint gateways toTME 10 Framework, Version 3.6.1.

2. Install or upgrade your TMR server and endpoint gateways toVersion 3.6.1 for each Tivoli product.

Note: These patches are not provided with this product.

3. Install the AS/400 enablement patch (3.6.1-TMF-0001) on yourendpoint gateways.

4. Install the AS/400 patches to enable AS/400 endpoint support foreach Tivoli product on the TMR server or endpoint gateways, asappropriate. For information on these patches, refer to “Theas4patch Directory,” on page 6.

5. Install new endpoints on AS/400 systems using either TME 10Software Installation Service or thew4inslcf.pl script. For details,refer to “Installing AS/400 Endpoints,” on page 10.

6. Upgrade existing AS/400 endpoints using the followingcommand:

wadminep EPname upgrade

whereEPnameis the object label of a previously installed AS/400endpoint.

7. Customize your installation as needed. For example, you mightwant to complete the following installations:

■ Install the patch for the AS/400 task library. This step isuseful if you are using the TME 10 Enterprise ConsoleAS/400 Message Adapter or the AS/400 Alert Adapter. Thetask library helps automate actions on the AS/400 endpoint.

■ Add supplemental language support for the AS/400 endpoint.By default, the installation of an AS/400 endpoint installsEnglish language support. For details, refer to “InstallingInternationalization Support,” on page 11.

Installing AS/400 Endpoints

10 Version 3.6.1

■ Extend your TME 10 Inventory configuration repository byrunning the database scripts provided for your RDBMS ifyou plan to scan AS/400 PTFs. Refer to “Extending theInventory Configuration Repository Schema for PTFs,” onpage 13 for implementation details.

■ Install the TME 10 Object Packaging Utility for AS/400 ifyou plan to package AS/400 objects for distribution usingTME 10 Software Distribution. Refer to “Object PackagingUtility for AS/400,” on page 14 for an installation summary.For more information about installing the Object PackagingUtility, refer to theTME 10 for AS/400 Endpoints User’sGuide, Version 3.6.

Installing AS/400 EndpointsYou can install AS/400 endpoints using either TME 10 SoftwareInstallation Service (SIS) or with thew4inslcf.pl script. Using eitherapproach, you can specify support for languages other than English.Refer to “Installing Internationalization Support,” on page 11 foradditional details.

Installing the endpoint creates theQTMELCF library and the followinguser accounts:

■ QTIVROOT

■ QTIVUSER

■ QTIVOLI

Installing with TME 10 Software Installation ServiceTME 10 Software Installation Service (SIS) installs AS/400 endpointsusing the FTP access method.

To install an AS/400 endpoint, select the correct interpreter type for thesystem on which you will install the AS/400 endpoint. SupportedAS/400 interpreter types are as follows:

os400-v3r2 CISC models with OS/400 V3R2.

os400-v3r7 RISC models with OS/400 V3R7 or higher.

Installing AS/400 Endpoints


SIS provides a field for specifying additional languages. Whenspecifying a language, use the AS/400 language code. For a list ofAS/400 language codes, refer to “Installing InternationalizationSupport,” on page 11.

Because SIS is designed to be used on managed nodes that support Javainterface, you will need to use thew4inslcf.pl script to install AS/400endpoint for operating systems currently not supported by SIS.

Installing with the w4inslcf.pl ScriptThew4inslcf.pl script installs and optionally starts the AS/400 endpointdaemon on one or more AS/400 systems. Thew4inslcf.pl script isinstalled on your endpoint gateway when you install the3.6.1-TMF-0001 enablement patch. The location or path of this script isas follows:

$BINDIR/../lcf_bundle/generic/w4inslcf.pl

To install the AS/400 endpoint (AS/400 Licensed Program 1TMELCF)with this script, youmust specify the path to the/1tmelcf directory.

Installing Internationalization SupportYou can install the AS/400 endpoint code (AS/400 Licensed Program1TMELCF) to use multiple languages. Although, Tivoli is translatedinto the following languages, the AS/400 system can be operating inother languages:

■ Brazilian Portuguese (Code 2980)

■ English Uppercase and Lowercase (Code 2924)

■ English Uppercase DBCS (Code 2938)

■ French (Code 2928)

■ German (Code 2929)

■ Italian (Code 2932)

■ Japanese (Katakana) DBCS (Code 2962)

■ Korean DBCS (Code 2986)

■ Simplified Chinese DBCS (Code 2989)

■ Spanish (Code 2931)

Starting the Endpoint after IPL

12 Version 3.6.1

The default installation language is English. If you install the AS/400endpoint code without specifying a language, English (2924) anduppercase English (2938) are installed.

When you install the AS/400 endpoint using Software InstallationService (SIS), you select the languages to install from a SIS dialog.

When you install the AS/400 endpoint using the installation script(w4inslcf.pl), you specify the languages using the–N argument. Forexample, to install French (2928) and German (2929), the command linewould be as follows:

w4inslcf.pl -g gwlable[+port] -N ‘2928 2929’ endpoint

Where:

gwlable[+port]The hostname or IP address and optionally the portnumber for the gateway to which the AS/400 endpointwill log in.

endpoint The host name or IP address of the AS/400 endpoint.

To use the OS/400 CL commands from the command line in a languageother than your primary language, add the appropriate Tivoli languagelibrary to your library list. The library format isQTME xxxx(wherexxxxis the 4-digit language code). For French, the language library isQTME2928.

For additional information on installing the endpoint code on an AS/400system, refer to “Installing AS/400 Endpoints,” on page 10. For generalinternationalization information and instructions on setting up anon-English TMR, refer to the Internationalization section of the TME10 Framework release notes.

Starting the Endpoint after IPLTo automatically start the endpoint daemon after IPL, you must modifythe program QSYS/QSTRUP. To enable auto start, perform thefollowing procedure:

1. Retrieve the CL Source into a member of a source file by runningthe following command:

RTVCLSRC PGM(QSYS/QSTRUP) SRCFILE(QGPL/QCLSRC)

Extending the Inventory Configuration Repository Schema for PTFs


2. Start the Source Entry Utility using the following command:

STRSEU SRCFILE(QGPL/QCLSRC) SRCMBR(QSTRUP) TYPE(CLP)

3. Add the following lines as the last job to start:

QSYS/STRTMEEPTMONMSG MSGID(CPF0000)

4. Optionally, save the original program.

5. Save the new program by compiling it using the followingcommands:

CRTCLPGM PGM(QSYS/QSTRUP) SRCFILE(QGPL/QCLDRC)CHGOBJOWN OBJ(QSYS/QSTRUP) OBJTYPE(*PGM) NEWOWN(QSYS)

Extending the Inventory Configuration RepositorySchema for PTFs

The steps for running RDBMS-specific scripts are documented in theTME 10 Inventory User’s GuideandTME 10 Inventory Release Notes.Refer to these documents for information on installing the configurationrepository schema. Follow the appropriate steps to install the schema,and run the appropriate script for AS/400 PTF support. The followingtable contains a list of available scripts for your RDBMS:

Note: You must copy the appropriate script from the$BINDIR/TME/INVENTORY/SCRIPTS/RDBMS directory

Database Type Schema Script

DB/2 tivoli_db2_schema_as400_ptf.sql

Informix tivoli_inf_schema_as400_ptf.sql

Microsoft SQL Server tivoli_ms_sql_schema_as400_ptf.sql

Oracle tivoli_ora_schema_as400_ptf.sql

Sybase tivoli_syb_schema_as400_ptf.sql

Object Packaging Utility for AS/400

14 Version 3.6.1

on the TMR server to a temporary directory on the RDBMSserver.

Object Packaging Utility for AS/400Using the TME 10 Software Distribution, you can distribute and deploysoftware to AS/400 endpoints throughout the network. The ObjectPackaging Utility for AS/400 creates AS/400-specific file packages tobe used with Software Distribution.

Before installing the Object Packaging Utility for AS/400, complete thefollowing steps:

1. Ensure that Client Access/400 is installed and configured on thesystem to be used to prepare AS/400 filepacks.

2. Ensure that this system is connected to the AS/400 SoftwareDistribution source host.

3. Install the Software Distribution for AS/400, Version 3.6.1 patchon the endpoint gateway managing the AS/400 endpoints.

4. Run thepackinst.sh script to install support for the ObjectPackaging Utility for AS/400. This script is located in the$BINDIR\..\lcf_bundle\generic\directory. The only argumentfor this script is the name of the AS/400 endpoint.

Installing the Object Packaging UtilityTo install the Object Packaging Utility for AS/400 on any Windows 95or Windows NT 4.0 system, complete the following steps:

1. From the WindowsFile Manager or Program Manager dialog,selectRun... from theFile menu to display theRun dialog. In theOpen field, type the path to theSETUP.EXE file, which residesin theX:\obj_pack directory on the compact disc, whereX is theCD-ROM drive where the AS/400 compact disc is inserted.

2. Click theOK button to run the setup program and display theWelcome dialog for the Object Packaging Utility for AS/400.

The setup program leads you through the Object Packaging Utilityfor AS/400 installation. Use theBack, Next, or Cancelbuttons tonavigate through these dialogs.

Removing the Endpoint from AS/400 Systems


The default installation location is theC:\Program Files\Tivoli\ObjPackAS400\ directory. Click theBrowse button to navigate through the directory structure andspecify another directory if you want to set a different location.

Click theNext button to continue the installation.

3. To start the Object Packaging Utility, double-click on theas4pack.exe icon from theObjPackAS400 dialog or select theTME 10 Object Packaging Utility for AS/400 option from theStart → Programs→ Tivoli menu.

Uninstalling the TME 10 Object Packaging UtilityPerform the following steps to remove the TME 10 Object PackagingUtility for AS/400 from a Windows system:

1. From the WindowsStart menu, selectControl Panel from theSettings menu to display theControl Panel dialog.

2. Double-click on theAdd/Remove Programs icon to display theAdd/Remove Programs Properties dialog.

3. From this dialog, select TME 10 Object Packaging Utility forAS/400 from the scrolling list and click theAdd/Removebutton.TheConfirm File Deletion dialog is displayed.

4. Confirm the removal operation by clicking theYes button, orcancel the operation by clicking theNo button. An uninstall shieldremoves the product from the system if you clickedYes.

5. Click theOK button to return to theAdd/Remove ProgramsProperties dialog.

6. Click theOK button on theAdd/Remove Programs Propertiesdialog to complete the uninstall.

Removing the Endpoint from AS/400 SystemsTo remove the TME 10 endpoint code from AS/400 systems, performthe following steps:

1. Stop all Tivoli jobs or any other jobs that are started by Tivoliproducts and are running on the endpoint.

Removing the Endpoint from AS/400 Systems

16 Version 3.6.1

Notes:

• Use theENDTMEEPT command to end the endpoint job.

• Use theWRKACTJOB command to find other jobs thatare running under any of the Tivoli user accounts. To enda job, you can use either theENDJOB command or the4option.

Endpoint processes can include thelcfd daemon processas well as any jobs started by Tivoli products. Forexample, you must stop the Distributed Monitoring engineand any monitor processes running on the endpoint.

2. Delete the Licensed Program by entering the following command:

DLTLICPGM LICPGM(1TMELCF)

3. Execute the followingWRKOBJOWN commands on each Tivoliuser account to display all objects owned by the specified user:

WRKOBJOWN USRPRF(QTIVUSER)WRKOBJOWN USRPRF(QTIVROOT)WRKOBJOWN USRPRF(QTIVOLI)

4. TheWRKOBJOWN command lists all objects that belong to auser. To prevent any listed object from being deleted, youmustchange the ownership of that object by selecting option9 for theobject from theWork with Objects by Owner display. Repeatthis step for each object that you want to save.

5. Delete the user account names by specifying the*DLT option,which deletes all objects owned by a user. TheDLTUSRPRFcommands must be entered in the following order:

DLTUSRPRF USRPRF(QTIVUSER) OWNOBJOPT(*DLT)DLTUSRPRF USRPRF(QTIVROOT) OWNOBJOPT(*DLT)DLTUSRPRF USRPRF(QTIVOLI) OWNOBJOPT(*DLT)

Note: If you deleteQTIVOLI before deleting other useraccounts, some objects may not be deleted, and you mighthave problems reinstalling the endpoint on the AS/400system.

AS/400 Endpoints


AS/400 EndpointsThe following sections describe the defects in Version 3.6.1 and thedefects fixed since Version 3.6.

Version 3.6.1 Defects, Limitations, and WorkaroundsThis section describes known defects and limitations in this release ofTME 10 for AS/400 Endpoints. Where applicable and known, suggestedworkarounds are identified. For each defect a tracking number isassigned.

■ TME 10 Software Installation Service and thew4inslcf.plcommand fail to install an AS/400 endpoint if objects belong toQDFTOWN . (CMVC-42837)

WORKAROUND: Ensure that the Tivoli IFS home directory(/QIBM/UserData/Tivoli/lcf ) and the product library(QTMELCF ) belong to theQTIVOLI user account or that theyare deleted from the system before reinstalling the endpoint on theAS/400 system.

■ For BCHJOB tasks, the default scripts run under theQPGMRuser account. When the task is run on an AS/400 endpoint, it issubmitted under theQPGMR profile, because no other jobdescription was specified. The task will not be submitted under theID specified in the task. (CMVC-43057)

WORKAROUND: Create a job description in which the user ID isset to the desired user and the batch job is changed to use theJOBD() argument, as shown in the following example:

//BCHJOB JOB(TEST) JOBD(MYLIB/MYJOBD) JOBQ(*JOBD)

■ The configuration path argument for theSTRTMEEPT commandis ignored. (CMVC-43127)

■ The AS/400 taskVary_Configuration command line iscase-sensitive. (CMVC-43313)

WORKAROUND: Use upper case characters for parameterinformation in the task.

AS/400 Endpoints

18 Version 3.6.1

■ When the AS/400 endpoint is started with theSTRTMEEPTcommand and the value of the debug flag is4, the endpoint doesnot start and there is no message or other indication of why theendpoint did not start. (CMVC-53965)

■ Installation of the AS/400 endpoint fails when the system is atsecurity level10. This level of security does not require apassword, but a sign-on password is required to perform the installfunctions. (CMVC-53968)

■ WhenPUBLIC authority is set to*EXCLUDE for theCRTLIB ,CRTDUPOBJ, CRTSAVF, orCHGJOB commands, theendpoint does not work properly. These commands require theuser accountQTIVOLI . This user account has no specialauthorities. (CMVC-54881)

WORKAROUND: AddQTIVOLI to the authorization list used inthe system for those commands where thePUBLIC authority waschanged, or grant*ALLOBJ authority toQTIVOLI .

■ When installing the endpoint using SIS, the endpoint is not startedcorrectly when the user profile has a current library other thanQPL. (CMVC-62794)

WORKAROUND: Use another privileged user profile that doesnot specify a current library. Alternatively, you can not specify acurrent library for the user (in the user profile) before installing theendpoint to the AS/400 system.

■ When SIS upgrades (forces an install on) an AS/400 endpointwhen the endpoint daemon is running, SIS returns a failure notice.The endpoint is upgraded, but it cannot connect to its endpointgateway (because the endpoint daemon is running). To completethe upgrade, youmust stop and restart the endpoint daemon.(CMVC-63561)

WORKAROUND: Log on to the specific AS/400 system wherethe installation failed. Stop the endpoint daemon with theENDTMEEPT command and restart it with theSTRTMEEPTcommand.

■ When using SIS or thew4inslcf.pl script to install the endpoint onan AS/400 system and the primary language does not recognize

AS/400 Endpoints


EBCDIC lowercase characters (for example, Japanese), theendpoint installs correctly but fails to start. (CMVC-63794)

WORKAROUND: Use thew4inslcf.plscript with the–I argumentto install the endpoint. For example, to install the AS/400 endpointon hostas41.tivoli.com with Japanese and uppercase Englishlanguage support and the installation image is in the/cdrom/1tmelcf directory, enter the following command:

w4inslcf.pl -v -I -N ’2938 2962’ -s /cdrom/1tmelcf as41.tivoli.com

You can verify the installation of the product using the followingcommand:

CHKPRDOPT PRDID(1TMELCF)

To start the endpoint after installation you have to log in to yourAS/400 system and run theSTRTMEEPT command. Forexample, enter the following command:

STRTMEEPT LGNINTRFC(MYGATEWAY.MYDOMAIN.COM 9494) GATEWAY(MYGATEWAY.MYDOMAIN.COM 9494) EPTNAME(MYAS400)

■ APAR 85618. If single quotes are used when passing parametersto any AS/400 task in task library from the command line, theparameter is not passed.

WORKAROUND: Instead of using single quotes, use two singlequotes. For example, use:

CALL PGM(MYLIB/MYPGM) PARM(’’X’’)

instead of:

CALL PGM(MYLIB/MYPGM) PARM(’X’)

Defects Fixed in Version 3.6.1This section describes the defects fixed in this release and are listed bytheir defect number.

■ Thewadminep command can now be used to upgrade theendpoint label. (CMVC-43296)

Distributed Monitoring for AS/400 Endpoints

20 Version 3.6.1

■ TheSTRTMEEPT command no longer displays extraneous logmessages that can be ignored. (CMVC-43524)

■ Thew4inslcf.pl command no longer forces the use of the–gargument to install endpoints. (CMVC-43637)

Distributed Monitoring for AS/400 EndpointsThis product is required if you plan to monitor critical system resourcesand performance of the AS/400 systems in your network. The set ofAS/400 monitoring collections provides the same monitoringcapabilities as the AS/400 Performance Monitor application plus thesame function found in the AS/400 Work Management APIs that arebuilt into the OS/400 operating system. Each collection contains severalmonitoring sources that allow you to manage different aspects of yournetwork, such as system resources and network protocols.

The following sections describe the changes to the Version 3.6documentation, the defects in Version 3.6.1, and the defects fixed sinceVersion 3.6.

Document Changes Since Version 3.6■ For Version 3.6.1, the location of the installation script for the

Tivoli Distributed Monitoring Application Response Management(ARM) agent for AS/400 Endpoints is as follows:

arm_bundle/bin/generic/TME/ARM/arminst.ep

For 3.6, the location of this installation script was:

arm_bundle/bin/generic/arminst.ep

■ The following changes were made to the OS/400 monitoringcollections.

• Monitors added to collections

- OS/400 System Monitoring

• User Monitor, Numeric script—Runs a user-definedscript that returns a numeric value. Refer to the UserMonitor, Numeric script of the Universal MonitoringCollection in theTME 10 Distributed MonitoringCollection Reference for details.



• String Script—Runs a user-defined script that returnsa string value. Refer to the User Monitor, String scriptof the Universal Monitoring Collection in theTME 10Distributed Monitoring Collection Reference fordetails.

- OS/400 Disk Monitoring Collection

• Blocks Read/Second—The number of blocks read.The block length is 520 bytes, which includes 8 bytesof system control information (BlocksReadPerSec).

• Blocks Written/Second—The number of blockswritten. The block length is 520 bytes, which includes8 bytes of system control information(BlocksWrittenPerSec).

• Writes/Second—The number of writes per second(WritesPerSec).

• Reads/Second—The number of reads per second(ReadPerSec).

• Percent Seeks less than 1/12—Percentage of time thedisk arm traveled less than 1/12 of the disk on a seekrequest (PctSeeksUnderTwelfth).

- OS/400 Ethernet Monitoring Collection

• Mail Frames Discarded—The number of stored andforward mail products dropped(MailFramesDiscarded).

- OS/400 Token Ring Monitoring Collection

• SABME Frames Sent—The number of setasynchronous balanced mode extended framestransmitted (SABMEFramesSent).

• Monitors changed in collections

- OS/400 Disk Monitoring Collection

• Processor Idle Loop Count—The count increasesdifferently for 9332 and 9335 disk drives. For 9332,increased only when disk controller is idle (no active


22 Version 3.6.1

I/O operation). For 9335, increased although an I/Ooperation is active (for example, a seek). This field isnon-zero for drive types that support dedicated diskprocessor and is zero for other drive types.

• Processor Idle Loop Time—This field is non-zero fordrive types that support a dedicated disk processor andis zero for other drive types.

• Monitors removed from collections

- OS/400 Bisync Monitoring Collection

• Percent Characters Resent

• Percent Characters Received in Error

• Characters Received in Error

• NAK Received to Text Sent

• Wrong ACK to Text Sent

• Enquiry to Text Sent

• Invalid Format

• Enquiry to ACK

• Remote Disconnect

• Remote EOT

• Host Disconnect

• Host EOT

- OS/400 Ethernet Monitoring Collection

• N2 Retry Expiration

• T1 Timer Expiration Count

- OS/400 Token Ring Monitoring Collection

• N2 Retry Expiration

• T1 Timer Expiration Count

- OS/400 ISDN Monitoring Collection

• Retry for Outgoing Calls

• Retry for Incoming Calls

- OS/400 X25 Monitoring Collection

Inventory for AS/400 Endpoints


• Reset Packets Sent

• Reset Objects Received

Version 3.6.1 Defects, Workarounds, and LimitationsThis section describes known defects and limitations in this release ofTME 10 for AS/400 Endpoints. Where applicable and known, suggestedworkarounds are identified. For each defect a tracking number isassigned.

■ Executables or dependencies downloaded from the gateway mightnot be deleted from the endpoint when the endpoint is removedfrom the TMR. For example, theQTMELCFDM library and itsobjects, which are installed by TME 10 Distributed Monitoring forAS/400 Endpoints, are not deleted when the endpoint is removedfrom the TMR. (CMVC-45032)

WORKAROUND: Follow the steps outlined in “Removing theEndpoint from AS/400 Systems” on page 15 to delete the librariesand objects from the AS/400 system.

■ The Inspector feature does not display monitors for the AS/400endpoints. When you attempt to expand an AS/400 endpoint toview its monitors, you receive a “No monitors found” message.(CMVC-63048)

Defect Fixed in Version 3.6.1An ARM daemon job no longer fails to restart if the job ends suddenlyor incorrectly. (CMVC-44828)

Inventory for AS/400 EndpointsThis product is required if you plan to manage AS/400 inventory. Youwill be able to electronically scan for AS/400 hardware and installedAS/400 products as well as for Program Temporary Fixes (PTFs) onyour AS/400 systems. This will help you manage assets and tracksoftware throughout your enterprise. Your information is tracked in anRDBMS database. Tivoli supports DB2, Informix, Sybase, Oracle, andMicrosoft SQL Server.

Security Management for AS/400 Endpoints

24 Version 3.6.1

Installation NotesInstead of installing one patch for Inventory support of AS/400endpoints, you now install two patches. One of the patches contains thegateway methods needed by the endpoints, and the other contains theconfiguration repository scripts and query scripts.

Security Management for AS/400 EndpointsThis product is required if you plan to secure a wide variety of networkresources, including files, directories, terminals, and OS/400 objects.TME 10 Security Management for AS/400 Endpoints incorporatesOS/400’s inherent security measures with Tivoli’s security profiles andaudit tasks to monitor network groups, resources, roles, andsystem-wide policies.

The following sections describe installation notes, the changes to theVersion 3.6 documentation, the defects in Version 3.6.1, and the defectsfixed since Version 3.6.

Installation Notes■ Installing 3.6.1-SEC-0002 requires no special installation

instructions. It is a cumulative patch that can be installed on top of3.6-SEC-0002 or can be installed stand-alone.

■ Installing 3.6.1-SEC-0001 requires no special installationinstructions. It is a cumulative patch that can be installed on top of3.6-SEC-0001 or can be installed stand-alone.

Document Changes Since Version 3.6Local copies of Security Profiles are kept using native AS/400 databasetables. Any database tables remaining from Version 3.6 must be deleted.Deleting these tables does not affect the endpoint. To delete the tables,run the following series of commands on each AS/400 endpoint runningTME 10 Security Management:



QSYS/ENDJRNAP FILE(*ALL) JRN(QUSRSYS/QLCFJRN)QSYS/ENDJRNPF FILE(*ALL) JRN(QUSRSYS/QLCFJRN)DLTF FILE(QUSRSYS/WLCF*)DLTJRN JRN(QUSRSYS/QLCFJRN)DLTJRNRCV JRNRCV(QUSRSYS/QLCFJR*)

Note: When you issue theDLTJRN command, you will receive awarning message. This message can be safely ignored.


■ Profile distribution fails if an invalid group name exists in rolerecords. (CMVC-44510)

WORKAROUND: Delete the current role record and create a newone.

■ When specifying to populate aLIBRARY resource type from anAS/400 endpoint, the format of the resource name must be enteredin the following form:

/QSYS.LIB/ library-name .LIB/

TheLIBRARY resource is not populated if the trailing backslash(/) is not included in the name. (CMVC-44933)

■ When profiles with very large numbers of records are distributedto AS/400 endpoints, an endpoint timeout can occur. This problemcan also occur when setting default access on all objects of acertain object type in system policies. (CMVC-45000)

WORKAROUND: On the endpoint gateway, enter the followingTME 10 Framework command:

wgateway gateway_name set_session_timeout timeout_value

This command increases the amount of time the gateway allows anendpoint to run the AS/400 endpoint methods. Note that thisincreases the amount of time for all methods on all platforms.


26 Version 3.6.1

■ When a user, created by TME 10 User Administration, is specifiedas a member of a group, the user is not added to the group profileon the AS/400 endpoint. (CMVC-45039)

■ Installing the OS/400 Security server patch (3.6.1-SEC-0001) failswhen installing to a TMR server that is interconnected with a TMRon which the patch is already installed. (CMVC-63213)

WORKAROUND: There is patch available to fix this problem.Connect to the Tivoli patch Web site and download the3.6.1-SEC-0003 patch.


■ When populating resource records for IFS stream files, theresource type no longer displays as an IFS directory.(CMVC-44373)

■ You can now set the value of theOS4Lockout attribute in theformatx,y,zwhen creating or editing a system policy record fromthe command line. (CMVC-44785)

■ When resource permissions are set manually after distributing aprofile to schedule resource authorizations, the permissions arenow reset to the correct authorization level. (CMVC-44786)

■ The population of a resource record no longer fails with an invalidResAudit value when success and failure auditing is activated.(CMVC-44836)

■ Records now distribute to endpoints during profile distributionwhen the records were populated from an endpoint.(CMVC-44842)

■ TheQBATCH job queue now grants and revokes resource accessand logins for groups as expected. (CMVC-44857)

■ When distributing a profile that containsSTREAM_FILEresource types defined with a wildcard character, neitherSTREAM_FILE norDIRECTORY types have their access

Software Distribution for AS/400 Endpoints


permissions or auditing values changed as dictated by the profile.(CMVC-44934)

■ Specifying default access toLIBRARY resource types in a systempolicy now changes the permissions for libraries on AS/400endpoints. (CMVC-45042)

■ A distribution failure no longer occurs when trying to modify anallocated resource on an AS/400 endpoint. (CMVC-45045)

■ AS/400DEVICE_DESCRIPTION resource types are no longerin system policy records. (CMVC-45052)

■ Editing a resource record from theResource Record Propertiesdialog and deselecting allAccess Rights check boxes in theResource Default Access dialog no longer generates an error.(CMVC-45274)

Software Distribution for AS/400 EndpointsThis product is required if you plan to distribute AS/400 software. Usedin conjunction with TME 10 Inventory, Software Distribution enablesyou to manage the deployment of new software products to all of yourAS/400 systems.

Tivoli provides the TME 10 Object Packaging Utility for AS/400 toquickly and efficiently create AS/400-specific file package blocks(fpblocks) for distribution to AS/400 systems. Note that if you use theTME 10 Object Packaging Utility for AS/400, you must ensure thatClient Access/400 is installed on the Windows 95 or Windows NTsystem on which you plan to package AS/400 software applications.

Document Changes Since Version 3.6■ To increase security, ownership of objects distributed to an

AS/400 endpoint defaults to user accountQTIVUSER , and thePUBLIC attribute for these object defaults to*EXCLUDE . Thismeans that you must have*ALLOBJ authorization to manipulatethese objects. After a successful distribution, use after scripts tochange ownership of these objects.

Note: The userQTIVUSER cannot log in to an AS/400 system.


28 Version 3.6.1

■ Each filepack specifies the location of its distribution log file. Thislog file contains summaries of the distribution to each AS/400endpoint by job ID. An example summary in this distribution logfile might be the following:

AS/400 Job ID: 10239/QTIVROOT/COURIER

Where10239 is the ID,QTIVROOT is the user account, andCOURIER is the job name.

If a distribution fails to an AS/400 endpoint, knowing this job IDis the key for learning what occurred from the AS/400 endpointpoint of view.

After reading the log file to obtain the job ID for the specificAS/400 endpoint distribution, go to that system and enter thefollowing command on the command line:

WRKJOBJobID

whereJobID is the qualified job name for the distribution.


■ When creating a file package block (fpblock) with the ObjectPackaging Utility for AS/400, it hangs if the network connection islost between the AS/400 system and the Windows system whereyou are creating the fpblock. (CMVC-38013)

WORKAROUND: Perform the following procedure:

1. Close the Object Packaging Utility

2. Re-establish the network connection through ClientAccess/400

3. Re-issue the create for the file package block

■ The Object Packaging Utility for AS/400 cannot be used onWindows NT, version 3.5.1, because Client Access/400 is notsupported for this operating system. However, installing theObject Packaging Utility for AS/400 on a Windows NT 3.5.1



system does not generate an appropriate error message.(CMVC-40250)

■ When the Object Packaging Utility for AS/400 is uninstalled, itsicon is not removed. The user must remove the icon manuallythrough Windows Explorer. (CMVC-40436)

■ (IX87114) When you create a file package with the Tivoli desktopand distribute it to a QSYS destination, you cannot control themember for the target file. Data bound for a*FILE in the QSYSfile system are always placed in the member named the same as thefile. The file will be named as specified in theDestinationDirectory Path field (or with the keywordos400_platform_prefix).

For example, if you specify in the following path in DestinationDirectory Path field:

/QSYS.LIB/QUSRSYS.LIB/QAYMACD.FILE

and distribute the following data:

/USRA/TIVOLI/TECADAPTERS/AS400/MSGCDS

The data is placed as follows:

• Library QUSRSYS

• File QAYMACDS

• Member QAYMACDS (not MSGCDS)

WORKAROUND: Use the Tivoli Object Packaging Utility forAS/400 to create the file package blocks of objects residing underQSYS if you need to distribute them to other AS/400 systems asspecified.

Alternatively, you can use after scripts to copy or rename themembers or files.


User Administration for AS/400 Endpoints

30 Version 3.6.1

■ Configuration programs and input files properly install in thedestination directory or library when theinstall_progskeyword isset toy. (CMVC-41786)

■ The problem associated with a configuration program failure canbe easily located and identified. (CMVC-43193)

User Administration for AS/400 EndpointsThis product is required if you plan to use Tivoli to manage AS/400 useraccounts across your enterprise.

The following sections describe installation information anddocumentation changes specific to TME 10 User Administration forAS/400 endpoints.

Installation Notes■ The 3.6.1-ADM-0001 patch is a cumulative patch that can be

installed on top of 3.6-ADM-0001 or can be installed stand-alone.If installed stand-alone, there are no special installationinstructions. If installed on top of 3.6-ADM-0001, use thefollowing procedure to not overwrite any of your UserAdministration customizations.

1. Source the Tivoli environment

2. Enter the following commands from the command line:

cd $BINDIRTME/USERPROFILE/Upgrade_OS400_ui.sh

■ Installing the 3.6.1-ADM-0002 patch requires no specialinstallation instructions. It is a cumulative patch that can beinstalled on top of 3.6-ADM-0002 or can be installed stand-alone.

Document Changes Since Version 3.6■ Changes to the validation policies for AS/400 attributes consist of

deleting the check to prevent blank input. In Version 3.6.1, thevalue for an attribute can be NULL.

■ Using the change-controlled (-c) flag of thewchgusrpropcommand will cause consumption of excessive memory resources

User Administration for AS/400 Endpoints


by theoservduring profile distribution. For example, distributinga Tivoli user profile in which 75OS400_PassW attributes arechanged will cause theoserv to consume excessive systemresources. To release this memory, restart the oserv using theodadmin reexec command.


■ OS/400 passwords can be only 10 characters long. If a password istyped in theCommon Password field, it is distributed as theAS/400 password. If this password is more than 10 characterslong, no validation policy on the server catches the error. Thecreation or modification of the user on the AS/400 fails atdistribution time. (CMVC-42963)

■ TheOS400_PassW attribute becomes a change-controlledattribute using thewchgusrprop –c command. This means that anative OS/400 user account password is not overwritten by aTivoli user profile unlessOS400_PassW is explicitly changed.(CMVC-43308)

WORKAROUND: Change theOS400_PassW attribute from theTivoli desktop, or run thewchgusrprop –ccommand on the Tivoliuser profile after a populate operation, as follows:

wchgusrprop -c @UserProfile: profile_name OS400_PassW

■ Creating two or more profile records with differentcommon_login names but the sameOS400_Login name anddistributing this profile to an AS/400 endpoint causes only the firstuser account to be created and overwritten by the repeatedOS400_Login name. (CMVC-43456)

■ The installation of the 3.6.1-ADM-0001 patch exits if it encounterserrors while adding the new attributes and dialogs.(CMVC-45044)

Changes to Reference Information

32 Version 3.6.1

WORKAROUND: Check theadd_OS400_properties.outputfile in the/tmp directory for descriptions of any errors thatoccurred during installation. Tivoli recommends that you back upthe TMR database before installing the 3.6.1-ADM-0001 patch. Ifyou encounter problems while installing this patch, perform thefollowing steps:

1. Restore the TMR database

2. Check theadd_OS400_properties.output file to solveinstallation problems

3. Back up the TMR database

4. Reinstall


■ User Administration records from profiles prior to the installationof the 3.6-ADM-0001 patch can now be copied without an errorthat states that the profile can not longer be changed.(CMVC-46342)

■ The validation policy for attributeOS400_Locale no longer failswhen user profiles are populated from AS/400 endpoints runningOS/400 V3R2M0. (CMVC-46771)

Changes to Reference Information

w4inslcf.plInstalls an endpoint on as AS/400 system.

Synopsis

w4inslcf.pl [-v} [ –a] [–F] [–I] [–ggwlabel[+port]] [–l ep_port] [–Lconfig_args] [–N code] [–P] [–sdir_name] [–Y] { endpoint | –ffilename}

w4inslcf.pl


Arguments

–a Specifies asynchronous installation of endpoints. Bydefault, the command waits for the endpoint to log in toits gateway before installing the next endpoint.

–F Forces an overwrite of an existing installation.

–I Indicates that the endpoint should be installed but notstarted.

–f filename Specifies the file containing a list of systems on whichto install endpoints. This file contains one system nameper line, specifying the user ID and password to beused. Each line in this file must be in the followingformat:

host [userID [password]]

–ggwlabel[+port]Specifies the IP address or host name and optionally theport number of the gateway to which the endpoint willlog in.

–l ep_port Specifies the port number for the endpoint. The defaultport number is 9495.

–L config_argsPasses configuration arguments to the daemon forstarting the endpoint. To pass multiple arguments,enclose them in quotes. Refer to thelcfd command intheTME 10 Framework Reference Manualfor a list ofvalid arguments.

–N code Specifies additional languages to support by AS/400code. The following are the codes: 2980 (Brazilian,Portuguese), 2989 (Chinese, simplified), 2924 (Englishuppercase and lowercase), 2938 (English uppercase),2928 (French), 2929 (German), 2932 (Italian), 2962(Japanese), 2986 (Korean), and 2931 (Spanish). Tospecify multiple languages, enclose them in quotes. Thedefaults are 2924 and 2938.

–P Specifies to prompt the user for a password. Thisargument overrides existing entries in a$HOME/.netrc file used for automatic logins.

w4inslcf.pl

34 Version 3.6.1

–sdir_name Specifies the directory that contains the endpointinstallation image. This directory can be on a compactdisc, the TMR server, a gateway, or a network drive.

–Y Specifies that the installation should proceed withoutconfirmation. The default is to request confirmation.

–v Writes verbose messages to standard output. Errormessages are still written to standard error.

endpoint … Specifies the names or IP addresses of AS/400 systemson which the endpoints will be installed.

Description

Thew4inslcf command installs and optionally starts an AS/400endpoint daemon job on one or more AS/400 systems. You can installmultiple endpoints by listing the system name on the command line orsupplying a file containing the system names. The file must contain onesystem name per line.

The command checks for prerequisites, sends code to the endpoint to beinstalled, using FTP, and then restores the product,1TMELCF , to theAS/400, usingRSTLICPGM . If requested, the endpoint is also startedby issuing the AS/400 CL command STRTMEEPT .

Authorization

You must have root access to install endpoints but you do not need anyTivoli authorization roles. On the AS/400 you will need authority to usetheRSTOBJ andRSTLICPGM commands and *SAVSYS specialauthority.

Return Codes

This command returns the following codes to standard output:

0 Indicates successful completion.

-1 Indicates failure due to an error.

Note: Host names for failed installations are written toos4LcfH.errand can be retried with the command using the–f os4LcfH.errkeyword specified on the command.

w4inslcf.pl


Examples

1. The following example installs the AS/400 endpoint on theAS/400 systemsas41.tivoli.comandas42.tivoli.com, connects togatewaysmithers.tivoli.com using port 9494. The installationimage is located in the/cdrom/1tmelcf directory.

w4inslcf.pl -v -g smithers.tivoli.com+9494 as41.tivoli.com as42.tivoli.com -s /cdrom/1tmelcf

2. The following example installs the AS/400 endpoint on theAS/400 system as42.tivoli.com, connects to gatewaysmithers.tivoli.com using port 9494, and installing French andGerman language support.

w4inslcf.pl -v -g smithers.tivoli.com+9494 -N '2928 2929' as42,tivoli.com

w4inslcf.pl

36 Version 3.6.1

AS400 Release Notes - IBMpublib.boulder.ibm.com/tividd/td/as400/as400-361rn/en_US/PDF/as40… ·...

Documents

Transcript of AS400 Release Notes - IBMpublib.boulder.ibm.com/tividd/td/as400/as400-361rn/en_US/PDF/as40… ·...