Eliminate Local IOF Modifications
Why this is important to you.Your usage of IOF may depend on local modifications made by your staff to distributed IOF components. Some of those components may become obsolete due to significant architectural changes that have become necessary for us to maintain IOF and deliver new function in a reasonable time frame. So it is imperative that you identify and eliminate IOF modifications now What if you really need these modifications?Over time IOF has provided an extensive set of installation options to provide the same functionality as the modifications that many customers have made to IOF. In virtually every case there are options available that can be used to replace your local IOF modifications. What if you don’t have time to worry about this right now?We have developed a simple audit tool to identify your IOF local mods. Downloading and running this tool takes only a few minutes. Once the audit results have been returned to us, we will be able to recommend ways to accomplish the same objectives without source modifications. The audit can be run in less than 5 minutes and produces a simple audit report to be returned to us by email or FTP. It is important that you download and run the audit as soon as possible!
Download and Run the Audit ProgramThe audit program is packaged as a single MPI file that can be downloaded here. Follow the simple steps below to load the audit MPI to your MVS system, run the audit, and return the report to IOF Technical Support. Allocating the Audit MPI Data Set on MVSThe audit MPI data set should be pre-allocated on the MVS system in order to insure the proper data set characteristics. The data set name should be 'prefix.IOFAUDIT.MPI'. The prefix can be the user's userid This prefix will be used to allocate the temporary files required by the audit procedure. Use ISPF option 3.2 to allocate the audit MPI data set as shown below.
Loading the Audit MPI Data SetThe IOF Audit MPI file can be downloaded with a web browser to your PC, or can be copied via FTP directly to MVS, or to your PC. Using FTP to load the MPI Data SetIf FTP is available on your MVS system, the MPI file can be copied directly from this web site to the audit MPI file you just allocated in the step above. Either batch FTP, or the TSO FTP command can be used. If you can run batch FTP on your system, the JCL shown below will copy the MPI to an MVS data set. Edit the JOB statement, the email address (used as the anonymous FTP password), and the "get" FTP statement and submit the job. The fields that require editing are colored red. NOTE: Be sure to specify the NONUM or UNNUM editor command. Sequence numbers in columns 73 through 80 confuse the FTP program and cause errors.
The TSO FTP command can be run from TSO READY or from ISPF option 6 to retrieve the audit MPI file. A sample FTP session is shown below, with the input commands shown in red. The same commands can be used from a PC or unix FTP session to get the MPI file.
Downloading the Audit MPI File with your Web BrowserClick here to download the Audit MPI file with your web browser. Select the "SAVE" option when prompted. Uploading the Audit MPI File to MVSThe MPI file must be uploaded to MVS if it was downloaded to your PC by the web browser, or by FTP. Upload to the pre-allocated MVS audit MPI file in BINARY mode. If you used FTP to get the file directly to MVS, this step is not required. Running the AuditThe audit can be run in less than five minutes. To run the audit:
If You Need HelpPlease contact IOF Technical Support if you have any questions or problems getting the IOF audit MPI file, running the procedure, or sending us the report data set. The information contained in the report data set is essential to IOF development to allow us to make improvements to the product with minimal impact on our installed product base. Email IOFTech@Triangle-Systems.Com
|