The PATHWAY records provide general data on each Pathway system that is configured in the PATHWAY Configuration. This includes a status summary for the TCP’s, server classes and terminals configured for the Pathway system.
The records which pertain to the PATHWAY Configuration are:
In order to obtain data in these records the PATHWAY Configuration must be setup appropriately. A sample configuration is supplied, this is called PATHCONF and is located in the public screen file.
This statement is mandatory and requires that a Pathway monitor (Pathmon) process be entered. Options are then available to monitor the Pathway TCP (terminal control processes) and Link (flow of data between the terminals and the servers) information.
The DYNTERMSTATUS option causes all dynamically created terminals to be monitored for status only (i.e. Terminals started by using 'run prog')
The DYNTERMSTATISTICS option causes all dynamically created terminals to be monitored for status and statistics (i.e. Terminals started by using 'run prog').
The BRIEF option significantly reduces the overheads associated with collecting pathway information. It will however, mean that Server process details and Link information (connections between TCP’s or Linkmon’s and server process) are not available.
This is the collection interval for the statistical (performance) information. The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.
Used to specify that status information is to be monitored at a shorter interval than specified in the INTERVAL parameter (the statistics interval). The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.
If STATUS-INTERVAL (0) is specified, TP Manager will monitor EMS events for the configured Pathway systems. If Pathmon is configured with a log destination of $0, using the EVENTFORMAT, STATUS options (e.g. log2, EVENTFORMAT, STATUS), then any state change in a Pathway entity will be immediately visible in the relevant record. Typically, only the state field in these records will be updated based on events, all other fields will only be updated at every statistics interval. However, if this Pathmon configuration option is used and an EVENTFORMAT, STATUS log destination is not configured for a Pathway then the status information will only be updated for that Pathway at every statistics interval.
Specifying a non-zero STATUS-INTERVAL causes TP manager to regularly query status information for each of the configured Pathway entities. This is typically less efficient than using STATUS-INTERVAL (0) but does not rely on having the Pathway configured to log to EMS. When using this option, typically only the relevant state field will be updated on this interval, all other fields will only be updated at every statistics interval.
This option specifies whether or not the Pathway TCP statistics counters will be reset for all configured Pathway systems every statistics interval. The default for this option is Y causing statistics in the TCP to be reset at the beginning of each collection interval.
Used to specify which static terminals are to be monitored. Dynamic terminals can be monitored using the DYNTERMSTATUS or DYNTERMSTATISTICS option in the ADD PATHMON statement.
The way in which to maximize the number of possible terminals is to use a single ADD PATHTERM command and concatenate all entries into a single line. For example, instead of having the following multiple statements:
ADD PATHTERM ($DB,TERM01)
ADD PATHTERM ($DB,TERM02)
ADD PATHTERM ($ST, ABC001)
ADD PATHTERM ($ST, ABC002)
ADD PATHTERM ($ST, ABC003)
ADD PATHTERM ($XY, PQR001)
ADD PATHTERM ($XY, PQR002), etc,
use as many of the 80 characters, that are available on a line and wrap around to the next line if required, such as ...
ADD PATHTERM ($DB,TERM01,TERM02,$ST,ABC001,ABC002,ABC003,$XY,PQR001, PQR002)
This should allow a maximum of approximately 3000 terminals.