Skip to Main Content
IBM Z Software


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).


Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Status Delivered
Categories z/TPF
Created by Guest
Created on Oct 20, 2022

(TPFUG) Support tpf_STCKE_to_timet and tpf_timet_to_STCKE

The tpf_STCK_to_timet and tpf_timet_to_STCK APIs convert an 8 byte TOD format used by STCK/STCKF to a time_t and vice versa. But the 8 byte TOD format will wrap in 2042. As part of the strategy to remediate existing date problems and avoid new ones, we need APIs to convert the 16 byte TOD format used by STCKE to a time_t and vice versa.

We have application logic that tries to set a TOD purge date for today + 20 years so we are already encountering problems with 8 byte TOD wrap.

This part of the request is "urgent" priority.


In addition, the tpf_STCK_to_timet API returns a negative time_t value if passed a wrapped TOD, and will return a wrapped TOD if passed a time_t value of > 2294610827. Neither API supports the concept of an error. It would be helpful to get some clarification on what the "correct" behavior of these APIs should be for date/time after 9/17/2042 23:53:47. Maybe wrapping is the correct behavior! This part of the request is "medium/high" priority.

Idea priority Urgent
  • Guest
    Reply
    |
    Jan 13, 2023
    This support is now available with z/TPF APAR PJ46952.