Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia 
PreviousNextUp[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>>
        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 >>

Common SSH Tectia Server for IBM z/OS Error Messages

  • Environment variable '_BPXK_AUTOCVT' is not set

  • Environment variable '_BPXK_AUTOCVT' is incorrect

  • Environment variable '_CEE_RUNOPTS' is not set

  • Environment variable '_CEE_RUNOPTS' is incorrect

    These environment variables must always be set to specific values when running SSH Tectia Server for IBM z/OS programs. When running under BPXBATCH use the SSHENV dataset on a STDENV DD statement (located in /usr/lpp/ssh2/doc/zOS/SAMPLIB). Before running client programs from a USS command prompt, source the sshsetenv script (located in /usr/lpp/ssh2/doc/zOS/samples).

  • sshd2[50397305]: FATAL ERROR: setuid: EDC5157I An internal error has occurred.

  • sshd2[50397305]: FATAL: setuid: EDC5157I An internal error has occurred.

    If a login attempt ends with this error message from the server, the reason may be that the sshd2 is not marked program-controlled. You can correct this by running:

    >extattr +p /usr/lpp/ssh2/sbin/sshd2
    

PreviousNextUp[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


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more