TME 10 for AS/400 Endpoints Release Notespublib.boulder.ibm.com/tividd/td/as400/rnas400/en_US/PDF/rnas400.… · AS400 Endpoint 0.63 MB 0 MB 0 MB TME 10 Software Distribution for

TME 10 for AS/400 EndpointsRelease Notes

Version 3.6

September 1998

are.rayteral, or

.

M,

ME

ks of

gh

thatse

therad ofctionibility

thisn sende,

TME 10 for AS/400 Endpoints Release Notes (September 1998)Copyright NoticeCopyright © 1998 by Tivoli Systems, an IBM Company, including this documentation and all softwAll rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement oAddendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication mbe reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any compulanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manuotherwise, 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

TrademarksThe following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, AS/400, IBOS/2, OS/400, RISC System/6000, Tivoli Management Environment, TME 10, TME 10 ApplicationDevelopment Environment, TME 10 Framework, TME 10 Enterprise Console, TME 10 Inventory, T10 Software Distribution, TME 10 Software Distribution AutoPack, UserLink for TME 10 SoftwareDistribution.

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

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

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

NoticeReferences in this publication to Tivoli Systems or IBM products, programs, or services do not implythey will be available in all countries in which Tivoli Systems or IBM operates. Any reference to theproducts, 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 olegally protectable right, any functionally equivalent product, program, or service can be used instethe referenced product, program, or service. The evaluation and verification of operation in conjunwith other products, except those expressly designated by Tivoli Systems or IBM, are the responsof the user.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter indocument. The furnishing of this document does not give you any license to these patents. You calicense inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus AvenuThornwood, New York 10594.

TME 10 for AS/400 EndpointsRelease 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 .................................................................................. 10

Installing AS/400 Endpoints ....................................................................... 12

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

Installing the TME 10 Object Packaging Utility for AS/400...................... 13

Installing Internationalization Support........................................................ 14

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

Removing TME 10 Object Packaging Utility for AS/400 .......................... 17

Version 3.6 Software Defects, Limitations, and Workarounds ........................... 17

AS/400 Endpoints........................................................................................ 18

TME 10 User Administration for AS/400 Endpoints.................................. 19

TME 10 Security Management for AS/400 Endpoints ............................... 20

TME 10 Distributed Monitoring for AS/400 Endpoints ............................. 24

TME 10 Software Distribution for AS/400 Endpoints................................ 25

TME 10 Object Packaging Utility for AS/400............................................ 25

Product Notes....................................................................................................... 26

TME 10 User Administration for AS/400 Endpoints.................................. 26

TME 10 for AS/400Endpoints Release Notes i

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

10y of

tosther

s

.

ces

1Release Notes

With the Version 3.6 release, Tivoli Management Environment 10(TME 10) provides support for AS/400 endpoints in the TivoliManagement Region. The TME 10 Framework and selected TMEapplications can be configured and used to manage a wide varietsystem resources on AS/400 systems in a TME 10 environment.

This Release Notesdocument provides important information abouTME 10 for AS/400 Endpoints, Version 3.6. These notes are the mcurrent information for the product and take precedence over all otdocumentation.

Please review these notes thoroughly before installing or using thiproduct.

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 pagewith new information about configuring and using Tivoli productsThis 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 thewww.support.tivoli.com/newssite for this information andadditional customer services. After you link to and submit thecustomer registration form, you will be able to access these servion the Web.

TME 10 for AS/400 Endpoints Release Notes 1

System Requirements

,

re

are

0

ster

rk

ll400

You will notice that both Tivoli and TME 10 are used in our salesmarketing, and product information materials. These terms areinterchangeable. We will be removing references to TME 10 in futuproduct releases.

System RequirementsThis section describes the system requirements, including softwand hardware, for each of the following resources in the TME 10environment.

AS/400 Hardware RequirementsAll TME 10 for AS/400 Endpoints products are supported for AS/40CISC models running OS/400 Version 3 Release 2.0, and RISCmodels running OS/400 Version 3 Release 7.0 or higher. You muensure that the following communication protocols are active in ordto transfer files to and from AS/400 endpoints in the Tivoli netwoenvironment:

■ TCP/IP communications

■ ftp services

The following tables list estimated disk space required to install aserver, gateway, and endpoint code needed to use TME 10 for AS/Endpoints products. For information about supported interpretertypes for servers and gateways in the TMR environment, see theTME10 Framework Planning and Installation Guide and theTME 10Framework Release Notes, Version 3.6.

2 Version 3.6

System Requirements

tallnfor

tall

Disk Space Required to Install AS/400 Endpoints

The following table lists the estimated disk space required to insthe endpoint code for the TME 10 Endpoint for AS/400 product oan AS/400 system. Note that you only need to install the binariesthe installed OS/400 interpreter type.

Disk Space Required to Install Gateway Components

The following table lists the estimated disk space required to insthe endpoint methods on gateways that will connect AS/400endpoints to the TMR environment.

ProductInterpreter

TypeBinaries

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

os400-v3r7 4.40 MB

Product Images Binaries Catalog

TME 10 User Administration forAS/400 Endpoints

1.74 MB 0 MB 0 MB

TME 10 Security Management forAS/400 Endpoints

4.85 MB 0 MB 0 MB

TME 10 Distributed Monitoring forAS/400 Endpoints

5.36 MB 0 MB 0 MB

TME 10 Distributed Monitoring ARM forAS400 Endpoint

0.63 MB 0 MB 0 MB

TME 10 Software Distribution forAS/400 Endpoints

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


System Requirements

tall

h

0

d

s

.

Disk Space Required to Install Server Components

The following table lists the estimated disk space required to insthe server-side components for TME 10 for AS/400 Endpoints.

Software RequirementsYou can install the following TME 10 products if you plan to usethem to manage your network. If so, install each product beforeinstalling TME 10 for AS/400 support which is provided as a patcin Version 3.6:

■ TME 10 User Administration, Version 3.6

Install this product if you plan to use Tivoli to manage AS/40user accounts across your enterprise.

■ TME 10 Security Management, Version 3.6

Install this product if you plan to secure a wide variety ofnetwork resources, including files, directories, terminals, anOS/400 objects. TME 10 Security Management for AS/400Endpoints incorporates OS/400’s inherent security measurewith Tivoli’s security profiles and audit tasks to monitornetwork groups, resources, roles, and system-wide policies

Product Binaries Catalog

TME 10 User Administration forAS/400 Endpoints

0.69 MB 0.02 MB

TME 10 Security Management forAS/400 Endpoints

0.81 MB 0.08 MB

4 Version 3.6

System Requirements

.

k

sk,

u

yrur

g

■ TME 10 Distributed Monitoring, Version 3.6

Install this product if you plan to monitor critical systemresources and performance of the AS/400’s in your networkThe set of AS/400 monitoring collections provide the samemonitoring capabilities as the AS/400 Performance Monitorapplication plus the same function found in the AS/400 WorManagement APIs that are built into the OS/400 operatingsystem. Each collection contains several monitoring sourcewhich allow you to manage different aspects of your networsuch as system resources and network protocols.

■ TME 10 Inventory, Version 3.6

Install this product if you plan to manage AS/400 inventory.Yowill be able to electronically scan for AS/400 hardware andinstalled AS/400 products as well as for Program TemporarFixes (PTFs) on your AS/400’s. This will help you manage youassets and track your software throughout your enterprise. Yoinformation 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, SoftwareDistribution enables you to manage the deployment of newsoftware products to all of your AS/400’s. Tivoli provides theTME 10 Object Packaging Utility for AS/400 to quickly andefficiently package AS/400 objects to be distributed.

Required TME 10 Product Installations

You must install the following TME 10 products on yourmanagement 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 installinthe TME 10 Framework Upgrade to Version 3.6 patch.


System Requirements

r

.

s

tor

ws

ll

.

0,

Optional TME 10 Product Installations

Install the following TME 10 products if you plan to use them tomanage your network. If so, you must install each product in youTMR 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 distributeAS/400 software. You can also use the TME 10 ObjectPackaging Utility to create AS/400-specific file package block(fpblocks) for distribution to AS/400 machines. Note that if youuse the TME 10 Object Packaging Utility for AS/400, you musensure that Client Access/400 is installed on the Windows 95WIndows NT system on which you plan to package AS/400software applications.

■ TME 10 User Administration, Version 3.6, to use Tivoli tomanage user and group accounts using TME 10 profiles.

■ TME 10 Distributed Monitoring, Version 3.6, to monitor criticalsystem resources and performance of the AS/400’s in yournetwork.

■ TME 10 Security Management, Version 3.6 to manage thesecurity aspects of the AS/400’s in your network from onecentralized source.

Client Access/400 InstallationClient Access/400 must be installed and configured on the Windo95 or Windows NT PC if you plan to use the TME 10 ObjectPackaging Utility for AS/400 to prepare AS/400 file packages. Instathe following versions of Client Access/400:

■ 57xx-XW1—Client Access/400 Windows Family Base

■ 57xx-XD1—Client Access/400 Optimized for Windows

wherexx is related to the version of the product you are installing

For more information about installing and using Client Access/40refer to the product documentation that accompanies the ClientAccess/400 product. You may download this and other AS/400documentation from the AS/400 library of manuals available at

6 Version 3.6

Installation Requirements

ther

sch

d the

s

0hatren

www.as400.ibm.com. The AS/400 reference library providessearchable online guides, AS/400 manuals and Redbooks, and oinformation about configuring and using AS/400 systems.

Installation RequirementsThe following information describes AS/400-specific requirementfor installing the TME 10 for AS/400 Endpoints products. See eaapplication-specific user’s guide for installation instructions andrequirements for each TME 10 application.

AS/400 Patch Installation PrerequisitesYou must satisfy the following requirements before installing theAS/400 patches:

■ Install and configure TME 10 Framework. For information anprocedures about setting up and using the Framework, seeTME 10 Framework Planning and Installation Guide.

■ Install the TMR server and endpoint gateways with TME 10Framework, Version 3.6.

■ Install any optional TME 10 products on your TMR server alisted in “Optional TME 10 Product Installations” on page 3.

The Tivoli for AS/400 CD-ROM (P/N LK3T-2330-00) contains allTivoli products that support AS/400 systems, including the TME 1Framework code needed on your TMR server, the endpoint code truns on the AS/400, and code for the TME 10 applications that asupported on the AS/400. Application code will either be installed othe TMR server or the AS/400 endpoint.

The Tivoli for AS/400 CD-ROM is shipped with the following Tivoliproducts:





■ TME 10 User and Group Management, Version 3.6



t

,

t

■ TME 10 Security Management, Version 3.6.

The following directories located on the CD-ROM contain allnecessary 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 3.6

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

3.6-ADM-0001 TME 10 User Administration for AS/400 Endpoint,Version 3.6. This code contains the graphical userinterface extensions for TME 10 UserAdministration.Note: Install the GUI extensiononly on the TMRserver. Do not install on any managed node in theTMR.

3.6-ADM-0002 TME 10 User Administration Gateway for AS/400Endpoint, Version 3.6. This code contains themethods supported by AS/400 systems. This produccan be installed on any gateway that will serveAS/400 endpoints.

3.6-SEC-0001 TME 10 Security Management for AS/400 EndpointVersion 3.6 and TME 10 Security AuditReports for AS/400, Version 3.6. This code containsthe graphical user interface extensions for TME 10Security Management.Note: Install the GUI extensiononly on the TMRserver. Do not install on any managed node in theTMR.

3.6-SEC-0002 TME 10 Security Management Gateway for AS/400Endpoint, Version 3.6. This code contains themethods supported by AS/400 systems. This produccan be installed on any gateway that will serveAS/400 endpoints.

8 Version 3.6


s

Notes:

• An AS/400 patch to enable Software Installations Service(SIS) is not required.

/as4patch 3.6-SEN-0001 TME 10 Distributed Monitoring for AS/400Endpoint, Version 3.6. This code includes the engineand the probes code for the AS/400. Install this patchon any gateway that will serve AS/400 endpoints.

3.6-SEN-0002 TME 10 Distributed Monitoring ARM for AS400Endpoint, Version 3.6. This code includes theApplication Response Management API to monitoravailability and performance transactions on AS/400systems. Install this patch on any gateway that willserve AS/400 endpoints

3.6-COU-0002 TME 10 Software Distribution Gateway for AS/400Endpoint, Version 3.6. This code contains methodsthat are installed on the TMR gateway that run onAS/400 endpoints.

3.6-INV-0001 TME 10 Inventory Gateway for AS/400 Endpoint,Version 3.6. This patch includes database schemascripts which are run on your database machine thatare needed to customize your database for AS/400PTF information. It also includes the AS/400inventory methods and scanner code. Install thispatch any gateway that will serve AS/400 endpoints.

/obj_pack n/a TME 10 Object Packaging Utility for AS/400. Installthis tool on any Windows PC on top os ClientAccess/400.

/1tmelcf ES_os400_36 TME 10 Endpoint daemon for AS/400. Install thispatch on AS/400 endpoints.

/books n/a Postscript and pdf versions ofTME 10 for AS/400Endpoints User’s Guide

Directory PatchID Description



sns

ll

if

se

at

0

in

• Do not install the 3.6-ADM-0001 and 3.6-SEC-0001 patcheon managed nodes in the TMR. Installing the GUI extensiofor TME 10 User Administration for AS/400 or for TME 10Security Management for AS/400 on a managed node wicorrupt the installation.

• When installing these patches on a Windows NT machine,you list directory contents in abash shell, all file anddirectory names appear in lowercase letters, such astmf36002.ind. However, when installing the patch form thecommand line, you must specify the file name in uppercaletters, as shown in the following example command lineprompt:

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

• To install TME 10 Security Management for AS/400Endpoints, you must havesuper andsecurity_adminauthority.

Installation SummaryThe following steps outline the general installation procedures thmust 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/40endpoints, ensure that one or all of the following products areinstalled on your TMR server and endpoint gateways as describedthe installation procedures for each product.

■ TME 10 Software Installation Service, Version 3.6





■ TME 10 User Administration, Version 3.6

■ TME 10 Security Management, Version 3.6

10 Version 3.6


li

0

ay

is

Complete the following procedure to install patches for yourenvironment:

1. Apply each product patch to enable the AS/400 support. Tivostrongly recommends that you use the TME 10 SoftwareInstallation Service to install all patches for TME 10 for AS/40Endpoints. See theTME 10 Software Installation Service User’sGuidefor information about using this product to install AS/400patches.

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

