![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Message DetailThere are four available levels of message detail that can be displayed
Since the message kind is stored in the catalog, neither the simple or cryptic forms are able to select the appropriate message prefix. Rather than use nothing or pick one prefix, "<UNKNOWN_KIND>" is used both as a marker and as a hint to the developer to fix the kind if it shows up during testing.
Examples:
- verbose
::: [apex check_out /people/marlin/test/rn?.ss/wrk.w*k/nothing] *** "/people/marlin/test/rn?.ss/wrk.w*k/nothing": Unable to resolve (/people/marlin/test/rn?.ss/wrk.w*k/nothing does not match any existing object) ::: [apex check_out has finished]
- concise
::: [apex check_out /people/marlin/test/rn?.ss/wrk.w*k/nothing] *** "/people/marlin/test/rn?.ss/wrk.w*k/nothing": Unable to resolve ::: [apex check_out has finished]
- cryptic
<UNKNOWN_KIND> User_Commands.Ruc_Msg.1 <UNKNOWN_KIND> User_Commands.Ruc_Error.25 <UNKNOWN_KIND> User_Commands.Ruc_Msg.2
- simple
<UNKNOWN_KIND> User_Commands.Ruc_Msg.1: (object_1 => , object_2 => , object_3 = > , pathname => apex check_out /people/marlin/test/rn?.ss/wrk.w*k/nothing, name => , string => , count => 0) <UNKNOWN_KIND> User_Commands.Ruc_Error.25: (object_1 => , object_2 => , object_3 => , pathname => /people/marlin/test/rn?.ss/wrk.w*k/nothing, detail => Object_Management.Rom_Naming_Error.1: , unix_detail => , operation => ) <UNKNOWN_KIND> User_Commands.Ruc_Msg.2: (object_1 => , object_2 => , object_3 = > , pathname => apex check_out, name => , string => , count => 0)
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |