Data Integration Studio - provide macro vars for source / target tables in Teradata Loader transform
on 04-07-201511:13 AM - last edited on 10-10-201509:11 PM by LainieH
There is a known issue with our connection via Single Signon for SAS Profile between sas.com/support.sas.com and the communities. The fix is a high priority and will be rolled out soon.
Here the current workaround: Go back to support.sas.com or sas.com from the community page, logout and log back in again on communities.sas.com. This will fix the problem for that particular time.
We expect this problem to be resolved very quickly. Thank you,
LainieIt would be very helpful to have macro variables available in the loader pre-code which provide the source / target libnames & table(s) in the Teradata Loader transform ( perhaps the generic Loader transform as well ). This would allow the creation of a generalized macro to drop the automatically created TPT fastload error / log / work tables, e.g. those suffixed with _ET, _UV, _WT, _RS, _LT, in the loader pre-code in the event the previous load resulted in errors. By default, the error / log / work tables created are the target table name followed by the suffix, eg. target table is Fuzzy_Navel, tables created would be Fuzzy_Navel_ET, Fuzzy_Navel_UT.
Yes, some of those names can be specified in the TPT Loader parms, eg. TPT_ERROR_TABLE_1, TPT_ERROR_TABLE_2, TPT_LOG_TABLE, but others cannot. DIS knows what the target lib/table is because it knows the metadata entity hanging off the transform and it uses those values to build the code, let the programmer use them too! eg. automatically generate the following:
%let etls_source_lib = work; * probably from &syslast;
%let etls_source_table = my_source_tbl; * probably from &syslast;
%let etls_target_lib = td_stg;
%let etls_target_table = td_table_nm;
The target macro variables would allow the programmer to utilize a macro to drop the left over error / log / work tables in the event they existed from the prior job to ensure the current job didn't abend when the error tables are automatically created again to start the load. While the usefulness of the source macro vars isn't defined, they might be helpful as well, who knows, provide for completeness.
If a more generalized approach was implemented, perhaps for all transforms, and more than one is lib/table is present, use the same mechanism as used by the multi-value macro vars created by EG when multiple values are selected from a prompt ( only showing the proposed table macro vars to avoid clutter );