Add Problem Selection Entry (ADDPRBSLTE)

Where allowed to run: All environments (*ALL)
Threadsafe: No

The Add Problem Selection Entry (ADDPRBSLTE) command allows you to define selection criteria that categorize a group of problem log entries. You can add a problem log selection entry to a problem log filter that was created using the Create Filter (CRTFTR) command.

Top

Parameters

Keyword	Description	Choices	Notes
FILTER	Filter	Qualified object name	Required, Positional 1
	Qualifier 1: Filter	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
SELECT	Selection data	Single values: *ANY Other values (up to 10 repetitions): Element list	Required, Positional 2
	Element 1: Relationship	IF, AND, *OR
	Element 2: Attribute	EVENT, ORIGIN, ORGNETID, ORGCPNAM, RCVNETID, RCVCPNAM, PROBTYPE, SEV, MSGID, ORGHDW, RSCHDW, RSCSFW
	Element 3: Relational operator	EQ, GT, LT, NE, GE, LE, *CT
	Element 4: Value	Character value
SEQNBR	Sequence number	1-9999, *GEN	Optional
GROUP	Group	Name, *DEFAULT	Optional

Top

Filter (FILTER)

Specifies the name of the filter.

This is a required parameter.

Qualifier 1: Filter

name: Specify the name of the filter.

Qualifier 2: Library

*LIBL: All libraries in the library list for the current thread are searched until the first match is found.

*CURLIB: The current library for the job is used to locate the filter. If no library is specified as the current library for the job, the QGPL library is used.
name: Specify the name of the library where the filter is located.

Top

Selection data (SELECT)

Specifies that a problem log entry is selected or not selected based on whether information in the problem log entry satisfies a specified relationship.

You can specify a single value (*ANY) or all four elements that define a relationship. When you specify the four elements, the attribute and attribute value are compared for the relationship specified by the relational operator.

This is a required parameter.

Single values

*ANY: Any problem log entry is selected.

Other values (up to 10 repetitions)

Element 1: Relationship

*IF: The specified relationship must be satisfied for a problem log entry to be selected.
*AND: The specified relationship must be satisfied in addition to the *IF relationship for a problem log entry to be selected.
*OR: The specified relationship must be satisfied in addition to or instead of the *IF relationship for a problem log entry to be selected.

Element 2: Attribute

*EVENT

The filter is applied when the problem log entry is created (a value of 1), changed (a value of 2), or deleted (a value of 3). If the entry has been created and is changed before being committed, use the value of 1.

*ORIGIN

The problem log entry was locally generated (a value of L) or was received from another system (a value of R).

*ORGNETID

The network identifier (ID) of the system in which the problem log entry originated is specified. This information is displayed using the Work with Problems (WRKPRB) command which shows the details for a specific problem. Specify the value in the following form:

'nnnnnnnnnn'

*ORGCPNAM

The control point name of the system in which the problem log entry originated is specified. This information is displayed using the Work with Problems (WRKPRB) command which shows the details for a specific problem. Specify the value in the following form:

'cccccccccc'

*RCVNETID

The network identifier of the remote system from which the problem log entry was received is specified. This information is displayed using the Work with Problems (WRKPRB) command which shows the details for a specific problem. Specify the value on the following form:

'nnnnnnnnnn'

*RCVCPNAM

This attribute specifies the Remote System Control Point name in which the problem log entry received from. This information is displayed using the Work with Problems (WRKPRB) command and shows the details for a specific problem. The value specified for this attribute should be of the following form:

'cccccccccc'

*PROBTYPE

The type of problem entry created. Possible problems are machine-detected (a value of 1), user-detected (a value of 2), PTF order (a value of 3), application-detected (a value of 4), Client machine-detected (a value of 5), or Client user-detected (a value of 6).

Note: User-Detected Remote Hardware problems are grouped with number 2 User-Detected problems.

*SEV

The severity of the problem log entry created. Possible choices are high (a value of 1), medium (a value of 2), low (a value of 3), none (a value of 4), or not assigned (a value of 5).

Note: Problems do not have a severity level when locally created.

*MSGID

The message ID found in the problem log entry. This is usually an i5/OS message ID.

*ORGHDW

