|
| Diagnostic Messages |
|
| Error Messages |
| CAUSE | The name being defined already has a |
|
| definition. Each identifier can only |
|
| have one legal meaning. You can't |
|
| define both a space and a subspace |
|
| with the same name. |
| ACTION | Change the name used by one of the |
|
| definitions to a unique name. |
1027 | MESSAGE | This item must be declared |
|
| within a space |
| CAUSE | A directive such as .SUBSPA, is used |
|
| before the first .SPACE directive. |
| ACTION | Insert a valid .SPACE directive prior |
|
| to the offending directive. |
1028 | MESSAGE | Subspace name required |
| CAUSE | .SUBSPA directive is not followed by |
|
| a valid name. |
| ACTION | Follow .SUBSP directive with a valid |
|
| name. |
1029 | MESSAGE | Directive .%s must occur |
|
| within a procedure |
| CAUSE | Directive such as .CALLINFO, |
|
| .ENTER or .LEAVE is used outside of |
|
| a procedure. A procedure is defined |
|
| by a matching pair of .PROC, |
|
| .PROCEND directives. |
| ACTION | Move the offending directive inside a |
|
| procedure or correct the location of |
|
| the .PROC and .PROCEND directives |
|
| for this procedure. |
1030 | MESSAGE | Only one .CALLINFO per |
|
| procedure |
| CAUSE | Multiple .CALLINFO directives were |
|
| found within a procedure. A |
|
| procedure is defined by a matching |
|
| pair of .PROC, .PROCEND directives. |
Chapter 8 | 159 |