{
{   The purpose of this request is to set  a  status  record  to  represent  a
{ message (usually describing some abnormal condition).
{
{   Additional    text    may    be   appended   to   the   status   via   the
{ osp$append_status_parameter,                      osp$append_status_integer,
{ osp$append_status_file, etc.  interfaces.
{
{   These  requests  provide  a basic capability for editing status parameters
{ into the status record's text field (e.g.  the removal  of  trailing  spaces
{ from the status parameters).
{
{   The  condition  code for the status may be specified as a single number or
{ via its "component parts", i.e.  the two character "product identifier"  and
{ the  "condition  number".  If the value given for the condition parameter is
{ within the bounds of a ost$status_condition_number, the identifier parameter
{ is  combined  with  it  to  form  the  condition  code in the status record;
{ otherwise the  condition  parameter  is  assumed  to  represent  the  entire
{ condition code and the identifier parameter is ignored.
{
{       OSP$SET_STATUS_ABNORMAL (IDENTIFIER, CONDITION, TEXT, STATUS)
{
{ IDENTIFIER:  (input) This parameter specifies the product identifier for the
{       condition.
{
{ CONDITION: (input) This parameter specifies the condition code (or condition
{       number) for the condition (see above).
{
{ TEXT: (input) This parameter specifies the first status parameter.  The text
{       field's size is initially set to zero (no text).  If this parameter is
{       not     the     null     string     (string     length    not    zero)
{       osp$append_status_parameter is called to add the parameter to the text
{       field  with  a  delimiter of osc$status_parameter_delimiter; otherwise
{       the text field is left empty.
{
{ STATUS: (output) This paraeter specifies the status record to be set.
{
