ContentsIntroductionHip Commands Using Hip Messages Examples Limits Warnings Support Future |
MessagesError messages are displayed on the standard error output, so they may be interspersed in the output. If any error conditions or warnings occur, the return code for HIP will be set greater than zero. The following table summarizes the possible messages and return values. RC Message/notes -- --------------------------------------------------- 0 (no message) all went well 1 (no message) An invalid HIP command was encountered and ignored. (i.e. <!--HIPPOS on parade -->) This may be a typo in the HIP command, a stray end line, or an unrelated comment just starting like HIP commands. The line is tagged with a comment by prepending the phrase <!-- skip --> and is copied into the final output. Note that errors in the top level file are not tagged, just copied. 2 (no message) An invalid HIP command was encountered and ignored. (i.e. <!--HIP ignores this -->) This is just like the preceding error, only the start tag was valid but the directive didn't make sense. 5 filename failed to load The specified file was not found. The command generating this error is tagged and copied into the output (unless the file was specified on the command line, in which case, no output occurs.) 5 Usage: ... No filename was specified on the command line. 10 filename nested too deep Nesting is stopped at an arbitrary depth to prevent looped includes. Expansion stops, as if the included file was not found. 20 *** Halting due to sever error *** Sever errors will cause a hasty exit from HIP and display this message in addition to any others. 20 (no message) Memory allocation failed. 20 Error during file writing (DISK FULL?) A write to the output file generated an error. Most probably a disk full condition. 20 Open filename for output failed The open for file filename failed while trying to write the results of the HIP process. Lack of write permission or read-only attribute are likely. 20 Error closing filename Closing the output file generated an error. Most probably a disk full condition. |
|
|