March Products 204 - Manual (Page 41)

——————————————————————————————————————————
Running SirFile under BATCH204
——————————————————————————————————————————
——————
CHAPTER 12
Running SirFile under BATCH204
Running SirFile's database refresh in batch has two advantages over running it in the
online:
1. It allows the database refresh to be scheduled on a regular basis by a job
scheduling system.
2. It allows the most expensive processing in SirFile to be run in off hours.
In addition, if you have specified “N” for the following prompt on the System Default
thresholds screen, the CFULLP statistic is only calculated if the refresh is run via the
SIRFIELD BATCH command:
Collect CFULLP only on specified files
CFULLP is a more accurate measure of the full status of Table C, but it requires that a
TABLEC command be executed, which can be a very resource-intensive operation.
Following is a sample job fragment and CCAIN stream showing the SirFile refresh being
run in BATCH204.
//SIRFILE JOB (0) 'Batch Refresh',CLASS=X
//REFRESH EXEC PGM=BATCH204,SYSOPT=187
//...
//CCASYS DD DSN=M204.CCASYS,DISP=SHR
//CCAGRP DD DSN=M204.CCAGRP,DISP=SHR
//SIRFILE DD DSN=M204.SIRFILE,DISP=SHR
//SIRLOCAL DD DSN=M204.SIRLOCAL,DISP=SHR
//PROCFILE DD DSN=M204.PROCFILE,DISP=SHR
//PROCFIL2 DD DSN=M204.PROCFIL2,DISP=SHR
//...
//CCAIN *
NFILES=99,NDIRS=99,NDCBS=99,NUSERS=2,NSERVS=2,...
IODEV=15,POLLNO=1,NOTERM=1
LOGON filemanagr
password
OPEN FILE PROCFILE1
password
OPEN FILE PROCFIL2
password
...
SIRFILE BATCH
EOJ
/*
//
——————————————————————————————————————————
SirFile User's Guide 35