How to verify that the application processes for an RDT are running

The associated processes for a specific RDT can be identified as follows.

1.  Obtain the TruckID from the workstation record associated with the RDT.

2.  The presence of the associated "ritch" process can be checked by searching for this TruckID (the "-j" parameter to "ritch").  For example if the TruckID was 511:

patdba@sal bash[998]: ps -fu patdba | grep ritch | grep ' 511 '
patdba   47356 47774  0 Dec20 ?        00:00:00 ritch -j 511 -s

3.  The presence of the associated "ptysvr" process (if a physical RDT is being used rather than one that is emulated) can be checked similarly (the "-j" parameter):

patdba@sal bash[999]: ps -fu patdba | grep ptysvr | grep ' 511 '
patdba   48759 47774  0 Dec13 ?        00:00:00 ptysvr -n -t -p 6511 crtrdt -j 511 -n -a -r 8 -c 40

4.  The "crtrdt" process can be similarly checked:

patdba@sal bash[1000]: ps -fu patdba | grep crtrdt | grep ' 511 '
patdba   48759 47774  0 Dec13 ?        00:00:00 ptysvr -n -t -p 6511 crtrdt -j 511 -n -a -r 8 -c 40
patdba   48760 48759  0 Dec13 ?        00:00:39 crtrdt -j 511 -n -a -r 8 -c 40

Note in the above that this is a physical RDT.  The "ptysvr" process spawns a child "crtrdt" process which is why the command line for "crtrdt" is included in that for "ptysvr" and why the "ps" command returns both processes in the above example.
 

RDTs will fail to connect or function correctly if one of the processes that manages them on the Dispatcher application server is absent.  The three processes are:

ritch : Contains the "business logic" for the RDT.
ptysvr : Manages the TCP/IP connection to the RDT.
crtrdt : Manages the screen display for the RDT.

Note that "ptysvr" is not used for emulated RDTs where the "startrdt" script is being used.
 

The TCP/IP port on which the "ptysvr" process is listening for connections from the physical RDT is defined by the "-p" parameter (port 6511 in this example).