

I then had enough space to be able to grow the zfs.
#Openzfs filesystem pdf pdf#
DFSMS return code = 104, PDF code = 204.ĭFSMS return code = 104, PDF code = 204 means no space on the volume.
#Openzfs filesystem pdf how to#
IEF196I IEC070I 104-204,OMVS,OMVS,SYS00022,0A9E,C4USS2,ZFS.USERS, This section is a step-by-step guide that shows how to perform certain ZFS file system tasks inside of Solaris containers for example, taking snapshots and. IOEZ00323I Attempting to extend ZFS.USERS to 36000 4096 byte control intervals. IOEZ00308E Aggregate ZFS.USERS failed dynamic grow, (by user COLIN). To make it bigger, but I got the Unix Services message So we can see the data set is ZFS.USERS and it is 100% full.ĭoesnt quite give enough info.

This gave me Filesystem 512-blocks Used Available Capacity Mounted on
#Openzfs filesystem pdf full#
Tells you the file system – and how full it is. Later I found the ZFS.USERS data set had 123 extents – and could not be expanded. Having made the ZFS.USERS larger, I then found IEC070I 104-204 is data set is > 4GB. To solve this file system full problem, I had to explore other areas of z/OS which I was not so familiar with – ADRDSSU to move data sets, zfsadmin commands, and how to stop SMS from being too helpful. As the file system filled up – it could not write the “file system full” message. I piped the output of a shell script to a file. The file system I was using in Unix Services filled up – but it didn’t tell me,I just had a truncated file.
