This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
this was delivered as part of 5.2 - REPATTERN now uses microsecs rather than secs as its intermediate value and thus avoids the problems of converting between decimal and float binary
As part of APAR PI75582 / PTF UI44364, these built-in functions are now supported
This requires the appropriate PTFs for the library APARs PI66445 & PI67787
MICROSECS
MICROSECS returns a FIXED BIN(63) value that is the number of microseconds corresponding to the date d.
Its syntax diagram etc is the same as that for the SECS built-in function except
If d is omitted, it is assumed to the value returned by TIMESTAMP()
If p is omitted, it is assumed to be the TIMESTAMP pattern, namely 'YYYY-MM-DD-HH.MI.SS.999999'
MICROSECSTODATE
MICROSECSTODATE returns a nonvarying character string containing the date in the date/time pattern specified by p that corresponds to m microseconds.
Its syntax diagram etc is the same as that for SECSTODATE except
m should be used for d
m is converted to FIXED BIN(63) if necessary
if p is omitted, it is assumed to be the TIMESTAMP pattern, namely 'YYYY-MM-DD-HH.MI.SS.999999'
MICROSECSTODAYS
MICROSECSTODAYS returns a FIXED BIN(31) value that represents the number of microseconds x converted to days, ignoring incomplete days.
x must have a computational type and will be converted to FIXED BIN(63) if necessary.
MICROSECSTODAYS(x) is the same as x/(24*60*60*1_000_000).
DAYSTOMICROSECS
DAYSTOMICROSECS returns a FIXED BIN(63) value that is the number of microseconds corresponding to the number of days x.
x must have a computational type and will be converted to FIXED BIN(31) if necessary.
DAYSTOMICROSECS(x) is the same as x*(24*60*60*1_000_000).
UTCMICROSECS
UTCMICROSECS returns a FIXED BIN(63) value that gives the current UTC time in microseconds.
This built-in function has no arguments.
And, if you're going to implement them anyway, plain MICROSECS() would from a readability point of view better be named DATETOMICROSECS() / DATE2USECS()...
Can we please also have abbreviated forms of these functions,
-MICROSECS() - USECS()
-MICROSECSTODATE() - USECS2DATE()
-MICROSECSTODAYS() - USECS2DAYS()
-DAYSTOMICROSECS() - DAYS2USECS()
-UTCMICROSECS() - UTCUSECS()
in retrospect, it would have been better if float had never been returned in the date time functions