Previous Topic: Other Members That Can Be DeletedNext Topic: Library Integrity Utility


Correcting Inefficient Block Size

The most efficient block size for a VLS library depends on the size of the members contained in the library. Therefore, it is a decision that you must make for each site and for each library.

Most often a site exceeds the space of a source library. Every VLS member in a user source library consists of at least two blocks, regardless of the actual size of the member. Unless almost every member is over three blocks, increasing the block size does not solve the problem on anything but a temporary basis, and increases the use of DASD and DSA.

Creating New Libraries for Existing Systems

If the VLS library contains more than one CA Ideal system, you can create another set of VLS libraries and separate the systems across the two sets of VLS libraries.

To migrate your systems with the least impact on your programmers

  1. Back up the existing source, panel, and object libraries.
  2. Create the new set of VLS libraries to contain source, panel, and object code.
  3. Decide which systems should be moved to the new set of libraries.
  4. Move all members associated with the selected systems into the new libraries and delete them from the existing library. You can use the VLSUTIL SELREST and DELETE cards to do this.
  5. Update the CA Ideal system definitions to point to the new libraries.
  6. Update the CICS JCL, the batch JCL, the FCT, and IDSYSFT to reflect the new libraries.
  7. Recycle CICS.

This method has no impact on the existing programs. You do not need to edit or recompile anything. The programmers are unaware of the change.

Splitting One System into Separate Systems

If a VLS library only has one system and that system is full, you can split the system into separate systems. Before you do this you should:

If either of the above suggestions does not provide a solution, create new CA Ideal systems. After the new systems are created, you can move programs as necessary.

To create new systems and migrate the programs into the systems

  1. Determine which programs belong together as part of an application. You can identify programs that belong to one application, and common programs that are called by many applications, by generating a report with the command
    DISPLAY INDEX PROGRAM RELATED TO PROGRAM
    

    You can also generate a path report from the dictionary.

  2. When you determine which applications you have, you can create the CA Ideal system definitions and the VLS libraries associated with those new systems. Be sure to add the new VLS libraries to the CICS JCL, batch JCL, FCT and IDSYSFT.
  3. Use the Source Transport Utility to export the programs, reports, and panels from the existing system and import them into the new CA Ideal systems. Use the SET IMPORT NEW SYSTEM source transport command to change the system for the imported entities.
  4. The entities are imported in test status and you must recompile the programs. You must mark production entities to production status.

    Note: The creation and compilation dates are changed to the date of import and recompilation.

  5. In the original system, use the CA Ideal DELETE command to delete the programs, reports, and panels that were moved to the new system.