• Install the patch for the AS/400 task library. Note that thstep is useful if you are using the TME 10 EnterpriseConsole’s AS/400 Message Adapter or AS/400 AlertAdapter. The task library helps automate actions on theAS/400 endpoint.

• Extend your Inventory configuration repository by runningthe scripts provided if you plan to scan AS/400 PTFs.

• Install the TME10 Object Packaging Utility for AS/400 ifyou plan to package AS/400 objects for later distributionusing TME 10 Software Distribution. See “Installing theTME 10 Object Packaging Utility for AS/400” on page 13for an installation summary. For more information aboutinstalling the Object Packaging Utility, see theTME 10 forAS/400 Endpoints User’s Guide.



0t,ine

y

to

y

u

in

hect

Installing AS/400 EndpointsThe TME 10 Software Installation Service (SIS) installs multipleTME 10 products on multiple systems in parallel, including AS/40endpoints in the TMR environment. To install an AS/400 endpoinyou must select the correct interpreter type for the AS/400 machon which you will install the Framework. Supported AS/400interpreter types include the following:

Thew4inslcf.pl command is also available to install and optionallstart an AS/400 endpoint daemon job on one or more AS/400systems. Although Tivoli recommends that you use the SIS facilityinstall AS/400 endpoints, you must use thew4inslcf.pl command ifyou are installing the endpoint from a platform not yet supported bSIS.

The /1tmelcf/install_sis/directory contains thew4inslcf.plcommand to install all endpoint code. Tivoli recommends that yorunw4inslcf.pl from the/1tmelcf/install_sisdirectory. If you chooseto copy and run thew4inslcf.pl command from a temporarydirectory, specify the path to the/1tmelcf/install_sis directory. Forprocedures to install an AS/400 endpoint using thew4inslcf.plcommand, see theTME 10 for AS/400 Endpoints User’s Guide.

Extending the Inventory Configuration RepositorySchema for PTFs

The steps for installing database-specific scripts are documentedtheTME 10 Inventory User’s Guide. Refer to this manual forinformation about installing the configuration repository schema.Follow the appropriate steps to install the schema and then run tadditional script required for AS/400 PTF support. Select the correschema for your database from the following table and follow the

Interp Type Supported Platform

os400-v3r2 For AS/400 CISC models with OS/400 at Version 3Release 2

os400-v3r7 For AS/400 RISC models with OS/400 at Version 3Release 7 or higher

12 Version 3.6


e

ut-re

e

toed.

installation steps as the detailed in theTME 10 Inventory User’sGuide:

Note: You must copy the appropriate script from the$BINDIR/TME/INVENTORY/SCRIPTS/RDBMSdirectory on the TMR server to a temporary directory on thRDBMS server.

Installing the TME 10 Object Packaging Utilityfor AS/400

Using TME 10 Software Distribution file package technology, youcan distribute and deploy software to AS/400 endpoints throughothe network. The TME 10 Object Packaging Utility for AS/400 creates AS/400-specific file packages to be used with TME 10 SoftwaDistribution.

Note: Client Access/400 must be installed and configured on thWindows 95 or Windows NT PC that you will be using toprepare AS/400 file packages. Ensure this PC is connectedthe AS/400 source machine on which the software is stor

To install the TME 10 Object Packaging Utility for AS/400 on anyWindows 95 or Windows NT 4.0 machine complete the followingsteps:

1. From theFile Manager or Program Manager window, selectRun... from theFile menu to display theRun dialog.

2. Enter the path to theSETUP.EXE file, which resides in theX:\obj_pack directory on the CD-ROM, in theOpen text field,

DatabaseType

Database Schema Script

DB/2 tivoli_db2_schema_as400_ptf.sql

Microsoft SQL tivoli_ms_sql_schema_as400_ptf.sql

Oracle tivoli_ora_schema_as400_ptf.sql

Sybase tivoli_syb_schema_as400_ptf.sql



e

dn.

ins

whereX is the CD-ROM drive where the TME 10 for AS/400CD-ROM image is inserted.

3. Press theOK button to run the setup program and display thWelcome dialog for the TME 10 Object Packaging Utility forAS/400.

The setup program leads you through the TME 10 ObjectPackaging Utility for AS/400 installation. Use theBack, Next,or Cancel buttons to navigate through these option dialogs.

The default location is automatically set to theC:\Program Files\Tivoli\ObjPackAS400\directory. Press theBrowse button to navigate through the directory structure anspecify another directory if you want to set a different locatio

Press theNext button to continue the installation.

4. To start the Object Packaging Utility, double-click on theas4pack.exe icon from theObjPackAS400 window or selecttheTME 10 Object Packaging Utility for AS/400 option fromtheStart -> Programs -> Tivoli menu.

Installing Internationalization SupportTivoli provides the AS/400 endpoint code (AS/400 LicensedProgram 1TMELCF) for the following languages.

Note: If you install TME 10 for AS/400 Endpoints on a machinethat supports one of the primary languages that are listedthe table, Tivoli automatically installs the AS/400 commandand help text for these commands.

Code Primary Supported Languages

2924 English

2938 Upper case English

2928 French

2980 Brazilian Portuguese

2962 Japanese

14 Version 3.6


s,d

esge

r

ete

li

d:

However, if you install the TME 10 for AS/400 Endpointsproduct on a machine on which the primary language isdifferent from the listed languages, Tivoli creates alanguage-specific library for each listed language, such aQTME2924 for English, QTME2938 for Upper case Englishand so on. You must change your system library list to adthe specific language, such as QTME29xx, before executingTivoli commands.

If the primary language is set to any of the listed languagon the AS/400 system, you can install a secondary languaby running the following command:

w4instlcf.pl -g gateway_name -N xxxx endpoint_name

wherexxxx is the code of the supported language that youwish to install, such as 2928 if you are installing support foFrench.

Removing Endpoint Code from AS/400 SystemsTo remove the TME 10 endpoint code from AS/400 clients, complthe following steps:

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

Note: Endpoint processes can include thelcfd daemonprocess as well as any jobs started by TME 10applications. For example, you must stop theDistributed Monitoring engine and any monitorprocesses running on the endpoint.

2. Delete the license program by entering the following comman

DLTLICPGM LICPGM(1TMELCF)



d

st

ut

3. Execute the followingWRKOBJOWN commands on eachTivoli user account to display all objects owned by the specifieuser:

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, you muchange the ownership of that object by selecting option9 for theobject from theWork with Objects by Owner window. Repeatthis step for each object that you wish to save.

5. Delete the user account names by specifying the*DLT optionto delete 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)

Notes: If you deleteQTIVOLI before deleting other useraccounts, some objects may not be deleted, and yomay have problems reinstalling the TME 10 endpoincode in the AS/400.

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

Version 3.6 Software Defects, Limitations, and Workarounds

g-

o

se

ds

Removing TME 10 Object Packaging Utility for AS/400Complete the following steps to remove the TME 10 Object Packaing Utility for AS/400 from your Windows PC:

1. From theStart menu, select theControl Panel option from theSettings menu item to display theControl Panel window.

2. Double-click on theAdd/Remove Programs icon to displaytheAdd/Remove Programs Properties window.

3. From the Install/Uninstall property sheet, select TME 10Object Packaging Utility for AS/400 from the scrolling list andpress theAdd/Removebutton.

