| 1 | Display panels | Input | Char(10) |
| 2 | Problem ID number | Input | Char(10) |
| 3 | Origin system | Input | Char(20) |
| 4 | Current problem status | Input | Char(10) |
| 5 | Requested problem statuses | Input | Array of Char(10) |
| 6 | Number of requested problem statuses | Input | Binary(4) |
| 7 | Service provider network identifier | Input | Char(8) |
| 8 | Service provider control point name | Input | Char(8) |
| 9 | Problem severity | Input | Char(1) |
| 10 | Error code | I/O | Char(*) |
| 11 | Note text | Input | Char(*) |
| 12 | Length of note text | Input | Binary(4) |
The Work with Problem (QPDWRKPB) API uses a problem log entry to analyze and prepare a machine-detected hardware problem for reporting. Only local machine-detected problems that have an OPEN, READY, PREPARED, or SENT status can be analyzed and prepared for reporting. Remote problems that have an OPEN, READY, PREPARED, or SENT status can be prepared for reporting but cannot be analyzed. This API does not analyze or prepare user-detected problems.
If a machine-detected problem is analyzed, the problem analysis program associated with the problem is called to generate a problem analysis list identifying all the possible causes for the problem.
None.
Whether or not displays are shown during problem analysis. Valid values are:
| *NO | No displays are shown. |
| Note: During problem analysis, if displays are usually shown for the type of hardware associated with the problem, then the Point of Failure list is saved. This list is only saved if no other list of causes currently associated with the problem exists. | |
| *YES | All displays are shown. This value is not allowed if the API is called in a batch job. |
The number the system generates to identify a problem.
The node name of the origin system (the format is network-ID.control-point-name).
The current status of the problem. If the problem is found to be in a status other than what is indicated, an error occurs. Valid values are:
| *OPENED | The problem was identified and a problem record was created. |
| *READY | Problem analysis information has been added to the problem record. |
| *PREPARED | The problem has been prepared for reporting. |
| *SENT | The problem record was sent to a service provider, and the information needed to correct the problem was not returned. |
| *ANSWERED | The problem has been answered. |
The requested status for the problem.
Valid values are:
| *READY | Analyze the problem. Valid for local machine-detected problems only. |
| *PREPARED | Prepare the problem for reporting. The service provider network identifier, service provider control point name, and problem severity parameters and the default contact database are used. |
| Note: If you select *READY and *PREPARED, the final status is *PREPARED. |
The number of statuses entered for requested problem statuses parameter.
The network identifier of the service provider system where the problem is to be sent.
Valid values are:
| *NETATR | The network identifier of this system. Use *NETATR if the control point name is *IBMSRV. |
The control point name of the service provider system where the problem is to be sent.
Valid values are:
| *IBMSRV | IBM service support. This value cannot be used if the problem has an *OPENED status unless you also have a requested problem status of *READY. |
| Name | The control point name. |
The severity of the problem.
Valid values are:
| 1 | A high severity level in which there is a critical affect on operations. A severity 1 problem requires a service representative at the site, and the person solving the problem must work on the problem 24 hours a day until the problem is solved or circumvented. If the problem needs more information, patching, or the problem must be created again on the failing system, a service representative must be available to do these tasks immediately. It is not a severity 1 if these and any other tasks cannot be performed immediately. |
| 2 | A medium severity level in which you are able to use the system, but your operations are severely restricted by the problem. |
| 3 | A low severity level in which you are able to continue operations with some restrictions. The restrictions do not have a critical effect on your operations. |
| 4 | The severity level is minimal because the problem causes little or no effect to your operation, or you have found a way to circumvent the problem. |
The structure in which to return error information. For the format of the structure, see Error Code Parameter.
The field used to include a note stating that a problem originated with the service director. The note will be included when the API is called.
The length of the text for the note text field. The text field for the note text field can be up to 80 characters long.
| Message ID | Error Message Text |
|---|---|
| CPF3C90 E | Literal value cannot be changed. |
| CPF3CF1 E | Error code parameter not valid. |
| CPF3CF2 E | Error(s) occurred during running of &1 API. |
| CPF7AA7 E | Problem &1 not found. |
| CPF7A9C E | Cannot work with the problem log at this time. |
| CPF7A9D E | Problem log object &1 is missing. |
| CPF7A93 E | Problem &2 currently in use by job &1. |
| CPF8C09 E | &1 not defined as a service provider. |
| CPF8C24 E | Error occurred while processing request. |
| CPF8C87 E | Service provider &1.&2 not found. |
| CPF9308 E | Unable to complete problem analysis. Reason code &1. |
| CPF931C E | Problem analysis results not recorded in problem log. |
| CPF9310 E | Problem analysis procedure was exited before it had completed. |
| CPF9313 E | Requested procedure is not allowed. |
| CPF932A E | Number of requested statuses is not valid. |
| CPF932B E | *IBMSRV not allowed as service provider for problems in OPENED status. |
| CPF9320 E | &1 to display panels is not valid. |
| CPF9321 E | Panels cannot be displayed in a batch job. |
| CPF9322 E | Current status &3 does not match problem status &4. |
| CPF9323 E | Current status &1 is not valid. |
| CPF9324 E | Problems on a remote system cannot be analyzed. |
| CPF9325 E | Problem &1 has a status that is not allowed. |
| CPF9326 E | Problem selected not allowed. |
| CPF9327 E | Problem analysis procedure was exited before it had completed. |
| CPF9328 E | Severity &1 is not valid. |
| CPF9329 E | Requested status &1 is not valid. |
| CPF7845 E | Error occurred while opening file &1. |
| CPF7846 E | Error while processing file &1 in library &2. |
| CPF7847 E | Error occurred while closing file &1 in library &2. |
| CPF7872 E | Program or service program &1 in library &2 ended. Reason code &3. |
| Top | Problem Management API list APIs by category |