Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Apr 17, 2018

Large number of joblogs produced

We are using Infor XA

When jobs run, instead of producing one joblog, they are producing many joblogs of approx. 100 pages. We have examples where hundreds of joblogs are produced. If there is an issue and Infor want the joblog, it is not practical to provide all these joblogs or for someone to review them looking for error messages.

There didn't us to be the case. It has only happened in recent years.

Please increase the size of the joblogs

Use Case:

See above

Idea priority Medium
  • Guest
    Sep 13, 2019

    The algorithm use to implement the *PRTWRAP function in a joblog must find a balance between removing enough messages to perform the wrap, but not taking so long removing messages that it can't keep up with the PQS threshold exceeded events. To accomplish this balance, we remove about 1 megabyte of messages at a time. This has not changed since *PRTWRAP was first implemented, however there are other factors that can affect the size of the printed joblog. Some messages that take up space in the PQS are not printed in the joblog, for example, status messages. So the printed portion of the wrapped joblog may not necessarily show all the messages that were removed from the internal job message queue. Additionally, not every message is necessarily able to be removed during a wrap, for example, scope messages, unanswered inquiry or notify messages, or messages with an action pending such as a request message. In some situations a job may be in a loop that fills the joblog with these types of messages, and we may not be able to remove the desired amount of messages during the wrap. While I can sympathize with the annoyance of many smaller joblogs, the alternative of removing all the messages at once may produce unexpected and unpleasant results.