Tracing events processed by the RMG demonstration program can be enabled by starting the Natural Access Server (ctdaemon) and running RMG with the -t option. This can be helpful in understanding the sequence of events in certain scenarios.
Configuring and starting the Natural Access Server (ctdaemon) is described in the Natural Access Developer's Reference Manual.
The following example shows sample trace output from the Natural Access Server (ctdaemon) when RMG is run with tracing enabled:
CT Access Daemon V.5 (Mar 4 1999)
ctdaemon: Configuration file './cta.cfg':
[ctasys] section loaded.
ctdaemon: Configuration file './cta.cfg':
[ctapar] section loaded.
ctdaemon> MESG: Thu May 13 10:31:10 1999
| pid=6a tid=75 ctahd=80010002 (RMGCMD) uid=0 tag=4003 sev=0
| DEBUG: RMG Controller FSM started
MESG: Thu May 13 10:31:10 1999
| pid=6a tid=75 ctahd=80010002 (RMGCMD) uid=0 tag=4003 sev=0
| RMGC State: INITIAL Event: Board Halted
MESG: Thu May 13 10:31:10 1999
| pid=6a tid=75 ctahd=80010002 (RMGCMD) uid=0 tag=4003 sev=0
| RMGC State: LOADING Event: Board Loading
MESG: Thu May 13 10:31:14 1999
| pid=6a tid=75 ctahd=80010002 (RMGCMD) uid=0 tag=4003 sev=0
| RMGC State: LOADING Event: Now Starting
MESG: Thu May 13 10:31:14 1999
| pid=6a tid=75 ctahd=80010002 (RMGCMD) uid=0 tag=4003 sev=0
| RMGC State: STARTING Event: Board Isolated
MESG: Thu May 13 10:31:17 1999
| pid=6a tid=75 ctahd=80010002 (RMGCMD) uid=0 tag=4003 sev=0
| RMGC State: STARTING Event: Timer_T1
MESG: Thu May 13 10:31:20 1999
| pid=6a tid=75 ctahd=80010002 (RMGCMD) uid=0 tag=4003 sev=0
| RMGC State: STARTING Event: Timer_T1
MESG: Thu May 13 10:31:20 1999
| pid=6a tid=75 ctahd=80010002 (RMGCMD) uid=0 tag=4003 sev=0
| RMGC State: ACTIVE Event: Now Primary