A list of actions that cannot be carried out when using
an EPI user application.
A CICS® transaction that
sends data to an EPI user application cannot:
- Use 14- and 16- bit addresses and structured fields, because the CICS Transaction Gateway supports
only the ASCII-7 subset of the 3270 data stream architecture. Only
12-bit SBA addressing is supported. Consequently, the maximum screen
size for EPI terminals is 27 rows by 132 columns.
- Use the purge function to cancel ATI requests queued against
the terminal. If a CICS transaction
uses EXEC CICS START with the
DELAY option to schedule transactions to a terminal resource autoinstalled
by a user application, the user application should ensure that delayed
ATI requests are not lost when the terminal resource is deleted. See
your server documentation to determine the effects of deleting a terminal
resource when delayed ATI requests are outstanding.
An EPI user application cannot:
- Use basic mapping support (BMS) paging.
- Determine the alternative screen size of the terminal resource
definition, although it can determine the default screen size.
An EPI user application communicating with CICS Transaction Server for iSeries® cannot:
- Support languages that use DBCS.
- Support sign-on capable terminals.
- Start the CEDA transaction from a client terminal.
- Use PF1 to get CICS online
help from a client terminal.