Filter
Top Products
ANR0925E Tracing is already active to standard output.
Explanation: A TRACE BEGIN command has been entered, but tracing is already
active to the standard output destination (usually the server console).
System Action: The command is ignored.
User Response: If the current trace output destination is acceptable, no action is
required. Otherwise use the TRACE END command to stop tracing and then reissue
the TRACE BEGIN command as desired.
ANR0926E Missing or invalid TRACE command parameter.
Explanation: The TRACE command issued contains an invalid parameter, or is
missing a required parameter.
System Action: The command is ignored.
User Response: Reissue the command with the proper parameters.
ANR0927E Unknown trace class keyword - class.
Explanation: A TRACE ENABLE command has been entered which specifies an
unknown trace class.
System Action: The command is ignored.
User Response: Reissue the TRACE command with the correct class.
ANR0928E Unable to open trace file file spec for appending.
Explanation: A TRACE BEGIN command specifies an output file, but the server
cannot write to that file.
System Action: The command is ignored.
User Response: Check the file for proper access permissions, or reissue the
TRACE command specifying a different output file.
ANR0929E Insufficient memory to activate tracing.
Explanation: A TRACE BEGIN command has been entered, but the server has
insufficient memory available to activate tracing.
System Action: The command is ignored.
User Response: If tracing is required, make more memory available to the server
then restart the server.
161
Tivoli Storage Manager Messages
3. Common and Platform
Specfic Messages