Other workspace customization

Learn about other workspace customizations and related workspace definition parameters.

The following information explains some common workspace definition statements that can be used to customize product provided workspaces. For an example of a detailed procedure to customize a workspace, see Customizing a workspace.

The initial and refresh cursor position for workspaces

The initial (on-entry) workspace cursor position is specified by the CURSOR= workspace definition statement. For example, CURSOR=HOME specifies that the initial cursor location is in the menu bar command field.

The CURSORREFRESH= workspace definition statement determines the cursor position behavior when the workspace is refreshed or when you return to the workspace, for example, after you enter PF3 (End). For example, CURSORREFRESH=ASIS specifies that the cursor position remains unchanged when you refresh or return to a workspace.

The possible values for the CURSOR= and CURSORREFRESH= statements are as follows:

HOME: Row 00, Column 1
COMMANDLINE: The cursor appears after the command-line prompt, Command ==>
SUBPANEL: The cursor appears in the first selectable field of the first subpanel.
ASIS: The cursor remains on the workspace wherever the user placed it.

Statically defined columns

Statically defined columns remain static during lateral scroll operations. These columns are usually the primary identification columns for a specific summary subpanel data row. For example, in the case of the KOBSITEC workspace, the Status and Situation Name columns are defined as static. The statically defined columns are controlled by the STATICCOLS= subpanel definition statement. Thus STATICCOLS=2 specifies that the two leftmost columns in a subpanel display are defined as static; that is, the first two columns that are specified in the subpanel DISPLAYCOLS statement as shown in the following excerpt from the KOBSITECworkspace definition:

 STATICCOLS=2                                       
                                                    
 DISPLAYCOLS='DELTASTAT(CAPTION='Status',WIDTH=7),  
 SITNAME(CAPTION='Situation_Name',WIDTH=30),        
 ORIGINNODE(CAPTION='MSN_Event_Source'),            
 GBLTMSTMP(CAPTION='HUB_Event_Time',DATETIME),      
 LCLTMSTMP(CAPTION='Agent_Event_Time',DATETIME),    
 ATOMIZE(WIDTH=30,SCROLL),                          
 TYPE(CAPTION='Type')'

Number of columns displayed

The columns that are displayed in a specific workspace are specified by the DISPLAYCOLS= workspace definition statement. To remove a column from the workspace display, remove its specification in the DISPLAYCOLS definition. To remove the Type column from the KOBSITEC workspace, remove the TYPE(CAPTION='Type') specification from the DISPLAYCOLS definition as shown in the example:

 STATICCOLS=2                                       
                                                    
 DISPLAYCOLS='DELTASTAT(CAPTION='Status',WIDTH=7),  
 SITNAME(CAPTION='Situation_Name',WIDTH=30),        
 ORIGINNODE(CAPTION='MSN_Event_Source'),            
 GBLTMSTMP(CAPTION='HUB_Event_Time',DATETIME),      
 LCLTMSTMP(CAPTION='Agent_Event_Time',DATETIME),    
 ATOMIZE(WIDTH=30,SCROLL)'

