Rational Developer for System z
Enterprise PL/I for z/OS, Version 3.8, Migration Guide

RULES(NOLAXLINK)

Specifying the option RULES(LAXLINK) causes the compiler to ignore the LINKAGE and other options specified in the declarations of two ENTRY variables or constants when you assign or compare them.

For example, if you use the RULES(LAXLINK) option, the following incorrect program, which would almost certainly cause an abend if executed, would not be flagged:

  dcl funtion ext entry returns( char(20) );
  dcl subrtn  entry variable;

  subrtn = function;

  call subrtn;

You should use the RULES(NOLAXLINK) option to catch these errors and to enforce basic coding standards.

However, it is probably not a good idea to use the RULES(NOLAXLINK) option in programs containing EXEC CICS statements because the CICS preprocessor generates these declares:

  DCL DFHEI0   ENTRY VARIABLE INIT(DFHEI01) AUTO;
  DCL DFHEI01  ENTRY OPTIONS(INTER ASSEMBLER);

Since the variable DFHEI0 is then used in the code that the CICS preprocessor generates for EXEC CICS statements, the compiler will flag under RULES(NOLAXLINK) that the entry DFHEI01 which is declared with OPTIONS(INTER ASSEMBLER), but assigned to DFHEI0 which is declared without any OPTIONS attribute.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)