Manuals / Compaq / Computer Equipment / Network Router

Compaq OSI/FTAM D43 manual Responder Manager, Notes on Configuration, OSI Address of Responder

Models: OSI/FTAM D43 OSI/APLMGR D43

1 130

Download 130 pages 52.02 Kb

Page 65

6 Responder Manager

This section discusses considerations that are related to the configuration and management of the responder process and its VFS on the Compaq system, but that you might need to know when writing or using FTAM applications on the remote system. It covers the following topics:

•

•

•

Notes on configuration Fault tolerance Event messages

Full details on FTAM configuration, management, and troubleshooting on the Compaq system are provided in the OSI/FTAM Configuration and Management Manual.

Notes on Configuration

Compaq FTAM (responder and APLMGR processes), the OSI/AS subsystem, the OSI/TS subsystem, and TLAM (or PAM for G06 and above releases) or X25AM or TCP/IP must be configured and running on the Compaq system before your application can communicate with the Compaq responder.

Because of the flexibility, and resultant complexity, of the configuration of underlying Compaq OSI layers, configuration errors are a common cause of problems in Compaq FTAM applications. The Compaq problem solver should pay special attention to checking the configuration of Compaq FTAM and the configuration of the underlying OSI layers (via Compaq OSI/AS).

The following aspects of configuration are important to writers and users of remote FTAM applications:

•

•

•

•

•

OSI address of responder

Initiator-identity and filestore-password parameters Protocol error counter

Ways to increase responder capacity Ways to increase responder performance

OSI Address of Responder

The assigned OSI address of each responder process is configured on the Compaq system. Remote applications must refer to this address when requesting the services of the responder. Several responders can be assigned to the same address.

OSI/FTAM Responder Manual—425199-001

6-1

Image 65

Compaq OSI/FTAM D43 manual Responder Manager, Notes on Configuration, OSI Address of Responder, OSI address of responder

Contents

Product Version AbstractSupported Releases Part NumberOrdering Information Document HistoryDocument Disclaimer Export Statement2. Conformance and Interoperatility OSI/FTAM Responder Manual1. Introduction to the Compaq FTAM Responder 5. Suggestions for Development of Remote Applications 3. Compaq FTAM Responder Operation4. Compaq FTAM Responder Support of ISO FTAM Functions 6. Responder Manager A. Compaq FTAM Responder Diagnostic MessagesGlossary IndexTables continued Manual Information What’s New in This ManualNew and Changed Information AbstractOSI/FTAM Responder Manual-425199-001 What’s New in This ManualNew and Changed Information About This Manual Supported Standards Related Manuals Operator Messages Manual Your Comments InvitedGeneral Syntax Notation Notation Conventionserror error = NEXTFILENAME file-nameerror = COMPRESSEDIT filenum error = FILENAMECOMPARE filename1lengthNotation for Messages Notation for Management Programming Interfaces Functional Overview Introduction to the Compaq FTAM ResponderFTAM Applications Compaq FTAM ServicesResponding Process Figure 1-1. An FTAM Service Using Four PrimitivesInitiating Process The Responder and Underlying Subsystems Architectural OverviewManagement Interfaces Compaq application, presentation, and session service provider TAPS processes perform the services of the Association Control Service Element ACSE in the Application Layer, plus the services of the Presentation Layer and the Session Layer. TAPS processes are provided by the OSI/AS subsystem CDT 204.CDD Figure 1-2. Compaq FTAM Responder Architectural OverviewThe Responder and the File System OSI/FTAM Responder Manual-425199-001 Introduction to the Compaq FTAM ResponderThe Responder and the File System Interoperability 2 Conformance and InteroperatilityConformance Service Classes Supported Basic Characteristics of FTAM ImplementationsUnderlying Services Roles of Initiator and ResponderFTAM Parameters AttributesLimitations on Value of Future-Filesize Attribute Document Types and Related ParametersMaximum-String-Length Parameter Mapping of Contents-Type ParametersString-Significance Parameter Universal-Class ParameterHandling of Escape Sequences Limits on Small String-Length Values With Large PDUsUse of Format Effectors Character SetsPresentation Encoding of FTAM PDUs and Data Writing of FTAM-2 FilesWhen receiving PDUs, Compaq FTAM supports all three options listed above. When sending PDUs, Compaq FTAM follows these rules OSI/FTAM Responder Manual-425199-001 Conformance and InteroperatilityPresentation Encoding of FTAM PDUs and Data Responder Structure Compaq FTAM Responder OperationFigure 3-1. Compaq FTAM Responder Process Responder Data Flow2. The FTAM initiator follows the OSI protocol established on the initiating system to send the outgoing FTAM protocol data unit PDU over the network to the Compaq responding system, where it is received as an indication OSI/FTAM Responder Manual-425199-001 Compaq FTAM Responder OperationResponder Data Flow Table 4-1. Service Classes Supported by the Compaq FTAM Responder Service ClassesCompaq FTAM Responder Support of ISO FTAM Functions Supported FunctionsAttribute Support Attribute GroupsTable 4-2. Functional Units Supported by the Compaq FTAM Responder Table 4-3. Attribute Groups Supported by the Compaq FTAM ResponderAttribute Table 4-4. Attributes Supported by the Compaq FTAM ResponderFile Attribute Level of SupportDocument Types Create Mappings Mapping Between FTAM Contents Types and Compaq File Structuresfall within the range supported by the Compaq responder for that document type and string-significance value, as follows Compaq File Structure Select-Open MappingsContents Type Page Default Parameter Values Contents TypeCompaq File Structure DescriptionWrite Operations Maximum-String-Length Checking of Data ValuesRead Operations Limits on Small String-Length Values With Large PDUsKernel Group File Attributes File-Attribute MappingsFilename Attribute Contents-Type AttributePermitted-Actions Attribute Table 4-8. Actions Permitted for FTAM Document TypeNBS-9 Documents Table 4-10. Bit String for NBS-9 File Attributes $volume.subvol.DIRLISStorage Group File Attributes Table 4-11 summarizes the Compaq support for the storage attributes Security Group File Attributes Access-Control Attributewhich access to a file is allowed. ISO 8571-2 provides a complete description of the ISO FTAM access-control attribute Guardian security is modified to… Table 4-13. Mapping From FTAM Action List to Guardian SecurityIf action list is set to… For delete-values Legal-Qualifications Attribute Supported and Unsupported Optional ParametersPrivate Group File Attributes Table 4-14. Mapping From Guardian Security to FTAM Action ListFile-Access and Security Considerations Guardian File Access Table 4-17. Guardian Access Required to Perform FTAM ActionsExclusion Mode FTAM VFS Actionactions are open for EXCLUSIVE access only one user at a time can open a file for writing. Where a combination of VFS actions are performed on a file, that file’s exclusion mode is EXCLUSIVE if any one of the actions qualify the file’s exclusion mode as EXCLUSIVE. If a file access is attempted on a file already opened for EXCLUSIVE access, the responder returns a diagnostic message to the remote application in the F-OPEN confirm Suggestions for Development of Remote Applications Error HandlingDesign and Programming InteroperabilityTroubleshooting The Compaq problem solver can use SCF commands to display configuration, status, and statistics information about the responder and APLMGR processes on the Compaq system. This information can sometimes provide clues to the cause of a problem, especially if an association is not yet established or if there are problems with system capacity or performance. In addition the STATUS SU command, which provides information about an FTAM association once it is established, can be especially useful in troubleshooting Suggestions for Development of Remote TroubleshootingApplications OSI/FTAM Responder Manual-425199-0016 Responder Manager Notes on ConfigurationOSI Address of Responder OSI address of responderInitiator-Identity and Filestore-Password Parameters Fault ToleranceProtocol-Error Counter Increasing Responder CapacityEvent Messages Failure to establish an association with a Compaq responder due to an invalid initiator ID or password Table A-1. Diagnostic Message Types Compaq FTAM Responder Diagnostic MessagesTable A-3. General FTAM Diagnostic Messages General FTAM Diagnostic MessagesTable A-2. Sources and Observers of Errors Recovery. No action is necessary Protocol and Supporting Service-Related Diagnostic Messages 1002 10011007 Unspecific FTAM protocol error1011 10091015 10161017 Association-Related Diagnostic MessagesTable A-5. Association-Related Diagnostic Messages 2003 20022013 20142016 20152018 2020A-10 Selection-Related Diagnostic Messages2021 3002 Table A-6. Selection-Related Diagnostic Messages3000 3005 30043006 A-123012 30073013 30163020 30183021 30223028 30273029 3030Table A-7. File-Management-Related Diagnostic Message File-Management-Related Diagnostic Messages4001 40024003 Access-Related Diagnostic Messages4005 40065000 Table A-8. Access-Related Diagnostic Messages5003 50015004 Bad FADU - size error5008 50055011 50125022 50155023 50245026 Table A-9. Access Contexts by Document Typ5027 A-225030 50285032 A-23A-24 5036Contents type inconsistent Table A-11. Recovery-Related Diagnostic Messages Recovery-Related Diagnostic Messages5040 6010Recovery-Related Diagnostic Messages Compaq FTAM Responder Diagnostic MessagesOSI/FTAM Responder Manual-425199-001 A-26APDU application protocol data unit. See PDU GlossaryAbstract Syntax Notation-1. See ASN.1 Application Manager. See APLMGR application service element. See ASEAssociation Control Service Element. See ACSE Glossary-4 Compaq OSI/AS. See OSI/AS Compaq OSI/FTAM. See Compaq FTAMCompaq OSI/TS. See OSI/TS Glossary-5 connection endpoint identifier. See CEPIData Definition Language. See DDL Glossary-6 Distributed Systems Management. See DSMend-of-file marker. See EOF Event Management Service. See EMS external process name. See Guardian process name file-access data unit. See FADUfile-attribute group. See attribute group Glossary-8Glossary-9 File Transfer, Access and Management. See FTAMFile Utility Program. See FUP Glossary-10 FTAM API. See APIThe file-access structure is an ordered tree Glossary-12 intermediate state. See state transitionInternational Standard. See IS International Organization for Standardization. See ISOISO646String. See VisibleString Management Information Base. See MIBGlossary-14 module file management procedures. See MFM proceduresNational Institute of Science and Technology. See NIST NonStop process pair. See process pair Open Systems Interconnection. See OSI object state. See state object state transition. See state transitionSPDU session PDU information exchanged between Session Layer entities PPDU presentation PDU. See PDU Glossary-19 protocol data unit. See PDUEstablishing the file-open regime root node. The first-level node in a hierarchical file. See root FADU Glossary-22 SPDU session protocol data unit. See PDU session selector. See SSEL session service access point. See SSAPsession address. See SSAP structured query language. See SQL Subsystem Control Facility. See SCF Subsystem Control Point. See SCP Tandem Advanced Command Language. See TACLSubsystem Programmatic Interface. See SPI summary-state transition. See state transitionTransaction Application Language. See TAL TPDU transport protocol data unit. See PDUtransition state. See state transition. transport address. See TSAP transport selector. See TSELGlossary-27 virtual filestore. See VFSGlossary-28 Index Page Page Index-4 Page Page Page Index-8