HP_ACMS_for_OpenVMS_________________________________ Version 4.5 Release Notes January 2004 This document provides information about the latest release of HP ACMS for OpenVMS software that is not supplied in the user documentation. Revision/Update Information: This is a new manual. Operating System: HP OpenVMS Alpha, Version 6.2, 7.2-2, 7.3-1, or 7.3-2 HP OpenVMS VAX, Version 6.2, 7.2, or 7.3 Software Version: HP ACMS for OpenVMS, Version 4.5 Hewlett-Packard Corporation Palo Alto, California ________________________________________________________________ © 2003 Hewlett-Packard Development Company, L.P. ACMS, DECforms, DECnet, DECset, OpenVMS, PATHWORKS, and Tru64 are trademarks of the Hewlett-Packard Development Company, L.P. in the United States and other countries. Motif is a registered trademark of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. ZK6619 The HP OpenVMS documentation set is available on CD-ROM. _________________________________________________________________ Contents Preface................................................... ix 1 Features of This Release 1.1 General ACMS Features......................... 1-1 1.1.1 New Agent Monitoring Capabilities......... 1-1 1.1.2 Change in Behaviour for ACMS on OpenVMS Alpha V7.3-2.............................. 1-2 1.1.3 Monitoring the TP Desktop Connector Server or TP Web Connector Gateway............... 1-3 1.1.3.1 TP Desktop Connector.................... 1-3 1.1.3.2 TP Web Connector........................ 1-4 1.1.4 Enhanced OpenVMS and Layered Product Support................................... 1-5 1.2 Remote Manager Features....................... 1-5 1.2.1 New Features in the ACMSCFG utility and ACMSMGR Client............................ 1-5 1.2.2 RPC Version Numbering..................... 1-7 1.2.3 New Features for the ACMSSNAP utility..... 1-7 1.2.4 Web-Enabled ACMS Systems Management....... 1-8 1.2.5 New Management API's and Agent Table Descriptions.............................. 1-8 1.2.5.1 ACMSMGMT_LIST_AGENT_2................... 1-9 1.2.5.2 ACMSMGMT_SET_AGENT_2.................... 1-12 iii 2 Installation Changes 2.1 General Installation Information.............. 2-1 2.2 Installing the ACMS Remote Manager Web Agent......................................... 2-3 2.3 ACMSTART.COM Installs DECC$SHR and ACMS$TRACE_SHR.EXE............................ 2-5 2.4 ACMS Version Identification File (ACMS_ECO_LEVEL.DAT).......................... 2-6 2.5 Reinstall ACMS After OpenVMS Upgrades......... 2-6 2.6 Programming Examples on ACMS Kit.............. 2-6 2.7 Installing ACMS on OpenVMS Field test versions...................................... 2-7 3 Corrected Problems 3.1 Corrections in ACMS V4.5...................... 3-1 3.2 Corrections in ACMS V4.4B..................... 3-1 3.2.1 Remote Manager Display Changes............ 3-1 3.2.2 Waiting Task Count........................ 3-2 3.2.3 Exiting Servers log ACCVIO in SWL......... 3-2 3.3 Corrections in ACMS V4.4A..................... 3-2 3.3.1 ACMSBOOT.EXE.............................. 3-2 3.3.2 ACMSTART.COM installs ACMSBOOT.EXE with /ARB_SUPPORT.............................. 3-2 3.3.3 ACMSMGR ADD Filter/file................... 3-3 3.3.4 Add collection, no compound name.......... 3-3 3.3.5 ACMSMGR SHOW ERROR/FULL loops............. 3-3 3.3.6 Remote Manager WEB Interface Sets Boolean values even if not specified.............. 3-3 3.3.7 User must pad date........................ 3-3 3.3.8 Remote Manager May Display Incorrect Run-time Values for EXC Free and Total Server Counts............................. 3-4 3.3.9 PROXY CREDENTIALS......................... 3-4 3.3.10 TWSC Pool Minimum Free display............ 3-4 3.3.11 WBEM Show Status.......................... 3-4 3.3.12 Wrong Values in SNMP interface............ 3-5 3.3.13 EXC POOL displays......................... 3-5 3.3.14 ACC POOL values display................... 3-5 3.3.15 ACMS/SHOW APPL/CONN sometimes ACCVIOs..... 3-5 3.3.16 ACMSCFG udp_enabled and tcp_enabled reversed.................................. 3-6 iv 3.3.17 ACMSDBG - EXAMINE workspace returns an error..................................... 3-6 3.3.18 Wrong protection mask for ACMS$TRACE_SHR.EXE........................ 3-6 3.3.19 RFC1155.MY file missing................... 3-6 3.3.20 Accessing an ACMSMGR Online Help Topic from the DCL Command Line May Display Wrong Topic............................... 3-6 3.4 Corrections in ACMS V4.4...................... 3-7 3.4.1 Minimum Disk Space Needed for Installation Calculated Correctly...................... 3-7 3.4.2 SWLPROC No Longer Fails When Disk Space is Unavailable............................... 3-7 3.4.3 Starting ACMS Applications With a High MAXPROCESSCNT Value No Longer Result in a Fatal Error............................... 3-7 3.4.4 ADU LINK/STDL Command Documented.......... 3-7 3.4.5 Spaces in SET PARAMETER Commands No Longer Trigger an Access Violation............... 3-7 3.4.6 New Default QTI State for ACMSMGR START SYSTEM.................................... 3-8 3.4.7 ACMSMGR SHOW ERROR and SHOW LOG Accept OpenVMS Date_Time Keywords................ 3-8 4 Documentation Changes 4.1 Remote Manager................................ 4-1 4.1.1 ACMSMGR HELP SHOW LOG..................... 4-1 4.1.2 ACMSMGR HELP.............................. 4-1 4.1.3 Identifiers............................... 4-1 4.1.4 ACMSMGR SHOW ERROR ....................... 4-2 4.1.5 ACMSMGR SHOW GROUP ....................... 4-2 4.1.6 ACMSMGR SHOW MANAGER...................... 4-2 4.1.7 ACMSMGR SHOW VERSION...................... 4-2 4.1.8 ACMSMGR SHOW FILTER....................... 4-2 4.1.9 ACMSMGR SHOW PROCESS...................... 4-3 4.1.10 ACMSMGR SET COMMANDS...................... 4-3 4.1.11 ACMSMGR ADD and SET COMMANDS.............. 4-3 4.1.12 ACMSMGR SET EXC........................... 4-3 4.1.13 ACMS$SNMP Account Reset................... 4-4 4.1.14 ACMSMGR START SYS/NOQTI/NOTERM no longer works..................................... 4-4 v 5 Known Problems 5.1 New Problems in ACMS Version V4.5............. 5-1 5.2 New Problems in ACMS Version V4.4B............ 5-1 5.2.1 HMMO may ACCVIO if remote server host unavailable............................... 5-1 5.3 Problems Continued from ACMS Version V4.4A.... 5-1 5.3.1 Invalid Error Filter File may cause ACMS processes to loop......................... 5-2 5.3.2 Remote Manager Unable to Register with TCP/IP RPC Service........................ 5-2 5.3.3 Remote Manager Error Log and Audit Log Share Filename............................ 5-3 5.3.4 ACMSMGR SHOW COLLECTION/BRIEF May Truncate Entity Name and Storage Location.......... 5-3 5.3.5 ACMSMGR SHOW TSC, CP, EXC, and QTI Does Not Display All Channel Count Values...... 5-3 5.3.6 ACMSMGR SHOW ACC Does Not Display Runtime Values for Some OpenVMS System Parameters................................ 5-4 5.3.7 Incomplete ACMSMGR SET Commands Result in Success Message........................... 5-4 5.3.8 ACMSMGR START, STOP, and SET Commands May Result in Misleading Error Messages When Issued Without Proper Rights Identifier... 5-4 5.3.9 ACMSMGR Displays Incorrect Error Messages When Updating Global Page File Value without ACMS$MGMT_SYSUPD.................. 5-5 5.3.10 ACMSMGR ADD FILTER/FILE Incorrectly Returns an Error Message.................. 5-5 5.3.11 ACMSMGR SET COLLECTION/ID and /CONFIG Does Not Allow Changes Only to Storage Start or End Time.................................. 5-6 5.3.12 Cannot Access ACMSSNAP Online Help from the DCL Command Line...................... 5-6 5.3.13 ACMSSNAP SHOW Commands Display Only One Timestamp Value........................... 5-6 5.3.14 ACMSSNAP SHOW Commands May Overlay the Status Message with the Timestamp Value... 5-7 5.3.15 ACMSSNAP OPEN/SUMMARY Displays an Additional Row for Manager Data........... 5-7 5.3.16 Remote Manager Web Agent May Fail with Access Violation if Connection to Remote Host is Terminated Unexpectedly........... 5-7 vi 5.3.17 Cannot Set Data Snapshot Storage Times for ID and CONFIG Classes with Remote Manager Web Agent................................. 5-8 5.3.18 Remote Manager Web Agent Show Log Commands May Display Blank Page.................... 5-8 5.4 Problems Continued from ACMS Version 4.3...... 5-8 5.4.1 Incorrect Queue Order with RMS Journaling................................ 5-8 5.4.2 ADU LINK Aborts with %STR-F-INSVIRMEM or %SYSTEM-F-ACCVIO Error.................... 5-9 5.4.3 ACMS SWL Process May be Deleted........... 5-9 5.4.4 EXC Process Can Disappear without Writing Error to SWL or ATR Logs.................. 5-11 5.4.5 Hard Coded Restriction of 4095 Application Starts During an ACMS Invocation.......... 5-12 5.4.6 ACMS May Fail to Start with %SYSTEM-F-NOSUCHNODE Error................ 5-12 5.4.7 Disabling Classes Can Have Unexpected Results................................... 5-12 5.4.8 Remote Manager May Lose Some Collection Table Update Messages..................... 5-13 6 Restrictions 6.1 Restrictions in ACMS Version 4.5.............. 6-1 6.1.1 Limit of 127 CP's per node in an ACMS system.................................... 6-1 6.1.2 Using a logical name for ACMSPAR.......... 6-1 6.1.3 Remote Management Web Interface errors with Netscape 6........................... 6-2 6.2 Restrictions in ACMS Version V4.4A and earlier....................................... 6-2 6.2.1 Multithreading and Upcalls on OpenVMS Alpha Version 7.*......................... 6-2 6.2.2 Length Restriction for TCP/IP Hosts....... 6-2 6.2.3 Remote Manager and TP Connector Software May Conflict Over TCP/IP Port 1023........ 6-2 6.2.4 New ACMS Configuration File Required...... 6-3 6.2.5 Compatibility Issues with ACMS Version 4.3....................................... 6-3 6.2.6 Certain ACMS Errors Not Sent to the Remote Manager Error Log......................... 6-4 vii 6.2.7 Running Multiple Data Snapshots from Remote Manager Can Exhaust Pagefile Quota..................................... 6-4 6.2.8 Correcting an Invalid Data Snapshot Storage Location.......................... 6-4 6.2.9 Using /ACTIVE and /STORED Qualifiers with ACMSMGR SET commands...................... 6-5 6.2.10 Use ACMSSNAP SHOW Commands to Display ERROR Class Data.......................... 6-5 6.2.11 Using the ACMSSNAP SHOW/AT Command........ 6-6 6.3 Restrictions Continued from ACMS Version 4.3........................................... 6-8 6.3.1 CDD Version 6.x Support Restricted........ 6-8 6.3.2 SNMP GETNEXT Calls Return Unpredictable Results................................... 6-8 6.3.3 Remote Manager is Unusable Following TCP/IP or UCX Shutdown.................... 6-8 6.3.4 Error Message When Stopping Remote Manager................................... 6-8 6.3.5 Remote Manager Reports Error Message if it Can't Get Collection State................ 6-9 6.3.6 Remote Manager May Report ACMSTRC$_MONPROCEXST Error When Trying to Start Trace Monitor............. 6-9 6.3.7 Remote Manager Takes a Few Seconds to Start..................................... 6-10 6.3.8 ACMSMGR SHOW LOG /SINCE Qualifier Default................................... 6-10 6.3.9 Remote Manager EVENT_SEVERITY Traps Do Not Include Text Messages..................... 6-11 6.4 Restrictions Continued from ACMS Version 4.1........................................... 6-11 6.4.1 Form Name Cannot be a Logical Name When Using Multiple Submitter Platforms........ 6-12 6.4.2 CDD Restriction Initializing Fields with Strings Shorter Than Field Size........... 6-12 6.4.3 Lowercase Characters Corrupted............ 6-13 6.4.4 On OpenVMS Alpha, Agent Hangs on Second Task Startup in Task Debugger............. 6-13 6.4.5 QTI's PIOPAGE Requirements for RMS Journaling on OpenVMS Alpha............... 6-13 6.4.6 Using the Terminal User Command SELECT.... 6-14 6.4.7 Problem Phoning from DCL Servers.......... 6-14 viii 6.4.8 Submitters on VAXstation Must Have SHARE Privilege................................. 6-14 6.4.9 Task Debugger and Online Server Debugging................................. 6-15 6.4.9.1 Examining Binary Date Data Types........ 6-15 6.4.9.2 Exiting the Task Debugger with Ctrl/C or Ctrl/Y.................................. 6-15 6.4.10 Application Management Commands and Tools..................................... 6-15 6.4.10.1 ACMSPARAM May Generate an Excessive PGFLQUOTA Value for the CP Account...... 6-15 6.4.10.2 ACMSPARAM and ACMEXCPAR Do Not Support Search Lists............................ 6-16 6.4.10.3 MSS Process Pool Exhausted Errors are Reported Incorrectly.................... 6-16 6.4.11 Task Queuing Restrictions................. 6-16 6.4.11.1 Processing of Failed Queued Task Elements................................ 6-16 6.4.12 Application Definition Utility (ADU) Restrictions.............................. 6-17 6.4.12.1 ADU Migration from DMU Dictionary to CDO Dictionary.............................. 6-17 6.4.12.2 Workaround for MMS Restriction with ADU..................................... 6-18 6.4.12.3 Invalid Characters in ADU Cause ADU to Terminate with TKN_INVALID Error Message................................. 6-18 6.4.12.4 Using Search Lists to Point to Multiple Dictionaries in ADU..................... 6-19 6.4.12.5 "End of Task-Referenced Workspace Table" Error on Selection of Invalid Task...... 6-19 6.4.13 Request Interface (RI) Restrictions....... 6-19 6.4.13.1 User-Written Menus for the ACMS$RI_AGENT........................... 6-19 6.4.14 ACMS and DECforms Restrictions............ 6-20 6.4.14.1 Problems Using DECforms and TDMS in the Same ACMS Application................... 6-21 6.4.14.2 DECforms Timeout Values................. 6-21 6.4.14.3 Naming Form Image Files................. 6-21 6.4.14.4 BOLD Video Attribute Carried Forward from Menus.............................. 6-22 ix 7 General Information 7.1 Compaq DECforms Web Connector Version 3.0 Available..................................... 7-1 7.2 Periodically Delete Remote Manager Credential Files......................................... 7-1 7.3 Add SYSLCK Privilege to Accounts That Run ACMS Processes..................................... 7-1 7.4 Setting Remote Manager Stacksize Parameters... 7-2 7.5 ACMSTRC$_NOSUCHPGM Warning Message............ 7-2 7.6 ACMS Does Not Support Pixel-Based Display Devices....................................... 7-3 7.7 ACMS$TRACE_SHR.EXE Cannot be Installed Resident...................................... 7-3 7.8 Remote Manager Shutdown Causes Accounting Records to be Written......................... 7-3 7.9 Logical Names for Workspace Pool Sizes in EXC........................................... 7-4 7.10 Use Logical Names for File Allocation in ACMSATL....................................... 7-5 7.11 New Logical Name Must be Defined for RI Agents and User-Written Agents....................... 7-5 7.12 Cache Directories for Application and Forms Files Should Not Be Write Protected........... 7-7 7.13 No Longer Necessary to Store ACMS Definitions in CDD........................................ 7-7 7.14 PATROL Knowledge Modules...................... 7-8 8 Guidelines for Reporting an ACMS Problem 8.1 Calling in a Problem to Your HP Support Representative................................ 8-1 8.2 Additional ACMS Information You Can Collect... 8-4 8.2.1 Reporting Problems with ACMS Utilities.... 8-6 8.2.2 Reporting Problems with the ACMS Run-Time System.................................... 8-7 8.2.3 Reporting Problems with the Remote Manager Web Agent................................. 8-10 x Tables 2-1 Alpha Kits................................ 2-1 2-2 VAX Kits.................................. 2-2 xi _________________________________________________________________ Preface These notes provide the following information about the Version 4.5 release of the HP ACMS for OpenVMS software: o New Features o Installation o Corrected problems o Documentation Changes o Known problems o Restrictions o General information o Guidelines for reporting ACMS problems Intended Audience Read this document if you are responsible for installing ACMS software or designing, implementing, or managing ACMS applications. This document supplements and contains information not found in the ACMS documentation. Structure of This Document This document has the following structure: Chapter 1 Gives a brief introduction to the release notes. Chapter 2 Describes any installation changes for this version of ACMS. ix Chapter 3 Describes problems that have been fixed with this version of ACMS. Chapter 4 Describes changes to the documentation. Chapter 5 Lists problems that can occur with this version of ACMS. Chapter 6 Lists any restrictions. Chapter 7 Provides general release information. Chapter 8 Describes how to report a software problem. Related Documents The following table lists the books in the HP ACMS for OpenVMS documentation set. ___________________________________________________________ ACMS_Information________Description________________________ Compaq ACMS for Information about the latest OpenVMS Version 4.4 release of the software Release Notes+ Compaq ACMS for Description of installation OpenVMS Version 4.4 requirements, the installation Installation Guide procedure, and postinstallation tasks. Compaq ACMS for Overview of ACMS software and OpenVMS Getting documentation. Started Tutorial for developing a simple ACMS application. Description of the AVERTZ sample application. Compaq ACMS for Description of how to design an OpenVMS Concepts and ACMS application. Design Guidelines +Available_online_only.____________________________________ x ___________________________________________________________ ACMS_Information________Description________________________ Compaq ACMS for Description of how to write task, OpenVMS Writing task group, application, and menu Applications definitions using the Application Definition Utility. Description of how to write and migrate ACMS applications on an OpenVMS Alpha system. Compaq ACMS for Description of how to write OpenVMS Writing programs to use with tasks and Server Procedures how to debug tasks and programs. Description of how ACMS works with the APPC/LU6.2 programming interface to communicate with IBM CICS applications. Description of how ACMS works with third-party database managers, with Oracle used as an example. Compaq ACMS for Description of using Systems OpenVMS Systems Interface (SI) Services to submit Interface Programming tasks to an ACMS system. Compaq ACMS for Reference information about the ADU OpenVMS ADU Reference commands, phrases, and clauses. Manual Compaq ACMS for List of ACMS syntax with brief OpenVMS Quick descriptions. Reference Compaq ACMS for Description of authorizing, OpenVMS Managing running, and managing ACMS Applications applications, and controlling the ACMS system. Compaq ACMS for Description of the features of OpenVMS Remote the Remote Manager for managing Systems Management ACMS systems, how to use the Guide features, and how to manage the Remote Manager. Online help+ Online help about ACMS and its utilities. +Available_online_only.____________________________________ ___________________________________________________________ xi For additional information on the compatibility of other software products with this version of ACMS, refer to the HP ACMS for OpenVMS Software Product Description (SPD 25.50.xx). For additional information about HP OpenVMS products and services, access the following OpenVMS World Wide Web address: http://www.hp.com/go/openvms Reader's Comments HP welcomes your comments on this manual. Please send comments to either of the following addresses: Internet openvmsdoc@hp.com Mail Hewlett-Packard Company OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation Use the following World Wide Web address for information about how to order additional documentation: http://www.hp.com/go/openvms/doc/order Conventions The following conventions are used in this manual: Ctrl/x A sequence such as Ctrl/x indicates that you must press and hold the key labeled Ctrl while you press another key or a pointing device button. PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button. xii In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets rather than a box. . . . A horizontal ellipsis in examples indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. . A vertical ellipsis indicates the omission . of items from a code example or command . format; the items are omitted because they are not important to the topic being discussed. Monospace text Monospace type indicates code examples and interactive screen displays. In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example. In the HTML version of this document, this text style may appear as italics. - A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line. xiii numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. bold text Bold text represents the introduction of a new term or the name of an argument, an attribute, or a reason. In the HTML version of this document, this text style may appear as italics. italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predefined code for the device type). UPPERCASE Uppercase text indicates the name of a routine, the name of a file, the name of a file protection code, or the abbreviation for a system privilege. In command format descriptions, uppercase text is an optional keyword. UPPERCASE In command format descriptions, uppercase text that is underlined is a required. You must include it in the statement if the clause is used. lowercase In command format descriptions, a lowercase word indicates a required element. xiv In command format descriptions, lowercase text in angle brackets indicates a required clause or phrase. ( ) In command format descriptions, parentheses indicate that you must enclose the options in parentheses if you choose more than one. [| |] In command format descriptions, vertical bars within square brackets indicate that you can choose any combination of the enclosed options, but you can choose each option only once. {| |} In command format descriptions, vertical bars within braces indicate that you must choose one of the options listed, but you can use each option only once. References to Products The ACMS documentation set often refers to products by abbreviated names. The following product abbreviations are used in this documentation set: ___________________________________________________________ Abbrev_____Product_________________________________________ ACMS HP ACMS for OpenVMS Alpha, and HP ACMS for OpenVMS VAX Ada HP Ada for OpenVMS Alpha Systems, and HP Ada for OpenVMS VAX Systems BASIC HP BASIC for OpenVMS, and HP BASIC for OpenVMS C HP C for OpenVMS Alpha Systems, and HP C for OpenVMS VAX Systems CDD Oracle CDD/Administrator, and Oracle CDD/Repository COBOL HP COBOL for OpenVMS Alpha Systems, and HP COBOL for OpenVMS VAX Systems DATATRIEVE HP DATATRIEVE for OpenVMS Alpha, and HP DATATRIEVE for OpenVMS VAX xv ___________________________________________________________ Abbrev_____Product_________________________________________ DBMS Oracle CODASYL DBMS DECforms HP DECforms for OpenVMS FORTRAN HP Fortran for OpenVMS Alpha Systems, and HP Fortran for OpenVMS VAX Systems OpenVMS The HP OpenVMS Alpha operating system, and the HP OpenVMS VAX operating system Pascal HP Pascal for OpenVMS Alpha, and HP Pascal for OpenVMS VAX PL/I PL/I for OpenVMS Systems Rdb Oracle Rdb SQL The SQL interface to Oracle Rdb TDMS_______HP_TDMS_for_OpenVMS_VAX_________________________ xvi 1 _________________________________________________________________ Features of This Release HP ACMS for OpenVMS, Version 4.5 includes corrections made to the product since the release of ACMS Version 4.4/4.4A/4.4B and offers the following new features for ACMS and the Remote Manager. 1.1 General ACMS Features This section describes the general features included in ACMS Version 4.5. 1.1.1 New Agent Monitoring Capabilities ACMS V4.5 provides additional monitoring capabilities within the ACMS Remote Manager for user defined agents and agents provided by HP and other vendors. Data that is collected and monitored includes: Process quotas Active tasks Total tasks executed TDMS (Requests, Reads, Writes, Cancels) DECforms (Enable, Disable, Send, Receive, Transceive) MSS Process Pool information In addition, there are 9 user-defined (3 date/time, 6 integer) data items that can be read or written by using the RPC or SNMP interfaces. Features of This Release 1-1 Features of This Release 1.1 General ACMS Features To use these new monitoring capabilities, you do not have to recompile or relink any agent programs. The monitoring of these agent processes is done through the use of logical names. When the logical names are used, the ACMS Systems Interface will automatically notify the ACMS Remote Manager that this agent process is to be monitored. There are 2 logicals names: ACMS$RM_AGENT_INIT - this is the primary logical name used. Define this logical name to any value. When the first task submitter signs in, the ACMS Remote Manager interface will be initialized for this process. The Remote Manager routines will collect the data associated with the agent. This data can be seen using the command: $ ACMSMGR SHOW AGENT When the last task submitter signs out, the Remote Manager will terminate the data collection. Use the logical name ACMS$RM_AGENT_KEEP to force the Remote Manager to continue to collect data. ACMS$RM_AGENT_KEEP - This logical name forces the ACMS Remote Manager to continue to collect data even though there are no task submitters signed in for this agent. Define this logical to any value. 1.1.2 Change in Behaviour for ACMS on OpenVMS Alpha V7.3-2 There are 2 changes of behavior noticed when ACMS is run on OpenVMS Alpha V7.3-2. 1. If the account specified in ACMSGEN for ACC_USERNAME has expired: In versions prior to OpenVMS Alpha V7.3-2, the error would be reported as: $ acms/start system/noterm %ACMSOPR-E-STRTSYSERR, Error while attempting to START SYSTEM -ACMSOPS-E-ACCDIED, ACC died unexpectedly. -LOGIN-F-ACNTEXPIR, your account has expired; contact your system manager %ACMSOPR-E-ERROR, Some operations may not have been performed 1-2 Features of This Release Features of This Release 1.1 General ACMS Features In OpenVMS V7.3-2 the error is reported as: $ acms/start system/noterm %ACMSOPR-E-STRTSYSERR, Error while attempting to START SYSTEM -ACMSOPS-E-ACCDIED, ACC died unexpectedly. %ACMSOPR-E-ERROR, Some operations may not have been performed The exact error can be seen in the accounting file. No errors are report in the ACMS audit log or in the SWL file. 2. If the account specified for an application does not exist, the application will not startup. In versions prior to OpenVMS Alpha V7.3-2, the error would be reported as: $ acms/start appl foo %ACMSOPR-E-STRTAPLERR, Error while attempting to START APPLICATION FOO -ACMSACC-E-APPLTERM, EXC process for application FOO terminated -LOGIN-F-NOSUCHUSER, no such user %ACMSOPR-E-ERROR, Some operations may not have been performed In OpenVMS V7.3-2 the error is reported as: $ acms/start appl foo %ACMSOPR-E-STRTAPLERR, Error while attempting to START APPLICATION FOO -ACMSACC-E-APPLTERM, EXC process for application FOO terminated %ACMSOPR-E-ERROR, Some operations may not have been performed The exact error can be seen in the accounting file. The SWL file will also have a log of the failure. 1.1.3 Monitoring the TP Desktop Connector Server or TP Web Connector Gateway 1.1.3.1 TP Desktop Connector A new feature in ACMS V4.5 allows the Remote Manager to monitor user-written and HP supplied agents. To allow the ACMS Remote Manager to monitor the TP Desktop Connector (ACMSDI$SERVER), the file SYS$STARTUP:ACMSDI$STARTUP.COM needs to be modified as follows: Features of This Release 1-3 Features of This Release 1.1 General ACMS Features Edit SYS$STARTUP:ACMSDI$STARTUP.COM and search for the lines: $ if _server_name .nes. "" $ then $ write tmpstartup "$ define/process ACMSDI$SERVER_NAME ", _server_name $ endif Insert the following before the lines above: $ write tmpstartup "$ define/process ACMS$RM_AGENT_INIT ", "T" $ write tmpstartup "$ define/process ACMS$RM_AGENT_KEEP ", "T" The ACMSDI$SERVER must be restarted after the changes are made. You should save a copy of this file. If you re-install or update the TP Desktop Connector, the installation procedure will replace the file that you have edited. 1.1.3.2 TP Web Connector To allow the ACMS Remote Manager to monitor the TP Web Connector (ACMSDA$GATEWAY), the file SYS$STARTUP:ACMSDA$STARTUP.COM needs to be modifed as follows: Edit SYS$STARTUP:ACMSDA$STARTUP.COM and search for the lines: $ write tmpstartup "$ define/process ACMSDI$ACMS_ERROR_MSG ", _acms_error_msg $ write tmpstartup "$ define/process ACMSDI$PASSWORD_EXP ", _password_exp $ write tmpstartup "$ define/process ACMSDI$INTEGRITY_CHECK ", _integrity_check Inserver the following after the lines above: $ write tmpstartup "$ define/process ACMS$RM_AGENT_INIT ", "T" $ write tmpstartup "$ define/process ACMS$RM_AGENT_KEEP ", "T" The ACMSDA$GATEWAY must be restarted after the changes are made. You should save a copy of this file. If you re-install or update the TP Web Connector, the installation procedure will replace the file that you have edited. 1-4 Features of This Release Features of This Release 1.1 General ACMS Features 1.1.4 Enhanced OpenVMS and Layered Product Support Version 4.5 provides support for ACMS with the following versions of the HP OpenVMS operating system and related layered products: o HP OpenVMS Alpha Versions 6.2, 7.2-2, 7.3-1, 7.3-2 o HP OpenVMS VAX Versions 6.2, 7.2, and 7.3 o Oracle CDD/Repository Version 7.0 or later o Oracle Rdb Version 7.0 or later o Oracle CODASYL DBMS Version 7.0 or later o HP DECnet Phase V for OpenVMS (with Phase IV protocols) o HP DECforms Version 3.3 or later 1.2 Remote Manager Features This section describes the general features included in the ACMS Remote Manager Version 4.5. 1.2.1 New Features in the ACMSCFG utility and ACMSMGR Client To support the new agent monitoring capabilities, the ACMSCFG utility and ACMSMGR client have been enhanced. - ACMSCFG - ACMS Remote Manager Configuration Utility An AGENT is now a valid entity for these commands: - add collection - delete collection - set collection A new command, SET PARAMETER/MAX_AGENTS=x - to set the value for the number of agents to be monitored. Default is 2, minimum is 1. This value sets the size of the table used to monitor agents. If the value is set too low, newly created agents will not be monitored. - ACMSMGR - ACMS Remote Manager Client Features of This Release 1-5 Features of This Release 1.2 Remote Manager Features An AGENT is now a valid entity for these commands: - add collection - delete collection - set collection New commands to show the data collected for agents. usage: $acmsmgr show agent (qualifier) Qualifiers Comment ------------------------------------------------------------------------------------ [M] = Mandatory (* = abbreviation) /act*ive (applies to CONFIG class brief display; default=active) /all (shows stopped process data if available) /br*ief (default when a class is specified; ignored when no class is speci /[CONFIG,ERROR,ID,POOL,RUNTIME] (default=if no class is specified, all are shown) /fu*ll (default when no class is specified) /interv*al=value (specified as number of seconds) /out=[filespec,logical_name] (default=sys$output) /process*_name=proc_name (default=*) /store*d (applies to CONFIG class brief display; default=active) /node=value (if ACMS$MGMT_SERVER_NODE not defined) /user=value (if ACMS$MGMT_USER not defined) usage: $acmsmgr set agent (qualifier) Qualifiers Comment ------------------------------------------------------------------------------------ [M] = Mandatory (* = abbreviation) 1-6 Features of This Release Features of This Release 1.2 Remote Manager Features [M] /pid=value hexadecimal value of the pid /ast*lm=value stored value only /bio*lm=value stored value only /byt*lm=value stored value only /dio*lm=value stored value only /enq*lm=value stored value only /fill*m=value stored value only /pgf*lquota=value stored value only /tqe*lm=value stored value only /wsd*ef=value stored value only /wse*xtent=value stored value only /wsq*uota=value stored value only /log /node=value (if ACMS$MGMT_SERVER_NODE not defined) /user=value (if ACMS$MGMT_USER not defined) - ACMS HMMO - ACMS WBEM Interface New commands to support the display of agent data. 1.2.2 RPC Version Numbering Two new calls have been added to the RPC API - ACMSMGMT_ LIST_AGENT_2 and ACMSMGMT_SET_AGENT_2, also one new configuration parameter has been added for Agents - MAX_ AGENTS. The RPC version has not changed and remains at V4.4 for ACMS V4.5. The new calls and parameter are only supported on ACMS V4.5 systems. ACMS V4.4 systems will function (minus the new functionality) with ACMS V4.5 systems. In ACMS V5.0 the RPC numbering might change completely. 1.2.3 New Features for the ACMSSNAP utility There is one new logical name for ACMSSNAP: ACMS$MGMT_SNAP_MAX_AGENTS - This logical determines the number of different AGENT processes that can be read while the snapshot file is open. AGENT data is stored internally in a statically sized table, with one row for each unique AGENT process name found. If there is insufficient space in the table to Features of This Release 1-7 Features of This Release 1.2 Remote Manager Features hold all the AGENT records in the file, AGENT records are discarded. There is one new qualifier for the ACMSSNAP OPEN command: /MAX_AGENTS This qualifier determines the number of different AGENT processes that can be read while the file is open. AGENT data is stored internally in a statically sized table, with one row for each unique AGENT process name found. If there is insufficient space in the table to hold all the AGENT records in the file, AGENT records are discarded. This qualifier overrides the ACMS$MGMT_SNAP_MAX_AGENTS logical name, which is an alternative way of specifying this value. There is one new entity that can be specified for the ACMSSNAP SHOW command: AGENT 1.2.4 Web-Enabled ACMS Systems Management The ACMS HMMO for V4.5 is built using the HP INSIGHT MANAGEMENT AGENTS V3.0. It is not compatible with previous versions of the MANAGEMENT AGENTS software. 1.2.5 New Management API's and Agent Table Descriptions New Management API's and Agent Table Descriptions (Remote Systems Management Guide - Chapters 8 and 9) There are 2 new Management API's that are intended to be called from ONC RPC clients: - ACMSMGMT_LIST_AGENT_2 - ACMSMGMT_SET_AGENT_2 1-8 Features of This Release Features of This Release 1.2 Remote Manager Features 1.2.5.1 ACMSMGMT_LIST_AGENT_2 ACMS Remote Manager clients call this procedure to obtain a list of Agent Process table entries. -------------------------------------------------------------------------------- Format agent_data_list *acmsmgmt_list_agent_2(agent_sel_struct *sub_rec, CLIENT *cl) -------------------------------------------------------------------------------- Parameters sub_rec Type: agent_sel_struct Access: Read Mechanism: By reference Usage: Structure that contains the following client authorization information. client_id Type: Integer Access: Read Mechanism: By value Usage: If explicit authentication is being used, a valid client ID must be provided. If the value for client_id is 0, proxy access is used. Client_id is obtained by calling the acms$mgmt_get_creds procedure. proc_name Type: String Access: Read Mechanism: By value Usage: String that lists the OpenVMS process name for each Agent. cl Type: CLIENT * Access: Read Mechanism: By value Usage: Pointer to an RPC client handle previously obtained by calling the RPC routine CLNT_CREATE. -------------------------------------------------------------------------------- Return Value Type: agent_data_list Access: Write Mechanism: By reference Usage: Pointer to a record that contains a union consisting of either a failure code or a pointer to a structure of type agent_data_list, which contains the start of a linked list of records. The following are the contents of this union: Features of This Release 1-9 Features of This Release 1.2 Remote Manager Features rc Type: Integer Access: Write Mechanism: By value Usage: Failure return code. list Type: agent_list Access: Write Mechanism: By reference Usage: Start of linked list. Pointer to a structure of Agent table record, and a forward pointer to the next node in the linked list. The following are the contents of this structure: pNext Type: agent_list Access: Write Mechanism: By value Usage: Start of linked list. Pointer to a structure of type coll_list. agent_data Type: agent_rec_r Access: Write Mechanism: By reference Usage: Agent table row. Agent table fields. -------------------------------------------------------------------------------- Description The ACMSMGMT_LIST_AGENT_2 procedure returns a linked list of Agent table rows. All Agent table rows are returned in each call. Records are returned sequentially from the table, beginning at the start of the table. Entire table rows are returned. If the ACMS run-time system is not running when this call is issued, the Remote Manager returns the MGMT_NOT_MAPPED error code. Rows in the Agent table are subject to reuse. Rows are assigned round-robin, and are not cleared until they have been reassigned. So some rows may contain data for inactive Agents. It is the caller's responsibility to examine the record_state field to determine whether this row belongs to an active (record_state field is MGMT_VALID) or inactive (record_state field is MGMT_INACTIVE) Agent, and to process the row accordingly. --------------------------- 1-10 Features of This Release Features of This Release 1.2 Remote Manager Features Example: int list_agent_data(int client_id,CLIENT *cl) { static char c_all_agents[2] = "*"; agent_data_list *agent_data; agent_link *nl; static struct agent_sel_struct sub_rec; int status; sub_rec.client_id = client_id; sub_rec.proc_name = c_all_agents; agent_data = acmsmgmt_list_agent_2(&sub_rec,cl); if (!agent_data) { printf("\n RPC Call to get agent data failed"); return(MGMT_FAIL); } if (agent_data->status == MGMT_FAIL) { if (agent_data->agent_data_list_u.rc == MGMT_NOMORE_DATA) { printf("\n No agent data found"); xdr_free(xdr_agent_data_list, agent_data); free(agent data); return(MGMT_FAIL); } printf("\n Call to get agent data failed, returning status code %d", agent_data->agent_data_list_u.rc); status = agent_data->agent_data_list_u.rc; xdr_free(xdr_agent_data_list, agent_data); free(agent_data); return(status); } if (agent_data->status == MGMT_WARN) printf("\n ** Warning, some data may be from inactive processes **"); for (nl = agent_data->agent_data_list_u.list; nl != NULL; nl = nl->pNext) { if (nl->agent_data.record_state == MGMT_INACTIVE) printf("\n INACTIVE "); else printf("\n "); printf(" PID: %8X Process Name: %-s", nl->agent_data.pid, nl->agent_data.process_name); } Features of This Release 1-11 Features of This Release 1.2 Remote Manager Features printf("\n End of data"); xdr_free(xdr_agent_data_list, agent_data); free(agent_data); return(0); } 1.2.5.2 ACMSMGMT_SET_AGENT_2 This procedure modifies the ACMS Agent Process class attributes. -------------------------------------------------------------------------------- Format agent_status_rec *acmsmgmt_set_agent_2(agent_config_rec *agent_cfg_rec,CLIENT *cl) -------------------------------------------------------------------------------- set_struct Type: agent_config_rec Access: Read Mechanism: By reference Usage: Structure that contains the following client identification and Agent table fields. client_id Type: Integer Access: Read Mechanism: By value Usage: If explicit authentication is being used, a valid client ID must be provided. If the value of client_id is 0, proxy access is used. Client_id is obtained by calling the acms$mgmt_get_creds procedure. current_sw Type: Integer Access: Read Mechanism: By value Usage: Update current values flag, required to be set to 1. pid Type: Integer Access: Read Mechanism: By reference Usage: PID of the Agent process to be updated, required. 1-12 Features of This Release Features of This Release 1.2 Remote Manager Features user1_time, user2_time, user3_time Type: Null-terminated string Access: Read Mechanism: By reference Usage: Time fields provided for use by programmers. Pointers to character strings representing VMS time (for example, "18-NOV-2003 00:00:00.00"). If these fields are not to be set, the fields should be initialized to a null string (""). See the note at the end of this section for a discussion of these fields. user1_data, user2_data, user3_data, user4_data, user5_data, user6_data Type: Integer Access: Read Mechanism: By value Usage: Integer fields provided for use by programmers. astlm, biolm, bytlm, diolm, enqlm, fillm, pgflquota, tqelm, wsdefault, wsextent, wsquota Type: Integer Access: Read Mechanism: By value Usage: Quota values to be updated. These fields correspond to the stored fields of the same names in the Agent table (for example, astlm will update astlm_stored). See the note at the end of this section for a discussion of these fields. cl Type: CLIENT * Access: Read Mechanism: By value Usage: Pointer to an RPC client handle previously obtained by calling the RPC routine CLNT_CREATE. -------------------------------------------------------------------------------- Return Value Type: agent_status_rec Access: Write Mechanism: By reference Usage: Pointer to a record that contains a union consisting of either a failure code or a structure of type agent_config_rec_out, which contains status codes for each quota field, as well as a linked list of status messages associated with the update. The following are the contents of this union: rc Type: Integer Access: Write Mechanism: By value Usage: Failure return code. Features of This Release 1-13 Features of This Release 1.2 Remote Manager Features data, data_warn Type: agent_config_rec_out Access: Write Mechanism: By value Usage: Structure containing fields corresponding to the quota fields in the agent_config_rec structure, as well as a linked list of status messages associated with the update. The following are the contents of this structure: astlm, biolm, bytlm, diolm, enqlm, fillm, pgflquota, tqelm, wsdefault, wsextent, wsquota Type: Integer Access: Write Mechanism: By value Usage: Status fields corresponding to the quota fields in the input argument. cmd_output Type: Dcl_list Access: Write Mechanism: By reference Usage: Pointer to a linked list of records containing status messages related to the failure of any updates. This structure contains the following fields: dcl_msg Type: Null-terminated string Access: Write Mechanism: By reference Usage: The status message. pNext Type: Dcl_list Access: Write Mechanism: By reference Usage: Pointer to the next node in the linked list. -------------------------------------------------------------------------------- Note: This procedure requests updates to ACMS Agent Config class fields contained in the Agent table at the end of this section. Note that the Agent table contains both active and stored quota values; however, only the stored fields can be changed. -------------------------------------------------------------------------------- Example: int set_agent_data(int client_id,CLIENT *cl) { 1-14 Features of This Release Features of This Release 1.2 Remote Manager Features static char null_time[] = ""; static agent_config_rec set_struct; agent_status_rec *ret_struct; dcl_link *nl; static char time1[MGMT$S_TIME_A+1] = "18-NOV-1858 00:00:00.00"; static char time2[MGMT$S_TIME_A+1] = "19-NOV-1858 00:00:00.00"; static char time3[MGMT$S_TIME_A+1] = "20-NOV-1858 00:00:00.00"; // Initialize the agent config record. memset(&set_struct,-1,sizeof(set_struct)); set_struct.user1_time = null_time; set_struct.user2_time = null_time; set_struct.user3_time = null_time; set_struct.pid = 0x45400931; set_struct.client_id = client_id; set_struct.current_sw = 1; set_struct.astlm = 500; set_struct.user1_time = time1; set_struct.user2_time = time2; set_struct.user3_time = time3; set_struct.user1_data = 1; set_struct.user2_data = 2; set_struct.user3_data = 3; set_struct.user4_data = 4; set_struct.user5_data = 5; set_struct.user6_data = 6; ret_struct = acmsmgmt_set_agent_2(&set_struct,cl); if (!ret_struct) { printf("\n Call to modify Agent failed"); return(MGMT_FAIL); } if (ret_struct->status != MGMT_SUCCESS) printf("\n Call to modify Agent returned the following warnings or errors\n"); else printf("\n Call to modify Agent completed\n"); for (nl = ret_struct->agent_status_rec_u.data.cmd_output; nl != NULL; nl = nl->pNext) printf("\n %s",nl->dcl_msg); Features of This Release 1-15 Features of This Release 1.2 Remote Manager Features xdr_free(xdr_agent_status_rec, ret_struct); free(ret_struct); return(0); } 1-16 Features of This Release Features of This Release 1.2 Remote Manager Features Agent Table The Agent table contains a row for each Agent Process running on the node. Collection Class Field Data Type SNMP Access RPC Access Dynamic ID id_coll_state integer R R ID process_name string R R ID pid integer R R ID start_time time R R ID end_time time R R ID user_name string R R ID acms_state integer R R CONFIG cfg_coll_state integer R R CONFIG astlm_active integer R R CONFIG astlm_stored integer RW RW CONFIG biolm_active integer R R CONFIG biolm_stored integer RW RW CONFIG bytlm_active integer R R CONFIG bytlm_stored integer RW RW CONFIG diolm_active integer R R CONFIG diolm_stored integer RW RW CONFIG enqlm_active integer R R CONFIG enqlm_stored integer RW RW CONFIG fillm_active integer R R CONFIG fillm_stored integer RW RW CONFIG pgflquota_active integer R R CONFIG pgflquota_stored integer RW RW CONFIG tqelm_active integer R R CONFIG tqelm_stored integer RW RW CONFIG wsdefault_active integer R R CONFIG wsdefault_stored integer RW RW CONFIG wsextent_active integer R R CONFIG wsextent_stored integer RW RW CONFIG wsquota_active integer R R CONFIG wsquota_stored integer RW RW Features of This Release 1-17 Features of This Release 1.2 Remote Manager Features RUNTIME rt_coll_state integer R R RUNTIME decnet_object integer R R RUNTIME active_task_calls gauge R R RUNTIME current_attached_terms gauge R R RUNTIME active_tdms_menu_reqs gauge R R RUNTIME total_tdms_menu_reqs integer R R RUNTIME active_tdms_reqs gauge R R RUNTIME active_tdms_msgrd gauge R R RUNTIME active_tdms_msgwt gauge R R RUNTIME active_tdms_cancel gauge R R RUNTIME total_tdms_reqs integer R R RUNTIME total_tdms_msgrd integer R R RUNTIME total_tdms_msgwt integer R R RUNTIME total_tdms_cancel integer R R RUNTIME active_vf_menu_reqs gauge R R RUNTIME total_vf_menu_reqs integer R R RUNTIME active_vf_reqs gauge R R RUNTIME active_vf_enable gauge R R RUNTIME active_vf_disable gauge R R RUNTIME active_vf_cancel gauge R R RUNTIME active_vf_sends gauge R R RUNTIME active_vf_receive gauge R R RUNTIME active_vf_xceive gauge R R RUNTIME total_vf_reqs integer R R RUNTIME total_vf_enable integer R R RUNTIME total_vf_disable integer R R RUNTIME total_vf_cancel integer R R RUNTIME total_vf_send integer R R RUNTIME total_vf_receive integer R R RUNTIME total_vf_xceive integer R R RUNTIME total_tasks_executed integer R R RUNTIME user1_time time RW RW RUNTIME user2_time time RW RW RUNTIME user3_time time RW RW RUNTIME user1_data integer RW RW RUNTIME user2_data integer RW RW RUNTIME user3_data integer RW RW RUNTIME user4_data integer RW RW RUNTIME user5_data integer RW RW RUNTIME user6_data integer RW RW RUNTIME astlm_current gauge R R RUNTIME biolm_current gauge R R RUNTIME bytlm_current gauge R R 1-18 Features of This Release Features of This Release 1.2 Remote Manager Features RUNTIME channelcnt_current gauge R R RUNTIME diolm_current gauge R R RUNTIME enqlm_current gauge R R RUNTIME fillm_current gauge R R RUNTIME pgflquota_current gauge R R RUNTIME wssize_current gauge R R RUNTIME tqelm_current gauge R R POOL pool_coll_state integer R R POOL mss_process_total integer R R POOL mss_process_free min gauge R R POOL mss_process_largest min gauge R R POOL mss_process_failures integer R R POOL mss_process_garbage integer R R ERROR error_coll_state integer R R ERROR error_count integer R R ERROR last_error_message integer R R ERROR time_of_last_error time R R Agent Table Field Descriptions The following are descriptions of the fields in the Agent table: - record_state The current state of this table entry. Valid states are VALID (the process is currently running and maintaining this table entry) or INACTIVE (the process is no longer running). Inactive rows are subject to reuse. - id_coll_state The current collection state for this class and this process. Collection states can be modified by modifying entries in the Collection table. If this field is set to DISABLED, the process is not currently collecting data for the fields in this class. Any field values reflect activity during a prior period when collection was enabled. - process_name Features of This Release 1-19 Features of This Release 1.2 Remote Manager Features The OpenVMS process name for the process. - pid The OpenVMS process identifier for the process. - start_time Date and time the process was started. - end_time Date and time the process ended. If the process has not yet ended, this field is null. - user_name The OpenVMS account under which the process is running. - acms_state The ACMS state of the process. - cfg_coll_state Collection states can be modified by modifying entries in the Collection table. If this field is set to DISABLED, the process is not currently collecting data for the fields in this class. Any field values reflect activity during a prior period when collection was enabled. astlm_active, biolm_active, bytlm_active, diolm_active, enqlm_active, fillm_active, pgflquota_active, tqelm_ active, wsdefault_active, wsextent_active, wsquota_ active The default value of the related OpenVMS process quota. This is the value of the quota when the Agent process was started. astlm_stored, biolm_stored, bytlm_stored, diolm_stored, enqlm_stored, fillm_stored, pgflquota_stored, tqelm_ stored, wsdefault_stored, wsextent_stored, wsquota_ stored The value of the related process quota currently 1-20 Features of This Release Features of This Release 1.2 Remote Manager Features stored in the OpenVMS system user authorization file (SYSUAF.DAT). - rt_coll_state The current collection state for this class and this process. Collection states can be modified by modifying entries in the Collection table. If this field is set to DISABLED, the process is not currently collecting data for the fields in this class. Any field values reflect activity during a prior period when collection was enabled. - decnet_object If the process has a current DECnet object, the value of this field is STARTED. Otherwise, the value is STOPPED. If the DECnet object is stopped (and the runtime_coll_ state is enabled for this process), either distributed processing has not been enabled (that is, the node_ name parameter in the ACMSGEN file is NULL) or there is currently a problem with DECnet. Also, check the ACC CONFIG parameters node_name_active and node_name_stored to determine the current status of the ACMSGEN node_name field. - active_task_calls The number of task calls currently being executed by all users of the Agent. - current_attached_terms The number of terminals currently attached to the Agent. - active_tdms_menu_reqs The number of TDMS menu requests currently being executed by all users of the Agent. - total_tdms_menu_reqs Features of This Release 1-21 Features of This Release 1.2 Remote Manager Features The total number of TDMS menu requests executed by all users of the Agent since the Agent was started. - active_tdms_reqs The number of TDMS requests of all types currently being executed by all users of the Agent. - active_tdms_msgrd The number of TDMS read messages currently being executed by all users of the Agent. - active_tdms_msgwt The number of TDMS write messages currently being executed by all users of the Agent. - active_tdms_cancel The number of TDMS cancels currently being executed by all users of the Agent. - total_tdms_reqs The total number of TDMS requests (menu and exchange) executed by all users of the Agent since the Agent was started. - total_tdms_msgrd The total number of TDMS read messages executed by all users of the Agent since the Agent was started. - total_tdms_msgwt The total number of TDMS write messages executed by all users of the Agent since the Agent was started. - total_tdms_cancel 1-22 Features of This Release Features of This Release 1.2 Remote Manager Features The total number of TDMS cancels executed by all users of the Agent since the Agent was started. - active_vf_menu_reqs The number of DECforms menu requests currently being executed by all users of the Agent. - total_vf_menu_reqs The total number of DECforms menu requests executed by all users of the Agent since the Agent was started. - active_vf_reqs The number of DECforms requests of all types currently being executed by all users of the Agent. - active_vf_enable The number of DECforms enable requests currently being executed by all users of the Agent. - active_vf_disable The number of DECforms disable requests currently being executed by all users of the Agent. - active_vf_cancel The number of DECforms cancel requests currently being executed by all users of the Agent. - active_vf_send The number of DECforms requests currently being executed by all users of the Agent. - active_vf_receive The number of DECforms receive requests currently being executed by all users of the Agent. Features of This Release 1-23 Features of This Release 1.2 Remote Manager Features - active_vf_xceive The number of DECforms enable transceives currently being executed by all users of the Agent. - total_vf_reqs The total number of DECforms requests of all types executed by all users of the Agent since the Agent was started. - total_vf_enable The total number of DECforms enable requests executed by all users of the Agent since the Agent was started. - total_vf_disable The total number of DECforms disable requests executed by all users of the Agent since the Agent was started. - total_vf_cancel The total number of DECforms cancel requests executed by all users of the Agent since the Agent was started. - total_vf_send The total number of DECforms send requests executed by all users of the Agent since the Agent was started. - total_vf_receive The total number of DECforms receive requests executed by all users of the Agent since the Agent was started. - total_vf_xceive The total number of DECforms transceive requests executed by all users of the Agent since the Agent was started. 1-24 Features of This Release Features of This Release 1.2 Remote Manager Features - total_tasks_executed The total number of tasks started in the Agent since the Agent was started. - user1_time, user2_time, user3_time, user1_data, user2_ data, user3_data, user4_data, user5_data, user6_data Additional generic runtime fields that are available to programmers and Agent developers. - astlm_current, biolm_current, bytlm_current, diolm_ current, enqlm_current, fillm_current, pgflquota_ current, tqelm_current, wssize_current, channelcnt_ current The actual amount of the related OpenVMS process or system resource that is being consumed by the Agent process. The frequency with which these fields are updated is based on the value of the vms_coll_interval field in the Parameter table. - pool_coll_state The current collection state for this class and this process. Collection states can be modified by modifying entries in the Collection table. If this field is set to DISABLED, the process is not currently collecting data for the fields in this class. Any field values reflect activity during a prior period when collection was enabled. - mss_process_total The total size of the MSS process pool allocated for this process. The frequency with which this field is updated is based on the value of the Parameter table field mss_coll_interval. - mss_process_free Features of This Release 1-25 Features of This Release 1.2 Remote Manager Features The amount of unused MSS process pool for this process. The frequency with which this field is updated is based on the value of the Parameter table field mss_coll_ interval. - mss_process_largest The largest unused block available in the MSS process pool for this process. The frequency with which this field is updated is based on the value of the Parameter table field mss_coll_interval. - mss_process_failures The number of failed attempts to allocate space in the MSS process pool for this process. The frequency with which this field is updated is based on the value of the Parameter table field mss_coll_interval. - mss_process_garbage The number of garbage collections that have been run to reclaim space in this processes MSS process pool. The frequency with which this field is updated is based on the value of the Parameter table field mss_coll_ interval. - error_coll_state The current collection state for this class and this process. Collection states can be modified by modifying entries in the Collection table. Errors for this process are only sent to the Remote Manager if this field is set to ENABLED. If this field is set to DISABLED, the process will not collect data for the fields in this class; existing field values reflect activity during a prior period when collection was enabled. - error_count The total number of errors related to this process that were sent to the Remote Manager. 1-26 Features of This Release Features of This Release 1.2 Remote Manager Features - last_error_message The text of the most recent error message related to this process that was sent to the Remote Manager. - time_of_last_error Date and time of the most recent error message related to this process that was sent to the Remote Manager. Features of This Release 1-27 2 _________________________________________________________________ Installation Changes This chapter describes changes to the installation process for ACMS Version 4.5. 2.1 General Installation Information This kit requires that ACMS be shut down either before or automatically during the installation. (For installation in an OpenVMS Cluster, Compaq recommends that ACMS be stopped on all cluster nodes prior to installation.) Install this kit with the VMSINSTAL utility by logging in to the SYSTEM account and typing a command in the following format at the DCL prompt, specifying the name of the kit (kit_name) and the location of the kit saveset (saveset_ location): $ @SYS$UPDATE:VMSINSTAL kit_name saveset_location Table 2-1 and Table 2-2 list the ACMS Version 4.5 kit names: Table_2-1_Alpha_Kits_______________________________________ Kit______________Name______________________________________ Development ACMSDEVA_045 Run-time ACMSRTOA_045 Remote-access____ACMSREMA_045______________________________ Installation Changes 2-1 Installation Changes 2.1 General Installation Information Table_2-2_VAX_Kits_________________________________________ Kit______________Name______________________________________ Development ACMSDEVV_045 Run-time ACMSRTOV_045 Remote-access____ACMSREMV_045______________________________ After the installation completes, run SYS$STARTUP:ACMSTART.COM on all nodes prior to restarting ACMS. This installation does not require a reboot; however, you will need to run the LOGIN.COM procedure after installation to refresh the symbol and logical definitions for this account. 2-2 Installation Changes Installation Changes 2.2 Installing the ACMS Remote Manager Web Agent 2.2 Installing the ACMS Remote Manager Web Agent This section contains a summary of the installation process for the ACMS Remote Manager web agent software, which is offered with the ACMS for OpenVMS Alpha Run-time and Development kits. For detailed information on configuring and using the ACMS Remote Manager web agent, see Chapter 3 of the Compaq ACMS for OpenVMS Remote Systems Management Guide. This software is intended for installation on an OpenVMS Alpha system local to the Remote Manager Version 4.5 server hosts used to monitor ACMS systems. Once installed, the web agent can be accessed by any system running of the supported web browsers. Refer to the Compaq ACMS for OpenVMS Software Product Description (SPD 25.50.xx) for the current operating system and browser requirements. To install the ACMS Remote Manager web agent software, do the following: 1. Run the HP ACMS for OpenVMS Alpha 4.5 installation procedure for either the ACMS Run-time or Development kit, as described in Section 3.2.1 of the Compaq ACMS for OpenVMS Version 4.4 Installation Guide. 2. A series of product-specific questions are displayed that prompt you to choose the appropriate installation options. Answer the following prompts accordingly: * Do you want the full ACMS installation [NO]? N * Do you want to install the ACMS component software [YES]? N * Do you want to install the WBEM-related files for ACMS [YES]? Y * Do you want to update the LSE environment for ACMS [YES]? N The installation procedure then performs a series of checks for prerequisite software and adequate disk space. 3. When prompted to continue the installation, answer YES. The procedure enters the ACMS WBEM Setup phase. 4. The WBEM setup procedure (SYS$STARTUP:ACMS$WBEM_ SETUP.COM) is then invoked, which creates or updates the ACMS$WBEM account and creates the necessary directories and web agent files. Installation Changes 2-3 Installation Changes 2.2 Installing the ACMS Remote Manager Web Agent Do one of the following: o If the account does not exist, you are prompted to supply a UIC and password for the account. The account is then created and assigned the ACMS$MGMT_ READ rights identifier. o If the account already exists, a list of the rights identifiers currently assigned to the account are displayed. You can choose to reset the identifiers at this time by answering YES when prompted. 5. Once the ACMS installation is complete, download and install the Compaq Management Agent for OpenVMS software. You can obtain this software and related installation material from the following web site: http://h71000.www7.hp.com/openvms/products/mgmt_agents/ 6. Follow the associated instructions to copy, unpack, and install the appropriate PCSI kit. 7. Once the Management Agent for OpenVMS software installation is complete, start the WBEM server process, as follows: $ @SYS$SPECIFIC:[WBEM]WBEM$RUN_WEBSERVER.COM 8. Next, start the ACMS web server, where queue-name is a valid OpenVMS batch queue: $ SUBMIT/NOTIFY/LOG=SYS$SYSROOT:[WBEM]/QUEUE=queue-name - _$ /USER=ACMS$WBEM SYS$SPECIFIC:[WBEM]RUN_ACMS_HMMO.COM 9. You can now access the Remote Manager web interface by entering the following URL from a client system: http://host-name:2301/acmshmmo/eng/acms_index.html where host-name represents the address of the Remote Manager server system on which the web agent software is running. This address can be expressed in any of the following forms: host-name (node name) host-name.company.com (URL) 165.112.94.78 (IP address) 2-4 Installation Changes Installation Changes 2.2 Installing the ACMS Remote Manager Web Agent The Remote Manager web interface and details regarding the Remote Manager system you have specified are displayed in the browser window. ________________________ Note ________________________ Although no functional differences exist, the physical appearance of the web interface may vary slightly between browsers. ______________________________________________________ 2.3 ACMSTART.COM Installs DECC$SHR and ACMS$TRACE_SHR.EXE ACMSHR.EXE now links with the shared image ACMS$TRACE_ SHR.EXE, which links with DECC$SHR.EXE. ACMSTART.COM has been modified to install both DECC$SHR.EXE and ACMS$TRACE_ SHR.EXE. It is necessary to leave both of these images installed. If the DECC$SHR image is not installed on the system, you get the following error when starting ACMS: $ ACMS/START SYSTEM %DCL-W-ACTIMAGE, error activating image DECC$SHR -CLI-E-IMGNAME, image file $100$DUA0:[SYS0.SYSCOMMON.][SYSLIB]DECC$SHR.EXE;1 -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image If ACMS$TRACE_SHR.EXE is not installed on the system, you get the following error when starting ACMS: $ ACMS/START SYSTEM %DCL-W-ACTIMAGE, error activating image ACMS$TRACE_SHR.EXE -CLI-E-IMGNAME, image file $100$DUA0:[SYS0.SYSCOMMON.][SYSLIB]ACMS$TRACE_SHR.EXE -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image If the ACMS Remote Manager was configured (using SYS$STARTUP:ACMS_POST_INSTALL.COM), ACMSTART.COM will execute the procedure ACMS$MGMT_SETUP.COM. This procedure prepares the OpenVMS environment to run the ACMS Remote Manager. ACMS$MGMT_SETUP.COM is executed just before ACMS_ SETUP.COM. Installation Changes 2-5 Installation Changes 2.4 ACMS Version Identification File (ACMS_ECO_LEVEL.DAT) 2.4 ACMS Version Identification File (ACMS_ECO_LEVEL.DAT) Starting with the ACMS Version 4.0 ECO Kit 1 release, there is a file distributed with the kit called ACMS_ECO_ LEVEL.DAT. This file is placed in the SYS$SYSTEM directory during the installation. The file ACMS_ECO_LEVEL.DAT contains the version identifier for the ACMS release that is currently installed on the system. This file is distributed for all releases including full releases, which have an ECO level of 0. When reporting any problems with ACMS, refer to this file to determine the current ACMS version that is being used. The version in this file may be more current than the version numbers that appear throughout the ACMS system, especially when running with an ECO release. 2.5 Reinstall ACMS After OpenVMS Upgrades When upgrading major versions of the OpenVMS Alpha operating system, it is necessary to reinstall ACMS. This applies when upgrading the OpenVMS Alpha operating system from Version 6.x to 7.x. It is not necessary to reinstall ACMS on OpenVMS VAX systems that have been upgraded from OpenVMS VAX Version 6.x to 7.x. 2.6 Programming Examples on ACMS Kit The Remote Manager programming examples shipped with the ACMS kit require that the file SYS$COMMON:[SYSHLP.EXAMPLES.ACMSMGMT]ACMSMGMT.OLB be copied to SYS$LIBRARY. To compile and link the Remote Manager programming examples, execute the following command procedure: $ @SYS$COMMON:[SYSHLP.EXAMPLES.ACMSMGMT]ACMS$MGMT_EXAMPLES_BUILD.COM In the file SYS$COMMON:[SYSHLP.EXAMPLES.ACMSMGMT]ACMS$MGMT_ EXAMPLES.C, remove the following sentence from the section called How to build this program: In addition, you must have access to object module acms$mgmt_get_creds.obj, which is installed in the ACMS$MGMT_EXAMPLES directory. 2-6 Installation Changes Installation Changes 2.6 Programming Examples on ACMS Kit In the file SYS$COMMON:[SYSHLP.EXAMPLES.ACMSMGMT]ACMS$MGMT_ EXAMPLES.C, item 4, change the following LINK command comment: **** $ LINK ACMS$MGMT_EXAMPLES,ACMS$MGMT_GET_CREDS,ACMSMGMT_RPC_CLNT, ACMSMGMT_RPC_XDR,SYS$INPUT/OPT **** SYS$SHARE:UCX$RPCXDR_SHR/SHARE **** SYS$SHARE:DECC$SHR/SHARE to: **** $ LINK ACMS$MGMT_EXAMPLES,ACMSMGMT_RPC_CLNT,ACMSMGMT_RPC_XDR,SYS$INPUT/OPT **** SYS$LIBRARY:ACMSMGMT.OLB/LIB **** SYS$SHARE:UCX$RPCXDR_SHR/SHARE **** SYS$SHARE:DECC$SHR/SHARE 2.7 Installing ACMS on OpenVMS Field test versions If you install ACMS on a field test version of OpenVMS Alpha, a new question will be asked if the version number cannot be determined: An unknown version of OpenVMS was found: E7.3-1 Which version of images do you want to install? 1. OpenVMS Alpha V6.2 2. OpenVMS Alpha V7.1 3. OpenVMS Alpha V7.2 and higher (default) Enter number of your choice [3] The default answer [3] will install the images for OpenVMS Alpha V7.2 and above. Installation Changes 2-7 3 _________________________________________________________________ Corrected Problems This chapter describes the software problems that have been corrected in ACMS V4.5 and earlier releases. 3.1 Corrections in ACMS V4.5 There are no known corrections in ACMS V4.5. 3.2 Corrections in ACMS V4.4B 3.2.1 Remote Manager Display Changes The remote manager show commands banners display the client version, that is, the version of ACMS system where the command is issued. The banner may not match the remote ACMS system for which you are displaying data if they are running different versions. The banners have been modified to indicate that the version is for the client node. In addition, the SHOW VERSION display has been modified as shown below. In the example the command is issued on node WARP to display data on node SEVEN. $ acmsmgr show ver/node=seven ACMS Remote Management -- Command line utility ACMS RM Client V4.4B-0 Version Display Time: 12-APR-2002 10:17:06.55 Node Version Information ------------ ----------------------------------------------------- warp Remote Manager Client Version V4.4B-0 SEVEN ACMS Version V4.4-0 MGMT Header Version 2 MGMT EXC Header Version 2 MGMT Config File Version 2 Corrected Problems 3-1 Corrected Problems 3.2 Corrections in ACMS V4.4B The remote manager web interface has also been modified to display the HMMO version in the SHOW VERSION command. Also the banner in the output frame indicates that the version display is for the web host. Note that the web host, running the ACMS HMMO process, is the remote manager client node in this case. 3.2.2 Waiting Task Count The waiting task count in the remote manager EXC and SERVER displays was not always accurate. In certain cases when a server failed or was rundown the count was not properly decremented. The incorrect value would be seen in the RPC and SNMP interfaces, e.g., command interface, web interface, and BMC PATROL. 3.2.3 Exiting Servers log ACCVIO in SWL Procedure servers that are defined with DCL AVAILABLE, logged ACCVIO errors in the SWL file even when a successful status is returned. 3.3 Corrections in ACMS V4.4A 3.3.1 ACMSBOOT.EXE There is a new version of ACMSBOOT.EXE which corrects a problem with privileges and identifiers on OpenVMS Alpha V7.2 and later. 3.3.2 ACMSTART.COM installs ACMSBOOT.EXE with /ARB_SUPPORT ACMSTART.COM was changed to install ACMSBOOT.EXE with the /ARB_SUPPORT=READ_ONLY on OpenVMS Alpha V7.2 and higher systems. 3-2 Corrected Problems Corrected Problems 3.3 Corrections in ACMS V4.4A 3.3.3 ACMSMGR ADD Filter/file ACMSMGR ADD Filter /File command no longer reports as Fail a successfully executed addition of error filters. 3.3.4 Add collection, no compound name In ACMS V4.4, if a web user tried to enter a compound collection name, such as employee_info_appl.empl_server, BUT had specified an Entity other than Server or Group, an HTML page was displayed which lacked the error text explaining what had happened. In ACMS V4.4A, when a web user tries adding a collection with a compound name for an Entity other than Server or Group, an alert box appears which warns the user of the NOCOMPND error situation. 3.3.5 ACMSMGR SHOW ERROR/FULL loops The command ACMSMGR SHOW ERROR /FULL no longer loops. 3.3.6 Remote Manager WEB Interface Sets Boolean values even if not specified The Remote Manager WEB Interface would set boolean values even if the state did not change. If you were going to set a value for an entity that had a settable boolean value in it, the RM WEB Interface would set the boolean value even if it didn't change. Now, it will only set the boolean value if the user actually changes the state. 3.3.7 User must pad date If a user forgets to pad the day less than 10 with a leading zero, then ACMSMGR SHOW ERROR or ACMSMGR SHOW LOG will not be able to create a valid date to display. The date no longer needs the leading 0. Corrected Problems 3-3 Corrected Problems 3.3 Corrections in ACMS V4.4A 3.3.8 Remote Manager May Display Incorrect Run-time Values for EXC Free and Total Server Counts The display of EXC run-time values for Free Servers and Total Servers Running may contain values that are greater than the actual number of servers. This could happen if a DCL STOP/ID command or ACMSMGR REPLACE SERVER command have been issued for a server. These commands do not decrement the server counts when a server is deleted. This has been fixed. 3.3.9 PROXY CREDENTIALS When proxy credentials were refreshed rights identifiers for the proxy account were not updated. If an identifier had been removed from the account the remote manager would not recognize this change until it was restarted. Now when the proxy_creds_lifetime time setting has expired the identifiers on the proxy account will he updated in the remote manager. 3.3.10 TWSC Pool Minimum Free display The TWSC Pool Minimum Free (bytes) percentage for task groups were incorrectly displayed in FULL displays. This affected both the ACMSMGR command interface and the web interface. 3.3.11 WBEM Show Status The Web Interface Remote Manager Show Status displayed incorrectly. The output was not formatted correctly and some data was included that didn't need to be displayed. 3-4 Corrected Problems Corrected Problems 3.3 Corrections in ACMS V4.4A 3.3.12 Wrong Values in SNMP interface The Remote Manager SNMP interface returned the wrong values for the following fields: - acc_ws_pool_min_free_num - acc_wsc_pool_min_free_num - acc_wsc_pool_min_free_min - acc_wsc_pool_min_free_time - acc_tws_pool_min_free_num - acc_tws_pool_min_free_min - acc_tws_pool_min_free_time - acc_twsc_pool_min_free_num - acc_twsc_pool_min_free_min - acc_twsc_pool_min_free_time 3.3.13 EXC POOL displays The EXC POOL displays have been modified to display the minimum task pool values found for all task groups in the application. 3.3.14 ACC POOL values display The ACC POOL values for minimum free workspace (for all EXCs) was calculated incorrectly. 3.3.15 ACMS/SHOW APPL/CONN sometimes ACCVIOs The ACMS/SHOW APPL/CONN operator command sometimes caused an ACCVIO on both VAX and ALPHA platforms. This resulted in an ACMSEXC process crash. This has been fixed. Corrected Problems 3-5 Corrected Problems 3.3 Corrections in ACMS V4.4A 3.3.16 ACMSCFG udp_enabled and tcp_enabled reversed The ACMSCFG parameters for UDP_ENABLED and TCP_ENABLED were reversed. 3.3.17 ACMSDBG - EXAMINE workspace returns an error There was a problem in the ACMS Task Debugger when using the OpenVMS V7.3 debugger (including the V7.3 debugger that is available on V7.1 and V7.2). The EXAMINE command returned an error when attempting to examine the workspaces of a task. 3.3.18 Wrong protection mask for ACMS$TRACE_SHR.EXE The protection mask for SYS$COMMON:[SYSLIB]ACMS$TRACE_ SHR.EXE is not correct after installing the ACMS WBEM software. The current protection may cause servers that startup under accounts with few privileges to fail. The file ACMS$WBEM_SETUP.COM now sets the protection mask to S:RWED,O:RWED,G:RWED,W:RE 3.3.19 RFC1155.MY file missing The file RFC1155.MY was missing from the ACMS V4.4 kit. This file is copied to ACMS$RM_EXAMPLES and required if you need to regenerate the ACMS MIB and OID listing as described in Chapter 7 - SNMP Overview. 3.3.20 Accessing an ACMSMGR Online Help Topic from the DCL Command Line May Display Wrong Topic If you try to access a specific ACMSMGR online help topic from the DCL command line (using either a full or abbreviated command), the incorrect online help topic may be displayed. For example, entering ACMSMGR HELP SAVE at the system prompt displayed help for the SHOW FILTER command. 3-6 Corrected Problems Corrected Problems 3.4 Corrections in ACMS V4.4 3.4 Corrections in ACMS V4.4 3.4.1 Minimum Disk Space Needed for Installation Calculated Correctly The ACMS installation procedure now correctly calculates the minimum disk space required to install the ACMS Development Kit. 3.4.2 SWLPROC No Longer Fails When Disk Space is Unavailable The Software Logger process (SWLPROC) has been enhanced so that it no longer fails when adequate disk space is not available. When disk space becomes low, SWLPROC now does one of the following: - Stops writing error records until disk space becomes available - Waits for the System Manager to redefine the logical ACMS$SWL_LOG to point to another device and issue the MCR SWLUP RENEW command. SWLPROC will resume writing to the new location. 3.4.3 Starting ACMS Applications With a High MAXPROCESSCNT Value No Longer Result in a Fatal Error The startup of an ACMS application with a high MAXPROCESSCNT parameter value no longer results in a %SYSTEM-F-BADPARAM error. 3.4.4 ADU LINK/STDL Command Documented Information about the LINK/STDL command now appears in ACMS ADU online help. 3.4.5 Spaces in SET PARAMETER Commands No Longer Trigger an Access Violation Including spaces to separate parameter values in ACMSCFG and ACMSMGR SET PARAMETER commands no longer result in an access violation. For example, in the following command the spaces surrounding the equal sign (=) now result a series of error messages: Corrected Problems 3-7 Corrected Problems 3.4 Corrections in ACMS V4.4 NODE> ACMSCFG SET PARAM/RPC_STACKSIZE = 10 %ACMSMGMT-E-BAD_VALUE, Invalid qualifier, cannot interpret value rpc_stacksize %ACMSMGMT-E-BAD_VALUE, Invalid qualifier, cannot interpret value = %ACMSMGMT-E-FAIL, Operation failed 3.4.6 New Default QTI State for ACMSMGR START SYSTEM The default QTI running state for the ACMSMGR START SYSTEM command has been changed to /NOQTI so that it is now consistent with the ACMS /START SYSTEM command. 3.4.7 ACMSMGR SHOW ERROR and SHOW LOG Accept OpenVMS Date_Time Keywords In addition to full and partial dates and times, the ACMSMGR SHOW ERROR and SHOW LOG commands now accept the traditional OpenVMS date_time keywords of TODAY, YESTERDAY, and TOMORROW as valid values to the /BEFORE and /SINCE qualifiers. For example, the following command is now valid: $ ACMSMGR SHOW ERROR /SINCE="1-JUN" /BEFORE=TODAY 3-8 Corrected Problems 4 _________________________________________________________________ Documentation Changes This chapter describes the documentation changes that have been corrected in ACMS Version 4.5. 4.1 Remote Manager Changes to the Documentation for the ACMS Remote Manager 4.1.1 ACMSMGR HELP SHOW LOG The help text for ACMSMGR Show Log was changed to include SNAP among its list of facilities and to describe a few of the qualifier defaults. 4.1.2 ACMSMGR HELP Help text for ACMSMGR Show Error was changed to list all of its qualifiers. Previously, only /NODE and /USER were listed. The qualifier list for Show Error is the same as for Show Log, plus /BRIEF and /FULL, with DEFAULT=BRIEF. 4.1.3 Identifiers The identifiers required for the SET CP, ADD TRAP, SET TRAP, and DELETE TRAP have been modified as shown below: Command New Identifier Old Identifier ----------- -------------- -------------- SET CP ACMS$MGMT_OPER ACMS$MGMT_WRITE ADD TRAP ACMS$MGMT_WRITE ACMS$MGMT_OPER SET TRAP ACMS$MGMT_WRITE ACMS$MGMT_OPER DELETE TRAP ACMS$MGMT_WRITE ACMS$MGMT_OPER Documentation Changes 4-1 Documentation Changes 4.1 Remote Manager 4.1.4 ACMSMGR SHOW ERROR The documentation for ACMSMGR SHOW ERROR is missing the /BRIEF and the /FULL qualifier. 4.1.5 ACMSMGR SHOW GROUP The documentation shows the /BRIEF /FULL qualifiers with a default of /FULL if no class qualifier is used on the command, and /BRIEF otherwise. The command actually ignores the /BRIEF qualifier if no class qualifier is used. The output is the same whether /BRIEF, /FULL, or no qualifier is used. If a class qualifier is used on the command, the default action provides a brief format display. Using /FULL with a class qualifier produces a full format display. 4.1.6 ACMSMGR SHOW MANAGER The /BRIEF and /FULL qualifiers for ACMSMGR SHOW MANAGER are not documented. The /BRIEF is default. /FULL qualifier displays timer information in addition to the information displayed in the brief display. 4.1.7 ACMSMGR SHOW VERSION The /OUT= and the /INTERVAL= qualifiers for ACMSMGR SHOW VERSION are not documented. 4.1.8 ACMSMGR SHOW FILTER The /OUT and /INTERVAL qualifiers for ACMSMGR SHOW FILTER are not documented for this command. They work identical to the way they work on other commands that take these qualifiers. 4-2 Documentation Changes Documentation Changes 4.1 Remote Manager 4.1.9 ACMSMGR SHOW PROCESS Previously, the SHOW PROCESS/BRIEF and SHOW PROCESS/FULL commands displayed all collection states for entities even when some were not applicable. You can enable/disable collection states for all classes and all entities. However, some combinations have no effect. These states are now shown in the SHOW PROCESS/BRIEF display as a "-", and as "N/A" for the SHOW PROCESS/FULL command. The display for the SHOW PROCESS command in the WEB display has also been modified. For Task Groups, the following classes are not applicable: CONFIG, RUNTIME, ERROR. For Servers, the following classes are not applicable: POOL, ERROR. 4.1.10 ACMSMGR SET COMMANDS The ACMS Remote Manager allows an authorized user to make changes to the VMS parameter file (via SYSGEN), ACMS parameter file (via ACMSGEN), user quotas (via AUTHORIZE), ACMS Remote Manager parameters (via ACMSMGR SET PARAM) and to a running ACMS system (via ACMSOPR commands). Some values are checked for minimums, like negative numbers and zero. ACMS Remote Manager parameters are checked for limits but Authorize, ACMSGEN and SYSGEN values are not. Use the same caution with the ACMS Remote Manager as you would with SYSGEN and AUTHORIZE and verify any changes you make. 4.1.11 ACMSMGR ADD and SET COMMANDS The ADD and SET commands now use /STORAGE_BEGIN_TIME instead of /STORAGE_START_TIME. 4.1.12 ACMSMGR SET EXC The command ACMSMGR SET EXC requires the /APPL qualifier for any values that are stored values. If the /APPL qualifier is missing, the error NOAPPLQUAL will be returned. A new error, NOSUCHAPPL, will be returned if the application you are attempting to modify is not active. Documentation Changes 4-3 Documentation Changes 4.1 Remote Manager 4.1.13 ACMS$SNMP Account Reset When the ACMS_POST_INSTALL.COM procedure is run, a question is asked about the ACMS$SNMP account used by the ACMS Remote Manager. If you request that the account be RESET, only the initial quotas and privileges will be reset and the ACMS$MGMT_READ identifier will be added. No other identifiers will be added or removed. The ACMS$SNMP account is used to access the Remote Manager through an SNMP agent (like BMC Patrol). The default setup for this account only allows a user to read the ACMS Remote Manager values. To make changes to ACMS, additional identifiers need to be added to the ACMS$SNMP account. See the Remote Manager documentation for information on which identifiers are used. 4.1.14 ACMSMGR START SYS/NOQTI/NOTERM no longer works The default values for the ACMSMGR START SYS command are /AUDIT, /TERMINALS, and /NOQTI. If you want to override a default you may use /NOAUDIT, /NOTERMINALS, or /QTI however you may not specify any of the defaults directly. You may only select them by leaving out the qualifier and taking the default. 4-4 Documentation Changes 5 _________________________________________________________________ Known Problems This chapter lists the known problems with the ACMS software in ACMS V4.5 and earlier releases. 5.1 New Problems in ACMS Version V4.5 There are no known problems in the ACMS V4.5 release. 5.2 New Problems in ACMS Version V4.4B 5.2.1 HMMO may ACCVIO if remote server host unavailable. The following commands may cause the ACMS$MGMT_HMMO process to ACCVIO if the Remote Manager Host Server becomes unavailable during command execution: Stop EXC - Choose APPL, then stop it. Start EXC - Enter APPL, then start it. Set EXC - Choose APPL, then set it. Set Server - Choose Server, then set it. Set Collection- Choose Collection, then set it. Note: This problem can also occur in ACMS V4.4A. 5.3 Problems Continued from ACMS Version V4.4A Known Problems 5-1 Known Problems 5.3 Problems Continued from ACMS Version V4.4A 5.3.1 Invalid Error Filter File may cause ACMS processes to loop When you start the ACMS Remote Manager, you should check the log file for any startup errors including the Error Filter file. This file is created by the ACMS Remote Manager server if the file does not exist. If the file is corrupted, the following error will be logged in the ACMS RM Log file: local 13-DEC-2001 13:55:56.80 : mgr: e : Failure mapping error global section local 13-DEC-2001 13:55:56.82 : mgr: e : %ACMSMGMT-E-VRSNMISMAT, Filter file version mismatch If you see this error, Stop the ACMS Remote Manager, delete the file SYS$SYSTEM:ACMS$MGMT_ERROR_FILTER.DAT, and restart the manager. A new file will be created. Do Not edit the error filter datafile. New error filters are added using the ACMSMGR ADD FILTER command. This Error Filter file is not designed to be shared. Each ACMS system should have it's own error filter file. The ACMS Remote Manager should be stopped prior to rebooting your system. This can prevent the corruption of the Error Filter file and will also allow any new filters added during runtime to be saved in the file. The command ACMSMGR STOP MANAGER can be used to bring the RM down. If the RPC fails, a STOP/ID on the RM Server process will also write out any changes to the Error Filter file. This problem can also occur in ACMS V4.4. 5.3.2 Remote Manager Unable to Register with TCP/IP RPC Service In some instances, the Remote Manager is unable to register with the TCP/IP RPC service. This condition is indicated by the following messages in the Remote Manager audit log: > rpc: e : Unable to register udp service for version 4.4. Retrying... > rpc: e : Unable to register tcp service for version 4.4. Retrying... If this occurs, shut down the Remote Manager and restart the Portmapper process (TCPIP$PORTM), as follows: 1. Issue the ACMSMGR STOP/ID command to shut down the Remote Manager process. 5-2 Known Problems Known Problems 5.3 Problems Continued from ACMS Version V4.4A 2. Enter the following commands to shutdown the Portmapper process and then enable the service: $ @SYS$STARTUP:TCPIP$PORTM_SHUTDOWN or $ @SYS$STARTUP:TCPIP$PORTMAPPER_SHUTDOWN $ TCPIP ENABLE SERVICE PORTMAPPER 3. Issue the @SYS$STARTUP:ACMS$MGMT_STARTUP.COM command to restart the Remote Manager. The TCPIP$PORTM process should start along with the Remote Manager process. 5.3.3 Remote Manager Error Log and Audit Log Share Filename The ACMS Remote Manager error log and audit log use the same filename (ACMS$MGMT_LOG.LOG). During installation, directories and logical names for the various Remote Manager files are created. Logicals are defined for the audit log (ACMS$MGMT_LOG) and error log (ACMS$MGMT_ERR_LOG) that, by default, reference separate directories. If you modify these logicals, make sure that they do not point to the same directory. 5.3.4 ACMSMGR SHOW COLLECTION/BRIEF May Truncate Entity Name and Storage Location The ACMSMGR SHOW COLLECTION/BRIEF command truncates the entity name and storage location fields if they exceed the length allocated for display. To view the full value of these fields, use the ACMSMGR SHOW COLLECTION/FULL command. 5.3.5 ACMSMGR SHOW TSC, CP, EXC, and QTI Does Not Display All Channel Count Values When displaying data for the TSC, CP, EXC, and QTI entities (ACMSMGR SHOW command), the Current (percentage used), Max (percentage used), and Limit fields for the Channel Count parameters are blank. To see the current Channel Count limit for each process, display the runtime data for ACC (with ACMSMGR SHOW ACC/RUNTIME/FULL). You can then calculate the Current and Max percentage used by dividing this limit by the Known Problems 5-3 Known Problems 5.3 Problems Continued from ACMS Version V4.4A respective Current and Max amount used, (displayed with ACMSMGR SHOW /RUNTIME/FULL). 5.3.6 ACMSMGR SHOW ACC Does Not Display Runtime Values for Some OpenVMS System Parameters When displaying data for an ACMS system (ACMSMGR SHOW ACC command), the stored and active values for Global Sections and Global Page File parameters are listed under the Configuration class. However, no values for these parameters are shown under the Runtime class. 5.3.7 Incomplete ACMSMGR SET Commands Result in Success Message When the SET ACC, EXC, CP, PARAM, QTI, and TSC commands are specified without qualifiers, a success message is displayed. This message is misleading since no values were actually set. For example, the following command is incomplete because no values have been specified (no qualifiers were provided): $ ACMSMGR SET ACC ACMS Remote Management -- Command line utility %ACMSMGMT-S-SUCCESS, Operation completed This message can effectively be ignored. 5.3.8 ACMSMGR START, STOP, and SET Commands May Result in Misleading Error Messages When Issued Without Proper Rights Identifier In some cases, if you attempt to issue an ACMSMGR START, STOP, or SET PARAMETER command from a user account that lacks the proper rights identifier, ACMSMGR displays error messages similar to the following: $ ACMSMGR START QTI ACMS Remote Management -- Command line utility %ACMSMGMT-E-FAIL, Operation failed Call to start QTI on server NODEXX failed %ACMSMGMT-E-FAIL, Operation failed These errors are misleading since they do not specify the cause of the problem. To determine why the command failed, consult the Remote Manager audit log. 5-4 Known Problems Known Problems 5.3 Problems Continued from ACMS Version V4.4A 5.3.9 ACMSMGR Displays Incorrect Error Messages When Updating Global Page File Value without ACMS$MGMT_SYSUPD If you attempt to update the Global Page File (GBLPAGFIL) value from an account without the ACMS$MGMT_SYSUPD rights identifier, ACMSMGR displays a series of system messages that are not indicative of the true problem. Instead of displaying the ACMSMGMT-E-SECCHKFAIL message, ACMSMGR parses the value of the /GBLPAGFIL qualifier as a hexadecimal code and displays one or more system messages (error, warning, or informational) related to that code. If the code does not resolve to an existing message, the SYSTEM-W-NOMSG warning is displayed. For example, issuing the following command from an account without the ACMS$MGMT_SYSUPD identifier results in a warning message since the hexadecimal equivalent of the GBLPAGFIL value of 60000 (0000EA60) does not correspond to an existing system message: $ ACMSMGR SET ACC/GBLPAGFIL=60000 ACMS Remote Management -- Command line utility Call to modify ACC parameters on server NODEXX failed %SYSTEM-W-NOMSG, Message number 0000EA60 -SYSTEM-S-NORMAL, normal successful completion -RMS-W-NOMSG, Message number 000117A0 %ACMSMGMT-W-WARN, Operation completed with warning, Not all operations completed successfully 5.3.10 ACMSMGR ADD FILTER/FILE Incorrectly Returns an Error Message The ACMSMGR command ADD FILTER/FILE returns the following error message even when the contents of the filter file are valid: ACMS Remote Management -- Command line utility Call to add error filter on server NODEXX failed %SYSTEM-S-NORMAL, normal successful completion %ACMSMGMT-E-FAIL, Operation failed To verify that the error filter records were created successfully, use the SHOW FILTER command. Known Problems 5-5 Known Problems 5.3 Problems Continued from ACMS Version V4.4A 5.3.11 ACMSMGR SET COLLECTION/ID and /CONFIG Does Not Allow Changes Only to Storage Start or End Time Attempting to change the only storage start time or storage end time for an ID or CONFIG class collection in ACMSMGR results in failure. For example, the following command results in an ACMSMGMT-E-FAIL error: $ ACMSMGR SET COLL/ENT=*/CLASS=CONFIG/STORAGE_END_TIME="11-JUN" To avoid this problem, add the /STORAGE_INTERVAL, /STORAGE_ STATE, or /STORAGE_LOCATION qualifier to the command, as follows: $ ACMSMGR SET COLL/ENT=*/CLASS=CONFIG/STORAGE_INTERVAL=600 - _$ /STORAGE_END_TIME="11-JUN" 5.3.12 Cannot Access ACMSSNAP Online Help from the DCL Command Line In contrast to other ACMS utilities, you can only access online help for ACMSSNAP from inside the utility itself and not from the DCL command line. For example, entering either ACMSSNAP HELP or ACMSSNAP HELP OPEN at the system prompt invokes the ACMSSNAP utility and not online help, as follows: $ ACMSSNAP HELP ACMSSNAP> To access online help, invoke the utility and enter HELP and the command prompt to display a list of topics. 5.3.13 ACMSSNAP SHOW Commands Display Only One Timestamp Value ACMSSNAP SHOW commands display only one timestamp even when multiple entities satisfy the selection criteria. The timestamp displayed is for the last record read, regardless of the entity to which the record belongs. For example, the timestamp in the following ACMSSNAP SHOW EXC/ID command belongs to the last record read, which may or may not be a record for the TAPP application: 5-6 Known Problems Known Problems 5.3 Problems Continued from ACMS Version V4.4A ACMSSNAP> SHOW EXC/ID ACMS Remote Management -- Snapshot utility ID Node Class PID Process Name Start Time Application Name ------------ -------- -------- --------------- ----------------------- -------------------------------- nodexx enabled 5954 ACMS01EXC002000 12-JUN-2001 14:26:49.00 TAPP1 nodexx enabled 5D53 ACMS01EXC001000 12-JUN-2001 11:33:14.76 TAPP [12-JUN-2001 15:45:02.06 ] 5.3.14 ACMSSNAP SHOW Commands May Overlay the Status Message with the Timestamp Value If you issue an ACMSSNAP SHOW command before any records for the specified entity have been read, the timestamp value will partially overlay the status message, as follows: ACMSSNAP>SHOW EXC/CONFIG ACMS Remote Management -- Snapshot utility [ 5-JUN-2001 09:02:07.26]EXC data was found for node nodexx 5.3.15 ACMSSNAP OPEN/SUMMARY Displays an Additional Row for Manager Data The ACMSSNAP OPEN/SUMMARY command displays an additional row for Manager data (MGR), even though it is not possible to collect or store this data. This row can be safely ignored. 5.3.16 Remote Manager Web Agent May Fail with Access Violation if Connection to Remote Host is Terminated Unexpectedly The Remote Manager web agent process (ACMS$MGMT_HMMO) may fail with an access violation if the connection to Remote Manager host is terminated unexpectedly during execution of one or more of the following operations: o Stop Application (EXC) (STOP EXC/APPLICATION) o Start Application (EXC) (START EXC/APPLICATION) o Set EXC, Application State (SET EXC/APPLICATION) o Set Server Types (SET SERVER/SERVER) o Set Remote Manager, Collection (SET COLLECTION) Known Problems 5-7 Known Problems 5.3 Problems Continued from ACMS Version V4.4A 5.3.17 Cannot Set Data Snapshot Storage Times for ID and CONFIG Classes with Remote Manager Web Agent The following storage time parameters for ID and CONFIG class data snapshot collections cannot be set using the Remote Manager web agent: Storage Begin Time (storage_start_time) Storage End Time (storage_end_time) Either use the ACMSMGR utility to set these values, or accept the default values of NOW and NEVER. 5.3.18 Remote Manager Web Agent Show Log Commands May Display Blank Page The Show Error Log (ACMSMGR SHOW ERROR) and Show Remote Manager Log (ACMSMGR SHOW LOG) options in the Remote Manager web agent each display a blank log page if an error occurs in the Remote Manager server or web agent (HMMO) process. To analyze the source of a problem with the Remote Manager server or web agent, see the web agent log file SYS$SPECIFIC:[WBEM]ACMS$MGMT_HMMO.LOG. 5.4 Problems Continued from ACMS Version 4.3 The following known problems have been in effect since ACMS Version 4.3. 5.4.1 Incorrect Queue Order with RMS Journaling When RMS journaling is enabled on an ACMS queue file, elements may be dequeued out of order of insertion. This is due to the way the ACMS$DEQUEUE_TASK service uses the RMS RRL (Ignore Read Lock, RAB$V_RRL bit in the RAB$L_ROP field) to find the next queue element. The queuing service will always attempt to return a queue element or a QUE EMPTY error. When there are multiple threads in a queue file, there is no guarantee of the order in which queue elements will be dequeued. 5-8 Known Problems Known Problems 5.4 Problems Continued from ACMS Version 4.3 5.4.2 ADU LINK Aborts with %STR-F-INSVIRMEM or %SYSTEM-F-ACCVIO Error Linking with a large number of tasks may cause the ADU LINK command to abort with one of the following error messages: %STR-F-INSVIRMEM, insufficient virtual memory or %SYSTEM-F-ACCVIO, access violation This error may be the result of the PGFLQUO parameter being set too low. To fix the problem, increase the size of the PGFLQUO parameter. 5.4.3 ACMS SWL Process May be Deleted Under certain circumstances, the ACMS_SWL process causes an access violation and the process is deleted. This causes ACMS processes that are trying to write information to the Software Event Logger (SWL) process to hang in RWMBX state. A workaround for this problem is to run the following command procedure as a batch job. This command procedure is not available on your system; you will need to copy it from this document. This batch file monitors the ACMS_SWL every minute (timing can be changed), and restarts the process if it is missing. The batch job should be queued to run under the SYSTEM account (from which SWLPROC is first run). Known Problems 5-9 Known Problems 5.4 Problems Continued from ACMS Version 4.3 $ !*************************************************************** $ begin: $ idx = "" $ $ $ loop: $ $ new_id = f$pid(idx) $ if new_id .eqs. "" then goto restart_swl $ full_name = f$getjpi(new_id,"PRCNAM") $ if full_name .eqs. "ACMS_SWL" $ then $ write sys$output "SWL is running, PID is ''new_id'" $ wait 00:01:00.00 ! wait 1 minute $ goto begin $ endif $ goto loop $ $ restart_swl: $ write sys$output "Restarting SWL" $ gosub start_swl $ exit $!*************************************************************** $START_SWL: $ RUN sys$system:SWLPROC - /PRIV=(SYSNAM,SYSPRV,WORLD,OPER,GRPNAM,GROUP)- /PROC=ACMS_SWL- /QUEUE=20- /UIC=[1,4]- /PAGE_FILE=15360- /PRIORITY=8- /DUMP - /OUTPUT=SYS$MANAGER:ACMSSWL.LOG $ RETURN $!*************************************************************** 5-10 Known Problems Known Problems 5.4 Problems Continued from ACMS Version 4.3 5.4.4 EXC Process Can Disappear without Writing Error to SWL or ATR Logs If the BYTLM quota is set too low, the ACMS EXC process can disappear without recording an error in either the SWL or Audit Trail Report (ATR) log file and without producing a process dump file. The SWL log shows the following error message, from the ACC process, indicating that the EXC process terminated: %ACMSACC-E-APPLTERM, EXC process for application terminated -Unknown message - error code 00000000 However, the EXC process does not log an error to the SWL log to provide additional details of the failure. This behavior occurs when the system runs out of BYTLM quota. To correct this problem, raise the system's BYTLM quota and reboot the system. To find a suitable higher value for the BYTLM quota, try doubling the current value. If there is still a problem when using the resulting value, monitor the system as you try different lower BYTLM values until you can find a suitable value. Monitoring the BYTLM value may not be a straightforward process. The DCL command ANALYZE/SYSTEM can report a BYTLM value that is lower than the value set during SYSGEN. Processes can appear to have a lower allocation of buffered I/O pool (BYTLM) than originally defined for the process, and the allocation can appear to vary. An article in the remedial kit describes how BYTLM is set and reported by OpenVMS. For more details about the BYTLM quota and the accounting of BYTLM, refer to the article, identified in the remedial kit as follows: Copyright (c) Digital Equipment Corporation 1996. All rights reserved. PRODUCT: OpenVMS VAX, All Versions OpenVMS Alpha, All Versions COMPONENT: Memory Management SOURCE: Digital Equipment Corporation QUESTION: Known Problems 5-11 Known Problems 5.4 Problems Continued from ACMS Version 4.3 Why do processes appear to have a lower allocation of buffered I/O pool, BYTLM, than originally defined for the process and why does the allocation seem to vary? 5.4.5 Hard Coded Restriction of 4095 Application Starts During an ACMS Invocation ACMS allows only 4095 application starts during an ACMS invocation. This restriction is hard coded. There is a check in the ACMS Central Controller (ACC) (ACCPACKAGES.LIS) for the package ID to be less than or the same as 4095. This is also used as part of the process name for the Application Execution Controller (EXC). The name is ACMS01EXCxxx000, where xxx is between 0 and FFF (hexadecimal). 5.4.6 ACMS May Fail to Start with %SYSTEM-F-NOSUCHNODE Error If ACMS is used in a mixed-network environment (Compaq DECnet Phase IV for OpenVMS and Compaq DECnet-Plus for OpenVMS), an ACMS Phase IV DECdtm transaction will fail with a '%SYSTEM-F-NOSUCHNODE, remote node is unknown' error message when it attempts to add the transaction from the DECnet-Plus system. This problem is a result of the translation of the logical name SYS$DECDTM_NODE_NAME on the DECnet-Plus system. ACMS translates this logical name and returns it to the Phase IV system, which is unable to use the long name. The workaround is to redefine this logical name to its Phase IV equivalent. 5.4.7 Disabling Classes Can Have Unexpected Results It is possible to add a collection record with class of * and a collection state of DISABLED. If the record includes either an entity type or entity name, it overrides the defaults for ID and Config class (which can't explicitly be disabled) for that entity. This can be seen with the acmsmgr show process command or through the individual show entity commands. Classes other than the ID and Config class can explicitly be disabled. In any case, if a class is disabled, some parameters in the class will continue to be updated. This is required to maintain data integrity when classes are 5-12 Known Problems Known Problems 5.4 Problems Continued from ACMS Version 4.3 cycled through an enable and disable. Some parameters such as process quotas are collected on a timer basis and will not be updated while the class is disabled. When re- enabled, the parameter data for the current value will be accurate, however the minimum or maximum values may not be. To maintain truly accurate data for all parameters, classes should never be disabled. 5.4.8 Remote Manager May Lose Some Collection Table Update Messages Under some circumstances, dynamic changes to the collection table are not always communicated to all ACMS processes. When this occurs, the ACMS processes that did not receive the update messages will not be synchronized with the collection table. This is most likely to occur for a short period of time (approximately 1 minute or less) whenever the ACMS Trace process (process name ACMS$TRACE_MON) is started. The Trace process is started under the following conditions: o Automatically by the Remote Manager when it starts up o Automatically by the Remote Manager when it needs to communicate with ACMS and the Trace process is not running o When the Trace process is started manually using a DCL command o When the Trace process is started manually using the ACMSMGR START TRACE command. The workaround is to delay updating the collection table for 30 seconds to 1 minute after the Trace monitor is started. For example, with the following set of commands, collection messages will be lost if the commands are executed serially with little or no time between commands, as in a command procedure: Known Problems 5-13 Known Problems 5.4 Problems Continued from ACMS Version 4.3 $ ACMS/START SYS $ @SYS$STARTUP:ACMS$MGMT_STARTUP $ ! WAIT FOR THE rm TO STARTUP $ WAIT 00:00:05 $ ! $ ACMSMGR ADD COLL/ENT=*/NAME=*/CLASS=RUNTIME/COLL_S=ENABLED The problem is uncovered by displaying the process collection states, as in the following example: $ ACMSMGR SHOW PROCESS ACMS Remote Management -- Command line utility ACMS V4.4A-0 Process Table Display Time: 01-DEC-2001 13:16:42.66 Server Entity Node Type PID Process Name -or- Application. [server_name, task_group_name] ID Cfg RT POOL -------- ----- -------- ------------------------------------------------ NODEXX acc 20200D4F ACMS01ACC001000 1 1 0 0 NODEXX tsc 20200D51 ACMS01TSC001000 1 1 0 0 NODEXX cp 20200D52 ACMS01CP001000 1 1 0 0 NODEXX cp 20200D53 ACMS01CP002000 1 1 0 0 NODEXX cp 20200D54 ACMS01CP003000 1 1 0 0 In this example, all processes have the run-time class disabled even though a collection table entry was just added to enable them all. You can take one of two possible actions. First, you can prevent this situation from occurring by delaying slightly before issuing the command to update the collection table. For example: $ ACMSMGR START SYS $ @SYS$STARTUP:ACMS$MGMT_STARTUP $ ! WAIT FOR THE RM TO STARTUP $ WAIT 00:00:05 $ ! NOW WAIT FOR TRACE TO GET CONNECTED $ WAIT 00:00:40 $ ACMSMGR ADD COLL/ENT=*/NAME=*/CLASS=RUNTIME/COLL_S=ENABLED 5-14 Known Problems Known Problems 5.4 Problems Continued from ACMS Version 4.3 Alternatively, you can correct the situation by applying a change to the collection table. This forces the Remote Manager to evaluate and synchronize the collection states of each process, as in the following example: $ ACMSMGR SET COLLECTION/ENT=*/NAME=*/CLASS=RUNTIME/COLL_S=ENABLED. Known Problems 5-15 6 _________________________________________________________________ Restrictions This chapter lists the restrictions that apply to ACMS Version 4.5. 6.1 Restrictions in ACMS Version 4.5 ACMS V4.5 has the same restrictions as the previous releases. 6.1.1 Limit of 127 CP's per node in an ACMS system Currently only 127 CP's are supported on a single node in an ACMS system. The ACMSGEN parameter of -1 indicates an unlimited # of them should be configurable but the limit is actually 127. If the value to set higher than 127, the following error will occur: $ acms/start term %ACMSOPR-E-STRTTCSERR, Error while attempting to START TERMINALS -ACMSTSC-F-INTERR, ACMSTSC internal error %ACMSOPR-E-ERROR, Some operations may not have been performed (this limit is not new to ACMS V4.5, it's been an architectural limit since ACMS V1.0) 6.1.2 Using a logical name for ACMSPAR If you use the logical ACMSPAR to point to an ACMS parameter file, you should include the .ACM extension. The ACMS runtime system will default the extension but the ACMS Remote Manager will not. The ACMS Remote Manager will not function properly because of this. This will be fixed in a future release. Restrictions 6-1 Restrictions 6.1 Restrictions in ACMS Version 4.5 6.1.3 Remote Management Web Interface errors with Netscape 6 From the remote management web interface, the SHOW LOG and SHOW ERROR LOG commands do not work properly with Netscape 6. The commands do not generate an error, however, the log window does not contain any data record. It appears that the file is empty even when it is not. The commands work properly with Netscape 4.7x, Netscape 7.0 Preview Release 1, Internet Explorer, and CSWB V1.0 on OpenVMS. 6.2 Restrictions in ACMS Version V4.4A and earlier 6.2.1 Multithreading and Upcalls on OpenVMS Alpha Version 7.* ACMS Version 4.5 running on OpenVMS Alpha Version 7.* systems do not have kernel threads or upcalls enabled. 6.2.2 Length Restriction for TCP/IP Hosts If the translation of the logical name UCX$INET_ HOST is greater than 31 characters, the results are unpredictable. The Remote Manager allocates only 31 bytes for the translation; longer TCP/IP host names will potentially corrupt Remote Manager local memory and lead to unpredictable results. In order for ACMS to parse and display node names consistently, it is recommended that ACMS TCP/IP and DECnet host names be identical, following the DECnet Phase IV naming conventions. If the TCP/IP host name for a potential ACMS client or server system differs from this convention, you should define a six-character alias for that system in the hosts database. 6.2.3 Remote Manager and TP Connector Software May Conflict Over TCP/IP Port 1023 When running the ACMS Remote Manager on the same node as the TP Desktop Connector (ACMSDI$SERVER) or the TP Web Connector (ACMSDA$GATEWAY), note the TCP/IP port being used by each server. Only one server can use a particular port at any given time. 6-2 Restrictions Restrictions 6.2 Restrictions in ACMS Version V4.4A and earlier By default, each server attempts to connect to port 1023. To prevent conflicts, the TP Desktop Connector and TP Web Connector have parameter files that allow you to manually specify a different port. The Remote Manager uses PORTMAPPER to select a free port. Depending upon the order in which the servers are started, and whether the parameter files are used, conflicts may occur. For example, if the Remote Manager is started before the TP Desktop Connector, and an alternate port was not specified in the parameter file, the Remote Manager and TP Desktop Connector will both attempt to use port 1023. To prevent this from occurring, Compaq recommends that you do the following: o Create or modify the parameter file (SYS$STARTUP:ACMSDA$STARTUP.PM) for the TP Web Connector so that it includes the following entry: "TCPIP_PORT = 1022" This prevents conflict between the TP Desktop Connector and TP Web Connector software. o Always start the Remote Manager last. PORTMAPPER will locate the next free port automatically. 6.2.4 New ACMS Configuration File Required A new configuration file is required for ACMS Version V4.4. You can create an updated version of this file automatically by running the ACMS postinstallation procedure (ACMS_POST_INSTALL.COM). 6.2.5 Compatibility Issues with ACMS Version 4.3 The following compatibility issues exist between the ACMS Remote Manager Versions 4.5 and 4.3: o ACMS V4.4 and ACMS V4.4A are compatible. o You can use the ACMS Version 4.3 Remote Manager to monitor ACMS 4.5 processes; however, you are limited to using Version 4.3 fields and parameters. o You cannot use the ACMS Version 4.5 Remote Manager to monitor ACMS Version 4.3 systems. Restrictions 6-3 Restrictions 6.2 Restrictions in ACMS Version V4.4A and earlier 6.2.6 Certain ACMS Errors Not Sent to the Remote Manager Error Log Note that the following ACMS run-time errors are sent to SWL but not to ACMS Remote Manager error log: o Errors signaled to a last chance handler outside of ACMS that does not have access to the Remote Manager process (such as those errors returned from performing a STOP/ID on either a CP or EXC process). o Errors that occur before the Remote Manager process has been initialized (such as those errors returned from starting a TSC process with the Forms Manager defined as NULL). 6.2.7 Running Multiple Data Snapshots from Remote Manager Can Exhaust Pagefile Quota The Remote Manager has a default pagefile quota of 100,000 pages. If a number of data snapshot collections are started, the resulting stacksize may exceed this value and cause the Remote Manager process to fail. The pagefile quota is specified in the file SYS$STARTUP:ACMS$MGMT_STARTUP.COM. If you initiate a number of simultaneous data snapshot collections, monitor the use of pagefile resources used by the Remote Manager process. If necessary, adjust the pagefile quota in the ACMS$MGMT_ STARTUP file; then stop and restart the Remote Manager system to apply the changes. 6.2.8 Correcting an Invalid Data Snapshot Storage Location To correct an invalid storage location for a data snapshot file, you must reset the storage state (disable/enable) after entering another location. This reinitializes the snapshot thread and forces it to write data to the new location. 6-4 Restrictions Restrictions 6.2 Restrictions in ACMS Version V4.4A and earlier 6.2.9 Using /ACTIVE and /STORED Qualifiers with ACMSMGR SET commands With the prior version of ACMSMGR, you could specify both the /ACTIVE and /STORED qualifiers with same ACMSMGR SET command; even for settings where either the active or stored value could not be updated. With ACMS Version 4.4, you can no longer specify both qualifiers with the same SET command. Attempts to do so will result in the following error: $ ACMSMGR SET TSC /MAX_LOGINS=50 /ACTIVE /STORED ACMS Remote Management -- Command line utility %ACMSMGMT-E-ERRBOTHFLAGS, Both current and active flags were set. They are mutually exclusive. No updates performed %ACMSMGMT-E-FAIL, Operation failed To set the active and stored values, you must now use separate SET commands. If you try to modify an active setting and only the stored value can be updated, the following warning messages are displayed: $ ACMSMGR SET TSC /CP_SLOTS=5 /ACTIVE ACMS Remote Management -- Command line utility Call to modify TSC parameters on server JANEWY failed %ACMSMGMT-W-ACTUPDINV, /active was specified for cp_slots, but this value is not dynamic. No update was performed %ACMSMGMT-W-WARN, Operation completed with warning, Not all operations completed successfully 6.2.10 Use ACMSSNAP SHOW Commands to Display ERROR Class Data To view stored ERROR class information, use the full entity display without a class qualifier. For example, use the following command to display ERROR class information for ACC: ACMSSNAP> SHOW ACC/FULL If both the collection state and storage state were enabled for the relevant collection, then the ERROR class data will be shown at the end of the displayed output. Restrictions 6-5 Restrictions 6.2 Restrictions in ACMS Version V4.4A and earlier 6.2.11 Using the ACMSSNAP SHOW/AT Command The ACMSSNAP SHOW/AT command does not always display the exact record specified. Sometimes, the record immediately before or immediately after the requested record is displayed. For instance, in the following example, five ACC records are read from the data snapshot file, and the same SHOW/AT command is specified three times. The first attempt displays the record previous to the requested record. The second attempt displays the exact record requested. The third attempt again displays the previous record. ACMSSNAP>SHOW ACC/ID/NEXT=5 ACMS Remote Management -- Snapshot utility ID Node Class PID Process Name Start Time User Name Version -------- -------- ------ --------------- ----------------------- --------- ---------------- nodexx enabled 5C67 ACMS01ACC001000 7-JUN-2001 09:30:56.71 SYSTEM V4.4-0 [ 8-JUN-2001 11:11:11.99] nodexx enabled 5C67 ACMS01ACC001000 7-JUN-2001 09:30:56.71 SYSTEM V4.4-0 [ 8-JUN-2001 11:11:22.24] nodexx enabled 5C67 ACMS01ACC001000 7-JUN-2001 09:30:56.71 SYSTEM V4.4-0 [ 8-JUN-2001 11:11:32.24] nodexx enabled 5C67 ACMS01ACC001000 7-JUN-2001 09:30:56.71 SYSTEM V4.4-0 [ 8-JUN-2001 11:11:42.24] nodexx enabled 5C67 ACMS01ACC001000 7-JUN-2001 09:30:56.71 SYSTEM V4.4-0 [ 8-JUN-2001 11:11:52.24] ACMSSNAP>SHOW ACC/AT="8-JUN-2001 11:11:22.24"/ID ACMS Remote Management -- Snapshot utility ID Node Class PID Process Name Start Time User Name Version -------- -------- ------ --------------- ----------------------- ---------- ---------------- nodexx enabled 5C67 ACMS01ACC001000 7-JUN-2001 09:30:56.71 SYSTEM V4.4-0 [ 8-JUN-2001 11:11:11.99] ACMSSNAP>SHOW ACC/AT="8-JUN-2001 11:11:22.24"/ID ACMS Remote Management -- Snapshot utility ID Node Class PID Process Name Start Time User Name Version -------- -------- ------ --------------- ----------------------- ----------- ---------------- nodexx enabled 5C67 ACMS01ACC001000 7-JUN-2001 09:30:56.71 SYSTEM V4.4-0 [ 8-JUN-2001 11:11:22.24] ACMSSNAP>SHOW ACC/AT="8-JUN-2001 11:11:22.24"/ID ACMS Remote Management -- Snapshot utility ID Node Class PID Process Name Start Time User Name Version -------- -------- ------ --------------- ----------------------- ---------- ---------------- nodexx enabled 5C67 ACMS01ACC001000 7-JUN-2001 09:30:56.71 SYSTEM V4.4-0 [ 8-JUN-2001 11:11:11.99] 6-6 Restrictions Restrictions 6.2 Restrictions in ACMS Version V4.4A and earlier To prevent this "toggle" effect from occurring, only specify the /AT qualifier once while navigating through a set of records. If you are not at the record which you want to view, then use either the /NEXT or /PREV qualifier to move through the record sequence. Once you locate the record you want to view, issue the appropriate SHOW command without any navigational qualifiers (/AT, /NEXT, and /PREV) to display the details of that record. Restrictions 6-7 Restrictions 6.3 Restrictions Continued from ACMS Version 4.3 6.3 Restrictions Continued from ACMS Version 4.3 The following restrictions have been in effect since ACMS Version 4.3. 6.3.1 CDD Version 6.x Support Restricted Oracle CDD/Repository Version 6.1 is not supported by ACMS Version 4.x. An access violation occurs whenever ACMS attempts to access the dictionary. Oracle CDD/Repository Version 6.1A is supported by ACMS Version 4.x. 6.3.2 SNMP GETNEXT Calls Return Unpredictable Results SNMP getnext calls are not supported in this release of the ACMS Remote Manager. SNMP getnext calls issued to the Remote Manager may appear to complete successfully; however, the data should not be considered to be accurate. 6.3.3 Remote Manager is Unusable Following TCP/IP or UCX Shutdown The ACMS Remote Manager depends on the underlying network software in order to communicate with external processes. If the IP network is stopped, the existing network connections between the ACMS Remote Manager and the IP network become orphaned and cannot be reconnected when the network is restarted. This prevents further communications between external processes and the ACMS Remote Manager. The workaround is to ensure that the Remote Manager is stopped prior to stopping the IP network, and to restart it only after the IP network has been restarted. If the Remote Manager is left running when the network is stopped, it is acceptable to stop it using the DCL command STOP/ID. 6.3.4 Error Message When Stopping Remote Manager When the Remote Manager process is stopped, a detached- process termination accounting record is written for the ACMS$MGMT_SVR process. The final status recorded will be %x00FE9F49, which is translated in the SYS$MESSAGE:ACMSMSG.EXE file as: %ACMSMGMT-S-SUCCESS, Operation completed. This status indicates a successful shutdown of the ACMS Remote Manager. 6-8 Restrictions Restrictions 6.3 Restrictions Continued from ACMS Version 4.3 6.3.5 Remote Manager Reports Error Message if it Can't Get Collection State One of the following error messages may appear in the Remote Manager log: msg_proc: e : Failure getting current collection states. Ignoring process ACMS01ACC001000 This message can be safely ignored. At the time this message is generated, the Remote Manager is attempting to synchronize collection states with the ACC. Because the ACC loads the Collection table, synchronization is implicit. procmon: e : Failure obtaining current collection states. Bypassing In this error message, is an ACMS entity type. You can disregard this message. At the time this message is generated, the Remote Manager is attempting to synchronize collection states with the process, but the process has either not fully initialized or is not started. An example of this condition is when the ACMS run-time system is started without the Queued Task Initiator (QTI). If the process is initializing, synchronization will occur when the process finishes initializing. If the process is not started, synchronization is not necessary. 6.3.6 Remote Manager May Report ACMSTRC$_MONPROCEXST Error When Trying to Start Trace Monitor In some situations, when the Remote Manager is trying to start the Trace monitor, it reports the following in the Remote Manager log: rpc: e : %ACMSTRC-W-MONPROCEXST, ACMS$TRACE_MON process seems to already exist since ACMS$TRACE_MBX is defined This error message indicates that the Remote Manager attempted to create a Trace monitor process and detected that the logical name for the Trace monitor mailbox ACMS$TRACE_MBX was defined in the system logical name table. The process is assumed to exist if this logical name is defined. If there is a working version of the Trace monitor process running (image name ACMS$TRACE_ MONITOR, process name ACMS$TRACE_MON), and the logical Restrictions 6-9 Restrictions 6.3 Restrictions Continued from ACMS Version 4.3 name ACMS$TRACE_MBX is defined as a mailbox device, then no action is required. If the monitor process is malfunctioning, then you can try to stop it with the DCL command STOP/ID. If this fails, you can take the following steps: 1. Deassign the system logical name ACMS$TRACE_MBX 2. Change the process name to something other than ACMS$TRACE_MON 3. Set the process priority to 1. The Remote Manager can then create a new process. If these attempts to disable the existing Trace monitor process fail, then you should report the problem to your Compaq support representative. 6.3.7 Remote Manager Takes a Few Seconds to Start It takes a few seconds for the Remote Manager to become fully initialized during startup. This usually occurs on machines that are heavily loaded, on networks that are busy, or in command procedures that execute ACMSMGR commands immediately after starting the Remote Manager. During the Remote Manager initialization period, ACMSMGR commands are likely to fail with the following error messages: %ACMSMGMT-W-NOCLNT_ATTACH, Cannot create client for node NODEXX %ACMSMGMT-E-NOCLIENTS, No clients created, cannot continue %ACMSMGMT-E-FAIL, Operation failed If this occurs, resubmit the command after pausing slightly. You can use the following series of commands in a command procedure to avoid this problem: $ @SYS$STARTUP:ACMS$MGMT_STARTUP $ WAIT 00:00:05 $ ACMSMGR SHOW ACC/ID 6.3.8 ACMSMGR SHOW LOG /SINCE Qualifier Default The /SINCE qualifier of the ACMSMGR SHOW LOG command defaults to the current date only if the qualifier is specified as /SINCE= (that is, if there is an equal sign but no value string). 6-10 Restrictions Restrictions 6.3 Restrictions Continued from ACMS Version 4.3 6.3.9 Remote Manager EVENT_SEVERITY Traps Do Not Include Text Messages All Remote Manager traps report the date and time, severity, entity type, process name, trap parameter and current value. Remote Manager traps do not report text messages. For event_severity traps, the traps include the severity of the event but do not indicate the actual text message. The traps receiver will know that a warning, an error, or a fatal event occurred, but it will not know what actually happened. To determine which event caused the traps, enter the ACMSMGR SHOW LOG command and specify the traps time in the /SINCE qualifier. For example, assume the following trap was received by a trap listener: Node NODEXX Date/Time 5-OCT-1999 14:50:05.13 Severity Error Entity Type MGR Process Name ACMS$MGMT_SVR Trap Parameter event_s Current Value 2 This trap indicates that the Remote Manager on node NODEXX detected a warning level condition (value 2) at time 14:50:05.13. To determine the event that raised this condition, use the ACMSMGR SHOW LOG command as follows: $ ACMSMGR SHOW LOG/NODE=NODEXX/SINCE="5-OCT-1999 14:50"/SAVE=WARN Note that the time of the event may slightly precede the trap time, since the trap time is the time the trap was generated, not the time of the event. 6.4 Restrictions Continued from ACMS Version 4.1 The following restrictions have been in effect since ACMS Version 4.1. Restrictions 6-11 Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 6.4.1 Form Name Cannot be a Logical Name When Using Multiple Submitter Platforms When the ACMS$MULTIPLE_SUBMITTER_PLATFORMS is defined as "T", "Y" or 1, the ACMS EXC process attempts to open the form files specified in the task group definition by adding _VAX or _AXP to the file name. If the task-group definition uses a logical name for the form name, the EXC will not be able to locate the forms because no logical name translation is performed. Form names when used in a multiplatform environment cannot be logical names. 6.4.2 CDD Restriction Initializing Fields with Strings Shorter Than Field Size Do not define a CDD field initialization string that is shorter than the field size. This may cause a memory access violation when using the Application Definition Utility (ADU) to build a group. For example, the following CDO file sometimes causes ADU to generate a memory access violation when the ADU REPLACE GROUP statement is issued: define field wksp_rep:r_1_field_1 datatype text size 30000 initial_value is "". define record wksp_rep:r_1. wksp_rep:r_1_field_1. end record. define field wksp_rep:r_2_field_1 datatype text size 30000 initial_value is "". define record wksp_rep:r_2. wksp_rep:r_2_field_1. end record. The workaround for this example is to remove the initial_ value clauses. 6-12 Restrictions Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 6.4.3 Lowercase Characters Corrupted If the terminal or terminal emulator is set to VT100 mode and both TDMS and DECforms are present on the same system, lowercase characters in DECforms menus are corrupted when an application is entered by bypassing the ACMS menus. As a workaround, issue a SET TERMINAL /DEC_CRT=2. This restriction occurs in ACMS Version 3.3 and higher. 6.4.4 On OpenVMS Alpha, Agent Hangs on Second Task Startup in Task Debugger When an agent attempts to start a task in the ACMS Task Debugger while the Task Debugger is already executing a task, the agent should abort with the following error message: %ACMS-E-EXCMAXDBGTSK, Only a single task may be debugged at one time As of ACMS Version 4.0 on OpenVMS Alpha, the agent hangs and does not return the error message. This is due to a problem in OpenVMS Alpha Version 6.x with certain $GETJPIW calls. 6.4.5 QTI's PIOPAGE Requirements for RMS Journaling on OpenVMS Alpha On OpenVMS Alpha, most recovery unit-journaled $PUT, $UPDATE, or $DELETE operations require at least 8.2 pagelets (512-byte pages) of PIOPAGES for the duration of these operations. In addition, a typical call to SYS$END_ TRANS or SYS$ABORT_TRANS to end a recovery unit may require approximately 16.5 pagelets of PIOPAGES for the duration of these operations. These figures are approximate and may vary depending on the characteristics of your application. While the need for additional PIOPAGES is temporary over the duration of the operation, RU applications that make extensive use of asynchronous RMS operations may have several operations launched at the same time, thus making heavier demands on their PIOPAGES. This is true in the multithreaded QTI process. The calculation of PIOPAGES requirements should be made by estimating the maximum number of threads that will be used by the QTI and multiplying that number by 16.5. Restrictions 6-13 Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 6.4.6 Using the Terminal User Command SELECT If a user is at the ACMS command menu and issues a SELECT command, the ACMS Command Process (CP) saves the selection and does not submit the task until the user issues a CONTINUE command. To use the SELECT command, you can do either of the following: o Use the SELECT command from a menu other than the ACMS command menu. o Use the SELECT command from the ACMS command menu and then issue the CONTINUE command. 6.4.7 Problem Phoning from DCL Servers You cannot use the OpenVMS Phone utility (PHONE) from a DCL server when using ACMS because a user who enters ACMS using the ACMS/ENTER/NORETURN command or through a controlled terminal does not have an OpenVMS process associated with the user. The Phone utility was designed for communication between interactive OpenVMS processes. DCL server processes are not true interactive OpenVMS processes. When the Phone utility tries to dial a user or answer a call, it checks the system for both an interactive process that has the correct user name and a login device that has the correct attributes. When a user enters ACMS using the ACMS/ENTER command, the user's original interactive process remains. PHONE sees the process and works from the DCL server to which the user is attached. If the user enters ACMS using the ACMS/ENTER/NORETURN command or through an ACMS controlled terminal, there is no interactive process to meet the Phone utility's requirements. Thus, the Phone utility does not work from the DCL server to which the user is attached. 6.4.8 Submitters on VAXstation Must Have SHARE Privilege A submitter logged in to a VAXstation device (WT or TK) cannot select a task that passes the terminal to a server process unless the server process has OpenVMS SHARE privilege. If the SHARE privilege is not defined, the submitter receives the %ACMSTRM-F-NOSHRPRV error and an entry is logged to the Software Event Logger (SWL). 6-14 Restrictions Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 SHARE privilege allows the server process to assign channels to devices allocated to other users, such as a workstation device. 6.4.9 Task Debugger and Online Server Debugging The following restrictions apply to the Task Debugger and online server debugging. 6.4.9.1 Examining Binary Date Data Types The ACMS Task Debugger EXAMINE command misrepresents the value of an OpenVMS ADT (quadword binary date) data type under some conditions, and accurately displays its contents under other conditions. For example, the following command format displays incorrect results: ACMSDBG> EXAMINE The workaround is to examine any binary date fields as individual, fully qualified single field names, rather than as part of the entire workspace. The following command displays the correct value for the date field: ACMSDBG> EXAMINE/DATE OF 6.4.9.2 Exiting the Task Debugger with Ctrl/C or Ctrl/Y Exiting the ACMS Task Debugger with a Ctrl/C or Ctrl/Y may not delete the subprocess created for a server. This can happen if Ctrl/C or Ctrl/Y is used to exit the Task Debugger, and a server is attached to an Rdb database and is waiting for access to the database. 6.4.10 Application Management Commands and Tools The following restrictions apply to the application management tools and commands. 6.4.10.1 ACMSPARAM May Generate an Excessive PGFLQUOTA Value for the CP Account The current formula for calculating the PGFLQUOTA value of the CP account is liberal. The formula assumes that each exchange step involves the sending or receiving of the LARGEST_MESSAGE (see the Variables Required for ACMSPARAM.COM table in the Compaq ACMS for OpenVMS Managing Applications manual. Restrictions 6-15 Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 After executing ACMSPARAM, review the value of CP_ PGFLQUOTA. If this value appears to be excessively large, then replace the LARGEST_MESSAGE variable with the average size of workspaces used in exchange steps, or with the size of the workspace most often used in exchange steps. The formula for calculating the CP_PGFLQUOTA provides only a rough approximation of this quota. To fine-tune your system, calculate the quota for your particular system. 6.4.10.2 ACMSPARAM and ACMEXCPAR Do Not Support Search Lists ACMSPARAM.COM and ACMEXCPAR.COM do not support logical name search lists for the TDB file specifications. 6.4.10.3 MSS Process Pool Exhausted Errors are Reported Incorrectly If a process runs out of ACMS message switch subsystem (MSS) process pool when allocating a buffer prior to reading a message from a network link, the status is truncated and the following error is written to the software error log: %ACMSMSS-I-ERRLNKREAD, Error reading network link Unknown message - error code 0000A342 The correct reason is: ACMSMSS-E-PROPOOEXH, Process local pool is exhausted To correct this problem, increase the MSS_PROCESS_POOL parameter in ACMSGEN, and restart the ACMS system. 6.4.11 Task Queuing Restrictions The following restrictions apply to task queuing. 6.4.11.1 Processing of Failed Queued Task Elements If you are using a task queue file marked for RMS recovery- unit journaling, and a large number of queued task instances fail at the same time, in rare circumstances the QTI is unable to correctly process a failed queued task element. When this happens, the QTI cannot set the queued task element into a retry state, move it on to an error queue, or delete the queued task element. Instead, the failed queued task element is processed again immediately. 6-16 Restrictions Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 The QTI logs the following error entry in the ACMS audit log when this error occurs: ************************************************************ Type : ERROR Time : 14-OCT-1996 10:35:20.22 Queue : QLT$QUEUE1 ErrQue : QLT$ERRQUEUE1 Appl : QLT_APPL Task : QLT_TASK_X User : QLT_USER_42 Elem Id: 00000309-0000007E-D032A4E0-00948E68 Text : Error processing queued task -ACMSQUE-E-ERRPRCREC, Error trying to read the failed queued task record during error processing -RMS-S-OK_RRL, record locked against read but read anyway ************************************************************ 6.4.12 Application Definition Utility (ADU) Restrictions The following restrictions apply to the Application Definition Utility. 6.4.12.1 ADU Migration from DMU Dictionary to CDO Dictionary If the 26th character of an ACMS definition name is an underscore (_) or a dollar sign ($), ADU is not able to convert the definition automatically from the DMU dictionary to the CDO dictionary. The reason that ACMS is unable to do the conversion is that in order to migrate to the CDO dictionary, ADU must save a copy of the original definition in DMU while it is putting the new copy in CDO. Because you cannot have a definition with the same name in DMU format and CDO format, ADU renames the definition by prefixing the object name with ACMS$. If the object name was longer than 26 characters to begin with, ADU has to truncate the object name. If the 26th character is a dollar sign or an underscore, DMU does not allow ADU to write this definition to the DMU side of the CDD dictionary. The workaround is to migrate manually any ACMS definitions with this characteristic. Restrictions 6-17 Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 6.4.12.2 Workaround for MMS Restriction with ADU The way that ADU handles procedure server transfer modules causes the DEC/Module Management System (MMS) to process the server transfer object module (.OBJ) as if it were out of date. This is because ADU closes the .OBJ before it writes the BUILD audit record to the dictionary. The workaround is to copy the server transfer object module to itself in the action line in which you build your group. For example: VR_TASK_GROUP.TDB DEPENDS_ON - VR_CHECKIN_TASK^, - VR_CHECKOUT_TASK^, - ... VR_VEHICLES_WKSP^ ADU BUILD GROUP VR_TASK_GROUP VR_TASK_GROUP.TDB COPY VR_READ_SERVER.OBJ VR_READ_SERVER.OBJ PURGE VR_READ_SERVER.OBJ This changes the modification date on the server transfer object module so that it is newer than the group definition in the dictionary. This ensures that MMS re-creates the server transfer object module only when necessary. 6.4.12.3 Invalid Characters in ADU Cause ADU to Terminate with TKN_INVALID Error Message If you use an invalid character in an ACMS definition, ADU terminates after giving the following error message: ADU> @UPDATE_TASK.TDF %ACMSTDU-F-TKN_INVALID, Invalid token class 1 detected by PARSER -CMU-F-INROUTINE, error detected in routine PAT$LS_OUTPUT_TOKEN The valid characters for identifiers are: o A through Z o a through z o 0 through 9 o Dollar sign ($) o Underscore (_) 6-18 Restrictions Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 6.4.12.4 Using Search Lists to Point to Multiple Dictionaries in ADU In ADU, if you set default to a logical name defined as a search list, ADU sets default to only the first dictionary in the search list. If you include a search list logical name in an object's path name, ADU uses all dictionaries included in the search list to process that object. 6.4.12.5 "End of Task-Referenced Workspace Table" Error on Selection of Invalid Task If you incorrectly specify the same workspace twice while using the TASK ARGUMENTS clause, ADU does not recognize the problem. For example, the following statement should produce a syntax error, but it does not: TASK ARGUMENTS ARE EMPLOYEE_REC WITH ACCESS READ, EMPLOYEE_REC; If you select this task, it is canceled. The message "end of task-referenced workspace table" is included as a part of the task's Audit Trail record, and it is written to SWL. If you attempt to dump a task group containing this task, ADU gives an ACCVIO error. 6.4.13 Request Interface (RI) Restrictions The following restrictions apply to the Request Interface. 6.4.13.1 User-Written Menus for the ACMS$RI_AGENT When you write a user-written menu routine for the ACMS$RI_ AGENT, it is important to be aware of how your chosen language handles dynamic string descriptors. The task name and application name arguments in the ACMS$RI_AGENT are passed to the ACMS$RI_MENU_ROUTINE as dynamic descriptors. If the language you have chosen does not support dynamic string descriptors, you must use an OpenVMS run-time library routine to return the task and application names to the ACMS$RI_AGENT. The following FORTRAN example accepts an application name and a task name into two fixed-length strings. The STR$TRIM OpenVMS RTL routine is then used to remove trailing spaces and copy the names into the arguments supplied by the ACMS$RI_AGENT. Restrictions 6-19 Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 ! ! THIS ROUTINE GETS THE TASK AND APPLICATION ! NAMES FROM THE USER.... ! INTEGER FUNCTION ACMS$RI_MENU_ROUTINE(TASK,APPL,TASK_STS) ! ! Addresses of appl and task name dynamic string descriptors INTEGER*4 TASK, APPL ! ! Completion status of previous task (0 if 1st time through) INTEGER*4 TASK_STS ! ! Local strings to input application and task names CHARACTER*32 TNAME, ANAME ! ! RTL completion status INTEGER*4 STATUS ! ! RTL routine to trim spaces from a string INTEGER*4 STR$TRIM ! WRITE( UNIT=5,FMT='(A,$)' ) ' INPUT APPLICATION SELECTION: ' READ ( UNIT=5,FMT='(A32)' ) ANAME WRITE( UNIT=5,FMT='(A,$)' ) ' INPUT TASK SELECTION: ' READ ( UNIT=5,FMT='(A32)' ) TNAME ! STATUS = STR$TRIM( %REF(TASK), %DESCR(TNAME) ) IF (STATUS) THEN STATUS = STR$TRIM( %REF(APPL), %DESCR(ANAME) ) END IF ! ACMS$RI_MENU_ROUTINE = STATUS RETURN END 6.4.14 ACMS and DECforms Restrictions The following restrictions apply to ACMS and DECforms. 6-20 Restrictions Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 6.4.14.1 Problems Using DECforms and TDMS in the Same ACMS Application DECforms does not know when screen management routines or other forms products have changed the state of the display. This situation can result in incorrect painting of the screen, particularly during a sequence of task calls or chained tasks performing DECforms I/O and non-DECforms I/O. In this case, add the REFRESH and the REMOVE statements to the form source file to eliminate incorrect repainting. 6.4.14.2 DECforms Timeout Values DECforms allows you to specify an infinite number of seconds as a timeout value for a panel or icon by specifying a zero or a negative value with the TIMEOUT subclause. As an alternative, ACMS allows you to specify an infinite timeout value in ACMS in one of the following ways: o You can code a zero value in the ADU subclause WITH TIMEOUT. The ADU subclause WITH TIMEOUT does not allow a negative value. If you code a negative value in this subclause, ADU returns the following syntax error: %ACMSTDU-E-SYNTAXERR: Found '-' when expecting ';' o You can place a negative value in the workspace field for WITH TIMEOUT. Note that if you specify timeout values in both the DECforms and the ACMS definitions, the ACMS timeout value overrides the DECforms timeout value. 6.4.14.3 Naming Form Image Files Each form image file must have a unique name. If two form image files have the same name, problems occur. DECforms uses the OpenVMS image activator to activate form images. The activator uses the file name to keep track of the images. Each image can be activated only once in a process. If an image file has been activated, then a different image file with the same name cannot be activated. Rather than giving two form image files the same name, use different file names. For example: Restrictions 6-21 Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 FORMS ARE form_a IN "DISK1$:[USER1]FORM.EXE" WITH NAME F1, form_b IN "DISK2$:[USER2]FORM.EXE" WITH NAME F2; FORMS ARE form_a IN "DISK1$:[USER1]FORM_1.EXE" WITH NAME F1, form_b IN "DISK2$:[USER2]FORM_2.EXE" WITH NAME F2; 6.4.14.4 BOLD Video Attribute Carried Forward from Menus If a task selected from a DECforms menu performs terminal I/O, stream I/O, or runs a DCL server, the characters in the task are displayed on the screen with the BOLD video attribute. In the DECforms form that displays the menu, the message panel uses the BOLD video attribute to display messages. After you enter input for the menu, the message line is updated and the BOLD video attribute is turned on. The BOLD video attribute is not turned off until DECforms or TDMS displays something on the terminal. Therefore, if you select a task that uses terminal I/O or stream I/O, or that runs a DCL server, the screen displays characters in the task with the BOLD video attribute. There are two workarounds to this problem. Both of them change the appearance of the menu slightly and require the modification of the DECforms form that displays the menu. If it is not necessary to use the BOLD video attribute in the message panel, change the definition of the message panel as follows: /* Message Panel */ Message Panel MSGS_PANEL End Panel If it is necessary to use the BOLD video attribute in the message panel, an alternative solution is to add a panel to display a blank space at the upper left hand corner of the terminal. This panel is displayed by the control text response for clearing the screen. When you select a task from a menu displayed by DECforms, ACMS calls this control text response to clear the screen. When this control text response displays the added panel, the BOLD video attribute 6-22 Restrictions Restrictions 6.4 Restrictions Continued from ACMS Version 4.1 is turned off. Change the control text response and add a new panel as follows: /* Control Text Response for clearing the screen */ Control Text Response "CLSCR" Remove All Display VIDEO_OFF_PANEL End Response /* Dummy panel to turn off video attributes from previous display */ Panel VIDEO_OFF_PANEL Viewport DEFAULT_VIEW Literal Text Line 1 Column 1 Value " " End Literal End Panel Restrictions 6-23 7 _________________________________________________________________ General Information This chapter discusses topics of general interest concerning the ACMS Version 4.5 release. 7.1 Compaq DECforms Web Connector Version 3.0 Available Compaq DECforms Web Connector Version 3.0 is now available. This software product provides transparent Web access to existing DECforms applications running on OpenVMS systems, including ACMS based applications. For more information, see the following World Wide Web (WWW) address: http://www.openvms.compaq.com/commercial/webconnector/index.htm 7.2 Periodically Delete Remote Manager Credential Files The Remote Manager automatically creates credential files in the current local directory or in the specified by the logical ACMS$MGMT_CREDS_DIR. To conserve disk space, Compaq recommends that you periodically delete these files. The credential file names follow the format Username_PID_ local-node_remote-node.DAT and are valid for the period of time specified by the proxy_creds_lifetime parameter (default value is 60 minutes). All files older than proxy_ creds_lifetime value can be deleted. 7.3 Add SYSLCK Privilege to Accounts That Run ACMS Processes The SYSLCK (system lock) privilege should be added to all accounts running the following ACMS processes: ACMS01ACC001000 ACMS01EXC001000 ACMS01TSC001000 ACMS01CP001000 General Information 7-1 General Information 7.4 Setting Remote Manager Stacksize Parameters 7.4 Setting Remote Manager Stacksize Parameters The Remote Manager is implemented using DECthreads, which means that each thread within a Remote Manager process maintains its own stack. The Remote Manager contains the following parameters that enable the ACMS system managers to control the size of each thread stack: dcl_stacksize (default=300) log_stacksize (default=300) msg_proc_stacksize (default=300) proc_mon_stacksize (default=300) rpc_stacksize (default=300) snap_stacksize (default=30) snmp_stacksize (default=300) timer_stacksize (default=300) trap_stacksize (default=300) Each stack unit represents 1024 bytes for VAX and 8192 bytes for Alpha. The current default values allow all threads to execute during normal operation. A single thread is required for each of the parameters, except for the snapshot thread (which uses the snap_stacksize parameter). For each data snapshot collection enabled, there is a thread associated with that snapshot collection. Therefore, the default stacksize for the snap_stacksize is 30 which equates to approximate 262 KB (on Alpha). If any of the stacksize values are set too low, the related thread will fail, which may also cause the Remote Manager process to fail. 7.5 ACMSTRC$_NOSUCHPGM Warning Message A warning message, ACMSTRC$_NOSUCHPGM, may occasionally appear in the SWL log file. The following information was extracted from the trace message file that describes the most common circumstance that causes this message, and what, if anything, you should do when you see it. Problem: This message is signaled when a trace mail message is received by the trace monitor from a program indicating that the program is about to exit and the trace manager was unaware that the program was running. 7-2 General Information General Information 7.5 ACMSTRC$_NOSUCHPGM Warning Message Action: In some cases, this message is normal, such as when some ACMS processes are started before the trace monitor starts and the processes exit shortly after the trace monitor starts. If you see an unusually high number of these messages, then you should report this to your Compaq support representative. To minimize the occurrence of these messages, start the Remote Manager process before starting ACMS. The Remote Manager will start the Trace monitor process. 7.6 ACMS Does Not Support Pixel-Based Display Devices DECforms Version 2.1 and higher provide display support for character-cell (VT series) and pixel (DECwindows Motif) devices. ACMS support is limited to the character-cell devices. 7.7 ACMS$TRACE_SHR.EXE Cannot be Installed Resident ACMS$TRACE_SHR.EXE cannot be installed resident because it is built with traceback. It could be built with notraceback, but the image never really needs to be installed resident anyway. ACMSTART.COM was modified to remove the optional resident flag from the install command for ACMS$TRACE_SHR.COM. 7.8 Remote Manager Shutdown Causes Accounting Records to be Written When the ACMSMGR STOP MANAGER command is issued, records similar to the following are written to the accounting file: Date / Time Type Subtype Username ID Source Status -------------------------------------------------------------------------------- 15-JUL-1999 11:08:50 PROCESS SUBPROCESS THOMPSON 2160056A 00FDA8AA 15-JUL-1999 11:08:52 PROCESS DETACHED THOMPSON 21600569 00FE9F49 General Information 7-3 General Information 7.9 Logical Names for Workspace Pool Sizes in EXC 7.9 Logical Names for Workspace Pool Sizes in EXC Prior to ACMS Version 4.2, the execution controller (EXC) used ACMSGEN parameters to size the workspace pools used during the execution of a task. In ACMS Version 4.2, logical names can be defined to size the workspace pools on a per-application basis. The logicals that can be defined are: o ACMS$EXC_WS_POOLSIZE o ACMS$EXC_WSC_POOLSIZE o ACMS$EXC_TWS_POOLSIZE o ACMS$EXC_TWSC_POOLSIZE The logicals can be defined at any level. To make them application-specific, reference logicals in the application definition or in a name table associated with an application. For example, in the application definition: APPLICATION LOGICAL NAMES ARE ACMS$EXC_TWS_POOLSIZE = "1750", ACMS$EXC_TWSC_POOLSIZE = "75"; EXC allows one additional translation of the logical name so that an application definition does not have to be rebuilt to change a value. For example: In the Application Definition Utility (ADU): APPLICATION LOGICAL NAMES ARE ACMS$EXC_TWS_POOLSIZE = "ACMS$EXC_SAMPLE_TWS_POOLSIZE"; At DCL level: $ DEFINE/SYSTEM ACMS$EXC_SAMPLE_TWS_POOLSIZE "1750" The logical name (or the translation of it) must contain a valid decimal number (in pages for VAX, in pagelets for Alpha). The ACMSGEN parameters are used if the logical cannot be translated or if the logical contains an invalid value or character. If the value in one or more of the logicals is too high, the application will not start. (This behavior is the same for any value specified by ACMSGEN.) 7-4 General Information General Information 7.9 Logical Names for Workspace Pool Sizes in EXC The ACMSPARAM and ACMEXCPAR procedures do not have any knowledge of the changes being made to the workspace pools. Any calculations done by these procedures reflects the values in ACMSGEN. 7.10 Use Logical Names for File Allocation in ACMSATL The Audit Trail Logger (ACMSATL) attempts to translate the following logical names and uses the values specified when the Audit Trail Log file is created: o ACMS$ATL_DEQ_BLOCKS - The default extension quantity (DEQ) specifies the number of blocks to be added when the file is extended. Valid values are 0 through 65535. o ACMS$ATL_ALQ_BLOCKS - The allocation quantity (ALQ) specifies the number of blocks to be initially allocated when the log is created. Valid values are 0 through 4,294,967,295. See the OpenVMS Record Management Services Reference Manual for additional information on these fields. 7.11 New Logical Name Must be Defined for RI Agents and User-Written Agents During the initialization of a CP process or a user-written agent, ACMS determines the following two conditions: whether CMA is in the process and the version of DECforms being used. Depending on these two conditions, the ACMS agent with respect to DECforms operates in either SINGLE- USER mode or MULTI-USER mode. SINGLE-USER mode is defined as one (1) user at a time executing an ACMS task. A single-threaded user-written agent is an example of SINGLE-USER mode. MULTI-USER mode is defined as more than one (1) user at a time executing an ACMS task. A CP process is an example of MULTI-USER mode. If you use a MULTI-USER user-written agent with DECforms Version 2.2, the agent must be linked with CMA. General Information 7-5 General Information 7.11 New Logical Name Must be Defined for RI Agents and User-Written Agents ACMS provides the logical name ACMS$DECFORMS_IN_AGENT. This logical name must be defined as a process logical name when a user-written agent uses DECforms in ACMS tasks. The following values are valid for defining the logical name to a TRUE value: 1, "T", "t", "Y", "y". For example: $ DEFINE/PROCESS ACMS$DECFORMS_IN_AGENT "Y" ACMS Version 4.1 used the logical name ACMS$CMA_USER_AGENT for essentially the same purpose, but the name was confusing. Later versions of ACMS still support this logical name, but it is undocumented. Compaq recommends that you use settings for the logical name based on the version of DECforms that the agent uses, as follows: o DECforms Version 1.4 is used. Defining the logical name ACMS$DECFORMS_IN_AGENT is not required but has no harmful effects. Defining the logical name causes ACMS to load the FORMS$MANAGER forms manager during initialization, rather than when the first DECforms call is made. o DECforms Version 2.1B is used. The logical name ACMS$DECFORMS_IN_AGENT must be defined to the TRUE value. Doing so ensures that ACMS brings CMA into the process if CMA is not already there. o DECforms Version 2.2 or later is used. If the agent is intended to run in SINGLE-USER mode, defining the logical name ACMS$DECFORMS_IN_AGENT has no effect, because CMA is not in the process. Defining the logical name causes ACMS to load the FORMS$MANAGER forms manager during initialization, rather than when the first DECforms call is made. Define the logical name ACMS$DECFORMS_IN_AGENT only when using DECforms Version 2.1B or when using DECforms Version 2.2 or later in MULTI-USER mode. 7-6 General Information General Information for Application and Forms Files Should Not Be Write Protected 7.12 Cache Directories for Application and Forms Files Should Not Be Write Protected The directories used for caching the application and forms files should not be write protected. Write protecting the caching directories will cause the task to fail when caching of the application or forms files to the submitter node is performed. 7.13 No Longer Necessary to Store ACMS Definitions in CDD In previous versions of ACMS, after ACMS definitions were checked for syntax errors they were always stored in CDD. When all the definitions were processed, the definitions were read out of the dictionary, and a database file to be used by the ACMS run-time software was created. With ACMS Version 4.3 and later, the ACMS definitions no longer have to be stored in CDD. The ADU COMPILE command can be used to compile ACMS definitions and store the results in an OpenVMS file. Once all the definitions are processed, the ADU LINK command can be used to create the runtime database files. CDD record definitions must continue to be stored in the dictionary. When determining whether to store definitions in CDD or to compile the definitions into OpenVMS files, keep in mind the following: o All ACMS definitions that are going to be transformed for inclusion into a database file must be processed the same way. For example, if you store a task group definition in the CDD, all task definitions referenced in the task group must also be stored in the dictionary. If, instead, you compile the task group definition, all referenced task definitions must be compiled. o File-based processing requires that the files that are the compilation results of all referenced ACMS definitions be in the same directory with the same file extension. That is, the compilation results of all tasks required by a task group must be in the same directory with the same file extension. The same is true for all submenus required by a menu. General Information 7-7 General Information 7.13 No Longer Necessary to Store ACMS Definitions in CDD For more information about the ADU COMPILE and LINK commands, refer to the Compaq ACMS for OpenVMS ADU Reference Manual. 7.14 PATROL Knowledge Modules The PATROL Knowledge Modules for ACMS V4.4 are valid for for ACMS Version 4.5. However, the fields associated with the new Agent monitoring entity are not included. The Management Information Block (MIB) can be found in ACMS$RM_ EXAMPLES:MIB_OID.LIS. Customers can edit the existing Knowledge Modules to include the new fields for the Agent entity. ACMS Version 4.3 KMs are compatible with and can be used to monitor Version 4.5 systems; however, you will not be able to use these KMs to monitor or change any of the new tuning fields offered with ACMS Version 4.5. 7-8 General Information 8 _________________________________________________________________ Guidelines for Reporting an ACMS Problem The following sections discuss the kinds of information you should have available when reporting an ACMS problem. 8.1 Calling in a Problem to Your HP Support Representative When you call your HP support representative to report a problem, the telephone support specialist will most likely ask you for the following information: o Which versions of OpenVMS, ACMS, network, forms product, and programming language are you using? Obtain the version information as follows: - OpenVMS version 1. Identify the hardware type by logging in to the system and looking at the output of this statement: $ WRITE SYS$OUTPUT F$GETSYI("ARCH_NAME") The output will be either Alpha or VAX. 2. Get the OpenVMS version from the first line of this command: $ SHOW SYSTEM - Network and firmware version and information 1. DECnet version number and ECO level 2. Firmware version 3. TCP/IP product name, version and ECO level - ACMS version Guidelines for Reporting an ACMS Problem 8-1 Guidelines for Reporting an ACMS Problem 8.1 Calling in a Problem to Your HP Support Representative Log in to the system experiencing the problem and type this file using the following command: $ TYPE SYS$SYSTEM:ACMS_ECO_LEVEL.DAT This file always contains the most accurate version identification information. Version IDs are not always updated throughout the ACMS system. This file is the most reliable source of ACMS version information. - DECforms version 1. Get the image file identification of the FORMS$MANAGER image: $ ANALYZE/IMAGE SYS$SHARE:FORMS$MANAGER.EXE Image Identification Information image name: "FORMS$MANAGER" image file identification: "FORMS V1.4-12" link date/time: 25-JUN-1993 11:46:59.70 linker identification: "05-13" Patch Information 2. Get the image file identification of the FORMS$CIOSHR image: $ ANALYZE/IMAGE SYS$SHARE:FORMS$CIOSHR.EXE Image Identification Information image name: "FORMS$CIOSHR" image file identification: "FORMS V1.4-5" link date/time: 8-APR-1992 21:04:07.36 linker identification: "05-05" Patch Information Report both of these image versions when reporting a problem with a system where DECforms is being used. - TDMS version 8-2 Guidelines for Reporting an ACMS Problem Guidelines for Reporting an ACMS Problem 8.1 Calling in a Problem to Your HP Support Representative Get the image file identification of the TSSSHR image: $ ANALYZE/IMAGE SYS$SHARE:TSSSHR.EXE Image Identification Information image name: "TSSSHR" image file identification: "TDMS V1.9A-0" link date/time: 29-APR-1991 16:59:21.21 linker identification: "05-05" Patch Information - Programming language version The programming language version is usually visible in the header of compiler listing files. For example: APPL_PROGRAM Source Listing 22-NOV-1993 DEC COBOL V1.1-747 Source Listing 12-OCT-1995 DEC C V4.1-001 o A clear statement of the problem, and why you feel this is an ACMS problem. o What commands or process caused the problem? o What were the exact error messages you received? o What additional information appeared in either the ACMS Audit Trail Log file or the ACMS Software Event Logger (SWL)? Be sure to have these logs on hand when you place your call. Refer to HP ACMS for OpenVMS Managing Applications for details about these files. The support specialist may also ask for the following information: o The version number of other products you are using with ACMS. o A description of the application and, if necessary, a small example of code that duplicates the problem. o Whether you are running a distributed application. If you have a distributed environment, please report the clock time on both systems and note any time difference. Guidelines for Reporting an ACMS Problem 8-3 Guidelines for Reporting an ACMS Problem 8.1 Calling in a Problem to Your HP Support Representative o Whether you are running with multiple submitter platforms (that is, whether the logical name ACMS$MULTIPLE_SUBMITTER_PLATFORMS is defined to true). o Whether the problem affects all users or only specific users. o Whether the problem affects all applications or only specific tasks. o Whether the tasks use remote requests. o The types of devices being accessed. o The ACMS system state at the time the problem occurred. o Whether the problem is reproducible. o Whether you can reproduce the problem running your application in the ACMS Task Debugger environment. o Whether this command, statement, or application has worked before. If you answer yes to this question, the specialist will want to know what might have caused the change. For example, such changes might include updates to the operating system or layered products, bringing new production applications online, and adding new users. After listening to your responses, the specialist might be able to provide immediate help or might have to call you back after doing some testing and research. For problems that the specialist cannot reproduce or resolve, you might be asked to supply additional detailed information. 8.2 Additional ACMS Information You Can Collect This section provides additional information that you may be asked to collect to assist in analyzing a problem. It would be helpful if, for very large log files, you extract and forward only the portion of the log file that represents the time of the error. o The SWLUP log file. This file is most important. It is located in SYS$ERRORLOG:SWL.LOG or in the directory pointed to by the logical ACMS$SWL_LOG. Send the binary log file rather than an output report. 8-4 Guidelines for Reporting an ACMS Problem Guidelines for Reporting an ACMS Problem 8.2 Additional ACMS Information You Can Collect o The Audit Trail Log file. This file is located either in SYS$ERRORLOG:ACMSAUDIT.LOG or in the directory pointed to by the logical ACMS$AUDIT_LOG. Send the binary log file rather than an output report. o Any ACMS dump files. These files are located in the SYS$ERRORLOG directory, the default directory for the associated process user name, or in the directory pointed to by the logical SYS$PROCDMP. The dump file names are in the form of ACMxxxx.DMP. Use the following commands to analyze the dump file: $ ANALYZE/PROCESS/OUTPUT=.DMP_INFO DBG> SHOW CALLS DBG> SHOW IMAGE DBG> SHOW STACK o All ACMSGEN parameters. Use the following commands to obtain this information: $ RUN SYS$SYSTEM:ACMSGEN ACMSGEN> USE_ACTIVE ACMSGEN> WRITE ACMSGEN.LOG ACMSGEN> EXIT o All OpenVMS SYSGEN parameters. Use the following commands to obtain this information: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SET /OUT=SYSGEN.LOG SYSGEN> SHOW /ALL SYSGEN> SHOW /SPECIAL SYSGEN> EXIT o Memory on all systems involved. Use the DCL command SHOW MEMORY to obtain this information: $ SHOW MEMORY/ALL/FULL/OUT=MEMORY.LOG o The authorization data for all OpenVMS accounts used by ACMS. Run the OpenVMS Authorize Utility and then obtain a full listing (SYSUAF.LIS file) for each account: $ RUN SYS$SYSTEM:AUTHORIZE UAF> LIST/FULL UAF> EXIT Guidelines for Reporting an ACMS Problem 8-5 Guidelines for Reporting an ACMS Problem 8.2 Additional ACMS Information You Can Collect o All logical name tables. Use the DCL command SHOW LOGICAL to obtain this information: $ SHOW LOGICAL/FULL/TABLE=*/OUT=ALL_LOG.LOG 8.2.1 Reporting Problems with ACMS Utilities In addition to the information listed in Section 8.2, it may be helpful to collect the following information for problems with ACMS utilities: o A listing of the definitions (including record, form, request, request library, task, task group, application, and menu) and procedures that may have caused the problem. o The SWLUP log file. This file is very important. It is located in SYS$ERRORLOG:SWL.LOG or in the directory pointed to by the logical ACMS$SWL_LOG. Send the binary log file rather than an output report. o The Audit Trail log file. This file is located either in SYS$ERRORLOG:ACMSAUDIT.LOG or in the directory pointed to by the logical ACMS$AUDIT_LOG. Send the binary log file rather than an output report. o All ACMSGEN parameters. Use the following commands to obtain this information: $ RUN SYS$SYSTEM:ACMSGEN ACMSGEN> USE_ACTIVE ACMSGEN> WRITE ACMSGEN.LOG ACMSGEN> EXIT o The authorization data for all OpenVMS accounts used by ACMS. Run the OpenVMS Authorize Utility, and obtain a full listing (SYSUAF.LIS file) for each account using the following commands: $ RUN SYS$SYSTEM:AUTHORIZE UAF> LIST/FULL UAF> EXIT o All logical name tables. Use the DCL command SHOW LOGICAL to obtain this information: $ SHOW LOGICAL/FULL/TABLE=*/OUT=ALL_LOG.LOG 8-6 Guidelines for Reporting an ACMS Problem Guidelines for Reporting an ACMS Problem 8.2 Additional ACMS Information You Can Collect 8.2.2 Reporting Problems with the ACMS Run-Time System In addition to the information listed in Section 8.2, it may be helpful to collect the following additional information for problems with the ACMS run-time system: o Process dump files. These files are located in the SYS$ERRORLOG directory, the default directory for the associated process user name, or the directory pointed to by the logical name SYS$PROCDMP, if the error occurred in the Command Process (CP), the Application Execution Controller (EXC), the ACMS Central Controller (ACC), the Audit Trail Log (ATL), or the Terminal Subsystem Controller (TSC). The dump file names are in the form of ACMxxxx.DMP. Use the following commands to analyze the dump file on VAX systems: $ ANALYZE/PROCESS/OUTPUT=.DMP_INFO DBG> SHOW IMAGE DBG> SHOW CALLS DBG> SHOW STACK On Alpha systems, the dump files should be analyzed on the system where they were created. This should be done before the system is rebooted or modified in any way. Please provide the support specialist with the output file. Use the following commands to analyze the dump file on Alpha systems: $ ANALYZE/PROCESS_DUMP/OUTPUT=.DMP_INFO- _$ /IMAGE=SYS$SYSTEM:ACMSEXC The /IMAGE= qualifier is sometimes necessary to access the DEBUG. $ DBG SHOW IMAGE DBG> SHOW CALLS DBG> SHOW STACK o All OpenVMS SYSGEN parameters. Use the following commands to obtain this information: Guidelines for Reporting an ACMS Problem 8-7 Guidelines for Reporting an ACMS Problem 8.2 Additional ACMS Information You Can Collect $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SET /OUT=SYSGEN.LOG SYSGEN> SHOW/ALL SYSGEN> SHOW/SPECIAL SYSGEN> EXIT o Memory on all systems involved. Use the DCL command SHOW MEMORY to obtain this information: $ SHOW MEMORY/ALL/FULL/OUT=MEMORY.LOG o Output from the SDA utility for any ACMS processes that appear to be hung. Use the following commands to obtain the information: $ ANALYZE/SYSTEM SDA> SET PROCESS/ID=pid-of-hanging-process SDA> SHOW PROCESS SDA> SHOW PROCESS/CHANNEL SDA> SHOW PROCESS/IMAGES SDA> SHOW PROCESS/PHD SDA> SHOW CALL SDA> SHOW CALL/NEXT SDA> SHOW CALL/NEXT !repeat this until there are no more calls Call Frame Information ----------------------- %SDA-E-NOTINPHYS, 00000000 : not in physical memory SDA> EXIT o Collection of current PCs and other information from any process that may be hung. Use the following process to capture this information: $ SET HOST/LOG=output-file NODE:: After logging in: $ SET TERM/UNKNOWN $ SHOW PROCESS/ID=pid/CONTINUOUS Let this run for 15 to 20 minutes, then press CTRL/Z. $ LOGOUT Submit the output file with the problem report. 8-8 Guidelines for Reporting an ACMS Problem Guidelines for Reporting an ACMS Problem 8.2 Additional ACMS Information You Can Collect o A machine-readable copy of the OpenVMS SYSGEN parameter values. This may be useful if there is an unexpected process dump. Use the following commands to obtain these values: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> WRITE The USE ACTIVE command copies the current parameter values into your work area. The WRITE command creates a machine-readable version of this information in the output file you specify. o A listing of the ACMSGEN parameters. o A listing of the definitions (including form, request, request library, task group, task, record, application, and menu) and procedures for the task that may have caused the problem. o A listing of the parameter settings of the various user names under which the ACMS components were running when the problem occurred. Use the OpenVMS Authorize Utility to obtain this information: $ RUN SYS$SYSTEM:AUTHORIZE UAF> LIST/FULL The LIST/FULL command writes the information to a file called SYSUAF.LIS in your default directory. The file includes the user name, the user identification code (UIC), the default OpenVMS directory, privileges, and a list of the OpenVMS quotas and values assigned for that user name. Information about the user names for the ACMS Central Controller (ACC), the Terminal Subsystem Controller (TSC), the Application Execution Controller (EXC), and the Command Process (CP) is useful in determining the events surrounding a problem with the ACMS system. o A listing of the Audit Trail Report for the error. o A listing of the ACCOUNTING log report. o A listing of the hardware error log (Error Log Utility). Guidelines for Reporting an ACMS Problem 8-9 Guidelines for Reporting an ACMS Problem 8.2 Additional ACMS Information You Can Collect 8.2.3 Reporting Problems with the Remote Manager Web Agent If you encounter problems with the Remote Manager web agent process (ACMS$MGMT_HMMO), refer to the following files for error information specific to the web agent: SYS$SPECIFIC:[WBEM]ACMS$MGMT_HMMO.LOG;* SYS$SPECIFIC:[WBEM]ACMS$MGMT_HMMO.ERR;*. SYS$SPECIFIC:[WBEM]*.DMP;* If the problem is with WBEM$SERVER process, supply your HP support representative with the dump file. If the problem is with the Remote Manager web agent process, please have the following files ready for analysis in addition to a procedure which reproduces the error condition: SYS$SPECIFIC:[WBEM]ACMS$MGMT_HMMO.LOG;* SYS$SPECIFIC:[WBEM]ACMS$MGMT_HMMO.ERR;* SYS$SPECIFIC:[WBEM]*.html;* SYS$SPECIFIC:[WBEM]*.txt;* SYS$SPECIFIC:[WBEM]SYS$OUTPUT.*; SYS$SPECIFIC:[WBEM]*.DMP;* 8-10 Guidelines for Reporting an ACMS Problem