SYSOUT Space utilization questions in View Database

Products

• View

Issue/Introduction

1) Is there a way to find out whether a JOB was taken from TAPE to DASD which filled the Index DB and caused the alert?

2) How to find which JOB is taking more space?

3) And how to move the high space utilization jobs to tape?

Environment

Release: View 12.2

Resolution

1) A sysout being loaded to DASD from TAPE will not have any effect on the filling of the View index. The alert, the SARDBI23 index message, was caused by regular database usage.

2) To identify the space taken by reports with a location of DISK or PERM, run the below SARGRW program.

//XXXXXXXX JOB ...

//SARGRW01 EXEC PGM=SARGRW
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== Modify, if used
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(5),,CONTIG)
//SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(5),,CONTIG)
//SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(5),,CONTIG)
//SYSUDUMP DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//OUTFILE DD SYSOUT=*
//PRTFILE DD SYSOUT=*
//SYSIN DD *
/CONTROL SEQ=RID DATABASE=view_db_hlq
/IF (LOC = 'DISK' OR LOC = 'PERM')
/ PRINT ID 'ID'
/ PRINT JOBNAME 'JOBNAME'
/ PRINT JOBID 'JOBID'
/ PRINT GEN 'GEN '
/ PRINT SEQ 'SEQ '
/ PRINT ARCHDATE 'ARC DATE'
/ PRINT ARCHTIME 'ARC TIME'
/ PRINT LOC 'LOC'
/ PRINT LINES 'LINES '
/ PRINT PAGES 'PAGES '
/ PRINT DISKBLKS 'BLOCKS'
/ PRINT XCODE 'XCODE'
/ PRINT TAPESEQ 'TSEQ '
/ PRINT DRSEQ 'DRSEQ'
/END
/*
//

3) For a report with a location of DISK, the next View backup will write it to tape. For reports with a location of PERM, the line command "DD" can be used, to remove a large report from the disk layer.