Manuals / Compaq / Computer Equipment / Network Router

Compaq OSI/APLMGR D43, OSI/FTAM D43 manual 5000, Table A-8. Access-Related Diagnostic Messages

Models: OSI/FTAM D43 OSI/APLMGR D43

1 130

Download 130 pages 52.02 Kb

Page 86

Table A-8. Access-Related Diagnostic Messages

Compaq FTAM Responder Diagnostic Messages

Access-Related Diagnostic Messages

Table A-8. Access-Related Diagnostic Messages

Identifier	Type	Observer	Source	Reason

5000	2	5	1	Bad FADU (unspecific)
5001	2	5	1	Bad FADU - size error
5003	2	5	1	Bad FADU - poorly specified
5004	2	5	1	Bad FADU - bad location
5005	0	5	5	FADU does not exist
5008	2	5	5	FADU not available for writing
5011	2	5	5	FADU cannot be inserted
5012	2	5	5	FADU cannot be replaced
5015	2	5	5	Operation not available
5022	2	5	5	Processing mode unsupported
5023	2	5	1	Processing mode inconsistent
5024	2	5	5	Access context not available
5026	2	5	5	Bad write (unspecific)
5027	2	5	5	Bad read (unspecific)
5028	2	5	5	Local failure (unspecific)
5030	2	5	5	Local failure - data corrupted
5032	2	5	5	Future filesize exceeded
5036	2	5	1	Contents type inconsistent
5040	2	5	5	FADU locking not available on
				file

5000

Bad FADU (unspecific)

Cause. The FADU-ID parameter on a read or write request is invalid.

Effect. The responder cancels the service, and the association is left in a data-transfer idle state.

Recovery. The application or FTAM user should issue a cancel response, and then reissue the read or write request with a valid FADU ID.

OSI/FTAM Responder Manual—425199-001

A-18

Image 86

Compaq OSI/APLMGR D43, OSI/FTAM D43 manual 5000, Table A-8. Access-Related Diagnostic Messages

Contents

