Using the Fixed-Form Call

Operations

 

 

For more information on operational descriptors, see “Using Operational

 

Descriptors” on page 138.

 

¹

There

are further restrictions that apply when using the CALL

or CALL

 

tion

codes. For a detailed description of theseILErestrictions,RPG for

see

 

AS/400

Reference.

 

Examples of CALL and CALLB

For

examples of

using

the

CALL operation,

see:

¹

“Sample Source

for

Debug

Examples” on

page 211, for example of calli

 

RPG program.

 

 

 

 

For examples of using the CALLB operation, see:

¹Figure 45 on page 99, for an example of calling a procedure in a se program.

¹ Figure 56 on page 123, for an example of calling bindable APIs.

¹“CUSMAIN: RPG Source” on page 347, for an example of a main inquiry program calling various RPG procedures.

Passing Parameters Using PARM

and

PLIST

 

 

 

 

When

you

pass

parameters using fixed-form call,

you must

pass

paramete

the PARM and PLIST operations. All parameters are passed by reference.

specify that an operational descriptor is to be passed and can also

parameter

is

omitted.

 

 

 

 

Using

the

PARM

operation

 

 

 

 

The

PARM operation is used to identify the parameters which are pass

received

by a procedure. Each parameter is defined in a separate

You

specify

the name

of the parameter in the

Result

field;

the name

the

same

as

in

the

calling/called procedure.

 

 

 

The Factor 1 and factor 2 entries are optional and indicate variables whose value is transferred to or received from the Result Field entr whether these entries are in the calling program/procedure or the cal program/procedure. Table 12 shows how factor 1 and factor 2 are use

Table

12. Meaning of Factor 1 and Factor 2 Entries in PARM Operation

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Status

 

 

Factor

1

 

 

Factor

2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Incalling

 

Value

transferred

from

ResultValue

placed

in

Result

Field

procedure

 

Field

entry upon return.

entry

when

call

occurs.

 

 

 

 

 

 

 

 

 

 

 

 

 

Incalled

 

Value

transferred

from

ResultValue

placed

in

Result

Field

procedure

 

Field entry when call occursentry. upon return.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note:

The

moves to

either

the

factor

1

entry

 

or

the result-field ent

 

when

the called procedure returns normally to its caller. If an

 

while

attempting to

move

data

to

either

entry, then

the move is

pleted.

150 ILE RPG for AS/400 Programmer's Guide

Page 173 Page 175
Page 174
Image 174
IBM AS/400 manual Examples of Call and Callb, Operations, Passing Parameters Using Parm, Data Either Entry, then Move is
Page 173 Page 175

AS/400 specifications

The IBM AS/400, now known as the IBM iSeries, is a midrange computer system that has been a cornerstone of enterprise computing since its introduction in 1988. Designed to provide a robust platform for business applications, the AS/400 is celebrated for its reliability, scalability, and integrated database capabilities.

One of the key features of the AS/400 is its Integrated Operating Environment, which blends hardware and software resources seamlessly. This integration allows businesses to execute diverse workloads, ranging from traditional applications to modern web-based services, all on a single platform. The operating system, OS/400 (now IBM i), offers a rich set of APIs and tools for developers, simplifying application development and management.

Another standout characteristic of the AS/400 is its built-in database, DB2 for i. This powerful relational database management system allows for efficient data handling and provides advanced features such as support for SQL, XML, and JSON, making it easier for businesses to manage their data and integrate it with other systems. The database's tight integration with the operating system enables high performance and security.

In terms of scalability, the AS/400 can accommodate small businesses as well as large enterprises, with the ability to support hundreds of users simultaneously. Its architecture allows for easy upgrades in hardware, meaning that organizations can scale their systems without replacing the entire infrastructure.

Security is another critical attribute of the AS/400. With a sophisticated security model, it offers built-in user authentication, access control, encryption, and auditing capabilities to protect data and applications from unauthorized access.

The AS/400 also supports multiple programming languages, including RPG, COBOL, Java, and PHP, giving organizations the flexibility to choose the development tools that best fit their needs. This diversity helps maintain legacy applications while also developing new ones that leverage modern technologies.

Moreover, the platform supports both traditional green-screen interfaces and modern graphical user interfaces, allowing organizations to transition smoothly into contemporary user experience paradigms.

Overall, the IBM AS/400 stands out as a resilient, flexible, and secure computing platform that enables organizations to effectively manage their business operations, streamline processes, and adapt to changing market demands. Its unique combination of integrated features and capabilities ensures that it remains relevant in today's fast-paced technology landscape.
Top Page Image Contents