MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2014

RE: CPF5009 , CPF5026, SQL9015 , MCH3601, MCH0601



fixed

Chuck,

I shouldn't have stated "test" ptf, but support is calling it a "TRAP" ptf.

Yes, there will be a normal TEST PTF out at some point and later a GA. The APAR created is SE59455.
Keep using TRAP PTF PTF SQPAH06 until then.

================================================================================
= APAR: SE59455 Status: INTRAN =
================================================================================

--------------------------------------------------------------------------------
- Abstract APAR SE59455 -
--------------------------------------------------------------------------------
OSP-DB-OTHER-F/QDBSIGEX-T/QSQPROCR-MSGCPF5009 MSGCPF5009
MSGCPF5026 MSGCPF5026 MSGSLQ0915 MSGMCH3601 T/QSQPROCR

--------------------------------------------------------------------------------
- Summary Page APAR SE59455 -
--------------------------------------------------------------------------------
STATUS INTRAN
SYMPTOM MS
KEYWORD MSGCPF5009
INITIAL COMP ID 5770SS1DB
SEVERITY 2

--------------------------------------------------------------------------------
- Submitter Page APAR SE59455 -
--------------------------------------------------------------------------------
ERROR DESCRIPTION:
msgCPF5009 F/QDBSIGEX T/QSQPROCR
msgCPF5026 F/QDBSIGEX T/QDBSIGEX
msgCPF5026 F/QSBSIGEX T/QSQPROCR
msgSLQ0915 F/QSQPROCR T/QLICRDUP
msgMCH3601 F/#rmsacs T/QSQPROCR

Stored procedure registration issue


It won't have the developer's comments until the PTF comes out.

Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, June 20, 2014 2:15 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CPF5009 , CPF5026, SQL9015 , MCH3601, MCH0601

On 19-Jun-2014 12:58 -0500, Steinmetz, Paul wrote:
IBM created test PTF SQPAH06. <<SNIP>>

FWiW: I am almost positive... That identifier must not be a TEST PTF; rather, that must be a TEST FIX. A distinction with a *big* difference.

* The former [upper-cased] term implies an intent that the PTF eventually would become a final\Generally-Available (GA) PTF that any\all customers might eventually apply; such a PTF can be permanently applied [accidentally, due to lack of necessary controls implemented on the system to prevent that effect], with the potential requirement of a reinstall of the OS [or LPP] to recover, if the specific code-level of that version of the PTF by that name\identifier will not become GA. A TEST PTF will use the same naming convention of the other PTFs for the feature; e.g. the OS or LPP.

* The latter term implies code was generated specifically to investigate\debug an issue, often to effect debug on a specific customer system, whereby that code-level and the /PTF/ that provided the code, will not be available to any other customer; a TestFix will never become GA, and the PTF apply-processing feature explicitly prevents accidental perm-apply.

--
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact