Setting and Removing Breakpoints

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

‡

 

 

 

 

 

Display Module Source

 

 

 

—

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Program:

 

MYPGM

 

Library:

MYLIB

Module:

MYPGM

 

 

 

 

 

 

 

33

 

002500

 

* Begin-procedure

 

 

 

 

 

 

 

 

 

 

 

34

 

002600

P

FmtCust

 

 

B

 

 

 

 

 

 

 

 

 

 

 

35

 

002700

D

FmtCust

 

 

PI

25A

 

 

 

 

 

 

 

 

 

 

36

 

002800

 

* Procedure-interface (same as the prototype)

 

 

 

 

 

 

 

37

 

002900

D

FirstName

 

10A

 

 

 

 

 

 

 

 

 

 

38

 

003000

D

LastName

 

 

15A

 

 

 

 

 

 

 

 

 

 

39

 

003100

D

ValidRec

 

 

N

 

 

 

 

 

 

 

 

 

 

40

 

003200

 

* Calculations

 

 

 

 

 

 

 

 

 

 

 

 

41

 

003300

C

 

 

 

IF

ValidRec = '0'

 

 

 

 

 

 

 

 

42

 

003400

C

 

 

 

RETURN

%TRIMR(FirstName) + ' ' + Last

 

 

 

 

 

 

 

43

 

003500

C

 

 

 

ENDIF

 

 

 

 

 

 

 

 

 

 

 

44

 

003600

C

 

 

 

RETURN

'Last Customer'

 

 

 

 

 

 

 

45

 

003700

 

* End-procedure

 

 

 

 

 

 

 

 

 

 

 

 

46

 

003800

P

 

 

 

E

 

 

 

 

 

 

 

 

 

 

 

47

 

 

*MAIN PROCEDURE EXIT

 

 

 

More...

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Debug . . . BREAK

fmtcust/2600_______________________________________________

 

 

 

 

 

_______________________________________________________________________________

 

 

 

 

 

 

 

F3=End program

F6=Add/Clear breakpoint F10=Step F11=Display variable

 

 

 

 

 

 

 

F12=Resume

 

F17=Watch variable

F18=Work with watch

F24=More keys

 

 

 

 

 

ˆ Breakpoint

added to

line 34.

 

 

 

 

 

 

˜

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Figure 87.

Setting a Breakpoint using Statement Numbers and a Listing View with

OPTION(*SRCSTMT)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

To

set

a

conditional

job

breakpoint

using

the

BREAK debug

command, typ

BREAK procedure-name/statement-number WHEN expression

 

 

 

 

 

 

 

on

the

debug

command

line.

The procedurevariables-name and statement-number

are the same as for unconditional breakpointsexpression. The variableisthe con-

ditional

expression that

is

evaluated when

the

breakpoint

is encounter

To remove an unconditional or conditional breakpoint using the CLEAR deb command, type:

CLEAR procedure-name/statement-number

on the debug command line.

Setting and Removing Conditional Thread Breakpoints

You can set or remove a conditional thread breakpoint by using:

¹ The Work with Module Breakpoints display

¹The TBREAK debug command to set a conditional thread breakpoint in current thread

¹ The CLEAR debug command to remove a conditional thread breakpoint.

Using the Work with Module Breakpoints Display

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

1.Type 1 (Add) Optin fitheld.

2.In Threadthe field, type the thread identifier.

3. Fill in the remaining fields as if it were a conditional job bre

4. Press Enter.

Chapter 11. Debugging Programs187

Page 210 Page 212
Page 211
Image 211
IBM AS/400 Setting and Removing Conditional Thread Breakpoints, Using the Work with Module Breakpoints Display, Return
Page 210 Page 212

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