Well, if you do a 

... where JOB_ENTERED_SYSTEM_TIME is null

does that only shows the rows with plus signs or is there a mix?

I would think this function would have to match the CPF1164 message with it's matching CPF1124 message like the following:

CPF1124: Job 146476/QSYS/QYMEARCPMA started on 06/26/24 at 00:00:02 in subsystem QSYSWRK in QSYS. Job entered system on 06/26/24 at 00:00:02.

CPF1164: Job 146476/QSYS/QYMEARCPMA ended on 06/26/24 at 00:00:03; .146 seconds used; end code 0

And if the job has been running longer than your purge interval on your history log, then I can see how those columns would be null.

GO CLEANUP     

1. Change cleanup options

System journals and system logs . . . . . . . .   30

Hi Robert,

I try with the clause "where JOB_ENTERED_SYSTEM_TIME  is null". The query failed with error 6 

SQL status : 22023

Provider code: -802 Message: [SQL0802] Data conversion or mapping error

Error 6  which mean Incorrect numeric data

I've look at a job with the two CPF1124 & CPF1164 in dsplog, the same i've the columms with ++++++++++++ and only ++++++++++++ no other characters for all job.

Well, if you do a 

... where JOB_ENTERED_SYSTEM_TIME is null

does that only shows the rows with plus signs or is there a mix?

I would think this function would have to match the CPF1164 message with it's matching CPF1124 message like the following:

CPF1124: Job 146476/QSYS/QYMEARCPMA started on 06/26/24 at 00:00:02 in subsystem QSYSWRK in QSYS. Job entered system on 06/26/24 at 00:00:02.

CPF1164: Job 146476/QSYS/QYMEARCPMA ended on 06/26/24 at 00:00:03; .146 seconds used; end code 0

And if the job has been running longer than your purge interval on your history log, then I can see how those columns would be null.

GO CLEANUP     

1. Change cleanup options

System journals and system logs . . . . . . . .   30

At one time you used to be able to search PTF cover letters.  There's still a site for this but it really no longer works.  I tried to submit feedback on it today but it seems non responsive.  Other IBM sites are having issues too so... But here is the ptf cover letter site. https://www.ibm.com/support/pages/access-ptf-cover-letters  I really tried to find a PTF which matches the issue but the search is upsetting me and I've got "real" work to do.

Today I am actually updating our sandbox P10.  I am putting the latest TR, cume, firmware and vios updates on.

In summary:  If you can put on PTF's I would strongly recommend you do so.  If you still have the issue, open a case with IBM.  

Hi Robert,

I try with the clause "where JOB_ENTERED_SYSTEM_TIME  is null". The query failed with error 6 

SQL status : 22023

Provider code: -802 Message: [SQL0802] Data conversion or mapping error

Error 6  which mean Incorrect numeric data

I've look at a job with the two CPF1124 & CPF1164 in dsplog, the same i've the columms with ++++++++++++ and only ++++++++++++ no other characters for all job.

Well, if you do a 

... where JOB_ENTERED_SYSTEM_TIME is null

does that only shows the rows with plus signs or is there a mix?

I would think this function would have to match the CPF1164 message with it's matching CPF1124 message like the following:

CPF1124: Job 146476/QSYS/QYMEARCPMA started on 06/26/24 at 00:00:02 in subsystem QSYSWRK in QSYS. Job entered system on 06/26/24 at 00:00:02.

CPF1164: Job 146476/QSYS/QYMEARCPMA ended on 06/26/24 at 00:00:03; .146 seconds used; end code 0

And if the job has been running longer than your purge interval on your history log, then I can see how those columns would be null.

GO CLEANUP     

1. Change cleanup options

System journals and system logs . . . . . . . .   30

Thank you Robert,

I will do that.

Regards

At one time you used to be able to search PTF cover letters.  There's still a site for this but it really no longer works.  I tried to submit feedback on it today but it seems non responsive.  Other IBM sites are having issues too so... But here is the ptf cover letter site. https://www.ibm.com/support/pages/access-ptf-cover-letters  I really tried to find a PTF which matches the issue but the search is upsetting me and I've got "real" work to do.

Today I am actually updating our sandbox P10.  I am putting the latest TR, cume, firmware and vios updates on.

In summary:  If you can put on PTF's I would strongly recommend you do so.  If you still have the issue, open a case with IBM.  

Hi Robert,

