TRANSFER - control the data transfer of the user data

The TRANSFER specifies the user data KDCUPD is to transfer to the new KDCFILE.

TRANSFER

[ ASYNLPAP=YES | NO ]  [ ,ASYNTACS=YES | NO ]  [ ,ASYNTERM=YES | NO ]  [, DB-CREDENTIALS = YES | NO ]  [ ,DIALOGS=YES | NO ]                      [ ,PASS=YES | NO ]  [ ,PROG-VER=YES | NO ]  [ ,SOCKET-DIALOGS=YES | NO ]  [ ,STORAGES=YES | NO ]  [ ,UPIC-DIALOGS=YES | NO ] Additional operand on BS2000 systems  [ ,LOCALE=YES | NO ]

If you omit the TRANSFER statement, KDCUPD transfers the user data as if the value YES was specified for all the TRANSFER operands.

ASYNLPAP=
YES	All asynchronous messages that have not yet been output to partner applications (distributed processing via LU6.1 / OSI TP) are also transferred. Messages from the dead letter queue with the original destination LPAP or OSI-LPAP are only transferred if the original destinations still exist in the new generation. The transfer happens regardless of whether DEAD-LETTER-Q=YES has been generated for the LPAPs or OSI-LPAPs. The following applies to UTM cluster applications: The parameter only applies to node updates.
NO	These messages are not transferred.
ASYNTACS=
YES	All background jobs not yet processed, including time-driven jobs and all asynchronous jobs with their data, are transferred. In addition, all messages in all TAC queues are transferred. Messages from the dead letter queue with original destination TAC or TAC queue are taken on regardless of whether the original destination still exists in the new generation or DEAD-LETTER-Q=YES was generated for TACs. The following applies to UTM cluster applications: The parameter only applies to node updates. CAUTION! In the case of wraparound queues, the messages which were transferred first are lost and replaced by the most recently transferred messages when the queue level is reached. No warning message is issued.
NO	These jobs and data are not transferred. Neither queued messages nor open asynchronous messages are transferred.
ASYNTERM=
YES	All asynchronous messages not yet output to LTERM partners are transferred, including time-driven messages.
NO	These messages are not transferred. The following applies to UTM cluster applications: The parameter only applies to node updates.
DB-CREDENTIALS =
YES	Database password and database user name are transferred. The following applies to UTM cluster applications: The parameter only applies to cluster updates.
NO	Database password and database user name are not transferred.
DIALOGS=
YES	The data to dialog services is transferred. If the service is open, this includes LSSBs, KB and the last dialog message. If the service is terminated, only the last logged dialog message is transferred. The following applies to UTM cluster applications: In the case of a node update, the service-specific data of connection user IDs is taken over. In the case of a cluster update, the service-specific data of genuine user IDs is taken over.
NO	No service-specific data is transferred.
LOCALE=	Additional operand on BS2000 systems
YES	KDCUPD transfers the current values of the locale of each UTM user (USER) to the new KDCFILE. The values can differ from generated values, e.g. if a user has changed his/her locale using the SIGN CL call in the application run.
NO	The locales of users are not transferred, i.e. the generated values apply.
PASS=
YES	Passwords are transferred from the old to the new KDCFILE. This applies to all USERs for whom a password was generated in the old and in the new KDCFILE. The following is also transferred (if generated): the remaining validity period of the password the most recently used passwords, in other words the password history the minimum period before the password can next be changed In the case of users for whom no password was defined in the old KDCFILE (in contrast to the new file), the new password is retained. If no password is generated for a user in the new KDCFILE, any existing password in the old KDCFILE is not transferred. The following applies to UTM cluster applications: The parameter only applies to cluster updates.
NO	No passwords are transferred.
PROG-VER=
YES	The current version numbers of the load modules (BS2000), shared objects (Unix and Linux systems) or DLLs (Windows systems) are transferred to the new KDCFILE. The following applies to UTM cluster applications: The parameter only applies to node updates.
NO	The current version numbers are not transferred.
QUEUES=
YES	All temporary queues and the messages they contain are transferred from the old to the new KDCFILE. The following applies to UTM cluster applications: The parameter only applies to node updates.
NO	The temporary queues and the messages they contain are not transferred.
SOCKET-DIALOGS=
YES	The data for dialog services started by socket partners is transferred. In the case of an open service, these are the LSSBs, KB and the most recent dialog message. In the case of a terminated service, it is the most recently saved dialog message. The following applies to UTM cluster applications: In the case of a node update, the service-specific data of connection user IDs is taken over. In the case of a cluster update, the service-specific data of genuine user IDs is taken over.
NO	The data is not transferred.
STORAGES=
YES	All UTM secondary storage areas, i.e. GSSB, TLS and ULS are transferred. The following applies to UTM cluster applications: In the case of a node update, the TLS areas are taken over. In the case of a cluster update, the GSSBs and the ULS areas are taken over.
NO	The UTM secondary storage area are not transferred.
UPIC-DIALOGS=
YES	The data for dialog services started by UPIC clients is transferred. In the case of an open service, these are the LSSBs, KB and the most recent dialog message. In the case of a terminated service, it is the most recently saved dialog message. The following applies to UTM cluster applications: The parameter only applies to cluster updates.
NO	The data is not transferred.