APP2
Explanation
The length of data that has been passed to DFHP3270 via temporary storage is less than or equal to 5.
System action
The transaction is abnormally terminated with a CICS transaction dump.
User response
Check the user DFHTEP. If it is not at fault, submit an APAR.
If this abend has occurred, the data that DFHP3270 obtained from temporary storage was probably put there with an incorrect length. The user may have requested indirectly that this data be placed in temporary storage either by an application request for printing (for example ISSUE PRINT) or by pressing the Print Request key. However, CICS should control the data length for this request. Under normal circumstances, the only way the user could have requested directly that data is to be placed in temporary storage is in the user's TEP. The user should check any invocations of DFHIC TYPE=PUT in handling print requests, particularly when dealing with the printer unavailable or busy
condition, and ensure that the length field is set correctly.
Problem determination
Register 6 points to the data retrieved from temporary storage via a DFHIC TYPE=GET macro invocation. The layout of this data is:
-
Terminal data area length (2 bytes)
-
Write control indicator (1 byte)
-
Write control or carriage control character (1 byte)
-
Data (variable length)
Analysis: DFHP3270 has been called to handle a print request from a 3270 Information Display System terminal. It obtains from temporary storage the data to be printed, via a DFHIC TYPE=GET invocation. It ensures that some data to be printed is present. The area returned from temporary storage contains the data to be printed preceded by 4 bytes as described above. DFHP3270 has found that, because the length of data passed to it is less than or equal to 5, there is no data to be printed.
Module
DFHP3270Applicable releases in Version 6
- beta
- 6.3
- 6.2
- 6.1