Rational Developer for System z

Generation properties of the FEPI invoke type

This topic describes the generation properties of the FEPI invoke type.
Important: A FEPI invoke node can validly occur only within a FEPI flow node (see About flow types).

The FEPI invoke type causes the specified screen operation to communicate with the terminal application using the FEPI interface. (FEPI, which stands for "front-end programming interface", is a separately-installable function of CICS® Transaction Server that enables communication with non-LU6.2 partners by simulating an LU0 or LU2 device.)

For more information about these generation properties see the CICS Service Flow Runtime User's Guide (see Supported runtime environments for each project type).

Table 1. Generation properties of the FEPI invoke type
NAME DESCRIPTION VALUE RANGE DEFAULT VALUE
Invoke Type Type of invoke node FEPI FEPI
Activity Name Name of the activity performed by the node.
Note: When the runtime code is generated for the CICS Service Flow Runtime environment, the runtime code generator uses the information in this node to create a CICS Business Transaction Services (BTS) activity. The name that you specify here is used as the name of the new BTS activity.
String value: 1-32 characters Node ID
Comment Optional text associated with the individual node N/A N/A
Skip Receives

Typically an application does not transmit a screen to a terminal until the terminal sends another input message to the application.

But in certain situations an application can transmit multiple screens to a terminal without waiting for the terminal to send input in return. Usually this is an isolated occurrence and involves only a few extra screens transmitted by the terminal application.

You can handle this situation in an individual FEPI node by setting the Skip Receives generation property for the FEPI node to a value equal to the number of received screens that you want the FEPI node to ignore. For example, if the application transmits three screens in response to the terminal sending a single input message, you can set the Skip Receives property to 2. This causes the FEPI node to ignore the first two screens and to process the third.

After the terminal has received the final screen, the contents of the screen are available to be mapped into messages in the flow. None of the information in the skipped screens is available to be mapped into messages in the flow.

0-32767 0

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)