1 | Receiver variable | Output | Char(*) |
2 | Length of receiver variable | Input | Binary(4) |
3 | PTF information | Input | Char(50) |
4 | Format name | Input | Char(8) |
5 | Error Code | I/O | Char(*) |
The Retrieve Program Temporary Fix Information (QPZRTVFX) API returns information about a specific program temporary fix (PTF). The information returned is determined by the format specified.
You can use the QPZRTVFX API to:
Lock conflicts may occur if this API is called while another PTF operation is in progress.
The receiver variable that is to receive the information requested. The length of this area must be passed in the length of receiver variable parameter. The API returns only the data the area can hold.
The length of the receiver variable. You can specify a smaller area than the format requested as long as you specify the length of receiver variable parameter correctly. If the length specified is larger than the size of the receiver variable, the results are not predictable. This value must be greater than or equal to 8.
The attributes of the PTF for which information is being requested. For more information on this parameter see Format of PTF Information.
The content and format of the information returned for the PTF. The possible format names are:
PTFR0100 | Basic information; for details, see PTFR0100 Format. |
PTFR0200 | This format contains the basic information as
well as an array of cover letters in the format given. If the receiver variable
does not have enough space for all the cover letters to be returned, only the
cover letters that fit in the space provided are returned. For details, see PTFR0200 Format. |
PTFR0300 | This contains the basic information plus an array
that contains information about the requisite PTFs. If the receiver variable
does not have enough space to return all requisite information, only the
information that fits in the space provided is returned. For details, see PTFR0300 Format. |
PTFR0400 | This contains the basic information plus an array
that contains a list of the PTF objects and their alternative names. If the
receiver variable does not have enough space to return all of the PTF object
information, only the information that fits in the space provided is returned.
For details, see PTFR0400 Format. |
PTFR0500 | This contains the basic information plus an array
that contains information about the dependent PTFs. If the receiver variable
does not have enough space to return all dependent information, only the
information that fits in the space provided is returned. For details, see PTFR0500 Format. |
PTFR0600 | This contains the basic information plus an array
that contains information about the APAR numbers. If the receiver variable does
not have enough space to return all APAR information, only the information that
fits in the space provided is returned. For details, see PTFR0600 Format. |
PTFR0700 | This contains the basic information plus an array
that contains information about the symptom strings. If the receiver variable
does not have enough space to return all symptom string information, only the
information that fits in the space provided is returned. For details, see PTFR0700 Format. |
PTFR0800 | This contains the basic information plus an array
that contains the exit program information. If the receiver variable does not
have enough space to return all exit program information, only the information
that fits in the space provided is returned. For details, see PTFR0800 Format. |
PTFR0900 | This contains the basic information plus an array that contains the information about the preconditions. If the receiver variable does not have enough space to return the precondition information, only the information that fits in the space provided is returned. For details, see PTFR0900 Format. |
PTFR1000 | This contains the basic information plus an array that contains the information about the superseded PTFs. If the receiver variable does not have enough space to return the superseded PTF information, only the information that fits in the space provided is returned. For details, see PTFR1000 Format. |
The structure in which to return error information. For the format of the structure, see Error Code Parameter.
For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | CHAR(7) | PTF ID |
7 | 7 | CHAR(7) | Product ID |
14 | E | CHAR(6) | Release level |
20 | 14 | BINARY(4) | CCSID for returned directory names |
24 | 18 | CHAR(1) | Close PTF database files |
25 | 19 | CHAR(25) | Reserved |
CCSID for returned directory names. The CCSID in which the directory names should be returned. If this field is blank, the CCSID is the job default CCSID. This value is used only for returned directory names.
Close PTF database files. Whether the PTF database files should remain open after returning from the API call. This field allows for improved performance when this API is called numerous times during processing. Do not leave the PTF database files open for long periods of time because other PTF operations cannot be performed while these files are open. If a blank is specified in this field, it will be treated as a 0.
0 | The PTF database files will be closed before returning from the API call. |
1 | The PTF database files will remain open until the API is called again with this field set to 0. |
Product ID. The product ID for the PTF for which information is requested. The possible values are:
*ONLY | The product ID is not known, but only one PTF exists on the system by this PTF ID. |
product ID | The product ID for the PTF. |
PTF ID. The identifier of the PTF for which information is requested.
Release level. The release of the PTF for which information is requested. This field is ignored if *ONLY is specified in the product ID field. The format is:
VxRyMz | The release of the PTF is in the format VxRyMz. Valid entries for x and y are any number between 0 and 9. A valid entry for z is a number between 0 and 9 or a character between A and Z. |
Reserved. This field must contain blanks.
This format returns basic information about the PTF. For detailed descriptions of 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) | Offset to additional information |
12 | C | CHAR(7) | Product ID |
19 | 13 | CHAR(7) | PTF ID |
26 | 1A | CHAR(6) | Release level |
32 | 20 | CHAR(4) | Product option |
36 | 24 | CHAR(4) | Load ID |
40 | 28 | CHAR(1) | Loaded status |
41 | 29 | CHAR(1) | Cover letter status |
42 | 2A | CHAR(1) | On-order status |
43 | 2B | CHAR(1) | Save file status |
44 | 2C | CHAR(10) | File name |
54 | 36 | CHAR(10) | File library name |
64 | 40 | CHAR(1) | PTF type |
65 | 41 | CHAR(1) | IPL action |
66 | 42 | CHAR(1) | Action pending |
67 | 43 | CHAR(1) | Action required |
68 | 44 | CHAR(1) | PTF is released |
69 | 45 | CHAR(6) | Target release |
75 | 4B | CHAR(7) | Superseding PTF |
82 | 52 | CHAR(1) | Current IPL source |
83 | 53 | CHAR(2) | Minimum level |
85 | 55 | CHAR(2) | Maximum level |
87 | 57 | CHAR(1) | Format information available |
88 | 58 | CHAR(13) | Status date and time |
101 | 65 | CHAR(7) | Licensed Internal Code group |
108 | 6C | CHAR(7) | Superseded by PTF ID |
115 | 73 | CHAR(1) | Current server IPL source |
116 | 74 | CHAR(1) | Server IPL required |
117 | 75 | CHAR(13) | Creation date and time |
130 | 82 | CHAR(*) | Reserved |
The fields that follow the cover letter records field define an entry in that array. That group of fields is repeated by the number of different NLVs available for the cover letter field. For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to first cover letter record from the beginning | ||
BINARY(4) | Number of different NLVs available for the cover letter | ||
BINARY(4) | Length of cover letter record | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to first cover letter of format PTFR0200. | |||
ARRAY of CHAR(*) | Cover letter records | ||
CHAR(4) | Cover letter national language version (NLV) | ||
CHAR(10) | Cover letter file name | ||
CHAR(10) | Cover letter library name | ||
CHAR(10) | Cover letter member name | ||
CHAR(1) | Pre-apply or pre-remove considerations | ||
CHAR(1) | Post-apply or post-remove considerations | ||
CHAR(*) | Reserved |
The fields following the requisite record field define an entry in that array. That group of fields is repeated by the number of requisites. For detailed descriptions of each field, seeField Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to first requisite record | ||
BINARY(4) | Number of requisites | ||
BINARY(4) | Length of requisite record | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to first requisite record of format PTFR0300. | |||
ARRAY of CHAR(*) | Requisite record | ||
CHAR(7) | Requisite product ID | ||
CHAR(7) | Requisite PTF ID | ||
CHAR(6) | Release of requisite | ||
CHAR(2) | Requisite minimum level | ||
CHAR(2) | Requisite maximum level | ||
CHAR(1) | Type of requisite | ||
CHAR(1) | Requisite is conditional | ||
CHAR(1) | Requisite is required | ||
CHAR(4) | Requisite option | ||
CHAR(4) | Requisite load ID | ||
CHAR(*) | Reserved |
The fields following the PTF object record field define an entry in that array. That group of fields is repeated by the number of PTF objects. If a PTF contains subobjects, an offset to an array of subobjects is provided. The subobject fields are repeated by the number of PTF subobjects. For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to the first PTF object record | ||
BINARY(4) | Number of PTF objects | ||
BINARY(4) | Length of PTF object record | ||
BINARY(4) | CCSID of returned directories | ||
CHAR(1) | Error indicator for CCSID conversion | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the first PTF object record of format PTFR0400. | |||
ARRAY of CHAR(*) | PTF object record | ||
BINARY(4) | Offset to this PTF object's first subobject record | ||
BINARY(4) | Number of PTF subobjects | ||
BINARY(4) | Length of subobject record | ||
CHAR(10) | Object name | ||
CHAR(10) | Object library | ||
CHAR(10) | Alternative object name | ||
CHAR(7) | Object type | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to this PTF object's first subobject record of format PTFR0400. | |||
ARRAY of CHAR(*) | PTF subobject record | ||
BINARY(4) | Offset to subobject name | ||
BINARY(4) | Length of subobject name | ||
CHAR(7) | Subobject attribute | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the subobject name in the subobject array record of format PTFR0400. | |||
CHAR(*) | Subobject name |
The fields following the dependent record field define an entry in that array. That group of fields is repeated by the number of dependents. For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to first dependent PTF record | ||
BINARY(4) | Number of dependent PTFs | ||
BINARY(4) | Length of dependent PTF record | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to first dependent PTF record of format PTFR0500. | |||
ARRAY of CHAR(*) | Dependent PTF record | ||
CHAR(7) | Dependent product ID | ||
CHAR(7) | Dependent PTF ID | ||
CHAR(6) | Release of dependent PTF | ||
CHAR(2) | Dependent minimum level | ||
CHAR(2) | Dependent maximum level | ||
CHAR(1) | Type of dependent PTF | ||
CHAR(4) | Dependent option | ||
CHAR(4) | Dependent load ID | ||
CHAR(*) | Reserved |
The fields following the APAR record field define an entry in that array. That group of fields is repeated by the number of APAR records. For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to first APAR record | ||
BINARY(4) | Number of APAR records | ||
BINARY(4) | Length of APAR record | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the first APAR record of format PTFR0600. | |||
ARRAY of CHAR(*) | APAR record | ||
CHAR(7) | APAR number | ||
CHAR(*) | Reserved |
The fields following the symptom string record field define an entry in that array. That group of fields is repeated by the number of symptom string records. For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to first symptom string record | ||
BINARY(4) | Number of symptom string records | ||
BINARY(4) | Length of symptom string record | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the first symptom string record of format PTFR0700. | |||
ARRAY of CHAR(*) | Symptom string record | ||
BINARY(4) | Offset to symptom string data | ||
BINARY(4) | Length of symptom string data | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the symptom string data of format PTFR0700. | |||
CHAR(*) | Symptom string data |
The fields following the exit program record field define an entry in that array. That group of fields is repeated by the number of exit programs. For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to first exit program record | ||
BINARY(4) | Number of exit program records | ||
BINARY(4) | Length of exit program record | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the first exit program record of format PTFR0800. | |||
ARRAY of CHAR(*) | Exit program record | ||
BINARY(4) | Offset to exit program user data | ||
BINARY(4) | Length of exit program user data | ||
CHAR(10) | Exit program name | ||
CHAR(10) | Exit program library | ||
CHAR(1) | Exit program run option | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the exit program user data of format PTFR0800. | |||
CHAR(*) | Exit program user data |
The fields following the precondition record field define an entry in that array. That group of fields is repeated by the number of precondition records. For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to first precondition record | ||
BINARY(4) | Number of precondition records | ||
BINARY(4) | Length of precondition record | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the first precondition record of format PTFR0900. | |||
ARRAY of CHAR(*) | Precondition record | ||
CHAR(10) | Precondition type | ||
CHAR(10) | Precondition name | ||
CHAR(10) | Precondition library name | ||
CHAR(*) | Reserved |
The fields following the superseded PTF record field define an entry in that array. That group of fields is repeated by the number of superseded PTF records. For detailed descriptions of each field, see Field Descriptions.
Offset | Type | Field | |
---|---|---|---|
Dec | Hex | ||
0 | 0 | All information from format PTFR0100 | |
Note: The decimal and hexadecimal offsets are reached by using the offset to additional information field in format PTFR0100. | |||
BINARY(4) | Offset to first superseded PTF record | ||
BINARY(4) | Number of superseded PTF records | ||
BINARY(4) | Length of superseded PTF record | ||
CHAR(*) | Reserved | ||
Note: The decimal and hexadecimal offsets are determined by using the value in the offset to the first superseded PTF record of format PTFR1000. | |||
ARRAY of CHAR(*) | Superseded PTF record | ||
CHAR(7) | Superseded PTF ID | ||
CHAR(*) | Reserved |
APAR number. The number of the APAR that is fixed when you install this PTF.
APAR record. The information about the APAR. The record is an array that contains the fields in format PTFR0600.
Action pending. Whether a required action has yet to be performed to make this PTF active. This field reflects the current status of any required actions. The following values are valid:
0 | No required actions are pending for this PTF. |
1 | A required action needs to occur for this PTF to
be active.
Check the activation instructions section of the cover letter to determine what the action is. If the action required field is a 2 and you have performed the activation instructions, then the PTF is active. However, this field will not be updated until the next IPL. |
Action required. Whether an action is required to make this PTF active when it is applied. See the cover letter to determine what action needs to be taken. The following values are valid.
0 | No activations instructions are needed for this PTF. |
1 | This PTF was shipped with activation instructions in the cover letter. This PTF has an exit program to update the status of the PTF after the activation instructions have been performed. |
2 | This PTF was shipped with activation instructions in the cover letter. No exit program exists to verify the activation instructions were performed. |
Alternative object name. The alternative name of the object when the PTF is temporarily applied or temporarily removed. PTFs that have been temporarily applied have alternative object names in the format of QPZAnnnnnn; PTFs that are temporarily removed have alternative object names in the format of QPZRnnnnnn, where nnnnnn is some number. This field is blank for the following reasons:
Bytes available. The number of bytes of data available to be returned to the user.
Bytes returned. The number of bytes that were returned to the user. This is the lesser of the number of bytes available to be returned or the length of the receiver variable.
CCSID of returned directories. The value of the CCSID in which the directories were returned. This will be the requested CCSID if the value of the CCSID conversion indicator is 0. This field is used only for subobject attributes of DIR (directory) and SOM (system object model).
Cover letter file name. The file containing the cover letter member.
Cover letter library name. The library containing the cover letter file.
Cover letter member name. The member containing the cover letter.
Cover letter national language version (NLV). The NLV corresponds to a code that indicates the language in which the cover letter was written. For more information on NLVs, see the Globalization topic in the iSeries Information Center.
Cover letter records. The record containing the cover letter information.
Cover letter status. Whether a cover letter exists for the PTF. The following values are valid.
0 | The PTF has no cover letter. |
1 | The PTF has a cover letter. |
Creation date and time. The date and time that the PTF was created. This value will be blanks when the creation date and time cannot be determined. The date and time field is in the CYYMMDDHHMMSS format:
C | Century, where 0 indicates years 19xx and 1 indicates years 20xx. |
YY | Year |
MM | Month |
DD | Day |
HH | Hour |
MM | Minute |
SS | Second |
Current IPL source. The copy of Licensed Internal Code that the system is currently operating from. The previous IPL of the system used this copy of Licensed Internal Code.
A | The system is currently operating on the A IPL source. |
B | The system is currently operating on the B IPL source. |
Blank | The current IPL source could not be determined. |
Current server IPL source. The copy of the server firmware that was used on the previous server IPL.
0 | There is no server IPL source because the system is not operating as a service partition. |
1 | The server is currently operating on the T server IPL source. |
2 | The server is currently operating on the P server IPL source. |
Dependent load ID. The load ID of the dependent PTF. This value is blank when the load ID of the dependent PTF cannot be determined.
Dependent maximum level. The indicator of the highest level of the product for which this PTF can be installed. This field will be blank if the product has no level.
Dependent minimum level. The indicator of the lowest level of the product for which this PTF can be installed. This field will be blank if the product has no level.
Dependent option. The product option of the dependent PTF. This value is blank when the option of the dependent PTF cannot be determined.
Dependent product ID. The product ID of the dependent PTF.
Dependent PTF ID. The PTF ID of the dependent PTF.
Dependent PTF record. The information about the dependent PTF. The record is an array that contains the fields in format PTFR0500.
Error indicator about CCSID conversion. Whether the CCSID conversion to the requested CCSID was successful. If the requested CCSID conversion fails, the CCSID in which the directories are returned is identified in the CCSID of returned directories field. This field is used only for subobject attributes of DIR (directory) and SOM (system object model). Possible values follow:
0 | CCSID conversion was successful. |
1 | CCSID conversion failed. |
Exit program library. The name of the library containing the exit program.
Exit program name. The name of a program that will be run at certain stages of the PTF process.
Exit program record. The information about the exit program. The record is an array that contains the fields in format PTFR0800.
Exit program run option.
The stage of the PTF process in which the exit program will be run. Possible values follow:
0 | *ACTION - The exit program is called to determine if there is action necessary to make the PTF active or inactive. |
1 | *BOTH - The exit program will be run at the end of apply and remove processing. |
2 | *APPLY - The exit program will be run at the end of apply processing. |
3 | *REMOVE - The exit program will be run at the end of remove processing. |
4 | *PREAPY - The exit program will be run before the PTF is applied and at the end of apply processing. |
5 | *PRERMV - The exit program will be run before the PTF is removed and at the end of remove processing. |
6 | *PREBTH - The exit program will be run before the PTF is removed and at the end of remove processing. It is also run before the PTF is applied and at the end of apply processing. |
File library name. The name of the library where the save file for the PTF is located. If no save file name has been reserved, this field will be blank.
File name. The name of the file where the save file for the PTF is located. If no save file name has been reserved, this field will be blank.
Format information available. When you request information using formats PTFR0300, PTFR0400, PTFR0600, PTFR0700, PTFR0800, PTFR0900, or PTFR1000 this field indicates whether the system has the information available to return for the PTF. The system may not be able to return the requested information if the PTF is permanently applied or superseded and does not have a save file. The possible values are:
0 | There was not enough information available about this PTF to return the requested data. |
1 | The information is available and complete. Refer to specific format fields for the details. |
IPL action. The action to be taken on this PTF during the next IPL. The following values are valid:
0 | No action will occur at the next IPL. |
1 | The PTF will be temporarily applied at the next IPL. |
2 | The PTF will be temporarily removed at the next IPL. |
3 | The PTF will be permanently applied at the next IPL. |
4 | The PTF will be permanently removed at the next IPL. |
Length of APAR record. The length of each APAR record.
Length of cover letter record. The length of each cover letter record.
Length of dependent PTF record. The length of each dependent PTF record.
Length of exit program record. The length of each exit program record.
Length of precondition record. The length of each precondition record.
Length of PTF object record. The length of one array element in the PTF object record.
Length of requisite record. The length of each requisite record.
Length of subobject name. The length of the subobject name.
Length of subobject record. The length of one array element in the subobject record.
Length of superseded PTF record. The length of each superseded PTF record.
Length of symptom string data. The length of the returned symptom string.
Length of symptom string record. The length of each symptom string record.
Length of exit program user data. The length of the returned exit program user data string.
Licensed Internal Code Group. The name of the Licensed Internal Code Group for this PTF. If the name of the group is not available or if the PTF is not a Licensed Internal Code fix, this field will be blank.
Loaded status. The current loaded status of the PTF. A PTF can have any of the following statuses:
0 | The PTF has never been loaded. |
1 | The PTF has been loaded. |
2 | The PTF has been applied. |
3 | The PTF has been applied permanently. |
4 | The PTF has been permanently removed. |
5 | The PTF is damaged. An error occurred while applying the PTF. It needs to be reloaded and applied. |
6 |
The PTF is superseded. A PTF will have a status of superseded when one of the
following situations occurs :
|
Note: These fields are returned as numbers instead of text because statuses are translatable text instead of special values. The text message that contains these values is CPX3501.
This field may be blank.
Load ID. The load ID of the product load for the PTF.
Maximum level. The indicator of the highest level of the product on which this PTF can be installed. If the minimum and maximum levels are the same, then this PTF can only be installed on one level of the product. The level can be AA to 99. This field will be blank if the product has no level.
Minimum level. The indicator of the lowest level of the product on which this PTF can be installed. If the minimum and maximum levels are the same, then this PTF can only be installed on one level of the product. The level can be AA to 99. This field will be blank if the product has no level.
Number of APAR records. The number of returned APAR records.
Check the format information available field returned in PTFR0100 before using this value. The number of APARs will be zero when the system cannot determine if this PTF has APARs.
Number of dependent PTFs. The number of dependent PTFs available. The receiver variable may not have been large enough to hold all the dependent PTF records. If so, the number of dependents returned may be less than this value.
Number of different NLVs available for the cover letter. Cover letter member names are returned in an array. This number indicates how many NLVs were available for the cover letter. However, the length of the receiver may not have been large enough to hold all the cover letter NLVs available. If so, the number of cover letter member names returned may be less than this value.
Number of exit program records. The number of exit program records. The receiver variable may not have been large enough to hold all the exit program records. If so, the number of exit programs returned may be less than this value.
Check the format information available field returned in PTFR0100 before using this value. The number of exit programs will be zero when the system cannot determine if this PTF has any exit programs.
Number of precondition records. The number of returned precondition records.
Check the format information available field returned in PTFR0100 before using this value. The number of precondition records will be zero when the system cannot determine if this PTF has preconditions.
Number of PTF objects. The number of PTF objects available. The receiver variable may not have been large enough to hold all the PTF object records. If so, the number of PTF objects returned may be less than this value.
Check the format information available field returned in PTFR0100 before using this value. The number of objects will be zero when the system cannot determine the number of objects contained in this PTF.
Number of PTF subobjects. The number of PTF subobjects associated with this PTF object. The receiver variable may not have been large enough to hold all the PTF subobject records. If so, the number of PTF subobjects returned may be less than this value.
Number of requisites. The number of requisite PTFs available. The receiver variable may not have been large enough to hold all the requisite PTF records. If so, the number of requisites returned may be less than this value.
Check the format information available field returned in PTFR0100 before using this value. The number of requisites will be zero when the system cannot determine if this PTF has requisite PTFs.
Number of superseded PTF records. The number of superseded PTF records. The receiver variable may not have been large enough to hold all the superseded PTF records. If so, the number of superseded PTFs returned may be less than this value.
Check the format information available field returned in PTFR0100 before using this value. The number of superseded PTF records will be zero when the system cannot determine if this PTF has any superseded PTFs.
Number of symptom string records. The number of returned symptom string records.
Check the format information available field returned in PTFR0100 before using this value. The number of symptom strings will be zero when the system cannot determine if this PTF has symptom strings.
Object library. The primary library where PTF objects will be placed for this product. If the product was installed in the primary library, this is the library where the PTF objects will reside.
Note: If the product was installed in a library other than the primary library, the API user might need to determine the installed library that corresponds to this primary library by using format PRDR0200 of the Retrieve Product Information (QSZRTVPR) API.
Object name. The name of the object that is contained in the PTF.
Object type. The symbolic type of the object that is contained in the PTF.
Offset to additional information. The offset from the beginning of the receiver variable to the start of either the cover letter information or the requisite information. This is to allow expansion of the basic information.
Offset to exit program user data. The offset from the beginning of the receiver variable to the start of the exit program user data.
Offset to first APAR record. The offset from the beginning of the receiver variable to the start of the APAR record.
Offset to first cover letter record from the beginning. The offset from the beginning of the receiver variable to the first cover letter record.
Offset to first dependent PTF record. The offset from the beginning of the receiver variable to the start of the first dependent PTF record.
Offset to first exit program record The offset from the beginning of the receiver variable to the start of the first exit program record.
Offset to first precondition record. The offset from the beginning of the receiver variable to the first precondition record.
Offset to first PTF object record. The offset from the beginning of the receiver variable to the start of the PTF object record.
Offset to first requisite record. The offset from the beginning of the receiver variable to the start of the first requisite record.
Offset to first superseded PTF record The offset from the beginning of the receiver variable to the start of the first superseded PTF record.
Offset to first symptom string record. The offset from the beginning of the receiver variable to the start of the first symptom string record.
Offset to subobject name. The offset from the beginning of the receiver variable to the start of the subobject name.
Offset to symptom string data. The offset from the beginning of the receiver variable to the start of the symptom string data.
Offset to this PTF object's first subobject record. The offset from the beginning of the receiver variable to the start of the first PTF subobject record.
On-order status. Whether the PTF has been ordered. The following values are valid:
0 | The PTF has not been ordered or has already been received. |
1 | The PTF has been ordered. |
Post-apply or post-remove considerations. Whether the cover letter contains special instructions that should be followed after applying or removing the PTF.
0 | The PTF cover letter does not have any post-apply or post-remove considerations. |
1 | The PTF cover letter does have post-apply or post-remove considerations. |
9 | It is not known if the PTF cover letter has any post-apply or post-remove considerations. The most likely reasons are that the PTF cover letter was created prior to operating system release V5R1M0, or the cover letter was created using the System Manager licensed product. |
Pre-apply or pre-remove considerations. Whether the cover letter contains special instructions that should be followed prior to applying or removing the PTF.
0 | The PTF cover letter does not have any pre-apply or pre-remove considerations. |
1 | The PTF cover letter does have pre-apply or pre-remove considerations that should be followed regardless of how the PTF is applied or removed (either immediately or during an IPL). |
2 | The PTF cover letter does have pre-apply or pre-remove considerations, but only when the PTF is applied or removed immediately. |
3 | The PTF cover letter does have pre-apply or pre-remove considerations, but only when the PTF is applied or removed during an IPL. |
9 | It is not known if the PTF cover letter has any pre-apply or pre-remove considerations. The most likely reasons are that the PTF cover letter was created prior to operating system release V5R1M0, or the cover letter was created using the System Manager licensed product. |
Precondition library name. The name of the library for the precondition object. This field contains blanks when the precondition type is *JOB, *SBS, *RSTD, or *JVM.
Precondition name. The name of the object, job, or subsystem for which the precondition exists. The name can be either a specific name or a generic name. A generic name is a character string that contains one or more characters followed by an asterisk(*). The field contains blanks when the precondition type is *RSTD or *JVM.
Precondition record. The information about the precondition. Precondition records identify objects, jobs, or subsystems that cannot be active when this PTF is temporarily applied or removed immediately. The record is an array that contains the fields in format PTFR0900.
Precondition type. The type of the object indicated in the precondition name. Possible values are:
Object type | The precondition name specifies the name of an object of this type that exists in the precondition library. |
*JOB | The precondition name specifies the name of a job. |
*SBS | The precondition name specifies the name of a subsystem. |
*RSTD | The system must be in a restricted state to temporarily apply or temporarily remove this PTF immediately. |
*JVM | No Java virtual machines can be active on the system in order to temporarily apply or temporarily remove this PTF immediately. Any new Java virtual machines will be prevented from being started during the apply or remove processing. |
Product ID. The PTF is for this product. The product must be installed or supported.
Product option. The PTF is for this option of the product.
PTF ID. The identifier of the PTF.
PTF is released. Whether the PTF save file is available for distribution to another system. This is set to 1 only when the System Manager licensed product is on the system and the product is supported. The user needs to check the PTF save file status before using this field. Possible values are:
0 | The PTF save file cannot be distributed. |
1 | The PTF save file is released and can be distributed to another system. |
PTF object record. The information about the PTF objects. The record is an array that contains the fields described in format PTFR0400.
This information is available only if the PTF is loaded, temporarily applied, or has a save file.
PTF subobject record. The information about the PTF subobjects. The record is an array that contains the fields described in format PTFR0400.
PTF type. The type of PTF. The possible values are:
0 | PTF is delayed. The PTF must be applied at IPL time. |
1 | The PTF is immediate. The PTF can be applied immediately. No IPL is needed. |
Blank | The PTF type is not known. |
Release level. The release of the PTF. It must be in the format of VxRyMz. Valid entries for x and y are any number between 0 and 9. Valid entries for z is any number between 0 and 9 or a character between A and Z.
Release of dependent PTF. The release of the dependent PTF.
Release of requisite. The release of the requisite PTF.
Requisite is conditional. Whether the requisite relationship is conditional. Users should check this field to determine whether it is necessary to check a remote system for the presence of the software that is described in the product ID, release, option, and load ID.
0 | The requisite relationship is not conditional. The requisite PTF is required by this PTF on all systems that can use this PTF. |
1 | The requisite relationship is conditional. The requisite PTF is required by this PTF only on systems that contain the software described in the other fields. |
Requisite is required. Whether a requisite PTF is required on this system. The possible values are:
0 | The requisite PTF is not required with this PTF on this system. |
1 | The requisite PTF is required with this PTF on this system. |
Requisite load ID. The load ID of the requisite PTF. This value may be blank when the load ID of the requisite PTF cannot be determined.
Requisite option. The product option of the requisite PTF. This value may be blank when the option of the requisite cannot be determined.
Requisite maximum level. The indicator of the highest level of the product on which this PTF can be installed. This field will be blank if the product has no level.
Requisite minimum level. The indicator of the lowest level of the product on which this PTF can be installed. This field will be blank if the product has no level.
Requisite product ID. The product ID of the requisite PTF.
Requisite PTF ID. The PTF ID of the requisite PTF.
Requisite record. The information about the requisite. The record is an array that contains the fields in format PTFR0300.
Reserved. This field is ignored.
Save file status. Whether a save file exists for the PTF. This field should always be checked to determine if a save file exists. The following values are valid:
0 | The PTF has no save file. |
1 | The PTF has a save file. |
Server IPL required. Indicates whether or not a server IPL must be performed in order to activate the changes for the PTF. The possible values are:
0 | No server IPL is required to activate the changes for the PTF. |
1 | A server IPL must be performed using the T server IPL source in order to activate the changes for the PTF. |
2 | A server IPL must be performed using the P server IPL source in order to activate the changes for the PTF. |
Status date and time. The date and time the PTF status was last changed. This field will be blank when the status date and time is not available. The date and time field is in the CYYMMDDHHMMSS format:
C | Century, where 0 indicates years 19xx and 1 indicates years 20xx. |
YY | Year |
MM | Month |
DD | Day |
HH | Hour |
MM | Minute |
SS | Second |
Subobject attribute. The type of subobject contained in the PTF. The possible values follow:
DIR | The PTF subobject is a directory. |
DOC | The PTF subobject is a document. |
Subobject name. The name of the subobject. This is a name of an object that is not limited to 10 characters.
Superseded by PTF ID. The identifier of the PTF that has replaced this PTF. This field will be blank when the PTF is not superseded or when the superseding PTF has not been loaded on the system.
Superseded PTF ID. The identifier of a PTF that is superseded by this PTF.
Superseded PTF record. The information about the superseded PTFs. The record is an array that contains the fields in format PTFR1000.
Superseding PTF. The identifier of the most recent supersede of this PTF that exists on the system. This field will be blank when the PTF does not have a superseding PTF.
Symptom string data. The symptom string for the problems fixed by this PTF.
Symptom string record. The information about the symptom string. The record is an array that contains the fields in format PTFR0700.
Target release. The earliest release of the operating system on which you can load and apply the PTF. The release level is specified in the format VxRyMz, where Vx is the version, Ry is the release, and Mz is the modification level.
Type of dependent PTF. The type of dependent relationship. The possible values are:
1 | The PTF you are retrieving is a prerequisite for this PTF. |
2 | The PTF you are retrieving is a corequisite for this PTF. |
Type of requisite. The type of requisite relationship. The possible values are:
1 | The requisite PTF is a prerequisite of this PTF. It does not require this PTF. |
2 | The requisite PTF is a corequisite of this PTF. It does require this PTF. |
9 | The requisite PTF is a distribution requisite of this PTF. It requires this PTF for distribution purposes only. |
Message ID | Error Message Text |
---|---|
CPF0CB3 E | Value for reserved field not valid. |
CPF24B4 E | Severe error while addressing parameter list. |
CPF3CF1 E | Error code parameter not valid. |
CPF3C19 E | Error occurred with receiver variable specified. |
CPF3C20 E | Error found by program &1. |
CPF3C21 E | Format name &1 is not valid. |
CPF3C24 E | Length of the receiver variable is not valid. |
CPF3C90 E | Literal value cannot be changed. |
CPF35BE E | Product &1 &3 not supported or installed. |
CPF358A E | Release not valid. |
CPF3598 E | PTF function already in progress. |
CPF3902 E | PTF &1 located more than once. |
CPF6602 E | PTF &1-&2 &3 not found. |
CPF9872 E | Program or service program &1 in library &2 ended. Reason code &3. |
Top | Software Product APIs | APIs by category |