UTM calls implement the KDCS interface as standardized under DIN 66 265 ("Interfaces of a Kernel for Transaction-oriented Application Systems"). The UTM program interface is an upward-compatible extension to this DIN standard. The table below lists these extensions.
CALL | Included in | Extensions to DIN 66 265 |
|---|---|---|
APRO | no | Distributed processing |
CTRL | no | Distributed processing (only for OSI TP) |
DADM | no | Administration of message queues (asynchronous jobs) |
DGET | no | Read from service-controlled message queues |
DPUT | yes | Confirmation jobs and user information |
FGET | yes | Distributed processing |
FPUT | yes | Distributed processing |
GTDA | yes | none |
INFO | no | Information services |
INIT | yes | Distributed processing |
LPUT | yes | none |
MCOM | no | Definition of job complexes |
MGET | yes | Distributed processing |
MPUT | yes | Distributed processing |
QCRE | no | Create temporary queue |
QREL | no | Delete temporary queue |
PADM | no | Administration of printers and printer output |
PEND | yes | Distributed processing, PEND KP/PS/FC/SP/RS/FR not contained in DIN 66 265 |
PGWT | no | Program management |
PTDA | yes | none |
RSET | no | Rollback operation |
SGET | yes | none |
SIGN | no | Signing on and off, changing password, checking authorization data |
SPUT | yes | none |
SREL | yes | none |
UNLK | no | Unlocking storage areas |
The table below shows the KDCS calls and their functions.
CALL | Function | Function group |
|---|---|---|
APRO | Address job-receiving service | Message communication (with distributed processing) |
CTRL | Control OSI TP dialogs | Message communication (with distributed processing) |
DADM | Administer asynchronous jobs | Management of message queues and printers |
DGET | Read messages from a service-controlled message queue | Message communication - message queuing |
DPUT | Generate time-driven asynchronous job and confirmation jobs | Message communication - message queuing |
FGET | Receive asynchronous message | Message communication - message queuing |
FPUT | Generate asynchronous job | Message communication - message queuing |
GTDA | Read from TLS | Memory management |
INFO | Request information | Information services |
INIT | Signing on a program to openUTM | Program management |
LPUT | Write to log file | Logging facility |
MCOM | Define job complex | Message communication |
MGET | Receive dialog message | Message communication - dialog |
MPUT | Send dialog message | Message communication - dialog |
QCRE | Create temporary message queues | Management of temporary message queues |
QREL | Delete temporary message queues | Management of temporary message queues |
PADM | Control printers and printer outputs | Management of message queues and printers |
PEND | Terminate program | Program management |
PGWT | Set wait point in a program unit run | Program management |
PTDA | Write to TLS | Memory management |
RSET | Roll back requested changes and operations | Program management |
SGET | Read from secondary storage area | Memory management |
SIGN | Sign on and off, change password, check authorization data | Sign-on management |
SPUT | Write to secondary storage area | Memory management |
SREL | Release secondary storage area | Memory management |
UNLK | Unlock TLS, ULS or GSSB | Memory management |
The next table lists the function groups and the calls associated with them.
Function group | Associated UTM calls |
|---|---|
Sign-on management | SIGN |
Program management | INIT, RSET, PEND, PGWT |
Message communication - dialog | MGET, MPUT |
Message communication - message queuing | MCOM, DGET, DPUT, FGET, FPUT |
Management of message - queues and printers | DADM, PADM |
Management of temporary - message queues | QCRE, QREL |
Memory management | GTDA, PTDA, SGET, SPUT, SREL, UNLK |
Information services | INFO |
Logging facility | LPUT |
Distributed processing | APRO, CTRL, DPUT, FPUT, INIT, MCOM, MGET, MPUT, PEND, RSET, PGWT |
After each call (except PEND) openUTM returns information in the KDCS communication area.
The fields of the KDCS parameter area set prior to a call or returned after its execution have particular names. These are meant to help you deal with the KDCS interface and its description. Their use also enhances the maintenance and transferability of programs. The appendix gives an overview of all operand fields and their use in the various calls.