Error conditions may be detected by HSI as the request is interpreted and executed. The basic format of an error response is
***HSInnnn: COMMAND (localfile:path) failed text mm/dd hh:mm
where
***HSI is the standard prefix for all HSI error messages and nnnn is the error code that uniquely corresponds to the text of the error message that follows. If the response uses more than one line, the following lines begin with one blank and an asterisk ( *).
localfile localfile, as interpreted by HPSS, could be present for error responses involving file transfers. A colon (:) separates localfile from the HPSS path in the response.
path is the complete parameter as HPSS would have interpreted it.
text is an explanation of the error and may contain relevant information from your input. Very long user input text may be shortened, and some of the text may be replaced with "...".
mm/DD hh:mm are the month, day and time (local time) the message was issued.
HSI Exit Codes contains HSI error codes and an explanation for each one.
When you work with HSI interactively or when you run a script that must handle responses from HPSS, you should be aware of some of the characteristics of error responses. Many of these are shown with examples in the following paragraphs.
Examples: Ellipsis (...) in an Error Response
An ellipsis (...) in an error response indicates that long user input has been shortened, as shown in the following example.
? set dir5=1'junefile
***HSI0340: /u/tom/subdir/z97-col...x25ly/junefile longer than
* 1024 characters. 04/26 14:39
Examples: TALK=ON and Error Responses
When TALK=ON, command information is returned within the error response. The command, fully translated path parameter, and the word "failed" are included in the response before the error message.
? get talk=on filea
***HSI0093: get /012345/filea failed
* /u/private/filea no access. 03/19 15:02
Examples: TALK=OFF and Error Responses
The following example repeats the previous error, except TALK=OFF, so that command information is not included in the response.
? Get talk=off filea
***HSI0093: /012345/filea no access. 03/19
* 15:02
The last response from HSI on UNIX systems provides an exit status whose use is oriented toward command language programmers and internal systems usage by utilities. This status is the translation of the HSI return code into an exit code (a zero exit code if the request was successful) and is used by the HSI utility on your computer to provide a locally meaningful return status for the HSI request.
If a one-liner contains only one request, the response from HSI contains the exit code equivalent of the HSI return code for that request, so that you can use your local operating system's commands and utilities to react appropriately to the exit status. For example, a shell script could test the status on a UNIX system to determine the course of action after a HSI request.
For an interactive session or a one-liner containing multiple requests, the exit code in the last HSI response is the highest exit code that was generated by any of the requests. Documentation for your system provides more information on the values and usage of these exit codes.
All output on UNIX-based systems is written to standard error (STDERR) or the current "OUT" file. In addition, if a LOG file is active, a time-stamped history of commands and responses is written.