If a command processor exists only in LPA, there must be an entry in the ISPTCM for the command processor. See z/OS ISPF Planning and Customizing for more details on customizing the ISPF TSO command table.

If the LIBRARY parameter is used with a table service, the user is not able to free the ddname for the table library pointed to by the LIBRARY parameter. ISPF keeps this library open until a new ddname is used in the LIBRARY parameter with another table service. ISPF functions in this manner for performance reasons.

Issuing a table service with a LIBRARY parameter containing a ddname that does not exist causes the previous library to be closed and therefore allows the user to free the previous ddname. Use of CONTROL ERRORS RETURN may be used to guard against a severe error as a result of a ddname not existing.

    ALLOC FILE(DD1) DATASET('USERID.YOUR.TABLES') SHR
    ISPEXEC TBOPEN MYLIB LIBRARY(DD1)
    .
    .                                   /*ISPF services against your table*/
    .
    ISPEXEC TBCLOSE MYLIB LIBRARY(DD1)
    ISPEXEC CONTROL ERRORS RETURN
    ISPEXEC TBOPEN JUNK LIBRARY(DDJUNK) /*nonexistent table in a  */
                                        /*nonexistent library     */
    ISPEXEC CONTROL ERRORS CANCEL
    FREE F(DD1)

or:

ISPP121 Panel 'name' error–Panel definition too large, greater than screen size.

when entering KEYLIST, when requesting field-level help in ISPF panels, or when displaying panels created using DTL.

These messages are often caused by having a GML library in the ISPPLIB concatenation or by having GML source code in the panel library. Check your ISPPLIB concatenation to make sure that the ISPF-supplied GML library is not concatenated first. The ISPF-supplied GML library should not be in any of the ISPF library concatenations. Make sure that the libraries in your ISPPLIB concatenation do not contain GML source code.

This message frequently occurs when batch jobs that use ISPF services run concurrently. This occurs because most batch jobs allocate a new profile each time they run. ISPF issues a TBOPEN against ISPPROF DD card for member ISPSPROF. The TBOPEN fails since ISPPROF does not contain this member. ISPF then issues a TBOPEN against ISPTLIB to copy the default ISPSPROF from ISPTLIB to ISPPROF.

If the first data set in the ISPTLIB concatenation sequence is the same for two batch jobs running concurrently, message ISPT036 is issued. To ensure that this condition does not occur, the first data set in the ISPTLIB concatenation should be user unique. For example, 'sysuid..ISPPROF' would be a user unique data set, which could be used as the first data set concatenated to the ISPTLIB DD.

For the same reasons, this problem can also occur when two users log on to ISPF for the first time if they have the same data set concatenated first in the ISPTLIB concatenation.

ISPF has various messages that reference I/O errors on either GET or PUT (READ and WRITE macros) such as message ISPT017. These errors are typically caused by concatenation problems on one of the ISPF libraries.

I/O error messages cannot be issued when there is a problem with the ISPMLIB concatenation since messages cannot be located due to the I/O error. Message CMG999 occurs when there is an I/O error due to an ISPMLIB concatenation problem.

CMG999 is issued with an appropriate description of the error condition for any problem with accessing a message. See z/OS ISPF Dialog Developer's Guide and Reference for further information on how to define a message.