PTF Cover Letter
PTF ( Program Temporary Fixes ) Cover letter
F/QCPFLD-MSGCPF2962 PRTPUBAUT / PRTPVTAUT FAILS WITH MESSAGE
Pre/Co-Requisite PTF / Fix List
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM RELEASE NUMBER MIN/MAX OPTION
---- -------- --------- ------- ------- ------
NONE
NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels. This PTF may be a prerequisite
for future PTFs. By applying this PTF you authorize and agree to the
foregoing.
This PTF is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are obtaining
the PTF. You are not authorized to install or use the PTF except as part
of a Program for which you have a valid Proof of Entitlement.
SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.
The applicable license agreement may have been provided to you in printed
form and/or may be viewed using the Work with Software Agreements (WRKSFWAGR)
CL command.
APAR Error Description / Circumvention
-------------------------------------------------
PRTPUBAUT / PRTPVTAUT fails with message CPF2962 when there's
other library on top of QSYS w/ object QAOBJAUT and it has
different CCSID with QUSRSYS/QPB* and QUSRSYS/QPV* files.
CORRECTION FOR APAR 'SE64226' :
-------------------------------
When upgrading the QPB*/QPV* files to accommodate new fields
found in the QAOBJAUT model outfile the model outfile in QSYS is
used when instead, the model outfile in *LIBL should be used. A
change will be made so that the model outfile QAOBJAUT in *LIBL
is used.
CIRCUMVENTION FOR APAR 'SE64226' :
----------------------------------
None.
Activation Instructions
None.
Special Instructions
On 7.2 systems where PRTPUBAUT / PRTPVTAUT has already been run for
object types that had existing QUSRSYS/QPB* and QUSRSYS/QPV* files, the
existing QPB* and QPV* files will need to be deleted or the CCSIDs
changed if the CCSIDs do not match the CCSID of the first occurrence of
the QAOBJAUT file in the library list. An exception to this are object
types *FLR, *DOC and file system object types. The corresponding
QUSRSYS/QPB* and QUSRSYS/QPV* files for these object types do not need
to be deleted or have their CCSIDs changed since they do not use model
outfile QAOBJAUT.
On 7.2 systems that have not yet run PRTPUBAUT / PRTPVTAUT for any
object types for which there is an existing QUSRSYS/QPB* or
QUSRSYS/QPV* file no additional action is needed.
Default Instructions
THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
Supersedes
PTF/FIX NO(S). APAR TITLE LINE
-------------- ------------------------------------------------------------
NONE
Summary Information
System.............................. | i |
Models.............................. | |
Release............................. | V7R2M0 |
Licensed Program............... | 5770SS1 |
APAR Fixed.......................... | View details for APAR SE64226 |
Superseded by:...................... | |
Recompile........................... | N |
Library............................. | QSYS |
MRI Feature ........................ | NONE |
Cum Level........................... | C6306720 |
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information.
Was this topic helpful?
Document Information
Modified date:
08 March 2016