OK, we have a PROC set up for DBUTLTY in SYS2.PROCLIB that has our standard execution. The TARGET= tells it which database system to use.
this is for CDC database 2009, that has 3 tables, 2 areas and one index.
the CTL table has only one row in it and it gets updated, never deleted, so there would be no benefit to run OLREORG on it.
//jobcard would be here...with a COND=(0,NE) to stop any step that does not completion code 00.
//CXXSUM1 EXEC DBUTLTY,TARGET=XX
//SYSIN DD *
COMM OPTION=STATS,DBID=2009
REPORT AREA=CXX,DBID=2009,TYPE=A
/*
//OLREORG1 EXEC DBUTLTY,TARGET=XX
//SYSIN DD *
OLREORG TABLE=MNT,DBID=2009,REFGROUP=2
/*
//OLREORG2 EXEC DBUTLTY,TARGET=XX
//SYSIN DD *
OLREORG TABLE=TSN,DBID=2009,REFGROUP=2
/*
//DEFRAG EXEC DBUTLTY,TARGET=XX
//SYSIN DD *
DEFRAG DBID=2009
/*
//CXXSUM2 EXEC DBUTLTY,TARGET=XX
//SYSIN DD *
COMM OPTION=STATS,DBID=2009
REPORT AREA=CXX,DBID=2009,TYPE=A
/*
//