[Contents] [Index]

About This Document >>     Installing SSH Tectia Server for IBM z/OS >>     Getting Started with SSH Tectia Server for IBM z/OS >>     Configuring the Server >>     Configuring the Client >>     Authentication >>     Transferring Files >>     Tunneling >>     Troubleshooting SSH Tectia Server for IBM z/OS >>         Debugging SSH Tectia Server for IBM z/OS>>             Debugging the Clients             Debugging the Server         Using the OMVS Shell         Common MVS Error Messages         Common SSH Tectia Server for IBM z/OS Error Messages         Problems with the z/OS System>>         Problems with Running SSH Tectia Server for IBM z/OS>>         Problems with Logging     Advanced Information >>     Man Pages >>     Log Messages >>

Debugging the Clients

The ssh2 application can be debugged by using the -d option. The scp2 and sftp2 applications can be debugged by using -D option.

Debug level 4 is usually sufficient. For more detailed information, debug level 7 can be used.

Debugging Interactive Sessions

When using interactive sessions from OMVS, Telnet, or SSH shells, debug information is displayed on screen. Debug option is entered to the used command, for example:

> ssh2 -d 4 user@server

> sftp2 -D 7 user@server

Debugging Non-Interactive Sessions

Similar options can be entered also to JCLs. When running clients from JCL, debug information is stored in a defined STDERR file.

//STDERR DD PATH='/home/&SYSUID./scp2get_stderr', // PATHOPTS=(OWRONLY,OCREAT,OTRUNC), // PATHMODE=SIRWXU //SYSTSIN DD * BPXBATCH PGM /usr/lpp/ssh2/bin/scp2 -D 4 + -oallowedauthentications=publickey + testuser@remote_host:textfile.txt + /FTADV:F=LINE,C=ISO8859-1,D=IBM-1047/__TEST.TEXTFILE /*