ILE Condition Handlers

*

-----------------------------------------------------------------

 

 

 

*

 

 

 

 

 

* Register the handler and generate errors

 

*

*

-----------------------------------------------------------------

 

 

 

*

C

 

EXSR

RegHndlr

 

 

 

*

-----------------------------------------------------------------

 

 

 

*

*

Generate a substring error

 

 

*

*

This is an "allowed" error for this example (RPGHDLR

 

*

*

handles the exception, allowing control to return to the

*

*

next instruction after the error).

 

*

*

RPGHDLR will not allow the error unless the "AllowError"

*

*

indicator is set on.

This ensures that if, for example,

*

*

a SCAN operation is added to SHOWERR later, RPGHDLR will

*

*

not by default allow it to have an error.

 

*

*

-----------------------------------------------------------------

 

 

 

*

C

 

Z-ADD

-1

Num

 

 

C

 

EVAL

AllowError = '1'

 

 

C

Num

SUBST

'Hello'

Examp

10

 

C

 

EVAL

AllowError = '0'

 

 

*

-----------------------------------------------------------------

 

 

 

*

*

The exception was handled by the handler and control

 

*

*

resumes here.

 

 

 

*

*

-----------------------------------------------------------------

 

 

 

*

C

 

EXCEPT

ImBack

 

 

 

*

-----------------------------------------------------------------

 

 

 

*

*

Generate an array out of bounds error

 

*

*

This is not an "expected" error for this example.

 

*

*

-----------------------------------------------------------------

 

 

 

*

C

 

Z-ADD

-1

Num

 

 

C

 

MOVE

Arr1(Num)

Arr1(Num)

 

 

*

-----------------------------------------------------------------

 

 

 

*

*

The exception was not handled by the handler, so,

 

*

*

control does not return here.

The exception is

 

*

*

percolated and control resumes in the *PSSR.

 

*

*

-----------------------------------------------------------------

 

 

 

*

*

-----------------------------------------------------------------

 

 

 

*

*

Deregister the handler

 

 

 

*

*

Note: If an exception occurs before the handler is

 

*

*

deregistered, it will be automatically deregistered

 

*

*

when the procedure is cancelled.

 

*

*

-----------------------------------------------------------------

 

 

 

*

C

 

EXSR

DeRegHndlr

 

 

C

 

SETON

 

 

 

LR

*=================================================================*

* RegHdlr - Call the API to register the Handler

 

*

*=================================================================*

C

RegHndlr

BEGSR

 

 

 

 

C

 

CALLP

CEEHDLR(pConHdlr : %ADDR(CommArea) : *OMIT)

C

 

ENDSR

 

 

 

 

*=================================================================*

* DeRegHndlr - Call the API to unregister the Handler

 

*

*=================================================================*

C

DeRegHndlr

BEGSR

 

 

 

 

C

 

CALLP

CEEHDLU(pConHdlr : *OMIT)

 

 

C

 

ENDSR

 

 

 

 

 

 

 

 

Figure

117 (Part 2

of 3).

Source for Registering a Condition Handler

Chapter 12. Handling Exceptions243

Page 267
Image 267
IBM AS/400 manual Subst, Begsr Callp

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.