Conditional Breakpoint, Opt Line Condition

Setting and Removing Breakpoints

is encountered. The relational operators supported for conditional break noted at the beginning of this section.


In	non-numeric		conditional breakpoint expressions,		the	shorter expression		i
itly	padded		with blanks before the	comparison is		made. This	implicit	p
before		any	National Language Sort Sequence (NLSS) translation. See “National
Language		Sort	Sequence (NLSS)” on page	183 for	more	information	on NLSS.

To remove a conditional breakpoint using the CLEAR debug command, type:

CLEAR line-number

on the debug command line. Thelinevariable-numberis the line number in the currently displayed view of the module object from which you want to breakpoint.

Example of Setting a Conditional Job Breakpoint Using F13

In this example you set a conditional job breakpoint using F13 (Work breakpoints).

1. To	set	a conditional	job breakpoint press F13 (Work with module br
The	Work	with Module	Breakpoints display is shown.

2.On this display type 1 (Add) on the first line of the list to a breakpoint.

3. To set		a	conditional breakpoint at line 127 when *IN02='1', type 12
Line	field,		*IN02='1' Conditionfor thefield.
4. If	a	thread column is shown, before pressing Enter, type *JOB in
field.
Figure 82 shows the Work with Module Breakpoints display after adding
conditional			breakpoint.

‡

		Work with Module Breakpoints		System:	TORASD80
				System:	TORASD80
Program	. . . :	DEBUGEX	Library . . . :	MYLIB
Module . . . :		DBGEX	Type . . . . . :	*PGM
Type options, press Enter.
1=Add	4=Clear
Opt	Line	Condition

127*in02='1'

Bottom

Command

===> ________________________________________________________________________

F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel

ˆBreakpoint added to line 127.

—

Figure

82.

Setting a Conditional Job Breakpoint

A conditional job breakpoint is set

on

line

127.

The

expression

before

the

statement

run.

the

result

true (in

the

exa

the

program

stops,

and

the

Display

Module

Source

display is

shown.

result

is false,

the

program

continues

run.

existing

breakpoint

always

replaced by

new

breakpoint

enter

same

location.

182 ILE RPG for AS/400 Programmer's Guide

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.

IBM AS/400 Example of Setting a Conditional Job Breakpoint Using F13, Opt Line Condition

Models: AS/400

Setting and Removing Breakpoints

Example of Setting a Conditional Job Breakpoint Using F13

Line

Figure 82 shows the Work with Module Breakpoints display after adding

conditional

breakpoint.

Work with Module Breakpoints

Opt

Line

Condition

Bottom

ˆBreakpoint added to line 127.

on

182 ILE RPG for AS/400 Programmer's Guide

AS/400 specifications