SmartSync/DCP Installation Guide
15
The BSC Task Monitor and Interrupt Clock should always be “Running”
during normal operation.
The BSC Processes can have the following states: “Not Running”, “Running
in IDLE State”, “Running in XMT State”, “Running in RCV State”, and “Not
Running in IDLE State” (this is an error state).
If the BSC Task Monitor or Interrupt Clock is in the “Not Running” state,
you must run Dcpload to reinitialize the SmartSync/DCP board. This is also
true if one the BSC Processes is hung in one of the “Running” states (i.e.,
Killbsc is unable to return it to the “Not Running” state).
DCPDUMP −− SmartSync/DCP Dump Utility
This program is used to access the onboard memory and registers of
SmartSync/DCP. This utility is strictly for diagnostic purposes and should
only be used under the direction of Serengeti Technical Support.
DCPDEBUG −− SmartSync/DCP Debug Utility
This program is used to access debug messages generated by
SmartSync/DCP BSC processes. This utility is used strictly for diagnostic
purposes and should only be used under the direction of Serengeti Technical
Support.
The debug messages obtained by Dcpdebug are automatically written to both
the screen and a file. For best results, Dcpdebug should be run minimized so
as not to affect transmission throughput when running 3780Link. If you've
configured one SmartSync/DCP, the default file name is “debug. x” where x
is the port number. If you've configured more than one board, the default file
name is “debug.xy” where x is the port number and y is the board number.
By default the output file is reset when it reaches 100,000 bytes. This
enables Dcpdebug to run continuously without overflowing disk storage. The
optional command line switches for Dcpdebug are described below:
