Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Creating diagnostic records

&pagelevel(3)&pagelevel

If, despite due care and attention, an error occurs that neither the FT administrator nor the BS2000 system administrator can rectify, contact your Service Center. To facilitate troubleshooting, please submit the following:

  • detailed description of the error situation and statement indicating whether the error is reproducible;

  • openFT trace files, see section “Trace function”

  • if applicable the result list of the request that triggered the error

  • CONSLOG file of the entire session (also from partner system if possible)

  • general information as for BS2000 system error on openFT or the BS2000 operating system, DCAM, PLAM, SDF and, if required, openFT-FTAM, openFT-AC for BS2000, NFS and POSIX:

    1. system version number,

    2. loader - subversion number / code,

    3. list of all rep corrections used;

  • version of the FT partner and details of the transport system (e.g. DCAM, CCP / CMX, VTAM, etc.)

  • system dumps requested under the TSN FTxx or FT server tasks

  • system dumps after interrupts in the modules of the FT and FTAC subsystems

The SHOW-FT-DIAG command can be used to output any diagnostic codes written when the error occurred (together with time and date). In this case, SHOW-FT-DIAG supplies the following output:

/SH-FT-DIAG
% DATE           TIME      SSID  COMPONENT    LOCATION-ID        INFO
% 20170121       143307    FT    79/yfasdia   3/EuisyMsg         fd00000c

SHOW-FT-DIAG INF=*ALL allows additional information on the current state of openFT to be obtained. This only makes sense, however, if it is done shortly after the problem arises.