Starting ARCMAIN from z/OS
This 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;
|
|
|
Note: 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:
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.
Calculating Region Size
Table 1 is applicable to Teradata ARC 8.0 or earlier. Use the information in this table to estimate the minimum region size (in kilobytes) needed to run Teradata ARC from z/OS.
Note: This table provides estimates for archive or restore operations only. Copy operations might require more memory.
Number of Sessions |
Region Size For 200 Objects |
Region Size For 2,000 Objects |
Region Size For 8,000 Objects |
10 |
2,500 KB |
3,200 KB |
5,620 KB |
50 |
4,420 KB |
5,140 KB |
7,540 KB |
100 |
6,820 KB |
7,540 |
9,940 KB |
where
Table Element |
Description |
Number of Objects |
The number of databases + number of tables and stored procedures to be archived, restored, or copied. The ALL keyword expands the number according to this query: SELECT count (*) from database DBC.CHILDREN WHERE PARENT = ‘<db>’ |
Sessions |
number of data sessions to use in the operation. |
Example
In this example, database db2 and table db3.a are not children of database db.
ARCHIVE DATA TABLES (db) ALL,(db2),(db3.a),
RELEASE LOCK,
FILE=ARCHIVE;
If the SELECT query returns 5 for db, the total number of objects in the ARCHIVE DATA TABLES statement is 7.