Documente Academic
Documente Profesional
Documente Cultură
Language) in Abinitio
26/04/2011
Author
Amitava Dey
amitava.dey@bt.com
About the Author
Having around 6 years of experience in Design & Development.
Currently working as a Billing Designer for GenIUS (Billing and Payment Platform)
project for British Telecom Plc., UK.
TCS Internal
Introduction
What is AbInitio
AbInitio is an ETL tool capable manipulating large volume of data.
AbInitio architecture:
Co>Operating System
Co>Operating System is a program provided by AbInitio which operates on
the top of the operating system and is a base for all AbInitio processes. It
provides additional features known as air commands which can be installed
on a variety of system environments such as UNIX, HP-UX, Linux, IBM
AIX, Windows systems. The AbInitio Co>Operating System provides the
following features:
- Manage and run AbInitio graphs and control the ETL processes
- Provides AbInitio extensions to the operating system
- ETL processes monitoring and debugging
- Metadata management and interaction with the EME
AbInitio EME
Enterprise Meta>Environment (EME) is an AbInitio repository and
environment for storing and managing metadata. It provides capability to
store both business and technical metadata. EME metadata can be accessed
from the Ab Initio GDE, web browser or AbInitio Co>Operating system
command line (air commands)
TCS Internal
Parameter Definition Language
PDL-embedded DML
• If you change to a version 2.13 Co>Operating System run host, you must turn
off dynamic script generation before running the graph.
TCS Internal
• If you change script generation back to GDE 1.13 Compatible, the GDE will
check to make sure you do not have any PDL-interpreted parameters (except
for layout parameters or eme-dependent parameters). If the GDE finds
otherwise, it will report an error and not change the setting.
in a transform with shell interpretation set will cause the following string to
be output:
But if you set pdl interpretation, the same rule will provoke an error, since
there is nothing for the \ to escape (the $ is already considered a literal
within the quotes).
TCS Internal
You can change such behavior by specifying $-text at the start of the value.
This makes PDL use "text" mode (with DML quoting conventions used
everywhere) for everything that follows the $-text:
The $-dml directive at the end of the value restores the PDL interpretation's
default DML mode.
Substitution in PDL
• If you don't want an identifier to be interpreted literally, you prefix $
to the identifier ($name) to specify parameter substitution.
• ${identifier} also specifies parameter substitution; the { }s are used
to delimit the identifier.
Escaping in PDL
• A single \, when it immediately precedes a $, escapes it.
• However, \ is interpreted as an escape only when it occurs
immediately before a $. In any other position, \ is regarded as a
normal character. The \ is not a global escape character.
TCS Internal
In record format strings interpreted in PDL, you don't have to specially escape \s (just
as you don't have to escape them in DML).
For example, the following definition for the test_value field in an Output File's
record format:
TCS Internal
will resolve like this:
Note also how the other fields' string('\n') definitions resolve as they were defined,
without any escaping.
TCS Internal
¾ PDL processing modes
There are three PDL parsing modes, which you can turn on and off with the following
inline directives:
• $-dml
DML mode (the default). Specifies that DML quoting conventions are to be used for
$"name" processing, and when scanning for embedded strings. This has the effect of
turning off $name substitution within strings.
• $-text
"Text" mode. Specifies that $name substitution is not to be suppressed inside quoted
strings. DML quoting conventions are still used for $"name" constructs.
• $-literal
¾ PDL examples
TCS Internal
Substitution examples
TCS Internal
Here the even number of \s results in the $ substitution occurring, and half of the \s
being output:
TCS Internal