Problem with Full Function Checks and compiles

Date:Archived
Product/Release:LANSA for the AS/400 - All Releases
Abstract:Full Function Checks (FFCs) and compiles are failing with error CPF4102, DC@F33 in DC@DTALIB member NOT_AVAIL not found
Submitted By:LANSA Technical Support

This problem can occur for a number of different reasons :

  • The maximum number of simultaneous full function checks and / or LANSA compiles has been exceeded. These maximum numbers are set when submitting the LANSA reorganization job.

    If this is the case, submit a LANSA reorganization job, specifying "Change Work Spaces" as "YES" and setting larger numbers than previously for Total FFC and Total Compiles. See below for guidelines.
     
  • The maximum number of simultaneous full function checks and / or LANSA compiles has been set to inappropriate values. These values would have been set when submitting the last LANSA reorganization job.

    If this is the case, submit a LANSA reorganization job, specifying "Change Work Spaces" as "YES" and set realistic values for Total FFC and Total Compiles. See below for guidelines.
     
  • A number of "C" compiles have been submitted from the full function checker. They are still in a job queue and 'reserve' work members for when they go active.

    If this is the case, after the "C" compiles have completed, other compiles will go through. If it is typical that many "C" compiles will be waiting on the job queue at any time, then submit a LANSA reorganization job, specifying "Change Work Spaces" as "YES" and setting larger numbers than previously for Total FFC and Total Compiles. See below for guidelines.
     
  • A number of "C" compiles have been submitted from the full function checker. They have been deleted from the job queue before going active but still 'reserve' work members.

    If this is the case, wait until there is no FFC or LANSA compile activity. This includes interactive FFCs, "C" compiles on the job queue and compile jobs being active (both "C" and non-"C"). Clear the data area called COM_CONTRL in the LANSA program library. This is usually, but not always, called DC@PGMLIB. For example:

    CHGDTAARA DTAARA(DC@PGMLIB/COM_CONTRL) VALUE(' ')

    This may have to be done regularly if "C" compiles are often canceled from the job queue. Because this occurs outside the LANSA environment, LANSA knows nothing about it.

Guidelines for Number of Compiles & Number of FFC.

Presuming no dual session terminals, use the following as a guide :

Number of CompilesThe maximum compiles that will ever be run simultaneously plus the maximum number of "C" compile jobs that will be on the job queue at any time.
Number of FFCNumber of Compiles plus 2 x the number of terminals that will be used,(ie the number of possible interactive simultaneous FFCs).