Академический Документы
Профессиональный Документы
Культура Документы
TCS Internal
MULTILOAD
Accounts
A# UPI
Customer
C# UPI
Account_Customer
A# C# NUSI UPI
Trans_Hist
A# NUPI DATE
Each New Account requires an INSERT into the Accounts table and an INSERT
into Account_Customer.
MultiLoad environment variables can be checked to optionally COLLECT STATISTICS as part of the job.
&SYSDELCNT_ &SYSINSCNT_ &SYSUPDCNT_ &SYSETCNT_ &SYSUVCNT_ where _ is 1 to 5 " " " "
Note:
.BEGIN IMPORT MLOAD TABLES Accounts, Account_Customer, Customer, Trans_Hist ; 1st table
TCS Internal
2nd table
3rd table
4th table
Work Tables
IMPORT Task: WORKTABLES wt_table1, wt_table2,
.BEGIN parameters
Default is in users default database and the work table is named WT_TableName. Alternative may be specified as DataBaseName.WorkTableName.
There must be one work table defined for each data table.
Example: .BEGIN [IMPORT] MLOAD TABLES Employee, PayCheck WORKTABLES util_db.WT_Emp ,util_db.WT_Pay ERRORTABLES util_db.ET_Emp util_db.UV_Emp ,util_db.ET_Pay util_db.UV_Pay ...;
Error Tables
ERRORTABLES et_tab1 uv_tab1, et_tab2 uv_tab2, ...
.BEGIN parameters
default is the users database and the table is named ET_Tablename. contains any errors that occur in the Acquisition Phase. contains primary index overflow errors that occur in the Application phase
default is the users database and the table is named UV_Tablename. contains Application Phase errors.
Uniqueness violations Constraint errors Overflow errors on columns other than primary index
Example:
TCS Internal
.BEGIN [IMPORT] MLOAD TABLES Employee, PayCheck WORKTABLES util_db.WT_Emp ,util_db.WT_Pay ERRORTABLES util_db.ET_Emp util_db.UV_Emp ,util_db.ET_Pay util_db.UV_Pay ...;
ERRLIMIT
ERRLIMIT ErrCount Without ERRPERCENT:
.BEGIN parameters
Specifies approximate number of data errors permitted during Acquisition. Does not count Uniqueness violations.
Specifies a percentage of data errors after an approximate number of records has been transmitted.
Example:
ERRLIMIT 10000 5
In this example, after processing 10,000 input records, the system looks for an error rate of 5%.
TCS Internal
CHECKPOINT
Rate may be specified in the Acquisition Phase of a complex IMPORT task as:
.BEGIN parameters
A number of incoming records (exact count; not less than 60) A time interval in minutes (approximate; less than 60)
If no CHECKPOINT value is specified MultiLoad will checkpoint every 15 minutes, and at the end of each Phase. The default is 15 minutes.
Example 1:
CHECKPOINT 30
Example 2:
CHECKPOINT 100000
TCS Internal
Used to specify the maximum, and optionally, minimum sessions generated by MultiLoad.
TENACITY
TENACITY 10
Number of hours MultiLoad will try to establish a connection to the system. The default is 4 hours.
SLEEP
SLEEP 3
Number of minutes MultiLoad waits before retrying a logon; must be greater than 0. The default is 6 minutes.
NOTIFY
NOTIFY OFF
NOTIFY LOW NOTIFY MEDIUM for the most significant events. NOTIFY HIGH for every MultiLoad event that involves an operational decision point. Internal OFF suppresses the notify option. TCS NOTIFY
Note: The MultiLoad manual specifies in detail which events are associated with each level.
NONE MultiLoad will not perform an AMPCHECK. It will proceed if AMPs are offline, provided all target tables are
FALLBACK.
APPLY MultiLoad will continue in all phases except the Application phase with
AMPs offline, provided all target tables are FALLBACK. This is the default.
ALL MultiLoad will not proceed with down AMPs, regardless of the
protection-type of the target tables. Most conservative option.
TCS Internal
TCS Internal
F1
F2
F3
TCS Internal
A U D
PI PI PI
F1 F4 F5
F2
F3
TCS Internal
Record_Layout ; trans_type PI F1 F2 F3 F4 F5
1 2 * * * 6 *
MARK or IGNORE
DO INSERT FOR [MISSING UPDATE] ROWS Operation: INSERT (Duplicate violation) UPDATE (Duplicate violation) UPDATE (Fails - missing row) DELETE (Fails - missing row) UPSERT (If successful) UPSERT (Fails) Default:
Marked in UV_tablename Marked in UV_tablename Marked in UV_tablename Marked in UV_tablename Ignored Mark failure of INSERT in UV_tablename
Example of UPSERT failure: 1. PI value doesnt exist, so UPDATE cant occur. 2. INSERT fails because of check violation - e.g., cant put character data in a numeric field. TCS Internal
DUPLICATE MISSING
Whether or not to record duplicate or missing INSERT, UPDATE, OR DELETE rows into the UV_error_table and continue processing.
Key statement that indicates an UPSERT. An SQL UPDATE followed by an SQL INSERT is required.
Example 1:
The default for an UPSERT operation is to not mark missing update rows.
Example 1:
TCS Internal
When the MARK MISSING UPDATE ROWS is used with an UPSERT, this will place (in the UV_table) data rows that cant be updated (no PI). If the insert also fails, the insert record is also marked in the UV_table.
DUPLICATE MISSING
Summary
On the .BEGIN statement, optionally, the names of work and error tables can be specified.
You can:
Specify error limits and checkpoints. Limit sessions. Designate time allowed for connection.
.DML commands define Labels and Error Treatment conditions for one or more operations.
You can use FastLoad or MultiLoad INMODs.
TCS Internal
Review Questions
1. Complete the BEGIN statement to accomplish the following:
Specify an error limit count of 200,000 and an error percentage of 5%. Specify a checkpoint at 50,000 records. Limit the sessions to 4. Set the number of hours to try to establish connection as 6.
.LOGTABLE RestartLog_mld; .LOGON ________________; .BEGIN [IMPORT] MLOAD TABLES Trans_Hist
TENACITY 6
.END MLOAD ;
TCS Internal
Review Questions
1. Complete the BEGIN statement to accomplish the following:
Specify an error limit count of 200,000 and an error percentage of 5%. Specify a checkpoint at 50,000 records. Limit the sessions to 4. Set the number of hours to try to establish connection as 6.
.LOGTABLE RestartLog_mld; .LOGON ________________; .BEGIN [IMPORT] MLOAD TABLES Trans_Hist