Frequently
Asked
Questions

IOFTech    Maintenance   Release8G       Newsletters    Doc    FAQ    Contact    Home

Q. What is the current release of  IOF?

A. Release 8G was officially released on October 2, 2017 with support for z/OS V2R3.  Release 8G is the only release that supports z/OS versions V2R3 and higher.
 

The latest release of IOF is Release 8G. The latest spin level of  IOF Release 8G is 2023300 (October 27, 2023).

IOF  provides support for JES2 data set encryption and compaction.  To get this support you can download and install the latest IOF MPI file, or download the release 8G CUMFIX file and apply all of the fixes to your current IOF 8G system.

Q. What releases of z/OS are supported by IOF Release 8G?

A. Release 8G with current maintenance supports all releases of z/OS through z/OS V3R1.

Q. What releases of IOF are currently supported?

A. Release 8G is fully supported. It is the only release that will run on z/OS V2R3 and later. Release 8F is no longer under development and no additional maintenance should be expected. For customers running on a back-level release, we will do our best to assist with questions or problems, but please understand: we can no longer run those releases on the z/OS systems we have available.

Q. How do I determine the release of  IOF  I am running?

A. Enter "VERSION"  from any IOF panel. Your IOF version and level will be displayed, as well as  the version of the CLIST, HELP and ISPPLIB libraries being used.

Q. Can I run release 8G run in parallel with my current IOF release?

A. Yes. Two IOF 8G images can co-exist in the same system provided a different IOF Installation level is used. (For example, 8G0 and 8G1) Release 8G is shipped with the "IOF8G" REXX exec which can be used to invoke release a test level of 8G instead of the current production version of IOF. The "$$TODO" member of the INSTALL library describes how to use "IOF8G" for testing. 

The latest MPI also includes the RUNIOF command.  RUNIOF parm is the version of IOF you want to run.  ie RUNIOF 8G3.

Q. Does IOF support the EVENTLOG data set introduced by JES2 V2R2?

A. The most important information in EVENTLOG is the completion code of each job step.  The IOF Job Summary Panel has always displayed this information, so EVENTLOG is of little use to IOF users.  But the IOF INTTEXT command will cause the EVENTLOG data set to be included on the Job Summary where it can be browsed.  Just enter INTTEXT primary command on the IOF Job Summary.

Q. When I install a new version of IOF, do I need to install a new SVC (or ESR)?

A. Probably not. The IOF SVC and optional ESR have not changed since Release 7D.  But a few customers have been running with the older version of the IOF SVC.  IOF now checks to be sure the newer version of the SVC/ESR is installed.

Q. What is an IOF spin level?

A. IOF is distributed as a single MPI file. Periodically, the MPI file is updated to apply maintenance. The new MPI version is called a spin level. Spin levels of an IOF release are the base level with maintenance applied. The fixes web page for each release shows which spin level, if any, has each fix pre-applied. The "name" of the spin level is the julian date it was built.

If you apply all maintenance in the CUMFIX file you will bring your IOF up to at least the latest spin level.  The spin level number will not be updated however.

Q. Do I need a new license patch when I convert to a new release of  IOF?

A. No. All  releases of IOF from 7D through 8G use the same license patch. When using Option 2 of the MPI dialog, the installation process automatically copies your old license patch from the old options data set to the new options data set. 

Q. Do I need a special license patch to run IOF at a disaster recovery site?

A. Probably not. As long as the date portion of your normal expiration patch is valid, IOF will run with a "license" error message until the third midnight after IPL. This provides at least 48 hours of disaster testing per IPL. If your disaster test will be longer than 48 hours per IPL, call technical support for a temporary patch.

Q. How do I determine when my IOF expiration patch will expire?

A. Enter "DVAR EXPRDATE" from any IOF panel to display the date the current patch in use will expire.  The VERSION command also displays this value.

IOF 8G provides a utility function that can be run in batch TSO to provide a warning when IOF is near expiration.  Refer to member M45DATCK in the INSTALL library for a sample job that can be submitted daily to warn when IOF is approaching expiration.  The job can be edited to change the warning threshold, and to specify userids to be notified of any exception conditions encountered.

Q. I applied my new expiration patch, but IOF still is "expired" What is the problem?

A. There are several possible problems. The most likely problem is that you applied the patch to the wrong linklist library. IOF provides the IOFWHERE Rexx exec to help you find the module that should be patched. From ISPF Option 6, or from TSO READY, enter "IOFWHERE". The library names in which each of the IOF load modules reside will be displayed. You have to apply the license patch to the "U" module in the library displayed.

Occasionally VLF or some other product that provides similar function prevents the updated load module from being loaded. Usually this can be corrected by issuing the MODIFY LLA,REFRESH command.

See the Virtual Help Desk for additional information.

Q.  Not all locations use Daylight Savings Time. How does IOF adjust for this? .

A.  IOF formats and prints dates from JES2 control blocks, but has no code that is aware of the change to or from DST.  IOF is not affected by a locale's use of Daylight Savings Time.