17.08.2013 Views

System i: Programming Message Handling APIs - IBM

System i: Programming Message Handling APIs - IBM

System i: Programming Message Handling APIs - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Value <strong>Message</strong> Type<br />

02 Diagnostic<br />

04 Informational<br />

05 Inquiry<br />

06 Sender’s copy<br />

08 Request<br />

10 Request with prompting<br />

14 Notify, exception already handled when API is called<br />

15 Escape, exception already handled when API is called<br />

16 Notify, exception not handled when API is called<br />

17 Escape, exception not handled when API is called<br />

21 Reply, not checked for validity<br />

22 Reply, checked for validity<br />

23 Reply, message default used<br />

24 Reply, system default used<br />

25 Reply, from system reply list<br />

26 Reply, from exit program<br />

<strong>Message</strong> with replacement data. The text of a predefined message with the replacement data included. If<br />

an impromptu message is listed, this field contains the impromptu message text.<br />

Microseconds. The microseconds part of the time sent.<br />

Number of fields returned. The number of identifier fields returned to the application.<br />

Number of fields to return. The number of fields to return in the LJOB0100 format (the number of<br />

entries in the identifiers of fields to return array).<br />

Number of fields to return specified. The number of identifier fields to return as specified on the call to<br />

the API.<br />

Number of receiving statement numbers or instruction numbers available followed by an array of the<br />

receiving statement numbers. The number of statement numbers or instruction numbers available for the<br />

receiving program or procedure.<br />

For OPM programs and nonoptimized procedures, this count is 1.<br />

For optimized procedures, this count can be greater than 1. In this case, each statement number<br />

represents a potential point at which the message could have been received. If the mapping table<br />

information has been removed from the program, this field returns a count of 0 and no statement<br />

numbers are available. The array of receiving statement numbers or instruction numbers immediately<br />

follows this field in the returned data.<br />

Number of sending statement numbers or instruction numbers available followed by an array of the<br />

sending statement numbers or instruction numbers. The number of statement numbers or instruction<br />

numbers available for the sending program or procedure.<br />

For OPM programs and nonoptimized procedures, this count is 1.<br />

For optimized procedures, this count can be greater than 1. In this case, each statement number<br />

represents a potential point at which the message could have been sent. If the mapping table information<br />

has been removed from the program, this field returns a count of 0, and no statement numbers are<br />

available. The array of sending statement numbers or instruction numbers immediately follows this field<br />

in the returned data.<br />

<strong>Message</strong> <strong>Handling</strong> <strong>APIs</strong> 25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!