IBM i Access for Linux

Installation and usage guide

iSeries Access Communication Error Messages


 
  • - CWBCO1001

    Cause
    iSeries Access could not start or could not access the TCP/IP communications provider on your personal computer. Either the communications provider is not installed, or is no longer in a usable state.

    Recovery
    The provider must be BSD sockets compatible.
    Install or re-install the TCP/IP communications provider and verify that it is working correctly.


  •  - CWBCO1002

    Cause
    The level of communications provider found is not supported by or compatible with iSeries Access.

    Recovery
    Use a communications provider that is supported for use with iSeries Access. The provider must be BSD sockets compatible.


  •  - CWBCO1003

    Cause
    An error occurred during communications. The name of the function that failed, if available, and its error code are specified.

    Recovery
    Check the list below for the error code specified in the message and take the action specified. If the function and/or error code in the message are not listed here, they may be listed in Informational APAR II10598 along with cause and recovery information.

    Error codes (for all functions)

    8405 - The connection was initially established, but was disconnected by the server application before communications were completed. See message CWBCO1047 for additional information.

    8411 - The connection attempt did not complete before the user configured timeout expired. The timeout can occur while querying the IP address or making the initial connection attempt to the server. See Server Connection Properties for information on configuring the connection to the server. See message CWBCO1051 for additional information.

    8413 - A user configurable time-out occurred during a send or receive attempt. See message CWBCO1054.

    11001, 11002, 11003 - The server name was not found during TCP/IP address lookup. Verify the server name entered is correct. Verify the TCP/IP settings are correct for resolving addresses. See message CWBCO1004 for additional help. See Server Connection Properties for information on changing the IP address and mode.

    11004 - The iSeries service name was not found in the local SERVICES file. Verify the required iSeries service names are correctly entered in the local SERVICES file.

    Port numbers for host servers and server mapper:

    Service Name Description Port Number Subsystem Daemon Server
    as-central Central server 8470 QSYSWRK QZSCSRVSD QZDASOINIT and QZSCSRVS
    as-database Database server 8471 QSERVER QZDASRVSD QZDASOINIT and QTFPJTCP
    as-dtaq Data queue server 8472 QSYSWRK QZHQSRVD QZHQSSRV
    as-file File server 8473 QSERVER QPWFSERVSD QNPSERVS and QIWVPPJT
    as-netprt Network print server 8474 QSYSWRK QNPSERVD QNPSERVS and QIWVPPJT
    as-rmtcmd Remote command / Program call server 8475 QSYSWRK QZRCSRVSD QZRCSRVS
    as-signon Signon server 8476 QSYSWRK QZSOSGND QZSOSIGN
    as-svrmap Server mapper 449 QSYSWRK QZSOSMAPD n/a
    drda DDM 446 QSYSWRK QRWTLSTN QRWTSRVR
    as-usf Ultimedia Facilities 8480 QSYSWRK QUMBDMN QUMBPJTC
    as-admin-http HTTP Administration 2001 QHTTPSVR n/a all within QHTTPSVR subsystem
    as-mtgtctrl Management Central 5555 QSYSWRK n/a QYPSSRV
    telnet Telnet server 23 QSYSWRK n/a QTVTELNET and QTVDEVICE

    See Server Connection Properties for information on changing the port mode.

    10014, 10022 - The TCP/IP provider has detected an invalid argument. This can happen when the connection terminates and invalidates its resources before notifying the calling application. Try re-connecting to the server, then try the action again.

    10050, 10051 - The network is down or unreachable. Check your local and remote network settings.

    10048 - The local socket address and port are already in use. Restart the application and try again.

    10050, 10051, 10064, 10065 - No route to the server was found. Check your TCP/IP address and configuration. There may also be a network problem.

    10052 - The server you were connected to somehow lost the knowledge of the connection, possibly due to a network failure or a "keep-alive" activity timeout. Try re-connecting to the server, then try the action again.

    10053 - The connection was established, but was broken by the client TCP/IP communications provider. Try re-connecting to the server, then try the action again.

    10054 - See 8405 above.

    10055, 10067 - The TCP/IP provider has run out of resources to process your request. Your PC system may be too low on available memory, or you may have too many programs that use TCP/IP running. End any unnecessary programs and try the action again. If this error still occurs, shutdown and re-start your pc, and try the action again with as few other programs active as possible.

    10057, 10058 - A request to send or receive failed because the socket had already been closed.

    10060, 10064 - The address used for the server was found, but the connection to the server timed out. See CWBCO1048 for additional information.

    10061 - The server was contacted, but refused the connection request. See CWBCO1049 for additional information.

    10107 - The TCP/IP provider received a failure from an operating system call that should never fail. Check to make sure you have the latest operating system service pack installed.

    Any other
    Ask your systems administrator to verify that the host servers are running on the iSeries server, and look for messages logged on the server that might indicate a network or other problem. If there are routers in the network between your personal computer and the server, the problem may be related to router configuration or operation. Check for general network problems.


  •  - CWBCO1004

    Cause
    iSeries Access could not determine the IP address for the server.

    Recovery
    If you use a Domain Name Server (DNS), contact your network administrator to verify that the DNS is operational. You can determine if your PC can communicate with the DNS by using the 'ping' utility that comes with the TCP/IP communications support you installed on your PC.
    If you rely on the file on your PC called 'HOSTS' for IP address resolution, verify that an entry exists in that file for the server you are trying to connect to. For example, if the server name is SYSA and its IP address is 4.5.6.7, for address resolution using the HOSTS file to work, the following entry must exist in the HOSTS file:
    4.5.6.7 SYSA
    If an entry for the server exists in the HOSTS file, but the ping utility fails to contact the server and tells you the system name you entered is an invalid IP address, the cause of failure may be invalid characters in the system name. Which characters are valid in a system name may vary from one TCP/IP implementation to another. Try using a system name containing only letters ('a'-'z' and 'A'-'Z'), numbers ('0'-'9'), dashes ('-') and periods ('.'). Add a new entry to the HOSTS file using the new system name, and if the ping program can contact the server using that system name, iSeries Access should no longer fail with this message.
    If you are not using either DNS or a HOSTS file for IP address resolution, but do have a connection to the server configured in iSeries Access, verify that the IP address field in the Properties for that system's connection is correct. Also, verify that the IP Address lookup mode is NEVER.
    See Server Connection Properties for information on changing the IP address and mode.


  •  - CWBCO1006

    Cause
    Connecting to the Service Mapper on the server failed.

    Recovery
    Ensure that the TCP/IP host servers on the iSeries server are started and see help for previous communications-related messages.
    For information on starting host servers, see How to Start OS/400Host Socket Servers.


  •  - CWBCO1007

    Cause
    The Service Mapper on the server was found and contacted. However, the port number to use for connecting to the specified host server was not successfully retrieved from the Service Mapper.

    Recovery
    Notify your system administrator of this message. The existence of an entry for the server application in the service table on the server must be verified. If this entry is missing, it can be re-entered, or Option 12 (Host Servers) can be re-installed on the server.


  •  - CWBCO1008

    Cause
    The Service Mapper was successfully contacted on the server, but connecting to the specified application server on that server failed, probably because the host server is not running. The error code is specified.

    Recovery
    Verify that the host server is ready to receive connections by doing the following on the server:

    1. Enter the NETSTAT command.
    2. Select option 3, Work with TCP/IP connection status.
    3. Search for an entry for which the Local Port is the name of the server application specified in the message. This name may be truncated for display in NETSTAT.
    4. Press F14 (Display port numbers) and note what port number that server is using; also note what the state of the server is.

    * If the entry exists but the port number shown is different from the one listed in the CWBCO1022 message text, then either the iSeries Access configuration for the system specifies to lookup the remote port on the PC, or the services table on the server is incorrect. Have your systems administrator verify that the entry for the specified host server is correct. See Server Connection Properties for information on configuring the connection to the server.

    * If there is no such entry, or if the State listed for the entry is not Listen, the server application is not ready to accept connections; see How to Start OS/400 Host Socket Servers. You may have to stop and restart the host socket servers.

    * If the entry exists and the state is Listen, there may be a problem related to one or more routers in your network not allowing connections to be made through them. Contact your system administrator for assistance.

    See CWBCO1003 for details on the error code specified.


  •  - CWBCO1009

    Cause
    This message displays the name of the TCP/IP provider in use on your PC.

    Recovery
    If you expected a different TCP/IP provider, contact whoever is responsible for installing and configuring software on your PC for assistance.


  •  - CWBCO1010

    Cause
    The server's IP address could not be resolved.

    Recovery
    See message CWBCO1004 for recovery methods to solve this problem.
    Check previous messages for details.


  •  - CWBCO1011

    Cause
    The remote server port could not be resolved

    Recovery
    See Server Connection Properties for information on changing the remote server port.
    Check previous messages for details.


  •  - CWBCO1014

    Cause
    The attempt to connect to the specified host server application on the specified server failed. Since this host server application is not necessary to complete a iSeries Access connection, this failure is a warning only. Although a iSeries Access connection does not require that the specified host server application be running, some iSeries Access functions do; those functions will not work until connecting to the host server application succeeds.
    For example, if the host server application as-database cannot be connected to, iSeries Access data transfer and ODBC functions will not work.

    Recovery
    See How to Start OS/400 Host Socket Servers
    See previous messages for recovery information.


  •  - CWBCO1015

    Cause
    At least one failure occurred when trying to connect to a host server application on the server. A connection may be established, but some iSeries Access functions will not work.

    Recovery
    See earlier messages related to the connection failures for recovery information.


  •  - CWBCO1016

    Cause
    At least one failure occurred during the connection verification that will prevent an iSeries Access connection from succeeding.

    Recovery
    See earlier messages for recovery information.


  •  - CWBCO1017

    Cause
    The connection verification was canceled, either by the user or by the PC operating system, before it completed. No determination was made of whether a iSeries Access connection to server will succeed.

    Recovery
    To verify the connection, retry the operation without canceling. If the connection verification seemed to take much too long to complete (and so was canceled), it is likely that there is a configuration problem. Have your network administrator help you determine if communications are correctly configured on your PC system and on the server, and whether or not there are any network problems.


  •  - CWBCO1018

    Cause
    The server you are verifying a connection to is running an OS/400 release older than V4R2M0. Most functions of iSeries Access will not work correctly or at all when running to such a server.

    Recovery
    Connect to a server running OS/400 release V4R2M0 or later, or upgrade the level of OS/400 on server you were trying to verify the connection to.


  •  - CWBCO1019

    Cause
    The specified communications provider is not ready for use.

    Recovery
    Verify that the communications provider is installed and configured properly, and that basic functions, such as 'ping', are working properly. Contact your network administrator to make sure there are no problems with the network or its configuration.


  •  - CWBCO1020

    Cause
    The Signon transaction program is not functioning properly or there is a network problem between your personal computer and the server.

    Recovery
    Have your system administrator verify that the latest service level for the Signon transaction program has been installed on the server, and retry the operation.


  •  - CWBCO1021

    Cause
    The connection to the server is not configured correctly.

    Recovery
    Verify that the properties of that connection are correct, and that the communication provider shown for that connection is what you expected.
    See Server Connection Properties for information on configuring the connection to the server.


  •  - CWBCO1022

    Cause
    Informational message - The remote port that will be used for this connection is shown.

    Recovery
    If the connections fails, verify this is the correct remote port.
    See Server Connection Properties for information on configuring the connection to the server.
    See help for message CWBCO1008.


  •  - CWBCO1023

    Cause
    Informational message - The local port that will be used for this connection is shown.

    Recovery
    See Server Connection Properties for information on configuring the connection to the server.


  •  - CWBCO1024

    Cause
    A condition exists that has prevented the cancel mechanism from working properly. The connection verification will continue, but if you try to cancel it, it may not end, or unpredictable results could occur. This could be the result of low PC system resources.

    Recovery
    Try freeing PC system resources by ending unnecessary programs (especially those that communicate with other systems) and deleting unnecessary files from your hard disk, and try the connection verification again. If the problem persists, shutdown and restart your pc, and try again.


  •  - CWBCO1039

    Cause
    Informational message - The remote TCP/IP address lookup mode that was used for this connection

    Recovery
    Verify the correct mode has been configured for this server.
    See Server Connection Properties for information on configuring the connection to the server.


  •  - CWBCO1040

    Cause
    Informational message - The remote port lookup mode that was used for this connection
    Server - Always connect to the Service Mapper to determine the port number for this service
    Local - Always look in the local services file for the port number
    Standard - Always use the pre-defined port number

    Recovery
    Verify the correct mode has been configured for this server.
    See Server Connection Properties for information on configuring the connection to the server.


  •  - CWBCO1041

    Cause
    Informational message - The TCP/IP gethostbyname() function will be used to resolve the TCP/IP address.

    Recovery
    If this is not desired, or if the time interval at which this happens needs to be changed, these settings can be changed. See Server Connection Properties for information on configuring the connection to the server.


  •  - CWBCO1042

    Cause
    The server configuration parameter is not correct for the reason code specified.

    Recovery
    Verify that the configuration for this server is correct. The reason codes can be found in the header files in the Programmer's Toolkit.


  •  - CWBCO1043

    Cause
    The server object instance could not be created for the reason code specified.

    Recovery
    Verify that the configuration for this server is correct. The reason codes can be found in the header files in the Programmer's Toolkit.


  •  - CWBCO1044

    Cause
    Informational message - The remote TCP/IP address that will be used for this connection attempt.

    Recovery
    See Server Connection Properties for information on configuring the connection to the server.
    You may need to refer to this message if the connection attempt fails.


  •  - CWBCO1045

    Cause
    Informational message - The local TCP/IP address that was used for this connection

    Recovery
    You may need to refer to this message if the connection attempt fails.


  •  - CWBCO1047

    Cause
    The connection was initially established, but was disconnected by the server or server application before communications were completed.

    Recovery
    Try the operation again. If the problem persists, have your systems administrator check the server to verify that TCP/IP and the host servers are running, and your connection is not restricted by an IP filter. See How to Start OS/400 Host Socket Servers.
    Have your system administrator check the server application job logs and server subystems. See message CWBCO1003 for the names of the server jobs and the default names of the subsystems.
    This can also result from incorrectly configured routing on the server when multiple routes to and from the server are possible. The result in this case is that packets sent to the server are discarded because they are too large. When this happens, TCP/IP on the PC assumes that the connection has been ended by the server since it is not responding to the packets sent from the PC, and reports error 10054 or 8405. Have your systems administrator analyze the configuration of TCP/IP and associated routing, as well as the maximum frame size configured for each TCP/IP interface that may be reachable from the PC, and correct any inconsistencies or problems with the configuration, then try the operation again.


  •  - CWBCO1048

    Cause
    The address used for the server was found, but the connection to the server timed out.

    Recovery
    Make sure TCP/IP has been started on that server, and that the host servers have been started. If this does not fix the problem, verify that the IP address used to attempt the connection is correct for the server. This address is logged in a previous message.
    Verify TCP/IP address servers (Domain Name Servers) are configured correctly on this PC and have the correct address for this server. If the address is correct, check the HOSTS file on your computer for errors. If the IP address specified in the HOSTS file is incorrect for the server, correct it and try the operation again.
    If a TCP/IP router of some kind exists on the network between the PC and the server, make sure the router is configured to allow connections to the iSeries Access host servers and to the Server Mapper on the server.


  •  - CWBCO1049

    Cause
    The server was contacted, but refused the connection request.

    Recovery
    Make sure the host servers have been started on the server; see How to Start OS/400 Host Socket Servers.
    If a TCP/IP router, firewall or gateway of some kind exists on the network between the PC and the server, make sure the router is configured to allow connections to the iSeries Access host servers and to the Server Mapper on the server. If message CWBCO1022 was logged as well, this message indicates the port number that must be allowed through the router to perform the iSeries Access function being attempted.


  •  - CWBCO1051

    Cause
    A user specified timeout occurred trying to connect to the server. A timeout can occur while querying the IP address or making the initial connection attempt the server.

    Recovery
    Check the current configured timeout value for this server. If your Domain Name Server is on another network, you might want to consider changing your IP address lookup mode to be less frequent. See Server Connection Properties for information on changing the IP address and mode.


  •  - CWBCO1054

    Cause
    A user configurable time-out occurred during a send or receive attempt.

    Recovery
    Check the network for possible configuration or routing errors. Adjust the time-out period.


  •  - CWBCO1099

    Cause
    An internal error occurred in iSeries Access communications. This may be due to low PC system resources or may be a programming error.

    Recovery
    Free some PC system resources by ending any unnecessary programs and by deleting any unnecessary files from your hard drive, then try the operation again. If the problem persists, shutdown and restart your pc. If the problem remains, contact IBM Support.


  • - Server Connection Properties

    AS/400 connection properties default values for your AS/400 connections are maintained through the user's INI file. You can view and change default values that will be used by your applications when connecting to the specified AS/400 system. Unique default values for each AS/400 system can be set, however these values may be overridden at the application level.

    Values can be set for:
    AS/400 signon information - specifies what default user ID to use
    Performance - specifies the properties of the PC to AS/400 connection for the PC that can affect performance.


  • - How to start iSeries Access servers

    To start all of the host socket servers on the AS/400 system, type the following command at the AS/400 command prompt:
    STRHOSTSVR SERVER(*ALL)

    To start just the signon server on the AS/400 system, type:
    STRHOSTSVR SERVER(*SIGNON *SVRMAP)

    To use the socket servers, the QUSER profile on the AS/400 system must be enabled and the password must not be expired. One way to make sure that the QUSER profile is always enabled is to set the password with no expiration time value. To do this, type the following command at the AS/400 prompt:
    CHGUSRPRF USRPRF(QUSER) PASSWORD(*NONE) PWDEXP(*NO) STATUS(*ENABLED) PWDEXPITV(*NOMAX)

    If you are having trouble starting the host socket servers, try the following:

    1. Type STRHOSTSVR SERVER(*ALL) at the AS/400 command prompt.
    2. If step 1 does not work, type ENDHOSTSVR SERVER(*ALL) to end the host socket servers, then try step 1 again.
    3. If step 2 does not work, type NETSTAT at the AS/400 command prompt. Then select option 3. Work with TCP/IP connection status. Look for any jobs with TCP addresses beside them. End those jobs with option 4, then try step 1 again.

    The various servers on the AS/400 system have different timeout values that come into play when the PC goes down before the connection is disconnected. For example, in the case where your PC goes into a hang condition before you can disconnect all of your host server connections and data queues, you will have server jobs active on the AS/400 system until they timeout. This timeout could be minutes, hours, or days, depending on the server.

    Ending the host servers does not clean up the jobs running on the AS/400 when the ENDHOSTSVR command is run on the AS/400. The good thing about not cleaning up jobs is that your host server connections and data queues will continue to work after the ENDHOSTSVR command is run. The downside to not cleaning up server jobs on the AS/400 is that jobs that are still active prevent the server from starting when the STRHOSTSVR command is run on the AS/400.

    When ending and restarting host servers on the AS/400, you should use the CWBPING command from a Client Access Express workstation to make sure the host servers actually start back up. If they do not start back up, use the NETSTAT command and end any active jobs with TCP/IP addresses next to them.

