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 Runtime
Created by Guest
Created on Jul 15, 2015

Cics Liberty Double Log Output

At the moment it is only possible to print the output of Liberty to JES or to ZFS.
We have the situation, that the developers prefer the ZFS (Unix/in their world Linux) Output, but we want to archive the output into Beta Systems BETA 92 Tool. This means we want put the output to Jes.

It would be great to have the possibility to write both.

Idea priority Medium
  • Guest
    Reply
    |
    Jul 6, 2016

    This functionality is available as part of the logging changes made in CICS TS 5.3

  • Guest
    Reply
    |
    Apr 26, 2016

    Peter, have you had chance to try out the logging changes provided in CICS TS 5.3 ?

  • Guest
    Reply
    |
    Jan 19, 2016

    As there are changes in Logging and 5.3 we will install the new System and have a look if this fits better.

    Regards Peter

  • Guest
    Reply
    |
    Jan 14, 2016

    Peter do you have a response to this ?

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |
    Jul 21, 2015

    At the Moment we are mostly interested in messages.log, so I will try your Suggestion to Redirect the Output to have both. As we are currently installing the System from zero I would say I need all the Output in both Locations, but not in every stage. So it demands on, where I am (Test/Production/...).

    I think I will start with what you suggested and during the Progress of the first Project (currenly in Test) I will update the RFE..

    thanks for reply

    Peter

  • Guest
    Reply
    |
    Jul 20, 2015

    Which specific output files were you interested in? A JVM server controls three main files, 'dfhjvmout' intended for user-application output, 'dfhjvmerr' to contain stacktraces of exceptions/abends, and 'dfhjvmtrc' which is designed for IBM service use.

    There are also Liberty output files where Liberty runs within the JVM server, for example 'messages.log' and 'trace.log' - these outputs are only available on zFS (not JES). Having said that, if you are interested in messages.log specifically and not other output, then it is possible to duplicate messages.log into dfhjvmout using -Dcom.ibm.ws.logging.console.log.level=INFO in the JVM profile. By doing this and redirecting STDOUT to JES in your JVM profile you can achieve output in both locations.