DSPPRB

DSPPRB (Display Problem)

DSPPRB Command syntax diagram

Purpose

The Display Problem (DSPPRB) command shows or print service information related to performing hardware and software maintenance. The service information, contained in the problem log entries, are shown on the DSPPRB display, printed with the job's output, or stored in a database file.

Optional Parameters

PRBID

Specifies the problem identifier of the problem being selected. Problems with different system origins can have the same identifier. This parameter can be used with the ORIGIN parameter to select a single problem from a particular system origin.
*ALL: All problem identifiers are selected.
problem-identifier: Specify the 10-character problem identifier of the problem being selected.

STATUS

Specifies the status of the problem log entries. The seven status types are as follows:

*OPENED

The problem is in OPENED status. The problem has been identified and a problem record has been created.

*READY

The problem is in READY status. Problem analysis information has been added to the problem record.

*PREPARED

The problem is in PREPARED status. The problem has been prepared for reporting.

*SENT

The problem is in SENT status. The problem has been sent to a service provider, but no answer has been returned.

*ANSWERED

The problem is in ANSWERED status. An answer was returned by the service provider or added by an operator on this system.

*VERIFIED

The problem is in VERIFIED status. The problem has been resolved and the system operator has verified that the problem has been corrected.

*CLOSED

The problem is closed.

*ALL: Problem log entries with any status are shown.
status-type: Specify up to six status types that identify the problem log entries being displayed.

SEV

Specifies the severity level of the problem log entries being shown on the display. The severity level is assigned by the user when the problem is prepared for reporting. The four severity levels are:

1

High

2

Medium

3

Low

4

None

*ALL: Problem log entries with any severity level are shown.
severity-level: Specify at least one or as many as three of the four severity levels.

PERIOD

Specifies the period of time for which the data log is printed. The following values can be coded in this parameter, which contains two sets of two values each (four list elements).
Element 1: Starting Time
*AVAIL: The error data that is available for the specified starting or ending date is printed.
start-time: Specify the starting time of the specified starting date for which the error data is printed. The time is specified in 24-hour format with or without a time separator as follows:

With a time separator, specify a string of 5 or 8 digits, where the time separator for the job separates the hours, minutes, and seconds. If you issue this command from the command line, the string must be enclosed in apostrophes. If a time separator other than the separator specified for your job is used, this command fails.

Without a time separator, specify a string of 4 or 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds. Valid values for hh range from 00 through 23. Valid values for mm and ss range from 00 through 59.

Element 2: Starting Date
*BEGIN: The logged data from the beginning of the log is displayed.

Note: If PERIOD(*BEGIN) is specified, then any time value other than *AVAIL for start-time is ignored.

*CURRENT: The logged data for the current day, and the time that has elapsed between the specified starting time and ending time for the day, is displayed.
start-date: Specify the date for which the first logged data is displayed. The date must be entered in the format specified by the system values QDATFMT and, if separators are used, QDATSEP.
Element 3: Ending Time
*AVAIL: The logged data that is available for the specified ending date is displayed.
end-time: Specify the time that the data logging ends. See the description of start-time for details about how time can be specified.
Element 4: Ending Date
*END: The last day on which data was logged is shown. If PERIOD(*END) is specified, a time value other than *AVAIL for end-time is ignored.
*CURRENT: The logged data for the current day, and the time that has elapsed between the specified starting time and ending time for the day, is displayed.
end-date: Specify the date that the data logging ends. The date must be entered in the format specified by the system values QDATFMT and, if separators are used, QDATSEP.

HARDWARE

Specifies the name of the problem log entries identifying the failing device.

Note: If *ALL is specified, then any value other than *ALL for model and serial number is ignored.

Element 1: Machine Type
*ALL: Entries are shown regardless of which device, if any, is identified as failing.
type-code: Specify the 4-character type code of the device.
Element 2: Model Number
*ALL: All entries identifying the specified type of failing device are shown.
model-number: Specify the 3-character model number of the device.
Element 3: Serial Number
*ALL: All entries identifying the specified type and model of the failing device are shown.
serial-number: Specify the serial number of the device in one of the following formats where n is a decimal digit (0-9).

nnnnn

nnnnnnn

nn-nnnnn

nn-nnnnnnn

RESOURCE

Specifies the name of the failing resource, or all failing resources, for which problem log entries are shown.
*ALL: Entries are shown regardless of which resource name, if any, is identified by the problem.
resource-name: Specify the name of the resource for which logged entries are being displayed.

LICPGM

