Valid Values for eTExitType

The following values are valid for eTExitType:
cim1265
The following values are valid for eTExitType:
  • PRE_ADD_ACCOUNT
    The account information that is being passed to the create account request is also passed to this program. Unlike the Modify operation, the password is passed to the Create operation as part of the account information.
  • POST_ADD_ACCOUNT
    The account information that is being passed to the create account request is also passed to this program. Unlike the Modify operation, the password is passed to the Create operation as part of the account information.
  • PRE_MODIFY_ACCOUNT
    The account information that is being passed to the modify account request is also passed to this program. The only exclusion to this is the password attribute.
  • POST_MODIFY_ACCOUNT
    The account information that is being passed to the modify account request is also passed to this program. The only exclusion to this is the password attribute.
  • PRE_CHANGE_ACCOUNT_PASSWORD
    A special case of MODIFY. This exit is triggered when the password attribute for the account changes. If the password attribute is the only change, the other modify code is not triggered. If other attributes change, this code is triggered. The account name and the password attributes contain the only information available to this program exit.
  • POST_CHANGE_ACCOUNT_PASSWORD
    A special case of MODIFY. This exit is triggered when the password attribute for the account changes. If the password attribute is the only change, the other modify code is not triggered. If other attributes change, this code is triggered. The account name and the password attribute contain the only information available to this program exit.
  • PRE_ENABLE_ACCOUNT
    A special case of MODIFY. This exit is triggered when the enable attribute for the account changes. If the enable attribute is the only change, the other modify code is not triggered. If other attributes change, this is triggered. The account name is the only account attribute available to this exit.
  • POST_ENABLE_ACCOUNT
    A special case of MODIFY. This exit is triggered when the enable attribute for the account changes. If the enable attribute is the only change, the other modify code is not triggered. If other attributes change, this is triggered. The account name is the only account attribute available to this exit.
  • PRE_DISABLE_ACCOUNT
    A special case of MODIFY. This exit is triggered when the disable attribute for the account changes. If the disable attribute is the only change, the other modify code is not triggered. If other attributes change, this is triggered. The account name is the only account attribute available to this exit.
  • POST_DISABLE_ACCOUNT
    A special case of MODIFY. This exit is triggered when the disable attribute for the account changes. If the disable attribute is the only change, the other modify code is not triggered. If other attributes change, this is triggered. The account name is the only account attribute available to this exit.
  • PRE_DELETE_ACCOUNT
    Triggered prior to a DELETE request. The account name is the only account attribute available to this exit.
  • POST_DELETE_ACCOUNT
    Triggered after a DELETE request. The account name is the only account attribute available to this exit.
  • PRE_ADD_GLOBAL_USER
    The global user information that is being passed to the create request is also passed to this program.
  • POST_ADD_GLOBAL_USER
    The global user information that is being passed to the create request is also passed to this program.
  • PRE_MODIFY_GLOBAL_USER
    The global user information that is being passed to the modify request is also passed to this program. The only exclusion to this is the password attribute.
  • POST_MODIFY_GLOBAL_USER
    The global user information that is being passed to the modify request is also passed to this program. The only exclusion to this is the password attribute.
  • PRE_CHANGE_GLOBAL_USER_PWD
    A special case of MODIFY. This exit is triggered when the password attribute for the global user changes. If the password attribute is the only change, the other modify code is not triggered. If other attributes change, this code is triggered. The global user name, the password, and optionally the password clue attributes are the only information available to this program exit.
  • POST_CHANGE_GLOBAL_USER_PWD
    A special case of MODIFY. This exit is triggered when the password attribute for the global user changes. If the password attribute is the only change, the other modify code is not triggered. If other attributes change, this code is triggered. The global user name, the password, and optionally the password clue attributes are the only information available to this program exit.
  • PRE_ENABLE_GLOBAL_USER
    A special case of MODIFY. This exit is triggered when the enable attribute for the global user changes. If the enable attribute is the only change, the other modify code is not triggered. If other attributes change, this code is triggered. The global user name is the only attribute available to this exit.
  • POST_ENABLE_GLOBAL_USER
    A special case of MODIFY. This exit is triggered when the enable attribute for the global user changes. If the enable attribute is the only change, the other modify code is not triggered. If other attributes change, this code is triggered. The global user name is the only attribute available to this exit.
  • PRE_DISABLE_GLOBAL_USER
    A special case of MODIFY. This exit is triggered when the disable attribute for the global user changes. If the disable attribute is the only change, the other modify code is not triggered. If other attributes change, this code is triggered. The global user name is the only attribute available to this exit.
  • POST_DISABLE_GLOBAL_USER
    A special case of MODIFY. This exit is triggered when the disable attribute for the global user changes. If the disable attribute is the only change, the other modify code is not triggered. If other attributes change, this code is triggered. The global user name is the only attribute available to this exit.
  • PRE_DELETE_GLOBAL_USER
    Triggered prior to a DELETE request. The global user name is the only attribute available to this exit.
  • POST_DELETE_GLOBAL_USER
    Triggered after a DELETE request. The global user name is the only attribute available to this exit.
  • PRE_ASSOCIATE_ROLE
    Refers to the changing of provisioning role membership in the Provisioning Server, regardless of what happens at the account level. The global user name and the provisioning role name are the only information available to this program exit.
  • POST_ASSOCIATE_ROLE
    Refers to the changing of provisioning role membership in the Provisioning Server, regardless of what happens at the account level. The global user name and the provisioning role name is the only information available to this program exit.
  • PRE_DISASSOCIATE_ROLE
    Refers to the changing of provisioning role membership in the Provisioning Server, regardless of what happens at the account level. The global user name and the provisioning role name are the only information available to this program exit.
    This value is called only for incremental provisioning role changes. If you use a replace-mode modification of global user's provisioning roles to replace one set of provisioning roles with another, this value calls the associate-role exits only. The exit would not read the database to find out which provisioning roles were previously included to see which were being set that were previously set and which were being removed.
  • POST_DISASSOCIATE_ROLE
    Refers to the changing of provisioning role membership in the Provisioning Server, regardless of what happens at the account level. The global user name and the provisioning role name are the only information that is available to this program exit.
    This value is called only for incremental provisioning role changes. If one uses a replace-mode modification of global user's provisioning roles to replace one set of provisioning roles with another, this value calls the associate-role exits only. The exit would not read the database to find out which provisioning roles were previously included to see which were being set that were previously set and which were being removed.
  • PRE_ADD_GLOBAL_GROUP
    The global group information that is being passed to the add request is also passed to this program.
  • POST_ADD_GLOBAL_GROUP
    The global group information that is being passed to the add request is also passed to this program.
  • PRE_MODIFY_GLOBAL_GROUP
    The global group information that is being passed to the modify request is also passed to this program.
  • POST_MODIFY_GLOBAL_GROUP
    The global group information that is being passed to the modify request is also passed to this program.
  • PRE_DELETE_GLOBAL_GROUP
    Triggered prior to a delete request. The global group name is the only attribute available to this exit.
  • POST_DELETE_GLOBAL_GROUP
    Triggered after a delete request. The global group name is the only attribute available to this exit.
  • PRE_ADD_ROLE
    The provisioning role information that is being passed to the add request is also passed to this program.
  • POST_ADD_ROLE
    The provisioning role information that is being passed to the add request is also passed to this program.
  • PRE_MODIFY_ROLE
    The provisioning role information that is being passed to the modify request is also passed to this program.
  • POST_MODIFY_ROLE
    The provisioning role information that is being passed to the modify request is also passed to this program.
  • PRE_DELETE_ROLE
    Triggered prior to a delete request. The provisioning role name is the only attribute available to this exit.
  • POST_DELETE_ROLE
    Triggered after a delete request. The provisioning role name is the only attribute available to this exit.
  • CUSTOM_FUNCTION
    Triggered when a program exit is invoked though a policy rule expression such as %$funcname(%UN%,%AC%)%.