Rational Developer for System z, Version 7.6

FEPI flow type -- additional generation properties

This topic describes the additional generation properties that are available for a flow node with the flow type of FEPI.

FEPI (which stands for "front-end programming interface") is a separately installable function of CICS® that enables communication with non-LU6.2 partners by simulating an LU0 or LU2 device.

When you set the flow type of the flow node in a generation properties file to FEPI, this causes the Generate Runtime Code wizard (when you run it on that generation properties file) to tailor the contents of the generated output files so that the resulting runtime program uses the FEPI interface to communicate with the target terminal application.

Important: You should be aware of the following:

The generation properties described in this help topic for the FEPI flow type are in addition to the common generation properties that are available for all three flow types (see Common generation properties of all three flow types).

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. Additional generation properties for a FEPI flow
NAME DESCRIPTION VALUE RANGE DEFAULT VALUE
Initial PFKey If applicable, this is the PFKey issued prior to executing the Startup Transaction. This is typically used to CLEAR a screen so that the transaction can be run from a native CICS screen. Clear, Enter, PF1-PF24, PA1-PA3, TESTREQ, SYSREQ Blank
Startup Transaction Data

The first 4 characters that you type into this field specify the transaction ID that is required to start the 3270 application.

You can type additional text after the transaction ID up to a maximum of 160 characters.

Optionally, instead of typing the information directly into this field you can click the Select button and select a variable in the input message of the flow in which the transaction ID and any additional text are stored.1

String value. Cannot be blank. Cannot have leading or embedded spaces within the first 4 characters. Blank
Use LU Owner/Pass Ticket Select to allow the flow to generate a UserID and Pass Ticket for signing on to the back end region. N/A Not selected
Pool Name used to establish the connection and conversation with a target application String value: 1-8 characters. Cannot be blank. Cannot have leading or embedded spaces. N/A
Target Target application for which a conversation and connection should be established or attempted to be established N/A Blank
Timeout Amount of time, in seconds, that the FEPI Pool will wait for a session to become available or that the FEPI Receive or Converse Datastream will wait for the requested data to arrive before timing out. Can be 0 30 seconds
Logoff Type Indicates what action, if any, should be taken on the connection or conversation when exiting the FEPI navigator. Determines and controls processing related to the SLU Connection and Target Interaction files.
  • Release: Sets connection to Released
  • Force: Causes FEPI to end the conversation unconditionally. Attempts to reset the connection used by the conversation.
  • Pass: Causes a task to release ownership of a conversation so another task can acquire it. Connection does not remain assigned to a user when exiting the runtime Navigator.
  • Hold: Ends the conversation but keeps the connection for other conversations. Attempts to reset the connection used by the conversation.
  • Assigned: Causes a task to release ownership of the conversation so another task can acquire it. Connection remains assigned to a user when exiting the runtime Navigator.
"R" (Release)
Allow Non-Unique User Select to allow LU assignment processing for non-unique user ids. N/A Not selected
Table notes:
  1. To specify a variable in the input message of the flow:
    1. Click the Select button to the right of the Startup Transaction Data field.
    2. Select the variable in the Element Selection window.
    3. Click OK.

    Caution: You cannot specify a variable name by typing it directly into the Startup Transaction Data field. Any text that you type into the Startup Transaction Data field is treated as a 4-character transaction ID followed by any additional text.

    When you specify a variable name the text in the variable is not subject to the 160-character limitation that exists when you type the text directly into the Startup Transaction Data field.

    The variable must have an Occurs property of 1.


Terms of use | Feedback

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