5. The ENDSR operation receives control, and the procedure is cancele

The approach used here to avoid looping can also be used within an subroutine.

Specifying a Return Point

in

the

 

ENDSR

Operation

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

When

using an INFSR or *PSSR error subroutine

in a main procedure, you

indicate

the

return

point

at

which the program will resume processing

one

of

the

following

as

the

 

Factor 2 entry of the ENDSR statement. T

be

a six-position character

 

field, literal, named constant, array ele

name

whose

value

specifies

one

of

the

following

return

points.

 

 

 

Note:

If the return points are specified

 

as literals, they must be

 

trophes

and

entered

in

uppercase

(for

example,

*DETL,

not

*detl).

 

are specified in fields or

array

elements,

the

value

must

be

 

the

field or array element.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

*DETL

 

Continue at the beginning of detail lines.

 

 

 

 

 

 

 

 

*GETIN

 

Continue at the get input record routine.

 

 

 

 

 

 

 

 

*TOTC

 

Continue at the beginning of total calculations.

 

 

 

 

 

 

 

*TOTL

 

Continue at the beginning of total lines.

 

 

 

 

 

 

 

 

 

*OFL

 

Continue at the beginning of overflow lines.

 

 

 

 

 

 

 

 

*DETC

 

Continue at the beginning of detail

 

calculations.

 

 

 

 

 

 

*CANCL

 

Cancel the processing of the program.

 

 

 

 

 

 

 

 

 

 

Blanks

 

Return

control

to

 

the

ILE RPG default exception handler. This

 

 

when

Factor 2 is

a

 

valueandof whenblanksFactor

2

is

not

specified.

 

 

the subroutine was called by the

 

EXSR

operation

and

Factor

 

 

 

control returns to the next sequential

instruction.

 

 

 

 

 

 

After the

ENDSR

operation

 

of

 

the INFSR or the *PSSR subroutine is run,

RPG

compiler resets the field or array element specified in Factor

 

Because Factor 2 is set to

blanks,

you

can

specify

the

return

poi

routine

that

is

 

best

suited

for

the

exception

that

occurred.

 

 

If

this

field

contains

blanks

at the end of the subroutine, the I

tion

handler

receives

control

 

following

the

running

of

the

subroutine,

u

INFSR

or

the

*PSSR

subroutine

was

called

by

the EXSR operation. If t

tine

was called by the EXSR

operation

and

 

Factor 2 of the ENDSR ope

blank, control returns to the

 

next

sequential

instruction

following

the

E

tion.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note:

You cannot specify a factor

2

 

entry

for

an

ENDSR

in

a

 

subproc

 

want to resume processing in the subprocedure, you have to us

 

operation to a TAG in the

body

 

of

the

subprocedure.

Alternativ

 

code a

RETURN

operation

in

the

 

*PSSR.

 

The

subprocedure

will

then

 

to

the

caller.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Chapter 12. Handling Exceptions237

Page 261
Image 261
IBM AS/400 manual Specifying a Return Point, Ofl

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.