The origin hardware resource information in the problem log entry. This information is displayed using the Work with Problems (WRKPRB) command and shows the details for a specific problem. Specify the value in the following form:

'tttt mmm ss-sssssss'
'tttt mmm ss-sssss'
'tttt mmm sssssss'
'tttt mmm sssss'

where tttt is the machine type, mmm is the model number and sssssssss is the serial number. Use this exact format to match a particular hardware resource exactly, or use a part of the hardware value with the Contains (*CT) relation to provide a partial match.

*RSCHDW

The failing hardware resource information in the problem log entry. This information is displayed using the Work with Problems (WRKPRB) command and shows the details for a specific problem. Specify the value in the following form:

'tttt mmm ss-sssssss'
'tttt mmm ss-sssss'
'tttt mmm sssssss'
'tttt mmm sssss'

*RSCSFW

The failing software resource information in the problem log entry. This information is displayed using the Work with Problems (WRKPRB) command and shows the details for a specific problem. Specify the value in the following form:

'ppppppp vv rr mm'

where ppppppp is the licensed program ID, vv is the version number, rr is the release number, and mm is the modification level. Use this exact format to match a particular software resource exactly, or use a part of the software value with the Contains (*CT) relation to provide a partial match.

Element 3: Relational operator

The value specified for element 2 (Attribute) must have the following relationship to value specfied for element 4 (Value) of this parameter.

*EQ: Equal to
*GT: Greater than
*LT: Less than
*NE: Not equal to
*GE: Greater than or equal to
*LE: Less than or equal to
*CT: Contains

Element 4: Value

attribute-value: Specify a value of up to 30 characters to compare with the contents of the attribute specified for element 2 of this parameter. The value must be specified in character format and must be enclosed in apostrophes if it contains blanks or special characters. If a CL variable is specified for the value, it must be a character variable.
generic-attribute-value: Specify the generic attribute value. A generic value is a character string of one or more characters followed by an asterisk (*); for example, ABC*. If a generic name is specified, all values that begin with the generic value are selected. If an asterisk is not included with the generic (prefix) value, the system assumes it to be the complete value.

Top

Sequence number (SEQNBR)

Specifies the sequence number of the problem log selection entry. Selection entries in a filter are numbered by sequence number. When a filter is applied, the selection entries are tested in order of ascending sequence number.

*GEN: The system generates the sequence number.
1-9999: Specify a sequence number.

Top

Group (GROUP)

Specifies the group to which a problem log entry is assigned if it matches the criteria specified on the SELECT parameter.

*DEFAULT: The problem log entry is assigned to the default group.
name: Specify the name of the group.

Top

Examples

Example 1: Adding a Selection Entry

ADDPRBSLTE   FILTER(PROBLIB/PROBFILTER)
             SELECT((*IF *EVENT *EQ 1) (*AND *SEV *EQ 1))
             SEQNBR(*GEN)  GROUP(HIGHPROB)

This command adds an entry to the filter PROBFILTER in library PROBLIB. Any problems that have been created and are of severity 1 are assigned to group HIGHPROB.

Example 2: Assigning Entries by Origin System Network ID

ADDPRBSLTE   FILTER(PROBLIB/PROBFILTER)
             SELECT((*IF *ORGNETID *EQ 'IOWA'))  SEQNBR(*GEN)
             GROUP(IOWA)

This command assigns any problems with a origin system network ID of IOWA to group IOWA.

Example 3: Assigning Entries by Problems for Messages

ADDPRBSLTE   FILTER(PROBLIB/PROBFILTER)
             SELECT((*IF *MSGID *EQ 'CPF89*'))  SEQNBR(*GEN)
             GROUP(MSGCPF89)

This command assigns any problems for message CPF8901, CPF8902, and so on, to group MSGCPF89.

Example 4: Assigning Entries by Hardware Problems

ADDPRBSLTE   FILTER(PROBLIB/PROBFILTER)
             SELECT((*IF *RSCHDW *CT 9404)
                    (*OR *RSCHDW *CT 9406)
                    (*OR *RSCHDW *CT 9402))
             SEQNBR(*GEN) GROUP(AS400USER)

All problems for System i5 hardware (the hardware resource information containing machine type 9402, 9404 or 9406) are assigned to group AS400USER.