I try with the clause "where JOB_ENTERED_SYSTEM_TIME  is null". The query failed with error 6 

SQL status : 22023

Provider code: -802 Message: [SQL0802] Data conversion or mapping error

Error 6  which mean Incorrect numeric data

I've look at a job with the two CPF1124 & CPF1164 in dsplog, the same i've the columms with ++++++++++++ and only ++++++++++++ no other characters for all job.

Well, if you do a 

... where JOB_ENTERED_SYSTEM_TIME is null

does that only shows the rows with plus signs or is there a mix?

I would think this function would have to match the CPF1164 message with it's matching CPF1124 message like the following:

CPF1124: Job 146476/QSYS/QYMEARCPMA started on 06/26/24 at 00:00:02 in subsystem QSYSWRK in QSYS. Job entered system on 06/26/24 at 00:00:02.

CPF1164: Job 146476/QSYS/QYMEARCPMA ended on 06/26/24 at 00:00:03; .146 seconds used; end code 0

And if the job has been running longer than your purge interval on your history log, then I can see how those columns would be null.

GO CLEANUP     

1. Change cleanup options

System journals and system logs . . . . . . . .   30

Hi.

The SYSTOOLS.ENDED_JOB_INFO table function is interpreting the message data in CPF1164 messages, but it gets the date wrong if you're not in US with dates on format MMDDYY!

IBM should fix this - requires some to report this issue - but meanwhile you can extract the source for SYSTOOLS.ENDED_JOB_INFO, change the code to correctly interpret your date format and create your fixed ENDED_JOB_INFO table function in a schema of your own.

HTH.

Best regards,

Christian

Hi,

Yes, It's not US version.

I have updated the DB2 PTFs on the partition, but I have the same thing. So I opened a case with IBM support

Thanks to all.

Best regards

Hi.

The SYSTOOLS.ENDED_JOB_INFO table function is interpreting the message data in CPF1164 messages, but it gets the date wrong if you're not in US with dates on format MMDDYY!

IBM should fix this - requires some to report this issue - but meanwhile you can extract the source for SYSTOOLS.ENDED_JOB_INFO, change the code to correctly interpret your date format and create your fixed ENDED_JOB_INFO table function in a schema of your own.

HTH.

Best regards,

Christian

Tried to recreate the error with:

cl: CHGJOB DATFMT(*YMD) ;
select * from table (SYSTOOLS.ENDED_JOB_INFO( START_TIME => CURRENT DATE - 1 DAYS);

But that didn't seem to do it.  Too bad, that would have been an easy work around.

Hi,

Yes, It's not US version.

I have updated the DB2 PTFs on the partition, but I have the same thing. So I opened a case with IBM support

Thanks to all.

Best regards

Hi.

The SYSTOOLS.ENDED_JOB_INFO table function is interpreting the message data in CPF1164 messages, but it gets the date wrong if you're not in US with dates on format MMDDYY!

IBM should fix this - requires some to report this issue - but meanwhile you can extract the source for SYSTOOLS.ENDED_JOB_INFO, change the code to correctly interpret your date format and create your fixed ENDED_JOB_INFO table function in a schema of your own.

HTH.

Best regards,

Christian

Hi Robert,

IBM Tech Support France give me an SQL function to bypass this problem. As Christian says it 's not a problem for OS in US version, but a problem for some other country.

I've try your query, not work, Ihave also +++++++++++++++. I've also try to modify parameters in strsql  and services (F13) bfore open a case, you can modify date and time with no success.

Best Regards

Tried to recreate the error with:

cl: CHGJOB DATFMT(*YMD) ;
select * from table (SYSTOOLS.ENDED_JOB_INFO( START_TIME => CURRENT DATE - 1 DAYS);

But that didn't seem to do it.  Too bad, that would have been an easy work around.

Hi,

Yes, It's not US version.

I have updated the DB2 PTFs on the partition, but I have the same thing. So I opened a case with IBM support

Thanks to all.

Best regards

Hi.

The SYSTOOLS.ENDED_JOB_INFO table function is interpreting the message data in CPF1164 messages, but it gets the date wrong if you're not in US with dates on format MMDDYY!

IBM should fix this - requires some to report this issue - but meanwhile you can extract the source for SYSTOOLS.ENDED_JOB_INFO, change the code to correctly interpret your date format and create your fixed ENDED_JOB_INFO table function in a schema of your own.

HTH.

Best regards,

Christian