SetWhiteList 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 White List, whi...") |
No edit summary |
||
| Line 22: | Line 22: | ||
<span class="f_CodeExample">TN3270 DEBUG CLIENTCOMMAND 'turnOnWhiteList' </span> | <span class="f_CodeExample">TN3270 DEBUG CLIENTCOMMAND 'turnOnWhiteList' </span> | ||
<span class="f_Para">See also the </span><span class="f_Monospace">[[ | <span class="f_Para">See also the </span><span class="f_Monospace">[[SetBlackList command|setBlackList]]</span><span class="f_Para"> command. </span> | ||
|- | |- | ||
| '''Client menu:''' | | '''Client menu:''' | ||
Revision as of 17:46, 8 July 2022
| Action: |
Lets you dynamically specify or clear a procedure White List, which explicitly identifies the outer procedures you want the to debug. Unlisted procedures get executed, but their code is not sent or debugged. This command overrides any existing White List, but it does not physically affect the contents of the white list file stored on disk (whitelist.txt). The command's effect is not persistent over runs of the Client. Syntax: setWhiteList [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 white list is treated as empty. If one or more procedure names are specified, the contents of the white list are overridden by this new set of procedure names. You might use this command for testing by putting it in a User Language procedure and sending that to the client via the existing TN3270 DEBUG CLIENTCOMMAND Model 204 command. Doing this lets you have a mainframe based testing harness that sets up a white list on the Client. For example: TN3270 DEBUG CLIENTCOMMAND 'setWhiteList P.MOE P.LARRY' See also the setBlackList command. |
| Client menu: | -- |
| Introduced: | Build 62 |