public interface AbstractDialogCommunicationMonitor extends AbstractRadicalElement
The Communication Monitor handles the following functions:
1: The definition of communication functions (message sending and receiving) according to the target environment.
2: Checking each message received.
3: Controlling the sending/receiving of the query.
According to the size allowed for the physical message, several physical messages may need to be issued in order to obtain the complete logical message.
A work file must therefore be available for a temporary storage of the current query.
4: Once the query is completely received, sequential processing of services which compose it by successive calls to the corresponding Services Manager.
5: Transactional management (COMMIT/ROLLBACK)
The Communications Monitor uses the COMMIT and ROLLBACK services of a Database or a transactional monitor depending on its generation variant.
The transactional management is always of the LUW Server type (Logical Unit of Work). Accordingly, the Server component takes in charge the Database integrity.
A query is processed as a whole.
The server part executes - before return to the client - a COMMIT or a ROLLBACK according to the error context (protocol error or application error) established at the end of the query processing.
In case of error, query processing is ended and an error message is sent back.
Thus, all the resources monopolized by a query processing are made available once the response has been sent.
Modifier and Type | Field and Description |
---|---|
static java.lang.String |
copyright |
Modifier and Type | Method and Description |
---|---|
java.lang.String |
getCobolFolder() |
java.lang.String |
getCobolProject() |
CobolTypeValues |
getCobolType() |
CommunicationTypeValues |
getCommunicationType() |
java.util.List<CPLine> |
getCPLines() |
ErrorMessageSentValues |
getErrorMessageSent() |
java.lang.String |
getExternalName() |
Library |
getGenerationLibrary() |
java.util.List<GLine> |
getGOLines() |
MapTypeValues |
getMapType() |
int |
getMessageSize() |
java.lang.String |
getTransactionCode()
This field corresponds to: |
getGCLines
getCalledEntities, getDescriptionTypes, getDesignId, getEntityVersion, getKeywords, getLabel, getName, getPackage, getProject, isResolved
static final java.lang.String copyright
java.lang.String getCobolFolder()
Returns the folder where the cobol is generated.
java.lang.String getCobolProject()
Returns the project where the cobol is generated.
CobolTypeValues getCobolType()
In this field, you have the COBOL variant for the generated Communication Monitor.
CommunicationTypeValues getCommunicationType()
Communication type
SOCKET : TCP-IP
LOCAL : Local Communication (default value)
The choice of the Communication type depends on the generated COBOL variant and possibly on the Transactional Monitor variant.
java.util.List<CPLine> getCPLines()
List of called predefined Macros into the generated program.
ErrorMessageSentValues getErrorMessageSent()
ErrorMessage Sent : sending of error labels option
Y: sends error labels (default)
N: sends error keys only
NONE: uses the option selected for the Dialog
java.lang.String getExternalName()
The name entered here is the name of the file generated from this instance. The generated file name can then differ from the instance name.
Library getGenerationLibrary()
Indicates the Library on which we can find the generation parameters for the entity.
Parameters are related to the adaptation to the operating system in use.
java.util.List<GLine> getGOLines()
The GOLines indicates the list of the generation options.
Some options are mandatory : WOKRFILO WORFILS and WORKILB
WORKFILB :Database Block code for a work file in organization H or external name for a work file in organization V.
External name :
IBM CICS - VSAM : DDNAME
For other variants : Logical name , generated in the SELECT clause.
WORKFILS : Code of Segment associated with the work file
WOKRFILO : Organization of the work file used by the associated Monitor and Services Manager
V : sequential indexed
H : relational
W : working
MapTypeValues getMapType()
In this field, you have the variant of the TP monitor for the generated Communication Monitor
int getMessageSize()
Message size [x 1024 characters]
The maximum physical size of a message between Client and Server - in kilobytes - between 2 and 32 K.
This value depends on the capacity allowed by the network administration of the application's execution environment.
Default = 24
The size of the message sent on the network corresponds to the useful size of its content.
java.lang.String getTransactionCode()
This field corresponds to:
The four-character transaction code (Dialog default code) for a CICS variant.
The transaction code associated with the Dialog for an IMS variant. This field is displayed on all the Dialog Screens except if the MONITOFF option (one transaction code for each Screen, no generated monitor) option is specified.