You can additionally specify the meta facts for a level in a plain text document called a schema record. This isn't always stored in the Repository but you could, as an example, maintain it in a record control or supply code manage gadget, or submit it on an intranet site.
Note: if you are using a schema report on an NLS machine, the schema report desires to be in UTF-8 layout. it's far, however, easy to transform textual content files among distinct maps with a WebSphere DataStage task. such a activity might examine statistics from a textual content record the use of a Sequential record level and specifying the correct person set at the NLS Map web page. it would write the facts to some other report using a Sequential report stage, specifying the UTF-8 map on the NLS Map page.
Some parallel process degrees can help you use a partial schema. which means that you most effective need outline column definitions for those columns that you are in reality going to perform on.
take into account that you ought to turn runtime column propagation on in case you intend to apply schema files to define column meta data.
complex information sorts
Parallel jobs support 3 complex facts types: v Subrecords v Tagged subrecords v Vectors while relating to complicated facts in WebSphere DataStage column definitions, you may specify completely qualified column names, as an instance:
A subrecord is a nested statistics shape. The column with kind subrecord does no longer itself define any storage, however the columns it carries do. these columns will have any records kind, and you can nest subrecords one inside any other. the level belongings is used to specify the shape of subrecords. the following diagram gives an example of a subrecord shape.
Child2 (string) LEVEL01
Grandchild3 (sfloat) LEVEL02