Using the TSSXTEND Utility with WHOHAS

This section contains the following topics:

Required Authority for TSSXTEND Utility with WHOHAS

About the TSSXTEND Utility with WHOHAS

When you run the TSSFAR utility with the RESOURCE option, the possibility exists that the utility may identify multiple reference pointers that may not be current.The TSSXTEND utility with the WHOHAS option lets you resolve these pointers in an automated fashion.

This section details the requirements to run the TSSXTEND utility with the WHOHAS option and its behaviors in response to the output of the TSSFAR utility using the RESOURCE option.

The TSSXTEND utility WHOHAS option flags the following:

Permits for resources that are not owned.
Target ACIDs (owning ACIDs) that will not hold the added WHOHAS information.

Important!: The job runs to completion even if it flags issues as previously detailed; however, before using the extended security file, you must continue to run the job until it does not flag any ownership concerns. This means you may need to run TSSXTEND WHOHAS multiple times. TSSXTEND will fail if it detects that the same output file used in a previous TSSXTEND WHOHAS run is specified without reinitializing the output file between the two runs. If you need to run TSSXTEND utility with the WHOHAS option more than once, you must delete and reallocate the output SECFILE each time. Until you correct the ownership errors, do not implement the TSSXTEND WHOHAS output security file.

Before you run TSSXTEND WHOHAS, note the following ownership concerns:

Run TSSXTEND with WHOHAS against the backup file. We recommend that you execute a TSS BACKUP prior to running the TSSXTEND WHOHAS utility. This ensures that the newly extended security file will be current.
Run TSSXTEND with WHOHAS using the same system where the security backup file is active. A backup file for a shared security file can be used as input on the TSSXTEND WHOHAS option on any of the sharing systems. You can only use a CPF-synchronized file as input on TSSXTEND WHOHAS under the system where the file was active.
TSSXTEND with WHOHAS takes significantly longer to execute than running a normal TSSXTEND without the WHOHAS option because the this option causes CA Top Secret to rebuild the WHOHAS data for the entire security file. Expect the added runtime to be ten times as long. For example, a TSSXTEND without WHOHAS that typically runs for 20 minutes will likely take approximately 3 hours when run with WHOHAS.

Required Authority for TSSXTEND Utility with WHOHAS

The following users may run TSSXTEND utility with WHOHAS:

The MSCA
A user with USE access to the entity TSSUTILITY.TSSXTEND in the CASECAUT resource class.
This access may be granted by an administrator using the following command:
```
TSS PERMIT(user) CASECAUT(TSSUTILITY.TSSXTEND) ACCESS(USE)
```

Run the TSSXTEND Utility with WHOHAS

Use this procedure to resolve reference pointers using the TSSXTEND utility with the WHOHAS option.

To obtain a valid SECFILE using TSSFAR and TSSXTEND with WHOHAS

Run the TSSFAR utility using the RESOURCE option.
The utility flags any ownership issues.
Run TSSXTEND WHOHAS to clean up the ownership problems flagged with each run, which includes:
- Defining ownerships.
- When an ACID is not large enough to handle the added WHOHAS information, you need to redefine ownership at multiple levels.
The utility resolves the out-of-date reference pointers.
Re-run the TSSFAR utility using the RESOURCE option.
After you do not have any un-owned resources permitted or target ACIDs (owning ACIDs) that exceed the maximum size, activate and leverage the extended security file using your standard, established site procedures.