Re: SQL's TIMESTAMP_FORMAT causes MCH3601 -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Thanks Branston! I've advised our admin on SI61084 as well.

- Dan

On Thu, Jan 26, 2017 at 7:30 PM, Branston DiBrell <
b.dibrell@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Yes, as a matter of fact. Also, we also ended up applying PTF SI61084 as
well - followed by an IPL. We didn't under the direction of IBM Support.

-Branston DiBrell, Jr - b.dibrell@xxxxxxxxxxxxxxxxxx
Peerless Tires 4 Less, IT Department, Denver CO - 720-274-0632

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Thursday, January 26, 2017 3:46 PM
To: Midrange Systems Technical Discussion
Subject: Re: SQL's TIMESTAMP_FORMAT causes MCH3601

Thanks Branston! Just to confirm, you were getting MCH3601 and CPF503E
errors, and CPF503E pointed to the TIMESTAMP_FORMAT function?

I confirmed that we do not have SI62554 installed on our system. I'll ask
our admin to look for it.

- Dan

On Thu, Jan 26, 2017 at 5:02 PM, Branston DiBrell <
b.dibrell@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Dan,

We had the same issue several months ago. We ended up installing a PTF
(PTF SI62554) to (eventually) fix the problem. We're on v7.1.

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.