Supported Releases AbstractProduct Version Part NumberDocument Disclaimer Document HistoryOrdering Information 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 Glossary A. Compaq FTAM Responder Diagnostic Messages6. Responder Manager IndexTables continued New and Changed Information What’s New in This ManualManual Information AbstractOSI/FTAM Responder Manual-425199-001 What’s New in This ManualNew and Changed Information About This Manual Supported Standards Related Manuals Your Comments Invited Operator Messages ManualNotation Conventions General Syntax Notationerror = COMPRESSEDIT filenum error = NEXTFILENAME file-nameerror error = FILENAMECOMPARE filename1lengthNotation for Messages Notation for Management Programming Interfaces Introduction to the Compaq FTAM Responder Functional OverviewCompaq FTAM Services FTAM ApplicationsResponding 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 Figure 1-2. Compaq FTAM Responder Architectural Overview CDT 204.CDDThe 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 Underlying Services Basic Characteristics of FTAM ImplementationsService Classes Supported Roles of Initiator and ResponderLimitations on Value of Future-Filesize Attribute AttributesFTAM Parameters Document Types and Related ParametersString-Significance Parameter Mapping of Contents-Type ParametersMaximum-String-Length Parameter Universal-Class ParameterUse of Format Effectors Limits on Small String-Length Values With Large PDUsHandling of Escape Sequences Character SetsWriting of FTAM-2 Files Presentation Encoding of FTAM PDUs and DataWhen 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 Compaq FTAM Responder Operation Responder StructureResponder Data Flow Figure 3-1. Compaq FTAM Responder Process2. 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 Compaq FTAM Responder Support of ISO FTAM Functions Service ClassesTable 4-1. Service Classes Supported by the Compaq FTAM Responder Supported FunctionsTable 4-2. Functional Units Supported by the Compaq FTAM Responder Attribute GroupsAttribute Support Table 4-3. Attribute Groups Supported by the Compaq FTAM ResponderFile Attribute Table 4-4. Attributes Supported by the Compaq FTAM ResponderAttribute Level of SupportDocument Types Mapping Between FTAM Contents Types and Compaq File Structures Create Mappingsfall 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 Compaq File Structure Contents TypeDefault Parameter Values DescriptionRead Operations Maximum-String-Length Checking of Data ValuesWrite Operations Limits on Small String-Length Values With Large PDUsFile-Attribute Mappings Kernel Group File AttributesPermitted-Actions Attribute Contents-Type AttributeFilename Attribute Table 4-8. Actions Permitted for FTAM Document TypeNBS-9 Documents $volume.subvol.DIRLIS Table 4-10. Bit String for NBS-9 File AttributesStorage Group File Attributes Table 4-11 summarizes the Compaq support for the storage attributes Access-Control Attribute Security Group File Attributeswhich 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 Private Group File Attributes Supported and Unsupported Optional ParametersLegal-Qualifications Attribute Table 4-14. Mapping From Guardian Security to FTAM Action ListFile-Access and Security Considerations Exclusion Mode Table 4-17. Guardian Access Required to Perform FTAM ActionsGuardian File Access 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 Design and Programming Error HandlingSuggestions for Development of Remote Applications 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 Applications TroubleshootingSuggestions for Development of Remote OSI/FTAM Responder Manual-425199-001OSI Address of Responder Notes on Configuration6 Responder Manager OSI address of responderProtocol-Error Counter Fault ToleranceInitiator-Identity and Filestore-Password Parameters Increasing Responder CapacityEvent Messages Failure to establish an association with a Compaq responder due to an invalid initiator ID or password Compaq FTAM Responder Diagnostic Messages Table A-1. Diagnostic Message TypesTable 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 1007 10011002 Unspecific FTAM protocol error1015 10091011 10161017 Association-Related Diagnostic MessagesTable A-5. Association-Related Diagnostic Messages 2013 20022003 20142018 20152016 2020A-10 Selection-Related Diagnostic Messages2021 3002 Table A-6. Selection-Related Diagnostic Messages3000 3006 30043005 A-123013 30073012 30163021 30183020 30223029 30273028 30304001 File-Management-Related Diagnostic MessagesTable A-7. File-Management-Related Diagnostic Message 40024005 Access-Related Diagnostic Messages4003 4006Table A-8. Access-Related Diagnostic Messages 50005004 50015003 Bad FADU - size error5011 50055008 50125023 50155022 50245027 Table A-9. Access Contexts by Document Typ5026 A-225032 50285030 A-23A-24 5036Contents type inconsistent 5040 Recovery-Related Diagnostic MessagesTable A-11. Recovery-Related Diagnostic Messages 6010OSI/FTAM Responder Manual-425199-001 Compaq FTAM Responder Diagnostic MessagesRecovery-Related Diagnostic Messages A-26APDU application protocol data unit. See PDU GlossaryAbstract Syntax Notation-1. See ASN.1 application service element. See ASE Application Manager. See APLMGRAssociation 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 file-attribute group. See attribute group file-access data unit. See FADUexternal process name. See Guardian process name Glossary-8Glossary-9 File Transfer, Access and Management. See FTAMFile Utility Program. See FUP FTAM API. See API Glossary-10The file-access structure is an ordered tree intermediate state. See state transition Glossary-12ISO646String. See VisibleString International Organization for Standardization. See ISOInternational Standard. See IS 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 object state. See state object state transition. See state transition Open Systems Interconnection. See OSISPDU session PDU information exchanged between Session Layer entities PPDU presentation PDU. See PDU protocol data unit. See PDU Glossary-19Establishing 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 Programmatic Interface. See SPI Tandem Advanced Command Language. See TACLSubsystem Control Facility. See SCF Subsystem Control Point. See SCP summary-state transition. See state transitiontransition state. See state transition. transport address. See TSAP TPDU transport protocol data unit. See PDUTransaction Application Language. See TAL transport selector. See TSELvirtual filestore. See VFS Glossary-27Glossary-28 Index Page Page Index-4 Page Page Page Index-8