Preparing a

Program for Debugging

members into the

module object. There

is

no dependency on the sourc

upon

which it is based, once the listing

view

is created.

For

example, to create a listing view for

a

program TEST1 that contai

DDS

type:

 

 

 

 

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

 

 

 

 

SRCMBR(TEST1)

OUTPUT(*PRINT)

 

 

 

 

TEXT('ILE RPG/400 program TEST1')

 

 

 

 

OPTION(*EXPDDS) DBGVIEW(*LIST)

 

 

 

Specifying DBGVIEW(*LIST) for the DBGVIEW parameter and *EXPDDS for th OPTION parameter on either create command creates a listing view with DDS for debugging the source for TEST1. Note that OUTPUT(*PRINT) and OPTION(*EXPDDS) are both default values.

Creating

a Statement

View

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

A statement

view

 

allows

 

the

module

object

to

be debugged

using

stateme

numbers and

the

debug

commands.

Since

the

source will not be display

must

make

 

use

of

statement

numbers which are shown in the

source

se

compiler

listing.

In

 

other

words, to effectively use this view, you

listing.

In

addition,

the

statement

numbers

generated

for

debugging

on whether *SRCSTMT or *NOSRCSTMT

is specified for the OPTION parameter.

*NOSRCSTMT means that statement numbers are assigned sequentially and are

displayed

as

Line

Numbers

on the left-most

column

of

the

source sect

compiler

listing. *SRCSTMT

allows

you to request that the compiler use SE

sequence

 

numbers and source IDs when generating

statement

numbers

fo

ging. The

Statement

Numbers

are

shown

on the right-most column

of

the

section

of

the

compiler

listing.

 

 

 

 

 

 

 

 

 

 

You create a statement view to debug a module by using the *STMT o DBGVIEW parameter for either the CRTRPGMOD or CRTBNDRPG commands

when you create a module.

Use this view when:

¹You have storage constraints, but do not want to recompile the mo

program if you need to debug it.

¹ You are sending compiled objects

to

other users and want to be

nose problems in your code using

the

debugger, but you do not w

users to see your actual code.

 

 

For example, to create a statement view for the program DEBUGEX usi CRTBNDRPG, type:

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

TEXT('ILE RPG/400 program DEBUGEX')

To create a statement view for a module using CRTRPGMOD, type:

CRTRPGMOD MODULE(MYLIB/DBGEX) SRCFILE(MYLIB/QRPGLESRC)

TEXT('Entry module for program DEBUGEX')

By default a compiler listing and a statement view are produced. U listing to obtain the statement numbers, you debug the program using commands.

Chapter 11. Debugging Programs169

Page 193
Image 193
IBM AS/400 manual View, Program for Debugging

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.