IntroductionRelease 7J of the Interactive Output Facility (IOF) program product provides support for all releases of OS/390 and for z/OS releases 1.1 through 1.8. The new IOF release is downloadable from this web page as a single MPI (mainframe product install) file. Release 7J runs in parallel with previous versions of IOF. It uses the same SVC or ESR as previous versions of IOF.Several additional enhancements are included in 7J to make IOF easier to install, maintain and use. This newsletter summarizes the major enhancements provided by the new IOF release.
Sort Assist Panel for the Job List Menu
The performance of the SORT command has been significantly enhanced. This will be most noticeable when sorting extremely long lists of jobs or output groups HELP on many panels displays the active sort for that panel.
HELP on the Job List Menu
(New fields in red)
Example of Alternate View 1
(DESTDEV moved to second screen, replaced by DATE and TIME)
New Profile Options for Snap Target Data SetsOption "P" (profile) on the IOF Option Menu has been reorganized. The primary reason for this reorganization was to provide full defaulting specifications for all SNAP sysout target data set attributes.
New IOF Profile Menu
Profile option "2" provides a selection of six additional menu items which allows default values to be defined for all possible snap sysout attributes. For example, select option "2" to define default UCS or FCB attributes for all snap to sysout commands. Default values specified on the panel are saved in the user's profile, and can be over-ridden on the SS panel.
Default Snap to Sysout Attributes Menu
Progress Messages for Long Snap and Find CommandsThe FIND and SNAP commands may run for an extended time when large amounts of data are being searched or copied. A progress message is now displayed while long SNAP and FIND commands are executing. A progress message is also displayed for the DF (display forms) command on the Output Group Display when a large number of output groups is being processed.
Example of Find Command Progress Message Improved MVS/JES2 Command Interface PanelThe new MVS command displays a panel where long MVS and JES2 commands can be entered. A maximum input length of 120 characters is supported. The "#" (pound sign) character with no parms also displays this panel at most sites. This panel saves the latest MVS and JES2 commands entered so they can be selected and resubmitted, much like ISPF option 6. It also allows you to specify where you would like to view command responses (console or syslog).
MVS and JES2 Commands Interface Panel Note that when the full 120 character command can
not be displayed in the list of old commands at the bottom of the screen,
the displayed command ends with "..." to indicate that there are more command
characters. The full 120 characters are
retrieved when the command is selected. Old commands can be edited
and deleted from the menu of old saved commands.
The TS command displays the TSO command interface
panel where long TSO commands can be entered. In release 7J,
the latest commands issued are saved much like ISPF Option 6. A maximum
of 32 commands will be saved for each user.
MVS and JES2 Commands Interface Panel
Note that when the original command is too long to be displayed in the list
of old commands at the bottom of the screen, the displayed command
ends with "..." to indicate that there are more command characters.
The original command is retrieved when the command is selected however.
Unlike ISPF option 6, old commands can be edited and deleted from the
menu of old saved commands.
Rexx Error Processing EnhancementPrior to release 7J, the "on error" routine of a Rexx exec running under IOF would not be invoked when an IOF function completed with a non-zero return code. This has been corrected for release 7J. A side effect of this enhancement is that non-zero return codes from IOF functions will now produce Rexx line-mode error messages unless the exec contains a "TRACE OFF" instruction. All distributed IOF execs have been modified to include a "TRACE OFF" instruction. If you have written local execs that run under IOF then you may wish to prevent these line-mode error messages by inserting the following statement in those execs.
Rexx execs running under IOF 7J can trap the line number, IOF error message number, and Rexx statement causing an error. For example, establish an IOF Rexx error routine that lists the error number, long IOF error message, and statement that caused the error by including the statement below at the beginning of the Rexx exec:
Password Analysis ProcedureThe IOF expiration password date can be displayed by entering the command below on any IOF panel. The end date of the current paid IOF license is displayed.
IOF continues to run for an additional eight days after the official expired date in "warning" mode. A message is displayed in the long error message area on the third line of the screen
Several customers have requested an automated way to be warned that the IOF license will soon expire. Release 7J provides a utility that can be run in batch to check the IOF expiration password and give meaningful messages and return codes for several conditions. A new job, M45DATCK, is generated in the IOF INSTALL library to invoke this new utility. M45DATCK has two parms that the user may wish to modify:
You may want to run this new utility daily, and have production control check the return codes and messages in the SYSTSPRT data set. You can modify the job to change the warning threshold, and to notify one or more users when the job gets a non-zero return code. Return values are:
To snap all data set fields, show input data sets, and add a parse template to a Job Summary snap, enter:
%IOFSNPJS FULL TEMPLATE INPUTJCL The panel snap execs can be invoked from a higher level exec with the Rexx CALL statement. For example, to snap the Job Summary with a parse template from a Rexx exec that is positioned to the panel:
CALL IOFSNPJS TEMPLATE The panel snap execs can be easily modified to change the specific fields that are snapped. Each exec contains a list of $COL and $OPT statements that define the specific fields to be snapped. $COL statements are always snapped. $OPT statements are snapped only if the FULL parm is specified. Remove unwanted $COL or $OPT statements, and save the modified exec under a different name to produce a tailored format.
All applicable IOF release 7H maintenance has been applied to
release 7J. IOF 7J supports all releases of OS/390 and z/OS 1.1
through 1.5.
HELP for the Job List Menu and Output Group Display now displays
filters in effect and the currently specified SORT.
IOFTech Maintenance Release8G Newsletters Doc FAQ Contact Home
|