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 IBM i Access Family
Created by Guest
Created on Feb 3, 2017

Add User Input History to IBM i ACS

I'm in the process of migrating 66 countries from a 3rd party tool Seagull to IBM i Access Client Solutions. There is a function that Seagull has that IBM doesn't and our users are asking for IBM to add it. In Seagull, Auto-Entry can be found under View > ToolBars > Auto-Entry. The function is called Auto-Entry and it saves all or selected user input and automatically reenters it when selected from a pull down list. Saved input can also be edited. This is a good method for storing frequently used command lines or IND$FILE transfers. This is similar to the F9=Retrieve IBM i OS function but better because all user input entered on either an editable field on the screen or command/function on the command line are stored in a pull down list automatically when the user hits enter, mouse clicks an option or does an F4=Prompt. Also there is no limit on user input entries in the drop down list, it has a scroll bar. It tracks user input history from when the session screen is opened and until the session screen is closed regardless of how many times the user signs in or out on that specific session. When a new session is opened it starts new history.

Use Case:

Instead of the user pressing F9=Retrieve many times to recall a previously entered command or retyping the command, the user can pull down the Auto-Entry list and select the previously entered or stored command. It would function somewhat like a GUI F9=Retrieve function, but it allows users to add and edit the stored list. Unlike the ACS Screen History function, when a command is selected, the session runs the command. It does not just show an image of the command output as the Screen History does. Also Auto-Entry isn't limited to what is in F9, it stores data from any editable field on user screens when 1 or more fields is updated. See attached examples 1, 2 and 3.

Scenario: User is talking to a customer and frequently needs to go back to account screen and bring up customers account.
User mouse clicks on screen option#
User goes to account field
User pulls down the Auto-Entry list and locates the account#
The user selects (clicks) the account#
The session brings up the account#

Scenario: File transfer that happens several times a day
User pulls down the Auto-Entry list of previous and stored commands
User selects (clicks) the command that transfers the specific file and the stored command populates the command line
User presses <ENTER> to start/complete the file transfer

Scenario: User frequently needs to return to a specific menu
User pulls down the Auto-Entry list and locates the menu in question
The user selects (clicks) the menu
The session goes to selected menu

Idea priority Medium
  • Guest
    Jan 8, 2018

    Thank you for submitting your Request For Enhancement. After evaluating your submission, the decision at this time is to not provide this support.

  • Guest
    Jun 29, 2017

    IBM has received this requirement and is evaluating it. A response will be provided when evaluation is complete.

  • Guest
    Feb 16, 2017

    In response to the comment: How do you see this differing from the ACS macro record/playback function that already exists?
    My understanding of a macro is that it is a set of commands that can be run sequentially (playback), for instance, to gather stats or creating listings to look for updates/differences. Those are two things for which I have used macros. As I understand this RFE, it is not set commands that can be played, it is returning to a previously entered screen, but not just to the screen but to the screen with the same data entered on it already. The OS option F9=Retrieve will return me to a screen, but if it is a menu option where I have entered parameters, it does not recall those parameters. I would need to re-enter the parameters. Additionally, the data that the users are entering is not consistent. It may be a different customer number, different policy number, different address, etc. and would change when the user is working with the next client. Though a macro can be edited, this would be above and beyond what would be expected in the role of the user.

  • Guest
    Feb 6, 2017

    How do you see this differing from the ACS macro record/playback function that already exists?

  • Guest
    Feb 3, 2017

    Attachment (Use case): 3rd Party Function Details

  • Guest
    Feb 3, 2017

    Attachment (Use case): Examples of how function is used