HP 3000 Manuals HP 3000 Manuals
Appendix C Troubleshooting
This appendix discusses the TSTART command which is a diagnostic tool
used to track the results of the Silhouette Manager Program >START
command. TSTART stands for "Trace START" .
To use this tool you run the Silhouette Manager Program (MP), designate
the configuration file, and issue the TSTART command:
:RUN SILMP.PUB.SYS
HP30302 (A.01.00) Silhouette Manager Program
(C) COPYRIGHT Carolian Systems International Inc. 1984
>SYSTEM configfile
>TSTART configfile
#J12
After several seconds (or minutes if the configuration is large and
includes many DS lines) a report is displayed showing the successful
startup of the system. A sample screen representing a system with one DS
line is shown below:
MP(Responses) OK, Rdrs=1 Wtrs=1
MP(Commands) OK, Rdrs=1 Wtrs=1
MPSent Who'r'u to CP
MPReceived response for Who'r'u
MPSent request for config.
MPConfig received OK.
CP OPENLOG intrnsic: Successful execution of function / request. (RQMSG 0)
Create tape process: Successful execution of function / request. (RQMSG 0)
REMOTE Hello : Successful execution of function / request. (RQMSG 0)
Master POPEN : Successful execution of function / request. (RQMSG 0)
CP send cnfg to SP : Successful execution of function / request. (RQMSG 0)
Open slave msgfiles: Successful execution of function / request. (RQMSG 0)
Create RP job : Successful execution of function / request. (RQMSG 0)
Slave to open DB's : Successful execution of function / request. (RQMSG 0)
CP Open logfile : Successful execution of function / request. (RQMSG 0)
CP files/lines open: Successful execution of function / request. (RQMSG 0)
The Silhouette system was started successfully. (MPMSG 55)
>
The first six lines of this display reports on the Manager Program (MP)
communication with the Communication Process (CP). Each of these lines
starts with MP denoting the source of the printout. The MP sets up
message files to use when communicating with the CP and checks for the
existence of a CP. If a CP already exists, the MP checks that it is set
up for the correct configuration file. If the CP does not exist, or if
it is serving another configuration file, the MP creates a CP and sets it
up for the current configuration file.
The next five lines of the display report on CP tasks on the primary
system. Each of these lines begins with CP to denoting the source of the
printout.
The remainder of the display reports on tasks involving the secondary
system. These lines do not start with identifying letters but the
reporting module is identified in the text of the message. Each task
reported on is identified immediately before it begins to execute and
when it is finished. The two messages form a complete sentence reporting
on the success or failure of the task.
For example, one of the tasks of the startup procedure is the creation of
a tape handling process (the TP). As the startup code is about to perform
this task the following message is displayed:
Create tape process:
Create tape process: Successful execution of function / request.
If the startup is not successful, Silhouette reports the reason for the
failure in as much detail as possible. A failure in startup does not
abort. However, control reverts to the Silhouette Manager Program and a
message is displayed stating that the system did not start successfully.
Appendix A includes the complete text of all Silhouette error messages.
The following example shows the results of a TSTART when the logfile on
the secondary system does not exist.
:RUN SILMP.PUB.SYS
HP30302 (A.01.00) Silhouette Manager Program
(C) COPYRIGHT Carolian Systems International Inc. 1984
>TSTART
#J14
MP(Responses) OK, Rdrs=1 Wtrs=1
MP(Commands) OK, Rdrs=1 Wtrs=1
MPSent Who'r'u to CP
MPReceived response for Who'r'u
MPSent request for config.
MPConfig received OK.
CP OPENLOG intrnsic: Error executing the OPENLOG intrinsic. (RQERR 15)
Parameter returned by above error: 3. (CPERR 70)
The specified system was NOT started. Check $STDLIST of the
CP or RP job for any errors and try again. (MPERR 54)
>