Table 1 lists all FML32 FIELDs, which will be published in $KIXDIR/include/msgflds32.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The name of the current MAPSET, which will be displayed in Client’s UI.
|
|
|
|
|
|
The name of the current MAP, which will be displayed in Client’s UI.
|
|
|
|
|
|
|
|
|
|
|
|
The terminal control characters of the command “CICS SEND”, “ CICS SEND MAP”, “ CICS SEND TEXT”, and “ CICS SEND CONTROL”.
At times, CICS APIs above will be invoked with some control options, such as FREEKB, ALARM, ERASE, ERASEUP, CURSOR, etc; therefore, these control options should be inserted to this FML field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
At ART CICS runtime, we also provide a corresponding utility tcxmapgen, which generates the Copybook from Mapset file; regarding that the structure of Copybook generated by
tcxmapgen is almost the same as the one generated in Mainframe CICS, application data exchanged between the Client and ARTWTRN/1 must follow the definition in the Copybook of each Mapset.
For CICS SEND/RECEIVE and
CICS SEND TEXT, ARTWTRN/1 and Client just need to insert the plain textual characters into the field
CX_WEB_APPDATA.
| Command | Write Control Character | Indicate Cursor | Orders | Data | Orders | Data | ...
If SEND MAP/TEXT command sets cursor option, IC should be inserted into the header of 3270 data stream with the following format in the case of
SEND command without cursor option. If this command sets option
ERASE, the cursor will set to the upper left corner of the screen.
At ART CICS runtime, we define a FML field CX_WEB_CTRL_CHAR, a CARRAY with 12 bytes, to store these control characters; however, in this release, we plan to support CMD, WCC, and IC, all of which are mostly used. The data sequence of this field is as below:
At ART CICS runtime, we defined a FML field CX_WEB_AID to store these three characters and
AID will always be function key of the keyboard, such as Enter, Clear, F01~F24, etc.
ROW and
COL mean the current cursor position when terminal sends the inbound data stream to application program. The code of these characters will be set as EBCDIC, not ASCII.
In case of using Tuxedo FML32 buffer,
COMMREA can be exchanged in the request/response, mirror transaction and TWA can be validated, even
CHANNEL and
CONTAINER can also be used.
In case of using Tuxedo RECORD buffer,
COMMAREA can be exchanged using
RECORD data area. Mirror transaction, TWA, or
CHANNEL/CONTAINER are not supported.
DPL <program> can be advertised by
ARTDPL as a Tuxedo service. And the prefix of service name is the CICS region
<sysid>_ which current
ARTDPL server belongs to. If client tries to call this service and exchange the
COMMAREA with
ARTDPL server, the following FML32 fields must be present in the request:
Meanwhile, the FML32 filed CX_PROGRAM must not be present, because
ARTDPL server can realize the name of DPL program to be executed from the service name.
|
•
|
Type C: <applid>_MIRROR_<transid>
|
To use RECORD as the data buffer to call
ARTDPL server, you should configure
IN-TYPE and
OUT-TYPE for the called program in
programs.desc. When you use
RECORD, Tuxedo clients can only use Type A services.
Table 2 lists all FML32 FIELDs, which will be published in
$KIXDIR/include/msgflds32.
In request to ARTDPL, if
CX_TRANSID is present,
ARTDPL sets
EIBTRNID as the value of
CX_TRANSID. If
CX_TRANSID is not present, the
EIBTRNID is set to system mirror transaction
CSMI/CVMI.
If DPL program aborts, ARTDPL server returns
TPFAILS to client. User can get the CICS ABEND code from FML32 field
CX_ABENDCODE in the response of
ARTDPL.
