Platform Analytics 7 Dataflow

WI_JOBTHROUGHPUT table

This describes the wi_jobthroughput table and how each column of data arises from the LSB_EVENTS table.
The wi_jobthroughput get its data from Data Collection Table LSB_EVENTS. The data is then inserted into this table. The "Submitted job" is the number of jobs that got submitted within this hour The "Done job" is the number of jobs that got finished successfully (not exited). The "Exited job" is the number of jobs that got exited. This means that the job exit status indicated this job got exited without finishing.
This is the column description of each data column of WI_JOBTHROUGHPUT and how each column is filled with data.
Column Name
Description
Key
CLUSTER_CODE
This comes from the CLUSTER_NAME field in the raw table. Once we get the cluster_name, we then look it up in the wi_clustercode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_clustercode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing sequence+1.
Primary key
TIME_PERIOD
This is in GMT time zone and is ended per hour.
Primary key
USER_CODE

This comes from the USER_NAME

field in the raw table.

Once we get the user name, we then look it up in the wi_usercode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_usercode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing sequence number +1.
Primary key
PROJECT_CODE

This comes from the PROJECT_NAME

field in the raw table. If this is null, then set this field to "-".

Once we get the host name, we then look it up in the wi_projectcode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_projectcode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing sequence number +1.
Primary key
HOST_CODE

This comes from the HOST_NAME field in the LSB_EVENTS_EXECHOSTLIST table . If this is null, then set this field to "-". Also if it contains a list of host, we'll only use the first one for this field.

Once we get the host name, we then look it up in the wi_hostcode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_hostcode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing sequence number +1. If it is null, then the "Subhost_Code" field will be used.
Primary key
QUEUE_CODE

This comes from the QUEUE

field in the raw table. Once we get the queue name, we then look it up in the wi_queuecode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_queuecode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing sequence number +1.
Primary key
SUBMIT_NUM
This is how many jobs got submitted within this hour.

EXIT_NUM
This is the number of jobs that have exited within this hour.

DONE_NUM
This is the number of jobs that have finished within this hour.