Starting the ILE Source Debugger

If the default values for either create command have been changed, explicitly specify DBGVIEW(*STMT) and OUTPUT(*PRINT).

Starting the ILE Source

Debugger

 

 

 

 

 

 

 

 

 

 

 

 

Once

you

have

created

the

debug view

(statement, source, COPY, or li

can begin debugging your application. To

start the ILE source debugge

Start

Debug (STRDBG) command. Once the debugger

is started,

it

remains

until you enter the End Debug (ENDDBG) command.

 

 

 

 

 

 

Initially

you

can

add

as many as 20 program

objects

to

a

debug

ses

the

Program (PGM) parameter on the STRDBG

command.

They

can

be any

comb

nation of OPM or ILE programs. (Depending

on how the OPM programs were

piled

and also

on

the

debug

environment

settings, you may be able to

by using the ILE source debugger.) In

addition, you can initially ad

service program objects to a debug session by

using

the

 

Service

Progr

(SRVPGM) parameter on the STRDBG command.

The rules

for

debugging

a

 

service

program are the same

as those

for

debugging

a

program:

 

 

¹ The program or service program must have debug data.

¹You must have *CHANGE authority to a program or service program objec include it in a debug session.

Note:

If

 

debugging

a

program

using

the

COPY

or

root

source

view, the

 

code

must be

on

 

the same system as the

program object

being

d

 

In

addition,

 

the

 

source

code

must

be

in

a

library/file(member)

 

name

 

as

when

 

it

was

compiled.

 

 

 

 

 

 

 

 

 

 

For

an

ILE

program,

the

entry

module

is

shown

if

 

it

has

debug

data;

first

module

bound

to

 

the ILE program with debug

data

is

shown.

 

For

an

OPM

 

program,

 

the

 

first

program

specified

on the STRDBG command is

shown

if

it

has

debug

data, and the OPMSRC parameter is *YES.

That

is,

OPM program is in a

debug session, then you can debug it using the I

debugger

 

if

the

following

conditions

are

met:

 

 

 

 

 

 

 

1.The OPM program was compiled with OPTION(*LSTDBG) or OPTION(*SRCDBG). (Three OPM languages are supported: RPG, COBOL, and CL. RPG and COBOL programs can be compiled with *LSTDBG or

*SRCDBG, but CL programs must be compiled with *SRCDBG.

2. The

ILE debug

environment

is set to

accept

OPM programs. You can d

by

specifying

OPMSRC(*YES) on

the

STRDBG command.

(The

system

default

is

OPMSRC(*NO).)

 

 

 

 

 

 

 

If these two conditions are

not

met,

then you

must

debug

the OPM pro

the

OPM

system debugger.

 

 

 

 

 

 

If an OPM program compiled without *LSTDBG or *SRCDBG is specified and a service program is specified, the service program is shown if it has there is no debug data, then the DSPMODSRC screen will be empty. If program and a service program are specified, then the ILE program wil

170 ILE RPG for AS/400 Programmer's Guide

Page 194
Image 194
IBM AS/400 manual Starting the ILE Source Debugger, Opmsrc*No

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.