6 2 4 Compile and Edit Settings

LANSA for i

previous page next page

6.2.4 Compile and Edit Settings

To display the Work with Compile and Edit Settings screen, select Administration from the Main System Menu (Advanced), choose Review system settings from the Administration Menu and then select Compile and Edit options from the Review of System Settings menu.

DC@P8118 Work with Compile and Edit Settings

Process and function compile defaults

Produce source listing . . . . . . . . . : N Y,N

Optimize RPG code . . . . . . . . . . : N Y,N

Ignore Decimal data errors in RPG . . : N Y,N

Enable debug in RPG . . . . . . . . . . : N Y,N

Compile process . . . . . . . . . . . . : N Y,N

Web Validate numerics . . . . . . . . : N Y,N

Always build for DBCS (IBM i RDML objects): N Y,N

Process, function and file compiles

Compile and export IBM i target release : *CURRENT

Compile using RPG/IV code . . . . . . . . : Y Y,N

ILE bind RPG/IV modules into program . . : Y Y,N

OTHER file I/O modules

Use *DATETIME conversion option . . . . . : Y Y,N

Use *VARCHAR conversion option . . . . . : Y Y,N

Fnn=Help Fnn=Exit Fnn=Cancel Fnn=Messages Fnn=Change

DC@P8118 Work with Compile and Edit Settings

I/O module compiles

I/O modules to have use adopted authority . . . . . . . : Y Y,N

Support Client, SuperServer or Server . . . . . . . . : Y Y,N

Support high speed record blocking in PF key order . : Y Y,N

Support high speed record blocking in RRN order . . : Y Y,N

Support LANSA/Server ODBC interface . . . . . . . . : N Y,N

Allow extended files to be added to HST . . . . . . . . : N Y,N

Use long (256 character) user stamping (USRC, USRU, USRX) : N Y,N

Suppress FATAL Crude Element Complexity Rating in function : N Y,N

Editor options

Default RDML editor . . . . . . . . . . . . . . . . . . : L E,U,L

Enable alternate editor user exits . . . . . . . . . . : N Y,N

Fnn=Help Fnn=Exit Fnn=Cancel Fnn=Messages Fnn=Change

The Work with Compile and Edit Settings are shown on two screens. The page up and down keys may be used to move from one screen to the other. Changes are not committed until you press Enter on second screen.

Setting	DC@A01	DC@A07	DC@OSVEROP
Source listing	146
Optimize code	147
Decimal error	148
Debug	400
Compile process	461
Web numerics			*WEBNUMVAL
Always build for DBCS			*DBCS_BUILD
Release level		631-638
RPGIV			*RPGIV
ILE			*ILE
*DATETIME			*OTHER_DATETIME
*VARCHAR			*OTHER_VARCHAR
Adopt authority			IOMNOADOPT Note – screen question is reverse of flag. So answer of Y does not set IOMNOADPOPT. Answer of N sets *IOMNOADOPT.
Support client, etc			*IOMXSERVER
Blocking in PF key order			*IOMBLOCKBYKEY
Blocking in RRN order			*IOMBLOCKBYRRN
Support ODBC			*ODBC
Allow HST			*HSTABEXTEND
Use long user stamping fields			*LONG_USER_AUDIT
Suppress Crude warning			*CRUDEWARNONLY
Default editor	393
Editor user exit	401

Produce source listing default

Position 146 in data area DC@A01.

Specifies the default value for producing a source listing from a compile. This option may be overridden for individual compiles.

Optimize RPG code

Position 147 in data area DC@A01.

Specifies the default value for compiling the RPG program that results from the function compile. This option may be overridden for individual compiles.

Ignore decimal data errors in RPG

Position 148 in data area DC@A01.

Specifies the default value for how decimal data errors should be dealt with in the compiled RPG program that results from the function compile. This option may be overridden for individual compiles.

Enable debug in RPG

Position 400 in data area DC@A01.

Specifies the default value for the function compile. It specifies whether the function should be able to be used in DEBUG mode. Refer to Compiling a Process for detailed information. This option may be overridden for individual compiles.

Compile process

Position 461 in data area DC@A01.

Specifies the default value for the 'Compile the process as well as the functions' option on the function compile. It specifies whether the process should be turned into compiled form, as well as the function. Refer to Compiling a Process for detailed information. This option may be overridden for individual compiles.

Web validate numerics

Equivalent setting is *WEBNUMVAL in data area DC@OSVEROP.

Specifies the default value for the Validate numerics option on the function compile in web enabled processes. It specifies if input numeric fields should be validated via JavaScript according to the allowable number of digits before and after the decimal point. This option may be overridden for individual compiles.

Always build for DBCS

Equivalent setting is *DBCS_BUILD in data area DC@OSVEROP

Specifies to always build IBM i RDML objects (DDS files and programs) for DBCS, irrespective of the current build language. This value does not impact the build of RDMLX objects on IBM i or the build of Windows objects.
When *DBCS_BUILD is not specified, RDML IBM i objects will be built according to the current build language type.
When *DBCS_BUILD is specified, all RDML IBM i objects will be built as though the current build language is a DBCS language. For example, all DBCS keyboard shift attributes of J, E or O for fields will be generated into the DDS.

Default is N.

Target Release

Positions 631-638 in data area DC@A07.

Specifies the TGTRLS value that IBM i compiles and saves in export are to use. The TGTRLS parameter is appended to LANSA compile and export requests.

Valid values include:

*CURRENT

*PRV

VxRyMz where VxRyMz is a valid IBM i version.

*N which means that the default for the command is used. New LANSA systems are shipped with this value.

If left blank, the target release used is *CURRENT, not the default for the command.

Compile using RPG/IV code

Setting *RPGIV in data area DC@OSVEROP.

Specifies that each program is to be compiled using RPG/IV code, then bound as a single module ILE type program.

Before you attempt to use any of the RPGIV and ILE related switches it is strongly recommended that you first read ILE Implementation.

ILE bind RPG/IV modules into program

Setting *ILE in data area DC@OSVEROP.

Activates the second level of ILE implementation. The compile will statically bind any GUI and multilingual program into the function program and use supplied service programs to dynamically call (CALLB) LANSA internal programs. *** Must be used in conjunction with *RPGIV ***

Before you attempt to use any of the RPGIV and ILE related switches it is strongly recommended that you first read ILE Implementation.

Use *DATETIME conversion option in OTHER file I/O modules

Setting *OTHER_DATETIME in data area DC@OSVEROP.

Indicates that the conversion option *DATETIME is to be used when OTHER file I/O modules are compiled. This allows date (L), time (T) and timestamp (Z) fields to be accessible in LANSA.

Use *VARCHAR conversion option in OTHER file I/O modules

Setting *OTHER_VARCHAR in data area DC@OSVEROP.

Indicates that the conversion option *VARCHAR is to be used when OTHER file I/O modules are compiled. This allows variable length (VARLEN or varchar) fields to be accessible in LANSA in an RDML partition.

Note that this setting does not allow variable length character fields to be used as keys within LANSA. If the physical file or any logical views made known to LANSA have a varchar field as a key, the I/O module will fail to compile.

I/O modules to have use adopted authority

Setting *IOMNOADOPT in data area DC@OSVEROP. An answer of N will set the *IOMNOADOPT in DC@OSVEROP.

When *IOMNOADOPT is set, I/O modules created by LANSA will have USEADPAUT(*NO) i.e. do not use program adopted authority for I/O modules.

Support Client, SuperServer or Server in I/O modules

Setting *IOMXSERVER in data area DC@OSVEROP.

Set this option to "Y" to indicate that I/O modules should be compiled to allow support of:

LANSA Client applications.

and/or

LANSA Open applications using blocked I/O methods or the "receive immediate" option

and/or

Visual LANSA SuperServer applications.

It is recommended that you set this option to "Y".

Setting *IOMXSERVER, *IOMBLOCKBYKEY, *IOMBLOCKBYRRN and *ODBC to Y increases the number of files declared in an I/O module, the amount of static (literal initialized) storage used by an I/O module and the number of subroutines in an I/O module.

Support high speed record blocking in PF order

Setting *IOMBLOCKBYKEY in data area DC@OSVEROP.

Set this option to "Y" to indicate that I/O modules should be compiled to support high speed record blocking in physical file key order. You must set this option when using:

LANSA Client

the LANSA Open *BLOCKBYRRNnnnn selection option, or the "receive immediate" option.

The "Support Client, SuperServer or Server" option (*IOMXSERVER) must also be set to "Y" if you set this option.

It is recommended that you set this option to "Y".

Support high speed record blocking in RRN order

Setting *IOMBLOCKBYRRN in data area DC@OSVEROP.

Set this option to "Y" to indicate that I/O modules should be compiled to support high speed record blocking in relative record number order. You must set this option when using:

LANSA Client

the LANSA Open *BLOCKBYRRNnnnn selection option or the "receive immediate" option.

The "Support Client, SuperServer or Server" option (*IOMXSERVER) must also be set to "Y" if you set this option.

It is recommended that you set this option to "Y".

Support LANSA Open ODBC interface

Setting *ODBC in data area DC@OSVEROP.

Set this option to "Y" to indicate that I/O modules should be compiled to allow support of the LANSA Open ODBC Interface. The "Support Client, SuperServer or Server" option (*IOMXSERVER) must also be set to "Y" if you set this option.

Allow extended files to be added to HST

Setting *HSTABEXTEND in data area DC@OSVEROP.

Setting this option to "Y" allows database files with record lengths up to 1988 bytes to be added to a user index for high speed lookup.

Warning: Review to Database File Attributes before using this option.

Warning: It is strongly recommended that if this option is changed, then all files tagged as high speed tables, all read-only functions that use these files and all other I/O modules and Dboptimized functions that use high speed tables for lookup validation rules be recompiled AFTER deleting the current user index. The user index is DC@TBLIDX if changing setting to "Y" (adding *HSTABEXTEND) or DC@TBLIDY if changing setting to "N" (removing *HSTABEXTEND).

Use long (256 character) user stamping (USRC, USRU, USRX)

Setting *LONG_AUDIT_USER in data area DC@OSVEROP.

Setting this option to "Y" allows for user stamping fields to be supplied with a user name of up to 256 characters. Refer to detailed information in Output Attributes before using this feature.

Suppress FATAL Crude Element Complexity Rating in function

Setting *CRUDEWARNONLY in data area DC@OSVEROP.

Setting this option to "Y" indicates that a function that would cause the "Crude Element Complexity Rating" to return a FATAL will cause a WARNING only.

Warning: It is not recommended to use this setting as the function may subsequently fail to compile.

Default RDML editor

Position 393 in data area DC@A01.

Possible values:

"L" - edit by standard LANSA editor

"E"- edit by IBM's SEU or EDTSRC editors.

"U"- edit by alternate user exit editor.

Enable alternate editor user exits

Position 401 in data area DC@A01.

Setting this option to "Y" will enable alternate editor user exits when editing help text and/or RDML commands. Refer to detailed information on User Exit Programs before using this feature.

previous page start next page