HP 3000 Manuals HP 3000 Manuals
Error Messages
1 AMBIGUOUS INPUT REDIRECT
More than one input redirection character ( < ) appears in the INFO
string. For example,
RUN prog; INFO="< infile1 < infile2"
Remove one of the input redirection specifiers.
2 AMBIGUOUS OUTPUT REDIRECT
More than one output redirection character ( > ) appears in the INFO
string. For example,
RUN prog; INFO="> outfile1 > outfile2"
Remove one of the output redirection specifiers.
3 BAD NAME FOR REDIRECT
The file name specified for input/output redirection in the INFO string
does not begin with an asterisk ( * ), a dollar sign ( $ ), or an
alphabetic character. For example,
RUN prog; INFO="> 2badfile"
Specify a valid file name for input/output redirection.
4 MISSING NAME FOR REDIRECT
An input/output redirection character ( < or > ) appears in the INFO
string but no corresponding file name is specified. For example,
RUN prog; INFO="<"
Specify a file name for the redirection.
5 UNMATCHED QUOTE WITHIN INFO STRING
A quoted string within the INFO string contains a beginning quote but no
matching end quote. For example,
RUN prog; INFO="'quoted string"
Add a matching end quote to the quoted string.
6 REDIRECTION OF STDIN FAILED
The file specified for input redirection in the INFO string can not be
opened. For example,
RUN prog; INFO="< badfile"
where badfile does not exist.
Check to see if the file specified for redirection exists and is
accessible for reading by the user invoking the program.
7 REDIRECTION OF STDOUT FAILED
The file specified for output redirection in the INFO string can not be
opened. For example,
RUN prog; INFO="> badfile"
where badfile can not be opened for writing.
Check to see if the file specified for redirection is accessible for
writing by the user invoking the program.
9 NO FILES FOUND IN FILE-SET
A file-set wildcard specified in the INFO string did not match any files.
For example,
RUN prog; INFO="@.nofiles"
where nofiles is a group containing no files.
Check to see if the file-set wildcard represents a non-empty file-set.
10 ERROR IN EXPANDING FILE-SET WILDCARD
The file-set wildcard expander encountered an error in trying to expand a
file-set wildcard in the INFO string. For example,
RUN prog; INFO="@.badgroup"
where badgroup is a non-existent group.
Check to see if the file-set wildcard represents a valid file-set.
Table B-0. (cont.)
12 INFO STRING ARG LIST TOO LONG
The number of arguments (argv elements) specified in the INFO string
exceeds the 1023 argument limit. For example,
RUN prog; INFO="@.@.@"
where the file-set @.@.@ contains more than 1023 files.
Reduce the number of arguments specified in the INFO string.
13 AMBIGUOUS USE OF QUOTES WITHIN INFO STRING
A quote character that is not a closing quote or an escaped quote is
specified within a quoted string in the INFO string. For example,
RUN prog; INFO="'abcd'e"
The quote character between the characters d and e is not considered a
closing quote because the character following it is not a valid string
terminator, such as a space, tab or redirection character.
Insert a string terminator character after the closing quote. For
example,
RUN prog; INFO="'abcd' e"