SetBlackList command: Difference between revisions
(Created page with "__TOC__ {| |width="50%"| '''Action:''' |width="50%"| <span class="f_Para">Lets you dynamically specify or clear a procedure Black List, whi...") |
No edit summary |
||
| Line 4: | Line 4: | ||
|width="50%"| '''Action:''' | |width="50%"| '''Action:''' | ||
|width="50%"| | |width="50%"| | ||
<span class="f_Para">Lets you dynamically specify or clear a procedure [[ | <span class="f_Para">Lets you dynamically specify or clear a procedure [[Running only to listed procedures|Black List]], which identifies the outer procedures you do </span>''not''<span class="f_Para"> want the Debugger to debug. These procedures get executed but their code is not sent to or displayed in the Client. This command temporarily overrides any existing Black List, but it </span><span class="f_Notes">does </span>'''not'''<span class="f_Notes"> physically affect the contents of the black list file stored on disk </span><span class="f_Para">(</span><span class="f_Monospace">blacklist.txt</span><span class="f_Para">)</span><span class="f_Notes">. The command's effect is not persistent over runs of the Client.</span><span class="f_Para"> </span> | ||
'''Syntax:''' | '''Syntax:''' | ||
| Line 10: | Line 10: | ||
<p class="syntax">setBlackList [''proc''] ... </p> | <p class="syntax">setBlackList [''proc''] ... </p> | ||
where ''proc'' is one of possibly multiple, blank separated, procedure file names. Name matching is case insensitive, and [[ | where ''proc'' is one of possibly multiple, blank separated, procedure file names. Name matching is case insensitive, and [[Running to a specific procedure#Shortcuts for specifying procedure names|wildcards]] are allowed. | ||
<span class="f_Para">If no names are specified, the current black list, if any, is treated as empty. If one or more procedure names are specified, the contents of the black list are overridden by this new set of procedure names. </span> | <span class="f_Para">If no names are specified, the current black list, if any, is treated as empty. If one or more procedure names are specified, the contents of the black list are overridden by this new set of procedure names. </span> | ||
| Line 17: | Line 17: | ||
# Put it in a User Language procedure. | # Put it in a User Language procedure. | ||
# Send it to the Client via the [[ | # Send it to the Client via the [[TN3270 DEBUG Syntax|TN3270 DEBUG CLIENTCOMMAND]] Model 204 command. | ||
<span class="f_Para">Doing this lets you have a mainframe based testing harness that sets up a list on the Client. For example: </span> | <span class="f_Para">Doing this lets you have a mainframe based testing harness that sets up a list on the Client. For example: </span> | ||
Revision as of 03:30, 9 December 2022
| Action: |
Lets you dynamically specify or clear a procedure Black List, which identifies the outer procedures you do not want the Debugger to debug. These procedures get executed but their code is not sent to or displayed in the Client. This command temporarily overrides any existing Black List, but it does not physically affect the contents of the black list file stored on disk (blacklist.txt). The command's effect is not persistent over runs of the Client. Syntax: setBlackList [proc] ... where proc is one of possibly multiple, blank separated, procedure file names. Name matching is case insensitive, and wildcards are allowed. If no names are specified, the current black list, if any, is treated as empty. If one or more procedure names are specified, the contents of the black list are overridden by this new set of procedure names. You might use this command for testing:
Doing this lets you have a mainframe based testing harness that sets up a list on the Client. For example: TN3270 DEBUG CLIENTCOMMAND 'setBlackList P.SHEMP' TN3270 DEBUG CLIENTCOMMAND 'turnOnBlackList' See also the setWhiteList command. |
| Client menu: | -- |
| Introduced: | Build 62 |