Test modes

In TEST mode, ISPF operates differently from normal mode in these ways:

Panel and message definitions are fetched again from the panel and message files when a panel name or message ID is specified in an ISPF service. In normal mode, the most recently accessed panel definitions are retained in virtual storage. If you have modified the panel or message file, use of TEST mode ensures that the latest version of each panel or message is accessed during a test run.
Using an editor to modify a panel, message, or skeleton can result in an additional DASD extent being required for the associated data set. DASD rarely (if ever) gains new extents as the result of the execution of software (with the possible exception of DASD formatting software). It can also be caused by link-editing a module. When a new extent is allocated, you can access the modification only by first terminating and then invoking ISPF again.
Tutorial panels are displayed with current panel name, previous panel name, and previous message ID on the bottom line of the display screen. This assists you in identifying the position of the panel in the tutorial hierarchy.
Screen printouts, obtained through use of the PRINT or PRINT-HI commands, include line numbers, current panel name, and message ID.
In PDF, the index listing (option 3.1) for a partitioned data set includes TTR data for each member of the data set.
If a dialog function is operating in the CANCEL error mode (the default), the panel that is displayed on an error allows you to force the dialog to continue in spite of the error. Results from that point on, however, are unpredictable and ISPF can abend.
If a dialog function is operating in any other error mode, and a command run from the SELECT service abends, any ISPF-detected error, abend, or program interrupt forces an abend of ISPF. You can also force an abend by entering ABEND or CRASH in the command line of any panel. For more information about the SELECT service, refer to the z/OS ISPF Services Guide.
The PA1 key causes an immediate exit from ISPF.

The ISPF controller task attaches one ISPF subtask for each logical screen. Any additional logical screens are created by the SPLIT command and there can be up to four screens on a 3290 terminal.

If an ISPF subtask abends, pressing Enter after the abend message appears generates a dump, provided that a SYSUDUMP, SYSMDUMP, or SYSABEND data set has been allocated.

Dialogs invoked with the SELECT CMD(XXX) cause an attach of a new subtask under the ISPF subtask. If an abend occurs under the new subtask, an immediate dump is taken.

In TESTX mode, ISPF operates the same as it does in TEST mode, except that all messages written to the ISPF log file are also displayed at the terminal.

ISPF provides the ENVIRON command, which allows you to cause a dump following an abend condition, even if ISPF is not running in TEST mode. See Using the ENVIRON system command for a description of using the ENVIRON command.