Override Work Data Set Allocations

Configuring Your System for CA Chorus for DB2 Database Management › Override Work Data Set Allocations

Override Work Data Set Allocations

You can override the Object Migrator and DBA Command Manager for DB2 work data set allocations on specific systems and for specific users. To do so, edit the members in the Object Migrator configuration data set to add <SYSTEM> and <PREFIX> control statements.

Follow these steps:

Edit the configuration members that you want to update to add the following control statements, replacing the italicized text with valid values:
```
<SYSTEM:lpar>
<PREFIX>
%TSOPREFIX or %USERID or Qualifier
</PREFIX>
</SYSTEM:lpar>
```
<SYSTEM:lpar>

Specifies the LPAR (logical partition) or system-specific information.

lpar

Identifies the logical partition or system name. Replace with values that are valid at your site. For example, if the system name is D10A, specify <SYSTEM:D10A>.

<PREFIX>
Specifies the prefix or high-level qualifier for use with the data set. The following symbols are supported for <PREFIX>:
- %TSOPREFIX (uses the TSO prefix from the TSO user profile table)
- %USERID (uses the CA Chorus user ID as the high-level qualifier)
- Qualifier (uses the specified qualifier). For example, MCOE.CHORUS01;. The semi-colon (;) is required.
If <PREFIX> is specified in the user configuration member or in the global @DEFAULT member, the user member is used first and then the global member.

If <PREFIX> is not specified, tsoprefix.userid.ETJ is used. If these values are the same for a user, userid.ETJ is used.
Note: To specify override values for a specific member on multiple systems, repeat these statements in the member as needed.

The member is updated.
Repeat as needed for each member.
The data set allocations are overridden.

Example: Override Data Set Allocations Using the TSO Prefix

This example shows how to use the TSO prefix during data set allocations:

<SYSTEM:SYS1>                                                      
<PREFIX>
%TSOPREFIX
</PREFIX>
</SYSTEM:SYS1>

If these control statements are added to the @DEFAULT member, the agent uses TSOPREFIX.ETJ.* if no user configuration member is specified. Otherwise, the agent retrieves the TSO prefix from the TSO user profile table and uses it.

Example: Override Data Set Allocations Using the CA Chorus User ID

This example shows how to use the CA Chorus user ID as the high-level qualifier during data set allocations:

<SYSTEM:SYS1>
<PREFIX>
%USERID
</PREFIX>
</SYSTEM:SYS1>

If these control statements are added to the @DEFAULT member, the agent uses the value userid.ETJ.* during run time if no user configuration member is specified.

Example: Override Data Set Allocations Using a Different High-Level Qualifier

This example shows how to use a site-specified high-level qualifier during data set allocations:

<SYSTEM:SYS1>
<PREFIX>
CHORUS.TEMP;
</PREFIX>
</SYSTEM:SYS1>

Example: Override Data Set Allocations Using the MYID.HLQ Prefix

This example shows how to use the MYID.HLQ prefix during data set allocations. To do so, add <SYSTEM> and <PREFIX> control cards to the user ID member:

<SYSTEM:SYS1>                                                        
<PREFIX>       
MYID.HLQ;
</PREFIX>
</SYSTEM:SYS1>

During run time, the agent ignores the values in the @DEFAULT member and instead uses the value MYID.HLQ.ETJ*. If these control statements are added to the @DEFAULT member, the agent uses the value MYID.HLQ.ETJ* during run time if no user ID member is specified.

Example: Override Data Set Allocations without Specifying a Prefix Value

This example shows how to override data set allocations without specifying a prefix value to <SYSTEM> and <PREFIX> control cards in the user ID member:

<SYSTEM:SYS1>                                                     
<PREFIX>      
</PREFIX>
</SYSTEM:SYS1>

During run time, the agent ignores the @DEFAULT member and uses the value TSOPREFIX.USERID.ETJ.* if the values for TSOPREFIX and USERID are different. If the values for TSOPREFIX and USERID are the same, the agent uses the value TSOPREFIX.ETJ.*. If these control statements are added to the @DEFAULT member, the agent uses TSOPREFIX.USERID.ETJ.* if the values for TSOPREFIX and USERID are different. If the values for TSOPREFIX and USERID are the same, the agent uses the value TSOPREFIX.ETJ.*.

Example: Override Data Set Allocations When the Configuration File contains the @DEFAULT and User ID Members

These examples show how to override the prefix values that are based on the originating system during data set allocations. To do so, add <SYSTEM> and <PREFIX> control cards to the @DEFAULT and user ID members:

The @DEFAULT member contains the following:

<SYSTEM:SYS1>                                                       
<PREFIX>    
MCA11   
</PREFIX>
</SYSTEM:SYS1>

The user ID member contains the following:

<SYSTEM:SYS2>                                                     
<PREFIX>    
MCOE     
</PREFIX>
</SYSTEM:SYS2>

During run time, the agent uses the value MCA11.ETJ.* for requests coming from SYS1 and the value MCOE.ETJ.* for requests coming from SYS2.