ABMB
Explanation
The user has specified a cursor position in the BMS output request. It is larger than the current screen size for the 3270 for which output is being built.
System action
The transaction is abnormally terminated with a CICS transaction dump.
User response
Correct the program that specified the incorrect cursor location.
Use trace to identify the statement issuing the request. Check that the cursor position is being correctly set. The program may have been designed to run in alternate screen size mode but is being run in default screen size mode, or it may have been designed to run on a 3270 model different from the one in use. If the program is routing a message, the route list should be checked. If the program is to run with various 3270 models, the cursor position should be within the size of the smallest screen.
Problem determination
If the abend occurs in DFHPBP:
At the time of the abend, register 2 points to the OSPWA and register 1 to the TTP. Relevant fields are:
-
OSPTR3 has X'10' bit set to indicate a user-specified cursor position
-
OSPCP contains a halfword cursor position specified by user
-
TTPSCSZ contains the halfword value of the screen size to compare against.
If the abend occurs in DFHMCP or DFHMCX:
-
Register 6 points to the OSPWA (in LIFO storage)
-
OSPCP contains a halfword cursor position specified by user
-
OSPTR3 has X'10' bit set to indicate a user-specified cursor position
-
OSPSCSZ contains the halfword value of the screen size to compare against.
Analysis:
Register Label Description
In DFHPBP:
R2=@OSPWA PBDBADC OSPTR3 X'10' bit set
indicates the user-
R1=@TTP specified cursor
position.
TTPSCSZ halfword screen
size.
OSPCP halfword cursor
position.
In DFHKCP or DFHMCX:
R6=@OSPWA MCENEAU2 OSPTR3 X'10' bit set
indicates the user-
specified cursor
position.
OSPSCSZ halfword screen
size.
OSPCP halfword cursor
position.