Multi-step service

In this example, information about the UTM application is retrieved in a first step and then, if necessary, object properties are modified in a second step. Both programs operate using a #format.

 /************************ Program unit ADMREAD ***************************/
 #include <kcadminc.h>       /* Header file for administration           */
 INIT
 MGET ... KCMF=#FORMADM       /* Entries are read in with a format        */
                              /* and the input is analyzed                */
 KDCADMI opcode=KC_GET_OBJECT
                              /* Administration call, UTM sends data to   */
                              /* the program                              */
 MPUT KCMF=#FORMADM           /* Output data/result to screen             */
 PEND RE KCRN=ADMMOD          /* Service is continued                     */

 /************************ Program unit ADMMOD ****************************/
 #include <kcadminc.h>       /* Header file for administration           */
 INIT
 MGET ... KCMF=#FORMADM       /* Entries are read in with a format        */
                              /* and the input is analyzed                */
 KDCADMI opcode=KC_MODIFY_OBJECT
                              /* The required object is modified          */
                              /* Several KDCADMI calls are possible       */
 MPUT KCMF=#FORMADM           /* Output data/result to screen             */
 PEND FI                      /* Service is terminated                    */

You can extend these programs, for instance, as follows:

• analyze the responses to the KDCADMI call and, in the event of errors, issue an appropriate message or

• write the data supplied to an LSSB in ADMREAD which can be reused in ADMMOD.

openUTM on Unix, Linux and Windows systems does not support a formatting system, so if you want to call the program using utmdtp in a shell resp. DOS window, you must program the MGET and MPUT calls in line mode

You can also address this program using a UPIC client.