Signon and IUI/API Errors

Signon errors keep you from accessing IBM® Connect:Direct®. IUI/API problems prevent you from successfully submitting a Process or executing a command.

This section describes the following types of signon and IUI/API errors:

  • ISPF signon failures can be caused by a variety of problems. Errors signing onto the IUI through the ISPF interface can include problems related to VTAM, TCP/IP, ISPF, or security. Refer to Troubleshooting Security Errors for a description of common security errors.
  • IUI/API IBM Connect:Direct session failures occur when the IUI/API cannot establish a session with the DTF. A session failure usually means you will be unable to sign on to IBM Connect:Direct.
  • SELECT command errors occur while issuing SELECT STATISTICS, SELECT PROCESS, SELECT NETMAP, SELECT USER, SELECT TYPE, and SELECT TASK commands from the IUI, batch, or operator interface.
Note: You can diagnose most IUI/API problems by running an API-to-DTF session trace. See information on the NDMCMDS trace in IBM Connect:Direct Automatic Traces.

To avoid insufficient space being allocated for the temporary data set upon signon as well as SB37 ABENDs, the administrator can define global signon defaults so that users do not have to individually alter their signon default values to increase their allocation. For more information, see Global Signon Defaults.

Condition: Signon to IUI Denied

Your signon to IUI is denied with the message Error during ACB open.

Error Cause Action Collect
SVTB002I The interactive applid that is used for signon is not active, is in an unacceptable state, or is not correctly defined to VTAM. Review both the short text and long text messages. Allocate NDMCMDS to display error messages to your terminal. NDMCMDS shows all actual commands issued to the DTF, including resolution of symbolics. It can be particularly helpful to debug IBM Connect:Direct commands through the IUI or through the batch interface if you are having signon problems, syntax errors, and so forth.
  • For Connect:Direct for z/OS®, type the following on your command line:


  • NDMCMDS output
  • Applid status display
  • Applid definitions
  • Network map

Condition: Signon to IUI Denied

Your signon to IUI is denied with the message USER attempted SIGNON with TIMEOUT=NO. Only an administrator can change the TIMEOUT value and only on their own signon panel. Non-ADMIN users cannot sign on with the inactivity timer disabled.

Note: The inactivity timer indicates the number of minutes a user can remain inactive without communicating with the DTF. This timer is active if an administrator has specified a value in the TCP.API.TIMER global initialization parameter.
Error Cause Action Collect
SAFA020I The user, who does not have administrative authority, attempted to change the TIMEOUT parameter value to NO from an IUI signon panel. Log off and log on again. Change the TIMEOUT parameter to YES to complete the signon process.
  • Statistics file

Condition: Signon to IUI Denied - No Error Message

Your attempt to sign on to the IUI is denied, but no error message is displayed.

Error Cause Action Collect
None Your TSO or TSS profile specifies the NOWTPMSG option, which inhibits some error output from being displayed to the terminal. Review both the short text and long text messages. For z/OS, change to the WTPMSG option by typing TSO PROF WTPMSG. With the WTPMSG option, error messages are displayed at the terminal. Retry the operation (sign on).
  • None

Condition: Signon Denied - IBM Connect:Direct not Active

Your signon is denied.

Error Cause Action Collect


The IBM Connect:Direct you are signing on to is not active. Review both the short text and long text messages. Ensure that IBM Connect:Direct has completed initialization before attempting a signon. Allocate NDMCMDS to display additional information about the session failure. NDMCMDS shows all actual IBM Connect:Direct commands issued to the DTF, including resolution of symbolics. It can be particularly helpful to debug IBM Connect:Direct commands through the IUI or through batch interface if you are having signon problems, syntax errors, and so forth.

For z/OS, check to see that the network map is specified correctly on the ISPF menu and that the network map is correctly loaded.

Try to sign on through the batch interface to isolate the problem.

  • NDMCMDS output
  • Network map
  • IBM Connect:Direct initialization parameters
  • For z/OS the ISR@PRIM panel

Condition: Signon Denied - Users Exceeds Limit

Signon is denied.

Error Cause Action Collect
STAA004I The number of interactive users on IBM Connect:Direct has reached the limit set in the MAXUSERS parameter. Review both the short text and long text IBM Connect:Direct messages. Check the MAXUSERS parameter in the IBM Connect:Direct initialization parameters data set. If it is commented out, the default is six users. Report this error to your IBM Connect:Direct administrator, and determine whether you need to increase the value of this parameter. If the TCP.API.TIMER is not being used, consider using this global initialization parameter to terminate orphaned sessions (some JAI users do not sign off, they just drop the connection).
  • IBM Connect:Direct initialization parameters

Condition: TCP/IP API session terminated

Users who are logged on to the DTF via TCP/IP may have their sessions dropped and see the message TCP/IP SEND error; Connection Lost. If the user presses F1 to see the help for this message, the following text is displayed for message SVTC006I:

 MSGID  ==> SVTC006I

 TCP/IP SEND error; Connection Lost

An error has been detected while sending a command via TCP/IP.
The TCP/IP connection has been lost.  A possible cause is
Connect:Direct has been shutdown and all TCP/IP connections
have been closed.

System Action: Normal processing can not continue.

Response: Logoff and attempt to signon again.

In addition, SAFA019 signoff errors are recorded in statistics along with matching user IDs and the message, TCP API session LOGOFF has been forced. To reduce the number of active sessions and stay below the limit set in the MAXUSERS global initialization parameter, the administrator can use the TCP.API.TIMER global initialization parameter to specify the maximum time of session inactivity a TCP/IP-connected IUI or API session waits before timing out and exiting. When a user has not done anything with the IUI to cause it to communicate with the DTF and the timer period expires, the DTF drops the session, and can then detect and recover lost sessions without having to be recycled.

Error Cause Action Collect


The TCP.API session has been inactive for the period specified by the TCP.API.TIMER global initialization parameter.
  • A TSO/ISPF/IUI user should log on to the DTF they lost connection with.
  • A program or system that was using the API should sign on again.
  • Statistics file–check the user and completion code (comp code) associated with the SAFA019I completion message (comp msg). On the SELECT STATISTICS screen, type Y in the CHANGE EXTENDED OPTS field and on the next screen, type SO (signoff) as a Record Type.

Condition: SELECT Command Issued Successfully - No Output Produced

The SELECT command is issued successfully and completes with a successful return code and message, but no output is produced.

Error Messages
SOPA011I SOPE000I SOPS001I      
Cause Action Collect
It is likely that IBM Connect:Direct is having trouble allocating the temporary data set that contains the output from the SELECT command. Review both the short text and long text messages. For Connect:Direct for z/OS, specify a UNIT and VOLSER for the temporary data set, and SPACE information. You can specify UNIT and VOLSER on the SIGNON DEFAULTS panel of the IUI or use the TEMPDSN parameter on your signon command for batch. Note that a UNIT type of VIO is not acceptable.
  • List of the SELECT commands that produce output and those not producing output
  • Any error messages

Condition: SELECT Commands - No Output Available

SELECT commands return with no output and a message indicating no output was available from the command.

Error Cause Action Collect


For the SELECT PROCESS and SELECT STATISTICS commands, it is likely that the userid issuing the command is defined as a general user by the stage 2 security exit, indicating that the user is only allowed to see the command output for Processes submitted by that same userid. Review both the short text and long text messages. Check to see that the userid is defined with the ability to select Process/statistics for Processes not submitted by that userid.
  • Authorization for the userid
  • Statistics file