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 AIX
Created by Guest
Created on Aug 21, 2015

Need large file support for /var/adm/cfglog beyond 256MB limit to avoid cfglog corruption

PMR 03490,L6Q,000 / 17292,L6Q,000

Currently AIX does not support changing cglog size using alog.

Problem description

We were doing 16 CC LPM loop test on 2 MMD systems. As we need
had to enable detailed logging, we tried to change the default
cfglog size using:

"alog -C -t cfg -s 10485760 -w 9" to
"alog -C -t cfg -s 1000001536 -w 9"

It failed after 6 successful loops.

We could see the problem and found the size of 268435456 for

For eg:

By displaying the last 10 lines of the log, we could see:
(when the file reached the 256MB size)
L4 22741110 06:38:51 fp_get_pci_slots.c 635 find_of_node:
drc_index=0x3000002b for tok=0x78f40
L4 22741110 06:38:51 umlaut chatacters appeared at the line without proper
entries. That would be the end of segment limit and circular log size
limit should have been lower than that.

Simply running any command that reads cfglog would core.

For eg: migmgr, savebase commands cored.

Core stack for migmgr:
strncpy 88
add_to_lo 114
cfglog 234
cfglog_st 230
drlog_ini 138
main 24
__start 6C

Idea priority High
  • Guest
    Aug 22, 2015

    Creating a new RFE based on Community RFE #75947 in product IBM AIX.