IBM Version 4 manual Dynamic Screen Manager APIs, Debugger, Low-level services, Window services

Ÿ

Original

program

model

(OPM)

APIs

– Retrieve Program Variable API

You can use these sets of source debugger APIs independently

of ea

together as needed. The source

debugger

APIs

can

be used

to

write

for the

AS/400

system. The users

of these

APIs

include:

Ÿ

The

source

debugger

that

is

shipped with the OS/400 licensed progr

source

debugger

is

a

tool

for

debugging

Integrated Language

Environment

(ILE)

programs

by

displaying a

representation

of

their source

code.

ŸAny other debugger that IBM or a business partner writes.

Debugger		functions		are	designed		to help you write and maintain your a
You	can run		your	programs in a special testing environment while closely
and	controlling		the	processing		of	these	programs in the testing environmen
can	write	a	debugger		application		that	interacts with the debugger API
use	the	debugger		provided		with	the	AS/400 system.

All debugger APIs must be called within the job in which the Start De (STRDBG) command is issued. The same program can be used at the same in another job without being affected by the debugger functions set

To enable source-level debugging of ILE programs, view information must b stored with the compiled program. The ILE compilers use the create vie create view information. This information is then available to source-level applications through the source debugger APIs.

Dynamic Screen Manager APIs

The Dynamic Screen Manager (DSM) APIs are a set of screen I/O interfa provide a dynamic way to create and manage screens for the Integrat Environment (ILE) high-level languages. Because the DSM interfaces are bind they are accessible to ILE programs only.

The DSM APIs provide an alternative to the existing way of defining sc ance outside a program by coding in data description specifications ( interface manager (UIM), for example. Instead, programmers can use a calls to DSM within their programs to dynamically specify and control scr appearance for their applications. Unlike static definition methods, the faces provide the flexibility needed for those applications requiring screen control. The DSM support provided varies from low-level interfaces direct screen manipulation to windowing support.

The DSM APIs fall into the following functional groups:

ŸLow-level services

The low-level services APIs provide a direct interface to the 5250 commands. These APIs are used to query and manipulate the state of screen; to create, query, and manipulate input and command buffers interact with the screen; and to define fields and write data to

ŸWindow services

The window services APIs are used to create, delete, move, and re windows, and to manage multiple windows during a session.

8-4System API Programming V4R1