Table

15.

Operation Codes Allowing Extender 'E' or an Error Indicator in Positions

73-74

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

ACQ

(e)

 

ADDDUR (e)

ALLOC

 

(e)

 

CALL

(e)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CALLB(d e)

 

CALLP

(e

1

CHAIN

 

(e

n)

CHECK

(e)

 

 

 

m/r)

 

 

 

CHECKR

(e)

 

CLOSE

(e)

 

COMMIT

(e)

 

DEALLOC(e/n)

 

 

 

 

 

 

 

 

 

 

 

 

 

DELETE

 

(e)

 

DSPLY

(e)

EXFMT

 

(e)

 

EXTRCT

(e)

 

 

 

 

 

 

 

 

 

 

 

 

FEOD

(e)

 

IN

(e)

 

NEXT

(e)

 

OCCUR

(e)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

OPEN

(e)

 

OUT

(e)

 

POST

(e)

 

READ

 

(e

n)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

READC

 

(e)

 

READE

(e

n)

READP

 

(e

n)

READPE

(e

n)

 

 

 

 

 

 

 

 

 

 

 

 

 

REALLOC

(e)

 

REL

(e)

 

RESET

 

(e)

 

ROLBK

(e)

 

 

 

 

 

 

 

 

 

 

 

 

SCAN

(e)

 

SETGT

(e)

 

SETLL

(e)

 

SUBDUR

(e)

 

 

 

 

 

 

 

 

 

 

 

 

SUBST

(e p)

 

TEST

(e

d/t/z)

UNLOCK

(e)

 

UPDATE

(e)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

WRITE

(e)

 

XLATE

(e

p)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Notes:

1.CALLP (e m/r) is an extended Factor-2 operation code and cannot have an e indictator. However, program status and error conditions can be determined ifying the 'e' extender with this operation code.

When

you

specify

an

error

indicator or an

'E'

extender

on

an operatio

can explicitly

call

a

file

error

subroutine

(INFSR)

or

a

program

error

(*PSSR)

with

the

EXSR

 

operation. If

either

INFSR

or

*PSSR

is

explicitly c

the EXSR operation and Factor 2 of the ENDSR operation

is

 

blank

or the

specified

has

a value of blank, control returns to the

next sequential

lowing

the

EXSR

operation.

 

 

 

 

 

 

 

 

 

Using an Error Subroutine

When you write a error subroutine you are doing two things:

1. Enabling the RPG subroutine error handler

The subroutine error handler will handle the exception and pass cont subroutine.

2. Optionally specifying a recovery action.

You can use the error

subroutine to take specific actions based

which

occurred

or

you

can have a generic action (for example, iss

inquiry

message

for

all

errors).

The following considerations apply to error subroutines:

¹You can explicitly call an error subroutine by specifying the name

routine in Factor 2 of the EXSR operation.

¹You can control the point where processing resumes in a main proced specifying a value in Factor 2 of the ENDSR operation of the subro subprocedure, factor 2 of the ENDSR must be blank. Use either a

RETURN

operation prior to the ENDSR operation to prevent the subproce

from

ending abnormally.

¹If an error subroutine is called, the RPG error subroutine handler handled the exception. Thus, the call to the error subroutine refle program processing. If an exception occurs while the subroutine is

228 ILE RPG for AS/400 Programmer's Guide

Page 251 Page 253
Page 252
Image 252
IBM AS/400 manual Using an Error Subroutine, Program Error, Operation. If Either, Explicitly c
Page 251 Page 253

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