Using a Compiler Listing

Coordinating Listing Options with Debug View Options

Correcting run-time errors often involves debugging a program. The follow siderations may help you when you go to debug your program:

¹If you use the source debugger to debug your program you hav

debug views: *STMT, *SOURCE, *LIST, *COPY, *ALL.

¹If you plan to use a compiler listing as an aid while debugging,

 

obtain

one

by specifying OUTPUT(*PRINT). A listing

is important if

 

to debug

using a

statement (*STMT) view since the

statement numbers

setting breakpoints are those identified in the

source

listing. T

numbers are listed in the column labeled as the Line Number when

OPTION(*NOSRCSTMT) is

specified, and in the column labeled as

the Sta

ment

Number

when

OPTION(*SRCSTMT) is specified.

 

 

¹If you know that you will have considerable debugging to do, you compile the source with DBGVIEW(*ALL), OUTPUT(*PRINT) and OPTION(*SHOWCPY). This will allow you to use either a source or listi

view, and it will include /COPY members.

¹ If

you specify DBGVIEW(*LIST), the information available to you

wh

ging

depends

on what you specified for the OPTION parameter.

The

include /COPY members and externally described files only if you

OPTION(*SHOWCPY

*EXPDDS) — these are the defaults.

 

Using a Compiler Listing for

Maintenance

 

A

compiler

listing

of an

error-free program can be used as documenta

¹

Teaching

the

program

to a new programmer.

¹ Updating the program at a later date.

In either case it is advisable to have a full listing, namely, one OUTPUT(*PRINT) and with OPTION(*XREF *SHOWCPY *EXPDDS *EXT

*SHOWSKP).

Note:

Except

for

*SHOWSKP, this is the default

setting for

each of

t

 

ters on both create commands.

 

 

 

Of

particular value for program maintenance is

the Prologue

section

of

This

section

tells

you:

 

 

 

¹ Who compiled the module/program

¹ What source was used to produce the module/program

¹ What options were used when compiling the module/program

You may need to know about the command options (for example, the de selected, or the binding directory used) when you make later change program.

The

following specifications for the OPTION parameter provide addition

tion

as indicated:

¹*SHOWCPY and *EXPDDS provide a complete description of the program, including all specifications from /COPY members, and generated speci from externally described files.

Chapter 6. Creating a Program with the CRTBNDRPG Command69

Page 92 Page 94
Page 93
Image 93
IBM AS/400 manual Using a Compiler Listing for Maintenance, Coordinating Listing Options with Debug View Options, Showskp
Page 92 Page 94

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