Setting and Removing Breakpoints

ˆ

Display Module Source

..............................................................................

:

 

 

 

 

 

Select View

:

:

 

 

 

 

 

 

:

:

Current View . . .

:

ILE RPG Copy View

:

:

 

 

 

 

 

 

:

: Type option, press Enter.

 

:

:

 

 

1=Select

 

 

:

:

Opt

View

 

 

:

:

 

 

:

:

1

 

ILE RPG Listing View

:

:

 

 

 

ILE RPG Source View

:

:

 

 

 

ILE RPG Copy View

:

:

 

 

 

 

 

 

:

:

 

 

 

 

 

 

Bottom :

:

F12=Cancel

 

 

:

:

 

 

 

 

 

 

:

:

............................................................................

 

 

 

 

:

 

 

 

 

 

 

 

More...

Debug . . .

_________________________________________________________________

_______________________________________________________________________________

F3=End program

F6=Add/Clear breakpoint

F10=Step

F11=Display variable

F12=Resume

F17=Watch variable

F18=Work with

watch

F24=More keys

˜

Figure 80. Changing a View of a Module

The current view is listed at the top of the window, and the o available are shown below. Each module in a program can have a di of views available, depending on the debug options used to creat

Note: If

a

module

is created with DBGVIEW(*ALL), the

Select

View

will

show three views available: root source, COPY,

and

listing

module

has no

/COPY members, then the COPY view

is

identical

root

source

view.

 

 

 

3.Type 1a next to the listing view, and press Enter. The Display Mod display appears showing the module with a listing view.

Setting and Removing Breakpoints

You can use breakpoints to halt a program object at a specific po

running. Anunconditional breakpointstops the program object at a specific

ment. Aconditional breakpointstops the program object when a specific c tion at a specific statement is met.

 

There are two types of breakpoints: job threadand threinad.threadedEach

 

 

 

application

may

have

it's

own thread

breakpoint

at

the

same position

 

time.

Both

job

and

thread

breakpoints can

be

unconditional

or

conditi

 

general, there

is one set of debug commands and Function

keys

for j

 

and another for

thread breakpoints. For the rest of this section on

 

word

breakpoint

refers

to

both

job

and

thread,

unless specifically

 

wise.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note:

Breakpoints

are

automatically

generated

for

input

and

output

spe

 

if

the

default

OPTION(*DEBUGIO)

is

specified.

If

you

do

not

 

erate

breakpoints,

specify

OPTION(*NODEBUGIO).

 

 

 

 

You set the breakpoints prior to running stops, the Display Module Source display

the program. When the progr is shown. The appropriate mo

Chapter 11. Debugging Programs177

Page 201
Image 201
IBM AS/400 manual Setting and Removing Breakpoints, Specified You Not Erate Breakpoints Specify, Option*Nodebugio

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.