Starting ARCMAIN from z/OS - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

Sample JCL for Starting ARCMAIN from z/OS

The following sample JCL shows how to start Teradata ARC from z/OS:

//ARCJOB   PROC  ARCPARM=,DBCPFX=,

//USERJOB  JOB  <job info>
//ARCJOB   PROC  ARCPARM=,DBCPFX=
//              DUMP=DUMMY,DUMPDSN=,DSEQ=,DVOL=,
//              RESTORE=DUMMY,RSTRDSN=,DBCLOG=
//*
//STEP1    EXEC PGM=ARCMAIN
//              PARM='&ARCPARM'
//STEPLIB  DD   DSN=&DBCPFX..AUTHLOAD,
//              DISP=SHR
//ARCHIVE  DD   &DUMP,DSN=&DBCPFX..&DUMPDSN,DISP=(,CATLG),
//              UNIT=TAPE,LABEL=(&DSEQ,SL),
//              VOL=SER=(&DVOL)
//ARCIN    DD   &RESTORE,DSN=&DBCPFX..&RESTORE&RSTRDSN,DISP=OLD
//DBCLOG   DD   DSN=&DBCPFX..&DBCLOG,DISP=OLD
//SYSPRINT DD   SYSOUT=*
//SYSUDUMP DD   SYSOUT=*
//         PEND
//*
//S1       EXEC ARCJOB,ARCPARM='SESSIONS=100 HEX',
//              DBCPFX=DBCTEST,DUMP='DUMP.DATA',DSEQ=1,
//              DVOL='TAPE01,TAPE02',DBCLOG='ARCLOG.DATA'
//SYSIN    DD   DATA,DLM=##

LOGON DBC,DBC

ARCHIVE DATA TABLES (PERSONNEL) ALL,
RELEASE LOCK,
INDEXES
FILE=ARCHIVE;

LOGOFF;
##
If specified, Teradata ARC honors a DCB=BLKSIZE value in the ARCHIVE DD statement, otherwise Teradata ARC uses the optimum BLKSIZE value supplied by the z/OS operating system.

ARCMAIN 14.10 (and later) writes a new format archive data set which always has the attribute DCB=RECFM=VBA. ARCMAIN 14.10 will read archive data sets of the new format and the old format, which it recognizes by the data set attribute DCB=RECFM=U.

The new archive data set format is not compatible with the old archive data set format. ARCMAIN depends on recognizing the archive data set format from the RECFM DCB attribute of the data set. On z/OS, if the RECFM DCB attribute is specified in the DD statement which identifies the archive input data set, that specification overrides and hides the actual RECFM DCB attribute of the data set itself, potentially misleading ARCMAIN as to the archive format.

Recommendation: Remove the DCB attributes RECFM, and BLKSIZE if present, from the DD statement for an input archive data set. On z/OS, it is never appropriate to specify those DCB attributes on input DD statements. It is always best to allow the input data set itself to supply the RECFM, LRECL, and BLKSIZE DCB attributes.

Starting with ARCMAIN 13.10, the RECFM, LRECL, and BLKSIZE DCB attributes for output archive data sets are set by default to optimum values for the output device supplied by z/OS. With ARCMAIN 13.10 and later, Teradata recommends removing RECFM, LRECL, and BLKSIZE DCB attribute specifications from all archive data set DD statements, whether ARCMAIN is reading or writing the archive data set.

The JCL example uses these syntax elements:

  • DUMP is the archive keyword, with DUMPDSN as the data set name for the archive output file. DUDISP specifies whether to KEEP or CATLG the output file.
  • DBCLOG is the log file data set name created by Teradata ARC.
  • DBCPFX is the high-level qualifier for Teradata Database load libraries.

The database DBCLOG card indicates the restart log file, and the data set must have RECFM either F, FBS or FS. For better results, set BLKSIZE near 32K. The ARCHIVE card is not needed in this example; it is shown for illustration purposes. Create and catalog database DBCLOG once and reuse it as needed. To create the database DBCLOG file, see the file on the release tape called ARCLOG, in dbcpfx.PROCLIB.