perror Messages
Available Languages
Table Of Contents
Internal format error Bad fmuid length
Internal format error Bad XFROM
Internal format error No XFROM
Unexpected reply from remote SMTP
User Configuration or Subsystem Error Messages
User Configuration or Subsystem Error
Access method CVT unavailable User Configuration or Subsystem Error Access method CVT unavailable
AMODE inconsistent with AOPEN User Configuration or Subsystem Error AMODE inconsistent with AOPEN
AMTV validity check error User Configuration or Subsystem Error AMTV validity check error
APCB already closed User Configuration or Subsystem Error APCB already closed
APCB already opened User Configuration or Subsystem Error APCB already opened
APCB has permanent error User Configuration or Subsystem Error APCB has permanent error
APCB is busy User Configuration or Subsystem Error APCB is busy
APCB validity check error User Configuration or Subsystem Error APCB validity check error
API application close failed User Configuration or Subsystem Error API application close failed
API application open failed User Configuration or Subsystem Error API application open failed
Application ID too long User Configuration or Subsystem Error Application ID too long
Application ID too short User Configuration or Subsystem Error Application ID too short
Atexit error User Configuration or Subsystem Error Atexit error
Cannot establish API session User Configuration or Subsystem Error Cannot establish API session
Cannot release API session User Configuration or Subsystem Error Cannot release API session
Close timeout value too big User Configuration or Subsystem Error Close timeout value too big
Duplicate session for user User Configuration or Subsystem Error Duplicate session for user
Environment memory free error User Configuration or Subsystem Error Environment memory free error
Errno base error User Configuration or Subsystem Error Errno base error
Internal logic error User Configuration or Subsystem Error Internal logic error
Invalid access method version User Configuration or Subsystem Error Invalid access method version
Invalid option on AOPEN/ACLOSE User Configuration or Subsystem Error Invalid option on AOPEN/ACLOSE
No memory for AOPEN User Configuration or Subsystem Error No memory for AOPEN
No subsystem ID configured User Configuration or Subsystem Error No subsystem ID configured
User Configuration or Subsystem Error Password too long
Password too short User Configuration or Subsystem Error Password too short
Service ID too long User Configuration or Subsystem Error Service ID too long
Service ID too short User Configuration or Subsystem Error Service ID too short
Signal initialization failed User Configuration or Subsystem Error Signal initialization failed
Socket buffering error User Configuration or Subsystem Error Socket buffering error
Socket descriptor error User Configuration or Subsystem Error socket descriptor error
Subsystem halted User Configuration or Subsystem Error Subsystem halted
Subsystem ID too long User Configuration or Subsystem Error Subsystem ID too long
Subsystem ID too short User Configuration or Subsystem Error Subsystem ID too short
Subsystem is terminating User Configuration or Subsystem Error Subsystem is terminating
Subsystem not active User Configuration or Subsystem Error
Subsystem not activeSubsystem not configured User Configuration or Subsystem
Error Subsystem not configuredSubsystem not initialized User Configuration or Subsystem
Error Subsystem not initializedUser memory free error User Configuration or Subsystem Error
User memory free errorSocket Library perror Messages
Address family not supported by protocol family
Can't assign requested address
Can't send after socket shutdown
Network dropped connection on reset
Operation not supported on socket
Option not supported by protocol
Protocol wrong type for socket
Socket operation on non-socket
Software caused connection abort
perror Messages
This chapter contains the perror messages issued by Cisco IOS for S/390. It includes sections describing perror messages and socket library error messages.
The perror messages included in the perror module in POPEN are described in the following sections:
•
User Configuration or Subsystem Error Messages
•
Overview
The perror function generates a message of this form:
user supplied string if any: socket library generated stringThe perror message connect includes a user-supplied string, and Operation already in progress is the socket library generated string:
connect : Operation already in progressNetwork perror Messages
This section lists all network perror messages.
Bad Source Route
Explanation The option field in the IP datagram requests source routing. A list of a sequence of machines that the datagram must visit is in error.
Recommended Action If the host or an intermediate network is down, contact your proper support personnel to bring the host or network back up. If the problem is an unknown or undefined host, check that the host is in the Cisco IOS for S/390 Host Names Table. Insert a host and/or network entry if necessary and reassemble the Host Names Table. Ignore this message if the user inadvertently entered a nonexistent host.
Host Unreachable
Explanation The host is down or does not exist.
Recommended Action If the host or an intermediate network is down, contact your proper support personnel to bring the host or network back up. If the problem is an unknown or undefined host, check that the host is in the Cisco IOS for S/390 Host Names Table. Insert a host and/or network entry if necessary and reassemble the Host Names Table. Ignore this message if the user inadvertently entered a nonexistent host.
Interrupt Received
Explanation An interrupt is received.
Recommended Action None.
Local Net Down
Explanation The local network is down.
Recommended Action None.
Net Unreachable
Explanation The network requested is not reachable.
Recommended Action If the host or an intermediate network is down, contact your proper support personnel to bring the host or network back up. If the problem is an unknown or undefined host, check that the host is in the Cisco IOS for S/390 Host Names Table. Insert a host and/or network entry if necessary and reassemble the Host Names Table. Ignore this message if the user inadvertently entered a nonexistent host.
Network Timeout
Explanation A network time-out occurs.
Recommended Action Check that the network node addressed is on the network and in the Host Names Table (ARPINAMS) and APPCFGxx. Ignore this message if the network addressed does not exist on your network. Monitor these occurrences. If they continue, notify your network specialist for further analysis and identification of the offending remote host.
No Buffer Storage
Explanation The event fails due to a lack of storage.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. If there is a lot of the same kind of storage, a ptask may be looping storage. Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down and back up again. Raise the region size on the Cisco IOS for S/390 job. Retry the operation again. If the error recurs, contact Customer Support.
Port Unreachable
Explanation The requested port is unavailable at this time.
Recommended Action Check the WTO and JOB logs for related messages to discover the PORT and the host that are unavailable. Verify that the host supports the protocol the PORT is used for. List the user commands that generated this error. Start up a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Contact Customer Support.
Retransmitting
Explanation A TCP acknowledgment for a segment is not received and TCP retransmits the segment.
Recommended Action Monitor these occurrences. If they continue, notify your network specialist for further analysis and identification of the offending remote host.
Software Error!
Explanation One of the programs performing this service ABENDed.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages that may direct the correct course of action. Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down and back up again. If the error recurs, contact Customer Support.
Source Quench
Explanation An ICMP source quench is sent requesting that the service stop or reduce the transmission of IP datagrams.
TCP Conn Closed
Explanation The TCP connection is closed.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Get the list of commands entered by the user that generated this error. Start a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Contact Customer Support.
TCP Conn Reset
Explanation A condition occurs that forces the software to break the connection.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Get the list of commands entered by the user that generated this error. Start a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Contact Customer Support.
Unknown TCP Error
Explanation An unknown TCP error occurs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Get the list of commands entered by the user that generated this error.
Start a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Contact Customer Support.
Disk perror Messages
This section contains all disk perror messages.
Access control violation
Explanation A user requests a resource that the user does not have access to. Access is denied.
DAIR error
Explanation The task fails in dynamic allocation of a resource. This is an SVC99 error.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages that may direct the correct course of action. Use the DAIR code to direct your actions.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails, bring it down and back up again. If the error recurs, contact Customer Support.
Dataset not found
Explanation A request is made to read a nonexistent data set.
Recommended Action Retry the task asking for the correct data set. Check to make sure the catalog actually points to a data set. If there is no data set, fix the catalog.
DSN syntax error
Explanation A request was made for a data set name that has illegal syntax.
Recommended Action Retry the task using a valid data set name.
ENQ conflict
Explanation A request is made for a data set owned by another user.
Recommended Action Retry the task later.
Member not found
Explanation A request is made to read a nonexistent PDS member.
Recommended Action Retry the task asking for the correct member.
Not enough disk space
Explanation Either the disk does not have enough space, or the data set has reached its maximum number of extents.
Recommended Action Retry the task asking for more space or an alternate volume that has more space.
Not enough real storage
Explanation Cisco IOS for S/390 runs out of real storage.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. If there is a lot of the same kind of storage, a ptask may be allocating storage in a loop.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down and back up again. Raise the region size on the Cisco IOS for S/390 job. Retry the operation again. If the error recurs, contact Customer Support.
Not enough TIOT space
Explanation The task runs out of core for the TIOT.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. If there is a lot of the same kind of storage, a ptask may be allocating storage in a loop.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails, bring it down and back up again. Raise the region size on the Cisco IOS for S/390 job. Retry the operation again. If the error recurs, contact Customer Support.
PDYNAL/IDYNAL bug
Explanation The Cisco IOS for S/390 dynamic allocation routines ABEND. The task cannot be completed.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages that may direct the correct course of action.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails, bring it down and back up again. If the error recurs, contact Customer Support.
POPEN failed
Explanation The Cisco IOS for S/390 POPEN utility to open a dcb (or ACB) fails.
Recommended Action Check for a correct call to POPEN. Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages that may direct the correct course of action.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down and back up again. If the error recurs, contact Customer Support.
Software error
Explanation The programs performing the service ABEND. The task cannot be completed.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages that may direct the correct course of action.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down and back up again. If the error recurs, contact Customer Support.
SVC99 parm error
Explanation The task sends bad parameters to Cisco IOS for S/390 dynamic allocation routines.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages that may direct the correct course of action.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down and back up again. If the error recurs, contact Customer Support.
Unknown disk error
Explanation An unknown disk error occurs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages that may direct the correct course of action.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down and back up again. If the error recurs, contact Customer Support.
VOL/Unit unavailable
Explanation The user requests access to a disk volume or unit that is unavailable.
Recommended Action Check that the volume or unit is on-line. If the user requested a nonexistent volume or unit, ignore this message.
Other perror Messages
This section lists other miscellaneous perror messages.
I/O error cc
Explanation I/O error occurs with a condition code of cc.
Recommended Action Save all output from the job. Contact Customer Support.
No free storage!
Explanation Cisco IOS for S/390 runs out of pcore storage.
Recommended Action Increase the region size for Cisco IOS for S/390. Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages.
Retry the operation first on the current version of Cisco IOS for S/390. Retry the operation again. If it fails again, bring Cisco IOS for S/390 down and back up again. Raise the region size on the Cisco IOS for S/390 job. If the error recurs, contact Customer Support.
Mail Error Messages
This section contains common error messages from mail.
Died during transmission
Explanation The Remote host goes down during transmission.
Recommended Action Check that the remote host is running and able to receive mail. Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Get the list of commands entered by the user that generated this error.
Start a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Contact Customer Support.
Embedded file recursion
Explanation USMTP discovers a recursive unsupported service within Cisco IOS for S/390.
Recommended Action Check related messages in the logs for proper response. Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Embedded file security failed
Explanation The Mailer encounters a .f= statement specifying an invalid data set name, a data set name that is not cataloged, or the name of a file that the local security system (e.g., RACF, ACF2, CA-TOPSECRET) will not let the Mailer read.
Recommended Action Correct the data set name; verify that it is in the catalog accessible to Cisco IOS for S/390 and that the local security system provides read authority to Cisco IOS for S/390 for that file.
This mail message must have been entered from SPOOL#3 or SPOOL#4. SNDMSG now expands .f= statements itself.
Embedded file unknown
Explanation USMTP cannot get to a file to perform the mail service.
Recommended Action Check related messages in the WTO logs for proper response.
File open fail!!
Explanation Cannot open the mail file data set.
Recommended Action Check related messages in the logs for the data set name. Examine the data set. Contact Customer Support.
Header parsing error
Explanation USMTP has trouble parsing either the X-FROM or X-TO address field.
Recommended Action Check related messages in the WTO logs for the data set name. Examine the data set. Check the X-FROM and X-TO headers for errors. Contact Customer Support.
Host down
Explanation The remote host is down.
Recommended Action Check that the remote host is running and able to receive mail.
Host look up error
Explanation Cisco IOS for S/390 encounters a problem looking up the host.
Recommended Action Check the Cisco IOS for S/390 WTO logs for the mail data set name. Check that the host in the message is on the network. Save all output from the Cisco IOS for S/390 job. Get the list of commands entered by the user that generated this error.
If the problem is an unknown or undefined host, check that the host is in the Cisco IOS for S/390 Host Names Table. Insert the needed host entry if necessary and reassemble the Host Names Table. Ignore this message if the user inadvertently entered a nonexistent host.
Retry the operation. If the problem persists, contact Customer Support.
Internal format error
Explanation An error is encountered with either the X-FROM or X-TO header.
Recommended Action Check related messages in the WTO logs for the data set name. Examine the data set. Check the X-FROM and X-TO headers for errors. Contact Customer Support.
Internal format error Bad fmuid length
Explanation The userid in the X-TO field is longer than eight characters and cannot be a userid on an IBM system. This error message should appear only if the MUNGE(YES) parameter is specified on the SMTP statement in APPCFGxx.
Recommended Action Check related messages in the logs for the data set name. Examine the data set name and userid. Examine the X-TO header for errors. Contact Customer Support.
Internal format error Bad XFROM
Explanation An error is encountered with the X-FROM header.
Recommended Action Check related messages in the logs for the data set name. Examine the data set. Examine the X-FROM header for errors. Contact Customer Support.
Internal format error Bad XTO
Explanation An error is encountered with the X-TO header.
Recommended Action Check related messages in the logs for the data set name. Examine the data set and the X-TO header for errors. Contact Customer Support.
Internal format error No XFROM
Explanation No X-FROM header exists.
Recommended Action Check related messages in the logs for the data set name. Examine the data set for an X-FROM header. Contact Customer Support.
Internal format error No XTO
Explanation No X-TO header exists.
Recommended Action Check related messages in the logs for the data set name. Examine the data set for an X-TO header. Contact Customer Support.
I/O Error reading disk file!!
Explanation An I/O error occurs when USMTP tries to read the mail data set on disk.
Recommended Action Check related messages in the logs for the data set name. Examine the data set. Use ICKDSF and/or EREP to find any problems on the tracks where the mail data set is stored. Contact Customer Support.
No such mailbox
Explanation The Remote sends a 55x reply. This can indicate either bad mailbox name or that the retry errors maximum was exceeded.
Recommended Action Check to make sure that the mailbox name is on the remote host.
No user table!!
Explanation This message may be generated from either of these conditions:
•
•
Recommended Action Retry the operation. Bring Cisco IOS for S/390 down and back up again. If the error recurs, contact Customer Support.
Not local user
Explanation The remote host states that the user is not a valid user on its system.
Recommended Action Check the validity of the host and user name for the remote host.
Overflow at remote site
Explanation The data transfer overflows the remote hosts buffers.
Recommended Action Retry the transfer.
SMTP protocol error
Explanation The Remote host believes a protocol error occurred.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Get the list of commands entered by the user that generated this error.
Start a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Contact Customer Support.
Syntax error in mailbox name
Explanation The Remote host encounters an error in the mailbox name.
Recommended Action Check other messages in the logs for related messages. Make sure that the mail message specifies a valid mailbox name.
TCP connection refused
Explanation The remote host refuses to accept a session with Cisco IOS for S/390.
Recommended Action Check the error logs for related messages. Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Get the list of commands entered by the user that generated this error.
Start a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Contact Customer Support.
Truncated spool file
Explanation The mail file data set is incomplete. A premature end-of-file condition occurred.
Recommended Action Check related messages in the logs for the data set name. Examine the data set. Contact your proper support personnel or Customer Support.
Unexpected reply from remote SMTP
Explanation The Remote host sends an unexpected reply to Cisco IOS for S/390.
Recommended Action Check related messages in the logs for proper response. Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Get the list of commands entered by the user that generated this error.
Start a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Contact Customer Support.
Unknown host
Explanation The Remote host is unknown.
Recommended Action Save all output from the Cisco IOS for S/390 job. Get the list of commands entered by the user that generated this error.
If the problem is an unknown or undefined host, check that the host is in the Cisco IOS for S/390 Host Names Table. Insert the needed host entry if necessary and reassemble the Host Names Table. Ignore this message if the user inadvertently entered a nonexistent host.
Retry the operation. If the problem persists, contact Customer Support.
User Configuration or Subsystem Error Messages
This section lists all the messages that might occur as subclasses to the main message, User Configuration or Subsystem Error. Messages are listed beginning with the most general message.
User Configuration or Subsystem Error
Explanation This error message is generated when a user issues a socket() function call and either the socket configuration is invalid or the socket library encounters a problem when trying to establish a session on behalf of the user with the API. This error message may be followed by another line that provides more insight into the exact cause of the problem. This extra line is generated if the sockcfg.flags element of the socket configuration structure has the EXTERRNOMSG bit set.
errno: ESCONFIG
Recommended Action Set the EXTERRNOMSG bit on in the socket configuration and rerun the program. A more descriptive error message should then be generated and the action listed under that message taken.
Access method CVT unavailable User Configuration or Subsystem Error Access method CVT unavailable
Explanation The access method CVT is unavailable at AOPEN time.
errno: ESCONFIG / EAPCBECVT
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
AMODE inconsistent with AOPEN User Configuration or Subsystem Error AMODE inconsistent with AOPEN
Explanation The address mode has changed between the time the AOPEN was issued and the time the ACLOSE was issued by the socket library to the API.
errno: ESCONFIG / EAPCBEAMD
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
AMTV validity check error User Configuration or Subsystem Error AMTV validity check error
Explanation The access method transfer vector causes an error at either AOPEN or ACLOSE time.
errno: ESCONFIG / EAPCBETRV
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
AOPEN/ACLOSE not issued from PRB User Configuration or Subsystem Error AOPEN/ACLOSE not issued from PRB
Explanation The AOPEN issued by the socket library is done when the socket library is not running under a PRB.
errno: ESCONFIG / EAPCBEPRB
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
APCB already closed User Configuration or Subsystem Error APCB already closed
Explanation The APCB issued on the ACLOSE by the socket library to the API is already marked as closed by the API.
errno: ESCONFIG / EAPCBECLS
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
APCB already opened User Configuration or Subsystem Error APCB already opened
Explanation The APCB used by the socket library to open a user session with the API is listed as open by the API.
errno: ESCONFIG / EAPCBEOPN
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
APCB has permanent error User Configuration or Subsystem Error APCB has permanent error
Explanation The APCB used by the socket library to initiate and terminate a user session with the API has been marked with a permanent error by the API.
errno: ESCONFIG / EAPCBEPER
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
APCB is busy User Configuration or Subsystem Error APCB is busy
Explanation The APCB used by the socket library to initiate and terminate user sessions with the API is detected busy by the API at either AOPEN or ACLOSE time.
errno: ESCONFIG / EAPCBEBSY
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
APCB validity check error User Configuration or Subsystem Error APCB validity check error
Explanation The APCB used by the socket library to perform an AOPEN to the API is invalid.
errno: ESCONFIG / EAPCBEVCK
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
API application close failed User Configuration or Subsystem Error API application close failed
Explanation During socket library termination, the ACLOSE issued to the API fails for an unspecified error.
errno: ESCONFIG / EACLOSEFAILED
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
API application open failed User Configuration or Subsystem Error API application open failed
Explanation When opening a session with the API, the socket library encounters an error about which it cannot be more specific.
errno: ESCONFIG / EAOPENFAILED
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
Application ID too long User Configuration or Subsystem Error Application ID too long
Explanation The user's socket configuration specifies an application ID that contains more than 8 characters.
errno: ESCONFIG / EAPPLIDTOOLONG
Recommended Action Correct the application ID parameters of the socket configuration, recompile it, and relink the application.
Application ID too short User Configuration or Subsystem Error Application ID too short
Explanation The user's socket configuration specifies an application ID to be used on the opening of the user's session with the API subsystem that had 0 characters.
errno: ESCONFIG / EAPPLIDTOOSHORT
Recommended Action Correct the application ID parameters of the socket configuration, recompile it, and relink the application.
Atexit error User Configuration or Subsystem Error Atexit error
Explanation The user's socket configuration has an error with the library termination exit function.
errno: ESCONFIG / EEXITERROR
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application.
Cannot establish API session User Configuration or Subsystem Error Cannot establish API session
Explanation The socket library cannot establish a user session with the API for an unknown reason.
errno: ESCONFIG / EAPCBEBEG
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
Cannot initialize user environment User Configuration or Subsystem Error Cannot initialize user environment
Explanation The API cannot initialize the user environment at AOPEN time.
errno: ESCONFIG / EAPCBEENV
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
Cannot release API session User Configuration or Subsystem Error Cannot release API session
Explanation At socket library termination time, the user session cannot be closed due to an internal error with the API.
errno: ESCONFIG / EAPCBEEND
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
Close timeout value too big User Configuration or Subsystem Error Close timeout value too big
Explanation The close time-out value of the socket library's configuration is invalid.
errno: ESCONFIG / ECLOSETIMEOUT
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application.
Duplicate session for user User Configuration or Subsystem Error Duplicate session for user
Explanation A duplicate user session with the API is detected when the socket library issues an AOPEN to the API.
errno: ESCONFIG / EAPCBEDUP
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
Environment memory free error User Configuration or Subsystem Error Environment memory free error
Explanation During socket library termination the socket library receives an error when trying to free storage that it had allocated.
errno: ESCONFIG / EENVRFREE
Recommended Action Determine the proper operation of the C runtime library.
Errno base error User Configuration or Subsystem Error Errno base error
Explanation The user's socket configuration has an error with the errno base value.
errno: ESCONFIG / EERRNOBASE
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application.
Internal logic error User Configuration or Subsystem Error Internal logic error
Explanation The API encounters an internal logic error while attempting to complete the AOPEN issued by the socket library to initiate a user session with the API.
errno: ESCONFIG / EAPCBELER
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
Invalid access method version User Configuration or Subsystem Error Invalid access method version
Explanation The version number of the APCB is not the same as the API.
errno: ESCONFIG / EAPCBEVER
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
Invalid option on AOPEN/ACLOSE User Configuration or Subsystem Error Invalid option on AOPEN/ACLOSE
Explanation The option field of the APCB is invalid when the socket library issues the AOPEN to the API.
errno: ESCONFIG / EAPCBEOPT
Recommended Action Review the installation procedure of the socket library. Particular attention should be paid to the socket configuration variable that the socket library stuffs into the APCB on the AOPEN. Correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, verify the proper operation of the API and Cisco IOS for S/390.
No memory for AOPEN User Configuration or Subsystem Error No memory for AOPEN
Explanation The API lacks the proper amount of storage to initiate another user session.
errno: ESCONFIG / EAPCBEMEM
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, the user should verify the proper operation of the API and Cisco IOS for S/390.
No memory for environment initialization User Configuration or Subsystem Error No memory for
environment initializationExplanation During socket initialization the socket library cannot allocate storage for its environment initialization routine.
errno: ESCONFIG / EENVRALLOC
Recommended Action Try to find out why there is a shortage of storage.
No memory for user initialization User Configuration or Subsystem Error No memory for user initialization
Explanation During socket library initialization, the socket library cannot allocate enough storage to initialize properly.
errno: ESCONFIG / EUSERALLOC
Recommended Action Try to find out why there is a shortage of storage.
No subsystem ID configured User Configuration or Subsystem Error No subsystem ID configured
Explanation The user's socket configuration does not specify a subsystem ID to be used when opening a session with the assembler API subsystem.
errno: ESCONFIG / ENOSUBSYSID
Recommended Action Correct the subsystem ID parameter of the socket configuration, recompile it, and relink the application.
Password too long
User Configuration or Subsystem Error Password too long
Explanation The user's socket configuration specifies an application password that contains more than eight characters.
errno: ESCONFIG / EPASSWDTOOLONG
Recommended Action Correct the application password parameters of the socket configuration, recompile it, and relink the application.
Password too short User Configuration or Subsystem Error Password too short
Explanation The user's socket configuration specifies an application password that contains zero characters.
errno: ESCONFIG / EPASSWDTOOSHORT
Recommended Action Correct the application password parameter of the socket configuration, recompile it, and relink the application.
Service ID too long User Configuration or Subsystem Error Service ID too long
Explanation The user's socket configuration specifies a service ID that is greater than 8 characters.
errno: ESCONFIG / ESVCIDTOOLONG
Recommended Action Correct the service ID parameters of the socket configuration, recompile it, and relink the application.
Service ID too short User Configuration or Subsystem Error Service ID too short
Explanation The user's socket configuration specifies a service ID of 0 bytes.
errno: ESCONFIG / ESVCIDTOOSHORT
Recommended Action Correct the service ID parameters of the socket configuration, recompile it, and relink the application.
Signal initialization failed User Configuration or Subsystem Error Signal initialization failed
Explanation The signal parameters of the socket configuration are invalid.
errno: ESCONFIG / ESIGNAL
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application.
Socket buffering error User Configuration or Subsystem Error Socket buffering error
Explanation The user's socket configuration has an invalid setting in the buffering configuration parameters.
errno: ESCONFIG / EBUFFERVALUES
Recommended Action Review the installation procedure of the socket library, correct any configuration information with the socket configuration, recompile it, and relink the application.
Socket descriptor error User Configuration or Subsystem Error socket descriptor error
Explanation The user's socket configuration has an invalid setting dealing with the assignment of socket descriptors.
errno: ESCONFIG / ESOCKETVALUES
Recommended Action Review the installation procedure of the socket library, make any necessary corrections to the socket configuration, recompile it, and relink the application.
Subsystem halted User Configuration or Subsystem Error Subsystem halted
Explanation The API subsystem is halted for some reason.
errno: ESCONFIG / EAPCBEHLT
Recommended Action Investigate the reason the API is halted and retry the program once it has been restarted.
Subsystem ID too long User Configuration or Subsystem Error Subsystem ID too long
Explanation The user's socket configuration specifies a subsystem ID of more than 4 bytes to be used when opening a session with the assembler API subsystem.
errno: ESCONFIG / ESUBSYSIDTOOLONG
Recommended Action Correct the subsystem ID parameter of the socket configuration, recompile it, and relink the application.
Subsystem ID too short User Configuration or Subsystem Error Subsystem ID too short
Explanation The user's socket configuration specifies a subsystem ID of zero bytes to be used when opening a session with the assembler API subsystem.
errno: ESCONFIG / ESUBSYSIDTOOSHORT
Recommended Action Correct the subsystem ID parameter of the socket configuration, recompile it, and relink the application.
Subsystem is terminating User Configuration or Subsystem Error Subsystem is terminating
Explanation The API subsystem is terminating execution. No more users can open sessions with it.
errno: ESCONFIG / EAPCBTERM
Recommended Action Determine why the API is terminating and then retry the program once it is running again.
Subsystem not active User Configuration or Subsystem Error
Subsystem not activeExplanation The subsystem of the API is not active.
errno: ESCONFIG / EAPCBEACT
Recommended Action Have the operations personnel start the API and Cisco IOS for S/390.
Subsystem not configured User Configuration or Subsystem
Error Subsystem not configuredExplanation The subsystem of the API is not configured.
errno: ESCONFIG / EAPCBCFG
Recommended Action Review the installation procedure of the socket library. Pay particular attention to the subsystem ID. Correct any configuration information with the socket configuration, recompile it, and relink the application. If no configuration errors are found, verify the proper operation of the API and Cisco IOS for S/390.
Subsystem not initialized User Configuration or Subsystem
Error Subsystem not initializedExplanation The subsystem of the API and Cisco IOS for S/390 is not initialized at the current time.
errno: ESCONFIG / EAPCBERDY
Recommended Action Verify that the API is running and has properly initialized before retrying the program.
User memory free error User Configuration or Subsystem Error
User memory free errorExplanation At socket library termination, the socket library encounters an error when trying to free storage that it had allocated.
errno: ESCONFIG / EUSERFREE
Recommended Action Verify that the C runtime library is functioning properly.
Socket Library perror Messages
This section lists all Socket Library perror messages in alphabetical order.
Address already in use
Explanation The user requests that a particular port number be used locally but this port is being used by another.
errno: ESADDRINUSE
Recommended Action Select another port number or try again later.
Address family not supported by protocol family
Explanation The socket user issues a call that requires a socket name but specifies a socket domain other than AF_INET.
errno: ESAFNOSUPPORT
Recommended Action Ensure that the domain of a socket name specifies AF_INET.
Bad address
Explanation The user passed a pointer to the socket library that points to an area of storage that cannot be accessed by the socket library.
errno: ESFAULT
Recommended Action Verify that the pointer(s) used on the socket function call are valid.
Bad socket number
Explanation A socket call is issued by the user specifying a socket descriptor that is not active. All socket functions have as their first argument the socket descriptor. The socket descriptor is the small integer returned by the socket function.
errno: ESBADF
Recommended Action Ensure that a proper socket descriptor is being passed when this call is issued.
Broken pipe
Explanation A socket that has had its transmit simplex shutdown has had a write request of some form issued to it. Write requests include send(), sendto(), sendmsg(), write(), and writev().
errno: ESKPIPE
Recommended Action Change this programming tactic.
Can't assign requested address
Explanation The name passed by a user to the socket library is invalid. Typically either the port is 0 or the address equals INADDR_ANY.
errno: ESADDRNOTAVAIL
Recommended Action Verify that a valid socket name is being passed to the failing function.
Can't send after socket shutdown
Explanation After shutting down a socket, the user attempts to transfer data. This error message is generated because the error code is never set by the socket library.
errno: ESSHUTDOWN
Connection refused
Explanation The connect request initiated by a connect() function call is refused by the remote system.
errno: ESCONNREFUSED
Recommended Action Verify that the connect request is formatted properly and if the failure still occurs, verify that the remote system is functioning properly.
Connection reset by peer
Explanation The remote endpoint reset the connection for some unknown reason.
errno: ESCONNRESET
Recommended Action Check the remote system and then try to solve the problem.
Connection timed out
Explanation The connection has timed out. The socket should be closed and then recreated and the connection re-established.
errno: ESTIMEDOUT
Recommended Action Close the socket and then reopen it and re-establish the connection.
Destination address required
Explanation A send request of some form is issued on a socket operating in connectionless mode but the user does not pass the socket library the name of the remote endpoint to send the data to.
errno: ESDESTADDRREQ
Recommended Action Either use a connection or association-base socket or ensure that either the function sendto() or sendmsg() be used and a name of the remote endpoint specified.
Destination unreachable
Explanation The remote destination is currently unreachable.
errno: ESDESTUNREACH
Recommended Action Determine the network problem that made the destination unreachable and then try again.
Host is down
Explanation The remote host to which the user is trying to establish a connection or transfer data to and from is not currently operating on the network. This error message is generated because the error code is never set.
errno: ESHOSTDOWN
Recommended Action Wait for the system to become operational.
Host is unreachable
Explanation The remote host of a connection or the remote host to which data is being transferred is unreachable.
errno: ESHOSTUNREACH
Recommended Action Ensure this is the case and then wait for the remote system to become reachable via the network.
I/O error
Explanation A socket call encounters an I/O error. This error message should never be generated because the error code is never set.
errno: ESIO
Interrupted system call
Explanation A system call is interrupted. This error message should never be issued because the error code is never set.
errno: ESINTR
Invalid argument
Explanation This error message is generated for a number of reasons. The reasons are listed in the Cisco IOS for S/390 Assembler API Macro Reference in the section covering each function.
errno: ESINVAL
Recommended Action Find out which socket function is being called at the time of the error and refer to the Cisco IOS for S/390 Assembler API Macro Reference for specific information.
Message too long
Explanation The user issues a send request of some form on a socket that maintains message boundaries but the length of the message exceeds either the maximum allowable message or the maximum allowable message based on the current buffer space allocations.
errno: ESMSGSIZE
Recommended Action Either decrease the size of the send request or, if buffer allocations are the restricting factor, increase buffer allocation.
Network dropped connection on reset
Explanation A network problem forces the connection to the remote endpoint to be terminated. This error message is never generated because the error code is not set by the socket library.
errno: ESNETRESET
Recommended Action Determine the problem with the network and retry.
Network flow control
Explanation The network is congested and the local user should slow his transmission rate to help alleviate the congestion.
errno: ESNETOVRRUN
Recommended Action Adjust the data transmission rate to lessen network congestion.
Network is down
Explanation The local network interface is not operational. This error message is never generated because the error code is not set by the socket library.
errno: ESNETDOWN
Recommended Action The local network interface must be placed on-line and a retry initiated.
Network is unreachable
Explanation The remote endpoint cannot be reached because the remote network is unreachable. This error message is never generated because the error code is not set by the socket library.
errno: ESNETUNREACH
Recommended Action Check that correct remote endpoint is being used; if so, try to find out why the remote network is unreachable.
No buffer space available
Explanation The function called cannot acquire the proper amount of buffer space necessary to complete execution of the request. The request is aborted abnormally.
errno: ESNOBUFS
Recommended Action Try to determine the reason for a lack of storage. This type of problem may be caused by a piece of software that is allocating storage and never freeing it.
No error
Explanation No error occurs within the socket library.
Not enough memory
Explanation Storage cannot be allocated to complete the request.
errno: ESNOMEM
Recommended Action Determine the reason for lack of storage.
Operation already in progress
Explanation The user issues a call to the socket library of a type that the socket is trying to complete on a previous call.
errno: ESALREADY
Recommended Action Wait, using select(), to determine when it is proper to issue another call of this type.
Operation not supported on socket
Explanation The user issues a socket function that is not supported by this type of socket. Cases of this error are issuing a listen(), accept(), or connect() function on a connectionless socket.
errno: ESOPNOTSUPP
Recommended Action The socket user should determine the type of socket being used and verify that the proper functions are being issued to it.
Operation now in progress
Explanation A request issued to the socket library has been initiated by the library and the user can determine when it is complete by using the select() function call.
errno: ESINPROGRESS
Recommended Action The user can issue a select() call to determine when the request has completed.
Operation would block
Explanation An operation requested on a socket that has had the nonblocking I/O option set would block the caller until some network related event occurs.
errno: ESWOULDBLOCK
Recommended Action This is more a warning than an error. Issue the request at some later time. Depending on the request, the user can issue a select() function call to determine when this time is.
Option not supported by protocol
Explanation The selected option for a setsockopt() or getsockopt() function call is not supported by the protocol layers. This message should not be generated because the error code is not currently set by the socket library.
errno: ESNOPROTOOPT
Recommended Action Verify that the proper options are being passed to this function.
Permission denied
Explanation The user does not have the proper authorization to make the request.
errno: ESACCESS
Recommended Action Determine the authorization to use the resource and then retry.
Protocol family not supported
Explanation This error message is never generated because the error code is never set.
errno: ESPFNOSUPPORT
Protocol not supported
Explanation The user issues a socket() and specifies a socket type that is not supported.
errno: ESPROTONOSUPPORT
Recommended Action Verify that the proper arguments are being passed to the socket() function.
Protocol wrong type for socket
Explanation The user issues a socket() function specifying both a socket type and a protocol to use. No support for a socket of this type is allowed.
errno: ESPROTOTYPE
Recommended Action Determine the correct settings for the arguments to the socket() function.
Socket is already connected
Explanation The user tries to issue a connect() function call on a socket that is already connected or to transfer data on a connected or associated socket and the user passes a name to send the data to.
errno: ESISCONN
Recommended Action Ensure that the user application is issuing the connect or send request on the proper socket.
Socket is not connected
Explanation The user tries to transfer data on a socket that requires connections but has not yet been connected.
errno: ESNOTCONN
Recommended Action First issue a connect() function call and then transfer data.
Socket operation on non-socket
Explanation The user issues a request on a file descriptor when the request can only be performed on a socket. This message should never be generated.
errno: ESNOTSOCK
Recommended Action Verify that the proper file or socket descriptor is being used.
Socket table overflow
Explanation The user has too many open sockets at the present time.
errno: ESNFILE
Recommended Action Close some of the sockets or modify the socket configuration to allow more sockets per user.
Socket type not supported
Explanation The error message should not be generated because the error code is never set.
errno: ESSOCKTNOSUPPORT
Software caused connection abort
Explanation The connection was aborted by either the local or remote endpoint.
errno: ESCONNABORTED
Recommended Action If this error persists the user should verify the proper operation of Cisco IOS for S/390 and the remote system that is being used.
System Related Error
Explanation This error is generated if the API or Cisco IOS for S/390 is stopped or terminated when a program using sockets is being executed. It may also be caused if the assembler API returns an error code to the socket library for which the socket library is not prepared.
errno: ESSYS
Recommended Action First determine that the API and Cisco IOS for S/390 are still functioning. If this is so and the error occurs repeatedly, contact Customer Support.
Too many open sockets
Explanation The user has too many open sockets at the present time.
errno: ESMFILE
Recommended Action Close some of the sockets or modify the socket configuration to allow more sockets per user.
Transport provider ended
Explanation The Cisco IOS for S/390 subsystem has been stopped by an operator command or has terminated abnormally.
errno: ESTPEND
Recommended Action The socketterm() function should be called to close all open sockets.
API ended
Explanation The API has been stopped by an operator command or has terminated abnormally.
errno: ESAPEND
Recommended Action The socketterm() function should be called to close all open sockets.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)
This Document Applies to These Products
- Collaboration Endpoints - Retired Products
- Conferencing - Retired Products
- Contact Center - Retired Products
- Optical Networking - Retired Products
- Routers - Retired Products
- Security - Retired Products
- Servers - Unified Computing (UCS) Retired Products
- Storage Networking Retired Products
- Switches - Retired Products
- Video - Retired Products
- Wireless - Retired Products