Description: Before z/OS V2R1, the batch utility ioeagfmt did not require that the zFS kernel be active. Starting in V2R1, ioeagfmt requires that the zFS kernel be active.
| Element or feature: | z/OS Distributed File Services. |
| When change was introduced: | z/OS V2R1. |
| Applies to migration from: | z/OS V1R13 and z/OS V1R12. |
| Timing: | Before the first IPL of z/OS V2R1. |
| Is the migration action required? | Yes, if you did not run ioeagfmt after the kernel was initialized. However, it would be unusual not to have zFS active when running ioeagfmt. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | None. |
| Related IBM Health Checker for z/OS check: | None. |
Steps to take: Look for JCL or vendor applications that might be creating or submitting JCL that contain ioeagfmt calls that are run when the zFS kernel is not active. Run them when the zFS kernel is active. If you are formatting file systems to be used by another system, you should be setting the -version parameter on ioeagfmt because the local zFS kernel would not have the information for a remote zFS system. You can also use the IOEFSUTL program to format aggregates. IOEFSUTL does not require the zFS kernel to be active to format a file system if you specify the -version parameter. But it will require the zFS kernel to be active if the -version parameter is left out.
Reference information: z/OS Distributed File Service zFS Administration