Progress/400
Product Guide


TCP/IP Communications Protocol

The TCP/IP components are:

The TCP/IP broker is a job on the AS/400 that has the capability of starting database servers. It starts one database server per client connection.

Figure 4–2 illustrates how the client and server components interact in a TCP/IP configuration.

Figure 4–2: TCP/IP Communications Jobs

You must be able to ping the host machine before Progress connects. If you cannot ping the host machine, Progress will not connect.

These notes help to explain Figure 4–2:

  1. Start a TCP/IP broker on the AS/400 manually with the STRPRONET command. The broker must be started by a user with all object authority (*ALLOBJ).
  2. The Progress client issues a CONNECT statement to the server. The CONNECT statement includes information about the network protocol (-N TCP), the host machine (-H), and the service name (-S). The connection is made to the broker that is waiting on the port identified by the service name.
  3. When the broker receives the connect information, it starts the DataServer.
  4. The broker determines the port that the server will use and notifies the server.
  5. The server acknowledges that it received the information about the port.
  6. The broker notifies the client of the port that the server will use.
  7. The client directly connects to the server using the port number provided by the broker.
  8. The broker continues to run as a job on the AS/400 until you manually end it with the ENDPRONET utility.

Because TCP/IP is single threaded, the broker must successfully start one database server job before it can service another. The broker services client requests one at a time only.

Running TCP/IP

You must start the TCP/IP broker with an OS/400 user containing all object authority. However, the actual server jobs run with the level of authority of the client. You specify the client’s user profile with the User ID (-U) and Password (-P) connection parameters. A client that uses a profile supplied by IBM (QDOC, QDFTOWN, QPMGR, QPRGOWN, QSECOFR, and so forth) cannot start a server with TCP/IP networking.

Follow these steps to run the TCP/IP broker on the AS/400:

  1. Type STRPRONET on the command line, then press F4 to display the utility’s parameters.
  2. Enter the information as described in AS/400 Utilities."

To verify that STRPRONET successfully started a broker, do one of the following:

Managing and Stopping TCP/IP Brokers

To manage a TCP/IP broker, execute the MNGPRONET command on the AS/400. This utility allows you to manage, monitor the status of, or stop a TCP/IP broker. For details, see the "Manage Progress/400 Networking (MNGPRONET)" section in AS/400 Utilities."

You can also stop a TCP/IP broker by running the ENDPRONET utility on the AS/400. For details, see the "End Progress Network (ENDPRONET)" section in AS/400 Utilities."


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095