Page 1 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.
Page 2: Document History
OSI/FTAM C30, OSI/APLMGR C30 098329 OSI/FTAM D20, OSI/APLMGR D20 425199-001 OSI/FTAM D43 OSI/APLMGR D43 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.
Page 3: Table Of Contents
Manual Information New and Changed Information About This Manual Supported Standards Related Manuals Your Comments Invited Notation Conventions 1. Introduction to the Compaq FTAM Responder Functional Overview Compaq FTAM Services FTAM Applications Management Interfaces Architectural Overview The Responder and Underlying Subsystems The Responder and the File System 2.
Page 4 3. Compaq FTAM Responder Operation Responder Structure Responder Data Flow 4. Compaq FTAM Responder Support of ISO FTAM Functions Supported Functions Service Classes Functional Units Attribute Groups Attribute Support Document Types Mapping Between FTAM Contents Types and Compaq File Structures...
Page 5 Attribute Groups Supported by the Compaq FTAM Responder Table 4-4. Attributes Supported by the Compaq FTAM Responder Table 4-5. Document Types and Parameters Supported by the Compaq FTAM Responder Table 4-6. Create Mappings: FTAM Contents Type to Compaq File Structure OSI/FTAM Responder Manual—425199-001...
Page 6 Select-Open Mappings: Compaq File Structure to FTAM Contents Type Table 4-8. Actions Permitted for FTAM Document Type Table 4-9. Simplification of Document Types Supported by the Compaq FTAM Responder Table 4-10. Bit String for NBS-9 File Attributes Table 4-11. FTAM Storage Attributes and Corresponding Compaq File Attributes Table 4-12.
Page 7: New And Changed Information
(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.
Page 8 What’s New in This Manual New and Changed Information OSI/FTAM Responder Manual—425199-001...
Page 9: About This Manual
Compaq OSI/File Transfer, Access and Management (FTAM) responder process. This manual has the following objectives: • Introduce the Compaq FTAM responder and how it fits into the Compaq FTAM architecture • Describe conformance and interoperability issues for the Compaq FTAM responder •...
Page 10: Supported Standards
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.
Page 11: Related Manuals
Compaq system, you need whatever documentation is provided for the remote implementation. If your FTAM initiator is on a Compaq system, you need the following manuals in the Compaq FTAM manual set: the OSI/FTAM Programming Guide and the OSI/FTAM Programming Reference Manual.
Page 12: Your Comments Invited
Reference Manual for FTAM and APLMGR. • Operator Messages Manual. If you need to understand how files are stored in the Compaq responder’s VFS or if you are diagnosing problems in the VFS, the following manuals are also likely to be of interest: •...
Page 13: Notation Conventions
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.
Page 14 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 ) ;...
Page 15 !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_ ( Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual.
Page 16 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.
Page 17: Introduction To The Compaq Ftam Responder
Solving problems involving a Compaq FTAM responder or its virtual filestore (VFS) While this manual is designed to be as complete as possible with regard to the Compaq FTAM implementation of the responder, it is not intended to duplicate or replace the ISO standards and National Institute of Science and Technology (NIST) FTAM Phase 2 agreements.
Page 18: Compaq Ftam Services
Compaq FTAM responder. There is no programmatic interface to the Compaq responder; you request the services of the responder by means of the FTAM interface on your remote system, which may or may not be a Compaq system.
Page 19: Figure 1-1. An Ftam Service Using Four Primitives
Compaq FTAM product with other FTAM implementations. If your remote FTAM application also runs on a Compaq system, you use the Compaq FTAM application program interface (API), a set of procedures that interact with the Compaq FTAM initiator process, to request FTAM services.
Page 20: 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: •...
Page 21 • 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.
Page 22: Figure 1-2. Compaq Ftam Responder Architectural Overview
RS-449 X.21, V.35 PDUs from a remote FTAM initiator are received by the Compaq system at the Physical Layer and are transmitted up through the appropriate communications controller (or adapter), NSP process, TSP process, and TAPS process to the FTAM responder process.
Page 23: The Responder And The File System
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.
Page 24 Introduction to the Compaq FTAM Responder The Responder and the File System OSI/FTAM Responder Manual—425199-001 1 -8...
Page 25: Conformance And Interoperatility
A list of the supported standards and agreements that apply to Compaq FTAM is provided in “About This Manual” at the beginning of this manual.
Page 26: Basic Characteristics Of Ftam Implementations
1 of the Presentation Layer, as stated in ISO IS 8822 and 8823; and version 2 of the Session Layer, as stated in ISO IS 8326 and 8327. To interoperate with Compaq FTAM, other FTAM implementations must support compatible versions of ACSE, Presentation, and Session, as well as the services underlying the Session Layer.
Page 27: Limitations On Value Of Future-Filesize Attribute
1 GB. The smallest file the Compaq responder can create has a future-filesize value of 64 KB. If a smaller future-filesize value is requested, the responder creates the file with a future- filesize value of 64 KB.
Page 28: Data-Transfer Considerations
Guardian file structures and attributes, and vice versa. Section 4 describes the mappings of FTAM document types to Guardian file types. Note that the Compaq responder does not keep a permanent record of the contents-type parameter values used on creation of a file in the VFS. These values are directly available only during the life of the FTAM association in which the file was created.
Page 29: Limits On Small String-Length Values With Large Pdus
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.
Page 30: Presentation Encoding Of Ftam Pdus And Data
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.
Page 31 PDV list encoded as single-ASN1-type. • When F-DATA requests are sent by the Compaq responder, the method of encoding depends on the number of data elements to be encoded. If only a single data element is to be sent, it is placed in a single PDV list encoded as single-ASN1-type.
Page 32 Conformance and Interoperatility Presentation Encoding of FTAM PDUs and Data OSI/FTAM Responder Manual—425199-001 2 -8...
Page 33: Responder Structure
The virtual filestore (VFS) acts as an interface to the file system. Files accessible via the file system can also be accessed via the VFS component of the Compaq responder. The VFS is responsible for translating file structures and attributes into FTAM file structures and attributes, and vice versa.
Page 34: Responder Data Flow
Initiator Responder Data Flow Protocol and user data generally flows to and from the Compaq responder in the steps described below. Note that the responder sends primarily responses, although cancel and abort requests—and data indications during a data transfer—are also possible. For the purposes of this subsection, assume that the remote initiator sends an FTAM request and the responder returns a response to that request.
Page 35 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.
Page 36 Compaq FTAM Responder Operation Responder Data Flow OSI/FTAM Responder Manual—425199-001 3 -4...
Page 37: Compaq Ftam Responder Support Of Iso Ftam Functions
Supported Functions The functional scope of an FTAM association depends on which FTAM functions are supported both by the Compaq FTAM responder and the remote FTAM initiator with which it is interoperating. The following four tables identify the FTAM service classes, functional units, attribute groups, and attributes that the Compaq responder process supports.
Page 38: Functional Units
Private Attribute Support Table 4-4 identifies the FTAM attributes that the Compaq responder supports and the type of support given—full or partial. In the case of fully supported attributes, the responder returns the current attribute value on a read-attribute request. When a OSI/FTAM Responder Manual—425199-001...
Page 39: Table 4-4. Attributes Supported By The Compaq Ftam Responder
For more information on levels of attribute support, refer to ISO 8571-2, clause 9.4. Note that Compaq files protected by the Compaq Safeguard system software security package have fewer fully supported attributes than files protected by the Guardian environment.
Page 40: Document Types
Document Types Table 4-5 identifies the FTAM document types that the Compaq responder supports and provides all supported values for associated contents-type parameters. The parameter values listed here are those directly supported; for information on the default values of these parameter values, see Table 4-7, later in this section.
Page 41: Mapping Between Ftam Contents Types And Compaq File Structures
FIXED, the file will be an unstructured file with a maximum-string-length of 4096 bytes. ∗∗∗ This value represents the Compaq FTAM responder default for NBS-9 files. If you open an NBS-9 file without specifying the file attributes to return, the Compaq responder defaults the parameter setting to the filename attribute only.
Page 42 ISO FTAM Functions fall within the range supported by the Compaq responder for that document type and string-significance value, as follows: Document String-Significance Type Value FTAM-1 not significant FTAM-1 fixed FTAM-1 variable FTAM-2 not significant FTAM-3 not significant FTAM-3 fixed...
Page 43: Select-Open Mappings
Select-Open Mappings Table 4-7 shows the FTAM document types that correspond to each Compaq file type that can be selected, opened, and read. This table indicates the default parameter values for the document types that Compaq supports, whereas Table 4-5, earlier in this section, indicates the full range of parameter values for these document types.
Page 44: Table 4-7. Select-Open Mappings: Compaq File Structure To Ftam Contents
When a remote initiator sends a file-open request to the Compaq responder and specifies a contents type of unknown on the open request, the contents type returned by the responder yields the appropriate FTAM document type according to the requirements of the file system and as outlined in Table 4-7.
Page 45 ∗∗ This is the standard Guardian file attribute that stands for the maximum record length. ∗∗∗ This value represents the Compaq responder default for NBS-9 files on an open. If you open an NBS-9 file without specifying the file attributes to return for the files in the directory, the Compaq responder defaults the parameter setting to the filename attribute only.
Page 46: Maximum-String-Length Checking Of Data Values
5027, indicating a bad read. Limits on Small String-Length Values With Large PDUs When the Compaq 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.
Page 47: File-Attribute Mappings
Note. When the Compaq responder encodes data, the maximum encoded-data header overhead (TAG + LEN) is always 4 bytes per string. (The same is true for data encoded by the Compaq initiator.) An FTAM configurable file cannot be opened by the responder. File-Attribute Mappings The following subsection maps FTAM virtual filestore file attributes to specific Guardian and NonStop SQL file attributes.
Page 48: Table 4-8. Actions Permitted For Ftam Document Type
ISO FTAM Functions 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”...
Page 49: Table 4-9. Simplification Of Document Types Supported By The Compaq Ftam Responder
F-SELECT primitive with a filename attribute of DIRLIS (all in uppercase), the Compaq responder returns a file of directory entries (an NBS-9 file) for the volume and subvolume specified in the filename attribute. The read and read- attribute actions are the only file actions that you can perform on an NBS-9 file.
Page 50: Table 4-10. Bit String For Nbs-9 File Attributes
ISO FTAM Functions 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 F- SELECT primitive to select an actual file by this name rather than the directory file.
Page 51: Storage Group File Attributes
NIST FTAM Phase 2 agreements, Part 9, Clause A.8.2. Note. On Compaq systems, an NBS-9 file does not correspond to an actual physical Compaq file; therefore, the read-attribute action does not provide much useful information for NBS-9 files.
Page 52: Table 4-11. Ftam Storage Attributes And Corresponding Compaq File Attributes
1 GB. The smallest file the Compaq responder can create has a future-filesize value of 64 KB. If a smaller future-filesize value is requested, the responder creates the file with a future- filesize value of 64 KB.
Page 53: Security Group File Attributes
Security Attributes Access control Legal qualifications ∗ In accordance with ISO 8571-2, clause 12.16, the Compaq responder supports only a single action list for the access-control attribute. Access-Control Attribute The ISO FTAM access-control attribute is a set of access-control elements, with each element consisting of an action-list field and, optionally, concurrency-access, identity, passwords, and location fields.
Page 54 Creating Files. For files created through FTAM, the access-control attribute provided by the initiating system with the initial-attributes parameter in the F-CREATE request maps to Compaq file security (R W E P—Read Write Execute Purge). This mapping is as follows: •...
Page 55: Table 4-13. Mapping From Ftam Action List To Guardian Security
The Compaq responder, however, processes only the first access-control element sent for insert-values and for delete-values. The Compaq responder also ignores all but the first component of the insert-values or delete-values information, using only the action-list information to modify Guardian security (R W E P) for the file.
Page 56 Guardian security is O, user is the owner of the file, and file is on the same Expand node as the responder. The Compaq responder sets the individual bits of the action list according to the Guardian access allowed for the user. Table 4-14 shows how Guardian security maps to FTAM action-list settings.
Page 57: Private Group File Attributes
Unsupported Optional ParametersSupported and Unsupported Optional Parameters Supported and Unsupported Optional Parameters Table 4-15 indicates the level of support provided by the Compaq responder for the optional parameters received in request PDUs. It shows what action the Compaq responder performs on the optional parameters received from a remote initiator.
Page 58: File-Access And Security Considerations
The VFS controls access to files through normal Guardian security mechanisms. Each FTAM association has a Compaq user ID associated with it. This user ID can assume two values, depending on whether the initiator-identity parameter is supplied in the F- INITIALIZE request primitive.
Page 59: Table 4-17. Guardian Access Required To Perform Ftam Actions
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. Table 4-17 shows the Guardian access required for each FTAM VFS action.
Page 60 Compaq FTAM Responder Support of File-Access and Security Considerations ISO FTAM Functions 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...
Page 61: Suggestions For Development Of Remote Applications
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.
Page 62: Troubleshooting
Guardian when the file creation attempt failed. A Compaq problem solver or someone else with access to the Compaq system can look up this number in the Guardian Procedure Errors and Messages Manual to obtain information on what occurred and how to correct the problem.
Page 63 FTAM association once it is established, can be especially useful in troubleshooting. The PTrace (print trace) utility allows the Compaq problem solver to look at trace data generated with the SCF TRACE command. The TRACE command provides a log of message traffic between the various processes running on the Compaq system;...
Page 64 Suggestions for Development of Remote Troubleshooting Applications OSI/FTAM Responder Manual—425199-001 5 -4...
Page 65: 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: •...
Page 66: Initiator-Identity And Filestore-Password Parameters
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.
Page 67: Event Messages
• Writing to a file that already existed In the case of reading a file, no recovery is necessary. The Compaq responder does not modify files opened for reading only. In the case of writing to a file, you should probably consider the file unusable. If you created the original file, the best recovery might be to delete the unusable file and recreate it.
Page 68 • 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.
Page 69: Compaq Ftam Responder Diagnostic Messages
FTAM user on the initiating system, or by the Compaq problem solver on the Compaq system. For problems that lie on the initiating system, it may be useful to notify the remote initiator site when error conditions occur in case the remote application does not check for returned diagnostics.
Page 70: General Ftam Diagnostic Messages
256 characters in the Further Details fields, providing additional information on the nature of the problem. General FTAM Diagnostic Messages Table A-3 displays the general error identifiers returned by the Compaq FTAM responder. Table A-3. General FTAM Diagnostic Messages Identifier...
Page 71 Compaq site for contacting the appropriate support personnel. These procedures might involve contacting the local Compaq support analyst. For details on how to trace the responder, refer to the SCF Reference Manual for FTAM and APLMGR and the Compaq PTrace Reference Manual.
Page 72: Protocol And Supporting Service-Related Diagnostic Messages
Recovery. The application or FTAM user can either retry with the correct select-request or create-request parameters, or use initiator-ID and filestore-password values that support the requested access; or the Compaq problem solver can change the local Compaq security for the file.
Page 73 Recovery. This can be an interoperability problem. Verify that the initiator is issuing a valid request to the responder. The Compaq problem solver can do this by tracing the responder and verifying the protocol. For information on tracing, refer to the SCF Reference Manual for FTAM and APLMGR and the OSI/FTAM Configuration and Management Manual.
Page 74 Effect. The responder aborts the association. Recovery. The application or FTAM user should discard the association context, reestablish the association, and retry the operation. If the problem persists, the Compaq problem solver should verify that the TAPS process is configured properly and trace the responder.
Page 75: Association-Related Diagnostic Messages
Recovery. The application or FTAM user should reselect the file with the required requested access and retry. If the problem persists, the Compaq problem solver can use the SCF TRACE command and the PTrace utility to troubleshoot the problem. For more information on tracing and troubleshooting, refer to the OSI/FTAM Configuration and Management Manual.Association-Related Diagnostic Messages...
Page 76 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. 2003 Unsupported functional unit Cause.
Page 77 Recovery. Either the application or FTAM user should retry with a valid initiator identity, or the Compaq problem solver should configure the responder to have a default user ID/password. Change the VFS profile for the responder to define a DEFUSER attribute.
Page 78: Selection-Related Diagnostic Messages
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.
Page 79: Table A-6. Selection-Related Diagnostic Messages
Table A-6. Selection-Related Diagnostic Messages Value Type 3000 3002 3004 3005 3006 3007 3012 3013 3016 3018 3020 3021 3022 3027 3028 3029 3030 3000 File name not found Cause. The file requested on the select service could not be found. File-system error 11 was returned.
Page 80 11 in attempting to access a previously selected file. Effect. The service fails. Recovery. The application or FTAM user should either retry the operation specifying a file that exists, or try again after the Compaq problem solver has replaced the file. 3005 File already exists Cause.
Page 81 PURGE procedure has failed. Effect. The file is not deleted. The Further Details field identifies the related file- system 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.
Page 82 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.
Page 83 Effect. The service fails. Recovery. The application or FTAM user should correct the value for that attribute and retry. For possible limitations on attribute values that the Compaq FTAM responder supports, see Section 4. 3028 Requested access violates permitted actions Cause.
Page 84: File-Management-Related 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. File-Management-Related Diagnostic Messages Table A-7 displays the diagnostic error identifiers that result from either file system errors or improper management of read-attribute or change-attribute requests.
Page 85: 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.
Page 86: Table A-8. Access-Related Diagnostic Messages
Table A-8. Access-Related Diagnostic Messages Identifier Type 5000 5001 5003 5004 5005 5008 5011 5012 5015 5022 5023 5024 5026 5027 5028 5030 5032 5036 5040 5000 Bad FADU (unspecific) Cause. The FADU-ID parameter on a read or write request is invalid. Effect.
Page 87 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. The application or FTAM user should issue a cancel response and then reissue the request, verifying that the number of data elements in the FADU sent is less than or equal to the number of columns in the table.
Page 88 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.
Page 89 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.
Page 90: Table A-9. Access Contexts By Document Typ
Data Values” in Section 4. If the application specified the correct file, the application or FTAM user should retry the application; if the error persists, the file is probably corrupt and cannot be accessed. In this case, the Compaq problem solver should perform the OSI/FTAM Responder Manual—425199-001...
Page 91 Recovery. The application or FTAM user should retry the request using a different file, delete the file and create a new one, or notify the Compaq problem solver of the file condition and find out if an alternative file can be used to access the information. If an alternative file is available, the application or FTAM user should retry the request using that file.
Page 92: Table A-10. Ftam Contents Types And Equivalent Guardian File Structures
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. A service has been attempted without specifying a valid document type (for example, if the application or FTAM user tries to perform an FTAM-2 simplification of an SQL file);...
Page 93: Recovery-Related Diagnostic Messages
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 FADU- lock parameter. Effect. The responder cancels the request. The association is left in a data-transfer idle state.
Page 94 Compaq FTAM Responder Diagnostic Messages Recovery-Related Diagnostic Messages OSI/FTAM Responder Manual—425199-001 A -26...
Page 95 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.
Page 96 Application Manager. See APLMGR. application name. The Compaq OSI/AS term for a reference name used to look up an OSI address in the local OSI/AS management information base (MIB). In Compaq FTAM terminology, this name is called the common name. See common name.
Page 97 The backup process that has an open to an FTAM initiator or responder process. See backup process. backup process. In a Compaq NonStop system, a process that is identical to the primary process and is created at the same time as the primary process. These two processes act as a NonStop process pair.
Page 98 ISO FTAM standard that provides the ability to manipulate files between local and remote file stores on a network. Compaq NonStop Kernel. The operating system, which consists of the core and system services. The operating system does not include any application program interfaces.
Page 99 If you are using the Compaq FTAM initiator, and you do not specify contents-type in a call to FTM_OPEN_REQ_ , it will default to indicate that the contents type is unknown.
Page 100 (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.
Page 101 (1) A condition that causes a command or other operation to fail. Contrast with warning. (2) A code that indicates the outcome of a procedure call. For the procedures in the FTAM API, this value can be either a negative error code defined by Compaq FTAM or a positive Compaq file-system error number.
Page 102 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. The NonStop Kernel always executes the highest-priority process that is ready to run.
Page 103 A unique number generated by the Compaq NonStop Kernel to be used in file-system calls. The number is assigned to a file when an application accesses that file, and it is discarded when the application is finished with the file.
Page 104 FTAM initiator errors. Locally generated errors returned when the return value on a Compaq FTAM procedure call (shown in the Compaq FTAM manuals as status or error, depending on the procedure) indicates an error. The value of status or error indicates what occurred and how to proceed.
Page 105 Guardian process name. The external name by which the Compaq NonStop Kernel identifies a process. This name is assigned when a process is created using the NAME attribute. To operate on a Compaq Expand network, this name must be a maximum of five ASCII characters, including the initial dollar sign ($).
Page 106 The file-service user that requests the establishment of the FTAM regime. In Compaq FTAM, the initiator is a process that allows FTAM applications on a Compaq NonStop system to access FTAM protocol and to request services of a responder on a remote computer system.
Page 107 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.
Page 108 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.
Page 109 X25AM and TLAM subsystems. See also TSP process and TAPS process. null object type. A Compaq term used to represent the absence of an object type in an SCF command. If a command supports the null object type, you can issue it without specifying an object type.
Page 110 (1) In a protocol data unit (PDU), a parameter that is sometimes but not always present. (2) In the Compaq FTAM API, a procedure-call parameter that can be included in a given procedure call or command, but is not required for use with the procedure or command.
Page 111 Transport Layer on a local Compaq system to the Transport Layer on a remote system in an OSI network. owner ID. The identity (Guardian user ID) of the owner of a process on a Compaq NonStop system.
Page 112 PID (process identifier). The combination of the central processing unit (CPU) number and the process identification number (PIN) for a process running on the Compaq NonStop Kernel. port address. For X25AM lines, the logical port number used with the X.25 network;...
Page 113 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.
Page 114 PSEL (presentation selector). A logical address in the Presentation Layer through which presentation services are made available to Application Layer implementations. On a Compaq system, the PSEL is a number that uniquely links a TAPS process with a process that implements Application Layer services—for example, an FTAM initiator or responder.
Page 115 The file-service user that accepts an initiator’s request to establish an FTAM regime. In Compaq FTAM, the responder is a process that services FTAM requests initiated from remote systems on an OSI network. The Compaq responder acts as an FTAM file server, mapping FTAM requests into Guardian file operations and providing a translation between Guardian file structures and FTAM file structures.
Page 116 A set of functional units negotiated at association establishment. ISO FTAM specifies five levels of service classes. service ID. A value identifying the Compaq OSI service that is the source of an error condition being reported. The APS_STATUS_ procedure returns service ID values in the service-id parameter and within the structure returned in the original-error-info parameter.
Page 117 Compaq NonStop systems to define common message-based interfaces for communication between requesters and servers—for example, in a management application. The SPI interface to Compaq FTAM is not available for customer use. SQL (structured query language). A fourth-generation-language standard that provides a means to access and associate data in a relational database.
Page 118 See SQL. subdevice. A logical entity maintained by a Compaq subsystem to provide access to a physical connection—that is, to 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.
Page 119 A DSM state. See state (definition 2). summary-state transition. See state transition. super group. The set of Compaq NonStop Kernel users whose group ID is 255. User IDs within the super group confer implicit authorizations not available to other users, including the ability to execute sensitive SCF commands.
Page 120 TSEL (transport selector). A logical address in the Transport Layer through which transport services are made available. TSP (transport service provider) process. A process in the Compaq OSI end system that performs service and protocol functions for the Transport Layer and for the internet OSI/FTAM Responder Manual—425199-001...
Page 121 VFS component of the Compaq FTAM responder. This includes all files on the Expand network to which the responder process’ system belongs. The Compaq FTAM responder uses the VFS to access the Guardian file system in servicing requests from a remote FTAM initiator.
Page 122 Transferring data from the initiator to the responder • Releasing the file-open regime X25AM (X.25 Access Method). A Compaq product that implements the services of the Network Layer and the Physical Layer for WANs. X.25 network. Any network or subnetwork linked using X.25 standards. X.25 standards are CCITT standards that define packet-switching carrier communication in the Network Layer over wide area networks (WANs).
Page 123 Application Control Service Element (ACSE) Application layer services Applications designing remote program interface (FTAM API) troubleshooting Architecture, Compaq FTAM responder 1-4, ASCII character set ASN.1 data element Association Control Service Element Association, definition of Attribute cannot be changed (message 4002)
Page 124 Compaq FTAM (continued) Guardian file system management considerations for remote applications interfaces responder See Responder, Compaq FTAM services provided standards supported viii troubleshooting underlying subsystems Compaq Nonstop Kernel See also Guardian Concurrency control parameter Configuration considerations Confirm primatives Conformance definition of...
Page 125 See Distributed Systems Management (DSM) EBCDIC character set Encoding data 2-5, EOF (end-of-file) attribute, Guardian Error handling Errors See Diagnostic messages Escape sequences Event Management Service (EMS) DSM component event messages troubleshooting tools Event messages See Event Management Service (EMS), Diagnostic messages FADU cannot be inserted (message 5011)
Page 126 Format effectors FPDUs encoding as presentation data limits on string-length values 2-5, size limit 4-10 FTAM See Compaq FTAM, ISO FTAM FTAM protocol data units See FPDUs FTAM-1 files data-transfer considerations maximum file size 4-6, parameters supported by responder permitted actions, table of...
Page 127 Last-modification attribute Last-reader attribute Last-read-access attribute Legal-qualifications attribute Local failure (messages 5028 and 5030) A-23 Lower OSI layers, Compaq products for Lower-layer failure (message 1011) Management configuration considerations event messages considerations fault tolerance considerations Management interfaces Managing files, diagnostic messages...
Page 128 See Compaq Nonstop Kernel Operation not available (message 5015) A-21 Operator messages See Event Management Service (EMS) Optional parameters, support for OSI Reference Model, Compaq products OSI/AS subsystem interaction with interoperability OSI/TS subsystem Override deleted and recreated ... (message 3021)
Page 129 SEQUENCE OF PDV-list Service class unsupported (message 2002) Service classes incompatible (message 2021) A-10 Service classes, interoperability Services provided by Compaq FTAM Service-related diagnostic messages (1001- 1017) Session layer services Simplification Specific PDU request inconsistent ... (message 1017) SQL files...
Page 130 Unconstrained service class Universal-class parameter Unspecific FTAM protocol error (message 1007) Unspecific initiator error (message 7) Unspecific responder error (message 1) Unsupported functional unit (message 2003) Unsupported parameter values (message 1001) Unsupported service class (message 2002) Viewpoint application Virtual filestore (VFS) Expand network file attributes and Guardian file attributes...

This manual is also suitable for:

Osi/aplmgr d43

Compaq OSI/FTAM D43 User Manual

1 Introduction to the Compaq FTAM Responder

2 Conformance and Interoperatility

3 Compaq FTAM Responder Operation

4 Compaq FTAM Responder Support of ISO FTAM Functions

5 Suggestions for Development of Remote Applications

6 Responder Manager

Compaq FTAM Responder Diagnostic Messages

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Compaq OSI/FTAM D43

Summary of Contents for Compaq OSI/FTAM D43

This manual is also suitable for:

Table of Contents