Exception Handling

Overview

 

2. If

an 'E' operation

code

extender is

present on

the calculation

the

exception is one

that

is expected

for

that

operation:

a. The return values for the built-in funtions %STATUS and %ERROR are

Note: %STATUS is set when any exception occurs even if the 'E' extender is not specified.

b. The exception is handled

c. Control resumes with the next ILE RPG operation.

3. If no error indicator or 'E' extenderand is present

¹you have coded a *PSSR error subroutine and the exception is exception

or

¹

you

have coded

a

INFSR

error

subroutine for the file

and

th

 

an

I/O

exception,

 

 

 

 

 

then

the

exception

will

be

handled

and control will resume

at

the

of

the

error subroutine.

 

 

 

 

4. If no error indicator, 'E' extender, or error subroutine is cod default error handler is invoked.

¹If the excepnotiona isfunction check, then the exception will be percolated.

¹If the exception is a function check, then an inquiry message

played. If the 'G' or 'R' option is chosen, the function chec and control will resume at the appropriate point (*GETIN for 'G'

calculation specification that

received

the

exception

for

'R')

dure. Otherwise,the function

check will

be

percolated

and

the

be abnormally terminated.

 

 

 

 

 

See “Unhandled Exceptions” on page 223 for a full description of the handler.

Exception

Handling

within Subprocedures

 

 

 

 

 

Exception

handling within a subprocedure differs from

a main

procedur

lowing ways:

 

 

 

 

 

 

¹ Because you cannot code

an

*INFSR

subroutine, you

should

handle fi

using

error

indicators or

the

'E'

operation code

extender.

¹There is no default handler; in other words, users will never see message.

Exception handling within a subprocedure differs from a main procedur because there is no RPG cycle code generated for subprocedures. there is no default exception handler for subprocedures and so sit default handler would be called for a main procedure correspond to of the subprocedure. This means that:

¹ Factor 2

of

an

ENDSR

operation

for

a

*PSSR

subroutine

within

a subp

must be

blank.

A

blank

factor

2 in

a

main

procedure

would

result

being passed to the default handler. In a subprocedure, if the reached, then the subprocedure will end abnormally and RNX9001 will nalled to the caller of the subprocedure.

Chapter 12. Handling Exceptions221

Page 244 Page 246
Page 245
Image 245
IBM AS/400 manual Infsr, Operation For
Page 244 Page 246

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