Important: The closing quotation mark (') that follows the TYPE column specification is not dropped. It is moved to the end of the ATOMIZE column definition. The closing quotation mark signifies the end of the DISPLAYCOLS definition statement.

Allotted subpanel row count

For workspaces that provide multiple subpanel displays, there might be cases where it is preferable to adjust the screen space. For example, you might modify the minimum number of rows that are allotted to a specific subpanel. This can be illustrated by using the KOBSITEC workspace as an example. The KOBSITEC workspace provides two subpanels, the first subpanel provides a list of Open situations, the second subpanel provides a situation alerts history list. As currently defined, if a user logs on to the interface with the 3270 model 5 emulation mode (27 rows), only the history (second) subpanel headers are displayed when the data rows in the first subpanel exceed five rows. The maximum rows that are allotted to a specific subpanel are defined by the subpanel LINESnn= parameter statements as shown in the following excerpt from the KOBSITEC workspace first subpanel definition:

 LINES24=4       
 LINES32=8       
 LINES43=12      
 LINES62=20      
 LINES90=25

Tip: The nn in LINESnn= represents the maximum available screen lines for a specific 3270 terminal.

To change the default space that might be allotted to the first workspace subpanel, for example, where most enhanced 3270 user interface users are using low maximum line emulation modes (such as a 3270 model 2 with 24 available lines), you might adjust the LINES24 definition to LINES24=2. This change reduces the screen space that is allotted to the first subpanel and frees up two lines for use by the second subpanel. Alternatively, if the second subpanel is used infrequently and you want more space for the first subpanel, the alternative adjustment might be applied; that is, adjust the LINES24 definition to LINES24=8, allowing up to eight rows of detailed data to be viewed in the first subpanel. This example might be considered extreme. The enhanced 3270 user interface recommended minimum screen size is 43x80, for example, a 3270 model 4 with 43 available lines.

Workspace sort columns

The workspace subpanel sortable columns are specified by the SORTCOLS= definition statement. Given that the sort indexes are constructed after row data is retrieved and before the workspace is rendered, the product provided workspaces employ discretionary use of this definition statement, especially in cases where the anticipated returned row set can produce many rows. The product provided workspaces are designed to anticipate the most common use cases.

If, after you use the enhanced 3270 user interface for some time, you find that more sortable columns will improve the usability of a specific workspace, you might consider expanding the SORTCOLS= definition. For example, for the KOBSITEC workspace, if the current SORTCOLS= definition is SORTCOLS='SITNAME', to expand the definition to also include other subpanel columns such as, the MSN Event Source and HUB and Agent Event Time columns, you might change the definition to SORTCOLS='SITNAME, ORIGINNODE, GBLTMSTMP, LCLTMSTMP'.

The SORTCOLS definition statement must be defined with discretion, giving thought to potential loading costs. Although it is possible to define up to 30 SORTCOLS columns, or to define SORTCOLS=ALL to enable sorting on any subpanel column, this option is best avoided unless there is a certainty that the retrieved data comprises few data rows.

Note that the SORTCOLS specification can have limited use when a column display value is derived from an internal enumerated list, that is, where the display value is derived from the translation of an internal value. In this case, the sort index is produced from the internal column value. As a result, the column display values might seem to be grouped, but not necessarily in the expected display order.

Local or agent filter definitions

The workspace subpanel filterable columns is specified by the FILTERCOLS= definition statement. The following considerations are for using the FILTERCOLS definition statement:

FILTERCOLS specifications support the data result row set for each workspace subpanel that defines the FILTERCOLS statement.
There might be cases where a workspace provides multiple subpanels that share a retrieved data row set, that is, a reusable query. In that case, the filters specification supports all subpanels that share the specific result row set.
The FILTERCOLS workspace operates in conjunction with the FILTERWHERE= definition statement to specify where the filter is applied, either after the data is collected and returned to the enhanced 3270 user interface, or at the agent, during data collection and before the data is returned to the enhanced 3270 user interface. The default FILTERWHERE= definition is FILTERWHERE=AGENT, that is, filter at the agent.
When a FILTERCOLS statement is defined along with FILTERWHERE=AGENT (the default), the filters are applied at the agent. As a result, a FILTERCOLS statement with FILTERWHERE=AGENT does affect the load that is incurred for data retrieval. Assuming the filters are effective, they reduce the amount of data that is collected and returned to the enhanced 3270 user interface.
The FILTERCOLS statement must be used with discretion as they are not always effective. For example, they are most usable with column values that contain text strings. However, their use is limited for a numeric column value or a column value that is derived from an internal enumerated list, that is, where the display value is derived from the translation of an internal value.

For more information about adjusting the filterable columns, see Adjusting the filterable columns.

Remember: There are other workspace definition statements, for example, FILTERVIEW(S) and FILTERSTRIP, that are related to filters that can be specified in the product provided workspaces. Filter definition statements can be complex and changes to product-provided workspace filter definitions must be applied with discretion to avoid unintended side-effects.

Number and order of workspace subpanels

The workspace subpanel definition start is specified by the presence of a subpanel start <SUBPANEL> tag statement. The subpanel definition end is specified in one of the following ways:

An implicit end that is defined by a <WORKSPACEEND> tag
An explicit end that is defined by a <SUBPANELEND> tag
An implicit end that is defined by a subsequent <SUBPANEL> tag that signifies the start of another subpanel

Remember: The <WORKSPACEEND> tag signifies the end of the workspace definition.

For more information about removing a subpanel, see Removing a subpanel

The following considerations are about the subject of removing and or reordering workspace subpanels:

Given that the subpanel definition boundaries are defined by the <SUBPANEL> and <SUBPANELEND> tag statements or by an implicit end of subpanel, you can make a subpanel order change by moving a block of all lines that define a specific subpanel from one location in the workspace definition to another location.
Remember: For product provided workspaces, the order of workspaces can matter. For example, the retrieved data result set for workspace A might be shared by workspace B. Another example is when workspace B depends on a value that is set by workspace A. Another case, is for a silent workspace, that is, a workspace that is not displayed but contributes to the navigation scenario. For example, a silent workspace can run intermediate steps that are required for a subsequent process. Take these considerations into account when customizing a workspace that for example, removes, adds, or reorders subpanels within a specific workspace.

Workspace panel definitions - reference

For more information about workspace definition statements that might have content and order implications, see Workspace panel definitions