Overview |
|
Tasks |
|
Included with |
Tivoli Problem Management |
The flat file option |
If you choose to archive data to a flat file,
you must be aware that manipulating the exported flat file requires significant effort.
The files are large and generally unwieldy. Choosing the flat file option results in a file that places one record from a table into one line in the file. There are five tables from which the archive utility reads data, but there are six label types, or tags, for the lines in the flat file. |
Flat file tags |
Labels are called tags in the
eaacust.kb knowledgebase. The flat file tags are:
The reason there is a CALL label as well as a CALLI label is that CALLI indicates an information call. An information call is a call that is created in Tivoli Problem Management without opening a corresponding problem. This means that only a CALL and one or more SESION records were created in the Tivoli Problem Management database. |
Flat file format |
The fields in a flat file occur in the same
order as they do in the Tivoli Problem Management Entity Relationship Diagram for your
particular version of Tivoli Problem Management. There is a distinction between string and non-string values. If a column is created as a char value, it is considered to be a string in the flat file. In this case, the value is surrounded by double quotes, like "string." The delimiter for columns in the database is considered a non-string and is not surrounded by double quotes. |
Creating a parse program for a flat file |
When you create a program to parse the
individual lines of a flat file, you need to read the tag. The tag is followed by a triple
pipe sequence (|||) to differentiate the tag from the start of the first field. When you create a parse program for a flat file, you should do the following:
All strings can be customized by editing eaacust.kb. The file export characters are shown here.
If changes are made to eaacust.kb, the file must be re-parsed. |
||||||||||||
Processing a flat file |
To process a flat file created by the Archive
Utility, use the following outline for the algorithm that recreates the relations between
the CALL, SESION, PROBLEMS, WORK_HISTORY, and PROBLEM_HISTORY tables.
|