Qshell Session Takes a Long for the Prompt or Time to Start and Run Commands

[richardschoen]

If you try running a command with QSHEXEC or QSHBASH and there is a long delay, most likely it's related to this KB article from IBM

Problem
When starting an interactive Qshell session, it takes more than 30 seconds for the prompt to be displayed. The Qshell terminal session is displayed, but the shell is not ready to accept commands.

Resolving The Problem
When starting an interactive Qshell session, it takes more than 30 seconds for the prompt to be displayed. The Qshell terminal session is displayed; however, the shell is not ready to accept commands. If the WRKACTJOB is used to display the QZSHSH job, the call stack shows the gethostbyname() API near the bottom of the stack.

This problem is caused by a Domain Name System (DNS) configuration error on the system. When the shell starts, it uses the gethostbyname() API to get the IP address of the local host. It then sets the HOSTID variable to the IP address. The gethostbyname() API uses the DNS to lookup the IP address. If the DNS is not configured correctly, gethostbyname() can block waiting for a response for a DNS server.

Visit this link for a potential resolution by changing DNS search priority from *REMOTE to *LOCAL
https://www.ibm.com/support/pages/qshell-session-takes-long-prompt-or-time-start-and-run-commands