Specifies the name of the failing licensed program for which problem log entries are shown.
Element 1: Licensed Program
*ALL: All licensed programs are shown regardless of whether any are identified as failing.

Note: If *ALL is specified, any value other than *ALL for release and modification is ignored.

licensed-program-name: Specify the name of the failing licensed program.
Element 2: Release Level of the Licensed Program
*ALL: All entries identifying failing licensed programs are shown.
release-level: Specify the release level of the failing licensed program.
Element 3: Modification Number of the Release
*ALL: All entries identifying a failing licensed program of the specified licensed program and release are shown.
modification-number: Specify the modification number of the release of the failing licensed program.

FUNCTION

Specifies the name of the function identifier for which the problem log entries are shown.
*ALL: Entries are shown regardless of which function identifier, if any, is identified.
generic*-function-identifier: Specify the generic name of the function identifier. A generic name is a character string of one or more characters followed by an asterisk (*); for example, ABC*. The asterisk substitutes for any valid characters. A generic name specifies all objects with names that begin with the generic prefix for which the user has authority. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete object name. For more information on the use of generic names, refer to generic names.
function-identifier: Specify the complete function identifier of the function. If blank characters are included, the character string must be enclosed in apostrophes.

PGM

Specifies that only problem log entries identifying the failing program are shown. For machine-detected problems, the failing program is identified by the possible cause with the highest probability of failure.
*ALL: Entries are shown regardless of which program, if any, is identified.
generic*-program-name: Specify the generic name of the program.
program-name: Specify the name of the program.

MSGID

Specifies the message or range of messages for which the problem log entries are shown. This is the problem message identifier shown in the problem details display. For user-detected problems, the message identifier is entered by the user.
*ALL: Entries are shown regardless of which problem message identifier is associated with a problem.
generic*-message-identifier: Specify the generic name of the message identifier.
message-identifier: Specify the problem message identifier.

ORIGIN

Specifies the nodes for which the problem log entries are shown.
Element 1: Network Identifier
*ALL: Entries are shown regardless of the network identifier of the origin system of each entry.
*NETATR: Only entries that originated on systems with the same local network identifier as the one defined in the network attributes for this system are shown.
network-identifier: Specify a network identifier. Only entries originating on systems with this local network identifier are shown.
Element 2: Control Point Name
*ALL: All entries originating on systems using the network identifier are shown.
*NETATR: Only entries originating on systems with the same control point name as the one defined in the network attributes are shown.
control-point-name: Specify the name of the control point. Only entries originating on systems with this control point name are shown.

SRVID

Specifies that only problem log entries using the IBM service-assigned number are shown. This number is assigned when the problem is reported to IBM service support.
*ALL: Entries are shown regardless of which service number, if any, is assigned to the problem.
service-identifier-number: Specify the service identifier number.

ASNUSER

Specifies which problem log entries are displayed.
*ALL: All problem log entries are shown, regardless of the user name assigned to them.
user-name: Specify the user name assigned to the problem log entries to be displayed.

GROUP

Specifies the group in the filter to which the problem is assigned.
*ALL: All problem log entries are shown, regardless of the group assigned to them.
group-name: Specify the 10-character problem filter group assigned to the entry.

Note: The values are blank if problem log filtering is not used.

PRBTYPE

Specifies which type of problems to display.
*ALL: All problem log entries are shown, regardless of the problem type.
1: Only machine-detected problems are shown.
2: Only user-detected problems are shown.
3: Only PTF order problems are shown.
4: Only application-detected problems are shown.
5: Only PC machine-detected problems are shown.
6: Only PC user-detected problems are shown.

PRBCGY

Specifies which category of problems to display.
*ALL: All problems are shown.
*REPORT: Problems that are logged and reported to the service provider are shown.
*CRITICAL: Problems that are critical are shown.
*LOGONLY: Problems that are logged, but not reported to the service provider, are shown.

OUTPUT

Specifies whether the output from the command is shown at the requesting work station, printed with the job's spooled output, or directed to a database file.
More information on this parameter is in commonly used parameters.
*: Output requested by an interactive job is shown on the display. Output requested by a batch job is printed with the job's spooled output.
*PRINT: The output is printed with the job's spooled output.
*OUTFILE: The output is directed to the database file specified on the OUTFILE parameter.

OUTFILE

Specifies the qualified name of the database file that receives the output of the command. If the file does not exist, this command creates a database file in the specified library. If a file is created, the text reads "Outfile for DSPPRB," and the authority for users other than those who have specific authority, group authority, or authority from an authorization list is *EXCLUDE. Refer to the tables at the end of the TYPE parameter description for the format used.

