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.

Add a new idea Subscribe
Status Not under consideration
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on Sep 4, 2016

RELATED IDEAS

JVM messages prefixed with timestamps

To day messages from JVM in CICS TS are not prefixed with timestamps.
The messages issued from JVM in neither HFS/ZFS directories pointed to JVMprofile, nor if redirected to STDOUT, STDERR, STDTRC contains any timestamps(DATE/TIME).

It would be of great benefit if they were prefixed with timestamps, and it would be of great help in debugging.
It would be easier to related messages to events happended. e.g.transactions , other error messages , alerts. e.t.c.

You should be able to implement timestamps to be prefixed to all kind of JVM messages , also application driven , via a parameter in JVMprofile or a SIT parameter.

Idea priority High
  • Guest
    Reply
    |     May 17, 2017

    CICS time stamps its messages. See previous comment as regards Liberty produced messages.

  • Guest
    Reply
    |     May 11, 2017

    The output seen in the provided stdout attachment is produced by Liberty (rather than CICS) and is a console replication of Liberty's actual message.log. It is typically used when a short-lived manually controlled Liberty server is run from the command-line. For a fully time-stamped output in a CICS environment, the customer should refer to Liberty's message.log instead (typically .../wlp/usr/servers/defaultServer/logs/message.log).

    Perhaps the customer had hoped that the console replica would include time-stamps? it doesn't because it wasn't designed by Liberty as a log. Customer should use message.log instead to see time-stamps.

    The output in stderr is also output from Liberty and not under CICS control. However, the same error will be written to the message.log along with ffdc files (where it would all be appropriately time-stamped).

    It is also worth note that Liberty 8.5.5.8 introduced logging of some key Liberty messages application lifecycle msgs to the syslog, which will appear in the CICS job log with timestamps and there is an open liberty requirement to make this list configurable. - see http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=85364

  • Guest
    Reply
    |     Sep 19, 2016

    Please could we have some more information as to which messages you are referring to?

    All JVM server 'messages' go to CICS and are timestamped. Only trace goes to zFS and the JVM trace (dfhjvmtrc on zFS) is fully timestamped.
    As far as STDOUT is concerned, this is for user messages only (not CICS) and so user code would have to do their own timestamping for their own messages.
    As far as STDERR is concerned, this is made up of:
    a) 'raw output' from the JVM that we don't control and can't timestamp
    b) output from CICS Java, which is already timestamped
    c) output from CICS C code, which we don't timestamp (and could) but the entries are very rare

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.