Progress/400
Product Guide


Connection Troubleshooting

Table 4–5 describes circumstances that can produce connection failures and how Progress responds to them.

Table 4–5: Connection Failure Responses 
Failure Circumstance
Progress Response
During startup
Progress displays an error message and returns to the operating system prompt.
During a CONNECT statement
Progress terminates the remainder of the CONNECT statement and a run-time error occurs. Connections made previous to the failed connection remain in effect.

Use the NO-ERROR modifier with the CONNECT statement to trap run-time errors. If you use the NO-ERROR modifier and it fails, you see the same failure behavior as with an unsuccessful CONNECT statement. However, run-time errors do not occur. Use the CONNECT statement to test for a valid connection.
During an auto-connect
Progress terminates the remainder of the auto-connect and a run-time error occurs. Any connections made previous to the failed connection remain in effect. You cannot trap auto-connect run-time errors.
During an attempt to connect using the Progress Data Dictionary
The Progress Data Dictionary displays an error message.
During an attempt to connect to a connected database with the same logical name
Progress responds with a warning. You can continue. (Use NO-ERROR to suppress the warning.)
During an attempt to connect to an unconnected database when the logical name is in use by a connected database
Progress responds with a run-time error. You cannot connect to the second database.

NOTE: Use the CONNECTED function to see if you are already connected. For more information, see the Progress Language Reference.

There are several reasons that a connection attempt to a Progress/400 database can fail:

When the server terminates unexpectedly, the Progress client is sometimes left in a semiconnected state. When the client-server connection is lost unexpectedly, make sure to issue a DISCONNECT statement before you attempt to reconnect.

NOTE: If the server terminates unexpectedly without producing a job log, do the following to ensure that the system generates a job log:

Use the resulting job log to help diagnose the connection problem.

Table 4–6 describes common error messages that you might encounter during connection and suggests responses.

Table 4–6: Connection Failure Error Messages
Error Message
Response
You cannot use AS/400 communications for the dbname database.
1. Verify that the database name is spelled
  correctly.
2. Verify that the schema holder is connected
and describes the specified database.
Partner LU alias or mode name unknown.
Check the PLU alias name and the mode name.
User ID/Password combination not accepted by AS/400.
Check the case-sensitive user ID and password passed by the -U and -P connection parameters.
The name of the server program was not recognized.
Verify that Progress was correctly installed.
The server program appended on the AS/400.
Check the OS/400 job log for information about the server program.1
The -H parameter for AS400SNA should be [LU=.../PLU=.../MODE=...].
Check the case-sensitive -H connection parameter.
The -H parameter LU, PLU, and MODE values cannot exceed 8 characters.
Check the case-sensitive -H connection parameter.
Could not establish initial conversation correctly.
Check the client job log, the OS/400 job log, or the operator’s message queue.
Unspecified error during initial send to AS/400.
Check the client schema job log or the OS/400 job log.
Unspecified error during initial receive from AS/400.
Check the client schema job log or the OS/400 job log.
Unspecified allocation error (AS/400 side).
Check the client schema job log or the OS/400 job log.
Unspecified error trying to initialize the session.
Verify basic connectivity between the client and the AS/400.
If you are connecting through SNA, check that you can establish a 5250 session.
If you are connecting through TCP/IP, use the ping command to check the connection.
Unspecified parameter error trying to allocate the session.
Verify basic connectivity between the client and the AS/400.
If you are connecting through SNA, check that you can establish a 5250 session.
If you are connecting through TCP/IP, use the ping command to check the connection.

Disconnecting from DB2/400 Databases

To disconnect from your target database, do any of the following:


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