Note: The format must be the same as that of the TYPE parameter.

The name of the database file can be qualified by one of the following library values:

*LIBL: All libraries in the job's library list are searched until the first match is found.

*CURLIB: The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.

library-name: Specify the name of the library to be searched.

database-file-name: Specify the name of the database file to which the output of the command is written.

OUTMBR

Specifies the name of the database file member to which the output is directed.
Element 1: Member to Receive Output
*FIRST: The first member in the file receives the output. If OUTMBR(*FIRST) is specified and the member does not exist, the system creates a member with the name of the file specified on the OUTFILE parameter. If the member exists, records may be either added to the end of the member or replace existing records.
member-name: Specify the file member that receives the output. If OUTMBR(member-name) is specified and the member does not exist, the system creates it.
Element 2: Operation to Perform on Member
*REPLACE: The system clears the existing member and adds the new records.
*ADD: The system adds the new records to the end of the existing records.

TYPE

Specifies the type of problem information that is placed in the output file. Only one type of data can be placed in each file. More information on each value of this parameter, including a table on the output record format for the value, is located at the end of this parameter description.

Note: This parameter is valid only when a value is specified also on the OUTFILE parameter.

*BASIC: Basic problem data includes problem type and status; device type, model, and serial number; product ID, contact information; and tracking data.
*CAUSE: Possible problem causes include point-of-failure, partial, isolation, or answer cause records. Answer causes are used if they are available. If they are not, isolation causes are used. If isolation causes are not available, partial causes are used. If partial causes are not available, then the point-of-failure causes are used.
*FIX: Fixes to the problem are program temporary fix (PTF) records.
*USRTXT: User-supplied text, consisting of note records, is placed in the output file.
*SPTDTA: Output files with supporting data identifiers are created.
Basic Problem Data (*BASIC)
The output file produced for type *BASIC has one record for each problem in the problem log. Each record has a unique problem identifier.
The record format is QASXPBOF. See the following "DSPPRB Fields for Basic Problem Data (TYPE(*BASIC))" table for the fields in the record.
Table 1. DSPPRB Fields for Basic Problem Data (TYPE(*BASIC))

Field Name Length Description

PBRCEN 1 Century that the data was retrieved and placed in the output file:

0

20th century

1

21st century

PBRDAT 6 Date that the data was retrieved and placed in the output file.

PBRTIM 6 Time that the data was retrieved and placed in the output file.

PBSYSN 8 Name of the system in which the DSPPRB command is run to create this output file.

PBFORM 8 Record format, which is always *BASIC.

PBID 10 Problem identifier.

PBORG 20 System origin.

PBORGI 1 Problem origin indication:

L

Local

R

Remote

PBSEV 1 Problem severity levels:

1

High

2

Medium

3

Low

4

None

PBTYPE 1 Problem type (which identifies how the problem was detected):

1

Machine-detected

2

User-perceived

3

PTF order

PBSTAT 1 Problem status:

O

Opened

R

Ready

P

Prepared

S

Sent

A

Answered

V

Verified

C

Closed

PBDESC 7 Message identifier of a message in the QCPFMSG message file that describes the problem.

PBPMSG 7 Message identifier of a message in the QCPFMSG message file that describes the reference code.

PBRFCD 4 Original reference code.

PBSLID 8 Identifies the entry recorded in the error log when the system detected a problem.

PBMACH 4 Identifies the type of device with which this problem is associated.

PBMODL 3 Identifies the model of the device with which this problem is associated.

PBFEAT 4 Identifies the feature number of the device with which this problem is associated.

PBMSER 10 Identifies the serial number of the device with which this problem is associated.

PBEC 12 Identifies the engineering change (EC) level of the device with which this problem is associated.

PBLPP 7 Shows the identification number of the program with the problem. This number could be for a licensed program or for licensed internal code.

PBVER 4 Identifies the version of the program with the problem.

PBREL 2 Identifies the release level of the program with the problem.

PBMDF 2 Identifies the modification level that applies to the release level of the licensed program with the problem.

PBCNT 36 The name of the person whom service personnel should contact to help resolve this problem.

PBTEL1 30 Primary telephone number. The number service support personnel should use to contact the user's company.

PBTEL2 30 Alternate telephone number. The number service support personnel should use to contact the user's company if the primary telephone number is not available.

PBFTEL1 30 Primary fax telephone number. The number service support personnel should use to contact the user's company.

PBFTEL2 30 Alternate fax telephone number. The number service support personnel should use to contact the user's company if the primary telephone number is not available.

PBENTR 36 Company name.

PBSTR1 36 First line of street address.

PBSTR2 36 Second line of street address.

PBSTR3 36 Third line of street address.

PBCITY 36 City and state.

PBCOUN 20 Country or region.

PBZIP 12 ZIP code.

PBSNUM 10 Service assigned number.

PBEPDP 8 Identifies the program used to run problem analysis.

PBPDPE 2 Identifies the code the system returned after problem analysis is run.

PBISOS 1 Identifies the result of running problem analysis:

1

Problem analysis was successful, the problem still exists.

2

Problem analysis was successful, the problem has been resolved.

3

Problem analysis was not successful.

4

Problem analysis was not completed.

5

Problem analysis was partially completed.

PBDATO 6 Date the problem was opened.

PBTIMO 6 Time the problem was opened.

PBUSRO 10 User who opened the problem.

PBDATA 6 Date the problem was analyzed.

PBTIMA 6 Time the problem was analyzed.

PBUSRA 10 User who analyzed the problem.

PBDATP 6 Date the problem was prepared.

PBTIMP 6 Time the problem was prepared.

PBUSRP 10 User who prepared the problem.

PBDATS 6 Date the service request was sent.

PBTIMS 6 Time the service request was sent.

PBUSRS 10 User who sent the service request.

PBDATN 6 Date the service request was answered.

PBTIMN 6 Time the service request was answered.

PBUSRN 10 User who answered the problem.

PBDATF 6 Date fix was verified.

PBTIMF 6 Time fix was verified.

PBUSRF 10 User who verified the fix.

PBDATC 6 Date the problem was closed.

PBTIMC 6 Time the problem was closed.

PBUSRC 10 User who closed the problem.

PBSYMP 256 Symptom string.

PBUSRD 10 User assigned to the problem.

PBFTRN 10 Filter assigned to the problem.

PBFTRL 10 Filter library.

PBFTRG 10 Group in filter assigned to the problem.

PBALIB 10 Library containing APAR data saved for the problem.

Note:

All fields are of type C (character).

All dates are represented in YYMMDD format where:

YY

Year

MM

Month

DD

Day

For example 940515 represents May 15, 1994.

All times are for a 24-hour clock and are represented in HHMMSS format where:

HH

Hour

MM

Minutes

SS

Seconds

For example 144526 represents 26 seconds past 2:45 p.m.

The contact name, telephone numbers, company name, and address are only present if different than the service contact information.

For those activities that can be done more than once, the date and time represent the last time the activity was done.

Possible Causes (*CAUSE)
The output file produced for type *CAUSE has one record for each possible cause identified at the time the failure was detected or as a result of running problem analysis. The cause list type indicates when the possible causes were identified and is the same for all records with a given problem identifier.
The sum of the possibilities will equal 100 percent for each problem identifier.
The record format is QSXCAOF. See the following "DSPPRB Fields for Possible Cause Data (TYPE(*CAUSE))" table for the fields in the record.

Table 2. DSPPRB Fields for Possible Cause Data (TYPE(*CAUSE))

Field Name Length Description

CARCEN 1 Century that the data was retrieved and placed in the output file:

0

20th century

1

21st century

CARDAT 6 Date that the data was retrieved and placed in the output file.

CARTIM 6 Time that the data was retrieved and placed in the output file.

CASYSN 8 Name of the system where the DSPPRB command was run to create this output file.

CAFORM 8 Format, which is always *CAUSE.

CAID 10 Problem identifier.

CAORG 20 System origin.

CALIST 1 Cause list type:

P

The possible cause list was identified when the failure occurred.

L

The possible cause list was identified by problem analysis which was not completed.

I

The possible cause list was identified by problem analysis.

A

The possible cause list was returned by RETAIN as result of a service request.

CACODE 4 Cause code.

CANAME 7 A message identifier of a message in QCPFMSG that describes a possible cause.

CADOC 7 Message identifier of a message in QCPFMSG that identifies the document being referenced when solving this problem.

CADEVL 40 Location of the rack or system unit when the device is installed.

CAPRT1 12 Part 1, a part which describes a possible hardware problem cause. Up to six part numbers are possible for a part because different part numbers are used to identify the part when it has different features.

CAPRT2 12 Part 2

CAPRT3 12 Part 3

CAPRT4 12 Part 4

CAPRT5 12 Part 5

CAPRT6 12 Part 6

CATYPE 1 Cause type:

Field

Type (Instances)

A, K, N

Hardware (communications controller or power supply)

C

Software (OS/400)

D

Device (terminal, printer, or tape unit)

E

S/370 channel attached device

G

Configuration (controller description parameter incorrect)

H

General (modem or cable)

M

Media (tape or diskette)

U

User (door open or diskette upside down)

CACHNC 3,0 The possibility that this part or action will correct the problem (1-100%).

CADEVN 10 Name of the device where the part is installed.

CAMACH 4 Type of device.

CAMODL 3 Model number of device.

CAFEAT 4 Feature number of device.

CAMSER 10 Serial number of the device.

CARSER 10 Serial number of the rack where the device is installed.

CAADDR 9 Address (1234-5678)

CALPP 7 Identifies a licensed program or licensed internal code. Only present for cause type 'C'.

CAVER 4 Version of the licensed program. Only present for cause type 'C'.

CAREL 2 Release level of the licensed program. Only present for cause type 'C'.

CAMDF 2 Modification level that applies to the release of the licensed program. Only present for cause type 'C'.

CAMOD 10 Module in the licensed program. Only present for cause type 'C'.

CAVOL 8 Removable media volume identifier. Only present for cause type 'M'.

CARSRC 10 Resource name assigned to the device by the system.

CAPORT 2 Port where the work station cable connects to the work station attachment.

CAPLOC 25 Location of the part in the device.

CAPCOD 4 Symptom code, also called the Fault Symptom Code (FSC). It is generated by the sense bits collected in the hardware device at the time of failure. Only present for cause type 'E'.

CASENS 64 Sense data bytes are made up of the bits that are collected in the hardware device to show the status of the device. Only present for cause type 'E'.

CAEADDR 13 Address of device where part is installed.

1-4

Identifies the device controller card.

5

Separator character (-).

6-13

Identifies the failing device or resource.

Note: All fields are of type C (character), except the CACHNC field, which is of type P (packed decimal).

Program Fixes (*FIX)
The output file produced for type *FIX has one record for each program temporary fix (PTF) identified as a result of a service call for a machine-detected or user-perceived problem. Multiple program fix records may have the same problem identifier.
The record format is QSXFXOF. See the following "DSPPRB Fields for Program Fix Data (TYPE(*FIX))" table for the fields in the record.

Table 3. DSPPRB Fields for Program Fix Data (TYPE(*FIX))

Field Name Length Description

FXRCEN 1 Century that the data was retrieved and placed in the output file:

0

20th century

1

21st century

FXRDAT 6 Date that the data was retrieved and placed in the output file.

FXRTIM 6 Time that the data was retrieved and placed in the output file.

FXSYSN 8 Name of the system where the DSPPRB command was run to create this output file.

FXFORM 8 Format, which is always *FIX.

FXID 10 Problem identifier.

FXORG 20 System origin.

FXPTF 7 Program temporary fix (PTF) number.

FXPST 1 Program temporary fix (PTF) status:

N

Not requested.

R

Requested.

FXSFS 1 PTF save file status: "Y" = yes; "N" = no; "R" = yes (released)

FXPRD 7 PTF product ID or special value *ONLY. *ONLY represents PTFID(*ONLYPRD) specified on the SNDPTFORD command.

FXRLS 6 PTF release level (VxRxMx) or special value *ONLY. *ONLY represents PTFID(*ONLYRLS) specified on the SNDPTFORD command.

Note: All fields are of type C (character).

User Text (*USRTXT)
The output file produced for type *USRTXT has one record for each line of user-entered text (notes). Multiple text records may have the same problem identifier.
The record format is QSXTXOF. See the following "DSPPRB Fields for User Text Data (TYPE(*USRTXT))" table for the fields in the record.

Table 4. DSPPRB Fields for User Text Data (TYPE(*USRTXT))

Field Name Length Description

TXRCEN 1 Century that the data was retrieved and placed in the output file:

0

20th century

1

21st century

TXRDAT 6 Date that the data was retrieved and placed in the output file.

TXRTIM 6 Time that the data was retrieved and placed in the output file.

TXSYSN 8 Name of the system where the DSPPRB command was run to create this output file.

TXFORM 8 Format, which is always *USRTXT.

TXID 10 Problem identifier.

TXORG 20 System origin.

TXTYPE 1 Type of text:

N

Note

S

Problem description

TXTEXT 80 User-entered text.

Note: All fields are of type C (character).

Supporting Data Identifiers (*SPTDTA)
The output file produced for type *SPTDTA has one record for each item identified. Multiple records may have the same problem identifier. Items identified contain information related to the problem. The data identifier type indicates the type of item being identified. The information in other fields is dependent on the type of item being identified.
The record format is QSXSDOF. See the following "DSPPRB Fields for Supporting Data Identifier Data (TYPE(*BASIC))" table for the fields in the record.

Table 5. DSPPRB Fields for Supporting Data Identifier Data (TYPE(*SPTDTA))

Field Name Length Description

SDRCEN 1 Century that the data was retrieved and placed in the output file:

0

20th century

1

21st century

SDRDAT 6 Date that the data was retrieved and placed in the output file.

SDRTIM 6 Time that the data was retrieved and placed in the output file.

SDSYSN 8 Name of the system where the DSPPRB command was run to create this output file.

SDFORM 8 Format, which is always *SPTDTA.

SDID 10 Problem identifier.

SDORG 20 System origin.

SDTYPE 1 Type of identifier:

S

Spooled file identifier

SDNAM1 10 Identifier name 1:

Type S

Spooled file name

SDNAM2 10 Identifier name 2:

Type S

Job name

SDNAM3 10 Identifier name 3:

Type S

User name

SDJNBR 10 Job number

SDFNBR 10 Spooled file number

Note: All fields are of type C (character).

Examples for DSPPRB
Example 1: Displaying Today's Problem Log Entries
DSPPRB PERIOD((*AVAIL *CURRENT) (*AVAIL *CURRENT))

This command shows all problem log entries that were created today.
Example 2: Creating an Output File
DSPPRB OUTPUT(*OUTFILE) OUTFILE(*CURLIB/NEWFILE)

This command creates a member in the physical file NEWFILE in the current library which contains a record for each problem log entry in the problem log.
Example 3: Displaying a List of Hardware Problems
DSPPRB SEV(1 2) HARDWARE(9347 001 10-7523489)

This command shows a list containing problems with the hardware specified by the user. The user has specified that the command track medium-to-high levels of severity.
Example 4: Displaying a List of Problems That Have Been Opened
DSPPRB STATUS(*OPENED) PERIOD((*AVAIL *CURRENT) (120000 *CURRENT)) LICPGM(5716SS1 03 00) PGM(QNOPGM)

This command shows a list containing problems that have been opened during the period starting at midnight and ending at noon on the current day, and have not yet been analyzed. This command also identifies the specified licensed program identifier and program name as the probable cause of the failure.
Example 5: Displaying a List of Machine-Detected Problems
DSPPRB RESOURCE(TAP01) MSGID(CPF6788)

This command shows a list containing machine-detected problems that were opened due to the message, CPF6788, having been sent to the system operator message queue. The list of problems includes user-detected problems. To get the user-detected problems, the user specified the resource name and message identifier by using the Analyze Problem (ANZPRB) command.
Example 6: Displaying a List of Reported Problems
DSPPRB SRVID(12345)

This command shows a list containing problems that have been reported to an IBM service support center and have 12345 as the service identifier.
Error messages for DSPPRB
*ESCAPE Messages

CPF7A9C

Cannot work with the problem log at this time.

CPF9845

Error occurred while opening file &1.

CPF9847

Error occurred while closing file &1 in library &2.

Field Name	Length	Description
PBRCEN	1	Century that the data was retrieved and placed in the output file: 0 20th century 1 21st century
PBRDAT	6	Date that the data was retrieved and placed in the output file.
PBRTIM	6	Time that the data was retrieved and placed in the output file.
PBSYSN	8	Name of the system in which the DSPPRB command is run to create this output file.
PBFORM	8	Record format, which is always *BASIC.
PBID	10	Problem identifier.
PBORG	20	System origin.
PBORGI	1	Problem origin indication: L Local R Remote
PBSEV	1	Problem severity levels: 1 High 2 Medium 3 Low 4 None
PBTYPE	1	Problem type (which identifies how the problem was detected): 1 Machine-detected 2 User-perceived 3 PTF order
PBSTAT	1	Problem status: O Opened R Ready P Prepared S Sent A Answered V Verified C Closed
PBDESC	7	Message identifier of a message in the QCPFMSG message file that describes the problem.
PBPMSG	7	Message identifier of a message in the QCPFMSG message file that describes the reference code.
PBRFCD	4	Original reference code.
PBSLID	8	Identifies the entry recorded in the error log when the system detected a problem.
PBMACH	4	Identifies the type of device with which this problem is associated.
PBMODL	3	Identifies the model of the device with which this problem is associated.
PBFEAT	4	Identifies the feature number of the device with which this problem is associated.
PBMSER	10	Identifies the serial number of the device with which this problem is associated.
PBEC	12	Identifies the engineering change (EC) level of the device with which this problem is associated.
PBLPP	7	Shows the identification number of the program with the problem. This number could be for a licensed program or for licensed internal code.
PBVER	4	Identifies the version of the program with the problem.
PBREL	2	Identifies the release level of the program with the problem.
PBMDF	2	Identifies the modification level that applies to the release level of the licensed program with the problem.
PBCNT	36	The name of the person whom service personnel should contact to help resolve this problem.
PBTEL1	30	Primary telephone number. The number service support personnel should use to contact the user's company.
PBTEL2	30	Alternate telephone number. The number service support personnel should use to contact the user's company if the primary telephone number is not available.
PBFTEL1	30	Primary fax telephone number. The number service support personnel should use to contact the user's company.
PBFTEL2	30	Alternate fax telephone number. The number service support personnel should use to contact the user's company if the primary telephone number is not available.
PBENTR	36	Company name.
PBSTR1	36	First line of street address.
PBSTR2	36	Second line of street address.
PBSTR3	36	Third line of street address.
PBCITY	36	City and state.
PBCOUN	20	Country or region.
PBZIP	12	ZIP code.
PBSNUM	10	Service assigned number.
PBEPDP	8	Identifies the program used to run problem analysis.
PBPDPE	2	Identifies the code the system returned after problem analysis is run.
PBISOS	1	Identifies the result of running problem analysis: 1 Problem analysis was successful, the problem still exists. 2 Problem analysis was successful, the problem has been resolved. 3 Problem analysis was not successful. 4 Problem analysis was not completed. 5 Problem analysis was partially completed.
PBDATO	6	Date the problem was opened.
PBTIMO	6	Time the problem was opened.
PBUSRO	10	User who opened the problem.
PBDATA	6	Date the problem was analyzed.
PBTIMA	6	Time the problem was analyzed.
PBUSRA	10	User who analyzed the problem.
PBDATP	6	Date the problem was prepared.
PBTIMP	6	Time the problem was prepared.
PBUSRP	10	User who prepared the problem.
PBDATS	6	Date the service request was sent.
PBTIMS	6	Time the service request was sent.
PBUSRS	10	User who sent the service request.
PBDATN	6	Date the service request was answered.
PBTIMN	6	Time the service request was answered.
PBUSRN	10	User who answered the problem.
PBDATF	6	Date fix was verified.
PBTIMF	6	Time fix was verified.
PBUSRF	10	User who verified the fix.
PBDATC	6	Date the problem was closed.
PBTIMC	6	Time the problem was closed.
PBUSRC	10	User who closed the problem.
PBSYMP	256	Symptom string.
PBUSRD	10	User assigned to the problem.
PBFTRN	10	Filter assigned to the problem.
PBFTRL	10	Filter library.
PBFTRG	10	Group in filter assigned to the problem.
PBALIB	10	Library containing APAR data saved for the problem.
Note: All fields are of type C (character). All dates are represented in YYMMDD format where: YY Year MM Month DD Day For example 940515 represents May 15, 1994. All times are for a 24-hour clock and are represented in HHMMSS format where: HH Hour MM Minutes SS Seconds For example 144526 represents 26 seconds past 2:45 p.m. The contact name, telephone numbers, company name, and address are only present if different than the service contact information. For those activities that can be done more than once, the date and time represent the last time the activity was done.

Field Name	Length	Description
CARCEN	1	Century that the data was retrieved and placed in the output file: 0 20th century 1 21st century
CARDAT	6	Date that the data was retrieved and placed in the output file.
CARTIM	6	Time that the data was retrieved and placed in the output file.
CASYSN	8	Name of the system where the DSPPRB command was run to create this output file.
CAFORM	8	Format, which is always *CAUSE.
CAID	10	Problem identifier.
CAORG	20	System origin.
CALIST	1	Cause list type: P The possible cause list was identified when the failure occurred. L The possible cause list was identified by problem analysis which was not completed. I The possible cause list was identified by problem analysis. A The possible cause list was returned by RETAIN as result of a service request.
CACODE	4	Cause code.
CANAME	7	A message identifier of a message in QCPFMSG that describes a possible cause.
CADOC	7	Message identifier of a message in QCPFMSG that identifies the document being referenced when solving this problem.
CADEVL	40	Location of the rack or system unit when the device is installed.
CAPRT1	12	Part 1, a part which describes a possible hardware problem cause. Up to six part numbers are possible for a part because different part numbers are used to identify the part when it has different features.
CAPRT2	12	Part 2
CAPRT3	12	Part 3
CAPRT4	12	Part 4
CAPRT5	12	Part 5
CAPRT6	12	Part 6
CATYPE	1	Cause type: Field Type (Instances) A, K, N Hardware (communications controller or power supply) C Software (OS/400) D Device (terminal, printer, or tape unit) E S/370 channel attached device G Configuration (controller description parameter incorrect) H General (modem or cable) M Media (tape or diskette) U User (door open or diskette upside down)
CACHNC	3,0	The possibility that this part or action will correct the problem (1-100%).
CADEVN	10	Name of the device where the part is installed.
CAMACH	4	Type of device.
CAMODL	3	Model number of device.
CAFEAT	4	Feature number of device.
CAMSER	10	Serial number of the device.
CARSER	10	Serial number of the rack where the device is installed.
CAADDR	9	Address (1234-5678)
CALPP	7	Identifies a licensed program or licensed internal code. Only present for cause type 'C'.
CAVER	4	Version of the licensed program. Only present for cause type 'C'.
CAREL	2	Release level of the licensed program. Only present for cause type 'C'.
CAMDF	2	Modification level that applies to the release of the licensed program. Only present for cause type 'C'.
CAMOD	10	Module in the licensed program. Only present for cause type 'C'.
CAVOL	8	Removable media volume identifier. Only present for cause type 'M'.
CARSRC	10	Resource name assigned to the device by the system.
CAPORT	2	Port where the work station cable connects to the work station attachment.
CAPLOC	25	Location of the part in the device.
CAPCOD	4	Symptom code, also called the Fault Symptom Code (FSC). It is generated by the sense bits collected in the hardware device at the time of failure. Only present for cause type 'E'.
CASENS	64	Sense data bytes are made up of the bits that are collected in the hardware device to show the status of the device. Only present for cause type 'E'.
CAEADDR	13	Address of device where part is installed. 1-4 Identifies the device controller card. 5 Separator character (-). 6-13 Identifies the failing device or resource.
Note: All fields are of type C (character), except the CACHNC field, which is of type P (packed decimal).

Field Name	Length	Description
FXRCEN	1	Century that the data was retrieved and placed in the output file: 0 20th century 1 21st century
FXRDAT	6	Date that the data was retrieved and placed in the output file.
FXRTIM	6	Time that the data was retrieved and placed in the output file.
FXSYSN	8	Name of the system where the DSPPRB command was run to create this output file.
FXFORM	8	Format, which is always *FIX.
FXID	10	Problem identifier.
FXORG	20	System origin.
FXPTF	7	Program temporary fix (PTF) number.
FXPST	1	Program temporary fix (PTF) status: N Not requested. R Requested.
FXSFS	1	PTF save file status: "Y" = yes; "N" = no; "R" = yes (released)
FXPRD	7	PTF product ID or special value ONLY. ONLY represents PTFID(*ONLYPRD) specified on the SNDPTFORD command.
FXRLS	6	PTF release level (VxRxMx) or special value ONLY. ONLY represents PTFID(*ONLYRLS) specified on the SNDPTFORD command.
Note: All fields are of type C (character).

Field Name	Length	Description
TXRCEN	1	Century that the data was retrieved and placed in the output file: 0 20th century 1 21st century
TXRDAT	6	Date that the data was retrieved and placed in the output file.
TXRTIM	6	Time that the data was retrieved and placed in the output file.
TXSYSN	8	Name of the system where the DSPPRB command was run to create this output file.
TXFORM	8	Format, which is always *USRTXT.
TXID	10	Problem identifier.
TXORG	20	System origin.
TXTYPE	1	Type of text: N Note S Problem description
TXTEXT	80	User-entered text.
Note: All fields are of type C (character).

Field Name	Length	Description
SDRCEN	1	Century that the data was retrieved and placed in the output file: 0 20th century 1 21st century
SDRDAT	6	Date that the data was retrieved and placed in the output file.
SDRTIM	6	Time that the data was retrieved and placed in the output file.
SDSYSN	8	Name of the system where the DSPPRB command was run to create this output file.
SDFORM	8	Format, which is always *SPTDTA.
SDID	10	Problem identifier.
SDORG	20	System origin.
SDTYPE	1	Type of identifier: S Spooled file identifier
SDNAM1	10	Identifier name 1: Type S Spooled file name
SDNAM2	10	Identifier name 2: Type S Job name
SDNAM3	10	Identifier name 3: Type S User name
SDJNBR	10	Job number
SDFNBR	10	Spooled file number
Note: All fields are of type C (character).