Last updated 1/8/2002

This document provides tips on how to maximize the performance of the CV1 CIM system.

Maintain healthy CIM work files:

The CV1 CIM system uses three primary files to construct and disseminate CIM messages.  At times, these files can become laden with large amounts of data.  Global price changes, CIM Dispatch utilities, and even general CV1 system usage will often place great demands on the system- and these files bear the results of that demand.

Dispatches (CVFICPP) - This database file contains the actual constructed CIM messages that are delivered to CIM targets.  All CIM messages for all targets are contained in this file and are individually disseminated based on the target's profile.  The job called CIMRTEOUT performs this dissemination task.  This file can grow very large at times and is extremely Input/Output intensive.  As records are disseminated from this file, they are physically deleted.  For this reason, no purge exists for this database.  The only process that creates these records is CIMDSPCH.

Dispatch Requests (CVFHCPP) - This file contains request for the CIM system to construct CIM messages and dispatch them to the proper targets.  These CIM messages are stored in the file CVFICPP as described above.  The job called CIMDSPCH processes the requests.  As each record containing a "request" is processed, the status of the record is changed, but it is not physically deleted.  The End of Day process performs a purge of these "Dispatched" records.  This file exhibits a mCIMum data volume and input/output intensity.  

Nearly every critical data processing function in CV1 creates records in this file.  For example, CIMting an item will cause a record to be created.  Therefore, this file is open when a CV1 user is on nearly any screen or running nearly any process.  The file can grow large even while the CIM system is not active.

Data Manipulation #2 (CVFJCPP) - This is a high-level file used primarily to hold requests for large dispatches of data.  The job called CIMDMF processes the records in this file and creates records in CVFHCPP as described above.

    It's absolutely crucial that these three files be reorganized using the CL command  RGZPFM.  The End of Day process will attempt to perform this process.  If, however, a file is in use, it will not be reorganized.  If the CIM system is left active during End of Day, the file will be in use.  Therefore, be sure to stop the CIM system using the Interface Control Panel prior to running your End of Day process.  Also, if a user is in nearly any CV1 CIMt function, the file CVFHCPP will be open and End of Day will not reorganize it.  If End of Day occasionally misses the reorganization, no harm is done.  It is good practice, however, to ensure it's being done most of the time.

    Check to ensure that the files are actually being reorganized.  Do this using the command DSPFD.  Scroll down several pages until you find an entry called "Reorganize operations".  This number should increase by one after End of Day is complete.  If it's not increasing on a regular basis, you may need to manually issue the RGZPFM occasionally.

     Using DSPFD, check the status of the "Reuse deleted records" option (REUSEDLT).  PTF # 3229 changes this option to be *YES on all three files.  Reusing deleted records can save considerable storage space.  If the option is already set to *YES, then you already have the PTF installed. If not, please call CDR support and request it.


Isolate CIM tasks:

CIM jobs can be submitted to a custom job queue.  From the Interface Control Panel, press F8 to access this setting.  You can create a specialized sub-system and attach a custom jobq to it.  By submitting the CIM jobs to your own queue and by tuning the run-time attributes of the sub-system to which that queue is attached, you can control how system resources are allocated to these jobs.  

Please see the IBM documentation on Work Management for information on how to tune subsystems.  It's available on-line at http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/books/c4153063.pdf.


Review CIM Configuration:

Visit all CIM Profiles and Targets:

Review CIM Options.  Pay close attention to the Cust/Item Dispatch Scope.  This setting can have a drastic affect on the performance of the CIM system.  Adjust it according to the following: