This RFE applies to Access Client Solutions:
We have over 100 IBM i systems in our network. Due to the number of active 5250/Printer/Console sessions, the ACS display Active Sessions panel is essential to our job for navigating between sessions.
We set the ACS Session Manager View settings as follows:
- Display Detail
- Display the Active Sessions
1. The Active Sessions pane is too narrow and truncates the session names. See TS004285863.
2. There is no filter support to allow the quick location of a single or set of existing active session(s) in a long list of "unordered" active sessions.
3. There is no support for ordering the list of Active Sessions. That would make locating an Active Session easier.
4. There is no filter support to allow the quick location of a single or set of Configured Session(s). At least the Configured Sessions pane can be sorted by column heading, which makes it a bit easier to find what you are looking for in a list of over 120 Configured Sessions.
The following will be "nice to haves" down the road:
a. The ability to assign Group names in the "System Configurations" where the group names carries over into the Configured Sessions and Active Sessions panes.
b. The ability to save and reuse filters for the Configured Sessions and Active Sessions panes.
Use Case: I will focus the use case on the Active Sessions pane, since it is the more pressing need.
All of the justifications and use cases for the Active Sessions pane equally apply to the Configured Sessions pane, although that one is a more complex use case due to the multiple columns.
The Configured Sessions filter will be very useful but is lower priority to us than the Active Sessions filter.
In general, any filter support should support wild card searches with multiple search arguments. In the examples below I modeled the syntax after the SQL LIKE statement (although regular expressions will be much more powerful but perhaps too complex for the average user). For example:
1. ~ means any single character (use ~ instead of the SQL _ underscore because session names can contain an underscore)
2. % means the same as in SQL.
3. The filter is case insensitive unless in apostrophes (case sensitive support is low priority).
3. Multiple search arguments are separated by a comma. (this is a high priority requirement).
4. Exclusion support is low priority, i.e. the ability to specify session names starting with ABC but NOT ending with 1, like this: ABC%,not(ABC%1)
Lets say you have 30 active sessions that is a mix of plain 5250, Console and Printer. Display session names have a D prefix, and printers have a P prefix. Consoles have the Console: prefix.
Use case 1: Install V74 PTF's. Find the active Console sessions for V74 hosts (assuming the session name carries the OS version number).
Filter = console:%74%
Result = Console: ABC74QA and Console: DEVO74
Use case 2: Setup or change BRMS for a subset of active sessions, consisting of all active "Sand box" Display sessions containing SB in positions 5-6 and that ends the letter A. Also include all HOST sessions.
Filter = Console: ~~~~SB%A, D~~~~SB%A, D%HOST%
Result = DPRODHOST, Console: PRODHOST, DDEMOHOST, PDEMOHOST, Console: TESTHOST, DPRODSB2A, DDEVOSB2A, DTESTSB3A and DDEMOSB1A
IBM understands this request and will consider it for a future code update, though no commitment is made or implied.