OPSMVS 13.0 : ISPP111 Panel 'ASOTETBL' error illegal character or statement accessing OPSVIEW 2.6 panel
search cancel

OPSMVS 13.0 : ISPP111 Panel 'ASOTETBL' error illegal character or statement accessing OPSVIEW 2.6 panel

book

Article ID: 124395

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

In OPSVIEW Option menu 2.6 it is possible to operate with 'RDF Table Editor', a relational table editor to simplify saving, updating, and fetching data from relational tables. These relational tables organize the information about your system that rules and automation procedures collect.
It can happen that, trying to access this menu, after any upgrade or maintenance activity on OPSMVS, an error looking like: 

EXEC NAME ..........ASOTEAPI 
SIGL value ..............4747 
Current SUbroutine ..?Unknown? 
Return Code .............20 
Result.........................0 
...
Short/long text for ISPF message: ISPP111 : Panel 'ASOTETBL' errpr  illegal characters or statements type found in )ATTR section 
-------------------------------------- Mainline failed on line 4747 --------------------------- 

CONDITION('C') .............. 
CONDITION('D') .............. 
CONDITION('I') ..............SIGNAL 
CONDITION('S') ..............

is got and the editor is not allowed to manage RDF table. 
How to bypass this problem?
 

Environment

Z/OS - OPSMVS 

Resolution

The error got generates a SYSTERM Trace that can be analysed in order to find possible causes of the problem. If the trace contains a message looking like the following: 
 
ISPP111 : Panel 'ASOTETBL' errpr  illegal characters or statements type found in )ATTR section 

this means that the error should be researched into the panel ASOTETBL used by the affected logon procedure and that can be identified by the commands:

TSO ISRDDN
MEMBER ASOTETBL

We provide this panel in Target library CCLXPENU(ASOTETBL) and it doesn't have line numbers in cols 73-80 while it has been found that the above error could be caused by the presence of line numbers in cols 73-80 of this panel.
So, removing them will solve the problem.

In every other situation, Please open a case with Broadcom Support.