|
|
 |
CICS Help Request Appears to be Ignored
When a user positions their cursor and presses
the Help request key defined for their CICS application, the keyboard
locks and then unlocks. Nothing else happens. The user appears
to have never left their CICS application.
The first step to trouble shoot this situation
is to perform a PREFERENCE Trace on this help request. Details
on how to perform a PREFERENCE Trace can be found at "Instructions
for getting a PREFERENCE Trace." If PREFERENCE Trace information
is filled in after issuing the Help Request, then research the
PREFERENCE Rules that are identified.
If the PREFERENCE Trace Table does not contain
any information following the Help Request, then verify that the
"Terminal ID" specified in the PREFERENCE Trace Table will match
the Help Requestor's "Terminal ID". If this is found to be a problem,
then modify the "Terminal ID" setting in the PREFERENCE Trace
Table and retry the Help Request. Then perform the following steps
if the Trace Table is still empty:
- From the Supervisor Type Command line type
"setdump on" and press ENTER
- You should receive a response message of
"DIAGNOSTIC DUMP ON"
- Have the user retry issuing the Help Request.
- If the user receives a GD024 error message,
then this is an indication that the "CICS TYPE TERM" definition
has a "Receive Size" that is too short to accommodate a full
Read Buffer DataStream.
To rectify this problem the "CICS TYPE TERM"
definition needs to specify a larger "Receive Size". If help is
working from some CICS regions but receives this failure from another,
we recommend that you compare the "CICS TYPE TERM" definitions for
each CICS region involved and increase the "Receive Size" to a value
known to work. As an example a model 2 (24 x 80) application needs
1920 bytes just for data. Add to that the Aid character and the
cursor address and you have an additional 3 bytes. If the application
screen contains multiple input and protected fields, the length
requirement will increase again. Finally if the screen contains
extended attributes such as color or highlighting, the length requirement
will increase again. Thus for a model 2 application screen-size
the "Receive Size" may easily require 2000 - 3000 bytes. If larger
screen-size applications are to be supported (such as a model 4
- 43 x 80), then the "Receive Size" requirement would be even larger.
|
|
|
Order
Your Upgrade Today!