Contact IBM

  • Call IBM Support Line:
    1-800-IBM-SERV (1-800-426-7378)1-800-426-7378
    Inside the US

To draw insights and make better decisions, businesses rely on the secure, flexible and open platform of IBM Power Systems. Built with the first processor designed for big data workloads, the design of Power Systems combines the computing power, memory bandwidth and I/O in ways that are easier to consume and manage, building on strong resiliency, availability and security.

IBM Power Systems deliver flexibility and choice of operating systems to enable your business to support the next generation applications for big data and analytics and cognitive computing that are transforming how organizations work today. Whether running 1, 2, or all 3 - coupled with PowerVM, they maximize the benefit of Power Systems in your business.

Transform your business with Systems Software that enables virtualization, high availability, flexibility, security and compliance on Power Systems™. IBM’s integrated approach to developing Systems and Systems Software together delivers optimized results with Power Systems.

As an open innovation platform, Power Systems is optimized for big data and analytics performance and to deliver scale-out economics and security for the cloud. IBM and IBM Business Partner solutions exploit key capabilities in IBM Power Systems.

Over the last five years thousands of clients have migrated to IBM Power Systems for choice and flexibility. Learn how Power Systems has helped them revolutionise the way IT is developed and delivered, optimise for big data and analytics, and support private, public and hybrid offerings for scale-out or scale-up implementations all while improving business performance, reducing risk, and establishing a platform for growth.