Did you check the DASD volume that SYS0.IODF60.WORK is on? Maybe the DASD volume is out of space.
Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Feller, Paul Sent: Tuesday, October 31, 2017 6:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Odd HCD/IODF issue with "space" I have not run across this issue before when using HCD. This is a z/OS 2.2 system. The IODF has two z13 boxes and a z13s (CF) box. There are 27 lpars across the three boxes, that's counting the CFs. I would say we are an average size shop when it comes to the number of IO devices and channels. We don't try to be to creative when it comes to the IODF. I was correcting some issues with esoterics that are missing some DASD devices when I ran across this error. The first time I did increase the size of the work file from 1024 to 2048 blocks. I had then cleaned up some esoterics that had devices defined that didn't need them. When I got the error a second time I was surprised. I saved what I was doing and got out of HCD. I went back in and was able to make more changes until I got the error a third time. I repeated the save/exit/enter process. Again I was able to make more changes. I think I had to do this save/exit/enter process maybe two more times. The whole time the "size/usage" of the work file did not change. So back to my question, has anyone run across this type of issue? Did you have to do the same type of "process" to get things done? Here is an odd question. Is there a way to reorg (reclaim space) an IODF file? CBDA563I Space exhausted in work IODF SYS0.IODF60.WORK. Explanation: A definition record is being added to the work IODF, but there is no space left to complete the function. This condition may not only occur during Add and Connect actions but also during Update, Disconnect and Delete actions when device groups of a version 5 IODF must be temporarily split to perform the operation. System Action: In Dialog mode, system waits for user action. In Migration mode, processing terminates. The IODF is not updated. User Response: Extend the IODF (for example with the COPY IODF function) and rerun the action. - end - IODF name . . . . . . : 'SYS0.IODF60.WORK' IODF type . . . . . . : Work IODF version . . . . . : 5 Creation date . . . . : 2017-10-31 Last update . . . . . : 2017-10-31 13:52 Volume serial number . : OSS001 Allocated space . . . : 2048 (Number of 4K blocks) Used space . . . . . . : 2048 (Number of 4K blocks) thereof utilized (%) 33 Activity logging . . . : Yes Multi-user access . . : No Backup IODF name . . . : Description . . . . . : All DASD and some other devices have 31 bit UCBs -- IODF Version 5 format -- Processor ID . . . : SYSB IBM 2964-N30 (508) CSS Devices in SS0 Devices in SS1 Devices in SS2 Devices in SS3 / ID Maximum + Actual Maximum + Actual Maximum + Actual Maximum + Actual _ 0 65280 23158 65535 4536 65535 0 65535 0 Processor ID . . . : SYSC IBM 2964-N30 (608) CSS Devices in SS0 Devices in SS1 Devices in SS2 Devices in SS3 / ID Maximum + Actual Maximum + Actual Maximum + Actual Maximum + Actual _ 0 65280 23110 65535 4536 65535 0 65535 0 Thanks.. Paul Feller AGT Mainframe Technical Support ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN