The Natural library and program names (NAT-MOD-ID) are blank.

Document ID : KB000055659
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Missing NAT-MOD-ID is a symptom that the CA APAS ACBX Facility has not been installed properly in the Adabas link routines.

Solution:

  1. Determine if all the CA APAS ACBX data is missing or just the Natural information by signing on to Natural, logging in to Insight, and starting the APAS request ACBXVRFY. Display the ACBXVRFY report and check the USER-TYPE column:
    1.1  If the USER-TYPE column contains valid values but NAT-MOD-ID is blank, proceed to Step 3.

    1.2  If USER-TYPE and NAT-MOD-ID are both blank, proceed with the following step.
  2. If USER-TYPE and NAT-MOD-ID are both blank then the CA APAS ACBX Facility is not installed properly in one or more of the Adabas link routines.
    2.1  To determine which Adabas link routine is involved, start and display the CA APAS request ACBXMISS.

    2.2  The JOB NAME column contains the name of the job where the commands missing the CA APAS ACBX data are coming from - a batch job, CICS, or a TSO user, and which Adabas link routine to concentrate on.

    2.3   Are there any additional user exits such as TMON, Omegamon, or locally written UEXITA/UEXITB (Adabas V7) or UEXIT1/UEXIT2 (Adabas V8) routines being used in the Adabas link routine?
    2.3.1.  If not, proceed with Step 2.4.
    2.3.2.   If so, remove all the additional exits from DBGSTACx. Reassemble and link the Stack module verifying it assembled cleanly and double check where the load module/phase was linked to.
    2.4. Install the CA-APAS ACBX modules (without any additional user exits) with the Adabas link routine:
    2.4.1.  Verify that LNUINFO has been set appropriately for the Adabas link routine involved.
    See "Part 3: Install the CA APAS ACBX Facility" section in the Installation Manual.

    2.4.2.   Reassemble and link the Adabas link routine verifying it assembled cleanly, that the assembly
    contains the correct LNUINFO value, and double check where the load module/phase was linked
    to.

    2.4.3.   Reassemble and link the CA APAS DBGLNxxx module verifying it assembled cleanly and double
    check where the load module/phase was linked to.

    2.4.4.   In the LNKLNxxx job that links the CA-APAS modules with the ADABAS module, double check that
    the libraries specified in the INCLUDE statements or sublibs specified in the LIBDEF concatenation
    are pointing to the libraries / sublibs where the Adabas link routine and the CA APAS DBG load
    modules/phases were linked to in the above steps and remove the INCLUDEs for any additional exits
    such as TMON, Omegamon, or locally written exits.

    2.4.5.  Rerun the LNKLNxxx job to link the CA APAS modules with the Adabas module and verify the new ADABAS
    module is being linked to the current load library or sublib.

    2.4.6.   Check each of the libraries in the STEPLIB or sublibs in the LIBDEF concatenation of the job identified in ACBXMISS looking for an old version of the ADABAS module in a library or sublib before the library/sublib
    that the CA APAS ACBX version of the ADABAS module was linked to.
    2.4.6.1.  If another ADABAS module is found, rename or delete it.
    2.4.7.   Is this a CICS Adabas link routine?
    2.4.7.1.  If so, recycle CICS to pick up the new copy of the ADABAS module.

    2.4.8.  Retest.

    2.4.8.1.  If not resolved, retain all output from assemblies and link edit jobs and open a CA
    Support Online issue.

    2.4.8.2.   If resolved and no additional user exits are used, done.

    2.4.8.3.   If USER-TYPE and NAT-MOD-ID now contain valid data but need to implement additional
    user exits, proceed with Step 2.5.
    2.5.  Reinstall the additional link routine exits such as TMON, Omegamon, and locally written UEXITA and UEXITB routines.
    2.5.1.  Add the additional user exit entries to DBGSTACx. Make sure that ENTRY2 thru ENTRYn are between ENTRYLEN and ENTRYCNT.

    2.5.2.   Reassemble and link the CA APAS DBGSTACx module verifying it assembled cleanly and double check where the load module/phase was linked to.

    2.5.3.  Add up the values of all the User Information Data Areas - ENTRY1 thru ENTRYn. UIDALEN is 112-bytes. Is the sum evenly divisible by 8?
    2.5.3.1.   If not, it does not have double word alignment and the sum must be rounded up until it is evenly divisible by 8.
    2.5.4. Determine the largest Work Area used by any of the entries. Is it evenly divisible by 8?
    2.5.4.1.  If not, it does not have double word alignment and the largest Work Area must be rounded up until it is evenly divisible by 8.
    2.5.5.  Add up -
    1)  total of the User Information Data Areas (adjusted for double word alignment - Step 2.5.3.1),
    2)  the largest Work Area (adjusted for double word alignment - Step 2.5.4.1), and
    3)   120-bytes for the DBGDRIVx Work Area requirement.
    2.5.6.   Specify the sum computed in Step 2.5.5 as the value of LNUINFO in ADALNK (Adabas V7) or in the LNKGBLS macro (Adabas V8) for batch, or in ADAGSET (Adabas V7) or in the CICSGBLS macro (Adabas V8) for CICS.

    2.5.7.  Reassemble and link the Adabas link routine (Adabas V7) or the GBLS macro (Adabas V8) verifying it assembled cleanly and double check where the load module/phase was linked to.

    2.5.8.   In the LNKLNxxx job that links the CA APAS modules with the ADABAS module, double check that the libraries specified in the INCLUDE statements or sublibs specified in the LIBDEF concatenation are pointing to the libraries / sublibs where the Adabas link routine and the CA APAS DBG load modules/phases were linked to, and add the necessary INCLUDEs for the additional user exits.

    2.5.9.   Rerun the LNKLNxxx job to link the CA APAS modules with the Adabas module and verify the new ADABAS module is being linked to the current load library or sublib.

    2.5.10.  Is this a CICS Adabas link routine?
    2.5.10.1.   If so, recycle CICS to pick up the new copy of the ADABAS module.
    2.5.11.   Retest.
    2.5.11.1.   If not resolved, retain all output from assemblies and link edit jobs and open a CA Support Online issue.
  3. If there are valid values for USER-TYPE but NAT-MOD-ID is blank, that indicates the CA APAS ACBX Facility is installed       properly but there is a problem with the Natural extraction process of the DBGLNxxx module.
    3.1.  Is this a Natural 4.1 CICS Transaction Server environment?
    3.1.1.   If yes, have you applied the CA APAS V4.1 Natural 4.1 compatibility zap - Z41007 (APAR # QO50259)?
    3.1.1.1.   If zap not applied, apply it and retest.

    3.1.1.2.   If zap has been applied and still not resolved, open a CA Support Online issue.
    3.2.   Is this a Natural 4.2 environment?
    3.2.1.  If yes, have you applied the CA APAS V4.1 Natural 4.2 compatibility zap - Z41073 (APAR # QO79598)?
    3.2.1.1.  If zap not applied, apply it and retest.

    3.2.1.2.   If zap has been applied and still not resolved, open a CA Support Online issue.