Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Control statements for KDCUPD

KDCUPD knows the following control statements for data transfer:

Statement

Meaning

TRANSFER

Control the transfer of the data from the old KDCFILE to the new KDCFILE

KDCFILE

Specify the base name of the newly generated and the old KDCFILE

CLUSTER-FILEBASE

Specify base name of old and new UTM cluster files
(Unix, Linux and Windows systems)

CATID

The catid of the old and new KDCFILE are specified on BS2000 systems

LIST

Control the runtime log

END

Terminate input and start processing

KDCUPD knows the following control statements for the consistency check:

Statement

Meaning

CHECK

Check the consistency of the KDFILE of a UTM application

LIST

Control the runtime log

END

Terminate input and start processing

The control statements are read from SYSDTA on BS2000 systems or from stdin (command prompt) on Unix, Linux and Windows systems.The control statements KDCFILE, CATID, LIST and CHECK may only be entered once per KDCUPD run. The input must be contained in a single line. Multiple (separate single) lines can be entered for the control statement TRANSFER.

Example

  1. KDCUPD is to transfer the data from the old KDCFILE (base name BOOK01) of a standalone UTM-S application to the new KDCFILE (base name BOOK02). All data is to be transferred except for the asynchronous messages intended for the communication partners (LPAP and LTERM) that are still located in the message queues of the old KDCFILE. KDCUPD is to output the successful transfer messages only to SYSLST (BS2000 systems) or stdout (Unix, Linux and Windows systems).

    BS2000 systems

    Unix, Linux and Windows systems

    *KDCFILE NEW=BUCH02,OLD=BUCH01 
    *CATID OLD=(20SN,20PN),NEW=(20SN,20PN)
    *TRANSFER ASYNLPAP=NO
    *TRANSFER ASYNTERM=NO 
    *LIST PROTOCOL=SYSLST
    *END

    *KDCFILE NEW=BUCH02,OLD=BUCH01

    *TRANSFER ASYNLPAP=NO
    *TRANSFER ASYNTERM=NO 
    *LIST PROTOCOL=STDOUT
    *END

  2. If you only enter the mandatory parameters in all statements, then KDCUPD attempts to transfer everything and outputs the log to SYSOUT and SYSLST or to stdout and stderr. You must specify the following to transfer all data:

    BS2000 systems

     Unix, Linux and Windows systems

    *KDCFILE NEW=BUCH02,OLD=BUCH01
    *CATID OLD=(20SN,20PN),NEW=(20SN,20PN)
    *END

    *KDCFILE NEW=BUCH02,OLD=BUCH01

    *END