CONTENTS

  Title Page

  Copyright Page

  Preface

  1      Introduction

  1.1     Overview of the VAX FTAM Software

  1.2     Software Components of the VAX FTAM Product

  2      Solving VAX FTAM Problems

  2.1     Problem-Solving Tools
    2.1.1      OSIF Control Program (OSIFCP)
    2.1.2      Network Control Language (NCL)
    2.1.3      Tracing
    2.1.4      Event Logging
    2.1.5      Responder Log File

  2.2     VMS Environmental Conditions
    2.2.1      For All Connections
    2.2.2      For Inbound Connections

  2.3     Failure to Connect to Target SAP
    2.3.1      General Considerations
    2.3.2      Physical and Data Link
    2.3.3      Network
    2.3.4      Transport
    2.3.5      Session
    2.3.6      Presentation
    2.3.7      ACSE
    2.3.8      FTAM

  3      The VAX FTAM Tracing Utility

  3.1     Tracing Options

  3.2     Using the Tracing Utility
    3.2.1      Ensuring That the OSIFserver Is Running
    3.2.2      Setting Up Tracing
    3.2.3      Running Individual Traces
    3.2.4      Sample:  Setting Up Tracing and Running a Trace

  3.3     Using the Tracing Utility to Locate a Problem

  3.4     Automatically Tracing Inbound Connections

  3.5     Automatically Tracing DAP-FTAM Gateway Connections

  3.6     Diagnosing Failed Inbound Tracing Attempts

  3.7     Interpreting Tracing Output

  3.8     Format of Tracing Output

  3.9     Tracing Example

  4      VAX FTAM Messages

  4.1     VAX FTAM Message Formats

  4.2     VAX FTAM Messages

  A   VAX FTAM Reasons for Issuing FTAM Diagnostic Codes

  B   Problem Solving Hints

  B.1     Connection Problems
    B.1.1      X.25 Problems
    B.1.2      Transport Problems
    B.1.3      Session and Presentation Problems
    B.1.4      OSIF Alias
    B.1.5      FTAM Responder Account
    B.1.6      Different Account Problems
    B.1.7      Initiator ID and Filestore Password

  B.2     File Handling Problems
    B.2.1      Foreign Filename Formats
    B.2.2      File Problems

  C   How to Report Problems

  C.1     Preparing an SPR

  C.2     Preparing Additional Information

  EXAMPLES

  3-1        Sample Tracing Session

  FIGURES

  3-1        Relative Placement of Tracing Information in a Unit of Output

  TABLES

  3-1        Correspondence of Message Facility Codes to Tracing Equivalence Strings

  A-1        VAX FTAM Reasons for Issuing FTAM Diagnostic Codes