4. A Confirm File Deletion window is displayed. Confirm theremoval operation by selectingYesto proceed with the deletionor No to cancel. An Uninstall shield removes the product fromthe Windows PC if you selectYes.

5. Select theOK button when the uninstall is complete to return ttheAdd/Remove Programs Properties window.

6. Select theOK button on theAdd/Remove ProgramsProperties window to complete the uninstall procedure.

Version 3.6 Software Defects, Limitations, andWorkarounds

This section describes known defects and limitations in this releaof TME 10 for AS/400 Endpoints. Defects are categorized byapplication component and are listed by their defect number anddescription. Where applicable and known, suggested workarounare identified. For each defect a tracking number is assigned.



o

e

the

e

AS/400 Endpoints1. TME 10 Software Installation Service (SIS) or thew4inslcf.pl

command fail to install an AS/400 endpoint if objects belong tQDFTOWN . PR-42837

WORKAROUND: Ensure that the Tivoli IFS home directory(/QIBM/UserData/Tivoli/lcf ) and product library(QTMELCF ) belong to theQTIVOLI user account, or thatthey are deleted from the systems before you reinstall theendpoint code on the AS/400 system.

2. For task execution, by default batch job scripts run under thQPGMR user account. PR-43057

WORKAROUND: Create a job description in which the user IDis set to the desired user and the batch job is changed to useJOBD() parameter, as in the following example:

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

3. Configuration path option for theSTRTMEEPT command isignored. PR-43127

4. Thewadminep command cannot be used to upgrade theendpoint label variable. PR-43296

5. AS/400 TasksVary_Configuration command line is casesensitive. PR-43313

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

6. TheSTRTMEEPT command may display the followingextraneous log message that should be ignored: File

file_name in library_name not a save file . PR-43524

7. Thew4inslcf.pl command forces the use of the–g option toinstall AS/400 endpoints. PR-43637

WORKAROUND: Specify a login interface IP address with th–g parameter, as in the following example:

w4inslcf.pl -v -g gateway_name +port endpoint_name

18 Version 3.6


ords

atn

ly

u1h,

e

TME 10 User Administration for AS/400 Endpoints8. OS/400 passwords can only be 10 characters long. If a passw

is entered in the ‘Common Password’ field, it is distributed athe AS/400 password. If that password is more than 10characters long, there is no validation policy on the server thwill catch the error. The creation or modification of the user othe AS/400 will fail at distribution time. PR-42963

9. TheOS400_PassWattribute is marked as a controlled attributevia thewchgusrprop -ccommand, which means that a nativeOS/400 user account password will not be overwritten by aTivoli user profile unless theOS400_PassW is explicitlychanged. PR-43308

WORKAROUND: Change theOS400_PassW attribute fromthe TME 10 desktop, or run thewchgusrprop -c command onthe Tivoli user profile after a populate operation, as follows:

wchgusrprop -c @UserProfile: profile_name OS400_PassW

10. Creating two or more profile records with differentcommon_login names but with the sameOS400_Login nameand distributing this profile to an AS/400 endpoint causes onthe first user account to be created and overwritten by therepeatedOS400_Login name. PR-43456

11. The installation script for the 3.6-ADM-0001 patch to installGUI extensions for TME 10 User Administration for AS/400exits if it encounters errors while adding the new OS400attributes and dialogs. PR-45044

WORKAROUND: Check theadd_OS400_properties.outputfile in the /tmp directory for descriptions of any errors that mayhave occurred during installation. Tivoli recommends that yoback up the TMR database before installing the 3.6-ADM-000patch. If you do encounter problems when installing this patcsuch as corrupted profiles that the installation script cannotupdate usingwaddprop, restore the TMR database, check thadd_OS400_properties.output file to solve installationproblems, back up the TMR database, and reinstall.



n

an

rt

e

hate

12. After installing the 3.6-ADM-0001 patch to install TME 10User Administration for AS/400 Endpoints, records from anyprofile that was created prior to the installation of this patchcannot be copied. Attempts to copy the record will result in aerror that states that the profile can not longer be changed.PR-46342

WORKAROUND: Provide values for the OS400 attributes toavoid assigning an empty string to the attribute. Also, you cmodify theOS400V validation policy scripts to checkvalidation first. Include the following code segment at the staof the script:

if [ $1 = ““ ]thenecho TRUEfi

13. The validation policy for attributeOS400_Localewill fail whenuser profiles are populated from AS/400 endpoints runningOS/400 V3R2M0 becauseLocale is not a valid attribute forOS/400 user profiles on V3R2M0. PR-46771

WORKAROUND: From the TME 10 User Administrationprofile, change the type of validation policy for attributeOS400_Locale to NONE. After the population is complete,enter the following command on the management servercommand line:

wputpolm -v args=\$OS400_Locale \@UserProfile: profile_name \OS400_Locale $bindir_path /OS400v_IFS_Path

TME 10 Security Management for AS/400 Endpoints14. When populating resource records for IFS stream files, the

resource type is shown as IFS directory. PR-44373

WORKAROUND: None required, since the populated resourcrecord can be distributed without affecting the operation ofSecurity Management. However, you can add a new record tduplicates the information in the populated record in which thresource type is correctly set toStream File, and then delete thepopulated record.

20 Version 3.6


lyis

e

a

nd

t,

ate

on

ndas

15. Populate of a resource record fails with an invalid ResAuditvalue, and the record is not added to the database. This onoccurs for a resource in which success and failure auditing activated. PR-44836

WORKAROUND: Temporarily turn off validation forResAudit, populate and edit the record, and then enable thesuccess and failure auditing. Ensure that the validation forResAudit is re-enabled after you have edited this record.

16. Profile distribution fails if an invalid group name exists in Rolrecords. PR-44510

WORKAROUND: Delete the current role record and create new one.

17. Cannot create or edit a system policy record from the commaline that specifies a value for theOS4Lockout attribute of theformat x,y,z. PR-44785

WORKAROUND: Set the last two values for OS4Lockout to0andForever when creating a record from the command line.

18. When editing a resource record from theResource RecordProperties window, deselecting allAccess Rightscheckboxesin theResource Default Access window generates an error.PR-45274

WORKAROUND: Delete the resource record and recreate iafter which the default access permissions for this resourcerecord are set toNone.

19. When restricting access to a resource for a role to a specific dand time, or restricting a login time for a group, jobs aresubmitted on the AS/400 endpoint under job queueQBATCHto grant and revoke resource access and logins. Dependingthe AS/400 configuration, theQBATCH job queue may beconfigured to only run one job at a time, and thus the grant arevoke of resource access or logins may not occur for a groupexpected. PR-44857



y

ss

g

ted

he

ed

WORKAROUND: On the AS/400 endpoint, enter the followingcommand:

DSPSBSD SBSD(QBATCH)

Select option6 from the menu. In theJob Queuecolumn, locateQBATCH . The number of allowed active jobs for theQBATCH job queue is located in theMax Active column. Toincrease the maximum number of active jobs allowed for theQBATCH job queue, enter the following command

CHGJOBQE SBS(*LIBL/QBATCH) JOBQ(*LIBL/QBATCH) MAXACT( x)

wherex 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 bTME 10 User Administration is specified as a member, theTME 10 user is not added to the group profile on the AS/400endpoint. PR-45039

