DL/I calls for transaction management
Use these DL/I calls with IMS™ TM to perform transaction management functions in your application programs.
Transaction management calls must use either i/o pcb or aib parameters.
Each call description contains:
- A syntax diagram
- A definition for each parameter that can be used in the call
- Details on how to use the call in your application program
- Restrictions on the use of the call
Each parameter is described as an input or output parameter. "Input" refers to input to IMS from the application program. "Output" refers to output from IMS to the application program.
The syntax diagrams for the transaction managment calls do not contain the complete call structure. Instead, the calls begin with the function parameter. The call, the call interface (xxxTDLI), and parmcount (if it is required) are not included in the syntax diagrams. See language-specific information (for COBOL, C language, Pascal, PL/I, and assembler language) in the topic "Defining Application Program Elements" inIMS Version 13 Application Programming for the complete structure.
- Transaction Management Call Summary
-
The following table summarizes the parameters that are valid for each of the transaction management message calls. The following table lists the function code, its meaning, use, parameters, and in which regions it is valid. Optional parameters are enclosed in brackets, [ ].
Exception: Language-dependent parameters are not shown here. The variable parmcount is required for all PLITDLI calls. Either parmcount or VL is required for assembler language calls. Parmcount is optional in COBOL, C, and Pascal programs. See the topic "Formatting DL/I Calls for Language Interfaces" in IMS Version 13 Application Programming for language-specific information.
Related reading: For information on writing calls with programming language interfaces, see the topic "Defining Application Program Elements" in IMS Version 13 Application Programming.
Table 1. Summary of TM message calls Function Code Meaning Use Parameters Valid for AUTH Authorization Verifies user's security authorization function, i/o pcb or aib, i/o area DB/DC, DCCTL CHNG Change Sets destination on modifiable alternate PCB function, alt pcb or aib, destination name[, options list, feedback area] DB/DC, DCCTL CMD Command Used by a program to issue IMS commands function, i/o pcb or aib, i/o area DB/DC, DCCTL GCMD Get Command Retrieves second and any subsequent responses to a command function, i/o pcb or aib, i/o area DB/DC, DCCTL GN Get Next Retrieves second and any subsequent message segments function, i/o pcb or aib, i/o area DB/DC, DCCTL GU Get Unique Retrieves the first segment of a message function, i/o pcb or aib, i/o area DB/DC, DCCTL ICAL IMS Call Sends a synchronous request for data or services to a non-IMS application program or service that runs in a distributed environment aib, request area, response area DB/DC, DCCTL ISRT Insert Builds an output message in a program's I/O area function, i/o or alt pcb or aib, i/o area [,mod name.] DB/DC, DCCTL PURG Purge Enqueues messages from a PCB to destinations function, i/o or alt pcb or aib[, i/o area, mod name.] DB/DC, DCCTL SETO Sets processing options for advanced print functions and APPC/IMS message processing Feedback area returns information about errors in the options list function, i/o pcb or alternate pcb or aib, i/o area, options list[, feedback area] BMP, MPP, IFP DB/DC, DCCTL
Related reading: DCCTL users can issue calls using GSAM database PCBs, which are described in IMS Version 13 Application Programming.
- AUTH call
An Authorization (AUTH) call verifies each user's security authorization. It determines whether a user is authorized to access the resources specified on the AUTH call. - CHNG call
The Change (CHNG) call sets the destination of a modifiable alternate PCB to the logical terminal, LU 6.2 descriptor, or transaction code that you specify. You can also use the CHNG call with the Spool Application Program Interface (Spool API) to specify print data set characteristics. - CMD call
The Command (CMD) call enables an application program to issue IMS commands. - GCMD call
The Get Command (GCMD) call retrieves the response segments from IMS TM when your application program processes IMS commands using the CMD call. - GN call
If an input message contains more than one segment, a Get Unique (GU) call retrieves the first segment of the message and Get Next (GN) calls retrieve the remaining segments. - GU call
The Get Unique (GU) call retrieves the first segment of a message. - ICAL call
The IMS Call (ICAL) call allows
an application program that runs in the IMS TM
environment to send a synchronous request for data or services to
a non-IMS application program or service that runs in a z/OS® or distributed environment, or to initiate
a synchronous program switch to an IMS transaction.
- ISRT call
The Insert (ISRT) call sends one message segment to the destination that you specify in the call. The destination is represented by the I/O PCB, alternate PCB, or AIB you specify in the call parameters. - PURG call
The Purge (PURG) call allows your application program to send one or more output message segments (specified with the ISRT call) to the specified destination before the application program retrieves the next input message or issues a commit point. - SETO call
The SET Options (SETO) call allows IMS application programs to set processing options. The SETO call can also be used to set processing options for Spool API functions.