Using

the Fixed-Form Call Operations

If

insufficient

parameters

are

specified when calling a procedure,

when

an

unresolved

parameter

is

used by the called procedure. To a

you

can

either:

 

 

 

¹Check %PARMS to determine the number of parameters passed. For an example using %PARMS, see “Checking for the Number of Passed Parameters” on page 141.

¹Specify *OMIT in the result field of the PARM operations of the parameters. The called procedure can then check to see if the been omitted by checking to see if the parameter has value of %ADDR(parameter) = *NULL. For more information, refer to “Omitting Parameters” on page 139.

Keep in mind the following when specifying a PARM operation:

¹

One

or

more PARM

operations

must

immediately

follow

a

PLIST

operation.

¹

One or more PARM operations can immediately

follow

a

CALL

or

CALLB ope

 

ation.

 

 

 

 

 

 

 

 

 

¹

When

a

multiple

occurrence

data

structure

is specified in the R

 

PARM operation, all occurrences of the data

structure

are

passed

 

field.

 

 

 

 

 

 

 

 

 

¹Factor 1 and the Result field of a PARM operation cannot contain

look-ahead field, a named constant, or a user-date reserved word.

¹ The following rules apply to *OMIT for non-prototyped parameters:

– *OMIT

is only

allowed

in

PARM

operations that immediately follows a

CALLB

operation

or in

a

PLIST

used with a CALLB.

–Factor 1 and Factor 2 of a PARM operation must be blank, if *O specified.

– *OMIT is not allowed in a PARM operation that is part of a *ENTR

¹ There are other restrictions that apply when using the PARM operat For a detailed description of these restrictions,ILE RPG for seeAS/400 the Reference.

For examples of the PARM operation see:

¹ Figure 47 on page 105

¹ Figure 42 on page 95

¹Figure 116 on page 239

Using the PLIST Operation

The PLIST operation:

¹Defines a name by which a list of parameters can be reference parameters is specified by PARM operations immediately following the operation.

¹Defines the entry parameter list (*ENTRY PLIST).

Factor 1 of the PLIST operation must contain the PLIST name. This name specified in the Result field of one or more call operations. If the entry parameter list of a called procedure, then Factor 1 must

Chapter 10. Calling Programs and Procedures151

Page 174 Page 176
Page 175
Image 175
IBM AS/400 manual Using the Plist Operation, Fixed-Form Call Operations
Page 174 Page 176

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