ARCMAIN scripts usually only use DATASETNAME when referring to particular backup images, but failure to specify this value in an IOPARM string does not cause a Teradata Access Module for Tivoli error.
- Specified in the IOPARM string, that name is used.
- Not specified, the Teradata Access Module for Tivoli uses the external name that is passed by ARCMAIN when the file opens. This external name is specified as follows:
- If the ARCMAIN FILEDEF command line option is used, the name indicated in FILEDEF is used.
- If no FILEDEF option is identified, the Teradata Access Module for Tivoli uses the name identified on the FILE= clause. This name is limited to eight alphanumeric characters.
Names stored in the TSM server catalog are case-specific. Therefore, if a restore job or TDDSMC QUERY BACKUP command does not correctly capitalize the non-wildcard portions of a DATASETNAME, an error message results, stating that the backup image cannot be found. For example, FILE=DATA01 and FILE=Data01 can mean the same thing to ARCMAIN, but if FILE=DATA01 is an ARCMAIN backup job and FILE=Data01 is an ARCMAIN restore job, an error results.
The following table lists sample backup image names that can be used in the Teradata Access Module. Also listed are the corresponding storage object name that each backup image generates.
Backup Image Name | Storage Objects Created |
---|---|
tivarc <arc.txt ioparm=’datasetname=Marketing\Research.data’ | Marketing\Research.data\F0000 Marketing\Research.data\F0001 Marketing\Research.data\F0002 |
tivarc <arc.txt filedef=(CLUST001, Marketing_Cluster_001) (arc.txt file contains an ARCHIVE DATA TABLES statement with the clause: “FILE=CLUST001”) |
Marketing_Cluster_001\F0000 Marketing_Cluster_001\F0001 Marketing_Cluster_001\F0002 |
tivarc <arc.txt (arc.txt file contains an ARCHIVE DATA TABLES statement with the clause: “FILE=ARCHDATA”) |
ARCHDATA\F0000 ARCHDATA\F0001 ARCHDATA\F0002 |