21. When profiles with very large numbers of records aredistributed to AS/400 endpoints, an endpoint timeout mayoccur. This problem can also occur when setting default acceon all objects of a certain object type in system policies.PR-45000

WORKAROUND: On the gateway system, enter the followinTME 10 Framework command:

wgateway gateway_name set_session_timeout timeout_value

to increase the amount of time that the gateway allows theendpoint to execute the AS/400 endpoint methods. Note thathis increases the amount of time that all methods are allowto run in for all platforms.

22. After populating resource records from an AS/400 endpoint, trecords will not be distributed to any AS/400 endpoint uponprofile distribution. PR-44842

WORKAROUND: For each populated resource, edit theresource record and save it. The record will then be distributupon the next profile distribution.

22 Version 3.6


n

s

ds,

ual

s,

ed

,

t0oflt

s

23. When specifying to populate a LIBRARY resource type from aAS/400 endpoint, the format of the resource name must beentered in the following form:/QSYS.LIB/library-name.LIB/ .TheLIBRARY resource will not be populated if the trailingbackslash (/) is not included in the name. PR-44933

24. When distributing a profile that containsSTREAM_FILE typeresources that are defined with a wildcard character, such a/usr/testlib/* or /usr/testlib/abc*, bothSTREAM_FILE andDIRECTORY (subdirectories) resource types in the specifiedirectory will have their access permissions or auditing valueor both, changed as dictated by the profile. PR-44934

WORKAROUND: Do not create resource records forSTREAM_FILE type resources that contain wildcardcharacters. Instead, create a resource record for each individresource, such as/usr/testlib/abc54.

25. After distributing a profile to schedule resource authorizationif resource role permissions are manually set to a higherauthorization, for example from*USE to *CHANGE or from*CHANGE to *ALL , then these permissions are not reset tothe correct authorization level until the permissions are revokby the scheduled job. PR-44786

WORKAROUND: If you are manually changing permissionsyou must reset authorization levels.

26. AS/400DEVICE_DESCRIPTION resource types can onlyexist in libraryQSYS—not in user libraries. Distributingprofiles that contains system policy records that sets defaulaccess to all objects of a resource type only modifies AS/40resources that exist in user libraries. Therefore, a distributiona profile that contains system policy records that sets defauaccess forDEVICE_DESCRIPTION resource types will haveno effect on AS/400 endpoints. PR-45052

27. Specifying default access toLIBRARY resource types in asystem policy will not change the permissions for any librarieon AS/400 endpoints. PR-45042



l

dtionn

ed

y tos

d

rly

WORKAROUND: Create a resource record for each individuaLIBRARY resource, and set access permissions for eachresource record.

28. A distribution failure occurs when trying to modify an allocateresource on an AS/400 endpoint. Each subsequent distribuwill fail until the resource is deallocated. This may occur whespecifying default access to allFILE resource types in a systempolicy, depending on the AS/400 endpoint configuration.PR-45045

WORKAROUND: Deallocate the object specified on theAS/400 endpoint using theDLCOBJ command and redistributethe profile.

TME 10 Distributed Monitoring for AS/400 Endpoints29. An ARM daemon job fails to restart if the job is terminated

suddenly or incorrectly. The ARM daemon may terminateunexpectedly if the job is ended via theENDJOB command,theQSYSWRK subsystem is ended, or the system is restart(IPL or reboot). The files in/tmp are not deleted, and the ARMjob cannot start a new client daemon job. PR-44828

WORKAROUND: Use theWRKLNK command to delete thefollowing files to restart a new ARM client daemon job:/tmp/arm* , /tmp/asx*, /tmp/ASX* .

30. Executables or dependencies downloaded from the gatewathe endpoint may not be deleted from the endpoint when it iremoved from the TMR. For example, theQTMELCFDMlibrary and its objects, which are installed by TME 10Distributed Monitoring for AS/400 Endpoints, are not deletewhen the endpoint is removed from the TMR. PR-45032

WORKAROUND: Follows steps outlined in “RemovingEndpoint Code from AS/400 Systems” on page 15 to propedelete libraries and objects from the AS/400 system.

24 Version 3.6


y.

0

n

0,

T,

te

er

TME 10 Software Distribution for AS/400 Endpoints31. Configuration programs and input files may not be properly

installed in the destination directory or library when theinstall_progs keyword is set to y. PR-41786

32. Messages resulting from configuration program failures manot contain enough information to easily identify the problemPR-43193

TME 10 Object Packaging Utility for AS/40033. When creating a file package block (fpblock) with the TME 1

Object Packaging Utility for AS/400, the Object PackagingUtility hangs if the network connection is terminated betweethe AS/400 system and the Windows PC on which you arecreating the fpblock. PR-38013

WORKAROUND: Close the Object Packaging Utility,reestablish the network connection through Client Access/40and recreate the file package block.

34. Because Client Access/400 is not supported on Windows NVersion 3.5.1machines, you cannot use TME 10 ObjectPackaging Utility for AS/400 on these systems. However,installing the TME 10 Object Packaging Utility for AS/400 ona Windows NT 3.5.1 system does not result in an appropriaerror message. PR-40250

35. The TME 10 Object Packaging Utility for AS/400 icon is notremoved when the Object Packaging Utility is deleted. The usmust delete the icon manually through Windows Explorer.PR-40436


Product Notes

ernt

or

rch

es

E

s

ere

.

0is

Product NotesThis section contains important information that you should considwhile using the product. This information is provided to supplemeinformation in theTME 10 for AS/400 Endpoints User’s Guide.

TME 10 User Administration for AS/400 Endpoints1. You must not install the graphical user interface extensions f

TME 10 for User Administration for AS/400 Endpoints onmanaged nodes in the TMR (Patch ID 3.6-ADM-0001).

2. You can install the TME 10 User Administration Gateway foAS/400 on any gateway that will serve AS/400 endpoints (PatID 3.6-ADM-0002).

3. The TME 10 User Administration graphical user interface donot contain OS/400 specific help panels.

4. When populating a user profile from an AS/400 endpoint, TM10 User Administration sets theOS400_PassWattribute to thesame as value as theOS400_Login attribute. Take this settinginto consideration when distributing the user profile to systemthat do not allow passwords to match login names.

5. The OS400 validation policies are designed to not allow anempty-string as a valid value for an attribute. This can causproblems when working with records that were created befothe installation of the 3.6-ADM-0001 patch, especially whencopying or moving these existing records into another profile

Generally, validation polices are run during a copy or moveoperation when the record is put in the destination profile,however, validation policies fail because of empty string OS40attributes do not pass validation policy. The workaround to thproblem is to provide values for the OS400 attributes or todisable validation policy in the destination profile.

The stock default and validation polices can be found in the$BINDIR/TME/USERPROFILE directory. For a completelist of files associated with the install, use thels *OS400*. Youcan use these files to customize your environment whennecessary.

26 Version 3.6

Product Notes

This

at

g

6. Using thewchgusrprop -ccommand can cause excessivememory consumption by theoservduring profile distributions.For example, distributing a Tivoli user profile in which 75OS400_PassWattributes are changed will mostly likely causethe oserv process to consume excessive system resources.memory can be released by restarting theoserv with theodadmin reexec command.

7. In theTME 10 for AS/400 Endpoints User’s Guide, the tablegiven in the “AS/400-Specific Account Information” on page3-6 describes AS/400 attributes in conjunction with thecorresponding parameter name and its valid values. Note ththeParameter Name and Values column lists the parametername as the first entry in the column and then provides validvalues for the attributes in a Tivoli user profile

The table format should be read as illustrated in the followinexample table:

AS/400 attributeParameter

NameValid Attribute

ValuesDescription

OS400_Accounting_Code ACGCDE *BLANKAssigns 15 blanksto accounting code

codeA user defined codeof up to 15characters.

Specifies theaccounting code, ifany, to be associatedwith this user profile.

OS400_Assist_Level ASTLVL *SYSVAL

*BASIC

*INTERMED

*ADVANCED

Specifies level ofhelp information tobe supplied for thisuser profile.


Product Notes

or

orch

es

tedr,

0on

se

r

TME 10 Security Management for AS/400 Endpoints1. You must not install the graphical user interface extensions f

TME 10 for Security Management for AS/400 Endpoints onmanaged nodes in the TMR (Patch ID 3.6-SEC-0001).

2. You can install the TME 10 Security Management Gateway fAS/400 on any gateway that will serve AS/400 endpoints (PatID 3.6-SEC-0002).

3. The TME 10 User Administration graphical user interface donot contain OS/400 specific help panels.

TME 10 Software Distribution for AS/400 Endpoints1. When specifying a destination path in theDestination

Directory Path field on theFile Package Properties dialog,enter the full path to which to distribute the file package onOS/400 subscribers. The destination path can be an integrafile system (IFS) or QSYS path name on the AS/400. Howevethe path name must always be specified in IFS format forexample,/QSYS.LIB/library_name.LIB/ . Note that the filename isnot specified in this path.

2. The names of files being distributed to/QSYSlibraries must bevalid OS/400 object names.

TME 10 Distributed Monitoring for AS/400 Endpoints1. The TME 10 Distributed Monitoring ARM for AS400 Endpoint

provides the Application Response Management API tomonitor availability and performance transactions on AS/40systems. To use the ARM APIs, you must create the applicatiand call the ARM APIs as described in theTME 10 DistributedMonitoring ARM Agents User’s Guide.

The following procedure briefly describes how to create and uthe program application on the AS/400 system. Follow thesesteps to use the ARM APIs:

a. Install the ARM patch in your gateway using the TME 10Software Installation Service (SIS), the TME 10 desktop, othewpatch command.

28 Version 3.6

Product Notes

:

d

e

le

e

e

b. From the ARM directory, install the binary files from thegateway on to the AS/400 endpoint by executing thefollowing 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 followingcommand.

CALL QTMELCFDM/WARMCMD (‘clntstart’ ‘-h’ ‘srv_host_name.domain.com’)

You can also start the client from the task library providewith ARM.

e. Check the status of ARM by running the followingcommand on the AS/400:

CALL QTMELCFDM/WARMCMD (‘clntstatus’)

f. Bind the AS/400 application with the ARM serviceprogram. TheTME 10 Distributed Monitoring ARM AgentsUser’s Guidedescribes the location of the header file in thsource directory. You can use thearm.h header file in theapplication program when compiling with ILE/C in theAS/400. When using this header file, you must move the fito your development AS/400. You can also use theVisualAge C++ cross-compiler for AS/400.

g. To bind the program, you must bind it to the ARM servicprogram, as in the following example:

CRTPGM PGM(MYLIB/MYPGM) BNDSRVPGM(QTMELCFDM/LIBARM)

h. Start the collections. The sample program provided in thTME 10 Distributed Monitoring ARM Agents User’s Guidehas spaces for the application name. Using spaces asdemonstrated may fail if you try to start the collection from


Product Notes

te

e

d

n

the task provided with the patch. Tivoli recommends thayou start the collection using the callable program from thAS/400, such as:

CALL QTMELCFDM/WARMCMD (‘startcoll’ ‘-a’ ‘ARM_sample’ ‘-t’‘Simple_transaction_1’ ‘-u’ ‘*’ ‘-i’ ‘240’ ‘-f’)

CALL QTMELCFDM/WARMCMD (‘startcoll’ ‘-a’ ‘ARM sampleprogram’ ‘-t’ ‘Long_transaction_1’ ‘-u’ ‘*’ ‘-i’ ‘240’‘-f’)

i. Run your application that uses ARM APIs with thefollowing command:

CALL MYLIB/MYPGM

j. To stop the ARM client from the AS/400 system, enter thfollowing command from the client:

CALL QTMELCFDM/WARMCMD (‘clntstop’)

k. To stop the ARM server, enter the following command fromthe TMR server:

warmcmd srvstop

2. The OS/400 Distributed Monitoring communication probesonly return statistics about the SNA traffic over the requesteline.

3. The following OS/400 Distributed Monitoring tables have beerevised since theTME 10 for AS/400 Endpoints User’s Guidewas published. Use the following table to replace thecorresponding tables listed in Chapter 5 of theTME 10 forAS/400 Endpoints User's Guide.

30 Version 3.6

Product Notes

obre

OS/400 System Monitoring Collection

The following table lists the monitoring sources for the OS/400System monitoring collection:

OS/400 Subsystem Monitoring Collection

The following table lists the monitoring sources for the OS/400Subsystem monitoring collection:

OS/400 Job Monitoring Collection

The following table lists the monitoring sources for the OS/400 Jmonitoring collection. All OS/400 job monitoring resources requithe following input:

■ Job name (char 10)

■ Job user (char 10)

Resource Monitored Description Name

Number of jobs Number of jobs running on theAS/400. Includes jobs at allstatuses.

NumberOfJobs

Percent CPU time Percentage of CPU time usedby all jobs.

CPUTimePct

ResourceMonitored

Description Input Name

Number of jobs Number of jobs activein this subsystem.

Subsystem name(char 10)

Library name(char 10)

NumberOfJobs

Subsystem status Indicates whether ornot the subsystem isactive.

Subsystem name(char 10)

Library name(char 10)

Status


Product Notes

■ Job number (char 6)

ResourceMonitored

Description Return Values Name

Job existence Indicates whether ornot the job exists.

Yes or No Existence

Job status Status of the job. HLD , DEQW,MSGW, and so on.

ActiveStatus

Job type Type of job or task. A - Autostart job;B -Batch job;H -Horizontal LicensedInternal code (tasksonly); I - Interactivejob; M - SubsystemMonitor job;R -spooled reader job;S-system job;V -licensed internal codetask;W - spooledwriter job;X Startcontrol programfunction system job

Type

Job subtype Subtype of the job. N No special subtype;D Immediate;E Evoke job or batchcommunicate;J Prestart job;P Print driver job;T Multiple requeststerminal (MRT) job(System/36environment only);U Alternate spool user

SubType

Job priority Priority over otherjobs.

Priority number Priority

Job pool Pool that the job isrunning in.

Pool name Pool

32 Version 3.6

Product Notes

Time slice Time slice value. Seconds TimeSlice

CPU time Processing unit usedby this job.

Milliseconds CPUTime

Function Function currentlyperformed by this job.

Function name asshown in the functioncolumn ofWRKACTJOB (forexample,PGM -pgmname;CMD -command name)

Function

Function type Type of functionperformed by this job.

U Not logged;C command;D delayed job;G transfer group job;I index path rebuild;L logging toQHST;M MRT job;N menu;O I/O;R procedure;* - special function(you must also requestthe function name toreceive additionalinformation)

Function Type

Transaction count Number oftransactionsperformed by this job.

Number oftransactions

TransactionCount

Transaction time Total transaction time. Seconds TransactionTime

Synchronous databasereads

Total number ofphysical synchronousread operations fordatabase operations.

Number of reads SyncDBReads

ResourceMonitored



Product Notes

Synchronous databasewrites

Total number ofphysical synchronouswrite operations fordatabase operations.

Number of writes SyncDBWrites

Synchronousnon-database reads

Total number ofphysical synchronousread operations fornon-databaseoperations.

Number of writes SyncNonDBReads

Synchronousnon-database writes

Total number ofphysical synchronouswrite operations fornon-databaseoperations.

Number of writes SyncNonDBWrites

Asynchronousdatabase reads

Total number ofphysicalasynchronous readoperations fordatabase operations.

Number of reads AsyncDBReads

Asynchronousdatabase writes

Total number ofphysicalasynchronous writeoperations fordatabase operations.

Number of writes AsyncDBWrites

Asynchronousnon-database reads

Total number ofphysicalasynchronous readoperations fornon-databaseoperations.

Number of reads AsyncNonDBReads

ResourceMonitored


34 Version 3.6

Product Notes

Asynchronousnon-database writes

Total number ofphysicalasynchronous writeoperations fornon-databaseoperations.

Number of writes AsyncNonDBWrite

Communication puts Number ofcommunicationwrites. This includesonly activity related tointersystemcommunicationfunction (or ICF) fileswhen the I/O is for anICF device. These donot include remoteworkstation activity.

Number of writes CommPuts

Communication gets Number ofcommunicationwrites. This includesonly activity related tointersystemcommunicationfunction (or ICF) fileswhen the I/O is for anICF device. These donot include remoteworkstation activity.

Number of reads CommGets

Binary overflows Number of binaryoverflows.

Number of overflows BinOverflows

Decimal overflows Number of decimaloverflows.

Number of overflows DecOverflows

Floating pointoverflows

Number of floatingpoint overflows.

Number of overflows FPOverFlows

ResourceMonitored



Product Notes

Logical databasereads

Number of times theinternal database readfunctions were called.This does not includeI/O operations toreaders/writers or I/Ooperations caused bytheCopy Spool File(CPYSPLF) orDisplay Spooled File(DSPSPLF)command. IfSEQONLY(*YES) isspecified on theOverride withDatabase File(OVRDBF)command, thisnumber shows eachblock of records read,not the individualnumber of recordsread.

Number of recordsread or number ofblocks read

LogicalDBReads

ResourceMonitored


36 Version 3.6

Product Notes

Logical databasewrites

Number of times theinternal databasewrite functions werecalled. This does notinclude I/O operationsto readers/writers orI/O operations causedby theCopy SpoolFile (CPYSPLF) orDisplay Spooled File(DSPSPLF)command. IfSEQONLY(*YES) isspecified on theOverride withDatabase File(OVRDBF)command, thisnumber shows eachblock of records read,not the individualnumber of recordsread

Number of recordswritten or number ofblocks written

LogicalDBWrites

Miscellaneousdatabase operations

Number of update,delete,forced-end-of-data,and releaseoperations.

Number of operations MiscDBOpts

Permanent writes Number of permanentwrites.

Number of writes PermanentWrites

PAG faults Number of times theprogram access group(PAG) was referred towhen it was not inmain storage

Number of times PAGFaults

ResourceMonitored



Product Notes

Number of print lines Number of lineswritten by the job.This does not reflectwhat was actuallyprinted. Spool filescan be ended orprinted with multiplecopies.

Number of lines NumPrintLines

Number of print pages Number of print pageswritten by the job.This does not reflectwhat was actuallyprinted. Spooled filescan be ended orprinted with multiplecopies.

Number of pages NumPrintPages

Active-to-waittransactions

Number of transitionsfrom active state towait state.

Number of transitions ActiveToWait

Wait-to-ineligibletransitions

Number of transitionsfrom wait state toineligible status.

Number of transitions WaitToIneligible

Active-to-ineligibletransitions

Number of transitionsfrom active state toineligible status.

Number of transitions ActiveToIneligible

ResourceMonitored


38 Version 3.6

Product Notes

k

OS/400 Disk Monitoring Collection

The following table lists the monitoring sources for the OS/400 Dismonitoring collection:

ResourceMonitored


System ASP used Storage capacity (inMB) of the systemauxiliary storage pool(ASP1).

N/A SystemASPUsed

Percent SystemASP used

Percentage (inten-thousandths) of thesystem storage poolcurrently in use. (Forexample, 41123 wouldbe reported as 4.1123.)

N/A SystemASPUsedPct

UnprotectedStorage Used

Amount of storage inuse for temporary (inMB) objects.

N/A MaxUnprotectedUsed

Maximumunprotectedstorage used

Largest amount ofstorage (in MB) fortemporary objectsused at any one timesince the last IPL.

N/A MaxUnprotectedUsed

Mirror status Status of diskmirroring. Possiblevalues are1 (Active),2 (Resuming), and3(Suspended).

Disk armnumber (char 4)

MirrorStatus


Product Notes

Drive Capacity Number of KB ofauxiliary storageprovided on unit forthe storage of objectsand internal machinefunctions. The unitreserved system spacevalue is subtractedfrom the unit capacityto calculate this value.


Capacity

Percent DriveAvailable

Percentage ofauxiliary storage spacethat is not currentlyassigned to objects orinternal machinefunctions


DriveAvailablePct

Processor IdleLoop Count

Number of times thedisk controller passesthrough the idle loop.


IdleLoopCount

Processor IdleLoop Time

Time (in hundredths ofa microsecond) tomake one pass throughthe idle loop.


IdleLoopTime

Percent seeksgreater than 2/3

Percentage of time thedisk arm traveled morethan two-thirds of thedisk on a seek request.


PctSeeksOverTwoThirds

Percent seeks 1/3to 2/3

Percentage of time thedisk arm traveled morethan one-third of thedisk but less thantwo-thirds of the diskon a seek request.


PctSeeksThirdToTwoThirds

ResourceMonitored


40 Version 3.6

Product Notes

Percent seeks 1/6to 1/3

Percentage of time thedisk arm traveled morethan one-sixth of thedisk but less thanone-third of the diskon a seek request.


PctSeeksSixthToThird

Percent seeks1/12 to 1/6

Percentage of time thedisk arm traveled morethan one-twelfth of thedisk but less thanone-sixth of the diskon a seek request.


PctSeeksTwelfthtoSixth

Percent zeroseeks

Percentage of time thedisk arm did not moveon a seek request.


PctSeeksZero

Buffer overruns Number of times thatdata was available tobe read into the diskcontroller buffer fromthe disk, but the diskcontroller buffer stillcontained valid datathat was not retrievedby the storage devicecontroller. The diskhad to make anadditional revolutionuntil the buffer wasavailable to acceptdata.


BufferOverruns

ResourceMonitored



Product Notes

Buffer underruns Number of times thatthe disk controller wasready to transfer datato the disk on a writeoperation, but the diskcontroller buffer wasempty. The data wasnot transferred in timeby the disk IOP to thedisk controller buffer.The disk had to makean additionalrevolution awaiting thedata.


BufferUnderruns

Average queuelength

Average number of I/Ooperation waiting forservice. This valueincludes the I/Ooperation that iscurrently in progress.


AvgQueueLength

ASP number Auxiliary storage poolto which this unit iscurrently allocated.Possible values are0(not allocated),1(allocated to systemASP), and2 through16 (allocated to a userASP).


ASPNumber

ResourceMonitored


42 Version 3.6

Product Notes

OS/400 Object Monitoring Collection

The following table lists the monitoring sources for the OS/400Object monitoring collection:

OS/400 Async Monitoring Collection

The following table lists the monitoring sources for the OS/400Async monitoring collection:

ResourceMonitored


Object Size Size (in bytes) of theobject.

Qualified objectname:

Object name (char 10)

Object lib (char 10)

Object type (char 10)

ObjectSize

Object Owner AS/400 user profilethat owns the object

Qualified objectname:

Object name (char 10)

Object lib (char 10)

Object type (char 10)

ObjectOwner

ResourceMonitored


Line Status Status of the line. The possiblevalues are0 (the line is notactive) and1 (the line is active).

Line description(char 10)

LineStatus

Active Time Amount of time (in seconds) thatthe line was active (varied on).


ActiveTime


Product Notes

OS/400 Bisync Monitoring Collection

The following table lists the monitoring sources for the OS/400Bisync monitoring collection:

Line Status Description Input Name

Active Time Status of the line. The possiblevalues are0 (the line is notactive) and1 (the line is active).


LineStatus

Line Status Amount of time (in seconds) thatthe line was active (varied on).


ActiveTime

Percent DataCharactersReceived inError

Percentage of data charactersreceived with a block-checkcharacter error while in datamode.


DataCharRcvErrPct

CharactersReceived inError

Number of characters receivedwith a block-check charactererror.


CharRcvErr

NAKReceived toText Sent

Number of times the remote sta-tion did not understand the com-mand sent from the host system.


NAKRcvTextSent

Wrong ACKto Text Sent

Number of times the host systemreceived an acknowledgmentfrom a remote device that was notexpected.


WrongACKTextSent

Enquiry toText Sent

Number of times text was sent bya station and an ENQ characterwas returned (the receiving sta-tion expected some form ofacknowledgment).


EnquiryTextSent

Invalid Format Number of times one of thedelimiter characters that enclosedthe data in brackets being sent orreceived was not valid.


InvalidFormat

44 Version 3.6

Product Notes

Enquiry toACK

Number of times the remote sta-tion returned an acknowledgmentand the host system sent an ENQcharacter. This indicates that thehost station did not recognize theacknowledgment as valid.


EnquiryACK

DisconnectReceived(Abort)

Number of times the remote sta-tion issued a disconnect withabnormal end. This can occurwhen error recovery does notsucceed or the binary synchro-nous job has ended.


DiscRcvAbort

EOT Received(Abort)

Number of times end of transmis-sion was received (abnormalend).


EOTRcvAbort

DisconnectReceived(ForwardAbort)

Number of times the host stationissued a disconnect with abnor-mal end. This can occur whenerror recovery does not succeedor the binary synchronous job hasended.


DiscRcvFAbort

EOT Received(ForwardAbort)

Number of times end of transmis-sion was received (forwardabnormal end).


EOTRcvAbort

PercentageDataCharactersResent

Number of characters receivedwith a block-check charactererror.


DataCharResentPct

Line Status Description Input Name


Product Notes

OS/400 Ethernet Monitoring Collection

The following table lists the monitoring sources for the OS/400Ethernet monitoring collection:

ResourceMonitored


Line Status Status of the line. Thepossible values are0 (the lineis not active) and1 (the line isactive).


LineStatus

Active Time Amount of time (in seconds)that the line was active (variedon).


ActiveTime

SABMEFrames Sent

Number ofset-asynchronous-balanced-mode-extended frames sent.


SABMEFramesSent

SABMEFramesReceived

Number ofset-asynchronous-balanced-mode-extended frames received.


SABMEFramesRcv

N2 retryExpirationCount

Number of times the hostattempted to contact a stationand the T1 timer ended beforethe station responded.‘


NTwoRetryExpirations

T1 TimerExpirationCount

Number of times the T1 timerended.


ToneTimerExpirations

46 Version 3.6

Product Notes

OS/400 Token Ring Monitoring Collection

The following table lists the monitoring sources for the OS/400Token Ring monitoring collection:

ResourceMonitored


Line Status Status of the line. Thepossible values are0 (the lineis not active) and1 (the line isactive).


LineStatus



ActiveTime

SABMEframesreceived

Number ofset-asynchronous-balanced-mode-extended framesreceived.


SABMEFrameRcv

N2 retryexpirationcount

Number of times the hostattempted to contact a stationand the T1 timer ended beforethe station responded.


NTwoRetryExpirations

T1 timerexpirationcount

Number of times the T1 timerended.


ToneTimerExpirations

Percent routingI-frames sent

Percentage of frames (logicalling control and mediumaccess control) with routinginformation sent.


RoutingIframesSentPct

Percent routingI-framesreceived

Percentage of frames (logicallink control and mediumaccess control) with routinginformation received.


RoutingIFramesRcvPct


Product Notes

C

N

OS/400 IDLC Monitoring Collection

The following table lists the monitoring sources for the OS/400 IDLmonitoring collection:

OS/400 ISDN Monitoring Collection

The following table lists the monitoring sources for the OS/400 ISDmonitoring collection:

Percent ringutilization

Percentage of time the ringwas in use. For half-duplexlines, this is line utilization.For full-duplex lines, isin-line and out-lineutilization.


RingUtilizationPct

ResourceMonitored


ResourceMonitored




LineStatus



ActiveTime

ResourceMonitored


Line Status Status of the line. Thepossible values are0 (theline is not active) and1 (theline is active).


LineStatus

Active Time Amount of time (in seconds)that the line was active(varied on).


ActiveTime

48 Version 3.6

Product Notes

OS/400 SDLC Monitoring Collection

The following table lists the monitoring sources for the OS/400SDLC monitoring collection:

Errored seconds Number of seconds that hadat least one DTSE-in orDTSE-out error. DTSE is amaintenance channel thatmeasures the quality of theline.


ErrorSeconds

Severely erroredseconds

Number of seconds that hadmore than three DTSE-inand DTSE-out errors. DTSEis a maintenance channelthat measures the quality ofthe line.


SeveErroredSeconds

ResourceMonitored


ResourceMonitored




LineStatus

Active Time Amount of time (in seconds) thatthe line was active (varied on).


ActiveTime

Polling WaitTime

Length of time (in tenths of asecond) that the system waitedfor a response to a poll while innormal disconnect mode beforepolling the next station.


PollWaitTime


Product Notes

5

OS/400 X25 Monitoring Collection

The following table lists the monitoring sources for the OS/400 X2monitoring collection:

ResourceMonitored




LineStatus



ActiveTime

50 Version 3.6

Documents

TME 10 for AS/400 Endpoints Release Notespublib.boulder.ibm.com/tividd/td/as400/rnas400/en_US/PDF/rnas400.… · AS400 Endpoint 0.63 MB 0 MB 0 MB TME 10 Software Distribution for