Creating diagnostic records

For diagnostics, the following traces and information features are available:

Traces

openFT	FT-Trace	supplies information about the NEABF protocol.
GTF trace	including SVC Trace	supplies information about the progress of SVC trace execution.
VTAM	buffer trace	supplies information about data traffic between VTAM and VTAM application.
VTAM	line trace	supplies information about data traffic via the line (SDLC protocol).

Obtaining information

openFT	NSTATUS command indicates the status of requests.
VTAM	DISPLAY command indicates status of local LUs and PUs
NETVIEW	indicates the status of the network.
NETSTAT	provides information about the TCP/IP network.

If, despite due care and attention, an error occurs that neither the FT administrator nor the z/OS 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 possible, the trace files should be formatted with the FTTRACE command, and, if applicable, the FT trace from the remote FT system. Run trace to cover a longer period (>= 2 h) in order to provide sufficient time stamps and possibly connection cleardown or, in the case of reproducible errors, activate trace before reproducing the same error).

• if applicable the command call and result list of the request that triggered the error

• job list of the openFT job (also from partner system is possible)

• general information as for z/OS system error:

  • type of system (z/OS,...) and system version

  • name and version of the job entry subsystem installed (JES2, JES3, ...)

  • information about the data protection support installed with name and version (SYS1.UADS, RACF, TOP-SECRET, ACF-2, MVS router exit, openFT-AC)

  • version of the Data Facility Product (DFP) installed, if applicable

  • openFT version installed

  • complete list of openFT corrections used

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

• openFT dump files with the name
  '<openft qualifier>.<inst>.SYSFDF.Dyymmdd.Thhmmss'
  or the SYSUDUMP assigned in the FJBATCH- job

• If necessary, create an HPNS trace if problems arise with respect to TCP/IP. To do this, you must create a member DIAGPAR in the instance-specific PARM library and either restart the batch job or issue the FTUPDADDR command. See DIAGPAR member in the FT parameter library. If the diagnostic event does not itself generate an openFT dump (<inst>.SYSUDUMP) together with the associated HPNS trace then the openFT batch job must be canceled with dump output.

The output from the FTINFO command can also be of use. This only functions for inbound requests and must therefore by called at TSO level using the FTEXEC command. The partner name in this case is the local host:

FTEXEC HOSTNAME,'ftinfo -csv',(<userId>,<account>,<password>)

would output the following:

CmdUiVer;CmdTiVer;OsType;UserId;IsFtAdm;IsFtacAdm;FtLang;CcsName;Home;Limited;
IsAdmAdm;ProdVer;SrcVer;Inst;TimeOffset;FtScriptDir;NativeX25;SingleUser;Crypt
1210;0;"z/OS";"OPFTWIT";1;1;"en";"IBM1047";"OPFTWIT";*NO;0;"12.1A00";"354";"STD";
3600;"";*NO;*NO;*YES

DIAGPAR member in the FT parameter library

To allow additional diagnosis with an HPNS trace, the member DIAGPAR must be supplied with the following values in the instance-specific FT parameter library PARM:

HPNSTRACE=17825791

DIAGSTAMPS=12

If the openFT (batch job) is restarted or the FTUPDADDR command is called with these entries, additional diagnosis records on data communication are returned at the socket interface or written to the file <inst>.SYSUDUMP in the event of a dump written to the file <inst>.SYSUDUMP.

If you restart the FJBATCH job – irrespective of whether or not a dump has previously been written –, then the dump file is renamed to <inst>.SYSUDUMP.PREV. As a result, it is not deleted immediately and can be used for diagnostic purposes. This only functions if the FJBATCH job is constructed as depicted in section “openFT as a job or started task”.