× 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, Birgitta!  Vern implied the same thing.  I was just hoping for a different answer. :)  I'll use another approach.  As it is, I can create a DDS file with a timestamp and select into it from an SQL view with TIMESTAMP(0) and everything works fine.  So that's one option.

On 4/28/2021 12:36 PM, Birgitta Hauser wrote:
DDS is stabilized since release V5R3M0.
TIMESTAMP(0) was not introduced (in SQL) before Release 7.2.
So, no, there is no way to define Timestamp(0) in DDS.
The only way IMHO is, to create a character column and insert the timestamp(0) value into this character column or a 14P 0 column and convert the timestamp value into a numeric value before you insert it.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser


"Shoot for the moon, even if you miss, you'll land among the stars." (Les Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them and keeping them!"
„Train people well enough so they can leave, treat them well enough so they don't want to.“ (Richard Branson)


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Joe Pluta
Sent: Mittwoch, 28. April 2021 18:59
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: TIMESTAMP(0) in DDS

Sorry, I replied to an unrelated messaged rather than creating a new message. Not sure why. Long day.

---

Once again, I'm in a position where I'm doing something that hurts. ("Doctor, it hurts when I do this..." "Well, don't do that!") I have an SQL defined file with a timestamp. However, it's specified as TIMESTAMP(0). I'd like to create a DDS-defined file that mirrors this. However, it I can't seem to find a way to specify the optional length for a timestamp field (type Z), so it used the default of TIMESTAMP(6) which creates a larger field.

Does anyone know if I can do this? Plan B is to use DDL, which should probably have been Plan A anyway, but now this has become personal.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.