The following information describes the processing that is associated with a passthrough request.
The request message contains the name of the DPL passthrough stub program (DFHMADPP), which initiates server runtime processing.
If the request message is in XML format, the DPL Stub program will call the XML Header to COBOL Converter program (DFHMAXMI) to parse the XML header tag data and return in a COBOL fixed format (DFHMAH).
The DPL Passthrough Stub program (DFHMADPP) will then call the ADS to XML Converter program (DFHMAXPI) to parse the XML application request tag data and return in a COBOL fixed format structure. The inbound application request tag data in passthrough mode must also include pertinent screen header (CIA-SCREEN-HEADER) and map header (CIA-MAP-HEADER) tag data.
See XML request and response processing for passthrough and XML message formats for passthrough requests for further information.
EXEC CICS DEFINE PROCESS (<processname>)
PROCESSTYPE (<processtype>)
TRANSID (<transid>)
PROGRAM (<program>)
NOCHECK
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
The NOCHECK processing option indicates that no record is to be written to the BTS repository data set to reserve the name of the process. Using the BTS NOCHECK option improves BTS performance by removing the write to the repository and its associated logging. See CICS Business Transaction Services manual for further information on the DEFINE PROCESS command and options.
State information includes the request name (DFHMAH-REQUESTNAME) as specified in the message header (DFHMAH) and the processing mode (DFHMAH-UOWCONTROL).
EXEC CICS RUN ACQPROCESS
SYNCHRONOUS
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
EXEC CICS DEFINE ACTIVITY (ADC-NAV-ACTIVITY)
EVENT (<completionevent>)
TRANSID (ADC-NAV-TRANSACTION)
PROGRAM (ADC-NAV-PROGRAM-ID)
ACTIVITYID (ADC-NAV-ACTIVITYID)
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
EXEC CICS RUN ACTIVITY (ADC-NAV-ACTIVITY)
SYNCHRONOUS
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
The BTS Link3270 Passthrough Manager activity will perform Link3270 passthrough processing in order to complete the request made by the service requestor.
The Link3270 Maintenance program performs initialization and exit processing for passthrough processing. It calls the Link3270 Facility State Management program (DFHMALTS), if necessary, to retrieve, store and/or delete Link3270 facility business state information.
The Link3270 Vector Processor program sends vectors to and receives vectors from any CICS target application that uses BMS commands (with some restrictions) where a single send and receive structure inclusive of the Link3270 bridge header (BRIH), the inbound/outbound vector header and appropriate inbound/outbound vector is not greater than 32000 bytes (i.e. the COMMAREA passed to the Link3270 bridge program, DFHL3270, is 32,000 bytes).
The Link3270 Vector Processor program can also call the Link3270 Vector Log program (DFHMAVCL), if vector logging is on, to log inbound and outbound Link3270 vector header information and data. See DFHMAH2 header structure for information on configuring for vector logging and additional passthrough header fields and definitions.
Each passthrough request issued by the service requestor results in a different BTS process instance to fulfill that passthrough request.
Each process instance consists of a Navigation Manager (DFHMAMGR) activity and the one Link3270 Passthrough Manager (DFHMALPT) activity that is needed to support that passthrough request.
With regards to data-container management, passthrough processing processes as a single connector type.