Eliminate Local IOF Modifications


January 2005
Newsletter

IOFTech    Maintenance   Release8D       Newsletters    Doc    FAQ    Q&A    Contacts    Home    Webmaster

 

Do you have local IOF mods?


Do you really know?
 

They may not be supported in future releases of IOF

Note:  The IOFAUDIT command is incorporated into release 8A to provide auditing function.  For release 8A and later, enter IOFAUDIT on the IOF Option Menu and follow the prompts to run the audit.

 


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 Program

The 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 MVS

The 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.

                            Allocate New Data Set
Command ===>                        
                                                                           
Data Set Name  . . . : userid.IOFAUDIT.MPI
                                              
Management class . . .                (Blank for default management class)
Storage class  . . . .                (Blank for default storage class)
 Volume serial . . . .                (Blank for system default volume) **
 Device type . . . . .                (Generic unit or device address) **  
Data class . . . . . .                (Blank for default data class)
 Space units . . . . . TRACK          (BLKS, TRKS, CYLS, KB, MB, BYTES
                                       or RECORDS)
 Average record unit                  (M, K, or U)
 Primary quantity  . . 5              (In above units)
 Secondary quantity    2              (In above units)
 Directory blocks  . . 0              (Zero for sequential data set) * 
 Record format . . . . FB                 
 Record length . . . . 80  
 Block size  . . . . . 0  
 Data set name type  :                (LIBRARY, HFS, PDS, or blank)  *   
                                      (YY/MM/DD, YYYY/MM/DD  
 Expiration date . . .                 YY.DDD, YYYY.DDD in Julian form 
Enter "/" to select option             DDDD for retention period in days  
   Allocate Multiple Volumes           or blank) 

 

Loading the Audit MPI Data Set

The 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 Set

If 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.

//GETMPI   JOB   acct,'Name',....           
//FTP EXEC PGM=FTP 
//INPUT DD * 
ftp.triangle-systems.com 
anonymous                                   
your.email.address 
cd download
binary 
get iofaudit.mpi  'userid.IOFAUDIT.MPI' (R    
quit 
/*				

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.

 READY                                                                    
ftp ftp.triangle-systems.com  
 IBM FTP CS V1R4                                            
 Connecting to: ftp.triangle-systems.com 64.82.105.182 port: 21.
 220 postumus.mspring.net FTP server (Version ms-vftpd 1.5.3 (1) Thu Apr 19 16: 
 39:26 EDT 2001) ready. 
 NAME (ftp.triangle-systems.com:USERID): 
anonymous  
 >>> USER anonymous
 331 Guest login ok, send your complete e-mail address as password.
 PASSWORD:     
 your email address 
 >>> PASS 
 230 User anonymous logged in. Access restrictions apply. 
 Command:
cd download 
 >>> CWD download 
 250 CWD command successful.
 Command:
binary  
 >>> TYPE I
 200 Type set to I.
 Command:    
get iofaudit.mpi 'userid.iofaudit.mpi' (R
 >>> PORT 192,168,94,18,4,224        
 200 PORT command successful. 
 >>> RETR iofaudit.mpi  
 150 Opening BINARY mode data connection for iofaudit.mpi (156640 bytes).
 226 Transfer complete. 
 156640 bytes transferred in 1.080 seconds.  Transfer rate 145.04 Kbytes/sec.
 Command: 
quit
 >>> QUIT 
 221-You have transferred 156640 bytes in 1 files.
 221-Total traffic for this session was 157206 bytes in 1 transfers. 
 221-Thank you for using the FTP service on postumus.mspring.net.
 221 Goodbye. 
 READY 

Downloading the Audit MPI File with your Web Browser

 Click here to download the Audit MPI file with your web browser.  Select the "SAVE" option when prompted.

Uploading the Audit MPI File to MVS

The 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 Audit

The audit can be run in less than five minutes.

To run the audit:

  1. Invoke IOF under ISPF
     
  2. From the IOF COMMAND line execute the MPI file by entering:
             TSO    ex    'userid.IOFAUDIT.MPI '
             (Specify the fully qualified MPI DSN you previously uploaded)
     
  3. Follow the prompts
     
  4. An audit report is generated in data set 'userid.IOFAUDIT.REPORT'
     
  5. Please FTP or email a copy of the report data set to IOF Technical Support.  Instructions for sending the report are shown in the audit dialog, and are also included in the report data set.
     
  6. You can delete the report data set after it has been successfully sent to IOF Technical Support if you wish.  You can optionally keep the report to document your IOF changes and options.

If You Need Help

Please 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.


Triangle Systems, Inc. PO Box 12752, Research Triangle Park, NC 27709
Email
IOFTech@Triangle-Systems.Com

[an error occurred while processing this directive]