Re: TO_CHAR VARCHAR_FORMAT enhancement for numeric editing format-string -- MIDRANGE-L

Subject: Re: TO_CHAR VARCHAR_FORMAT enhancement for numeric editing format-string
From: Dan <dan27649@xxxxxxxxx>
Date: Wed, 12 Oct 2016 10:38:50 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

FWIW, our v7r1 box:

PTF GrpLvl Desc
SF99701 40 DB2 FOR IBM I
SF99707 11 TECHNOLOGY REFRESH
SF99709 171 GROUP HIPER
SF99710 16120 CUMULATIVE PTF PACKAGE C6120710

- Dan

On Tue, Oct 11, 2016 at 9:16 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

I was curious about 7.1, as well - the SQL Reference at Knowledge Center
has this bit -

What's new as of April 2016

* Additional formatting options for TIMESTAMP_FORMAT and
VARCHAR_FORMAT scalar functions.

So it appears that some kind of update as of April this year provided the
other capabilities, including character to varchar, timestamp to varchar,
and number to varchar.

Now to get whatever update is needed to activate these things!

Vern

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.