This document covers the following topics:
The Administration Data Maintenance function is used to maintain the essential information that is required for each Con-nect node and the central directory in your Con-nect network.
With the Administration Data Maintenance function you can add new Con-nect nodes to the central directory, delimit the role a Con-nect node will play in the directory synchronization, modify a node's information and erase a node from the directory synchronization.
When you select the Administration Data Maintenance functions, the screen below is displayed.
12:58 * * * C O N - N E C T 3 * * * 14/02/94
CD Name DAEFCOC Administration Data Maintenance OCAP20
Cmd Node Node Type DB FNR Date Last Uploaded Date Last Downloaded
*_______
__ DAEFCOC central 180 12
__ BOSTON up/download 180 30 12/02/1994 10:22:03.4 12/02/1994 10:27:43.8
__ CEDERRPD up/download 177 143 09/02/1994 13:24:50.9 09/02/1994 13:54:15.1
__ DALLAS up/download 67 30 29/01/1994 11:05:08.7
__ DENVER up/download 83 2 05/02/1994 16:42:21.7 05/02/1994 15:51:19.1
__ PORTLAND Renamed 177 143 22/12/1993 09:19:36.9 23/12/1993 17:06:25.0
__ RESTON up/download 180 37 01/02/1994 13:50:20.5 01/02/1994 11:28:18.0
Cmd: MO Modify DI Display ER Erase
Mark with unique letters from the list shown above
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Flip + Canc
|
Each Con-nect node defined to the central directory as well as the central directory is displayed here.
- Node
Identifies the transport service node responsible for uploading and downloading addresses to/from the central directory.
This is the transport service node name specified when the Con-nect's transport service was initialized. For further information, see Initializing the Transport Service.
In the case of the central directory, it is the directory's system name.
- Node Type
Indicates how the node participates within the network.
It can be one of the following:
Central Node is the central directory for this network. Upload Con-nect node is allowed to upload its local addresses to the central directory. Download Con-nect node is allowed to download addresses from the central directory. Up/download Con-nect node is allowed to upload local addresses to the central directory and to download addresses from the central directory. Renamed Node name has been renamed. Prepared Name has been changed and all addresses which originate from this node are being modified. Once all addresses have been modified, the status is changed to renamed. - DB
Database number of the node.
- FNR
File number of the node.
The values you specify for fields Node, DB and FNR are not verified when you add the node to the central directory, however, when the node performs an upload or download the system verifies the values in these fields against that values specified on the node's "Directory Synchronization Maintenance" screen.
The same values for the DBID and FNR can be used by several nodes.
- Date Last Upload
Date and time of last upload to the central directory.
- Date Last Download
Date and time of last download from the central directory.
To add a new Con-nect node or central directory, you press PF4.
Note:
You cannot define more than one central directory.
11:11 * * * C O N - N E C T 3 * * * 14/02/94
CD Name DAEFCOC Administration Data Maintenance OCAP21
Synchronization Abilities .... undefined (C,U,D,B)
Transport Service Node Name ..
DBID .........................
FNR ..........................
Renamed as ...................
Renamed on ...................
MRU Transaction Counter ......
MRD Transaction Counter ......
Date of Last Upload .......... 00/00/0000
Time ......................... 00:00:00.0
Date of Last Download ........ 00/00/0000
Time ......................... 00:00:00.0
Make the required changes and exit to add
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip Canc
|
The following information is required each time you add a node:
- Synchronization Abilities
Defines the role the node plays in the network. Specify one of the below values:
C The central directory. Once you have defined the central directory, you cannot add another, nor can you delete it. U Node is permitted to upload addresses to the central directory. D Node is permitted to download addresses from the central directory. B Node is permitted to upload and download to/from the central directory. - Transport Service Node Name
If you are adding the central directory, this is the central directory's file name.
If you are adding a Con-nect node, this identifies the node's transport service node name.
This is the transport service node name specified when the Con-nect's transport service was initialized. For further information, see Initializing the Transport Service.
- DBID
Database number of node. If you are adding the central directory, a default value is automatically provided for the LFILE parameter. In the case of a Con-nect node, no default is provided.
- FNR
File number of node. If you are adding the central directory, a default value is automatically provided for the LFILE parameter.
The remaining fields pertain to Con-nect nodes only and are automatically updated each time the node uploads or downloads to/from the central directory.
To add the new Con-nect node or central directory, press PF3.
Notes:
If you want to cancel the addition, you press PF12.
To display additional information pertaining to the central directory, you can enter DI in the Cmd column for the central directory and press ENTER.
11:13 * * * C O N - N E C T 3 * * * 14/02/94
CD Name DAEFCOC Administration Data Maintenance OCAP21
Synchronization Abilities .... C central
Central Directory Name ....... DAEFCOC
DBID ......................... 180
FNR .......................... 12
Log Level .................... 3
Current Node Uploading .......
Next Alias ................... D4l
Current Transaction Range ....
Next Transaction Counter...... 56601
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip Canc
|
The following information is displayed:
- Synchronization Abilities
Defines what role the node plays within the central directory. Since this is the central directory, C central will always be displayed here.
- Central Directory Name
Name of the central directory. This name will correlate to the name displayed in the upper left corner of the screen.
- DBID
Database number of central directory.
- FNR
File number of central directory.
- Log Level
Designates the type of event that will cause a record to be written to the log file.
It can be one of the below values:
0 Default. Log significant events which occur (e.g. uploads, downloads). 1 Log events that are traced by the system. It is recommended that log level one should only be used when additional information is required. 2 Log all programs that are traced. It is recommended that log level two should only be used when additional information is required. 3 Log all events that occur. It is recommended that log level three should only be used when additional information is required. - Current Node Uploading
Name of Con-nect node that is currently uploading addresses to the central directory. If no Con-nect node is uploading addresses this field is blank.
- Next Alias
Next available alias which will be assigned to the next new address uploaded. Each address uploaded to the central directory for the first time is assigned a unique alias.
- Current Transaction Range
This field is used as an extension for the "Next Transaction Counter" field, as described below. When the "Next Transaction Counter" field exceeds 27 digits, this field is filled with capital letter "A" and the "Next Transaction Counter" field is restarted with 1. The next time the "Next Transaction Counter" field exceeds 27 digits, the value in the "Current Transaction Range" field is changed to capital letter "B" and, once again, the "Next Transaction Counter" field is restarted with 1.
The sequence of values used for this field are:
" " (blank),
A - Z (upper-case letters A through Z), then
a - z (lower-case letters a through z), and then
0 - 9 (numbers 0 through 9).
It is recommended to reorganize your system when 9 is reached, otherwise duplicate transaction numbers may be assigned.
- Next Transaction Counter
Transaction number that will be assigned to the next address uploaded to the central directory. When this field exceeds 27 digits, it is restarted with 1.
To display additional information about a Con-nect node, you can enter DI in the Cmd column for that node and press ENTER.
16:41 * * * C O N - N E C T 3 * * * 14/02/94
CD Name DAEFCOC Administration Data Maintenance OCAP21
Synchronization Abilities .... B up/download
Transport Service Node Name .. BOSTON
DBID ......................... 180
FNR .......................... 30
Renamed as ...................
Renamed on ...................
MRU Transaction Counter ...... 000000000000000000000058284
MRD Transaction Counter ...... 000000000000000000000058273
Date of Last Upload .......... 09/02/1994
Time ......................... 11:43:42.4
Date of Last Download ........ 02/02/1994
Time ......................... 16:44:26.8
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip Canc
|
The following information is displayed:
- Synchronization Abilities
Defines what role the node plays within the central directory. It can be one of the following:
B up/download Node is permitted to upload and download addresses to/from the central directory. D download Node is permitted to download addresses from the central directory. U upload Node is permitted to upload addresses to the central directory. - Transport Service Node Name
Identifies the transport service responsible for transmitting mail items to/from the Con-nect node.
This is the transport service node name specified when the Con-nect's transport service was initialized. For further information, see Initializing the Transport Service.
- DBID
Database number of node.
- FNR
File number of node.
- Renamed as
Signifies whether the transport service node name has been changed with the Define Local Node function in the Con-nect administration. The name displayed here is the new name. See Modifying the Transport Service Node ID.
When the transport service node name is modified, a record with the new name is created. It is recommended that you do not erase the old record until all nodes on the network have performed a download from the central directory after the date of the rename to update all data that belongs to this node.
You must then notify each Con-nect administrator whose Con-nect interacts within the network of the transport service node name change. Each Con-nect administrator must add a new node with the new transport service node name (using the Add External Mail Node function).
Note:
If the node name is used as part of the import rule, the imported address' nickname is not modified with the new transport service node name.- Renamed on
Date the transport service node name was modified.
- MRU Transaction Counter
A transaction number is assigned to each address uploaded to the central directory. The number displayed here is also recorded on the Con-nect node and will be used to determine with which address the next upload will begin.
- MRD Transaction Counter
Transaction number assigned to the last address downloaded to this Con-nect node. The number displayed here is also recorded on the Con-nect node and will be used to determine with which address the next download will begin.
- Date of Last Upload
Date of last upload for this node.
- Time of Last Upload
Time of last upload for this node.
- Date of Last Download
Date of last download for this node.
- Time of Last Download
Time of last download for this node.
You can press PF5 to display the CSCI and broker address information (the server address):
13:04 * * * C O N - N E C T 3 * * * 14/02/93
CD Name DAEFCOC Administration Data Maintenance OCAP21
CSCI Address Data
Active Address .... _
Server Name ....... ________
Server Node ....... ________
Broker Address Data
Active Address .... _
Broker Id ......... ________________________________
Server Class ...... ________________________________
Server Name ....... ________________________________
Service ........... ________________________________
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip Canc
|
- Active Address
This field must be marked if the CSCI address is active.
- Server Name
Name of server. Together with field Server Node, it identifies which server is accessed by the client.
- Server Node
Name of node on which the server is executed.
- Active Address
This field must be marked if the broker address is active.
- Broker ID
Identifies the broker that will be addressed.
- Server Class
Together with fields Server Name and Service, the server class uniquely identifies the service (e.g. database, TP-monitor).
- Server Name
A logical name for a server which is used to distinguish between several servers of the same type or server class. The server name is used in conjunction with fields Server Class and Service to uniquely identify the service offered by the server.
- Service
Together with fields Server Class and Server Name, this field uniquely identifies the service. By convention, it is a readily understandable name for an actual service offered by the server.
To modify the central directory's data record, you can enter MO in the Cmd column for the central directory and press ENTER.
11:34 * * * C O N - N E C T 3 * * * 14/02/94
CD Name DAEFCOC Administration Data Maintenance OCAP21
Synchronization Abilities .... C central
Central Directory Name ....... DAEFCOC
DBID ......................... 180
FNR .......................... 12
Log Level .................... 3
Current Node Uploading .......
Next Alias ................... D4l
Current Transaction Range ....
Next Transaction Counter...... 56601
Make the required changes and exit to modify
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Force Flip Canc
|
You can modify the following fields:
- Central Directory Name
Name of the central directory. This name will correlate to the name displayed in the upper left corner of the screen.
If you modify the central directory name, you must notify all Con-nect administrators whose systems interact with the central directory of the modification, so that the administrators can modify their directory synchronization maintenance information to reflect the new name. If a Con-nect administrator fails to modify the central directory name, he cannot upload nor download addresses to/from the central directory.
- DBID
Database ID of central directory. If this field is modified, it is also automatically changed in the LFILE parameter.
- FNR
File number of central directory. If this field is modified, it is also automatically changed in the LFILE parameter.
- Log Level
Designates the type of event that will cause a record to be written to the log file.
It can be one of the below values:
0 Default. Log significant events which occur (e.g. uploads, downloads). 1 Log events that are traced by the system. It is recommended that log level one should only be used when additional information is required. 2 Log all programs that are traced. It is recommended that log level two should only be used when additional information is required. 3 Log all events that occur. It is recommended that log level three should only be used when additional information is required.
Additionally, if the Current Node Uploading field (displays the Con-nect node currently uploading) is blocked by a Con-nect node for longer than the usual amount of time, you can force the Con-nect node out of the upload process with PF5. As a result, a confirmation window is displayed in which you must enter Y and press ENTER to confirm the force.
To save your changes, press PF3.
To modify the data record for a Con-nect node, you can enter MO in the Cmd column for that node and press ENTER.
16:49 * * * C O N - N E C T 3 * * * 14/02/94
CD Name DAEFCOC Administration Data Maintenance OCAP21
Synchronization Abilities .... B up/download (C,U,D,B)
Transport Service Node Name .. BOSTON
DBID ......................... 180
FNR .......................... 30
Renamed as ...................
Renamed on ...................
MRU Transaction Counter ...... 000000000000000000000058284
MRD Transaction Counter ...... 000000000000000000000058273
Date of Last Upload .......... 09/02/1994
Time ......................... 11:43:42.4
Date of Last Download ........ 02/02/1994
Time ......................... 16:44:26.8
Make the required changes and exit to modify
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip Canc
|
You can modify the following fields:
- Synchronization Abilities
Defines what role the node plays within the central directory. It can be one of the following:
B up/download Node is permitted to upload and download addresses to/from the central directory. D download Node is permitted to download addresses from the central directory. U upload Node is permitted to upload addresses to the central directory. - DBID
Database number of node.
- FNR
File number of node.
Press PF3 to save your changes.
You can press PF5 to define the CSCI and broker address information (the server address). See the Entire Broker Reference Manual and the CSCI Reference Manual.
12:09 * * * C O N - N E C T 3 * * * 14/02/94
CD Name DAEFCOC Administration Data Maintenance OCAP21
CSCI Address Data
Active Address .... _
Server Name ....... ________
Server Node ....... ________
Broker Address Data
Active Address .... _
Broker Id ......... ________________________________
Server Class ...... ________________________________
Server Name ....... ________________________________
Service ........... ________________________________
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip Canc
|
- Active Address
If the CSCI address is active, this field must be marked.
- Server Name
Name of server. Together with field Server Node, it identifies which server is accessed by the client.
- Server Node
Name of node on which the server is executed.
- Address Active
If the broker address is active, this field must be marked.
- Broker ID
Identifies the broker that will be addressed.
- Server Class
Together with fields Server Name and Service, the server class uniquely identifies the service (e.g. database, TP-monitor).
- Server Name
A logical name for a server which is used to distinguish between several servers of the same type or server class. The server name is used in conjunction with fields Server Class and Service to uniquely identify the service offered by the server.
- Service
Together with fields Server Class and Server Name, this field uniquely identifies the service. By convention, it is a readily understandable name for an actual service offered by the server.
To save your changes, press PF3.
To cancel your modifications, press PF12.
To erase the data record of a Con-nect node, you enter ER in the Cmd column for that node and press ENTER.
If you have selected a node whose addresses are still contained in the central directory, a warning is issued, since addresses uploaded to the central directory are not deleted with the Con-nect node data record. If you wish to cancel the erasure, press PF3, otherwise press ENTER to continue.
As a result a confirmation window is displayed, enter Y and press ENTER.
12:10 * * * C O N - N E C T 3 * * * 15/02/94
CD Name DAEFCOC Administration Data Maintenance OCAP20
More: +
Cmd Node Node Type DB FNR Date Last Uploaded Date Last Downloaded
*_______
__ DAEFCOC +------------------------------------------+
__ BOSTON ! ! 02/1994 10:27:43.8
__ CEDERRPD ! Warning ! 02/1994 13:54:15.1
__ DALLAS ! ! 01/1994 11:05:08.7
__ DENVER ! ! 02/1994 15:51:19.1
__ PORTLAND ! Node CEDERRPD will be erased. ! 12/1993 17:06:25.0
__ RESTON ! ! 02/1994 11:28:18.0
! 185 Address Records still exist !
! for this Node. !
! !
! !
! !
! !
+------------------------------------------+
Cmd: MO Modify DI Display ER Erase
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Flip + Canc
|
The data record is immediately erased from the "Administration Data Maintenance" screen.
If you select the data record of a Con-nect node for erasure that has been renamed and at least one of the Con-nect nodes defined in the central directory have not performed a download since the rename, a window is displayed advising you of the fact. If you wish to continue with the deletion, press ENTER to display the confirmation window, or press PF3 to quit.
Notes: