User exit record
The user exit record called user.exits provides interfaces to specified programs. The available user exits include Statistics Exit, File Open Exit, and Security Exit. The following parameters are available for this record:
||The gateway control program used during the user exit procedure. This exit is given control for each statistics record that is written.||Name of the gateway control program.||No|
||The file open exit program used during the user exit procedure. It enables
you to control file names on both the sending and receiving node. The exit is located so that
it takes control on the receiving (remote) node before the file is opened.
This exit applies only to the copy statement and provides access to all file control parameters (including the data set name file name, sysopt parameters, and disposition).
|Name of the file open exit program.||No|
||The security exit program used during the user exit procedure. This exit generates and verifies passtickets, and it also supports other password support programs, such as PASSTICKET, part of the RACF security system available on MVS hosts and also supported by IBM® on UNIX AIX and OS/2 computers using the NETSP product.||Name of the security exit program.||No|
||Modifies the default behavior of security.exit.program. This is an optional parameter.||snode_sec_exit_only | sec_exit_only
snode_sec_exit_only— Causes IBM Connect:Direct® to use the security exit, when it is acting in the role of the SNODE. After IBM Connect:Direct receives a valid message, it evaluates the proxy and the secure point-of-entry to establish the local user. The security exit is not used when IBM Connect:Direct is the PNODE.
sec_exit_only—Causes IBM Connect:Direct to always use the security exit. After IBM Connect:Direct receives a valid message, it evaluates the proxy and the secure point-of-entry to establish the local user.