Micro Focus Enterprise Test Server 2.3 Update 1 > Data Access > Database Access > Data Manager > z/OS Toolkit Guide > Load IMPSRC for Life Cycle

Load IMPSRC for Life Cycle

The Life Cycle is a feature that enables automatic updates for file layout information. The Life Cycle process can use a guide file, which is a sequential file with a name that is similar to the project and group specification and followed by the IMPSRC file. It can be completed by the user (using an interface from Endevor, Changeman, or any other change management tool) or directly with the job Load Sequential for Life Cycle.

The job Load Sequential for Life Cycle writes the IMPSRC file (starting from a PDS with the copy loaded in the knowledge base or from a DB2 owner (schema)) with all the copy or the new or changed DB2 tables. After a new job is created and scheduled, the IMPSRC file is used when the job executes to schedule the Life Cycle phases.

Note: The Life Cycle process uses only one IMPSRC file. Therefore, we recommend that the process be executed for every DB2 owner (database schema) or for every partitioned data set.

For more information about the Life Cycle, see the chapter Life Cycle in the Process Guide for z/OS.

To load the IMPSRC file for the Life Cycle:

From the Main Menu panel, enter the following command: TSO CUINLIC.
Insert parameter names into all fields as required:
Data Set Type

Mode with which you want to work.

Note: Like the Analyze FDT report, the Life Cycle for ADABAS lets you analyze an FDT report, but with the difference that you can analyze multiple FDT Reports simultaneously.

Data Set Name

Name of the partitioned data set or DB2 Owner (schema name) with which you want to work.

Note: If you are using Life Cycle for ADABAS, the data set name must be the name of the PDS file that contains the desired FDT Report as a member.

Select Count
Type of select to get the total number of records:
1. select count on DB2 table (slowest).
2. select on SYSIBM.SYSTBALES (fastest).
3. select on SYSIBM.SYSTBALES and if there are no statistics, a select count on the DB2 table is performed.