Generating KDCDADM and KDCPADM

The program units KDCDADM and KDCPADM must either be configured statically with KDCDEF or entered dynamically in the configuration. To enable you to use the functions of KDCDADM and KDCPADM you must assign dialog transaction codes to these program units. You can select any TAC name of your choice. In the following example, KDCDADM is assigned the transaction code tacdadm and KDCPADM is assigned the transaction code tacpadm.

Example of KDCDEF generation:

• on BS2000 systems:

  PROGRAM  KDCDADM,COMP=ILCS
  PROGRAM  KDCPADM,COMP=ILCS
  TAC      TACDADM,PROGRAM=KDCDADM,CALL=FIRST,TYPE=D
  TAC      TACPADM,PROGRAM=KDCPADM,CALL=FIRST,TYPE=D
  

• on Unix, Linux and Windows systems:

  PROGRAM  KDCDADM,COMP=C
  PROGRAM  KDCPADM,COMP=C
  TAC      tacdadm,PROGRAM=KDCDADM,CALL=FIRST,TYPE=D
  TAC      tacpadm,PROGRAM=KDCPADM,CALL=FIRST,TYPE=D
  

For KDCDEF generation in this application, you must also note the following:
The length of the standard primary working area specified in MAX SPAB= must be sufficient to accept the KDCS parameter area.