IBM Support

Loading a DXL script within another DXL script results in error "non local variable access"

Troubleshooting


Problem

In IBM Rational DOORS, loading a DXL script from within another DXL results in an error "non local variable access".

Symptom

The full error message is as follows:

-E- DXL: <example/include/linkops.inc:66> non local variable access (linkErrorNonObjectData) too many messages -- suspending error reporting-I- DXL: all done with 52 errors and 0 warnings

Cause

This can occur when variables being declared in one function are used in another function; however, the problem has more to do with where the variable was assigned rather than where it was declared.

Environment

A DXL script runs without error; however, when it is called from another DXL script it fails to load.

Resolving The Problem

The solution is to define the variables globally.

To declare a global variable:

  • declare them in startup files
  • declare them at the very start of the "parent" script
  • declare them using evalTop_

[{"Product":{"code":"SSKR2T","label":"IBM Engineering Requirements Management DOORS"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"General Information","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.3;9.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
01 May 2020

UID

swg21406887

Page Feedback