Apologies, we are on 6.1 – V6R1M0
I read about how to determine your cumulative PTF number (http://www.itjungle.com/tfh/tfh100603-story04.html
), but I may have it wrong… DSPPTF LICPGM(5761SS1) shows the highest one being TC13058 which is Temporarily Applied. From that I think the cumulative PTF level is C13058610.
I don’t know what a tech refresh is but this redbook (http://www.redbooks.ibm.com/redbooks/pdfs/sg247858.pdf
) says I can find the Technology Refresh PTF Group level with WRKPTFGRP. The highest installed PTF Group on that screen is SF99609.
Thank you for your patience,
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Wednesday, May 14, 2014 6:25 AM
To: Sarah Kemp
Subject: Re: SQLRPGLE Service Program Activation and GET DIAGNOSTICS
Still need to know OS level. :)
On Tue, May 13, 2014 at 7:19 PM, Sarah Kemp <Sarah@xxxxxxxxxxxxxxxx<mailto:Sarah@xxxxxxxxxxxxxxxx>> wrote:
I will keep my question here brief and link to a more detailed version so the code is readable.
I am implementing SQL error handling based on this page: https://www.ibm.com/developerworks/community/forums/html/topic?id=d2c49b79-5a01-46f7-9a11-b9de0f2b0e02#3b47a829-e864-44db-99c4-653a7547add2
GET DIAGNOSTICS is incorrectly returning an SQLSTATE of 00000 when it is first called in a newly activated service program. All subsequent calls return correctly. Executing an otherwise unnecessary SQL statement beforehand eliminates the issue. The service program containing the GET DIAGNOSTICS statement is bound-by-reference to the service program containing the erroring SQL statement and activates *IMMED in group *CALLER.
Please see my full question here: http://stackoverflow.com/questions/23643045/initialize-activate-sql-prior-to-get-diagnostics
I will be happy to answer my own question on that site with any information sent to this list.
Thanks for reading,
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives