Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

9.21 COMPILE_COMPONENT

Note
titleNote:
Built-In Function Rules     Usage Options

This BIF compiles a component.

This is a Specialized Built-In Function for use in a Development Environment only.

Arguments

No.

Type

Req/

Opt

Description

Min Len

Max Len

Min Dec

Max Dec

1

L

Req

Working List Name. The working list must have an aggregate length of 9 bytes.

Each list entry should be formatted as follows:

Bytes 1-9: A(9), Component Name

1

9



2

A

Opt

Force Compile (YES/NO).
When this option is NO, only those components that need to be are compiled, otherwise all the components are compiled.

Default: NO

2

3



3

A

Opt

Keep the generated source code (YES/NO).

Default: NO

2

3



4

A

Opt

Compile for debug (YES/NO).

Default: NO

2

3



5

A

Opt

Web services to compile (A/W/N)

A - All Web Routines
W - New Web Routines only
N - None.

Default: N

1

1



6

L

Opt

Working List Name. The working list must have an aggregate length of 21 bytes.

Each list entry should be formatted as follows:

Technology Services identifier. A(21). This should be specified in the following format <Provider>:<Technology Service Name>.
For example, LANSA:XHTML

1

21



Return Values

No.

Type

Req/

Opt

Description

Min Len

Max Len

Min Dec

Max Dec

1

A

Req

Return code.
The component may fail if it doesn't pass the build process or is locked.

OK = successful submission of compile.

NR = No compilable components found in list.

ER = argument details are invalid or an authority problem has occurred. In this case, return code error message(s) are issued automatically.

2

2



Example

A user wants to control the compilation of components using their own version of the "Compile / Re-Compile a Component" facility.

*********  Define arguments and lists

...