FPSAPP.ADM_LOAD_COMBINED

LOAD_JOB

Name of load job (* inherited from FPSADMIN.CFG_JOBS)

IS_SCHEDULED

LOAD_ORDER

Order of objects to load within the load job (* inherited from FPSADMIN.CFG_SCHED)

OWNER

OBJECT_NAME

This could be an object name (we will disable loading of that object in the scheduled jobs), a load job (we will disable loading of all objects in that scheduled job), an FPSAPP prefix (we will disable loading of all objects with that prefix), a constraint (we can explain why it is permanently disabled), or a trigger (technically an object so we can get away with omitting this from the column name and also to explain why it is permanently disabled). (* inherited from FPSADMIN.CFG_DISABLED)

OBJ_TYPE

METHOD

Method used to load data in table or execute procedure (* inherited from FPSADMIN.GEN_LOAD_METHODS)

ERR_IF_NO_ROWS

If set to Y then the job will error if no rows are inserted. This cannot be used with DBPM because the match logic frequently updates no rows. (* inherited from FPSADMIN.CFG_TABLES)

OTHERS_TO_LOAD_IF_CHG

This allows us to load a table only if another table changed. This is rarely used but can save time. (* inherited from FPSADMIN.CFG_TABLES)

DO_NOT_CHECK_DIFFS_LOOP

For tables loaded by ADM_TABLE_LOOP the default is to use a minus query to check for differences and only update the necessary rows. But if we know that all rows will change on each load then we can skip this check and just update all rows. (* inherited from FPSADMIN.CFG_TABLES)

WHY_DISABLED

DISABLED_OBJECT_NAME

IS_PERMANENT

This boolean flag includes whether this is permanently disabled at this site. With the default value of N, SYSMNTR_DISABLED will remind you that it is disabled which can be helpful so you do not accidentally leave it disabled forever. (* inherited from FPSADMIN.CFG_DISABLED)

DO_NOT_COMMIT

If this is set to Y then we will not commit after this object. This allows an entire job consisting of multiple objects to run and then commit at the end. Our 3min job must have this flag set to Y. (* inherited from FPSADMIN.CFG_SCHED)

WARN_SEC_IF_OVER_ONE_MIN

Our default warning limit for CHK_SLOW is over one minute but many jobs, particularly those which are shiftly or daily or weekly, normally take longer. Once an acceptable time is established for a long running job enter about 25% higher here then the object will only appear in CHK_SLOW if it gets slower. (* inherited from FPSADMIN.CFG_SCHED)