Preparing a Program for Debugging

Creating a COPY Source

 

View

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

A COPY

source

view

 

contains

text

from

the root

source

 

member,

as

well

a

text

of

all

/COPY

members

expanded

into the text of the source. Whe

COPY view, you can debug the root

source member

of

the

program

using

source

view

and

 

the

/COPY

members

of

the

program

using

the

COPY

 

source

The

view

of the root source member

generated by

DBGVIEW(*COPY)

 

is

th

view generated by DBGVIEW(*SOURCE).

As with the root source view, a C

source

view

is

not available

if

the

source

file

is

a

DDM

file.

 

 

You create a COPY source view to

debug

a

module

by

using

the

*COPY

option

on

the

DBGVIEW

parameter.

 

 

 

 

 

 

 

 

 

 

 

 

 

The compiler creates the COPY view

while

the

module

 

object

(*MODULE)

is

compiled. The COPY view is created

using references to locations of t

source members (both root source

member and /COPY members) rather than

copying the text of the members into the view. For

this

reason,

you

modify, rename, or move source members between the

 

time

 

the module

ob

created

and

the

debugging of

the

module

created

from

these

members.

the

views

for

these

source

members

may

not

be

usable.

 

 

 

 

 

For example, to create a source view of a program TEST1 that contains members type:

CRTBNDRPG PGM(MYLIB/TEST1) SRCFILE(MYLIB/QRPGLESRC)

TEXT('ILE RPG/400 program TEST1')

DBGVIEW(*COPY)

Specifying DBGVIEW(*COPY)

with

either create command creates a root sou

view with

/COPY

members

for

debugging module TEST1. By default, a compil

listing is

produced. The compiler listing will include /COPY members as w

OPTION(*SHOWCPY) is

a default

value.

Creating

a Listing View

 

 

 

 

 

 

 

 

 

 

 

 

 

A listing view contains

text

similar to the

text in the compiler listing th

produced by the ILE RPG compiler. The information contained in the lis

dependent on whether OPTION(*SHOWCPY), OPTION(*EXPDDS), and

 

 

 

 

 

OPTION(*SRCSTMT) are specified for either create command.

 

 

 

 

OPTION(*SHOWCPY) includes /COPY members in the listing; OPTION(*EXPDDS)

 

 

includes

externally

described files.

OPTION(*SRCSTMT)

allows

the

program

ob

to be debugged using the Statement Numbers instead

of

the

Line

Numbe

compiler

listing.

 

 

 

 

 

 

 

 

 

 

 

 

Note:

Some

information

that

is available

in

the

compiler

listing

will

not

a

 

the listing view. For example, if

you

specify

indentation in

the

 

listing (via the INDENT parameter),

the indentation will not appear

 

listing view. If you specify OPTION(*SHOWSKP) in

the

compiler

listin

 

skipped statements will not appear

in the

listing

view.

 

 

 

 

You

create a listing view to debug a

module by using the *LIST or *A

 

the

DBGVIEW parameter for either the

CRTRPGMOD

or

CRTBNDRPG commands

 

 

when

you

create a

module.

 

 

 

 

 

 

 

 

 

 

The compiler creates the listing view while the module object (*MODULE) generated. The listing view is created by copying the text of the

168 ILE RPG for AS/400 Programmer's Guide

Page 191 Page 193
Page 192
Image 192
IBM AS/400 manual Listing View, Dbgview, Module, Listing view contains
Page 191 Page 193

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