IBM AS/400 manual Calling Special Routines, Multithreading Considerations

Multithreading Considerations

¹ The name of the graphics routine you want to run.

¹The appropriate parameters for the specified graphics routine. T

ters must	be of the data type required by the graphics routi
a float	format.

The procedure that processes the CALL does not implicitly start or e graphics routines.

For

more

information on OS/400

Graphics,

graphics

routines and parameters

theGDDM Programming

Guide

manual

and

theGDDM

Reference.

Note:

You

can

call

OS/400

Graphics

using

the

CALL

operation.

You

can

als

CALLP if you define a prototype

for the routine and specify t

keyword on the prototype. You cannot

use

the CALLB

operation.

Y

cannot pass

Date,

Time,

Timestamp,

or

Graphic fields

to

GDDM,

nor

you

pass

pointers

to it.

Calling Special Routines

ILE	RPG supports	the	use	of the following special routines using the
PARM	operations or	the	CALLP	operation:

¹Message-retrieving routine (SUBR23R3)

¹Moving Bracketed Double-byte Data and Deleting Control Characters (SUBR40R3)

¹Moving Bracketed Double-byte Data and Adding Control Characters (SUBR41R3).

Note:

You

cannot

use

the

CALLB

operation

to

call

these special subrout

can

use

CALLP

if

you define a prototype for the subroutines.

While

the

message

retrieval routine

is

still

supported,

it

is

recomme

use the QMHRTVM message API, which is more powerful.

Similarly,

the

routines

SUBR40R3

and

SUBR41R3

are

being

continued for

ibility

reasons

only.

They

will

not

be

updated

to

reflect

the

level

provided

by

RPG

IV

via

the

new graphic

data

type.

Multithreading Considerations

Normally,

running

an

application

in multiple threads can

improve the

perf

the application. In the case of ILE RPG, this

is not true in gene

formance of a multithreaded application could be

worse

than

that

of

version when the thread-safety is achieved by

serialization

of

the

module

level.

Running ILE RPG procedures in

a

multithreaded

environment

is

only

recom

when

required

by

other aspects

of

the

application

(for

example, w

Domino exit

program

or when

calling a

short-running

RPG

procedure

from

For long-running RPG programs called from Java, we

recommend

using

a

se

process

for

the

RPG

program.

The

THREAD(*SERIALIZE)

control

specification

keyword

can

be

specified

you

achieve

thread

safety

for

an

ILE

RPG

module.

Specifying

Chapter 10. Calling Programs and Procedures157