EVAL debug

command

(continued)

 

examples

 

(continued)

 

 

 

using

199

 

 

 

 

 

 

 

 

 

 

passing parameters using the CL CALL

event file for CODE/400 411

 

 

command

 

104

 

 

 

 

 

examples

 

 

 

 

 

 

 

 

 

 

 

 

program/procedure call

 

 

compiling

 

 

 

 

 

 

 

 

 

 

 

checking number of passed parameters 141

binding multiple

modules

84

 

 

using

 

omitted

parameters

94

OPM-compatible program 61

 

 

 

sample ILE RPG program 6

 

program for source debugging 59

 

subprocedures

37, 38

 

 

program with static binding 60

 

 

creating a NOMAIN module 75

sample

binder

listing

100

 

exception

 

 

 

 

 

 

 

 

 

service

program

94

 

 

 

 

 

monitoring during run time 109

converting

to

RPG

IV

 

 

 

 

 

nested,

 

223

 

 

 

 

all members in a file 388

 

exception

 

handler

 

 

 

 

performing a trial conversion 388

 

priority

 

of

 

223

 

 

 

sample

conversion

390

 

 

 

 

 

RPG-specific

 

220, 226

 

 

some members in a file 388

 

exception

 

messages

 

 

 

 

debugging

 

 

 

 

 

 

 

 

 

 

percolation

 

218

 

 

 

 

adding a service program to a session

173types

 

of

218

 

 

 

 

changing

field

 

values

209

 

 

unexpectedly handled by CL MONMSG 247

changing the debug view of a module 176

unhandled

 

223

 

 

 

 

displaying attributes of a field 210

exception/error

handling

 

 

displaying data addressed by pointers 206

*PSSR

error subroutine 232

 

displaying fields as hexadecimal values 205avoiding a loop 235

 

 

displaying fields in character format 205

cancel

handler 244

 

 

 

displaying fields in UCS-2 format 206

 

condition

 

handler

238

 

 

displaying fields in variable-length format 206differences between ILE RPG and OPM

displaying

indicators

204

 

 

RPG/400

 

 

222, 374

 

 

 

displaying multiple-occurrence data

 

error

 

indicators

227

 

 

structures

203

 

 

 

 

 

 

error/exception

subroutine

overview 228

displaying the contents of a table 202

 

file error/exception (INFSR) subroutine 229

displaying the contents of an array 202

 

general

 

considerations

223

 

removing programs from a session 173

 

NOOPT

keyword

 

226

 

 

 

setting a conditional breakpoint 182

 

optimization

considerations

226

setting an unconditional breakpoint 179

 

overview

 

217

 

 

 

 

setting

debug

 

options

171

 

 

percolation

 

218

 

 

 

 

source for debug examples 211

 

RPG-specific

 

220

 

 

 

using %SUBSTR to display field values 207

 

specifying a return point 237

viewing a different module in a debug

 

types

 

of

217

 

 

 

 

session

 

175

 

 

 

 

 

 

 

 

unhandled

 

223

 

 

 

 

handling

 

exceptions

 

 

 

 

 

 

using

'E'

 

extender

227

 

 

*PSSR

error

subroutine

232

 

EXFMT (write/then read format) operation code 342

avoiding

a

loop

 

in

an

error

subroutine 235EXPCPY

parameter

386

 

 

 

cancel

handler

 

244

 

 

 

 

EXPORT

keyword

 

 

 

 

 

 

file

 

error subroutine

 

229

 

 

duplicate

names

84

 

 

 

unhandled

escape

message 224

expressions

 

 

 

 

 

 

 

unhandled

function

check

225

 

 

returning

 

values

134

 

 

using a cancel handler 245

 

extension

specifications

 

 

using a condition handler 238

 

 

conversion

problems

392,

400

 

I/O

 

 

 

 

 

 

 

 

 

 

 

external-references list in compiler listing 435

data

 

maintenance

349

 

 

 

externally

described

file

 

inquiry by zip code and search on name

364access

 

path

 

282

 

 

 

inquiry

program

346

 

 

 

 

 

adding to external description 265

subfile

processing

358

 

 

 

 

advantages

261

 

 

 

 

interactive

application 345

 

 

as program-described 264

 

managing your own heap 119

 

 

as WORKSTN file 331, 335

 

module

with

multiple

procedures

41

 

definition

 

263

 

 

 

 

Index 451

Page 475
Image 475
IBM AS/400 manual Binder Listing 100 Exception Service

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.