z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

Files
Localization
Usage notes
Exit Values
yacc uses the following files:
/usr/lib/liby.a
yacc function library.
/usr/lib/libyxp.a
yacc archive library with functions compiled with XPLINK. Includes two
versions: 64-bit addressing mode and 31-bit addressing mode.
y.output
Default statistics file when you specify -v.
y.tab.c
Default file for the generated parser.
y.tab.h
Default header file when you specify –d.
/etc/yyparse.c
Default parser template.
yacc uses the following localization environment variables:
v LANG
v LC_ALL
v LC_CTYPE
v LC_MESSAGES
v LC_SYNTAX
v NLSPATH
See Appendix F for more information.
In a doublebyte environment, yacc can use doublebyte characters, although this
practice is possibly nonportable.
1. Comments and rule names can contain doublebyte characters.
2. Doublebyte characters can be used in symbolic token names (generated by
%token statements only if the C preprocessor and compiler will interpret them
correctly. Symbolic token names are converted directly into #define statements
and are then interpreted by the preprocessor and the compiler.
3. You can use doublebyte characters as literal token definitions (a doublebyte
character surrounded by apostrophes), although this will generate a warning
and may create a conflict with an assigned token name.
0 Successful completion
1 Failure due to any of the following:
v number rules never reduced
v Reduce-reduce conflict
v Shift-reduce conflict
v NAME should have been defined earlier
v \000 not permitted
v EOF encountered while processing %union
v EOF in string or character constant
v EOF inside comment
v Use of $number not permitted
v Nonterminal number, entry at number
v Action does not terminate
yacc
Chapter 2. Shell command descriptions 821