October 2007 Newsletter
IOFTech Maintenance Release8G Newsletters Doc FAQ Contact Home |
Managing the IOF EnvironmentTopics
|
IntroductionAn IOF user’s session can be affected by a number of environmental factors, including:
The information below describes IOF tools that help you display and manage these environmental factors.
Displaying the Current IOF EnvironmentThe IOF DVAR command displays the IOF environmental variables. Many environment variables are defined by IOF options settings. Others, such as a user's userid or logon procedure name, are set by the TSO session logon. Still other variables are internal IOF settings that may be useful in diagnosing IOF problems. DVAR can be entered on any IOF panel. The Display Current Variable Values lets you select the type variable to be shown. Or you can press ENTER repeatedly to step through all the variable displays.
Selecting option 1, or just pressing ENTER displays the first variable screen.
When a variable is defined or is controlled in some way by the parameters in an IOF option member, that member name is listed in the Option column. In the display above, the IOF Group definition parameters are specified in the B23ALLOW option as shown. The IOF Expiration date password is defined in options data set member A50EXPIR. This information often shows you exactly where to make desired changes to IOF. Enter END then select option 4 to see system variables. An alternate way to do this is to just press ENTER 3 times from the previous variable display.
Many of the system variables are defined in the B49CMPAT option. The JES2 level is indirectly controlled in the C75ASMJS option member by defining the JES2 and z/OS macro libraries. Press ENTER multiple times to step through the remaining options. Many variables that control how IOF operates are displayed. The last screen is the user's profile variables. Alternately enter DVAR PROFILE to display just the profile variables. Profile variables will include the user's PFKey settings, default sort values and other personal settings for each user. Scroll up or down to see additional variables
Using the New SETIOF Command to Manage IOF OptionsWhile the DVAR command displays the IOF options in effect within the current IOF load modules, the actual options are stored in the IOF options library. This library is a PDS with each option, or set of related options, stored as a separate member. A generation process is required install changes to the options library into the IOF load modules Finding the correct option to change in the IOF OPTIONS PDS can be a difficult task for IOF installers. Familiarity with the OPTIONS library is required in order to find the member that defines a particular option. The new SETIOF command eases this task. SETIOF is included in release 8D of IOF. SETIOF was added to earlier release 8 versions of IOF by fix U8x2333. U8C2333 is applied to spin level 2007280. For prior spin levels of 8C, and for all levels of 8A and 8B, download the latest CUMFIX file and apply U8x2333 to add the SETIOF command. After applying U8x2333, SETIOF can be entered on any IOF panel to display the Setting IOF Options panel. This panel divides IOF options into three categories based on option change frequency and importance.
Selecting option 1 displays the most commonly changed options on the IOF Options Display.
The IOF Options Display shows one line for each options member. The change date column shows the last time the option was changed locally, or is blank if the option has never been changed locally. The description column gives a brief description of each option. The current value column gives a brief description of the current setting for each option where possible. Some options have multiple macros that can not be described accurately in a single column of information. For example, the B23ALLOW option description shows the number of IOF GROUP macros defined in that member. Additional current value information can be seen by scrolling right, or by running on a wide screen terminal. Note that if you do not see the "current value" column on this display, then you have the preliminary version of SETIOF installed. You should apply fix U8x2354 to replace the preliminary version. Edit or view a member to read the complete description of the parameters that can be defined in each member. Any changes you make will be reflected in the IOF Options Display when it is re-displayed. SETIOF can be run as a stand-alone command. This is the only method available to run SETIOF for IOF/CICS. The stand-alone command is useful for IOF/TSO to change options after the MPI has been run but before IOF is generated. To run stand-alone execute SETIOF from the IOF INSTALL data set from ISPF Option 6.
Determining the IOF VersionIt is not uncommon for a systems programmer to change IOF options, run the required IOF generation jobs, but see no change in the way IOF operates. The first thing to do in this case is to issue the VERSION command to prove that the latest generation is in fact being run. The current IOF version will be displayed in the top right corner. Press PF1(HELP) to see the long message which includes the date and time of the latest IOF generation. If the date is older than the latest generation date then you were not successful in putting the latest generation into production. Release 8B and later support the ALL parameter on the VERSION command. To display the version of IOF ans several IOF libraries, enter: VERSION ALL
Finding IOF Load ModulesIf the VERSION command shows that you are not running the latest IOF generation, the problem most likely is that you didn't properly copy the IOF load modules to a linklist library or to LPA. The IOFWHERE command shows which IOF load modules are running and where they reside. IOFWHERE is a Rexx exec that can be executed from TSO READY, from ISPF Option 6, or using the ISPF TSO command. IOFWHERE has no parameters. For example, from any ISPF panel enter:
IOFWHERE produces the following line mode messages.
Note that IOF and IOFSPF are the only two IOF load modules that will run from a STEPLIB. See the February 1999 IOF Newsletter for more information of where IOF modules must reside
Building Complex OptionsSeveral IOF options require multiple macros to be used. Some of these options require significant documentation. The B21ACESS member is documented in the special B21$DOC documentation member. B23$DOC documents the B23ALLOW member. Documentation for all other options is contained in the comments at the beginning of the member. Additional information can be found in Chapter 27 of the IOF Installation Guide. The B23ALLOW OPTIONS library member is the primary option member for controlling IOF access for sites that chose not to use the installation security system for access control. This option can participate even when SAF is used for most access control. ALLOW and LIMIT macros in B23ALLOW can be used to define exactly who can or can not access any IOF resource. These macros are documented in Chapter 27 of the IOF Installation Guide. The ALLOW command initiates the ALLOW dialog that helps build many common ALLOW and LIMIT macros. The December 1998 IOF Newsletter describes the ALLOW dialog is detail. However, the dialog is self documenting. Try it by entering ALLOW on the IOF Option Menu and follow the prompts.
Restoring Default OptionsThe IOF options data set includes duplicate copies of many of the options under an alternate name to make it easy to restore the default version. The duplicate member names begin with "Z". Member Z00INDEX lists the "Z" member names and the original option. Z00INDEX for release 8C is shown below.
|
|||||||||||
Email IOFTech@Triangle-Systems.Com
IOFTech Maintenance Release8G Newsletters Doc FAQ Contact Home