SSH Tectia  
Previous Next Up [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 Server

The server can be debugged by using either the -d or -D option.

The -d option launches the server to one-shot mode. In this mode, the server accepts only one connection and exits after the session is disconnected. The server does not spawn a separate task for the connection.

The -D option launches the server to continuous debug mode. In this mode, the server keeps on listening to the TCP port and accepts several connections. The server spawns new task for each new connection and needs to be stopped manually when you want to finish the debugging.

The debug level is either a number, or a comma-separated list of assignments of the format ModulePattern=debug_level, for example "*=7,sshd2=2". Debug level 4 is usually sufficient. For more detailed information, debug level 7 can be used.

Debugging Using USS shell

When debugging the server, a second server daemon can be started to a different TCP port or alternatively the existing server can be stopped and the same port can be used for debugging.

Debugging can be started with the following command (run as the SSHD2 user):

> /etc/ssh2/init.d/ssh2 start foreground -d 4 -p 1234

In the command, -d defines the debug level and -p the TCP port. With this command the debug output is displayed to the screen.

Debug can also be forwarded to a file:

> /etc/ssh2/init.d/sshd2 start foreground -d 4 -p 1234 >/tmp/sshd2_debug.out 2>&1

Debugging for the SFTP server subsystem can be controlled with the SSH_SFTP_DEBUG and SSH_SFTP_DEBUG_FILE environment variables. SSH_SFTP_DEBUG defines the debug level for the file transfer server. SSH_SFTP_DEBUG_FILE defines the output file for the debug messages.

Debugging using a Started Task

The -D option can be used on the SSHD2 started task. Output is stored in the defined STDERR file.

//RUNSSHD2D PROC
//SSHD2   EXEC PGM=BPXBATCH,REGION=0M,TIME=NOLIMIT,
//             PARM='PGM /bin/sh /etc/ssh2/init.d/sshd2
//             start foreground -D 7'
//STDOUT   DD  PATH='/tmp/SSHD2-sshd2.out',
//             PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
//             PATHMODE=(SIRUSR,SIWUSR)
//STDERR   DD  PATH='/tmp/SSHD2-sshd2.err',
//             PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
//             PATHMODE=(SIRUSR,SIWUSR)
//STDIN    DD  DUMMY
//        PEND

Previous Next Up [Contents] [Index]


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

Copyright © 2007 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice