Connectivity parameters that specify the location of the CCT file and credentials to use when accessing the file
Report destination parameters that direct message output
Report content parameters that control report content to a specific destination
Other parameters that controls whether to validate or change the registration status

Connectivity Parameters

GLOBAL_REGISTRATION_LOCATION={

listener_node_name

|

local

}

Specifies the location of the VSAM CCT file that contains the capture registrations. Default value is "local."

You can override this value for a particular registration-specific command by including the REGISTRATION_LOCATION parameter in the command.

If you are processing a CCT file on a remote system such as IBM i where a PowerExchange Listener runs, specify the NODE name for the PowerExchange Listener.

Although you can run PWXUCREG on z/OS to process the CCT file locally, you might find it advantageous to run PWUXREG on a remote Linux, UNIX, or Windows system and pipe the reports to a local file by using the stdout pipe syntax.

GLOBAL_USER=

user_id

Specifies a user ID that has the authority to access capture registrations in the CCT data set on the source system. This value is case-sensitive.

If the SECURITY statement in the PowerExchange Listener DBMOVER configuration file is set to " 2", the following requirements apply:

If you are not accessing the CCT file locally, a password or passphrase must be supplied to enable connection to the listener.
On z/OS, the user ID must have SAF authority to access certain CAPX resources.

Consult with your system security administrator to determine the security requirements for the user ID and the password or encrypted password based on your system security and the SECURITY statement in the DBMOVER configuration member.

If you specify this parameter, also specify either the GLOBAL_EPWD or GLOBAL_PWD parameter.

You can override the global user ID for a particular registration-specific command by including the USER parameter in the command.

GLOBAL_EPWD=

encrypted_password

Specifies an encrypted password to use with the user ID that is specified in the associated GLOBAL_USER parameter.

Consult with your system security administrator to determine the security requirements for the user ID and the password or encrypted password based on your system security and the SECURITY statement in the DBMOVER configuration member.

To ensure that passwords are not stored in a readable format, Informatica recommends that you use the EWPD parameter instead of the PWD parameter. Do not specify both the EPWD and PWD parameters.

You can use the PowerExchange Navigator to create an encrypted password. Click

File

Encrypt

.

You can override this value for a particular registration-specific command by including the EPWD parameter in the command.

GLOBAL_PWD=

password

Specifies a nonencrypted password to use with the user ID that is specified in the associated GLOBAL_USER parameter. This value is case-sensitive. Overrides the GLOBAL_PWD parameter in a preceding SET_CONTROL_VALUE command, if specified.

Consult with your system security administrator to determine the security requirements for the user ID and the password or encrypted password based on your system security and the SECURITY statement in the DBMOVER configuration member.

To ensure that passwords are not stored in a readable format, Informatica recommends that you use the EWPD parameter instead of the PWD parameter. Do not specify both the EPWD and PWD parameters.

You can override this value for a particular registration-specific command by including the PWD parameter in the command.

OVERRIDE_CCT_FILE_NAME={

file_name

]

Specify this parameter to use a non-standard CCT file. Default is to use the standard CCT file.

Report Destination Parameters

NO_MESSAGES_TO_DETAIL_LOG={

N

|Y}

Controls whether messages are written to the detail log file. Options are:

N
. Write messages to the detail log file.
Y
. Do not write messages to the detail log file.

Default is N.

On Linux, UNIX, and Windows it is often useful to pipe the stdout results to a file and to suppress writing messages to detail.log.

SYSTEM_CONSOLE_MESSAGES_COMMAND={

N

|Y}

Controls whether the utility routes message output from registration-specific commands that change the registration status to the z/OS system console and to the DTLLOG log or does not route the message output to either location.

N
. When the utility runs on z/OS, the utility does not route message output from registration-specific commands to the z/OS system console and DTLLOG log.
Y
. When the utility runs on z/OS, the utility routes message output from registration-specific commands to the z/OS system console and DTLLOG log.

Default is N.

SYSTEM_CONSOLE_MESSAGES_DISPLAY={

N

|Y}

Controls whether the utility routes message output from an explicit or automatic display registration request to the

z/OS

system console and DTLLOG log or only to the DTLOG log. Options are:

N
. Send the messages to the DTLLOG log.
Y
. Send the messages to the system console and the DTLLOG log.

