8.2 ATMI Server Programming

ATMI server can only use FML32 APIs to manipulate channel / container according to following approximate mapping:

Table 8-1 CICS Container and FML32 APIs Mapping

CICS Container Commands	CICS Container Commands
PUT	Fadd32() or Fchg32()
GET	Fget32() or Ffind32()
DELETE	Fdel32()
STARTBROWSE GETNEXT ENDBROWSE	A loop based on Foccur32()

Meanwhile, five FML32 field macros should be included in ATMI server code; all of them belong to a given FML32 definition:

#define CX_PROGRAM ((FLDID32)231327331)

#define CX_TRANSID ((FLDID32)231327333)

#define CX_CHANNEL_NAME ((FLDID32)231329593)

#define CX_CONTAINER_NAME ((FLDID32)231329594)

#define CX_CONTAINER_DATA ((FLDID32)231329595)

These fields are used to map relevant CICS command options:

Table 8-2 CICS Command Options and FML32 Fields Mapping

CICS Command Options	Mapping FML32 Fields
PROGRAM of LINK	CX_PROGRAM
TRANSID of LINK	CX_TRANSID
CHANNEL of LINK or container commands	CX_CHANNEL_NAME
CONTAINER of container commands	CX_CONTAINER_NAME
FROM of PUT container INTO or SET of GET container	CX_CONTAINER_DATA
FLENGTH of PUT or GET container	Length of CX_CONTAINER_DATA