This section describes the Adabas System Coordinator Online Services application SYSCOR.
To invoke Adabas System Coordinator Online Services
log on to SYSCOR and enter the command
MENU.
During logon to SYSCOR, the application will determine its current run mode. Run mode can be any of the following:
| Run Mode | Description |
|---|---|
| Coordinator not installed | The Adabas link module does not contain the Coordinator stub. Local session information will not be available but all other functions will work. |
| Local (node 0) | The TP system in use is running in local (non-daemon) mode. By default, session information will be obtained locally. |
| Daemon (node nnn) | The TP system in use is running with an Adabas System Coordinator daemon. The daemon Node ID is displayed. By default, session information will be obtained from the daemon. Dynamic transaction routing (DTR) is possible for clustered applications in TP systems defined to run in daemon mode. |
| Pulsing (node nnn) | The TP system in use has been configured to send session activity statistics to the daemon Node ID displayed. By default, session information will be obtained from the daemon and can be viewed from any other TP system by setting the perspective to the daemon Node ID displayed. DTR is not possible for TP systems defined to run in pulsing mode. |
| Startup | The Adabas link module contains the Coordinator stub, however the database containing the Coordinator configuration file is not yet available. The Coordinator periodically retries access to the configuration file until it becomes available. |
The run mode will be displayed on an Environment Information screen at logon. This screen also shows information about the current Adabas System Coordinator daemon, if one is used. It is displayed before the main menu appears.
The Main Menu screen will then appear:
17:31:56 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03
- Main Menu - C1MAINM1
Run-mode: Pulsing (node 2650)
Code Service
---- -------------------------
0 System Settings
1 Maintenance
2 Current Activity Displays
3 Special Services
4 About System Coordinator
. Exit
---- -------------------------
Code..: _
You can easily switch around the tools for Fastpath, Vista etc by use of
PF11, or use the codes COR, AFP, AVI, AAF, ATM as commands - anytime.
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Prods Vers
|
The following options are available:
| Option | Description |
|---|---|
| System Settings | Maintain configuration file setting. |
| Maintenance | Define and maintain definitions and parameters. |
| Current Activity Displays | Display information about the current session and other sessions in this TP system or, when using a daemon, other sessions anywhere in the entire enterprise. |
| Special Services | Provide installation and applied fix information for the Adabas System Coordinator components, and define timeout settings. |
| About Adabas System Coordinator | Display product information. |
Note:
From the Adabas System Coordinator main menu, you may switch to the
online systems of Adabas Fastpath, Adabas Vista, Adabas SAF Security or Adabas
Transaction Manager by pressing PF11. PF11 cycles in the
sequence System Coordinator to Transaction Manager to Fastpath to Vista to SAF
Security. You may also switch from any screen with a command line by entering
the appropriate three-character code (for example, AVI for Adabas Vista) as a
command. You may only switch to the same version of another online system.
You can access screens in two ways:
sequentially by selecting a menu service and entering it in the Code field; or
directly by typing a numerical command on the command line.
For example, entering the command 1.1 on the
command line directly accesses the Client Runtime
Controls screen within the Maintenance function without first
accessing the Maintenance menu.
| Function | Object | Command |
|---|---|---|
| System Settings | Menu | 0 |
| LFILE 152 Maintenance | 0.1 | |
| Maintenance | Menu | 1 |
| Client Runtime Controls | 1.1 | |
| Daemon Groups | 1.2 | |
| Current Activity Displays | Menu | 2 |
| Display Adabas Client Jobs | 2.1 | |
| Network Discovery | 2.2 | |
| Display Daemons in a Daemon Group | 2.3 | |
| Special Services | Menu | 3 |
| Verify System Coordinator Client Installation | 3.1 | |
| Verify System Coordinator Server Installation | 3.2 | |
| Display Applied Fixes (Zaps) | 3.3 |
SYSCOR uses PF keys for various actions. Key functions are standard throughout the system, wherever possible. The PF keys that apply to each screen are indicated at the bottom of the screen.
The following keys apply throughout the system:
| PF Key | Function | Description |
|---|---|---|
| PF1 | Help | invoke the help specific to the current screen |
| PF3 | Exit | quit and return to the previous screen |
The following keys apply generally, depending on the type of action or function in use:
| PF Key | Function | Description |
|---|---|---|
| PF4 | Refr | from active screens, refresh the data |
| PF5 | Upd. | from general maintenance screens, commit the update |
| PF7 | Back | from list screens, return to the previous page |
| PF8 | Next | from list screens, move to the next page |
| PF10 | Add | from general maintenance screens, add an object |
| PF12 | Menu | return immediately to the main menu |
To invoke Adabas System Coordinator help information
Press PF1.
The help screen that appears applies to the current screen and may comprise several pages. From each help screen, you can access lower level options or return to previous, higher levels.
You can navigate by entering
| - | to move backwards and up a menu level |
| 1 - 8 | to move down a level to the function selected |
If the help screen comprises multiple pages, you can enter
| + | to move to the next page |
| - | to move to a previous page until page 1, then back up a level |
