Directions for those cases where a CA MICS timespan has run out of space as indicated by a SB37 or SE37 abend and a larger DASD volume is available for the new file. This solution works when the step was not in AGING when the abend occurs.
- Allocate the new timespan on the larger volume by using a neutral name for now. For example, for
Make sure that the DCB information for the new dataset is the same as that for the old one and that the primary space allocation for the new one is larger than the total allocation for the old dataset.
The DCB information would typically look like
The RECFM must be FS. The LRECL and BLKSIZE values might be different for your site.
- Copy the data from the old timespan to the new one by using a SAS job like this one:
//S1 EXEC MICSSHRx
//NEWFILE DD DISP=OLD,DSN=prefix.MICS.DAYS.NEW
//SYSIN DD *
PROC COPY INDD=DAYS OUTDD=NEWFILE;
- Rename the old timespan to a neutral name like:
- Rename the new timespan to the actual production name as in
Once this has been done, the normal DAILY update job can be submitted or restarted in the step that filed.