View - Daily Backup running extremely long. Causes JOBQ shortage

Products

• View

Issue/Introduction

Our daily backup is running 8-10 hours a day, which has caused JOBQ and JNUM shortages on numerous occasions.

After the backup runs, it then takes hours for View to pick up all the output created during the 8-10 hours that the backup was running. 

Running both standard and interim backups, could it be that the DB could be performing backups potentially all day? 

During an interim backup, does View pick up reports?

Environment

Release : 14.0

Resolution

It was suggested that the client run the following SARDBASE job, to collect database statistics both before and after a REORG ASYNCH:

//XXXXXXXX JOB ...                                                
//SARDBASE EXEC PGM=SARDBASE,PARM='VIEW_HLQ'  <=== MODIFY DB NAME 
//STEPLIB  DD  DISP=SHR,DSN=VIEW.CVDELOAD     <=== MODIFY, IF USED
//SYSPRINT DD  SYSOUT=*                                           
//SYSIN    DD *                                                   
STATUS  
REORG ASYNCH
STATUS                                                      
/*                                                                
//   

Though the REORG ASYNCH ran for a long time, the amount of database index usage dropped by 10%. 

It was also suggested that the client may want to make the database in question a static (historical) database, and to start with a new database.