When you save a connection, System Administration & Diagnostics checks if the connection is in use, examines what changes were made, and considers whether the save can be allowed or if any warnings are needed. The following table shows the save processing and warning messages that may appear in the warning message box. The possible situations are listed in order of precedence, highest to lowest. If more than one situation applies, the message box and operation for the situation listed highest in the table is used.
Table: Save Connection Warnings and Operation
|
Connection Type |
Connection in Use By: |
Message Box Text (Title: Save Connection) |
Operation Result: |
|
Any or any field relating to the active connection only |
DB Programminga |
<connection name> is a [modem / remote configuration / network / onsite] connection, which is in use by DB Programming or a Scheduled Backup. Before you change settings affecting this connection, you must terminate the DB Programming session or wait for the backup to complete. (Save connection anyway / Cancel) |
The connection is closed.b Monitoring stops. DB Programming and any other applications are left running, their links go down. |
|
<connection name> is in use by DB Programming or a Scheduled Backup. Before you change settings affecting this connection, you must terminate the DB Programming session or wait for the backup to complete. (Save connection anyway / Cancel) |
The settings are updated. Most likely, DB Programming and other applications are unaffected. However, there are possible negative results.c |
||
|
Modem or Remote Configuration or any field relating to the connection type in the Offsite Connection group box. |
Another application |
<connection name> is a [modem / remote configuration] connection, which may be in use by the following: <list>d Are you sure you want to change settings affecting this connection? (Save connection / Cancel) |
The connection is closed.b Monitoring stops. Other applications are left running, but their links go down. |
a. Because DB Programming may be in the middle of performing a scheduled backup, or processing a restore or other update, System Administration & Diagnostics does not blindly force it to terminate. Verify that DB Programming is not busy, and then end the session, or wait for the backup to complete.
b. When the changes are saved, if the connection changed is the active connection, it is disconnected. If setup options indicate (see Programming System-Wide Options), the System Administration & Diagnostics application re-connects to the connection using the new settings. If successful and setup options indicate (see Programming System-Wide Options), diagnostic monitoring begins for the connection. Also at this time, if a Modem or Remote Configuration connection is restored with the same PPP IP address, some applications using the connection may restore their links.
c. If settings are updated while DB Programming is active for the connection, there are two possible negative results. First, System Administration & Diagnostics might overwrite changes being made by DB Programming at the same time, or DB Programming might overwrite the changes made by System Administration & Diagnostics. Second, you may expect that changes saved will be reflected in the active DB Programming session, but they will not. This is why the application prompts you to terminate the DB Programming session.
d. The list of applications that may be using the connection may include one or more of the following: AWS Web page, SSH connection, and Diagnostics Monitor. System Administration & Diagnostics checks for these applications at least as reliably as DB Programming did in versions 3.0 through 3.2. If applications other than those listed are using the connection, they may not be detected. Also if the AWS Web page is open for any 5000 CP, because the IP address is not internally visible to System Administration & Diagnostics, it is listed as an application possibly using the connection.