DEBUGUL parameter: Difference between revisions
(adding Usage section and text that seems to have been missed during wiki conversion) |
|||
| Line 18: | Line 18: | ||
<p>The DEBUGUL settings and their effects are: </p> | <p>The DEBUGUL settings and their effects are: </p> | ||
<table> | <table> | ||
<tr><th>Setting</th><th>Displays procedure list...</th></tr> | <tr class="head"><th>Setting</th><th>Displays procedure list...</th></tr> | ||
<tr><th align="right"><var>X'20'</var></th><td>After warning messages about truncation for User Language WITH operator string concatenations greater than 255 bytes </td></tr> | <tr><th align="right"><var>X'20'</var></th><td>After warning messages about truncation for User Language WITH operator string concatenations greater than 255 bytes </td></tr> | ||
<tr><th align="right"><var>X'10' </var></th><td>Debug messages on user's terminal in addition to audit trail.</td></tr> | <tr><th align="right"><var>X'10' </var></th><td>Debug messages on user's terminal in addition to audit trail.</td></tr> | ||
| Line 25: | Line 25: | ||
<tr><th align="right"><var>X'02'</var></th><td>After counting errors that do not terminate execution of the request </td></tr> | <tr><th align="right"><var>X'02'</var></th><td>After counting errors that do not terminate execution of the request </td></tr> | ||
<tr><th align="right"><var>X'01' </var></th><td>After informational messages </td></tr> | <tr><th align="right"><var>X'01' </var></th><td>After informational messages </td></tr> | ||
<tr><th><var>Any nonzero</var></th><td>After a snap or a dump</td></tr> | <tr><th nowrap><var class="term">Any nonzero</var></th><td>After a snap or a dump</td></tr> | ||
<tr><th align="right"><var>X'00'</var></th><td>Does not display procedure list</td></tr> | <tr><th align="right"><var>X'00'</var></th><td>Does not display procedure list</td></tr> | ||
</table> | </table> | ||
| Line 35: | Line 35: | ||
====How the MSGCTL command can override both the MSGCTL and DEBUGUL parameters==== | ====How the MSGCTL command can override both the MSGCTL and DEBUGUL parameters==== | ||
<p>If you use the <var>[[MSGCTL_command|MSGCTL]]</var> command, and suppress the display of a message by using the NOTERM keyword, then no matter how the MSGCTL or DEBUGUL parameters are set, the message does not go to the terminal. Conversely, if you want messages displayed at the terminal, enter MSGCTL command using the following syntax: </p> | <p>If you use the <var>[[MSGCTL_command|MSGCTL]]</var> command, and suppress the display of a message by using the NOTERM keyword, then no matter how the MSGCTL or DEBUGUL parameters are set, the message does not go to the terminal. Conversely, if you want messages displayed at the terminal, enter MSGCTL command using the following syntax: </p> | ||
<p class="code">MSGCTL {M204 | USER}.< | <p class="code">MSGCTL {M204 | USER}.<var class="term">msg-number</var> TERM </p> | ||
</p> | <p><strong>Where:</strong></p> | ||
<ul> | |||
<li>M204 or USER specifies either Model 204 or User defined message, respectively</li> | |||
<li><var class="term">msg-number</var> is the 4-digit number of the message</li> | |||
<li>TERM displays the specified error message on the user’s terminal, when appropriate</li> | |||
</ul> | |||
<p><strong>DEBUGUL parameter and QTBL size</strong></p> | |||
<p>Setting the DEBUGUL parameter to anything other than 0 significantly increases QTBL. | |||
Increases in STBL and VTBL are dependent on how many INCLUDEs the procedure does | |||
because of the storage described here:</p> | |||
<table> | |||
<tr class="head"><th>Table name</th><th>Stores</th></tr> | |||
<tr><td>QTBL</td> <td>An extra word for every QUAD in the request</td></tr> | |||
<tr><td>STBL</td> <td>Procedure names</td></tr> | |||
<tr><td>VTBL</td> <td>Chain storage for file and procedure pointers</td></tr> | |||
</table> | |||
====Usage in production==== | |||
<p>A UTABLE command can handle the additional space requirements before the request is | |||
compiled. Although there is a storage penalty for using the DEBUGUL parameter, there is no evaluation time penalty in CPU unless an error that you are debugging is reported on.</p> | |||
====Rocket Software recommends==== | |||
<p>Set this parameter in User 0’s CCAIN only if the job is not set up to use subsystems (SYSOPT does not include the 1-bit setting). Procedures that are run for APSY subsystem initialization do not allow for the extra compiler table requirements needed when DEBUGUL is set.</p> | |||
<ul> | |||
<li>If you are not using APSY, you can set DEBUGUL in the CCAIN.</li> | |||
<li>If you are using APSY, you can set DEBUGUL: | |||
<ul> | |||
<li>On IODEV lines</li> | |||
<li>In APSY subsystem login procedures</li> | |||
<li>In user procedures</li> | |||
</ul></li> | |||
</ul> | |||
[[Category:User parameters]] | [[Category:User parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 20:03, 29 March 2017
User language debug options
Summary
- Default value
- X'00'
- Parameter type
- User
- Where set
- By any user
- Related products
- All
- Introduced
- Model 204 V6.1 or earlier
Description
Included procedures can accompany evaluation time Model 204 error messages
You can display the names of the procedures that were included up to the point of the evaluation time error on the audit trail or at your terminal.
The DEBUGUL settings and their effects are:
| Setting | Displays procedure list... |
|---|---|
| X'20' | After warning messages about truncation for User Language WITH operator string concatenations greater than 255 bytes |
| X'10' | Debug messages on user's terminal in addition to audit trail. |
| X'08' | After errors (other than counting errors) that terminate execution of the request |
| X'04' | After counting errors that terminate execution of the request |
| X'02' | After counting errors that do not terminate execution of the request |
| X'01' | After informational messages |
| Any nonzero | After a snap or a dump |
| X'00' | Does not display procedure list |
DEBUGUL and error messages display
When DEBUGUL is set to x'10', Model 204 forces the error message along with the DEBUGUL messages to the user's terminal regardless of the setting of MSGCTL. However, if an error message is normally suppressed from going to the user's terminal through the use of NOTERM (or by default it is not displayed) then the DEBUGUL messages are suppressed regardless of the setting of DEBUGUL.
How the DEBUGUL parameter can override the MSGCTL parameter
If you have set the MSGCTL parameter to a value that suppresses the message, AND set the DEBUGUL parameter to a value where the X'10' bit is on, then the DEBUGUL parameter setting forces the message to the terminal, even though the MSGCTL parameter setting says not to.
How the MSGCTL command can override both the MSGCTL and DEBUGUL parameters
If you use the MSGCTL command, and suppress the display of a message by using the NOTERM keyword, then no matter how the MSGCTL or DEBUGUL parameters are set, the message does not go to the terminal. Conversely, if you want messages displayed at the terminal, enter MSGCTL command using the following syntax:
MSGCTL {M204 | USER}.msg-number TERM
Where:
- M204 or USER specifies either Model 204 or User defined message, respectively
- msg-number is the 4-digit number of the message
- TERM displays the specified error message on the user’s terminal, when appropriate
DEBUGUL parameter and QTBL size
Setting the DEBUGUL parameter to anything other than 0 significantly increases QTBL. Increases in STBL and VTBL are dependent on how many INCLUDEs the procedure does because of the storage described here:
| Table name | Stores |
|---|---|
| QTBL | An extra word for every QUAD in the request |
| STBL | Procedure names |
| VTBL | Chain storage for file and procedure pointers |
Usage in production
A UTABLE command can handle the additional space requirements before the request is compiled. Although there is a storage penalty for using the DEBUGUL parameter, there is no evaluation time penalty in CPU unless an error that you are debugging is reported on.
Rocket Software recommends
Set this parameter in User 0’s CCAIN only if the job is not set up to use subsystems (SYSOPT does not include the 1-bit setting). Procedures that are run for APSY subsystem initialization do not allow for the extra compiler table requirements needed when DEBUGUL is set.
- If you are not using APSY, you can set DEBUGUL in the CCAIN.
- If you are using APSY, you can set DEBUGUL:
- On IODEV lines
- In APSY subsystem login procedures
- In user procedures