To add the start procedure to the PROCLIB for the started task:
//RMOSTC EXEC PGM=RMOSTC,TIME=1440,REGION=128M //STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR //SYSUDUMP DD SYSOUT=A //RMOPARMS DD DSN=CAI.CVDEOPTN(RMOPARMS),DISP=SHR //*RMOJTAB DD DSN=your.rmojtab,DISP=SHR
We recommend that you run CA Deliver with a minimum REGION=128M. This covers the current storage requirements for a daily cycle and can be useful and still provide a reserve that might be needed when extra storage is required.
Alternately, if you do not want to set the REGION size to 128M, start RMOSTC with a 128M region and continue with the same value for at least two days to monitor the processing for two daily cycles.
Bring RMOSTC down and review the IEF374I message in the JOBLOG; this log provides a high-water mark of the storage use.
The REGION value is in K not M, so divide the value nnnK by 1024 to get the value in M. Round the result up and add at least 5 to the result. This gives you the minimum region size to use.
For example:
VIRT 540K SYS 296K EXT 40998K SYS 10124K
The storage usage value in this example is 40998K. If you divide this by 1024 you get a value over 40 (round up the result to 41 and add 5).
The required region in this case is 46M.
Load module SARPAM in the CA View load library is required for direct‑to‑VIEW archival.
RMOPARMS can be a member of a PDS:
//RMOPARMS DD DSN=CAI.CVDEOPTN(RMOPARMS),DISP=SHR
The DD statement that is commented out in the procedure is an example only and must be changed to point to your rmojtab.
Note: For more information about how to code this table, see the chapter "The Database" in the Reference Guide.
| Copyright © 2012 CA. All rights reserved. |
|