Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps 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 (

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 Functionality already exists
Workspace Instana
Categories Agent
Created by Guest
Created on Oct 5, 2022

Start/stop instana agent looking for environment variable not set and maxdepth flag inside find which doesn't exist on AIX clients

Everytime an instana agent when stopped or started throws up this error on two environment variables not being set. JAVA_MAX_MEM' and 'JAVA_OPTS'. Assuming these needs to be defined in the setenv file. These variables needs to be set and exported so as to avoid getting this message. Also, the message ends with "find: 0652-017 -maxdepth is not a valid option." As per the support the default values should be export JAVA_MIN_MEM=64m
export JAVA_MAX_MEM=160m along with that there is one additional change memory-related that can be can be implemented for our agent service:


There isn't any option in AIX OS for the find command called "-maxdepth" which is mentioned in the karaf file present in the bin folder in line 151 where it says PID_FILE=`find "${KARAF_HOME}" -maxdepth 1 -name '*.pid' -print -quit`

Supported opted to replace

FIND_EXISTS=`command -v find &> /dev/null`



Explanation: this sets FIND_EXISTS to an empty string and bypasses the find call altogether. This needs to be updated so that we do not see any error on find command

Idea priority Medium