1 | Message information | Output | Char(*) |
2 | Length of message information | Input | Binary(4) |
3 | Format name | Input | Char(8) |
4 | Message identifier | Input | Char(7) |
5 | Qualified message file name | Input | Char(20) |
6 | Replacement data | Input | Char(*) |
7 | Length of replacement data | Input | Binary(4) |
8 | Replace substitution values | Input | Char(10) |
9 | Return format control characters | Input | Char(10) |
10 | Error code | I/O | Char(*) |
11 | Retrieve Option | Input | Char(10) |
12 | CCSID to convert to | Input | Binary(4) |
13 | CCSID of replacement data | Input | Binary(4) |
The Retrieve Message (QMHRTVM) API retrieves the message description of a predefined message. The message description is created with the Add Message Description (ADDMSGD) command. It consists of the text of the message and other information, such as the message help and the default reply for the message. You can use the QMHRTVM API to copy the text of predefined messages into a program.
Retrieving a message is not the same as receiving a message. Retrieving a message with this API returns the message and associated information stored in the message file. In contrast, receiving a message with the Receive Nonprogram Message (QMHRCVM) or Receive Program Message (QMHRCVPM) API focuses on the message as it is sent to a particular user or program at a particular time. The information returned from the QMHRCVM or the QMHRCVPM API includes details about who sent the message, when it was sent, why it was sent, and so on.
The variable that receives information returned, in the format specified in the format name parameter, of the length specified in the length of message information parameter. If the user is retrieving the next message of the last message of a message file or the first message of an empty message file, blanks are returned for the message information field.
The size of the area to contain the message information, in bytes. The minimum size is 8.
This parameter must specify the size of the variable you use for the message information parameter. If this parameter specifies a longer size, other parts of storage could be overwritten when the API returns the information.
The API returns as much information as it can fit in this length. If the available message information is longer, it is truncated. If the available message information is shorter, the unused output area is unchanged; whatever is already stored in that space remains there.
To determine how much information the API actually returns in response to this call, see the bytes returned field in the message information format. To determine how much information the API could return if space were available, see the bytes available field.
The format to use for the message information. Specify one of these format names:
RTVM0100 | Brief message information. For details, see RTVM0100 Format. |
RTVM0200 | Similar to RTVM0100 plus message severity, alert index, alert option, log indicator, and default reply. For details, see RTVM0200 Format. |
RTVM0300 | Similar to RTVM0200 plus the message ID, CCSID information, and the replacement text formats. For details, see RTVM0300 Format. |
RTVM0400 | All message information. For details, see RTVM0400 Format. |
The identifying code for the predefined message being retrieved. If the retrieve option parameter is *FIRST, this field is ignored and the first alphabetical message is retrieved from the message file.
The name of the message file from which to retrieve the message information and the library in which it resides. The first 10 characters specify the file name; thesecond 10 characters specify the library. You can use these special values for the library name:
*CURLIB | The job's current library |
*LIBL | The library list |
The values to insert in the substitution variables in the predefined message and message help.
If you use blanks for this parameter, blanks are inserted for the substitution variables.
If this parameter contains pointer data, each pointer must start on a 16-byte boundary to keep the data accurate.
The length of the replacement data parameter, in bytes. Valid values are 0 through 32767.
Whether to replace the substitution variables with the values given in the replacement data parameter. Specify one of these values:
*NO | Do not use the replacement data. Instead, return the substitution variable numbers (that is, &1, &2, and so on) in the message text. |
*YES | Use the replacement data in the message text. If you specified blanks in the replacement data parameter, blanks are used for the substitution variables. |
Whether or not the format control characters are returned in the message help output field. Specify one of these values:
*NO | Do not return the format control characters in the text. |
*YES | Return the format control characters in the text. |
Three format control characters can be returned within the message. They are defined in the online help of the Add Message Description (ADDMSGD) command to have these meanings:
&N | Forces the text to a new line (column 2). If the text is longer than one line, the next lines are indented to column 4 until the end of text or another format control character is found. |
&P | Forces the text to a new line indented to column 6. If the text is longer than one line, the next lines start in column 4 until the end of text or another format control character is found. |
&B | Forces the text to a new line, starting in column 4. If the text is longer than one line, the next lines are indented to column 6 until the end of text or another format control character is found. |
The structure in which to return error information. For the format of the structure, see Error Code Parameter.
If this parameter is not used, it is defaulted to *MSGID. The following options are allowed:
*MSGID | Retrieve the message description specified by the message ID parameter. This is the default value of this parameter. |
*NEXT | Retrieve the next message description in the message file that is after the message description specified on the message ID parameter. |
*FIRST | Retrieve the first message description of the message file. Note that if *FIRST is specified for this parameter, the message ID parameter is ignored. |
Note: Although the last 4 characters of a message identifier can be thought of as 4 hexadecimal numbers, the values 'A' through 'F' are treated as characters when sorting. For example, CPFAAAA is listed before CPF0001.
The coded character set identifier (CCSID) in which you want your message text returned. This only applies to text returned in the message and message help fields. The following values are allowed:
0 | The retrieved message description is converted to
the CCSID of the job. This is the default value if this parameter is not
specified.
If the job is 65535 and the text or data is something other than EBCDIC single byte or EBCDIC mixed, the text and data are converted to the default job CCSID. |
65535 | The retrieved message description will not be converted before it is returned. |
CCSID | A valid CCSID in which you want your message text
returned. The CCSID must be between 1 and 65535. The CCSID will be validated by
this API.
Only CCSIDs that a job can be changed to are accepted. For a list of valid job CCSIDs, prompt the CCSID parameter on the Change Job (CHGJOB) CL command. |
Note: If the text contains substitution variables, only the substitution variables that are *CCHAR type data are converted to this CCSID. All other message data is not converted before being returned.
The coded character set identifier (CCSID) that the supplied replacement data is in. This only applies to parts of the replacement data that are defined as *CCHAR. The *CCHAR data is converted from this CCSID to the CCSID in which you want all your text converted. The following values are allowed:
0 | The replacement data is assumed in the CCSID of the job. This is the default value if this parameter is not specified. |
65535 | The replacement data will not be converted. |
CCSID | Specifies a valid CCSID that your replacement data is in. The CCSID must be between 1 and 65535. The CCSID is validated by this API. For a list of valid CCSIDs, see CCSIDs: Message Support in the Globalization topic. |
The following table lists the fields in the RTVM0100 format. For more information about each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | BINARY(4) | Bytes returned |
4 | 4 | BINARY(4) | Bytes available |
8 | 8 | BINARY(4) | Length of message returned |
12 | C | BINARY(4) | Length of message available |
16 | 10 | BINARY(4) | Length of message help returned |
20 | 14 | BINARY(4) | Length of message help available |
24 | 18 | CHAR(*) | Message |
The offset to this field equals the last offset identified plus the length of the previous variable length fields. | CHAR(*) | Message help |
The following table lists the fields in the RTVM0200 format. For more information about each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | BINARY(4) | Bytes returned |
4 | 4 | BINARY(4) | Bytes available |
8 | 8 | BINARY(4) | Message severity |
12 | C | BINARY(4) | Alert index |
16 | 10 | CHAR(9) | Alert option |
25 | 19 | CHAR(1) | Log indicator |
26 | 1A | CHAR(2) | Reserved |
28 | 1C | BINARY(4) | Length of default reply returned |
32 | 20 | BINARY(4) | Length of default reply available |
36 | 24 | BINARY(4) | Length of message returned |
40 | 28 | BINARY(4) | Length of message available |
44 | 2C | BINARY(4) | Length of message help returned |
48 | 30 | BINARY(4) | Length of message help available |
52 | 34 | CHAR(*) | Default reply |
The offset to this field equals the last offset identified plus the length of the previous variable length fields. | CHAR(*) | Message | |
CHAR(*) | Message help |
The following table lists the fields in the RTVM0300 format. For more information about each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | BINARY(4) | Bytes returned |
4 | 4 | BINARY(4) | Bytes available |
8 | 8 | BINARY(4) | Message severity |
12 | C | BINARY(4) | Alert index |
16 | 10 | CHAR(9) | Alert option |
25 | 19 | CHAR(1) | Log indicator |
26 | 1A | CHAR(7) | Message ID |
33 | 21 | CHAR(3) | Reserved |
36 | 24 | BINARY(4) | Number of substitution variable formats |
40 | 28 | BINARY(4) | CCSID conversion status indicator of text |
44 | 2C | BINARY(4) | CCSID conversion status indicator of replacement data |
48 | 30 | BINARY(4) | CCSID of text returned |
52 | 34 | BINARY(4) | Offset of default reply |
56 | 38 | BINARY(4) | Length of default reply returned |
60 | 3C | BINARY(4) | Length of default reply available |
64 | 40 | BINARY(4) | Offset of message |
68 | 44 | BINARY(4) | Length of message returned |
72 | 48 | BINARY(4) | Length of message available |
76 | 4C | BINARY(4) | Offset of message help |
80 | 50 | BINARY(4) | Length of message help returned |
84 | 54 | BINARY(4) | Length of message help available |
88 | 58 | BINARY(4) | Offset of substitution variable formats |
92 | 5C | BINARY(4) | Length of substitution variable formats returned |
96 | 60 | BINARY(4) | Length of substitution variable formats available |
100 | 64 | BINARY(4) | Length of substitution variable format element |
104 | 68 | CHAR(*) | Reserved |
The offsets to these fields are specified in the previous offset variables. | CHAR(*) | Default reply | |
CHAR(*) | Message | ||
CHAR(*) | Message help | ||
CHAR(*) | Substitution variable formats |
The following table lists the fields in the RTVM0400 format. For more information about each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | BINARY(4) | Bytes returned |
4 | 4 | BINARY(4) | Bytes available |
8 | 8 | BINARY(4) | Message severity |
12 | C | BINARY(4) | Alert index |
16 | 10 | CHAR(9) | Alert option |
25 | 19 | CHAR(1) | Log indicator |
26 | 1A | CHAR(7) | Message ID |
33 | 21 | CHAR(3) | Reserved |
36 | 24 | BINARY(4) | Number of substitution variable formats |
40 | 28 | BINARY(4) | CCSID conversion status indicator of text |
44 | 2C | BINARY(4) | CCSID conversion status indicator of replacement data |
48 | 30 | BINARY(4) | CCSID of text returned |
52 | 34 | BINARY(4) | Offset of default reply |
56 | 38 | BINARY(4) | Length of default reply returned |
60 | 3C | BINARY(4) | Length of default reply available |
64 | 40 | BINARY(4) | Offset of message |
68 | 44 | BINARY(4) | Length of message returned |
72 | 48 | BINARY(4) | Length of message available |
76 | 4C | BINARY(4) | Offset of message help |
80 | 50 | BINARY(4) | Length of message help returned |
84 | 54 | BINARY(4) | Length of message help available |
88 | 58 | BINARY(4) | Offset of substitution variable formats |
92 | 5C | BINARY(4) | Length of substitution variable formats returned |
96 | 60 | BINARY(4) | Length of substitution variable formats available |
100 | 64 | BINARY(4) | Length of substitution variable format element |
104 | 68 | CHAR(10) | Reply type |
114 | 72 | CHAR(2) | Reserved |
116 | 74 | BINARY(4) | Maximum reply length |
120 | 78 | BINARY(4) | Maximum reply decimal positions |
124 | 8C | BINARY(4) | Offset of valid reply value entries |
128 | 80 | BINARY(4) | Number of valid reply values entries returned |
132 | 84 | BINARY(4) | Length of valid reply value entries returned |
136 | 88 | BINARY(4) | Length of valid reply value entries available |
140 | 8C | BINARY(4) | Length of valid reply value entry |
144 | 90 | BINARY(4) | Offset of special reply value entries |
148 | 94 | BINARY(4) | Number of special reply values returned |
152 | 98 | BINARY(4) | Length of special reply value entries returned |
156 | 9C | BINARY(4) | Length of special reply value entries available |
160 | A0 | BINARY(4) | Length of special reply value entry |
164 | A4 | BINARY(4) | Offset of lower range reply value |
168 | A8 | BINARY(4) | Length of lower range reply value returned |
172 | AC | BINARY(4) | Length of lower range reply value available |
176 | B0 | BINARY(4) | Offset of upper range reply value |
180 | B4 | BINARY(4) | Length of upper range reply value returned |
184 | B8 | BINARY(4) | Length of upper range reply value available |
188 | BC | BINARY(4) | Offset of relational test entry |
192 | C0 | BINARY(4) | Length of relational test entry returned |
196 | C4 | BINARY(4) | Length of relational test entry available |
200 | C8 | CHAR(7) | Message creation date |
207 | CF | CHAR(1) | Reserved |
208 | D0 | BINARY(4) | Message creation level number |
212 | D4 | CHAR(7) | Message modification date |
219 | DB | CHAR(1) | Reserved |
220 | DC | BINARY(4) | Message modification level number |
224 | E0 | BINARY(4) | Stored CCSID of message |
228 | E4 | BINARY(4) | Offset of dump list entries |
232 | E8 | BINARY(4) | Number of dump list entries returned |
236 | EC | BINARY(4) | Length of dump list entries returned |
240 | F0 | BINARY(4) | Length of dump list entries available |
244 | F4 | CHAR(10) | Default program name |
254 | FE | CHAR(10) | Default program library name |
The offsets to these fields are specified in the previous offset variables. | CHAR(*) | Default reply | |
CHAR(*) | Message | ||
CHAR(*) | Message help | ||
CHAR(*) | Substitution variable formats | ||
CHAR(*) | Valid reply value entries | ||
CHAR(*) | Special reply value entries | ||
CHAR(*) | Lower range reply value | ||
CHAR(*) | Upper range reply value | ||
CHAR(*) | Relational test entry | ||
CHAR(*) | Dump list entries |
The following table lists the fields in the Relational Test Entry format. For more information about each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | CHAR(10) | Relational operator |
10 | A | CHAR(2) | Reserved |
12 | C | BINARY(4) | Length of relational value |
16 | 10 | CHAR(*) | Relational value |
The following table lists the fields in the Special Reply Value Entry format. For more information about each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | CHAR(32) | From-value |
32 | 20 | CHAR(32) | To-value |
The following table lists the fields in the Substitution Variable format. For more information about each field,see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | BINARY(4) | Length of replacement data for substitution variable |
4 | 4 | BINARY(4) | Field size or decimal positions |
8 | 8 | CHAR(10) | Substitution variable type |
18 | 12 | CHAR(*) | Reserved |
The following table lists the fields in the Valid Reply Entry format. For more information about each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | CHAR(32) | Valid reply value |
This section describes the fields returned in further detail. The fields are listed in alphabetical order.
Alert index. The format number for the message data field. This number is also called the resource name variable. For more information, see the Alerts Support book.
Alert option. Whether and when an SNA alert is created and sent for the message. Valid values follow:
*DEFER | An alert is sent after local problem analysis. |
*IMMED | An alert is sent immediately when the message is sent to a message queue that has the allow alerts attribute set to *YES. |
*NO | No alert is sent. |
*UNATTEND | An alert is sent immediately when the system is running in unattended mode (when the value of the alert status network attribute, ALRSTS, is *UNATTEND). |
For more information, see the Alerts Support book.
Bytes available. The length of all available information about the format. Bytes available can be greater than the length specified in the APIs length of message information parameter. If it is greater, the information returned is truncated.
Bytes returned. The length of all information returned in the format. The value of the bytes returned field is always less than or equal to the value of the length of message information parameter, and less than or equal to the bytes available. If the bytes returned value is less than the length of message information value, the unused space is unchanged.
CCSID conversion status indicator of replacement data. This value indicates the status of any CCSID conversion that may have occurred when inserting the replacement data into the message description. The following values may be returned:
0 | No conversion was needed because the CCSID of the data matched the CCSID you wanted the data converted to. |
1 | No conversion occurred because either the data was 65535 or the CCSID you wanted the data converted to was 65535. |
2 | No conversion occurred because you did not supply enough space for the data or the replacement data did not contain any *CCHAR type substitution variables. |
3 | The data was converted to the CCSID specified using the best fit conversion tables. |
4 | A conversion error occurred using the best fit conversion tables so a default conversion was attempted. This completed without error. |
-1 | An error occurred on both the best fit and default conversions. The data was not converted. |
CCSID conversion status indicator of text. This value indicates the status of any CCSID conversion that may have occurred when retrieving the message description from the message file. The following values may be returned:
0 | No conversion was needed because the CCSID of the text matched the CCSID you wanted the text converted to. |
1 | No conversion occurred because either the text was 65535 or the CCSID you wanted the text converted to was 65535. |
2 | No conversion occurred because you did not supply enough space for the text. |
3 | The text was converted to the CCSID specified using the best fit conversion tables. |
4 | A conversion error occurred using the best fit conversion tables so a default conversion was attempted. This completed without error. |
-1 | An error occurred on the best fit conversion. The text was not converted. |
CCSID of text returned. The coded character set identifier in which the text of the message description is returned.
Note: If a conversion error occurs or if the CCSID you requested the text to be converted to is 65535, the CCSID that the message description is stored in is returned. Otherwise the CCSID you wanted your text converted to is returned. If you do not want the text converted before it is returned but you do want to know the CCSID that the message description is stored in, specify 65535 on the coded character set identifier to convert to parameter. The CCSID the message description is stored in is returned in the coded character set identifier or text returned field.
The CCSID returned in the coded character set identifier for text returned may not apply to the replacement data substituted in the text returned. Only the *CCHAR substitution variables are converted to the CCSID specified. The rest of the replacement data is not converted before it is returned. Also, if an error occurred trying to convert the replacement data from the CCSID of the message data to the CCSID to convert to, the replacement data would not be converted before it is returned.
Default program library name. The library specified for the default program. This can be the actual library name, *LIBL, or *CURLIB.
Default program name. The name of the program called to take default action if this message is sent as an escape message to a program or procedure that is not monitoring for it.
Default reply. The default reply for the message identifier retrieved.
Dump list entry. Each dump list entry is a BINARY(4) value that specifies data to be dumped when the message is sent as an escape message to a program that is not monitoring for it. The following values may be returned:
1-99 | The number of the message data field that is to be dumped. |
-1 | The data areas of the job are dumped as specified by the Dump Job (DMPJOB) command. This corresponds to the special value *JOBDMP that can be specified in the DMPLST parameter of the ADDMSGD and CHGMSGD commands. |
-2 | The internal machine data structures related to the machine process in which the job is running are dumped to the machine error log. This corresponds to the special value *JOBINT that can be specified in the DMPLST parameter of the ADDMSGD and CHGMSGD commands. |
-4 | The job information produced by the Display Job (DSPJOB) command is printed. This corresponds to the special value *JOB that can be specified in the DMPLST parameter of the ADDMSGD and CHGMSGD commands. |
Field size or decimal positions. This value is used in one of two ways, depending on the substitution variable type.
From-value. The from-value in a special reply value entry. This is a value that can be entered as a reply to the message even though it may not meet the other reply validity checking specifications. It will be accepted and converted to a valid response specified in the to-value.
Length (general information about the following length fields). These formats use two types of length fields, each related to a single variable length text field. (The variable length text fields return information to the caller.) The first type of length field is returned length; the second is available length. Returned length is the actual length of the text in the variable length text field. Available length is the length of the text before it is placed in the variable length text field. It is always greater than or equal to the returned length. If the available length equals the returned length, all the message information is returned. If the text is truncated when placed in the variable length field, the available length is greater than the returned length by the number of characters truncated.
Length of default reply available. The length of the available default reply, in bytes.
Length of default reply returned. The length of the returned default reply, in bytes.
Length of dump list entries available. The length of the available dump list entries, in bytes.
Length of dump list entries returned. The length of the available dump list entries that were actually returned, in bytes.
Length of lower range reply value available. The length of the available lower range reply value, in bytes.
Length of lower range reply value returned. The length of the returned lower range reply value, in bytes.
Length of message available. The length of the available message text, in bytes.
Length of message help available. The length of the available help information for the message, in bytes.
Length of message help returned. The length of the returned help information for the message, in bytes.
Length of message returned. The length of the returned message text, in bytes.
Length of relational test entry available. The length of the available relational test entry, in bytes.
Length of relational test entry returned. The length of the returned relational test entry, in bytes.
Length of relational value. The length of the value to be compared to the reply entered for a relational test entry, in bytes.
Length of replacement data for substitution variable. The number of characters or digits that are needed in the message replacement data for this substitution variable. The value returned is dependant on the substitution variable type and length:
Length of special reply value entriesavailable. The total length in bytes of all the available special reply value entries.
Length of special reply value entries returned. The length in bytes of the special reply value entries that were actually returned.
Length of special reply value entry. The length of the special reply value entry, in bytes.
Length of substitution variable format element. The length in bytes of each substitution variable format element.
Length of substitution variable formats available. The total length in bytes of all the available substitution variable formats.
Length of substitution variable formats returned. The length in bytes of the substitution variable formats that were actually returned.
Length of upper range reply value available. The length of the available upper range reply value, in bytes.
Length of upper range reply value returned. The length of the returned upper range reply value, in bytes.
Length of valid reply value entries available. The total length in bytes of all the available valid reply value entries.
Length of valid reply value entries returned. The length in bytes of the valid reply value entries that were actually returned.
Length of valid reply value entry. The length of the valid reply value entry, in bytes.
Log indicator. The log problem indicator for the message retrieved. Possible values follow:
N | Problems are not logged. |
Y | Problems are logged. |
Lower range reply value. The lower value limit for the valid reply.
Maximum reply decimal positions. The maximum number of decimal positions allowed in the message reply.
Maximum reply length. The maximum length of a reply to an inquiry or notify message.
Message. The text of the message retrieved.
Message creation date. The date this the message was created, in CYYMMDD format.
Message creation level number. The level number of this message. This will be a value from 1 to 99.
Message help. The message help for the message retrieved.
Message ID. The message ID of the message retrieved.
Message modification date. The date this message was modified, in CYYMMDD format.
Message modification level number. The modification level number of this message. This will be a value from 1 to 99.
Message severity. The severity of the message retrieved.
Number of dump list entries returned. The number of dump list entries that were returned in the message information format. The dump list entry field is repeated once for each dump list entry.
Number of special reply values returned. The number of special reply values that were returned in the message information format. The special reply value entry field structure is repeated once for each special reply value.
Number of substitution variable formats. The number of substitution variables in the message description. The substitution variable formats field structure is repeated once for each substitution variable in the message.
Number of valid reply values returned. The number of valid reply values that were returned in the message information format. The valid reply value entry field structure is repeated once for each valid reply value.
Offset of default reply. The offset of the default reply, in bytes.
Offset of dump list entries. The offset of the dump list entries, in bytes.
Offset of lower range reply value. The offset of the lower range reply value, in bytes.
Offset of message. The offset of the first-level message, in bytes.
Offset of message help. The offset of the second-level message, in bytes.
Offset of relational test entry. The offset of the relational test entry, in bytes.
Offset of special reply value entries. The offset of the special reply value entries, in bytes.
Offset of substitution variable formats. The offset in bytes to the substitution variable formats.
Offset of upper range reply value. The offset of the upper range reply value, in bytes.
Offset of valid reply value entries. The offset of the valid reply value entries, in bytes.
Relational operator. The relational operator for a relational test entry. This value is one of the following:
*LT | Less than |
*LE | Less than or equal to |
*GT | Greater than |
*GE | Greater than or equal to |
*EQ | Equal to |
*NE | Not equal to |
Relational test entry. The relational test for the reply value that is defined in the message description. For more information, see Relational Test Entry.
Relational value. The value to be compared to the reply entered for a relational test entry.
Reply type. The type of valid values that can be made to an inquiry or notify message. One of the following values will be returned:
*CHAR | Any character string is valid. If it is a quoted character string, the apostrophes are passed as part of the character string. |
*NONE | No reply type is specified. |
*DEC | Only a decimal number is a valid reply. |
*ALPHA | Only an alphabetic string is valid. Blanks are not allowed. |
*NAME | Only a simple name is a valid reply. The name does not have to be an object name, but it must start with an alphabetic character; the remaining characters must be alphanumeric. |
Reserved. An ignored field.
Special reply value entries. Each special reply value that is defined in the message description is returned in a special reply value entry. For more information, see Special Reply Value Entry.
Stored CCSID of message. The CCSID that was specified for the message. For messages created on a release prior to V3R1 the value 65535 will be returned.
Substitution variable formats. Each substitution variable that is defined in the message description is returned in a substitution variable format. For more information, see Substitution Variable Format.
Substitution variable type. The type of data the substitution variable contains and how the data is formatted when substituted into the returned message text. The value is one of the following types:
*QTDCHAR | A character string formatted with enclosing apostrophes ('Monday, the 1st'). |
*CHAR | A character string formatted without enclosing apostrophes. |
*CCHAR | A convertible character string. |
*HEX | A string of bytes formatted as a hexadecimal value (X'C0F4'). |
*SPP | A 16-byte space pointer to data in a space object. |
*DEC | A packed decimal number that is formatted in the message as a signed decimal value with a decimal point. |
*BIN | A binary value that is 2, 4, or 8 bytes long (B'0000 0000 0011 1010') and is formatted in the message as a signed decimal value (58). |
*UBIN | A binary value that is 2, 4 or 8 bytes long (B'0000 0000 0011 1010') and is formatted in the message as an unsigned decimal value (58). |
*DTS | An 8-byte field that contains a system date/time stamp. The date/time stamp contains the date followed by one blank separator and then the time. |
*SYP | A 16-byte system pointer to a system object. |
*ITV | An 8-byte binary field that contains the time interval (in seconds) for wait time-out conditions. |
To-value. The to-value in a special reply value entry. This is the value that will be used as the reply value when the value entered matches the from-value.
Upper range reply value. The upper value limit for the valid reply.
Valid reply entries. Each valid reply value that is defined in the message description is returned in a valid reply value entry. For more information, see Valid Reply Entry.
Valid reply value. The valid reply value in a valid reply value entry.
Message ID | Error Message Text |
---|---|
CPF24AA E | Value for replace substitution variables not valid. |
CPF24AB E | Value for return format control characters not valid. |
CPF24A7 E | Value for the length of message information not valid. |
CPF24B4 E | Severe error while addressing parameter list. |
CPF24B6 E | Length of &1, not valid for message text or data. |
CPF2401 E | Not authorized to library &1. |
CPF2407 E | Message file &1 in &2 not found. |
CPF2411 E | Not authorized to message file &1 in &2. |
CPF2419 E | Message identifier &1 not found in message file &2 in &3. |
CPF2465 E | Replacement text of message &1 in &2 in &3 not valid for format specified. |
CPF247E E | CCSID &1 is not valid. |
CPF247F E | Retrieve option &1 not valid. |
CPF2499 E | Message identifier &1 not allowed. |
CPF2531 E | Message file &1 in &2 damaged for &3. |
CPF2548 E | Damage to message file &1 in &2. |
CPF3CF1 E | Error code parameter not valid. |
CPF3C21 E | Format name &1 is not valid. |
CPF3C36 E | Number of parameters, &1, entered for this API was not valid. |
CPF3C90 E | Literal value cannot be changed. |
CPF8100 E | All CPF81xx messages could be returned. xx is from 01 to FF. |
CPF9830 E | Cannot assign library &1. |
CPF9872 E | Program or service program &1 in library &2 ended. Reason code &3. |
Top | Message Handling APIs | APIs by category |