Setting and Removing Watch Conditions

To remove a conditional thread breakpoint using the Work with Module Bre display:

1. Type 4 (Clear) Optin fitheld next to the breakpoint you want to remove

2. Press Enter.

Using

the

TBREAK or CLEAR

Debug Commands

 

 

 

 

 

You

use

the

same syntax for the TBREAK debug command

as

you

would

fo

BREAK

debug command. The difference between these

commands

is

that

th

BREAK

debug command sets a conditional job breakpoint

at

the same posit

all

threads,

while the TBREAK debug command sets a

conditional

thread

b

point in

the

current thread.

 

 

 

 

 

To remove

a

conditional

thread breakpoint, use the

CLEAR

debug

command.

When

a conditional thread breakpoint is removed, it

is

removed

for

the

thread only.

 

 

 

 

 

 

 

Removing All Job and

Thread

Breakpoints

 

 

 

 

 

 

 

 

You

can

remove

all job and

thread

breakpoints,

conditional

and unconditio

a program object that has

a

module

object

shown on

the

Display

Module

display by using the CLEAR

PGM

debug

command.

To

use

the

debug

command,

type:

 

 

 

 

 

 

 

 

 

 

CLEAR PGM

 

 

 

 

 

 

 

 

 

 

on the debug command line.

The

breakpoints are

removed from all

of the

bound to

the

program.

 

 

 

 

 

 

 

 

Setting and Removing

Watch

Conditions

 

 

 

You

use watch condition

to monitor

if

the current value of an expression

variable

changes

while your program runs. Setting watch conditions is sim

setting

conditional

breakpoints,

with

one important difference:

¹Watch conditions stop the program as soon as the value of a watche

expression or variable changes from its current value.

¹ Conditional job breakpoints

stop the program only if a variable change

value specified in the

condition.

The debugger watches an expression or a variable through the contents storage address , computed at the time the watch condition is set. When content at the storage address is changed from the value it had whe condition was set or when the last watch condition occurred, the progr

Note: After a watch condition has been registered, the new contents a watched storage location are saved as the new current value of sponding expression or variable. The next watch condition will be if the new contents at the watched storage location change subs

188 ILE RPG for AS/400 Programmer's Guide

Page 211 Page 213
Page 212
Image 212
IBM AS/400 manual Removing All Job, Debug Commands, Setting and Removing Watch Conditions
Page 211 Page 213

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