Caution must be taken when using the contains operation. In this example if the sending machine had a serial number containing 9402, 9404, or 9406 it would also match this selection entry even if the machine type was not 9402, 9404, or 9406. A better example follows.

Example 5: Assigning Entries by Hardware Problems

ADDPRBSLTE   FILTER(PROBLIB/PROBFILTER)
             SELECT((*IF *RSCHDW *EQ 9404*)
                    (*OR *RSCHDW *EQ 9406*)
                    (*OR *RSCHDW *EQ 9402*))
             SEQNBR(*GEN) GROUP(AS400USER)

This command assigns all problems for System i5 hardware (the hardware resource information equals machine type 9402, 9404 or 9406) to group AS400USER.

This is a better way to select on the sending hardware machine type. Only those machines with types of 9402, 9404, or 9406 will result in a match.

Example 6: Assigning Entries by Machine-detected Problems

ADDPRBSLTE   FILTER(PROBLIB/PROBFILTER)
             SELECT((*IF  *PROBTYPE *EQ 1))
             SEQNBR(*GEN)  GROUP(MACHDETECT)

This command assigns any problems that are machine-detected to group MACHDETECT.

Example 7: Assigning Entries by Product-specific Problems

ADDPRBSLTE   FILTER(PROBLIB/PROBFILTER)
             SELECT((*IF *RSCSFW *EQ '5716SS1 03 06 00'))
             SEQNBR(15)  GROUP(OS400V3R6)

This command assigns any problems that are specifically for Operating System Version 3 Release 6 Modification 0 to group OS400V3R6. Notice that this entry is placed after entry number 10 in the filter, since 15 is specified as the sequence number.

Example 8: Assigning Entries by Matching Products

ADDPRBSLTE   FILTER(PROBLIB/PROBFILTER)
             SELECT((*IF *RSCSFW *EQ '5716SS1*'))
             SEQNBR(25)  GROUP(OS400)

This selection entry matches Version 3 Release 6 of the Operating System licensed program.

Notes:

The order of selection entries within a filter is important. When the filter is applied to the problem log entry, the selection entries are examined from the first entry to the last entry in ascending order. The first selection entry that matches a problem is used. To ensure correct operation the most specific selection entries should be first, and the least specific selection entries last.
If the selection entries are not order specific (i.e. each selection entry matches one and only one problem) then the most likely or the most common should be placed first. This will ensure the best performance as fewer selection entries will need to be checked.
If no selection entries result in a match when a filter is applied, then the *LAST selection entry is used to assign a group. The *LAST selection entry is automatically added to the filter when it is created. The SELECT parameter for the *LAST selection entry is *ANY, which will always result in a match.
The *AND logical operator takes precedence over the *OR logical operator within a selection entry. Therefore, the following SELECT specification:
```
((*IF *PROBTYPE *EQ 1) (*AND *SEV *EQ 1)
(*OR *PROBTYPE *EQ 2) (*AND *SEV *EQ 1))
```
is equivalent to the following Boolean expression:
```
if ((*PROBTYPE = 1) and (*SEV = 1)) or
((*PROBTYPE = 2) and (*SEV = 1))
```
All attribute values are interpreted as character data, including numbers. When the problem filter is applied to a problem, the system converts all of the data in the filter to the type given in the problem template and compared. Message IDs are considered character data and are ordered as such.

Top

Error messages

*ESCAPE Messages

CPF2150: Object information function failed.
CPF2151: Operation failed for &2 in &1 type *&3.
CPF7A82: Error occurred while applying the problem filter.
CPF812F: Filter damaged.
CPF91DA: Sequence number &4 already exists.
CPF91DE: Filter &1/&2 at maximum size.
CPF91D9: Sequence number cannot be automatically created.
CPF91EA: *IF relationship not in correct position.
CPF91EB: Filter type &3 not correct for this operation.
CPF91EC: Internal processing error occurred.
CPF91E6: Generic values only allowed with *EQ or *NE.
CPF91E7: Character in position &4 not valid in value specified.
CPF91E8: Internal processing error occurred.
CPF9802: Not authorized to object &2 in &3.
CPF9803: Cannot allocate object &2 in library &3.
CPF9807: One or more libraries in library list deleted.
CPF9808: Cannot allocate one or more libraries on library list.

Top