The bop_sinfo command is used to interrogate the Unicenter Service Desk Object layer.
This command which is run from the Service Desk primary server command prompt provides information about a particular object and its attributes. There are various flags and options for running bop_sinfo. These options are:
- bop_sinfo -q <object_name>. Returns the logical database name for a particular object. For example, "bop_sinfo -q cr" returns "Call_Req" meaning the cr object is associated with the Call_Req table in the logical database layer.
- bop_sinfo -d <object_name>. Lists all the attributes for an object. For example, "bop_sinfo -d cr" returns a listing of attributes. The listing is not sorted, but you can sort the output by piping to the sort command (bop_sinfo -d cr | sort).
- bop_sinfo -da <object_name>. Lists all the attributes with additional information. The output is much longer than with just the -d flag. The additional information is useful in identifying whether the attribute name is the same name used in the logical database layer. Typically, the attribute name and the field name in the logical database are the same, but in some very prominent cases the names are different between these two layers. When the logical database field is different from the attribute name, then the right column of the bop_sinfo -da output displays a phrase beginning with ddict that indicates the different logical database field name.
- bop_sinfo -f <object_name>. This command lists the factory connections. Of importance is that the output of this command lists the "Rel Attr" and "Common Name". The RelAttr (or relationship attribute) is the attribute that is stored when the object is referenced. The "Common Name" is the attribute that is displayed when the object is referenced. For instance the command bop_sinfo -f cnt displays the RelAttr as "id" and the Common Name as "combo_name". This means that whenever a contact is used (cnt object is for contacts), the id value for the contact is stored (like in the Affected End User field for an incident) but the common_name attribute (last name, first name) is displayed.