Log Program Temporary Fix Information (QPZLOGFX) API

The Log PTF Information (QPZLOGFX) API allows you to specify the device from which PTFs are loaded as *SERVICE. You can use the QPZLOGFX API to indicate that a PTF or cover letter should be put into device *SERVICE.

PTFs are put into *SERVICE when they are received on the system using the Copy PTF Save File (CPYPTFSAVF) or Send PTF Order (SNDPTFORD) command. These commands put information about the PTF into the PTF database files so that the PTF can be displayed with the Display PTF (DSPPTF) command. The PTF is then loaded from device *SERVICE using the Load PTF (LODPTF) command. PTFs received on the system by any other method are not in *SERVICE.

The PTF must exist in a save file with a valid name in the designated PTF library before this API is called. If the PTF is put in a save file with a name that is being used by another PTF, an error (CPF35BD) occurs. The save file must be deleted or renamed. Checking is done to ensure that the correct library is being used.

The cover letter must exist in the designated PTF cover letter file with a valid member name before this API is called. If the member name is being used by another PTF, an error (CPF35FE) will occur; you must delete the member or rename it.

The product the PTF is for must be installed or supported.

The save file or member name must be Q plus the PTF ID. If that name is being used by another PTF that is in *SERVICE, you must select another name.

Authorities and Locks

API Public Authority

*EXCLUDE

Required Parameter Group

PTF information

INPUT; CHAR(50)

The information needed to put the PTF into device *SERVICE. If the information specified here does not match the information in the member or save file specified on the qualified file name parameter, an error occurs (CPF35E6). A check is done to verify that the PTF ID, product ID, and release specified here match the PTF ID, product ID, and release of the cover letter or PTF. For more information about this parameter see PTF Information Format.

Request type

INPUT; CHAR(10)

The type of log operation to be done.

The possible values are:

*LOGPTF	The PTF is to be put in device *SERVICE. Product information from the save file is checked against the product information passed into this API. Therefore, the PTF must exist in the save file specified on the qualified file name parameter.
*LOGCVR	A cover letter is to be put in device *SERVICE. The cover letter must exist in the library, file, and member specified in the qualified file name and member name parameters. Information from the member is checked against the product information passed into the API.

Qualified file name

INPUT; CHAR(20)

The file where the cover letter or PTF is located. If the request type parameter is *LOGPTF, then this is the save file name and library name where the PTF is located. If the request type is *LOGCVR, then this is the file and library that contain the cover letter. The first 10 characters are the file name and the second 10 characters are the library name.

Member name

INPUT; CHAR(10)

The member that contains the cover letter. This parameter is ignored if the request type parameter is *LOGPTF.

Error code

I/O; CHAR(*)

The structure in which to return error information. For the format of the structure, see Error Code Parameter.

PTF Information Format

For a description of these fields, see Field Descriptions.

Field Descriptions

Product ID. The product that the PTF or the cover letter is for.

PTF ID. The identifier of the PTF.

Release level. The version, release, and modification level of the PTF. The release must be in the format VxRyMz. Valid values for x and y are 0 through 9, and valid values for z are 0 through 9 or A through Z.

Reserved. This field must be blank.

Error Messages