Software Distributor Administration Guide for HP-UX 11i

Using Control Scripts
Control Script Input and Output
Chapter 11398
ERROR: The "unconfigure" script for "PRODUCT.FILESET"
failed (exit code "1"). The script location was
"/var/adm/sw/products/PRODUCT/FILESET/unconfigure".
* This script had errors but the execution of this
product will still proceed. Check the above output
from the script for further details.
WARNING: The "unconfigure" script for
"PRODUCT.FILESET" failed (exit code "2"). The script loc
ation was
"/var/adm/sw/products/PRODUCT/FILESET/unconfigure"
* This script had warnings but the execution of this
product will still proceed. Check the above output
from the script for further details.
• The messages written by a control script must conform to the
following format conventions whenever possible.
1. Never emit blank lines.
2. All output lines must have one of these forms:
ERROR:
text
WARNING: text
NOTE: text
blank text
In each case, the keyword must begin in column 1, and the text
must begin in column 10 (indented nine blanks).
3. Choose the keyword (ERROR, WARNING, NOTE, or blank) as follows:
ERROR: Cannot proceed, may need corrective action.
WARNING: Can proceed, but something went wrong and
may need action.
NOTE: Can proceed, but something happened that is
out of the ordinary or worth special attention.
(Not just a status message.)
blank Generic progress and status messages (keep
them to a necessary minimum).
Do not start a line with an asterisk (*) character. This is reserved
for operational messages printed by the agent so you can easily
distinguish them from other messages.