OSI/FTAM Configuration and Management Manual Abstract This manual describes how to configure and manage the Tandem OSI/FTAM and OSI/APLMGR subsystems. It is intended for system and network managers and operators who manage initiators and/or responders on Tandem NonStop systems. Product Version OSI/FTAM D43 and OSI/APLMGR D43 Supported Releases This manual supports D43 and all subsequent D-series releases and G06.05 and all subsequent G-series releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 421944-001 OSI/FTAM D43 OSI/APLMGR D43 June 1999 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.
OSI/FTAM Configuration and Management Manual Glossary Index Figures Tables What’s New in This Manual xiii Manual Information xiii Manual Changes xiii About This Manual xv Manual Audience xv Manual Contents xvi ISO and NIST FTAM Phase 2 Standards FTAM Manuals xviii Related Manuals xx Your Comments Invited xvii xxii Notation Conventions xxii 1.
2. FTAM Management Environment Contents 2.
3. Planning, Installing, and Configuring Tandem FTAM Contents 3.
3. Planning, Installing, and Configuring Tandem FTAM (continued) Contents 3. Planning, Installing, and Configuring Tandem FTAM (continued) Configuring FTAM Application Entities 3-59 Initiator Application Entity 3-59 Responder Application Entity 3-63 4.
5. Monitoring FTAM Performance Contents 5.
6. FTAM Troubleshooting Contents 6. FTAM Troubleshooting General Strategy 6-2 Troubleshooting Tools and Their Use 6-3 Event Management Service (EMS) Event Log 6-3 Inspect 6-4 Subsystem Control Facility (SCF) TRACE Command and PTrace Utility Other SCF Commands Types of Problems 6-10 6-12 Configuration Errors 6-12 Interoperability Problems 6-19 System Problems 6-20 Capacity and Performance Problems 6-20 Tandem Software Internal Errors 6-20 Getting Help 6-21 A.
B. FTAM EMS Filters Contents B. FTAM EMS Filters Filtering All FTAM and APLMGR Event Messages B-2 Filtering Critical FTAM and APLMGR Event Messages B-3 TACL Macro to Compile Filter Examples B-4 C. FTAM Software Files Glossary Index Figures Figure i. Tandem FTAM Manual Set xviii Figure 1-1. A General View of Tandem FTAM Architecture Figure 1-2. Tandem FTAM Components 1-5 Figure 1-3. Underlying Subsystems Supporting Tandem FTAM 1-9 Figure 1-4.
Figures (continued) Contents Figures (continued) Figure 3-1. One APLMGR Process Managing One Initiator and One Responder Figure 3-2. One APLMGR Process Managing Multiple Initiators and Responders 3-4 Figure 3-3. Multiple APLMGR Processes, Each Managing One Initiator or One Responder 3-5 Figure 3-4. Use of Common Names and OSI Addresses Figure 3-5. Establishing an FTAM Association Through a Tandem Initiator 3-12 Figure 3-6. Establishing an FTAM Association to a Tandem Responder 3-16 Figure 3-7.
Tables (continued) Contents Tables (continued) Table 3-1. User ID and Password Used by the Tandem Responder 3-20 Table 3-2. Guardian File Access Required to Perform FTAM VFS Action 3-21 Table 3-3. Mapping From FTAM Action List to Guardian Security 3-24 Table 3-4. Mapping From Guardian Security to FTAM Action List 3-26 Table 3-5. FTAM Installation Subvolumes 3-40 Table 6-1. OSI Process Device Types and Subtypes 6-11 Table A-1. Example Configuration Names Table A-2.
Contents OSI/FTAM Configuration and Management Manual—421944-001 xii
What’s New in This Manual Manual Information OSI/FTAM Configuration and Management Manual Abstract This manual describes how to configure and manage the Tandem OSI/FTAM and OSI/APLMGR subsystems. It is intended for system and network managers and operators who manage initiators and/or responders on Tandem NonStop systems. Product Version OSI/FTAM D43 and OSI/APLMGR D43 Supported Releases This manual supports D43 and all subsequent D-series releases and G06.
What’s New in This Manual • • • • • • • Manual Changes High-PIN processes. By default, FTAM processes now run at a high PIN. If you want the APLMGR to run at a low PIN, you must specify this in the RUN command. For initiator and responder processes, you can specify the attribute HIGHPIN OFF in the SCF ADD PROCESS or ALTER PROCESS command. For more information, see the OSI/FTAM and OSI/APLMGR SCF Reference Manual. TCP/IP software and hardware requirements.
About This Manual This manual describes how to configure and manage the Tandem OSI/FTAM and OSI/APLMGR subsystems.
Manual Contents About This Manual Manual Contents Table i lists the contents of each section and appendix in this manual. Table i. Manual Contents Section or Appendix Contents Section 1, Introduction to Tandem FTAM Introduces OSI/FTAM and provides an explanation of its architecture. Also discusses the hardware and software you need to run FTAM on a Tandem NonStop system.
ISO and NIST FTAM Phase 2 Standards About This Manual ISO and NIST FTAM Phase 2 Standards This manual and the other OSI/FTAM manuals are for readers familiar with the ISO standards and the National Institute of Standards and Technology (NIST) FTAM Phase 2 agreements, to which Tandem FTAM and the underlying Tandem OSI products conform. Table ii lists these standards. Table ii.
FTAM Manuals About This Manual FTAM Manuals This manual is one in a set of Tandem FTAM manuals. Figure i shows all the manuals in the Tandem FTAM manual set. Figure i. Tandem FTAM Manual Set Tandem OSI/FTAM Programming Guide Concepts and Programming Management Methods Management Reference for Operators Tandem OSI/FTAM Programming Reference Manual Tandem OSI/FTAM Responder Manual OSI/FTAM Configuration and Management Manual Operator Messages Manual OSI/FTAM and OSI/APLMGR SCF Ref Manual CDT 001.
FTAM Manuals About This Manual The following list describes the manuals shown in Figure i on page xviii: • • • • Tandem OSI/FTAM Programming Guide explains important programming concepts pertaining to the Tandem FTAM application program interface (API) and describes sequences of procedure calls to use to perform common FTAM programming operations. This manual also provides an overview of FTAM concepts for those who have not recently read the ISO 8571 specification.
Related Manuals About This Manual Related Manuals The following manuals contain helpful information on Tandem FTAM and related products. These manuals provide information on underlying OSI subsystems: • • • • • The OSI/AS Configuration and Management Manual describes how to install, configure, and manage OSI/Application Services (OSI/AS). This manual also includes information on monitoring and adjusting OSI/AS to optimize performance and information on diagnosing and fixing problems.
Related Manuals About This Manual • • • The PAM Configuration and Management Manual describes the Port Access Method (PAM) subsystem, which allows applications running on Himalaya S-series servers access to Ethernet and token-ring networks. This manual is written for system managers, operators, and others who configure and manage network subsystems on Himalaya S-series servers. PAM supports G-series releases.
Your Comments Invited About This Manual Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the Tandem User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
1 Introduction to Tandem FTAM For Tandem NonStop systems, Tandem Open Systems Interconnection/File Transfer, Access, and Management (Tandem OSI/FTAM) implements the FTAM service and protocol specification ISO 8571, defined by the International Standards Organization (ISO). The five-part ISO 8571 standard specifies the basic functions for an implementation of ISO FTAM.
Introduction to Tandem FTAM Implemented Standard Tandem FTAM communicates with FTAM implementations on remote computer systems by establishing associations with these remote implementations. The Tandem FTAM initiator makes requests to remote FTAM implementations on behalf of applications running on a Tandem system. The Tandem FTAM responder services requests initiated by remote FTAM implementations.
Tandem FTAM Interfaces Introduction to Tandem FTAM Tandem FTAM Interfaces As shown in Figure 1-1, two interfaces allow you to directly interact with Tandem FTAM. The API allows you to use the Tandem FTAM services. The management interface provides a means for monitoring and managing the Tandem FTAM software. Figure 1-1.
Introduction to Tandem FTAM Tandem FTAM Components FTAM Application Program Interface (API) The FTAM API allows you to write applications that use the initiator services of Tandem FTAM. The FTAM API provides a set of procedures that implement ISO FTAM initiator functions. Programmers can incorporate these procedures into applications developed in either the Tandem Transaction Application Language (TAL) or the C programming language.
Tandem FTAM Components Introduction to Tandem FTAM Figure 1-2 shows the components of the Tandem FTAM software. Figure 1-2. Tandem FTAM Components User application API DSM APLMGR Subsystem FTAM Subsystem SCF EMS APLMGR Initiator Guardian File System PTrace Responder (VFS) MIB OSI/AS OSI/TS TLAM (or PAM) or X25AM or TCP/IP Communications Network CDT 004.
Introduction to Tandem FTAM Tandem FTAM Components Application Manager (APLMGR) Subsystem on page 1-6 and FTAM Subsystem on page 1-6 describe the components shown in Figure 1-2 on page 1-5. FTAM Subsystem further describes the components shown in the figure in its subsections Initiator Process, Responder Process, and Virtual Filestore (VFS), all on page 1-7.
Introduction to Tandem FTAM Tandem FTAM Components Initiator Process The Tandem FTAM initiator process allows FTAM applications on a Tandem NonStop system to access FTAM protocol and to request services of a responder on a remote computer system. The initiator process operates by establishing an association with the remote responder over the OSI network. The initiator then sends and receives FTAM protocol data units (PDUs) to and from the remote responder.
Introduction to Tandem FTAM OSI/AS, OSI/TS, and TLAM, PAM, X25AM, or TCP/IP OSI/AS, OSI/TS, and TLAM, PAM, X25AM, or TCP/IP Part of the overall Tandem FTAM architecture are the services provided by OSI/Application Services (OSI/AS), OSI/Transport Services (OSI/TS), and one of the following data communications subsystems: the Tandem LAN Access Method (TLAM) for D-series systems or, for G-series systems, the Port Access Method (PAM); the X.25 Access Method (X25AM); or Tandem NonStop TCP/IP.
OSI/AS, OSI/TS, and TLAM, PAM, X25AM, or TCP/IP Introduction to Tandem FTAM Figure 1-3 shows the major components of the subsystems that support Tandem FTAM. Figure 1-3. Underlying Subsystems Supporting Tandem FTAM User application API DSM SCF Tandem FTAM Guardian File System EMS PTrace OSI/AS OSI Manager TAPS OSI/TS TSP MIB TLAM (or PAM) or X25AM or TCP/IP NSP Communications Network Remote FTAM Initiator Remote FTAM Responder CDT 005.
Introduction to Tandem FTAM OSI/AS, OSI/TS, and TLAM, PAM, X25AM, or TCP/IP The following subsections provide a general discussion of the OSI/AS, OSI/TS, and TLAM (or PAM), X25AM, and TCP/IP subsystems: • • • Tandem Open Systems Interconnection/Application Services (Tandem OSI/AS) on this page Tandem Open Systems Interconnection/Transport Services (Tandem OSI/TS) on this page OSI/TS and Tandem NonStop TCP/IP, TLAM (or PAM), and X25AM on page 1-11 Tandem Open Systems Interconnection/Application Services
Introduction to Tandem FTAM OSI/AS, OSI/TS, and TLAM, PAM, X25AM, or TCP/IP OSI/TS and Tandem NonStop TCP/IP, TLAM (or PAM), and X25AM OSI/TS uses OSI Transport Protocol class 0 while running over TCP/IP, because the Transport Control Protocol (TCP) itself provides the features of error-recovery, errordetection, or multiplexing within TCP. The Tandem NonStop TCP/IP subsystem runs on the Tandem NonStop Kernel operating system over an X25AM or a TLAM (or a PAM for G-series) input/output (I/O) process.
Tandem FTAM in the OSI Reference Model Introduction to Tandem FTAM Tandem FTAM in the OSI Reference Model Figure 1-4 shows how the Tandem FTAM architecture fits into the various layers of the OSI Reference Model for both LANs and WANs. OSI/AS, OSI/TS, TLAM, X25AM, PAM, and TCP/IP are represented by their respective TAPS, TSP, and NSP processes. The figure also shows the hardware used to implement lower-layer communications through TLAM, PAM, or X25AM, as defined under Hardware Requirements on page 1-13.
Introduction to Tandem FTAM Subsystem Interdependencies Subsystem Interdependencies For Tandem FTAM to communicate across an OSI network, the following entities must be fully configured and running: • • • • • • OSI manager process and MIB TLAM (or PAM for G-series) or X25AM subsystem, or both OSI/TS subsystem OSI/AS subsystem APLMGR subsystem FTAM subsystem To communicate with remote computer systems, your APLMGR subsystem configuration must specify the Guardian name of the OSI manager process managing
Software Requirements Introduction to Tandem FTAM Table 1-1. Communications Controller Requirements Subnetwork Types Protocol/Interface Controllers X.25 WANs RS-232C and RS-449 RS-232C X.21 (leased lines) V.35 36xx, 61xx, 62xx 36xx 36xx, 61xx 36xx, 61xx Local area subnetworks 802.3 CSMA/CD 36xx, 56xx TCP/IP wide area networks X.25 36xx, 61xx, 62xx 36xx 36xx, 61xx 36xx, 61xx Software Requirements Table 1-2 lists the software products you need to have running on your system to use Tandem FTAM.
Introduction to Tandem FTAM Security Considerations Security Considerations Logon and disk-file access security on Tandem systems is enforced by the operating system, and by the Safeguard security software, if used. Section 3, Planning, Installing, and Configuring Tandem FTAM, describes how you can control access to a Tandem FTAM responder process and its associated file storage.
Introduction to Tandem FTAM OSI/FTAM Configuration and Management Manual—421944-001 1-16 Fault Tolerance
2 FTAM Management Environment This section describes the three Distributed Systems Management (DSM) tools you can use to manage OSI/FTAM: the Subsystem Control Facility (SCF), the Event Management Service (EMS), and the PTrace (print trace) utility.
Distributed Systems Management (DSM) Tools FTAM Management Environment Figure 2-1. Tandem FTAM and the DSM Environment User application Management Interface API DSM Tools SCF Tandem FTAM EMS Guardian File System PTrace OSI/AS OSI/TS TLAM (or PAM) or X25AM or TCP/IP Communications Network Remote FTAM Initiator Remote FTAM Responder CDT 007.CDD SCF is a command interpreter that allows you to manage Tandem FTAM in a manner similar to the way you manage many other Tandem products.
FTAM Management Environment Using SCF to Manage Tandem FTAM The Print Trace utility (PTrace) formats trace data for output to terminals, printers, and disk files. You use the SCF TRACE command to collect traces of various kinds of process activity and then use PTrace to display and analyze the traced information. These three DSM tools create the management environment for the Tandem FTAM product. The remainder of this section discusses how each of these tools applies to Tandem FTAM.
Using SCF to Manage Tandem FTAM FTAM Management Environment Figure 2-2. SCF Management Interface SCF SCF Commands Displays Tandem FTAM SCF APLMGR SCP Initiator Responder CDT 008.CDD When you enter an SCF command at your terminal, you also must specify the object on which the command is to act. Command/object combinations allow you to configure, monitor, and control the Tandem FTAM software. SCF Objects on page 2-9 discusses SCF commands and objects for the APLMGR and FTAM subsystems.
FTAM Management Environment SCF Commands and Object Types SCF Commands and Object Types SCF commands allow you to configure and manage Tandem FTAM. Table 2-1 lists the SCF commands used to manage Tandem FTAM, describes command functions, and lists the types of objects to which you can apply the commands. Table 2-1.
Sensitive and Nonsensitive SCF Commands FTAM Management Environment Table 2-1. SCF Commands and Associated Object Types (page 2 of 2) Command Function Applicable Object Types SUSPEND Changes the state of an object from STARTED to SUSPENDED. PROCESS TRACE Starts, modifies, or stops the gathering of trace data. PROCESS VERSION Displays information about the product version.
SCF Help Utility FTAM Management Environment Note. The owner, or process accessor ID, of the Tandem FTAM responder process changes depending on the particular remote application process that is using the responder services. This condition does not affect the operation of sensitive commands that are issued to a responder through the APLMGR process, because the ownership of the APLMGR process determines whether these commands can be executed.
FTAM Management Environment SCF Error Messages The subsystem variable uses the values OSIAPLMG and OSIFTAM for the APLMGR and FTAM subsystems, respectively. For example, to get information about the DELETE command for the APLMGR subsystem, you would use the command HELP OSIAPLMG DELETE This command returns the following help screen: DELETE Command The DELETE command removes the definition of the object that you specify from the APLMGR configuration database. DELETE is a sensitive command.
SCF Objects FTAM Management Environment SCF Objects Objects provide SCF commands a target on which to act. Using objects, you can direct commands to an entire subsystem (SUBSYS object) or one of its components such as a subdevice (SU object). This subsection discusses the different object types supported by Tandem FTAM and how you can use them in configuring and managing a Tandem FTAM installation.
FTAM Management Environment FTAM Object Types and Hierarchy FTAM Object Types and Hierarchy The FTAM subsystem supports two object types: PROCESS and SU (subdevice). Figure 2-4 shows the hierarchical relationship of these two object types: in the Tandem FTAM subsystem, the PROCESS object controls the SU objects. (Again, the null object type is supported but is not shown in the diagram, because it is not a true object type and has no place in the hierarchy.) Figure 2-4.
FTAM Management Environment Object States Object States An object state describes the condition of the object and its readiness to do work. For example, a process can be in the STARTED, STOPPED, or SUSPENDED state, and each of these states has different implications for what can be done with the object. Three Tandem FTAM object types—SUBSYS, PROCESS, and SU—have states you can display by using SCF commands. There are no displayed states for PROFILE objects.
FTAM Management Environment SUBSYS Objects SCF Commands for the null Object Only two commands are valid for the null object type: NAMES VERSION The NAMES null command refers to a collection of object types; for the VERSION null command, the object type is irrelevant. The following are examples of SCF commands that use the null object type.
SUBSYS Objects FTAM Management Environment SUBSYS Object Attributes SUBSYS object attributes allow you to modify the configuration of the subsystem using the SCF ALTER command. The location of the FTAM initiator and responder object files, the maximum number of processes that can be started, the MIB location, and the name of the OSI manager process are all attributes that you can configure for the SUBSYS object. Table 2-4 describes these attributes. Table 2-4.
FTAM Management Environment PROCESS Objects PROCESS Objects There are three types of processes in Tandem FTAM: the APLMGR process, the FTAM initiator process, and the FTAM responder process. The PROCESS object type allows you to address these processes individually. Using PROCESS objects, you can either send commands directly to an APLMGR, FTAM initiator, or FTAM responder process, or you can send commands to an FTAM initiator or responder process indirectly through the APLMGR process.
PROCESS Objects FTAM Management Environment PROCESS Object States A PROCESS object has four states—STARTED, STOPPED, SUSPENDED, and UNDEFINED—and four intermediate states—STARTING, ABORTING, STOPPING, and SUSPENDING. Table 2-5 describes the states and intermediate states of the PROCESS object. Table 2-5. Process and Intermediate States Process State Description of Process Condition ABORTING The process is in transition to the STOPPED state because the ABORT command has been received.
PROCESS Objects FTAM Management Environment Figure 2-5 illustrates the process states, the commands that produce each state, and the intermediate states that exist during process-state transitions. Figure 2-5. Process-State Transitions UNDEFINED STOPPED START PROCESS Aborting Stopping Starting ABORT PROCESS STOP PROCESS Suspending SUSPEND PROCESS SUSPENDED Aborting Stopping ABORT PROCESS STOP PROCESS STARTED ACTIVATE PROCESS Starting START PROCESS CDT 011.
PROCESS Objects FTAM Management Environment Processes in some states can accept only certain commands. Table 2-6 lists the SCF commands that can be applied to processes in the STOPPED, SUSPENDED, and STARTED states. Note that you can issue the ALTER command to a process in the STARTED state only if it is a responder process and you are changing the ALLOWSU attribute. Table 2-6.
PROCESS Objects FTAM Management Environment PROCESS Object Attributes PROCESS object attributes allow you to configure and modify the configuration of FTAM initiator and responder processes located on your local or on remote systems. Table 2-8 and Table 2-9 describe the attributes of a PROCESS object and indicate which process types (initiator and/or responder) apply to each attribute.
PROCESS Objects FTAM Management Environment Table 2-9 describes the attributes used by APLMGR in managing the initiators and responders. Table 2-9.
FTAM Management Environment SU (Subdevice) Objects PROCESS Object Names The form of the object name for the PROCESS object determines if a command destined for an initiator or a responder process will be sent to that process directly or if it will be sent through the APLMGR process. Tandem FTAM supports two object-name formats for PROCESS objects. The first format names processes directly using the external Guardian process name, as in the following examples: ACTIVATE PROCESS \MARS.
SU (Subdevice) Objects FTAM Management Environment Figure 2-6 shows the differences between initiator and responder subdevices along with their relationship to subdevices in underlying subsystems. Figure 2-6. Tandem FTAM Subdevices User Application Initiator Responder Tandem FTAM TAPS TAPS OSI/AS TSP TSP OSI/TS = Subdevice CDT 012.
FTAM Management Environment PROFILE Object SU Object Names The names of subdevices associated with FTAM initiator processes are assigned by the APLMGR process so that they are unique within the subsystem. These names always begin with #Z, followed by six decimal digits—for example, #Z254634. The APLMGR process keeps an internal count of initiator requests and assigns numeric identities to initiator subdevices, beginning with 000001.
FTAM Management Environment PROFILE Object PROFILE Object Attributes PROFILE object attributes allow you to configure and alter profiles for FTAM responder processes. Table 2-10 describes the attributes of a PROFILE object. Table 2-10.
FTAM Management Environment Using the Event Management Service (EMS) With Tandem FTAM Using the Event Management Service (EMS) With Tandem FTAM EMS provides event collection, event logging, and event distribution facilities for Tandem FTAM. EMS enables you to monitor events that occur during the operation of Tandem FTAM and other subsystems. This subsection discusses EMS in relation to Tandem FTAM. For detailed information on EMS itself, see the EMS Manual.
FTAM Management Environment EMS Interface EMS Interface A collector process within EMS (either the primary process or the alternate process, or both) collects event messages from APLMGR, FTAM initiator, and FTAM responder processes and writes those events to a log file within EMS. EMS distributor processes read the event log file, which also contains event messages from other subsystems. Each distributor process uses filters to select subsets of messages for routing to various destinations.
EMS Interface FTAM Management Environment Figure 2-7 shows how EMS receives event messages from the FTAM and APLMGR subsystems and routes them to their destinations. Figure 2-7.
FTAM Management Environment Event Messages Event Messages When a subsystem or system component detects an event that might affect its operation, it generates an event message describing the event. Such event messages can be related to hardware or software malfunctions or to important changes in the state of a system component. Text (readable) versions of these event messages can be displayed as operator messages.
FTAM Management Environment Displaying Saved Event Messages The distributor $DIST1 displays messages for all events reported from the time you start the distributor until you stop it. Because the distributor has been assigned a name, you can stop the process that has that name. As a general rule, distributor processes should be named. You can use similar commands to run printing distributors to other terminals or printers by substituting other names for $TERM1.
FTAM Management Environment Using TRACE and PTrace With Tandem FTAM Using TRACE and PTrace With Tandem FTAM You can use the combination of the SCF TRACE command and the PTrace utility to trace Tandem FTAM activity. This subsection discusses how to use SCF to trace process activity and PTrace to view collected information. Objects Supporting Traces The TRACE command is valid only for the PROCESS object.
FTAM Management Environment Traceable Process Activities Traceable Process Activities The TRACE command allows you to select the process activities you want to trace. You can use SCF to trace any or all of the following information, then display the information using PTrace: • • • • • • • • User-interface requests for services from FTAM initiator processes FTAM-related protocol data units (PDUs) of the provider interface Input and output from ASN.
Traceable Process Activities FTAM Management Environment Figure 2-8 shows process activities that are traceable using the SCF TRACE command. This figure shows the keywords used as select options for the TRACE command and demonstrates visually what type of process activity each keyword selects for tracing. If you select the default option for a trace, all types of data are collected. You can apply the select options in Figure 2-8 to the PTrace command to choose the trace records you want to analyze.
FTAM Management Environment Traceable Process Activities Table 2-12 lists and describes the select options shown in Figure 2-8 on page 2-31. The table also indicates which processes you can trace through each option. Table 2-12.
3 Planning, Installing, and Configuring Tandem FTAM This section presents information for installing and configuring Tandem FTAM.
Planning, Installing, and Configuring Tandem FTAM Underlying Subsystems Underlying Subsystems You also need to understand how to configure the underlying Tandem OSI subsystems. The configuration set up in the OSI manager MIB, through OSI/AS SCF commands, configures the architecture of underlying subsystems, sets up OSI addressing relationships, and establishes protocol parameters for the Session Layer and below.
Planning, Installing, and Configuring Tandem FTAM Process Architecture Considerations Process Architecture Considerations Each APLMGR subsystem, consisting of an APLMGR process and its MIB, uses the services of a single OSI/AS subsystem: that is, a single OSI manager process, its OSI manager MIB, and the associated TAPS, TSP, and NSP processes.
Planning, Installing, and Configuring Tandem FTAM Process Architecture Considerations Also easy to manage, but with higher capacity, is one APLMGR process with multiple initiators and/or responders, and one OSI/AS subsystem, as shown in Figure 3-2. Figure 3-2. One APLMGR Process Managing Multiple Initiators and Responders Initiator Responder Initiator Responder APLMGR MIB OSI/AS OSI/TS OSI Manager TLAM (or PAM) or X25AM or TCP/IP MIB CDT 016.
Planning, Installing, and Configuring Tandem FTAM Process Architecture Considerations Figure 3-3. Multiple APLMGR Processes, Each Managing One Initiator or One Responder APLMGR MIB APLMGR MIB OSI APLMGR Manager MIB OSI APLMGR Manager MIB Initiator or Responder OSI/AS Initiator or Responder ••• OSI/AS OSI/TS OSI/TS TLAM (or PAM) or X25AM or TCP/IP TLAM (or PAM) or X25AM or TCP/IP CDT 017.
Planning, Installing, and Configuring Tandem FTAM Configuration Information in the OSI Manager MIB Configuration Information in the OSI Manager MIB This subsection provides basic information on configuring OSI addresses, processes, and protocols in the OSI manager MIB for use by Tandem FTAM initiators and responders.
Planning, Installing, and Configuring Tandem FTAM Configuration Information in the OSI Manager MIB Using Common Names to Identify OSI Addresses OSI/AS allows you to identify the four components of an OSI address locally by using a single name. This name is called an application name in OSI/AS and a common name in FTAM.
Planning, Installing, and Configuring Tandem FTAM Configuration Information in the OSI Manager MIB The OSI manager MIB maintains the correspondence between common names and OSI addresses by using APPL ENTRY objects and provides translation from common names to OSI addresses. Common names are used locally only; the actual OSI addresses are transmitted across the OSI network, as shown in Figure 3-4. Figure 3-4.
Planning, Installing, and Configuring Tandem FTAM Configuration Information in the OSI Manager MIB Use of Common Names With a Tandem Initiator Suppose a Tandem FTAM application on System A in Figure 3-4 on page 3-8 issues a request for FTAM services specifying a local common name and a remote common name. The FTAM subsystem routes the common names to its associated OSI/AS subsystem, which looks up the corresponding OSI addresses in its OSI manager MIB.
Planning, Installing, and Configuring Tandem FTAM Configuration Information in the OSI Manager MIB Addressing of Tandem Responders All FTAM associations with a particular responder process use the common name or OSI address configured for that responder through its VFS profile. VFS profiles, which can be shared by several responders, allow multiple responders to share the same common name (that is, the same OSI address). One advantage of sharing profiles is load distribution.
Planning, Installing, and Configuring Tandem FTAM How Configured Information Is Used in Making FTAM Associations Configuration of Remote Responders If your applications use remote common names, you must also configure these common names and their corresponding OSI addresses in the OSI manager MIB. For remote addresses, you need to configure only the common name and the OSI address components; no servers or profiles are required.
Planning, Installing, and Configuring Tandem FTAM How Configured Information Is Used in Making FTAM Associations How an FTAM Association Is Made Through a Tandem Initiator Figure 3-5 shows how an FTAM association is established through a Tandem initiator. Figure 3-5.
Planning, Installing, and Configuring Tandem FTAM How Configured Information Is Used in Making FTAM Associations The following steps occur when Tandem FTAM is started: 1. A system operator or a command file sends the APLMGR process an SCF START command to start the initiator. 2. The APLMGR process retrieves information from its MIB as follows: Using This Item... Internal initiator name in the START command The APLMGR Process Selects This MIB Entry... PROCESS And Extracts This Information...
Planning, Installing, and Configuring Tandem FTAM How Configured Information Is Used in Making FTAM Associations 9. The OSI manager retrieves information from its MIB, as shown in the following table: The OSI Manager Process Selects This MIB Entry... And Extracts This Information...
Planning, Installing, and Configuring Tandem FTAM How Configured Information Is Used in Making FTAM Associations 15. On behalf of the initiator, the OSI/AS API opens the TAPS subdevice and sends a message, including the OSI address, to request an ACSE association through that subdevice. 16. TAPS sends a connect register request to the TSP process. 17. The TSP process establishes a connection through the NSP process.
Planning, Installing, and Configuring Tandem FTAM How Configured Information Is Used in Making FTAM Associations How an FTAM Association Is Made to a Tandem Responder Figure 3-6 shows the steps to establish an FTAM association to a Tandem responder. Figure 3-6.
Planning, Installing, and Configuring Tandem FTAM How Configured Information Is Used in Making FTAM Associations The following steps occur when Tandem FTAM is started: 1. A system operator or command file sends the APLMGR process an SCF START command to start the responder. 2. The APLMGR process retrieves information from its MIB as follows Using This Item... The APLMGR Process Selects This MIB Entry... and Extracts This Information...
Planning, Installing, and Configuring Tandem FTAM How Configured Information Is Used in Making FTAM Associations 8. The OSI manager then sends an internal ADD SU request to the local TAPS server process, using the TAPS subdevice name chosen in step 6. This ADD SU request includes the name of the TSP process. The TAPS subdevice corresponds to the responder’s attach and will be displayed as a responder subdevice in response to SCF commands sent to the responder.
Planning, Installing, and Configuring Tandem FTAM Security of Files in a Tandem Responder’s Virtual Filestore (VFS) Security of Files in a Tandem Responder’s Virtual Filestore (VFS) When setting up Tandem FTAM responder processes, you must determine how you want to control access to each responder and its virtual filestore (VFS). Security on Tandem systems is enforced by the Tandem NonStop Kernel, the Expand network operating software, and the Safeguard system-software security package, if used.
Planning, Installing, and Configuring Tandem FTAM Logon Access If you configure the DEFUSER attribute with a user ID but omit the password, associations with the responder succeed only if the specified user ID has no associated Guardian password.
Planning, Installing, and Configuring Tandem FTAM Disk-File Access You should choose how the user ID and password are specified based on the needs of your installation. If you want to avoid having remote users send passwords over communications lines, you must use the DEFUSER attribute.
Planning, Installing, and Configuring Tandem FTAM Mapping of FTAM File-Security Attributes to Guardian Security Settings For Safeguard-protected files, Safeguard security is enforced. The responder cannot translate Safeguard security attributes into the FTAM access-control attribute. Therefore, when a remote application reads the attributes of a file that the Safeguard security software protects, the access-control attribute indicates that no value is available.
Planning, Installing, and Configuring Tandem FTAM Mapping of FTAM File-Security Attributes to Guardian Security Settings Further, for Safeguard-protected files, the access-control attribute is partially rather than fully supported. For these files, no mapping to Guardian security is attempted, and the responder indicates that no value is available when it reads the access-control attribute. In this case, attempts to change the attribute fail.
Planning, Installing, and Configuring Tandem FTAM Mapping of FTAM File-Security Attributes to Guardian Security Settings The mapping of FTAM action-list settings to Guardian security settings is summarized in Table 3-3. Table 3-3. Mapping From FTAM Action List to Guardian Security If Action List Is Set to... Guardian Security Is Modified to...
Planning, Installing, and Configuring Tandem FTAM Mapping of FTAM File-Security Attributes to Guardian Security Settings The following rules apply to changing the access-control attribute: For insert values: • • • If the read access-control bit of the action-list is set, the responder sets READ access to N, indicating that any user on the Expand network can read the file.
Planning, Installing, and Configuring Tandem FTAM Mapping of FTAM File-Security Attributes to Guardian Security Settings File Attributes Read by a Remote FTAM User When the Tandem responder reads FTAM file attributes on behalf of a remote user, it maps the values for access control from Guardian security based on the user ID for the association, as defined by the initiator-identity parameter sent in the F-INITIALIZE request or by the DEFUSER attribute specified in the VFS profile used by this responder.
Planning, Installing, and Configuring Tandem FTAM Using Tandem FTAM Configuration Attributes Using Tandem FTAM Configuration Attributes The following subsections describe how to perform these configuration functions: • • • • • • Configuring OSI Addresses and Common Names Naming Processes on page 3-29 Allocating Resources on page 3-30 Controlling System Performance on page 3-33 Monitoring Protocol Errors on page 3-36 Determining Access to Tandem Responders on page 3-37 You perform these functions by usi
Planning, Installing, and Configuring Tandem FTAM Configuring OSI Addresses and Common Names The following commands add a process named FTI1 that has the given OSI address and a profile named VFS1 that has the specified OSI address: ADD PROCESS $AMGR.#FTAMI.FTI1, NAME $FTI1, & PSEL 43, SSEL 0176, TSEL 54, NSAP 30104085551212 ADD PROFILE $AMGR.#VFS.
Planning, Installing, and Configuring Tandem FTAM Naming Processes Naming Processes In your Tandem FTAM configuration, you must specify process names to be used for reference throughout your configuration and by the NonStop Kernel operating system.
Planning, Installing, and Configuring Tandem FTAM Allocating Resources Allocating Resources Resource allocation allows you to plan how you want to distribute the workload on your system.
Planning, Installing, and Configuring Tandem FTAM Allocating Resources Location of Process Code Files Three attributes—FTAMIFILE, FTAMRFILE, and CODEFILE—specify the location of the code files for creating initiator and responder processes. FTAMIFILE and FTAMRFILE are attributes of the SUBSYS object. They allow you to specify a default location—that is, volume name, subvolume name, and filename—for the code files for initiator and responder processes.
Planning, Installing, and Configuring Tandem FTAM Allocating Resources Primary and Backup Processors for Initiator and Responder Processes The CPU and BACKUPCPU attributes of the PROCESS object specify the processors on which the primary and backup processes run. If you specify a primary processor when you use the TACL RUN command to create the APLMGR process, the primary processor becomes the default processor when you create processes managed by that APLMGR process.
Planning, Installing, and Configuring Tandem FTAM Controlling System Performance Controlling System Performance The following object attributes affect the performance of your Tandem FTAM implementation, as described in the following subsections: • • • • • Number of Process Assocations and Attaches on this page Maximum Number of Configurable Processes on page 3-34 Execution Priority on page 3-34 Regeneration of Subdevices on page 3-35 Resource Allocation Interdependencies on page 3-36 By manipulating th
Planning, Installing, and Configuring Tandem FTAM Controlling System Performance For example, to allow the responder $FTR1 to post a maximum of four attaches and to service a maximum of four associations, you could configure the process with the following command: ADD PROCESS $AMGR.#FTAMR.FTR1, NAME $FTR1, & PROFILE $AMGR.#VFS.
Planning, Installing, and Configuring Tandem FTAM Controlling System Performance Regeneration of Subdevices Each FTAM subdevice services a particular association through an FTAM initiator or responder. When an initiator or responder process completes an association and no longer requires the subdevice, the process discards the subdevice. Each initiator process creates its own subdevices as it receives requests for associations, using subdevice names furnished to it by the APLMGR process.
Planning, Installing, and Configuring Tandem FTAM Monitoring Protocol Errors Resource Allocation Interdependencies Obviously, there is some overlap between these functional groupings. For example, where you allocate resources such as code files, swap volumes, and the MIB file affects how your system performs. Keep in mind that several of the attributes discussed here are interdependent. Consider how the setting for one attribute might affect other attributes.
Planning, Installing, and Configuring Tandem FTAM Determining Access to Tandem Responders In a production environment, you might want to set the value to 1, so that you can see all protocol errors: ADD PROCESS $AMGR.#FTAMI.FTI2, NAME $FTI2, COMNAME "FTMI2", & THRESHOLD 1 You also can use this attribute for troubleshooting. A large number of protocol errors may indicate potential FTAM software or interoperability problems.
Planning, Installing, and Configuring Tandem FTAM Example FTAM Configuration Example FTAM Configuration The following example FTAM configuration provides you with a point of reference for configuring and managing your installation. The remaining sections of this manual use this example configuration to illustrate subsystem management and troubleshooting procedures.
Planning, Installing, and Configuring Tandem FTAM Tandem FTAM Product Distribution Figure 3-7. Example FTAM Configuration User application API Tandem FTAM $FTI2 $AMGR Management Interface $FTI1 $FTR2 ZOSADB Guardian File System $FTR1 OSI/AS $L51 $OSM1 OSI/TS $L41 MIB X25AM CDT 023.CDD Tandem FTAM Product Distribution Table 3-5 lists the installation subvolumes and describes the type of information in those subvolumes.
Planning, Installing, and Configuring Tandem FTAM FTAM Configuration Overview Table 3-5.
Planning, Installing, and Configuring Tandem FTAM Installation, Configuration, and Startup Instructions Installation, Configuration, and Startup Instructions Before you begin configuring FTAM, you must install and configure the supporting communications lines, management components, and processes that work together to provide OSI and management services. Installing the Basic Components Installing the basic components for FTAM involves four main tasks.
Planning, Installing, and Configuring Tandem FTAM Installing the Basic Components Recompiling Responder Object Files Using NonStop SQL If applications using the Tandem responder access SQL tables as FTAM-2 files, you must use NonStop SQL to recompile the responder object files. To do this, issue the following TACL (implicit) RUN command: SQLCOMP / IN FTAMROBJ / CATALOG sys-catalog-subvol For sys-catalog-subvol, specify the subvolume you use for your SQL system catalog.
Planning, Installing, and Configuring Tandem FTAM Installing the Basic Components Configuring the OSI/AS Subsystem for FTAM Once the OSI/AS, OSI/TS, and TLAM, X25AM, PAM, or TCP/IP subsystems are running, configure the OSI/AS subsystem to communicate with Tandem FTAM. The OSI/AS Configuration and Management Manual explains how to configure OSI/AS.
Planning, Installing, and Configuring Tandem FTAM • Installing the Basic Components Tandem FTAM does not retrieve application entity titles (AE titles) from the APPL ENTRY configuration. If you are using the Tandem initiator and the remote FTAM implementation expects to be sent local and/or remote AE titles, you can specify the AE titles in your application, and the initiator will send the AE titles you specify.
Planning, Installing, and Configuring Tandem FTAM Installing the Basic Components Creating the MIB Database for APLMGR The MIB is the database in which APLMGR stores configuration information for FTAM processes and profiles. You must create the MIB database before you can add any FTAM processes or profiles. Creating a New MIB For new FTAM installations and for existing FTAM installations for which you want to create a new MIB, use the MAKDB file discussed in the following paragraphs.
Planning, Installing, and Configuring Tandem FTAM Installing the Basic Components Using an Old MIB For existing FTAM installations for which you want to use an existing APLMGR MIB, you must first back up the MIB and then restore it. Caution. Do not use the MAKDB file—it does not retain the contents of an existing MIB. Creating and Starting the APLMGR Process After you have created the MIB file, the next step is to create and start the APLMGR process.
Planning, Installing, and Configuring Tandem FTAM Installing the Basic Components 2. Modify necessary attributes of the subsystem object using the SCF ALTER SUBSYS command. In most cases, the default attributes for the subsystem will not be adequate for your installation. For example, the MIB filename and the name of the OSI manager process on your system will probably not be the same as the default values established for the SUBSYS object.
Planning, Installing, and Configuring Tandem FTAM Starting and Adding an Alternate Collector Starting and Adding an Alternate Collector All Tandem FTAM processes default to sending event messages to the primary collector, $0. However, you can choose to have messages sent to an alternate collector, or to both the primary collector and an alternate collector. This is determined by the value of EVENTDESTINATION in the FTC PROFILE object.
Planning, Installing, and Configuring Tandem FTAM Changing SUBSYS Object Attributes Changing SUBSYS Object Attributes When you install APLMGR, default values are automatically set for all SUBSYS attributes to provide an initial configuration. In most instances, these defaults will not be appropriate for your installation. In addition to the attributes you modified before you started the APLMGR process, you may need to modify some other SUBSYS attribute values.
Planning, Installing, and Configuring Tandem FTAM Changing SUBSYS Object Attributes The following display is returned: OSIAPLMG Detailed Info SUBSYS \NET.$AMGR *MaxFTAMI..... 128 *MaxFTAMR..... 128 Current FTAMI... 0 Current FTAMR... 0 *FTAMIfile...... \NET.$SYSTEM.SYS00.FTAMIOBJ *FTAMRfile...... \NET.$SYSTEM.SYS00.FTAMROBJ *MIB............... \NET.$SYSTEM.SYS00.ZOSADB *OMGRNAME.......... \NET.$OSIM The APLMGR process name ($AMGR) is displayed on the top line at the far right of the screen.
Planning, Installing, and Configuring Tandem FTAM Changing SUBSYS Object Attributes To change the maximum number of initiator and responder processes in the Example FTAM Configuration on page 3-38, use the following ALTER SUBSYS command: ALTER SUBSYS $AMGR, MAXFTAMR 8 & , MAXFTAMI 8 This command sets the maximum number of initiators and the maximum number of responders to 8.
Planning, Installing, and Configuring Tandem FTAM Adding, Changing, and Deleting VFS Profiles The second, third, and fourth steps are exactly as described earlier. Section 4, Managing the FTAM Configuration, discusses suspending processes, as well as stopping subdevices and processes. See the OSI/AS SCF Reference Manual for details on altering the subsystem configuration.
Planning, Installing, and Configuring Tandem FTAM Adding, Changing, and Deleting VFS Profiles Adding Profiles You must configure one VFS profile for each unique OSI address to be used by one or more responder processes. Profiles should be configured before you add responder processes, although this is not required. You must, however, have profiles configured before you start responder processes associated with those profiles; otherwise, you will be unable to start the processes.
Planning, Installing, and Configuring Tandem FTAM Adding, Changing, and Deleting VFS Profiles Deleting Profiles If you no longer want to configure responder processes using the characteristics provided by a given profile, you should either change the profile or delete it from your installation. You can proceed in either of the following ways: • • Reconfigure the profile using the SCF ALTER PROFILE command, as described in the previous subsection.
Planning, Installing, and Configuring Tandem FTAM Changing and Deleting an FTC Profile Changing and Deleting an FTC Profile Only one alternate collector (and, therefore, only one FTC profile) is allowed for each Tandem FTAM subsystem. Once an alternate collector is added, it cannot be altered. To change an FTC profile, you must first delete the profile and then add a new FTC profile. To change the FTC profile added earlier in this section, perform the following steps: 1.
Planning, Installing, and Configuring Tandem FTAM Configuring and Starting Initiator and Responder Processes Configuring and Starting Initiator and Responder Processes You can configure two types of FTAM processes using the SCF ADD command: the initiator and the responder. Initiator processes are responsible for receiving user requests, interpreting those requests, and communicating with a remote FTAM system through the OSI/AS subsystem.
Planning, Installing, and Configuring Tandem FTAM Configuring and Starting Initiator and Responder Processes You also can specify the ALLOWSU attribute, which determines if the process is able to automatically regenerate subdevices. However, normally you will want to leave this attribute configured with its default value, ON, until you wish to prepare to stop the process.
Planning, Installing, and Configuring Tandem FTAM Configuring and Starting Initiator and Responder Processes Changing Process Configurations Once a process is started, you may need to adjust PROCESS attributes for your installation. You can change the values of all attributes listed in Table 2-9 on page 2-19 using the ALTER command in SCF. You must first stop the process before issuing the ALTER command.
Planning, Installing, and Configuring Tandem FTAM Configuring FTAM Application Entities Configuring FTAM Application Entities The OSI/AS Configuration and Management Manual provides an illustration showing step-by-step configuration of an application entity.
Planning, Installing, and Configuring Tandem FTAM Initiator Application Entity Figure 3-8. Initiator Application Entity Example APLMGR MIB (for $AMGR) SUBSYS PROCESS Application Layer 1 2 ALTER SUBSYS $AMGR , MAXFTAMI 8 , MAXFTAMI 8 , OMGRNAME $OSM1 , MIB ZOSADB & & & & ADD PROCESS $AMGR.#FTAMI.
Planning, Installing, and Configuring Tandem FTAM Initiator Application Entity The steps shown in Figure 3-8 on page 3-60 are as follows: 1. First, use an ALTER SUBSYS command to change any APLMGR subsystem attributes for which you will not be using the installation defaults. This example defines the maximum numbers of FTAM initiator and responder processes, the OSI manager name, and the filename of the primary APLMGR MIB file. 2. Then add the initiator process, $AMGR.#FTAMI.FTI1, to the APLMGR MIB.
Planning, Installing, and Configuring Tandem FTAM Initiator Application Entity 7. At the Transport Layer, add the TSP process $OSM1.#TSP.L41. Associate this process with a unique process name, $L41, by which it will be known to the operating system. This example also specifies the primary and backup CPUs for the TSP process. 8. Next, add the NSAP ENTRY object, $OSM1.#NSAP.03, specifying the same NSAP value as that in the APPL ENTRY configuration.
Planning, Installing, and Configuring Tandem FTAM Responder Application Entity Responder Application Entity Figure 3-9 on page 3-64 shows the configuration of the first responder, $FTR1, in Appendix A, Example FTAM Configuration Command Files.
Planning, Installing, and Configuring Tandem FTAM Responder Application Entity Figure 3-9. Responder Application Entity Example APLMGR MIB (for $AMGR) SUBSYS PROCESS Application Layer 1 PROFILE 2 ALTER SUBSYS $AMGR , MAXFTAMI 8 , MAXFTAMI 8 , OMGRNAME $OSM1 , MIB ZOSADB & & & & 3 ADD PROCESS $AMGR.#FTAMR.FTR1 , NAME $FSR1 , PROFILE $AMGR.#VFS.VFS1 , CPU 1, BACKUPCPU 3 , SWAP $OSI, MAXATTACH 8 & & & & ADD PROFILE $AMGR.#VFS.VFS1 & , COMNAME “APPL1A” & , DEFUSER “USER.
Planning, Installing, and Configuring Tandem FTAM Responder Application Entity The steps shown in Figure 3-9 on page 3-64 are as follows: 1. First, use an ALTER SUBSYS command to change any APLMGR subsystem attributes for which you will not be using the installation defaults. This example defines the maximum numbers of FTAM initiator and responder processes, the OSI manager name, and the filename of the primary APLMGR MIB file. 2. Then add the responder process, $AMGR.#FTAMR.FTR1, to the APLMGR MIB.
Planning, Installing, and Configuring Tandem FTAM Responder Application Entity OSI/FTAM Configuration and Management Manual—421944-001 3- 66
4 Managing the FTAM Configuration Once you have configured Tandem FTAM, you must perform several important tasks to manage your installation.
Managing the FTAM Configuration Creating a New Configuration Command File Configuration command files and the MIB file are related in that you can use a command file to create the MIB. There are, however, two important differences you should be aware of when working with these two files: • • You can edit a configuration command file anytime. You can add or remove commands, edit existing command lines, or change command parameters.
Managing the FTAM Configuration Invoking a New Configuration Command File The length of the delay needed depends on the workload of the processor in which the APLMGR or OSI manager process runs: if the processor is heavily loaded, a longer delay is needed. If you do not include a delay or if the delay is not long enough, subsequent SCF commands that depend on completion of the START command will fail.
Managing the FTAM Configuration Using Multiple MIB Files 3. Use the PURGEDATA command in the File Utility Program (FUP) utility to remove old configuration data from the MIB file: FUP PURGEDATA ZOSADB FUP PURGEDATA ZOSADB0 Note that this command purges all information in any files named ZOSADB and ZOSADB0 that might exist in that volume and subvolume. For more information on the PURGEDATA command, see the File Utility Program (FUP) Reference Manual. 4.
Managing the FTAM Configuration Using Multiple MIB Files 2. Suspend the APLMGR process: SUSPEND PROCESS $AMGR 3. Change the MIB attribute using the SCF ALTER SUBSYS command. For this example ALTER SUBSYS $AMGR, MIB $DATA1.OSI.ZOSAEVE changes the filename of the MIB that the APLMGR process accesses to ZOSAEVE. 4. Activate the APLMGR process.
Managing the FTAM Configuration Retrieving Configuration Information Retrieving Configuration Information The ability to retrieve, view, and interpret information is vital to managing any installation. Management interfaces such as SCF provide you with the tools necessary to perform these important tasks. Information such as the number of initiator and responder processes running, object names, and object configuration is necessary to make management decisions that affect your FTAM installation.
Managing the FTAM Configuration Displaying Object Names When you direct the command to the APLMGR process, the display returns the APLMGR name, the names and types of all processes associated with that APLMGR, and the names of all associated profiles. Note the following example applied to the example FTAM configuration: NAMES $AMGR This command returns the following display. Note that the names in each category are not returned in any particular order: OSIAPLMG Names \NET.
Managing the FTAM Configuration Displaying Object Names SUBSYS Object A NAMES command is provided for the SUBSYS object; for example: NAMES SUBSYS $AMGR However, since this command merely returns the subsystem name that was specified in the command, it is not useful to interactive users. It is provided for conformance with general Tandem conventions for communications subsystems and might be useful in command files whose output is being saved to a log.
Managing the FTAM Configuration Displaying Object Names SU Object The NAMES SU command allows you to view the names of all subdevices associated with the FTAM process you designate in the command line. The NAMES command is especially helpful for subdevices because subdevices are created—and named— automatically. Note the following example: NAMES SU $FTR1.* OSIFTAM Names SU \NET.$FTR1.* SU $FTR1.#ZF00002 $FTR1.#ZF00004 $FTR1.#ZF00003 $FTR1.
Managing the FTAM Configuration Displaying the Subsystem Configuration PROFILE Object As is the case with the PROCESS object, you can use asterisks (*) with the NAMES command to display all of the profiles associated with this APLMGR, or you can select the profiles associated with this APLMGR by profile type. For the Tandem FTAM product, there is only one profile type: VFS. Knowing profile names is important when creating new FTAM responder processes.
Managing the FTAM Configuration Displaying Process Configurations This display shows that a maximum of eight initiator and eight responder processes can be configured and that two initiator and two responder processes are currently configured. The code file for initiator processes is \NET.$SYSTEM.SYS00.FTAMIOBJ, the code file for responder processes is \NET.$SYSTEM.SYS00.FTAMROBJ, and the APLMGR MIB file is \NET.$DATA.ZAPLMMIB.ZOSADB. The name of the OSI manager process in OSI/AS is $OSM1.
Managing the FTAM Configuration Displaying Process Configurations Additional information provided for responder processes, not shown in the example display, includes the following: • • • • • • Swap Threshold (0 indicates that no event messages are ever generated.) MaxAssoc (This field shows the maximum number of concurrent FTAM associations allowed between this responder process and remote initiators.
Managing the FTAM Configuration Displaying Profile Configurations Displaying Profile Configurations Tandem FTAM supports two types of profiles: a virtual filestore (VFS) profile that can later be associated with one or more responder processes, and an alternate collector (FTC) profile that defines an alternate collector for event messages. VFS Profiles To check the configuration of a VFS profile, use the SCF INFO PROFILE command.
Managing the FTAM Configuration Displaying Profile Configurations The following example (applied to Example FTAM Configuration on page 3-38) displays the configuration of the FTC profile. Note that the FTC profile does not have a profile name: INFO PROFILE $AMGR.#FTC This command returns the following display: OSIAPLMG Info Profile \NET.$AMGR.#FTC Name \NET.$AMGR.#FTC Collector \NET.
Managing the FTAM Configuration Controlling Open Requests Controlling Open Requests An open request is a request for the services of an FTAM initiator or responder process. SCF allows you to list information on all opens for a given process or subdevice, to prevent a process from receiving open requests, and to permit a process to receive open requests. Listing Open Requests The LISTOPENS command in SCF allows you to monitor the opens a process or subdevice is currently servicing.
Managing the FTAM Configuration Listing Open Requests Note that a LISTOPENS PROCESS display for an initiator or responder should always show the SCF and APLMGR openers; for an APLMGR process, the display should always show the SCP opener. If the same application has opened a specified initiator process more than once, a separate line of information is displayed for each open.
Managing the FTAM Configuration Stopping and Allowing Open Requests Stopping and Allowing Open Requests Once you have viewed the number of opens for an initiator process, you may decide that you want that process to concentrate on its current opens. In this case, you can force the initiator process to reject additional open requests by issuing the STOPOPENS command to that process. The command STOPOPENS PROCESS $AMGR.#FTAMI.
Managing the FTAM Configuration Controlling Object States Controlling Object States Another important tool for managing your installation is the ability to control object states. You can use SCF commands to control the states of subdevices and processes in an FTAM configuration. Aborting Subdevices The SCF command ABORT causes a subdevice to change from the STARTED state to being nonexistent—that is, it discards the subdevice.
Managing the FTAM Configuration Stopping Processes in an Orderly Fashion Stopping Processes in an Orderly Fashion To place a process in the STOPPED state, you can use either of two commands: ABORT or STOP. The ABORT command places a process in the STOPPED state abruptly, whether or not its processing of requests is completed. The STOP command can be issued only to a process that is no longer servicing requests, to place that process in the STOPPED state.
Managing the FTAM Configuration Aborting Processes Aborting Processes The ABORT command places processes in the STOPPED state without regard for the integrity of the data being processed. The ABORT PROCESS command automatically stops all pending requests for subdevices, stops all subdevices associated with the process, and then stops the process. Use the ABORT PROCESS command when you need to stop a process as quickly as possible, and the integrity of the data is less important than stopping the process.
Managing the FTAM Configuration Suspending and Activating Processes Because the ABORT command immediately and abruptly terminates all associations for the process, it should be used only in emergency situations. Examples of these types of situations include • • A situation in which an attribute in the configuration is incorrect, and you need to correct it quickly. In this case, the process may be servicing requests incorrectly, and you simply want to stop the process quickly and correct the situation.
Managing the FTAM Configuration Checking Association Status Checking Association Status The FTAM management interactive interface, the Subsystem Control Facility (SCF), can provide you with useful information on an association between a remote initiator and the Tandem responder. Each FTAM association is associated with one subdevice.
Managing the FTAM Configuration Checking Association Status To obtain status information, issue the SCF STATUS SU command for a specific responder subdevice: STATUS SU $FTR1.#ZF54321, DETAIL where $FTR1 refers to the process name of the FTAM responder, #ZF54321 is the name of the FTAM subdevice, and DETAIL is an optional request to display for all available information. This command displays the following: OSIFTAM Detailed Status SU \NET.$FTR1.#ZF54321 State Opens Error Error ............ ............ .
Managing the FTAM Configuration Checking Association Status The CEPI field identifies the association between the Tandem responder and remote initiator by means of its connection endpoint identifier (CEPI), and the TAPS SU field identifies the name of the TAPS subdevice used for the association. The FTAM Functional Units Selected field displays the functional units negotiated for the association between the calling and called entities. The information in this display might prove useful to you.
5 Monitoring FTAM Performance Many factors influence the system performance of OSI/FTAM, including the state of an object, the number of FTAM processes configured, and the location of a process swap file. This section provides instructions for system managers using SCF to tune system performance and maintain maximum throughput.
Monitoring FTAM Performance Monitoring Object Status Monitoring Object Status The SCF STATUS command provides information concerning the status of Tandem FTAM components. This information is useful if you note an inconsistency in the level of FTAM operation. For example, if you perform a particular file transfer on a daily basis and find one day that the transfer is taking longer than usual, the STATUS command can help you determine why.
Monitoring FTAM Performance Displaying Process Status Displaying Process Status To ensure that your FTAM subsystem is running correctly, you should monitor the status of FTAM initiator and responder processes. To display this information, issue the STATUS PROCESS command either to the FTAM initiator or responder process directly or to the FTAM process indirectly (through APLMGR).
Monitoring FTAM Performance Displaying Subdevice Status In addition to the information shown in the previous display, this display shows that a trace is currently in progress and that the SELECT option ALL was either specified in the command or was selected as a default (all keywords are listed in the display). The name of the file in which the trace data is being written is \NET.$OSI.TEST.TRACE. Note. Setting the TRACE option to ON can negatively affect performance.
Monitoring FTAM Performance Displaying Subdevice Status This command returns the following display: OSIFTAM Detailed Status SU \NET.$FTI1.#Z000001 State Opens Error Error ............ ............ ............ Subcode..... STARTED 1 0 0 CEPI ............. -10 TAPS SU .......... \NET.$L51.#Z000009 FTAM Functional Units Selected Read LimitedFileMgmt Calling Address: PSEL..... 01 SSEL..... 0110 TSEL..... 07 NSAP..... 03 ComName.. FTMI1A (LOCAL) Called Address: PSEL..... 10 SSEL..... 0119 TSEL.....
Monitoring FTAM Performance Displaying Subdevice Status This display provides the OSI addresses for various connections and associations across an OSI network. The addressing fields in the display are interpreted according to the type of activity. When a local initiator makes an association with a remote responder and you issue the STATUS SU command to the appropriate subdevice, for example STATUS SU $FTI2.
Monitoring FTAM Performance Monitoring Statistics Monitoring Statistics One important task when monitoring the system is verifying that the system is running at expected capacity.
Monitoring FTAM Performance Displaying Subsystem Statistics Displaying Subsystem Statistics To find out how current subsystem activity compares with activity at peak periods, issue the STATS SUBSYS command. This command is valid only if directed at the APLMGR process, as in this example: STATS SUBSYS $AMGR The command returns the following display: OSIAPLMG Stats SUBSYS \NET.$AMGR Reset Time..... 03 Apr 1992, 9:49:03.883 Sample Time.... 03 Apr 1992, 10:18:19.285 Configuration: FTAMI Process..............
Monitoring FTAM Performance Displaying Process Statistics The STATS SUBSYS display indicates the number of register requests APLMGR has received from user applications. The values returned for the register requests may be important to monitor. If several requests have been attempted and none has succeeded, the request might not have been able to find the resources it needs.
Monitoring FTAM Performance Displaying Subdevice Statistics Displaying Subdevice Statistics During the course of daily system monitoring, a process may unexpectedly slow down. To check the activities of a specific association, issue the STATS SU command and monitor the number of ACSE and Presentation PDUs (APDUs) being sent to the TAPS process and returned by it in support of the FTAM protocol.
Monitoring FTAM Performance Filtering Event Messages Filtering Event Messages As described in Section 2, FTAM Management Environment, a filter is a program you can write to select the event messages that you want to display, route, or process. Filtering strategies involve sorting the collected messages collected by EMS into logical groupings to which you can refer.
Monitoring FTAM Performance Reconfiguring the System to Improve Performance Reconfiguring the System to Improve Performance To improve system performance, you can reconfigure your system in one of several ways. For example, moving the swap file, adding processes, adjusting the maximum number of associations, adjusting the maximum number of attaches, and changing the processors in which your processes run all affect how your system performs.
Monitoring FTAM Performance Detecting the Need for Additional Processes To do so, issue an ADD PROCESS command. For example, to add a new initiator process named FTI3 to the example configuration (see Example FTAM Configuration on page 3-38), issue a command such as the following: ADD PROCESS $AMGR.#FTAMI.FTI3, NAME $FTI3, COMNAME "FTMI3A" & , CPU 2, BACKUPCPU 0, SWAP $OSI This command adds the definition of a new FTAM initiator with the internal name $AMGR.#FTAMI.
Monitoring FTAM Performance Adjusting the Maximum Number of Associations Adjusting the Maximum Number of Associations If you see error messages indicating that association requests from applications are failing, you may be able to solve the problem without adding processes. The maximum number of associations an FTAM initiator or responder process can make is determined by the MAXASSOC attribute of the process.
Monitoring FTAM Performance Redistributing Processes Among Processors Redistributing Processes Among Processors To maximize system efficiency, including the speed of disk access and response to requests, you should ensure that your workload is balanced over the resources available in the system. If you determine that one of your processors is overloaded, you can relocate some of your initiator or responder processes to different processors by changing the values of their CPU and BACKUPCPU attributes.
Monitoring FTAM Performance Reconfiguring OSI/AS Subsystem Attributes Reconfiguring OSI/AS Subsystem Attributes Configuration attributes set in the underlying OSI/AS subsystem(s) can have a marked effect on the performance of your FTAM applications. You should consider the number of TAPS, TSP, and NSP processes you use, their relationships to one another, and the values of various lower-layer service or profile parameters.
6 FTAM Troubleshooting This section provides information to help you diagnose problems encountered in the operation of Tandem FTAM and your application programs that use Tandem FTAM. It describes the available troubleshooting tools along with specific types of problems and their symptoms, with troubleshooting strategies for each type of problem.
FTAM Troubleshooting General Strategy General Strategy Troubleshooting an FTAM problem begins when you become aware that a problem exists. Depending on the kind of problem, you first notice it in one of two main ways: • • Your application does not function correctly and/or returns errors (in the case of a remote application using the Tandem responder, your application receives diagnostic messages from the responder).
FTAM Troubleshooting Troubleshooting Tools and Their Use Troubleshooting Tools and Their Use Tandem provides four main tools for troubleshooting problems you encounter when using Tandem FTAM.
FTAM Troubleshooting Inspect The filter you use for your EMS log should pass all FTAM and APLMGR critical events, which include those that cause an association to be lost. It should also pass securityviolation events. In addition, it should pass critical events from underlying subsystems, including OSI/AS, OSI/TS, and X25AM, TLAM, PAM, or TCP/IP. Under some circumstances during troubleshooting, you might want to pass additional events, such as the file transfer complete event.
FTAM Troubleshooting Inspect Figure 6-1 illustrates how to use the Inspect utility in troubleshooting an FTAM application. Run the application under Inspect and establish breakpoints at which to examine the data. Run the application program and view the data that the Inspect utility displays. Analyzing the data displayed by Inspect may point out the location of a problem in the code. Once you fix the problem, you can resume normal operations. Figure 6-1.
FTAM Troubleshooting Inspect If an APLMGR, an initiator, or a responder process abends, or if an application or a Tandem responder hangs, you should create an Inspect save file to capture more information about the problem. In the case of an abend, the operating system usually creates such a file automatically, placing it in a file named ZZBInnnn in the subvolume where the process’s object file resides.
FTAM Troubleshooting Subsystem Control Facility (SCF) TRACE Command and PTrace Utility Subsystem Control Facility (SCF) TRACE Command and PTrace Utility The PTrace (print trace) utility allows you to look at trace data generated by the SCF TRACE command. The TRACE command provides a log of message traffic between the various processes in your system; PTrace shows you the contents of these messages, including the types and contents of protocol data units (PDUs).
FTAM Troubleshooting Subsystem Control Facility (SCF) TRACE Command and PTrace Utility Figure 6-2 outlines a procedure to follow. Figure 6-2. Analyzing Process Traces Using PTrace Turn Tracing On Rerun Application Turn Trace Off View Trace File Using PTrace Recognize Problem YES NO Fix Problem Follow Standard Procedures at Your Site for Problem Resolution Resume Normal Operations CDT 022.
FTAM Troubleshooting Subsystem Control Facility (SCF) TRACE Command and PTrace Utility Trace data can help you understand what is happening as the APLMGR, FTAM, TAPS, TSP, and NSP processes attempt to perform the work of an application. Close examination of process activity can help you determine the source of a problem so that you can correct it.
FTAM Troubleshooting Other SCF Commands Other SCF Commands In addition to the TRACE command (see Subsystem Control Facility (SCF) TRACE Command and PTrace Utility on page 6-7), SCF provides a number of informational commands that can provide clues to the cause of a problem: • • • • • • • INFO shows you the currently configured attributes for a specified object (for example, the attributes configured in the APLMGR MIB for a particular initiator process.
FTAM Troubleshooting Other SCF Commands Each type of OSI process has a different device type/subtype combination, as shown in Table 6-1. Table 6-1.
FTAM Troubleshooting Types of Problems These SCF commands are most useful for troubleshooting when an association has not yet been established and when you are troubleshooting capacity or performance problems. Possible problems that can be indicated by the information returned by SCF commands are incorrect common name or address information, no activity on the association, or product version incompatibilities.
FTAM Troubleshooting Configuration Errors Checking Your Command Files Carefully check your OSI/AS and APLMGR configuration command files before using them. Use the OSI/AS CHECK ENTRY command to check the internal consistency of your OSI/AS configuration. Then check it against your APLMGR configuration command file. See Figure 3-8 on page 3-60 and Figure 3-9 on page 3-64 for a visual summary of the configuration commands that must be checked against each other.
FTAM Troubleshooting Configuration Errors Troubleshooting Configuration Problems That Occur When You Run Your Application When you’ve successfully installed your configuration, you’re ready to run your application. If configuration problems still exist, often your application will be unable to make an association.
FTAM Troubleshooting Configuration Errors The following sample display is returned by the STATUS SU command with the DETAIL option: OSIFTAM Detailed Status SU \NET.$FTI1.#Z000001 State Opens Error Error ............ ............ ............ Subcode..... STARTED 1 0 0 CEPI ............. -11 TAPS SU .......... \NET.$L51.#Z00000A FTAM Functional Units Selected Read Write FileAccess Group Calling Address: PSEL..... 17 SSEL..... 0112 TSEL..... 03 NSAP..... 03 ComName..
FTAM Troubleshooting Configuration Errors The STATUS SU display shows the calling address being used by the initiator (the address specified by the application, if any, or the configured default address), the called address, and the responding address. A missing responding address indicates that the remote entity has not responded to the association request; this might indicate address configuration problems.
FTAM Troubleshooting Configuration Errors Applications Using the Tandem Initiator When troubleshooting applications that use the Tandem initiator (Tandem FTAM applications), the most useful tools are Inspect, the SCF TRACE command, and the PTrace utility. For initial testing of your application, it’s a good idea to set up a loopback configuration on a Tandem system, using a Tandem responder.
FTAM Troubleshooting Configuration Errors To obtain still more detailed information about what is happening on the association, you can trace the initiator and underlying TAPS, TSP, and NSP processes, then use the PTrace utility to examine the trace records. Each message sent from or to one of these processes is represented by a trace record.
FTAM Troubleshooting Interoperability Problems If your remote application accesses FTAM-2 files as SQL tables, your filter should also pass FTAM event message #10. You must recompile the FTAMROBJ file using NonStop SQL before starting your responder processes; otherwise, the responder will generate this event message, reporting an SQL error of -8025, on the first attempt to access an FTAM-2 file as an SQL table. The responder also reports this event if any other NonStop SQL error occurs.
FTAM Troubleshooting System Problems System Problems The operation of Tandem FTAM and your FTAM application can be affected by system problems unrelated to the FTAM software or your application or configuration: for example, problems with the Tandem NonStop Kernel operating system, processor failures, communications-line problems, or problems in the disk device used for the virtual filestore (VFS). These problems can be reported to you in a number of ways.
FTAM Troubleshooting Getting Help Getting Help If you encounter a problem that you are unable to resolve, you will need to follow your installation’s procedures for seeking additional help. These procedures might involve contacting the Global Customer Support Center (GNSC) or your local service provider. Provide a description of the conditions under which the problem occurred, along with SCF status and statistics data and a copy of the trace files.
FTAM Troubleshooting Getting Help OSI/FTAM Configuration and Management Manual—421944-001 6- 22
A Example FTAM Configuration Command Files This appendix presents a detailed reference model for the example FTAM configuration shown in Example FTAM Configuration on page 3-38.
Example FTAM Configuration Command Files A Detailed Look at the Example FTAM Configuration A Detailed Look at the Example FTAM Configuration Some entities in Table A-1 on page A-1—$AMGR, $FTI1, $FTI2, $FTR1, $FTR2, and VFS1—have attributes associated with them that require further definition for the example configuration. The values assigned to these attributes are summarized here for reference purposes.
Example FTAM Configuration Command Files APLMGR Subsystem Table A-2. Attribute Values for Example APLMGR (page 2 of 2) Attribute Description Value Set for This Example FTAMRFILE The fully qualified Guardian name of the file containing the code for the FTAM responder processes. You can configure this attribute using the SCF ALTER SUBSYS command. $SYSTEM.SYSnn.FTAMROBJ MIB The fully qualified Guardian name of the primary MIB file where the APLMGR process stores configuration information.
Example FTAM Configuration Command Files Initiator and Responder Processes Initiator and Responder Processes The example FTAM configuration includes four processes: two FTAM initiator processes and two FTAM responder processes. Table A-3 presents attribute values for the two initiator processes.
Example FTAM Configuration Command Files VFS Profile Table A-4 presents attribute values for the two responder processes. Again, the values in this table represent the configured installation using the examples in Section 3, Planning, Installing, and Configuring Tandem FTAM, Section 4, Managing the FTAM Configuration, and Section 5, Monitoring FTAM Performance. The process identified in the first column is fully qualified as $AMGR.#FTAMR.FTR1 or $AMGR.#FTAMR.FTR2.
Example FTAM Configuration Command Files Creating the APLMGR MIB File Creating the APLMGR MIB File This subsection presents two alternatives for creating the MIB file for the APLMGR process. The first alternative is a FUP command file that creates a MIB file where one did not previously exist. The second is a TACL command file that purges the data in a MIB that already exists.
Example FTAM Configuration Command Files Command File to Purge Data Command File to Purge Data An alternative to creating the MIB is to purge the contents of MIB files that already exist. The TACL command file EXCLRMIB purges information in MIB files named ZOSADB and ZOSADB0. Enter the following command at the TACL prompt to execute this command file: OBEY EXCLRMIB Note. Before executing this file, you must stop the APLMGR process.
Example FTAM Configuration Command Files Configuring OSI/AS to Support Tandem FTAM Configuring OSI/AS to Support Tandem FTAM This subsection first provides a listing of the FUP command file (provided with the OSI/AS product) that you should use to create the MIB for the OSI manager process (for the example configuration and for any other configuration). Following this FUP command file is an SCF command file that configures OSI addresses for Tandem FTAM in the OSI manager MIB.
Example FTAM Configuration Command Files Command File to Purge Data Command File to Purge Data An alternative to creating the OSI manager MIB is to purge the contents of MIB files that already exist. The TACL command file EXCLOMIB purges information in OSI manager MIB files named ZOSIDB and ZOSIDB0. Enter the following command at the TACL prompt to execute this command file: OBEY EXCLOMIB Note. Before executing this file, you must stop the OSI manager process.
Example FTAM Configuration Command Files Command File to Configure Tandem FTAM Addresses in OSI/AS Command File to Configure Tandem FTAM Addresses in OSI/AS The SCF command file EXOSIUP creates and starts the OSI manager process, defines profile and entry information, configures and starts all underlying layer processes, and defines the Tandem FTAM common names and OSI addresses. This command file is written under the assumption that you are communicating over an X.
Example FTAM Configuration Command Files Command File to Configure Tandem FTAM Addresses in OSI/AS To execute this command file, run SCF and enter the following command at the SCF prompt: OBEY EXOSIUP The EXOSIUP file consists of the following: ============================================================= == File: EXOSIUP == == Example SCF command file to configure and start up OSI/AS == and underlying processes in support of a Tandem FTAM == installation. == == This SCF command file is specific to an X.
Example FTAM Configuration Command Files Command File to Configure Tandem FTAM Addresses in OSI/AS == Define NSP, TSP, and TAPS processes. ============================================================= ADD PROCESS $OSM1.#NSP.L31, NAME $SX250 ADD PROCESS $OSM1.#TSP.L41, NAME $L41, CPU 0, BACKUPCPU 1 ADD PROCESS $OSM1.#TAPS.L51, NAME $L51, CPU 0, BACKUPCPU 1 ============================================================= == Define profile and entry information.
Example FTAM Configuration Command Files Command File to Configure Tandem FTAM Addresses in OSI/AS == Local common names ADD ENTRY $OSM1.#APPL.FTMI1A, PSEL 01, SSEL 0110 & , TSEL 07, NSAP 03 ADD ENTRY $OSM1.#APPL.FTMI2A, PSEL 17, SSEL 0112 & , TSEL 03, NSAP 03 ADD ENTRY $OSM1.#APPL.APPL1A, PSEL 03, SSEL 0114 & , TSEL 05, NSAP 03 == == == == Remote Common Names These address components must be the ones expected by the remote entity. Some remote entities might not expect a PSEL or SSEL. ADD ENTRY $OSM1.
Example FTAM Configuration Command Files Starting an FTAM Installation Starting an FTAM Installation This subsection presents an SCF command file to create and start the APLMGR process, configure the FTAM processes, and configure the VFS profile. The SCF command file EXFTMUP creates and starts the APLMGR process, defines the VFS profile, and adds and starts the four FTAM processes in the example FTAM configuration.
Example FTAM Configuration Command Files Starting an FTAM Installation ADD PROFILE $AMGR.#VFS.VFS1, COMNAME "APPL1A" & , DEFUSER "USER.BOB,passwd" ============================================================= == Add and start the initiator and responder processes. == == Responders use the same VFS profile, and are therefore == tied to the same OSI address. == Default values for MAXASSOC (8) and MAXATTACH (8) are used == for FTR2.
Example FTAM Configuration Command Files Stopping an FTAM Installation Stopping an FTAM Installation This subsection explains how to shut down the FTAM environment. It provides a sample SCF command file, EXFTMDWN, which stops the APLMGR process and the FTAM processes in the example FTAM configuration. These commands require that no subdevices exist for the named initiator and responder processes.
Example FTAM Configuration Command Files Collecting Diagnostic Information Collecting Diagnostic Information If you have attempted the troubleshooting procedures outlined in Section 6, FTAM Troubleshooting, and a problem persists, you need to collect diagnostic information to provide to a support representative.
Example FTAM Configuration Command Files Command File for Resetting Statistics Counters ============================================================= == File: EXTBL1 == == THIS SCF COMMAND FILE RESETS ALL SERVICE, PROCESS, == AND SUBSYSTEM STATISTICS COUNTERS. == == To run this SCF command file, you must be a member of == the Guardian super user group (group ID 255).
Example FTAM Configuration Command Files Command File for Obtaining Diagnostic Information Command File for Obtaining Diagnostic Information After you have reset the statistics counters, you can collect diagnostic information to document the problem. The following SCF command file collects and displays service and process statistics and other information for the sample configuration described in this appendix.
Example FTAM Configuration Command Files Command File for Obtaining Diagnostic Information stats process $amgr stats process $fti1 stats process $fti2 stats process $ftr1 stats process $ftr2 ============================================================= == USE INFO TO LOOK AT THE PROCESSES.
Example FTAM Configuration Command Files Command File for Obtaining Diagnostic Information info entry $osm1.#tsel.07, detail info entry $osm1.#tsel.03, detail info entry $osm1.#tsel.05, detail info entry $osm1.#nsap.03, detail info entry $osm1.#snpa.05, detail ============================================================= == REMOTE ADDRESSES ============================================================= info entry $osm1.#appl.ftmr1b, detail info entry $osm1.#nsap.04, detail info entry $osm1.#snpa.
Example FTAM Configuration Command Files Command File for Obtaining Diagnostic Information OSI/FTAM Configuration and Management Manual—421944-001 A -22
B FTAM EMS Filters This appendix presents example Event Management Service (EMS) filters that sort the following sets of event messages related to Tandem FTAM: • • All event messages generated by Tandem FTAM processes, including those from both APLMGR and FTAM subsystems Event messages generated by Tandem FTAM processes, including those from both APLMGR and FTAM subsystems, that report critical events only The source code given here must be run through the filter language compiler (EMF) to produce a fi
FTAM EMS Filters Filtering All FTAM and APLMGR Event Messages Filtering All FTAM and APLMGR Event Messages The example filter EXFLT1 selects all event messages that have the APLMGR or FTAM subsystem ID. This filter allows you to separate events reported by Tandem FTAM processes from other events that occur on the system.
FTAM EMS Filters Filtering Critical FTAM and APLMGR Event Messages Filtering Critical FTAM and APLMGR Event Messages The example filter EXFLT2 selects only those event messages that fulfill both of the following criteria: • • The subsystem ID is that of either the APLMGR or the FTAM subsystem. The EMPHASIS token is set to TRUE. This filter allows you to separate critical events reported by Tandem FTAM processes from all other events occurring in the system.
FTAM EMS Filters TACL Macro to Compile Filter Examples TACL Macro to Compile Filter Examples Before installing a filter, you must compile it using the EMS filter compiler. Since filters are based on TACL, compilation requires that you first load in the TACL versions of the definition files containing the definitions you use in your filter. You can use the following TACL macro, EXEMF, to load the definitions and compile the two example filters presented in this appendix.
C FTAM Software Files This appendix identifies the files and subvolumes where the Tandem Install program places the Tandem FTAM software on your system. The person running Install at your site chooses the volumes on which these subvolumes are placed. Note. When running the Tandem Install program to place the required software on your system, be sure to install the OSI/AS subsystem before installing Tandem FTAM; otherwise, FTAM will not operate properly.
FTAM Software Files Table C-2 lists the filename, subvolume name, file type, and content description of each FTAM subsystem file to install on your system. These files are part of Tandem product number T6982. Table C-2.
FTAM Software Files Table C-2.
FTAM Software Files Table C-3 lists the filename, subvolume name, file type, and content description of each Tandem FTAM SCF product module file to install on your system. These files are part of Tandem product numbers T6983 and T6984. Table C-3. SCF Product Module Installation Subvolumes and Filenames Filename Subvolume File Type Description ZOSASCF $SYSTEM.SYSTEM OBJECT SCF product module object file for the APLMGR subsystem ZOSATEXT $SYSTEM.
Glossary The following glossary defines terms used in this manual and in the other Tandem OSI product manuals. Not all terms listed here are used in this particular manual. abstract syntax. A representation of the way in which components of information are to be specified in a communication. It defines a set of primitive elements whose range of values is fully defined—for example, integers, characters, and Boolean values—and ways of combining these elements. action event.
Glossary Configuration Utility Program (COUP) Configuration Utility Program (COUP). An interactive program that allows system managers to make online changes to the configuration of devices and controllers. COUP is part of the Dynamic System Configuration (DSC) facility, which is not used to configure Tandem OSI subsystem objects, but which can be used to configure the underlying ViewPoint and Tandem LAN Access Method (TLAM) objects. connection-establishment phase.
Glossary DSM DSM. See Distributed Systems Management (DSM). Dynamic System Configuration (DSC). A facility that allows system managers to make online changes to the configuration of devices and controllers. Its interactive utility program is called the Configuration Utility Program (COUP). DSC is not used to configure Tandem OSI subsystem objects, but it can be used to configure the underlying X.25 Access Method (X25AM) and Tandem LAN Access Method (TLAM) objects. EMS. See Event Management Service (EMS).
Glossary initiator initiator. The entity that initiates a connect request. Initiators and responders are defined with respect to a single connection. Some entities can be both an initiator and a responder simultaneously, but not over the same connection.
Glossary network service access point (NSAP) network service access point (NSAP). The logical point at which network service provider (NSP) process services are provided by the Network Layer entity to the Transport Layer entity. See also network service access point (NSAP) address. network service access point (NSAP) address. The global, network-unique address of an end system’s network service access point (NSAP), through which network service provider (NSP) process services are provided.
Glossary Open Systems Interconnection (OSI) subsystem Open Systems Interconnection (OSI) subsystem. One Open Systems Interconnection (OSI) manager process controls one or more TAPS and TSP processes. The OSI manager processes communicates with NSP processes but do not control them. The OSI manager, TAPS, TSP, and NSP processes can be on the same or different nodes within the same Expand network. See also Open Systems Interconnection (OSI) and Open Systems Interconnection (OSI) manager process. OSI/AS.
Glossary SCF SCF. See Subsystem Control Facility (SCF). sensitive command. A Distributed Systems Management (DSM) command that can be issued only by a restricted set of users. For Tandem communications subsystems, the sensitive commands are those that can change the state or configuration of objects, start or stop tracing, or change the values of statistics counters. service. A set of primitives (operations) that a layer provides to the layer above it.
Glossary subdevice subdevice. A logical entity providing access to a physical entity (a communications line). There may be one or many subdevices associated with a given line or process. Exactly what constitutes a subdevice differs depending on the subsystem. A ViewPoint subdevice corresponds to an X.25 network virtual circuit.
Glossary SYSGEN SYSGEN. The Tandem system generation program used to configure objects such as devices, controllers, and input/output processes (IOPs) in a newly installed system or to update the system when new software is released. Objects to be configured are defined to SYSGEN in a special configuration file, which can then be coldloaded into the system. The Tandem Open Systems Interconnection (OSI) products are not configured with SYSGEN, but the underlying X.
Glossary Transmission Control Protocol/Internet Protocol (TCP/IP) Transmission Control Protocol/Internet Protocol (TCP/IP). A set of layered communications protocols for connecting workstations and larger systems. See also Tandem NonStop TCP/IP. Transport entity. A process in the Transport Layer that sends or receives a given transport protocol data unit (PDU). Transport Layer. Layer 4 in the Open Systems Interconnection (OSI) Reference Model.
Index A ABORT commands discarding subdevices with 4-18 using NAMES SU before 4-18 Access-control attribute 3-22 ADD commands 3-27 ADD PROCESS 3-28, 3-31 ADD PROFILE 3-28 Adding initiator and responder processes 5-12, 5-13 ALLOWSU attribute 3-58 ALTER commands ALTER PROFILE example 3-53 ALTER SUBSYS 3-29, 3-47 APLMGR changing default configuration 3-51 creating and starting with TACL RUN command 3-46 displaying configuration 3-49 example FTAM configuration information A-2 installation subvolumes and filename
Index B B D BACKUPCPU attribute, using 3-32 DBFUP file A-8 Debugging See Troubleshooting DEFUSER attribute in VFS 3-19 using to specify default user ID and password 3-19 when to omit 3-37 DELAY, in START PROCESS commands 3-57 Distributed Systems Management (DSM) in Tandem FTAM architecture 1-9, 2-1 interfaces for FTAM 1-4 C CHECK ENTRY command, in OSI/AS 6-13 Code files, recompiling for FTAM processes 3-42 Collectors, alternate, starting and adding 3-48 Command files creating the APLMGR MIB 3-45 examp
Index F F Fault tolerance, configuring FTAM for 1-15 Files access 3-26 command collecting diagnostic information A-17 creating OSIMGR MIB A-8 creating APLMGR MIB A-6 managing APLMGR configuration 4-1 purging data A-7, A-9 configuration command, creating new file 4-2 configuration command, invoking new file 4-3 configuring for security 3-37 EMSACOLL object 3-48 EXECUTE access 3-25 MIB, using multiple 4-4 object-code, recompiling for FTAM processes 3-42 PURGE access 3-25 remotely modified, security for 3-24
Index H H L Hardware environment 1-13 monitoring system performance with 5-1 HELP commands, in SCF 2-7 HIGHPIN OFF, setting 1-6 LISTDEV commands OSI process device types and subtypes, table of 6-11 using for troubleshooting 6-10 LISTOPENS commands, using for troubleshooting 6-10 Load distribution 3-32 Local area subnetworks, communications controllers 1-14 Local directory information base (LDIB) 1-8 Loopback configuration, in initial testing 6-17 I INFO commands INFO PROCESS 3-29, 4-11 INFO SUBSYS det
Index N N NAME attribute using 3-29 in TACL RUN command 3-47 Names, configuring process 3-29 NAMES commands NAMES null, using to display objects 4-6 NAMES PROCESS example 4-8 NAMES PROFILE example 4-10 NAMES SU example 4-9 using for troubleshooting 6-10 NIST FTAM agreements xv NonStop process pairs, creating 3-32, 3-47 NonStop TCP/IP 1-2 communications controllers 1-14 in Tandem FTAM architecture 1-9 installing 3-41 NSAP in OSI addresses 3-6 using 3-27 NSP processes, configuring 1-8, 3-61, 3-65 Null objec
Index P P R Performance, monitoring statistics 5-7 Planning the FTAM configuration 3-1 Port Access Method (PAM) 1-2 in Tandem FTAM architecture 1-9 installing 3-41 PRIORITY attribute, using 3-34 Process names, configuring 3-29 PROCESS objects 2-14 adding and configuring 3-56 deleting 3-58 maximum number of 3-34 Processes aborting 4-20 deciding when to stop and when to abort 4-20 listing configured and running 4-6 load distribution 3-32 stopping in an orderly fashion 4-19 suspending and activating 4-21 P
Index S S Safeguard, support of access-control attribute 3-23 Save files, creating manually 6-6 SCF commands INFO, using for troubleshooting 6-10 LISTDEV OSI process device types and subtypes, table of 6-11 using for troubleshooting 6-10 LISTOPENS, using for troubleshooting 6-10 NAMES, using for troubleshooting 6-10 STATS STATS PROCESS, detailed example 5-9 using for troubleshooting 6-10 STATUS STATUS PROCESS, monitoring performance with 5-3 STATUS SU, detailed example 5-4, 6-15 using for troubleshooting
Index T Subsystem Control Facility (SCF) commands and object types, table of 2-3 help utility, table of 2-7 sensitive and nonsensitive 2-6 error messages 2-8 managing FTAM with 2-3 objects attributes 2-11 introduction 2-9 null 2-11 object-name format 2-10 PROCESS 2-14 PROFILE, displaying configuration information 4-13 states 2-11 SU 2-20 SUBSYS 2-12 product module installation subvolumes and filenames C-4 using to check association status 4-22 using to monitor system performance 5-2/5-16 Subsystem interde
Index U Troubleshooting 6-1/6-21 application protocol errors 6-16 command file for resetting statistics counters A-17 configuration problems, causes 6-14 EMS event log in 6-3 FTAM trace records in 6-9 Inspect interactive debugger in 6-4 of FTAM responder 6-18 SCF TRACE commands in 6-7 using PTrace utility for 6-7 TSEL in OSI addresses 3-6 using 3-27 TSP processes, configuring 3-61, 3-65 TSP processes, in OSI/TS 1-8 X X.25 Access Method (X25AM) 1-2 in Tandem FTAM architecture 1-9 installing 3-41 X.
Index Z OSI/FTAM Configuration and Management Manual—421944-001 Index -10
