Customization of product provided workspaces

Guidance on customizing cloned workspaces.

Before customizing a workspace, you must first clone it. For more information about cloning a workspace, see Cloning a workspace.

Use a file editor such as the ISPF editor to customize a workspace. Save the cloned workspace in the user workspace data set, that is, the data set pointed to by the enhanced 3270 user interface (enhanced 3270UI) started task JCL UKANWENU DD statement.

Important: Product provided workspaces rely on both the workspace content and supporting REXX code to control context and navigation. Customization changes must avoid modifications that might have unintended results; for example; loss of context.
The following examples are workspace customization actions that a user might want to perform.
  • Change the order of columns that are displayed in a summary data subpanel.
  • Change the columns that are displayed. For example, remove some columns in a summary subpanel, and eliminate some of the attribute values in a detailed data subpanel.
  • Change the workspace header.
  • Change the workspace default (on entry) cursor position.
  • Change the workspace default sort columns.
  • Change the statically defined columns in a summary subpanel.
  • Change the Agent filter that is specified in a subpanel query.
  • Add local Filters to a summary subpanel.
  • Change the number or order of subpanels that are displayed in the workspace.
  • Combine data from two or more input tables and generate output in a singular view.
You can achieve these types of customization by editing and changing workspace definition statements and associated keywords in the cloned workspace source. For more information, see Customizing a workspace.
Tip: Consider the following things before you change workspace definitions or view the source definition for a specific workspace:
  • The absence of workspace definitions statements and or associated keywords (modifiers) is usually an indication that defaults are being used. For example, in the DISPLAYCOLS statement, there is no requirement for the specification of the CAPTION or WIDTH keywords. These keywords would more likely be used when the defaults are not adequate or preferable.
  • The syntax that is used in the workspace definition language is important. Keyword spelling, column name spelling, commas, spaces, quotation marks, parentheses, and other syntax cannot be ignored or excluded; for example, quotation marks and parentheses must be balanced. Although the enhanced 3270UI provides comprehensive parsing of the workspace source definitions statements, runtime errors and in some cases unexpected results might occur if the syntax is incorrect. For more information about the workspace definition language, see Workspace panel definitions.
  • The workspace definition language specifications employ the internal column name to refer to a specific application product and table column/attribute. Taking note of the displayed workspace column order position along with the workspace DISPLAYCOLS definition (specified column order position) can be useful as a technique for correlating displayed columns with their corresponding internal column names.
    Remember: When customizing product provided workspaces, when the changes are deployed for use by a wider audience, the changes affect all users of a given enhanced 3270UI address space. Consider the other users when customizations of this type are done. The customization must benefit all of your users.