OSI/FTAM Responder Manual Abstract This manual describes the operation of the Compaq Open Systems Interconnection/File Transfer, Access and Management (OSI/FTAM) responder and its virtual filestore (VFS). It is for programmers and users who are working with or writing remote FTAM applications that use the services of the Compaq responder. It is also useful to those with access to the Compaq system who are diagnosing and solving problems involving the Compaq FTAM responder.
Document History Part Number Product Version Published 030246 OSI/FTAM C30, OSI/APLMGR C30 August 1992 098329 OSI/FTAM D20, OSI/APLMGR D20 September 1993 425199-001 OSI/FTAM D43 OSI/APLMGR D43 February 2000 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.
OSI/FTAM Responder Manual Glossary Index Figures Tables What’s New in This Manual v Manual Information v New and Changed Information v About This Manual vii Supported Standards viii Related Manuals ix Your Comments Invited x Notation Conventions xi 1.
3. Compaq FTAM Responder Operation Contents 3. Compaq FTAM Responder Operation Responder Structure 3-1 Responder Data Flow 3-2 4.
6. Responder Manager Contents 6. Responder Manager Notes on Configuration 6-1 OSI Address of Responder 6-1 Initiator-Identity and Filestore-Password Parameters 6-2 Protocol-Error Counter 6-2 Increasing Responder Capacity 6-2 Increasing Responder Performance 6-2 Fault Tolerance 6-2 Event Messages 6-3 A.
Tables (continued) Contents Tables (continued) Table 4-7. Select-Open Mappings: Compaq File Structure to FTAM Contents Type 4-8 Table 4-8. Actions Permitted for FTAM Document Type Table 4-9. Simplification of Document Types Supported by the Compaq FTAM Responder 4-13 Table 4-10. Bit String for NBS-9 File Attributes 4-14 Table 4-11. FTAM Storage Attributes and Corresponding Compaq File Attributes 4-16 Table 4-12. Security Attributes Supported by the Compaq FTAM Responder Table 4-13.
What’s New in This Manual Manual Information Abstract This manual describes the operation of the Compaq Open Systems Interconnection/File Transfer, Access and Management (OSI/FTAM) responder and its virtual filestore (VFS). It is for programmers and users who are working with or writing remote FTAM applications that use the services of the Compaq responder. It is also useful to those with access to the Compaq system who are diagnosing and solving problems involving the Compaq FTAM responder.
New and Changed Information What’s New in This Manual OSI/FTAM Responder Manual—425199-001 vi
About This Manual The OSI/FTAM Responder Manual provides instructions and reference information needed to write application programs, or to use interactive applications, that use the services of the Compaq OSI/File Transfer, Access and Management (FTAM) responder process.
Supported Standards About This Manual Supported Standards This manual and the other Compaq FTAM manuals are written on the assumption that you are familiar with the ISO standards and the National Institute of Standards and Technology (NIST) FTAM Phase 2 agreements to which Compaq FTAM and the underlying Compaq OSI products conform.
Related Manuals About This Manual Related Manuals This manual is one in a set of Compaq FTAM manuals. • • • • • • OSI/FTAM Programming Guide. This manual explains important programming concepts pertaining to the Compaq FTAM application programmatic interface 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.
Your Comments Invited About This Manual If you are diagnosing and solving FTAM problems using tools on the Compaq system where your responder resides, you also need to refer to the following manuals: the OSI/FTAM Configuration and Management Manual and the SCF Reference Manual for FTAM and APLMGR.
Notation Conventions About This Manual Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
General Syntax Notation About This Manual An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
Notation for Messages About This Manual !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum , [ filename:maxlen ] ) ; !i !o:i Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text.
Notation for Management Programming Interfaces About This Manual 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: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line.
1 Introduction to the Compaq FTAM Responder This manual describes the Compaq Open Systems Interconnection/File Transfer, Access and Management (OSI/FTAM) responder and its virtual filestore (VFS). Compaq OSI/FTAM is the Compaq implementation of the FTAM standard ISO 8571, developed by the International Organization for Standardization (ISO).
Introduction to the Compaq FTAM Responder Compaq FTAM Services FTAM users communicate with the FTAM service provider by way of primitives, the smallest units of interaction between the FTAM user and the FTAM service provider. An operation like any of those mentioned above requires the exchange of multiple primitives, which the FTAM software encodes as protocol data units (PDUs). FTAM file handling is defined in terms of initiator and responder functions.
FTAM Applications Introduction to the Compaq FTAM Responder responder, you use the standard FTAM file-handling conventions to perform remote filehandling tasks, by means of the FTAM interface on your remote system. Each FTAM service, or file operation, requires that multiple FTAM protocol operations be performed, in sequence, to complete the service.
Introduction to the Compaq FTAM Responder Management Interfaces Management Interfaces For those people with access to the Compaq system who are responsible for configuring and managing FTAM responder processes and for solving FTAM problems, Compaq FTAM supports the Distributed Systems Management (DSM) management interfaces, which include the following: • • • Subsystem Control Facility (SCF) PTrace utility Operator message facility of the Event Management Service (EMS) The use of these management utilit
Introduction to the Compaq FTAM Responder • • • The Responder and Underlying Subsystems 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. Transport service provider (TSP) processes perform the services of the Transport Layer.
The Responder and Underlying Subsystems Introduction to the Compaq FTAM Responder Figure 1-2. Compaq FTAM Responder Architectural Overview User Application API Application Layer Tandem FTAM TAPS (OSI/AS) Presentation Layer Session Layer Transport Layer TSP (OSI/TS) Network Layer Data Link Layer NSP (X25AM) NSP (TLAM or PAM) Controllers Controllers RS-232C RS-449 X.21, V.
Introduction to the Compaq FTAM Responder The Responder and the File System The Responder and the File System Figure 1-2 also shows the file system used by the Compaq responder to access files. When a remote FTAM initiator requests access to files, the Compaq FTAM responder provides that service via its virtual filestore (VFS) component, which acts as an interface to the file system.
Introduction to the Compaq FTAM Responder The Responder and the File System OSI/FTAM Responder Manual—425199-001 1 -8
2 Conformance and Interoperatility This section presents information about the conformance to standards and the interoperability of the Compaq FTAM responder. Conformance is the satisfaction of the requirements of the applicable standards, consistent with the capabilities stated in the protocol implementation conformance statement (PICS) for the implementation. Interoperability is the ability of an implementation of a standard to work with other implementations of the same standard to deliver services.
Basic Characteristics of FTAM Implementations Conformance and Interoperatility When evaluating interoperability between Compaq FTAM and another FTAM implementation, consider the following aspects in which FTAM implementations can vary. Section 4 of this manual provides you with additional details about the Compaq FTAM implementation that you need to determine whether another implementation can interoperate with the Compaq FTAM product.
Limitations on Value of Future-Filesize Attribute Conformance and Interoperatility Attributes Aspects of attributes that can affect interoperability include the optional groups of attributes, the level of support for each individual attribute (see Table 4-4) and its optional components, and the range of values supported for each attribute. The Compaq FTAM implementation supports three attribute groups: kernel, storage, and security.
Data-Transfer Considerations Conformance and Interoperatility Maximum-String-Length Parameter Compaq FTAM supports unbounded strings. The limitations of the maximum-stringlength parameter are described in detail in Section 4. String-Significance Parameter The Compaq FTAM responder supports all three values (fixed, variable, and notsignificant) for the string-significance parameter in FTAM-1 documents. For the FTAM-3 document type, it supports the values not-significant, fixed, and variable.
Data-Transfer Considerations Conformance and Interoperatility Limits on Small String-Length Values With Large PDUs When the Compaq FTAM responder receives data from a remote initiator, it decodes the data and stores it, as a sequence of strings, in an internal buffer with a maximum size of 25 KB.
Presentation Encoding of FTAM PDUs and Data Conformance and Interoperatility For FTAM-3 files, keep in mind that the native character sets (ASCII, EBCDIC, and so on) might be incompatible on the sending and receiving systems. For example, Compaq systems use the 7-bit ASCII character set, whereas some other vendors’ systems use 8-bit EBCDIC. If you decide to send or receive text characters as FTAM-3 binary data, some conversion of the native character set might be necessary.
Conformance and Interoperatility Presentation Encoding of FTAM PDUs and Data When receiving PDUs, Compaq FTAM supports all three options listed above. When sending PDUs, Compaq FTAM follows these rules: • • • If single FTAM PDUs are to be sent, they are placed in a single PDV list encoded as single-ASN1-type. If multiple FTAM PDUs are to be sent (grouped requests or responses), they are sent in a single PDV list encoded as single-ASN1-type.
Conformance and Interoperatility Presentation Encoding of FTAM PDUs and Data OSI/FTAM Responder Manual—425199-001 2 -8
3 Compaq FTAM Responder Operation The Compaq responder receives an FTAM request from an initiating system, processes it, performs the appropriate action, and returns an FTAM response to the initiating system. It performs file-handling operations through its virtual filestore (VFS), which acts as an interface to the Guardian file system. This section explains the major components of the Compaq responder process and describes the flow of communication between an initiating system and the Compaq responder.
Responder Data Flow Compaq FTAM Responder Operation Figure 3-1. Compaq FTAM Responder Process FTAM Responder 5 Protocol State Machine VFS 7 6 4 OSI/AS API 4 7 Guardian File System TAPS TSP 3 8 NSP 2 Communications Network 1 Remote FTAM Initiator CDT 208.CDD Responder Data Flow Protocol and user data generally flows to and from the Compaq responder in the steps described below.
Compaq FTAM Responder Operation Responder Data Flow 2. 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. 3. Once on the Compaq responding system, the incoming FTAM indication is sent through the NSP, TSP, and TAPS processes, where it is formatted and processed as required by each OSI layer. 4.
Compaq FTAM Responder Operation OSI/FTAM Responder Manual—425199-001 3 -4 Responder Data Flow
4 Compaq FTAM Responder Support of ISO FTAM Functions This section provides detailed information on the Compaq FTAM responder’s support of ISO FTAM functions.
Compaq FTAM Responder Support of ISO FTAM Functions Functional Units Functional Units Table 4-2 identifies the FTAM functional units that the Compaq responder process supports. The Compaq responder supports all ISO-defined functional units except the FADU locking, recovery, and restart-data-transfer functional units. Table 4-2.
Compaq FTAM Responder Support of ISO FTAM Functions Attribute Support responder partially supports an attribute, it recognizes the attribute name as valid, but provides no value for it. In this case, any reference to that attribute yields the result that no value is available, and any attempt to change the attribute fails. For more information on levels of attribute support, refer to ISO 8571-2, clause 9.4.
Compaq FTAM Responder Support of ISO FTAM Functions Document Types Table 4-4.
Compaq FTAM Responder Support of ISO FTAM Functions Mapping Between FTAM Contents Types and Compaq File Structures Table 4-5. Document Types and Parameters Supported by the Compaq FTAM Responder (continued) FTAM Document Types NBS-9 Parameters Parameter Values maximum-string-length 1-4072 (in bytes) string-significance fixed or variable** Not applicable *** FTAM-2 files are relative (sequential) files, and each logical record of a relative file can be a maximum of 4072 bytes.
Compaq FTAM Responder Support of ISO FTAM Functions Create Mappings fall within the range supported by the Compaq responder for that document type and string-significance value, as follows: Document Type String-Significance Value Maximum-String-Length Value FTAM-1 not significant 1 <= maximum-string-length <= 7148 FTAM-1 fixed 1 <= maximum-string-length <= 7148 FTAM-1 variable 1 <= maximum-string-length <= 7148 FTAM-2 not significant 1 <= maximum-string-length <= 4072 FTAM-3 not significan
Compaq FTAM Responder Support of ISO FTAM Functions Select-Open Mappings Table 4-6.
Compaq FTAM Responder Support of ISO FTAM Functions Select-Open Mappings When you issue a file-open request, you specify a contents-type parameter that provides the document type of the file and, optionally, parameter values that further define the document type.
Compaq FTAM Responder Support of ISO FTAM Functions Select-Open Mappings Table 4-7.
Compaq FTAM Responder Support of ISO FTAM Functions Maximum-String-Length Checking of Data Values Note. Though a default value for each parameter is proposed, if there is a user-defined default value for a particular combination of a file type and file code, that user-defined value will override the system default. Maximum-String-Length Checking of Data Values The responder enforces strict rules on maximum-string-length checking.
Compaq FTAM Responder Support of ISO FTAM Functions File-Attribute Mappings strings may require you to increase the value of the maximum-string-length parameter in your requests.
Compaq FTAM Responder Support of ISO FTAM Functions Kernel Group File Attributes Filename Attribute The filename attribute maps directly from the Compaq external file name to the FTAM VFS, with the exception of specifying NBS-9 files. For an explanation of the relationship between the filename attribute and NBS-9 files, see “NBS-9 Documents” later in this subsection.
Compaq FTAM Responder Support of ISO FTAM Functions Kernel Group File Attributes The responder allows for the simplification of FTAM-2 document types to FTAM-1 document types only. In addition, FTAM-2 simplification is allowed only on Compaq Enscribe relative files, not on SQL tables. Per the ISO 8571-2 provisions, the responder allows no simplification of FTAM-1 or FTAM-3 files. Compaq FTAM does not permit the relaxation of document type parameters to less restrictive values.
Compaq FTAM Responder Support of ISO FTAM Functions Kernel Group File Attributes You can specify DIRLIS with volume or subvolume in any of the following ways: • • • • $volume.subvol.DIRLIS $volume.DIRLIS subvol.DIRLIS DIRLIS Note. Because using ‘DIRLIS’ (uppercase) in the F-SELECT primitive returns the directory file, and Guardian file names are not case-sensitive, you should use “dirlis” (lowercase) in the FSELECT primitive to select an actual file by this name rather than the directory file.
Compaq FTAM Responder Support of ISO FTAM Functions Storage Group File Attributes request primitive. This allows you to specify all or a subset of the attributes listed above. (Likewise, to control which attributes the responder returns when you read the attributes of an NBS-9 file, you set the bit string in the attribute-names parameter of the read-attribute request.) When you read the NBS-9 file, the responder returns only the attributes you select.
Compaq FTAM Responder Support of ISO FTAM Functions Storage Group File Attributes filesize parameter is not specified in a create request, the responder creates a file with a future-filesize value of 8 MB. Subsequent change-attribute requests can change the value of max-extents. In all cases, the minimum value of max-extents is 16, and the maximum value is 978. The extent size cannot be changed.
Compaq FTAM Responder Support of ISO FTAM Functions Security Group File Attributes Table 4-11.
Compaq FTAM Responder Support of ISO FTAM Functions Security Group File Attributes which access to a file is allowed. ISO 8571-2 provides a complete description of the ISO FTAM access-control attribute. Within the access-control attribute, the Compaq responder uses only the action-list field of the first access-control element; the concurrency-access, identity, passwords, and location fields are ignored, as are all access-control elements after the first.
Compaq FTAM Responder Support of ISO FTAM Functions Security Group File Attributes Table 4-13.
Compaq FTAM Responder Support of ISO FTAM Functions • • Security Group File Attributes If any of the insert, replace, extend, change-attribute, or erase access-control bits of the action list are set, the responder sets WRITE access to N, indicating that any user on the Expand network can write to the file. If the delete-file access-control bit of the action list is set, the responder sets PURGE access to N, indicating that any user on the Expand network can purge the file.
Compaq FTAM Responder Support of ISO FTAM Functions Private Group File Attributes Table 4-14. Mapping From Guardian Security to FTAM Action List Guardian Access Action-List Bits Set READ Read WRITE Insert, Replace, Extend, Erase, Change-attribute EXECUTE No effect on access control PURGE Delete-file The read-attribute bit is always set. Legal-Qualifications Attribute The legal-qualifications attribute conveys information about the legal status of the file and its use.
Compaq FTAM Responder Support of ISO FTAM Functions File-Access and Security Considerations Table 4-15. Compaq Support of Optional Parameters Received in Request PDUs (continued) Parameters Level of Compaq Support Diagnostic Decoded and ignored. Access passwords Decoded and ignored. Concurrency control Decoded and ignored. Create password Decoded and ignored. Activity identifier Decoded and ignored. Remove contexts Decoded and ignored. Define contexts Decoded and ignored.
Compaq FTAM Responder Support of ISO FTAM Functions File-Access and Security Considerations password. For details on configuring a default user, refer to the OSI/FTAM Configuration and Management Manual. The VFS actions allowed by the FTAM responder depend on the Guardian security (R W E P) for a file and the user ID for the association. For example, if you have Compaq purge access to a given file, the responder allows the FTAM delete-file action.
Compaq FTAM Responder Support of ISO FTAM Functions File-Access and Security Considerations actions 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.
5 Suggestions for Development of Remote Applications When you write an FTAM application that uses the services of the Compaq responder, how you design, code, and debug it depends largely on the interface you are using on the remote system. However, there are some general things you should consider to make the most effective use of the Compaq FTAM responder.
Suggestions for Development of Remote Applications Troubleshooting The Compaq FTAM responder returns diagnostic messages to your application as specified by the ISO 8571 standard. In many cases, more information is returned than is required by the standard. Appendix A, “Compaq FTAM Responder Diagnostic Messages,” provides cause, effect, and recovery information about all diagnostic messages returned by the responder.
Suggestions for Development of Remote Applications Troubleshooting 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.
Suggestions for Development of Remote Applications OSI/FTAM Responder Manual—425199-001 5 -4 Troubleshooting
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.
Initiator-Identity and Filestore-Password Parameters Responder Manager Initiator-Identity and Filestore-Password Parameters The initiator-identity and filestore-password parameters in the F-INITIALIZE request correspond, respectively, to the Guardian user ID and password on the Compaq system. Optionally, a default user ID and password can be set up in the Compaq FTAM configuration, allowing remote applications access to the responder and its VFS without sending a user ID and password across the network.
Event Messages Responder Manager If the Compaq FTAM responder process is running as a NonStop process pair, the backup Compaq FTAM responder process takes over, and your remote application must reinitiate its Compaq FTAM associations. You or your application should then check and verify all previous work performed using the Compaq responder, correct inappropriate file states left from the component failure, and proceed as appropriate to the needs of your application.
Event Messages Responder Manager • • Failure to establish an association with a Compaq responder due to an invalid initiator ID or password Compaq responder virtual filestore (VFS) file-access failures due to file-system errors or security violations The responder also returns an event message whenever it starts or completes a file transfer, indicating whether or not the transfer was successful.
A Compaq FTAM Responder Diagnostic Messages The Compaq FTAM responder diagnostic messages can be returned in indications and confirms to an initiating FTAM implementation that requested the Compaq FTAM responder to execute a service that it cannot perform. They can also be returned to provide additional information on a successful action.
General FTAM Diagnostic Messages Compaq FTAM Responder Diagnostic Messages Table A-2. Sources and Observers of Errors Source/Observer Identifier Description 0 Source of the error cannot be identified. This identifier is not valid for the observer. 1 Initiating file-service user (initiating application). 2 Initiating file protocol machine. 3 Service supporting the protocol machines. This identifier is not valid for the observer. 4 Responding file protocol machine.
Compaq FTAM Responder Diagnostic Messages General FTAM Diagnostic Messages Effect. The responder aborts the association. If the data buffer capacity was exceeded for the reason given under “Cause,” the Further Details field contains the message smaller PDU or larger MSL needed. Recovery. If the Further Details field indicates that a smaller PDU or a larger MSL is needed, the application or FTAM user should decrease the number of strings sent in one PDU.
Protocol and Supporting Service-Related Diagnostic Messages Compaq FTAM Responder Diagnostic Messages Recovery. The application or FTAM user should retry the operation. This can be a transient condition. If the condition persists, the Compaq problem solver can start another FTAM responder process to balance the load across multiple responder processes.
Compaq FTAM Responder Diagnostic Messages Protocol and Supporting Service-Related Diagnostic Messages 1001 Unsupported parameter values Cause.
Compaq FTAM Responder Diagnostic Messages Protocol and Supporting Service-Related Diagnostic Messages 1009 FTAM protocol error, functional unit error Cause. The responder received a service request that requires a functional unit that was not negotiated when the association was established. Effect. The responder rejects the request. Recovery. The application or FTAM user should establish a new association and negotiate the required functional units. 1011 Lower-layer failure Cause.
Association-Related Diagnostic Messages Compaq FTAM Responder Diagnostic Messages access is less than the number of services in the group. (Only the file-access service class allows a threshold of less than the number of services in the group, allowing a group of primitives to provide some service even if one of the primitives fails.) Effect. The responder aborts the association. Recovery.
Compaq FTAM Responder Diagnostic Messages Association-Related Diagnostic Messages 2002 Unsupported service class Cause. The responder received an initialize request for the unconstrained service class. The Compaq FTAM implementation does not support the unconstrained service class. Effect. The association is not established. Recovery. The application or FTAM user should specify a supported service class on the initialize request. For a list of service classes that Compaq FTAM supports, see Section 4.
Compaq FTAM Responder Diagnostic Messages Association-Related Diagnostic Messages 2015 Initiator identity unacceptable Cause. The initiator-identity parameter in the initialize request was invalid, or it was omitted and there was no default user ID/password configured for the responder. Effect. The association is not established. The responder generates the passwordfailure event (event number 20). Recovery.
Compaq FTAM Responder Diagnostic Messages Selection-Related Diagnostic Messages Effect. The association is not established. The responder generates the password-fail event (event number 20). Recovery. For the first cause, the application or FTAM user should retry the request using a valid password; for the second cause, the Compaq problem solver should correct the default password by reconfiguring the DEFUSER attribute in the responder’s VFS profile on the Compaq system.
Selection-Related Diagnostic Messages Compaq FTAM Responder Diagnostic Messages Table A-6.
Compaq FTAM Responder Diagnostic Messages Selection-Related Diagnostic Messages Effect. The service fails. Recovery. The application programmer or FTAM user should check the attribute values and determine which attribute the responder does not support, and then retry the request without specifying the unsupported attribute in the create request. If the problem persists, the Compaq problem solver can use the SCF TRACE command and the PTrace utility to troubleshoot the problem.
Compaq FTAM Responder Diagnostic Messages Selection-Related Diagnostic Messages 3007 File cannot be deleted Cause. The application or FTAM user attempted to delete a directory list (NBS-9), or the PURGE procedure has failed. Effect. The file is not deleted. The Further Details field identifies the related filesystem error number. Recovery. For an interpretation of the file-system error number, refer to the Compaq Guardian Procedure Errors and Messages Manual. 3012 File busy Cause.
Compaq FTAM Responder Diagnostic Messages Selection-Related Diagnostic Messages 3018 Initial attributes altered Cause. The application or FTAM user attempted to create a file with a future-filesize value greater than one gigabyte. The Compaq FTAM responder does not support files larger than one gigabyte. Effect. This is an information-only diagnostic message. The file is created with a future-filesize value of one gigabyte. Recovery. No action is necessary. 3020 Override selected existing file Cause.
Compaq FTAM Responder Diagnostic Messages Selection-Related Diagnostic Messages 3027 Bad attribute value Cause. An invalid value was detected in an attribute on the create or select service. This message is caused if the filename attribute cannot be decoded or is invalid for the file system. Effect. The service fails. Recovery. The application or FTAM user should correct the value for that attribute and retry.
File-Management-Related Diagnostic Messages Compaq FTAM Responder Diagnostic Messages Effect. The file is created, but not selected. The state-result parameter of the create confirm returns a failure indication. Recovery. The application or FTAM user should issue a select request specifying the correct requested access.
Compaq FTAM Responder Diagnostic Messages Access-Related Diagnostic Messages 4003 Attribute not supported Cause. Either a read-attribute request including the private attributes was issued, or an attempt was made to change an attribute that cannot be changed. Compaq FTAM does not support private attributes. Effect. The service fails. Recovery. No recovery is possible in the case of the read-attribute service. The Compaq FTAM responder does not support private attributes.
Access-Related Diagnostic Messages Compaq FTAM Responder Diagnostic Messages Table A-8.
Compaq FTAM Responder Diagnostic Messages Access-Related Diagnostic Messages 5001 Bad FADU - size error Cause. The application or FTAM user tried to access a nonexistent column in an SQL table. Effect. The responder cancels the service, and the association is left in a data-transfer idle state. Recovery.
Compaq FTAM Responder Diagnostic Messages Access-Related Diagnostic Messages 5005 FADU does not exist Cause. The responder received a read or erase request for an empty FTAM-2 relative file. Effect. In the case of a read, the responder cancels the service. In the case of an erase, the responder issues a negative erase confirmation. Recovery. This is an information-only diagnositic message. Nothing happened. 5008 FADU not available for writing Cause.
Compaq FTAM Responder Diagnostic Messages Access-Related Diagnostic Messages 5015 Operation not available Cause. Either the VFS has attempted to open a file, but the operating system OPEN procedure has failed, or a write request has been issued without the FADU operation set to insert, replace, or extend. Effect. In the case of an open, the responder rejects the request. In the case of a write, the responder cancels the service. Recovery.
Compaq FTAM Responder Diagnostic Messages Access-Related Diagnostic Messages 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 request with the correct FADU operation. Make sure the document type opened supports the access context. Refer to Table A-9 for valid access contexts. Table A-9.
Compaq FTAM Responder Diagnostic Messages Access-Related Diagnostic Messages file recovery operations normally used at the site; then the application or FTAM user can retry the application. 5028 Local failure (unspecific) Cause. A local file-system error occurred as a result of one of the following actions: • • • • • F-ERASE error occurred while the responder was attempting to erase data from a file. F-LOCATE error occurred while the responder was attempting to locate a FADU.
Access-Related Diagnostic Messages Compaq FTAM Responder Diagnostic Messages Recovery. The application or FTAM user should send a cancel response, close the file, and use the change-attribute service to increase the value of the future-filesize attribute of the file. 5036 Contents type inconsistent Cause.
Recovery-Related Diagnostic Messages Compaq FTAM Responder Diagnostic Messages 5040 FADU locking not available on file Cause. The Compaq FTAM responder received a request with a FADU-lock parameter on a read or write service. The Compaq FTAM responder does not support the FADUlock parameter. Effect. The responder cancels the request. The association is left in a data-transfer idle state. Recovery.
Compaq FTAM Responder Diagnostic Messages Recovery-Related Diagnostic Messages OSI/FTAM Responder Manual—425199-001 A -26
Glossary The following glossary defines terms used both in this manual and in the other Compaq FTAM manuals. Not all terms listed here are used in this particular manual. abstract syntax. A standardized method of describing data structures that is independent of the way they are represented in data transmission. An abstract syntax uses a set of primitive elements defined by an abstract syntax notation such as ASN.
Glossary (Application Layer) to manipulate files on remote computer systems. For Compaq FTAM, applications can be written in C or TAL. application entity. The part of an application process that interacts with its peer entity in a remote application process. In an OSI application, the application entity is the part that represents the communication functionality necessary for interoperation. application entity title (AE title).
Glossary ASN.1 (Abstract Syntax Notation-1). The type and value syntax or notation language for representing semantics of protocol that is described in ISO 8824. The Basic Encoding Rules (ISO 8825) standard defines a set of encoding rules that can be applied to values of types defined using the notation specified in ISO 8824. See also abstract syntax. association. A connection between Application Layer entities. See connection. Association Control Service Element. See ACSE. attach.
Glossary code file. A Guardian file containing the object code that you must run to create the specified process. collector An EMS process that accepts event messages from subsystems and logs them in the event log. See EMS. Compare distributor. command file. A text file containing a series of commands that you can run by issuing the OBEY command in TACL or SCF, followed by the name of the text file. common name.
Glossary protocol implementation conformance statement (PICS). Static conformance requirements are constraints specified in the standards or related profiles to facilitate interworking. Dynamic conformance requirements determine what observable behavior is permitted by the standards or profiles in instances of communication. The PICS is a statement, made by the supplier of an OSI implementation, describing the capabilities and options that have been implemented for a given OSI protocol. See also profile.
Glossary (FUP) commands, and generates object-definition source code in a variety of programming languages. default user (DEFUSER). An attribute of a Compaq virtual filestore (VFS) profile that allows access to files in the Compaq responder’s VFS in cases where the initiator identity and filestore password are not provided when an association is established. The default user specifies the default Guardian user ID and password to be used. diagnostic parameter.
Glossary Enscribe. The Compaq database file-management software provided as part of the Guardian file system. The Enscribe software provides access to—and manipulation of—records in a database on a Compaq system. Files on a Compaq NonStop system can be either Enscribe files or NonStop SQL tables. See also NonStop SQL. entry. A DSM object type representing a routing table or directory entry in the OSI manager MIB.
Glossary occurrence of a condition that might affect its operation. Event messages are collected centrally and distributed to files, processes, and terminals that are programmed to receive them. They are displayed in text form as operator messages. execution priority. A numeric-valued attribute of a Compaq process that determines whether the Compaq NonStop Kernel will preempt execution of the process in favor of other processes running in the same CPU.
Glossary encountered in accessing the file on the demountable device. The attribute value is set when a file is created. file-management service class. A service class that permits control of the virtual filestore through a series of independent confirmed service exchanges, but does not include file-transfer mechanisms. The file-management service class permits the ability to read and change file attributes, and create and delete files. file number.
Glossary first-level data types. The lowest-level DDL structures, which serve as building blocks on which DDL parameter structures are based. format effectors. A class of control characters mainly intended for layout and positioning of information on character-imaging devices, such as printers and video display terminals. FTAM (File Transfer, Access and Management). A set of Application Layer services and protocols used for manipulating files across an OSI network, as defined by the ISO-8571 specification.
Glossary Compaq max-extents attribute: modifying the future-filesize attribute changes the maxextents attribute, and vice versa. GeneralString. The character-string type of strings containing any of the characters for all G sets and all C sets (as defined by ISO 2022), the space character, and the delete character. These strings contain format effectors. GraphicString. The character-string type of strings containing any of the characters for all G sets (as defined by ISO 2022) and the space character.
Glossary • There are no restrictions on the number of levels, on the arc lengths, or on the number of arcs originating from each node. The access unit, or subtree, of a node in this model is called a file-access data unit (FADU). FTAM-2 files have a two-level hierarchy of one root node and many secondlevel nodes. FTAM-1 and FTAM-3 files have only a single root FADU. See FADU and root FADU. IA5String.
Glossary internal process name. The name by which APLMGR recognizes a Compaq initiator or responder process. This name is assigned when the process is created and can be a maximum of eight ASCII characters. International Organization for Standardization. See ISO. International Standard. See IS. interoperability. The ability of an FTAM implementation to work with other FTAM implementations to deliver FTAM services. IS (International Standard). A final specification standard issued by ISO.
Glossary management interface. An interface available to the system manager for use in configuring, monitoring, and controlling subsystems and relationships between subsystems. Manager process. A Compaq subsystem process with which the Subsystem Control Point (SCP) management process communicates to control a particular subsystem. The APLMGR process is the manager process for Compaq FTAM; the OSI manager process is the manager process for OSI/AS; and the TSP process is the manager process for OSI/TS.
Glossary Network service access point. See NSAP. network service provider. See NSP. NIST (National Institute of Science and Technology). A U.S. government institution, formerly known as the National Bureau of Standards (NBS), that sets standards and promotes their acceptance. node. (1) The basic building block of the FTAM hierarchical file structure. (2) A Compaq NonStop system that is part of an Expand network. node descriptor.
Glossary object identifier. A value, distinguishable from all other such values, that is associated with an ISO information object. A standard representation of an object identifier is a set of numbers representing a directed path through a standards-based tree hierarchy, often shown as a sequence of two or more values enclosed in braces ({}). Examples of objects represented by object identifiers are document type names, constraint sets, abstract syntaxes, transfer syntaxes, and AE titles. object state.
Glossary OSI Reference Model. A communications architecture, adopted by the ISO in 1984, that includes seven layers that define the functions involved in communications between two systems, the services required to perform these functions, and the protocols associated with these services. See also layer. OSI subsystems. The Compaq subsystems that support the various layers and application service elements of the OSI Reference Model, including the FTAM subsystem, APLMGR, OSI/AS, OSI/TS, and TLAM or X25AM.
Glossary example, a default set of permitted actions that is always used for a specific document type regardless of what is proposed. The responder implements the set of permitted actions in some way that maps them onto the underlying real system. Physical Layer. Layer 1 in the OSI Reference Model. This layer establishes the actual physical connection between the network and the computer equipment.
Glossary private group. A free-standing group of FTAM attributes that are outside the scope of OSI standardization. process. A running entity, managed by the Compaq NonStop Kernel, that is created by taking a program from a file on a disk and running it in a processor. process identification number (PIN). An unsigned integer that identifies a process in a processor module. Internally, a PIN is used as an index into the process control block (PCB) table.
Glossary The PSAP is highly system-dependent and generally refers to the way interlayer communication is accomplished. See also SAP. PSAP address. A presentation address that is used to identify a single PSAP. PSEL (presentation selector). A logical address in the Presentation Layer through which presentation services are made available to Application Layer implementations.
Glossary required parameter. (1) In a protocol data unit (PDU), a parameter that is always present. (2) In a Compaq programmatic or interactive interface, a parameter to a procedure (for example, a procedure in the FTAM API) or to an interactive command (such as an SCF command) that must be specified when the procedure is called or the command is issued. Contrast with conditional parameter and optional parameter. reset time.
Glossary SCF (Subsystem Control Facility). A utility that provides a common, interactive management interface for configuring, controlling, and collecting information from Compaq data communications products. SCP (Subsystem Control Point). The process used to provide the focal point for all Compaq data communications subsystems. There can be several instances of this process.
Glossary service user. An entity that uses services provided to it by a lower-layer entity. For example, the FTAM initiator is a service user of ACSE and presentation services provided by OSI/AS. Contrast service provider. session address. See SSAP. Session Layer. Layer 5 in the OSI Reference Model. This layer allows the setup and termination of communication sessions between systems on the network. session selector. See SSEL. session service access point. See SSAP. simplification.
Glossary status. A Compaq procedure completion code that indicates the outcome of a call. This code can assume one of nine values. storage group. File attributes that provide information about a file and the data stored in it. These attributes are negotiated at association establishment.
Glossary objects. Each subsystem has a process through which applications can request services by issuing commands defined by that subsystem; in some cases, this process is the entire subsystem. Many subsystems also have interactive interfaces. Subsystem Control Facility. See SCF. Subsystem Control Point. See SCP. Subsystem Programmatic Interface. See SPI. subtree.
Glossary also performs some management services in the DSM environment. See also NSP process and TSP process. TAPS subdevice. A subdevice, maintained by OSI/AS, that enables communication between an FTAM initiator or responder and the TAPS process. See subdevice. TeletexString. The character-string type of strings conforming to CCITT Recommendation T.61. These strings do not contain format effectors. TLAM (Tandem LAN access method).
Glossary protocol (IP) of the Network Layer. TSP processes are provided by the underlying OSI/TS subsystem. See also NSP process and TAPS process. UA (unstructured all data units). An access context for which data is transferred as file-contents data elements; that is, only the data contents of the file are transferred. See access context; contrast with FA. unconfirmed service.
Glossary warning. An information-only message returned by the system, indicating a possible problem. A warning can be significant, but does not cause the command or operation to fail. A warning is less serious than an error. Contrast with error. write functional unit. A functional unit that allows the following activities on an association: • • • Establishing the file-open regime Transferring data from the initiator to the responder Releasing the file-open regime X25AM (X.25 Access Method).
Index A Access context, not available (message 5024) A-21 Access contex, for writing FTAM-2 files 2-6 Access control inconsitent (message 3016) A-13 Access request violates ...
D Index Compaq FTAM (continued) Guardian file system 1-7 management considerations for remote applications 6-1 interfaces 1-4 responder See Responder, Compaq FTAM services provided 1-2 standards supported viii troubleshooting 5-2 underlying subsystems 1-4 Compaq Nonstop Kernel 1-2 See also Guardian Concurrency control parameter 4-22 Configuration considerations 6-1 Confirm primatives 1-3 Conformance definition of 2-1 ISO standards 2-1 Contents type inconsistent (message 5036) A-24 Contents type list cut .
E Index DSM See Distributed Systems Management (DSM) E EBCDIC character set 2-6 Encoding data 2-5, 2-6 EOF (end-of-file) attribute, Guardian 4-15 Error handling 5-1 Errors See Diagnostic messages Escape sequences 2-5 Event Management Service (EMS) DSM component 1-4 event messages 6-3 troubleshooting tools 5-2 Event messages See Event Management Service (EMS), Diagnostic messages F FADU cannot be inserted (message 5011) A-20 FADU cannot be replaced (message 5012) A-20 FADU diagnostic messages A-17 FADU d
G Index File-type attribute, Guardian 4-8 Format effectors 2-5 FPDUs encoding as presentation data 2-6 limits on string-length values 2-5, 4-10 size limit 4-10 FTAM See Compaq FTAM, ISO FTAM FTAM protocol data units See FPDUs FTAM-1 files data-transfer considerations 2-4 maximum file size 4-6, 4-8 parameters supported by responder 4-4 permitted actions, table of 4-12 select-open mappings to Guardian structure, table of 4-8 FTAM-2 files create mappings to Guardian structure, table of 4-7 parameters support
K Index Indication primitives 1-3 Initial attributes altered (message 3018) A-14 Initial attributes not possible (message 3002) A-11 Initial attributes parameter 4-17 Initiating system, definition of 1-4 Initiator Compaq FTAM and FTAM API 1-3 definition of 1-2 role in architecture 1-2 Initiator identity unacceptable (message 2015) A-9 Initiator, remote interoperability with 2-1 Initiator-identity parameter 4-20, 4-21, 4-22, 6-2 Interfaces file system 3-1 management 1-2 programmatic interface See FTAM API
O Index Network layer services 1-5 NIST FTAM agreement 2-1 Nonstop SQL 4-11 NSP process 1-5 O Open mappings 4-7 Operating system See Compaq Nonstop Kernel Operation not available (message 5015) A-21 Operator messages See Event Management Service (EMS) Optional parameters, support for 4-21 OSI Reference Model, Compaq products for 1-4 OSI/AS subsystem API 3-1 interaction with 1-4 interoperability 2-2 OSI/TS subsystem 1-4 Override deleted and recreated ...
S Index Relaxation of parameters 2-4, 4-4 Remote initiator definition of 1-2 interoperability with 2-1 Remove-contexts parameter 4-22 Request primitives 1-3 Request procedures, optional parameters supported 4-22 Requested access violates ...
U Index U Unconstrained service class 4-1 Universal-class parameter 2-4 Unspecific FTAM protocol error (message 1007) A-5 Unspecific initiator error (message 7) A-3 Unspecific responder error (message 1) A-2 Unsupported functional unit (message 2003) A-8 Unsupported parameter values (message 1001) A-5 Unsupported service class (message 2002) A-8 V Viewpoint application 6-3 Virtual filestore (VFS) 3-1 Expand network 1-7 file attributes and Guardian file attributes 4-11 file-access and security considerati