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 Future consideration
Workspace IBM i
Categories Web Serving
Created by Guest
Created on Mar 22, 2018

Enhancement to get better messaging in the joblog for missing directory for access logs

As described in the PMR #11243,033,724, the apache version 2.4.2 is now "checking during config test that directories for the
access logs actually exist." (PR 29941). If the directory is missing, then the apache instance will not restart. This is not written in the IBM i job logs, either in any other system log. For that reason, if the issue exists, is very difficult to identify.

Use Case:

PMR #11243,033,724

System: Apache server v2.4.2
Actor: Administrator

Use cases for the system:
OS Upgrade from V7R1 to V7R3 (that includes apache upgrade from v2.2 to v.2.4)

After OS/400 Upgrade, apache instance is not starting.
System shows a "SIGKILL signal" in the job logs. No other logs pointing to the root cause of the problem.

Create missing access log directories, specified in the virtualhosts.

Idea priority Medium