Debugging the Clients

[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server for IBM z/OS >>
    Using SSH Tectia Server for IBM z/OS >>
    Configuring the Server >>
    Configuring the Client >>
    Authentication >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Examples of Use >>
        Secure File Transfers Using the z/OS Client>>
        Secure File Transfers Using Windows and Unix Clients>>
        Submitting JCL Jobs over Secure Shell
        Debugging SSH Tectia Server for IBM z/OS>>
            Debugging the Clients
            Debugging the Server
        Example of Distributing Keys >>
    Man Pages >>
    Log Messages >>

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 to 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
/*

[Contents] [Index]

[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]