When DISKACNT is using a minidisk to record its files, you cannot link its 191 disk in R/W mode (unless you want to break it). So, you should stop DISKACNT. Maybe an exec like this can do what you want - LINK & ACCESS DISKACNT 191 in RR mode - LISTFILE to find the oldest file - SET SECUSER DISKACNT * - CP SEND CP DISKACNT EXT - CP SLEEP 1 SEC - CP SEND DISKACNT END - CP SLEEP 1 SEC - CP SEND DISKACNT ERASE fn ft - CP SLEEP 1 SEC - CP SEND DISKACNT PROFILE - restore DISKACNT's SECUSER; DETACH the linked DISKACNT 191
If you have the REXX compiler, you can extract the IMMERASE MODULE from my PRFRUN package on VM's download lib. Store it on DISKACNT's 191, change its PROFILE EXEC to include a line like this: 'IMMERASE LOAD_ME_AS IMMERAS' When this setup is OK, you can simplify the code above to: - LINK & ACCESS DISKACNT 191 in RR mode - LISTFILE to find the oldest file - CP SEND DISKACNT IMMERAS fn ft - DETACH the linked DISKACNT 191 (I wrote IMMERASE to solve the problem of DISK FULL in MONWRITE: by loading a compiled REXX EXEC as a CMS Immediate command, this exec can execute commands without stopping the server. The compiled exec should not perform console IO). 2007/9/20, Derek Ackerman <[EMAIL PROTECTED]>: > > Is there any problem with erasing the oldest file every day on DISKACNTs > 191, or does DISKACNT have to be bounced to reaccess its 191. (I'm deleting > a file not adding one) > > Derek Ackerman > Capacity Planning etc. > (201) 759-0833 > -- Kris Buelens, IBM Belgium, VM customer support
