KDCS calls

The UTM function calls can be divided into the following function groups:

• program and transaction management

• dialog communication

• communication via message queuing

• administration of message queues and printers

• storage area management

• information services

• logging

• signing on/off and changing passwords

Program and transaction management:

Call	Function
INIT	Sign on a program to openUTM
PEND	End the program
PGWT	Set a waiting point in a program unit run
RSET	Roll back requested changes and operations

Dialog communication:

Call	Function
APRO	Address a job-receiving service (for distributed processing)
CTRL	Control an OSI TP dialog (for distributed processing)
MGET	Get a dialog message
MPUT	Send a dialog message

Communication via message queuing:

Call	Function
APRO	Address a job-receiving service (for distributed processing)
DGET	Read a message from a service-controlled queue
DPUT	Create time-controlled asynchronous jobs, messages in service-controlled queues and confirmation jobs
FGET	Get asynchronous messages
FPUT	Create asynchronous jobs and messages in TAC Queues
MCOM	Define a job complex
QCRE	Create a temporary queue
QREL	Delete a temporary queue

Administration of message queues and printers:

Call	Function
DADM	Administer messages in UTM-controlled and service-controlled queues and administer the dead letter queue
PADM	Control printers and print jobs

Storage area management:

Call	Function
GTDA	Read from a TLS
PTDA	Write to a TLS
SGET	Read from a secondary storage area
SPUT	Write to a secondary storage area
SREL	Release a secondary storage area
UNLK	Unlock a TLS, ULS, or GSSB

Information services:

Call	Function
INFO	Request information

Logging:

Call	Function
LPUT	Write to the log file

Signing on/off and changing passwords:

Call	Function
SIGN	Sign on/off, change passwords

Return codes of KDCS calls

After each KDCS call, openUTM returns a standard KDCS return code and, if necessary, a UTM-specific return code.

Among other things, these return codes indicate whether or not the desired operation was successful. The return codes are divided into the following categories:

• no errors

• minor errors that can be rectified by the program

• codes for function keys that were pressed while an input message was being transmitted

• errors that still allow you to end the dialog step or the service

• serious errors that cause openUTM to roll back the transaction and terminate the service with a dump. In this case the return code can be taken from the dump. If possible, openUTM sends an error message to the communication partner.

An overview of all return codes can be found in the openUTM manual ”Messages, Debugging and Diagnostics”.