|
|
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:
The perror function generates a message of this form:
user supplied string if any: socket library generated string
The perror message connect includes a user-supplied string, and Operation already in progress is the socket library generated string:
connect : Operation already in progress
This section lists all network perror messages.
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.
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.
Explanation An interrupt is received.
Recommended Action None.
Explanation The local network is down.
Recommended Action None.
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.
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.
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.
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.
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.
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.
Explanation An ICMP source quench is sent requesting that the service stop or reduce the transmission of IP datagrams.
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.
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.
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.
This section contains all disk perror messages.
Explanation A user requests a resource that the user does not have access to. Access is denied.
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.
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.
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.
Explanation A request is made for a data set owned by another user.
Recommended Action Retry the task later.
Explanation A request is made to read a nonexistent PDS member.
Recommended Action Retry the task asking for the correct member.
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.
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.
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.
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.
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.
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.
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.
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.
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.
This section lists other miscellaneous perror messages.
Explanation I/O error occurs with a condition code of cc.
Recommended Action Save all output from the job. Contact Customer Support.
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.
This section contains common error messages from mail.
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.
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.
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.
Explanation USMTP cannot get to a file to perform the mail service.
Recommended Action Check related messages in the WTO logs for proper response.
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.
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.
Explanation The remote host is down.
Recommended Action Check that the remote host is running and able to receive mail.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation The data transfer overflows the remote hosts buffers.
Recommended Action Retry the transfer.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation 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.
Explanation 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.
Explanation 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.
Explanation 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.
This section lists all Socket Library perror messages in alphabetical order.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
Explanation The remote destination is currently unreachable.
errno: ESDESTUNREACH
Recommended Action Determine the network problem that made the destination unreachable and then try again.
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.
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.
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
Explanation A system call is interrupted. This error message should never be issued because the error code is never set.
errno: ESINTR
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.
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.
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.
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.
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.
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.
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.
Explanation No error occurs within the socket library.
Explanation Storage cannot be allocated to complete the request.
errno: ESNOMEM
Recommended Action Determine the reason for lack of storage.
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.
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.
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.
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.
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.
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.
Explanation This error message is never generated because the error code is never set.
errno: ESPFNOSUPPORT
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.
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.
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.
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.
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.
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.
Explanation The error message should not be generated because the error code is never set.
errno: ESSOCKTNOSUPPORT
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.
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.
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.
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.
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.
|
|