IBM Version 4 manual Error, Parameter

à

Display Messages

ð

System:

GENSYS9ð

Queue . . . . . :

QPGMR

Program . . . . :

\DSPMSG

Library . . . :

QUSRSYS

Library . . . :

Severity

. . . :

ðð

Delivery

. . . :

\HOLD

Type reply (if required), press Enter.

From

. . . :

SMITH

ð7/25/94

11:1ð:12

No such \JOBD exists

If

another

exception

occurs (for

example,

a

library name that is n

not

receive

an

indication

that an error occurred because of the w

routine

is currently coded.

In

addition, you

can

use

the

Message

Handling

APIs to

receive

the

to

your

program

message

queue.

The

call

to

the

API

fails

if

you

specify a valid job description

ifier

such

as

*ALLUSR. The

value *ALLUSR

is

not

supported

by the

des

the

required

parameter

group.

Retrieving the Hold

Parameter

(Error

Code

Structure)—OPM RPG

Example

In the program example in “Retrieving the Hold Parameter (Exception Message)—OPM RPG Example,” QUSBNB (.6/ on page 3-7) was set to a value binary zero to tell the API to send exceptions (escape messages) ditions. The example in this topic uses an error-code data structure tive to receiving exceptions.

Some	languages do	not support	the use of exceptions, so you may pre
for	errors using	error code	structures.

In your programs, you can use error code structures in the followin

ŸDefine an 8-byte error code structure that provides feedback on error occurred. If an error does occur, you are not able to d

cifics of the problem.

ŸDefine a 16-byte error code structure that allows you to deter

exists and to	access	the	exception message ID. The exception me
are the same	as shown	in	“Error Messages” on page 3-36.

ŸDefine a larger than 16-byte error code structure that provides

mation	as	described		in the previous		two	error	code structures		a
or all of the exception					data. The exception data is the message
sent	with	the	exception		message. Because		the	vast	majority of	e
sages do not have more					than 512 bytes of message data, a 600-by
code	structure		would	be	adequate for almost			all cases.
Note: Lengths		of 1	through		7 bytes are	not	valid	for	the error	cod

Chapter 3. Common Information across APIs—Basic (OPM) 3-Example11