If you specify Y, when PWXUCREG runs on z/OS, the utility routes message output that reports registration attributes to the z/OS system console and to the DTLLOG log. The messages result from running one of the following commands:

A DISPLAY_REGISTRATION command
A SET_CONTROL_VALUE command with the DISPLAY_REGISTRATION_AFTER_COMMAND or DISPLAY_REGISTRATION_BEFORE_COMMAND parameter.

Default is N.

Report Content Parameters

DISPLAY_REGISTRATION_AFTER_COMMAND={N|

Y

}

Displays information about the capture registration or registrations that were processed by a preceding registration-specific command that changed the registration status. This information includes the registration current status and the activation and suspension timestamps. You can use this information to verify that the preceding command correctly changed the status. Options are:

N
. Do not display registration information after each command that changes the registration status.
Y
. Display registration information after each command that changes the registration status.

Default is Y. If you accept the default value, you do not need to specify the DISPLAY_REGISTRATION command in the PWXUCREG JCL to display registration status information after a command, unless you want to override this global parameter setting.

You can use this parameter with the DISPLAY_REGISTRATION_BEFORE_COMMAND parameter to display registration status information before and after a command that changes the status.

DISPLAY_REGISTRATION_BEFORE_COMMAND={

N

|Y}

Displays information about the capture registration or registrations to be processed by a subsequent registration-specific command that changes the registration status. This information includes the registration current status and the activation and suspension timestamps. You can use this information to verify that the command correctly changes the status. Options are:

N
. Do not display registration information before each command that changes the registration status.
Y
. Display registration information before each command that changes the registration status.

Default is N. If you accept the default value, you can still specify the DISPLAY_REGISTRATION command in the PWXUCREG JCL to display registration status before a particular command.

You might want to specify DISPLAY_REGISTRATION_BEFORE_COMMAND=N before deleting registrations to verify that they are no longer active.

You can use this parameter with the DISPLAY_REGISTRATION_AFTER_COMMAND parameter to display registration status information before and after a command.

DISPLAY_REGISTRATION_DETAIL={

N

|Y}

Controls how attributes of the registration are reported. Options are:

N
. The attributes of the registration are reported on a single line.
Y
. The attributes of the registration are reported across multiple lines.

This parameter applies when the following commands are used:

Command DISPLAY_REGISTRATION
Active, Delete, and Suspend commands with parameters DISPLAY_REGISTRATION_BEFORE_COMMAND or DISPLAY_REGISTRATION_AFTER_COMMAND

Default is N.

SHOW_EXPANDED_STATEMENT={

N

|Y}

Controls whether to display the input command statements in an expanded format that includes the parameters that you specified and the other valid parameters that you did not specify but are in effect with their default values or an asterisk (*) wildcard entry. Options are:

N
. Do not report the command statements in an expanded format.
Y
. The command statements are reported in an expanded format.

Default is N.

Other Parameters

GENERIC={

N

|Y}

Indicates whether registration-specific commands process only a single registration or multiple registrations. This parameter is not supported for the DELETE_INACTIVE_REGISTRATION and DISPLAY_REGISTRATION commands, which act generically across multiple registrations by default.

N
. The commands process only a single registration.
Y
. The commands process more than one registration. If you need a command to process more than one registration, specify GENERIC=Y either globally within the SET_CONTROL_VALUE command or within the registration-specific command. When you specify GENERIC=Y, you must also specify masks that contain the asterisk (*) wildcard in certain parameters of the registration-specific commands, such as REGISTRATION_NAME.

You can override this global setting for a particular registration-specific command by including the GENERIC parameter in the command.

Default is N.

GLOBAL_VALIDATE={

N

|Y}

Controls whether to validate the registrations. Options are:

N
. Perform processing for the command and update registrations on the CCT file.
Y
. Validate the registrations. Perform processing for the command, except for modifying the registration. Processing can be performed by a user who has read permission to the CCT file.

For example, if GLOBAL_VALIDATE=Y when suspending a registration, the following actions are performed:

The selected registration or registrations are read and reported if DISPLAY_REGISTRATION_BEFORE_COMMAND=Y.
The selected registration or registrations are read and added to the process list.
The selected registration or registrations receive last-minute validations according to the command and errors are reported. For example, only active registrations can be suspended and only suspended registrations can be activated.
The modification step is not executed.