Relation section rules
This section must adhere to the following rules:
- The key properties of the relation can be either class or interval references or explicit keys. All key properties for the relation must always be present.
- The name of the property that is a class reference is the same as the name of the corresponding class.
In the data records for the class references, the ordinal number of corresponding class instances in the input file is specified.
For example, the PARTOSAD relation appears as follows:
T;PARTOSAD
K;INTVL,PARTNS,OSAS,TCPINB,TCPOUTB,UDPINB,UDPOUTB
;1,1,1,0.002,15.5,25.1,37,
;1,1,2,0.002,14.5,25.1,37,
;1,1,3,0.002,13.5,25.1,37,
;1,2,1,5.002,115.5,25.1,37,
;1,2,2,0.002,15.5,25.1,37,
;1,2,3,0.002,15.5,25.1,37,
;2,1,1,0.002,15.5,25.1,37,
;2,1,2,0.002,15.5,25.1,37,
...In this input file, the first data record is related to Interval 1, LPAR 1 and OSA Link 1, which translates to:
- The interval 08/09/11 from 00:00 to 01:00
- The LPAR named LPPROD
- OSA link OSAL1
- Only the following types of data are permitted in non-key relation properties:
- Additive metrics represented as rates over time (such as Kbytes/sec, Transactions/hour, Calls/day, or IO/sec)
- Average metrics represented as rates over one of the additive metrics above, that are present in the same relation (such as average cost in Dollars/Transaction or average response time of an I/O operation in msec/IO)
Nonadditive absolute numbers like memory size in Mbytes or the number of available scratch tapes
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*