FEPI property set definitions - FEPRODEF

The FEPI property set definition (FEPRODEF) views display information about the physical and operational characteristics of FEPI property set definitions.

Supplied views

To access from the main menu, click:

Administration views > CICS resource definitions > FEPI property set definitions

Table 1. Views in the supplied FEPI property set definitions (FEPRODEF) view set
View Notes
FEPI property set definitions

EYUSTARTFEPRODEF.ADDTOGRP

Add one or more FEPI property set definitions to a resource group.
FEPI property set definitions

EYUSTARTFEPRODEF.CREATE

Create a FEPI property set definition and add it to the data repository.
FEPI property set definitions

EYUSTARTFEPRODEF.DETAILED

Detailed information about a selected FEPI property set definition.
FEPI property set definitions

EYUSTARTFEPRODEF.INSTALL

Install a FEPI property set definition in an active system.
FEPI property set definitions

EYUSTARTFEPRODEF.REMOVE

Remove a FEPI property set definition from the data repository.
FEPI property set definitions

EYUSTARTFEPRODEF.TABULAR

Tabular information about all FEPI property set definitions for the current context.

Actions

Table 2. Actions available for FEPRODEF views
Action Description
ADDTOGRP Add one or more FEPI property set definitions to a resource group.
CREATE Create a FEPI property set definition and add it to the data repository.
INSTALL Install a FEPI property set definition in an active system.
REMOVE Remove a FEPI property set definition from the data repository.
UPDATE Update a FEPI property set definition in the data repository.

Fields

Table 3. Fields in FEPRODEF views
Field Attribute name Description
Begin-session transaction BEGINSESSION (Optional.) Specify the name of the transaction that will perform begin-session processing, immediately after a session has been established. If this option is omitted, there is no user-supplied begin-session processing.
Last modification agent CHANGEAGENT The change agent identifier that made the last modification.
  • DREPAPI - Resource was last changed by a CICSPlex SM API command.
Last modification agent release CHANGEAGREL The CICS release level of the agent that made the last modification.
Last modification time CHANGETIME The local date and time when the definition was last changed.
Last modification user ID CHANGEUSRID The user ID that made the last modification.
Contention resolution result CONTENTION Identifies what is to happen when an EXEC CICS FEPI SEND command is issued and there is inbound data with begin-bracket. The options are:
  • LOSE - The EXEC CICS FEPI SEND command fails; an EXEC CICS FEPI RECEIVE command must be issued to get the inbound data.
  • WIN - The EXEC CICS FEPI SEND commands succeeds; inbound data is rejected with a negative response
Time created CREATETIME The local date and time when the definition was created.
Version DEFVER The version number of the FEPI Property Set definition, from 1 to 15.
Description code page DESCCODEPAGE The code page of the description field.
Description DESCRIPTION A description of the FEPI Property Set definition.
Device type DEVICE The LU mode and the device type that is to be simulated. The options are: T3278M2, T3278M3, T3278M4, T3278M5, T3279M2, T3279M3, T3279M4, T3279M5, TPS55M2, TPS55M3, TPS55M4, LUP.
End-session transaction ENDSESSION (Optional.) The name of the transaction that will perform end-session processing, either when a conversation is ended or when a session is to be ended. If this option is omitted, there is no user-supplied end-session processing.
TDQ queue holding exceptions EXCEPTIONQ The name of the transient data queue to which pool-specific exceptional events are to be written. If this option is omitted, there is no user-supplied exceptional event queue processing.
Journal name FJOURNALNAME (Optional.) The name of the journal where data is to be logged. If the value is omitted, no journaling is done.
Journal number FJOURNALNUM (Optional.) The number of the journal where data is to be logged, in the range 1 (the default) through 99. If the value is 0 (zero) or omitted, no journaling is done.
Data format FORMAT For SLU2 mode, the data mode to be used:
  • FORMATTED - Formatted operations. Character attributes are not supported on outbound data and ignored on inbound data.
  • DATASTREAM - Data stream operation.
Initial-inbound-data option INITIALDATA Identifies whether initial inbound data is expected when a session is started:
  • NOTINBOUND - No inbound data is expected.
  • INBOUND - Inbound data is expected
Maximum length of returned data MAXFLENGTH The maximum length of data that can be returned on any FEPI RECEIVE, CONVERSE, or EXTRACT FIELD command for a conversation, or that can be sent by any FEPI SEND or CONVERSE command for a conversation. This value helps FEPI use storage in a more efficient manner, so should be set no larger than necessary. It must be in the range 128 through 1048576. If this value is omitted, the default value 4096 is used.
Journal status MSGJRNL Identifies the required journaling of data to and from the back-end system:
  • NOMSGJRNL - No journaling.
  • INPUT - Journal inbound data.
  • OUTPUT - Journal outbound data.
  • INOUT - Journal inbound and outbound data
Name NAME The name of the FEPI Property Set definition.
Set and test sequence numbers (STSN) transaction STSN (Optional.) The name of the transaction to be started to handle 'set and test sequence number', for SLU P mode only. If this value is omitted, there is no user-supplied STSN handling; FEPI handles STSN automatically.
Unsolicited data transaction UNSOLDATA (Optional.) The name of the transaction that will handle unsolicited data. If no transaction name is specified, there is no user-supplied processing of unsolicited data. The Unsolicited data response and Unsolicited data transaction fields are mutually exclusive.
Unsolicited data response UNSOLDATACK (Optional.) The acknowledgement FEPI is to give if there is to be no unsolicited data processing:
  • NEGATIVE - Negative response X'0813'; BID is not accepted.
  • POSITIVE - Positive response, BID is accepted and subsequent data is accepted and discarded. If this option is omitted, unsolicited data is handled by the transaction specified in the Unsolicited data transaction field. The Unsolicited data response and Unsolicited data transaction fields are mutually exclusive.
  • NOTAPPLIC - This value must be chosen when the Unsolicited data transaction field is non-blank, as these two fields are mutually exclusive.
User data area 1 USERDATA1 Optional string of up to 8 characters that allows you to provide additional site-specific data related to the resource definition.
User data area 2 USERDATA2 Optional string of up to 8 characters that allows you to provide additional site-specific data related to the resource definition.
User data area 3 USERDATA3 Optional string of up to 8 characters that allows you to provide additional site-specific data related to the resource definition.


eyua7cps.html | Timestamp icon Last updated: Sunday, 4 June 2017