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 Is a defect
Categories Commands
Created by Guest
Created on Feb 18, 2014

QUERY TIMESTAMP output order

The output order of the TimeStamp fields (TimeCreate, TimeUpdate, TimeAccess, TimeImport) is different for QUERY TRAN, QUERY PGM, QUERY DB (we don't use Fast Path, so I don't know about routing codes).
QUERY TRAN NAME(xxxxxxxx) SHOW(TIMESTAMP) has these fields in the order: TimeAccess, TimeUpdate, TimeCreate, TimeImport
QUERY PGM NAME(xxxxxxxx) SHOW(TIMESTAMP) has these fields in the order: TimeCreate, TimeUpdate, TimeAccess, TimeImport
QUERY DB NAME(xxxxxxxx) SHOW(TIMESTAMP) has these fields in the order: TimeCreate, TimeUpdate, TimeAccess, TimeImport

The output order of the TimeStamp fields with TRAN is inconsistent with PGM or DB.

It would be helpful if these fields were output in the same order for all resources.

Idea priority Low
  • Guest
    Reply
    |
    Aug 26, 2014

    Hello Derek,

    Thank you for submitting this IMS enhancement request.
    After giving the request a comprehensive review, we have determined this is a defect and a PMR
    66541,004,000 has been open and this is addressed in a FIN APAR PI22018. As a consequence we have, unfortunately, closed this request.

    We appreciate your input to the IMS development team. We also hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of IMS.

    Sincerely,
    Anu Vakkalagadda

  • Guest
    Reply
    |
    Mar 4, 2014

    Hello Derek,
    I could not find any rationale on why the order of timestamps on TRAN differ from the order of timestamps on DB, PGM and RTC. The timestamps returned on SHOW(TIMESTAMP) or SHOW(ALL) were added in IMS V10 with DRD. The consistency in output order was not maintained. We cannot change the order of the columns at this time as the change can impact customer automation.

    The local timestamps are obtained from the IMS runtime blocks on the QUERY commands. When you use DRD with either the RDDS or the IMSRSC repository the QUERY commands with SHOW(TIMESTAMP) will return the same information.

    When IMS is enabled with DRD with IMSRSC repository we have a new SHOW(DEFN) on the QUERY commands. The QUERY commands with SHOW(DEFN) or SHOW(DEFN,TIMESTAMP) will also return the create and update timestamps from the repository. So if you plan to use SHOW(DEFN) you need to ensure the repository timestamps are also in the order you prefer them to be in.

    regards,
    Anu Vakkalagadda

  • Guest
    Reply
    |
    Mar 3, 2014

    Making our own OM output user exit would be doable, though that wasn't really what I was hoping for when I opened the RFE. Maybe if I understood why it was decided to have the order different between tran and PGM/DB, then I could be more sympathetic.
    Also, I should have mentioned we are currently using the RDDS, with plans to go to the IMSRSC sometime in the future. I'm assuming the timestamp output order is the same between RDDS and IMSRSC.

  • Guest
    Reply
    |
    Feb 26, 2014

    Hello Derek, Thank you for opening the RFE.

    The order of the command output headers can be modified by you by writing your own OM output exit.  You can link in an OM output exit which modifies the order of the TIMESTAMP headers for the QUERY TRAN command.  The OM output exit documentation is in:
    http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.ims12.doc.err/ims_cslom_output.htm
    The TimeStamp headers for QUERY TRAN are built by IMS as follows:                                                               
     scroll="yes" len="20" dtype="CHAR" align="left" skipb="no" />     
     scroll="yes" len="20" dtype="CHAR" align="left" />                
     scroll="yes" len="20" dtype="CHAR" align="left" />                
     scroll="yes" len="20" dtype="CHAR" align="left" />                
    In your OM output exit when you receive the command response for QUERY TRAN you will need to modify the headers to:
     scroll="yes" len="20" dtype="CHAR" align="left" />                
     scroll="yes" len="20" dtype="CHAR" align="left" />                
     scroll="yes" len="20" dtype="CHAR" align="left" skipb="no" />     
     scroll="yes" len="20" dtype="CHAR" align="left" />                        
    You will also need to set the OOUX_OUTMDLEN to the same value as OOUX_OUTPTLEN and
    set that output was modified in OOUX_OUTMOD by setting it to OOUX_CHNGOUT. When OM sends the modified output you will see that the order of the columns in the output is modified to what you want to see.
    Please update the RFE if the proposed change works for you.
    regards,
    Anu Vakkalagadda
    IMS Development