ERROR: ISPP330 BDISPMAX exceeded during running TPLSDEAJ
Article ID: 218237
Updated On:
Products
Issue/Introduction
When running the Mainframe Topology configuration job TPLSDEAJ (from the INSTJCL) and getting a BDISPMAX error.
16:52 Start of ISPF Log - - - - Session # 1 -------------------------------------------------------
16:52 TSO - Command - - %TPLBDEAL CAAPJMF.TPL.RUNTIME.INSTJCL
16:52 TSO - Command - - %TPLSDEDT
16:52 Panel ISREDDE3 message - In batch, the following message was displayed on the panel.
16:52 TPLSDEDT macro error - Command as entered: "TPLSDEDT SAVE".
16:53 ***** Dialog Error ***** - Application(ISP); Function Command (TPLBDEAL); Service(EDIT)
16:53 Line from cmd: - EDIT DATAID(ISR00001) MEMBER(TPLSALU),
16:53 BDISPMAX exceeded - 40000 displays exceeded in batch mode on panel
Environment
Release : 14.0
Component : TOPOLOGY
Resolution
The problem is in this case the statement in the TPLSDEDT macro:
ISREDIT CHANGE ALL @javahome@ +
"/sys/java64bt/v8r0m0/usr/lpp/java/J8.0_64/
The replacement value was in quotes but now the closing quote is missing. This throws the ISPF editor in a loop when in batch mode.
Check your TPLSDEDT macro and see if you are missing begin and/or ending quotes.
Correct them and rerun the job.
Additional Information
If the attempt is done interactive, the error showed is:
****************************************************************************************************
* *
* Command in error . : ISREDIT CHANGE ALL @javahome@ "/sys/java64bt/v8r0m0/u *
* *
* Incomplete string *
* Put an ending quote at the end of the string. *
* *
* Error message ID . : ISRE060 *
* *
* Last return code . : 20 *
* *
* Macro executing . : TPLSDEDT *
* *
* Press ENTER key to terminate the macro. *
* *
* *
* *
****************************************************************************************************
The possible issue is the message "Press ENTER key to terminate the macro.".
Checking the IBM manual at this page:
It says:
"When writing new dialogs or altering existing dialogs to run in the batch environment, dialog developers must be very careful not to create functions that result in a processing loop where user input is expected and none is supplied."
Feedback
