Manipulating the windowed environment

This section describes those CICSPlex® SM display commands that allow you to define and alter the windowed environment in which you are working. It describes how to:

Opening additional windows

When the Information Display panel is initially produced, its display area contains one open window. You can open additional windows, up to a maximum of 20 windows per display area, by splitting any window either horizontally or vertically.

To split a window horizontally, type the command

   HSplit

in the COMMAND field, move the cursor to the row in which the window information line of the new window is to appear, and press Enter. (Alternatively, if the HSplit command has been assigned to a PF key, move the cursor into position before pressing the PF key.)

To split a window vertically, type the command

   VSplit

in the command field, move the cursor to the column in which the left border of the new window is to appear, and press Enter. (Alternatively, if the VSplit command has been assigned to a PF key, move the cursor into position before pressing the PF key.)

A window must be at least four lines deep (of which the first is the window information line) and eight columns wide. If you position the cursor inside an open window prior to issuing HSplit or VSplit, space for the new window is taken from that window. If the cursor is on a window information line or window border, space for the new window is taken from the adjacent windows.

The newly opened window becomes the current window and its status code is T (temporary). Window status codes are described in Displaying the window status description.

Changing the current window

The window to which the results of a command are directed by default is known as the current window. Regardless of the number of windows on the information display, only one window at any one time can be the current window.

You can change the current window by:

For example, assume you have three open windows and that window 1 is the current window. Issuing the command W3 causes window 3 to become the current window. Issuing the NEXt command causes window 1 to become the current window. Finally, issuing the PREVious command causes window 3 to become the current window again.

Directing command results to another window

By default, the results of a command are displayed in the current window. However, you can direct the results of a command to a different window by prefixing the command with the value:

   Wn.

where n is the number of the open window that is to receive the results of the command. For example, if window 1 is the current window and you issue W2.MENU OPERATE, a list of all operations-related menus is displayed in window 2. Window 1 remains the current window.

The Wn. prefix

This prefix can be used with all view commands, and with any of the display commands described in the remainder of this section whose effects are felt by a single window.

As described in Changing the current window, the Wn value can also be used as a command. To illustrate the difference between the use of Wn as a command and as a prefix, consider this example:

       W2;W3.MENU OPERATE;MENU MONITOR

Displaying the window status description

Every window has a one-character code that describes its status. To display the meaning of the status code for the current window in the short message area, issue the command:

   STATus

The status codes are described in Table 2.

Table 2. Window status codes
Code
Meaning
Description
W
Waiting
The window contains data and is available for use.
T
Temporary
The window is empty and no commands are processing. A window’s status is T when it is first opened and when it is subsequently cleared.
E
Error
An error has occurred as the result of an action directed to the window.
L
Locked
The LOCK command (which is described in Locking and unlocking a window) has been issued to prevent the window’s contents from being automatically updated.
P
Pending
CICSPlex SM is processing one or more commands. (Pending status is described in more detail below.)
Pending status:

While a CICSPlex SM command is being processed, you cannot issue commands against any window. In most cases, this does not present difficulties. However, if CICSPlex SM is processing a command or stack of commands that require complex processing, you might require access to the remaining windows before that processing is complete. In order to "release" the remaining windows, you must cause a TSO terminal attention. You do this by pressing either the ATTN key, on an IBM® 3270 display, or any combination of keys that simulates the ATTN function. (For example, the RESET key followed by the PA1 key simulates the ATTN function on the IBM Personal Computer display and the IBM 3179 display.) This causes CICSPlex SM to:

This will allow you to issue commands in windows whose status is not P. If command processing is complete the next time you press Enter or a PF key, the contents of the window are updated and the status code changes from P to W.

In a window whose status is P you can issue only the CLEar, CLOse, RESet, and Quit commands.

If you issue the STATus command as part of a list of commands, it is recommended that you place it last in the list. This is because the STATus command remains displayed after it is issued, and any commands following it cannot be processed until you remove STATus and press Enter.

To display a detailed explanation of a status code, issue the HELp display command while the status-code meaning is displayed (that is, after you have issued the STATus command). The explanation of the status code temporarily replaces the CURR WIN and ALT WIN fields. These fields are restored when you press Enter or a PF key.

Displaying information about a view

The window information line, which is described in The window information line, provides some information about the view currently on display in a window. For example, the window information line tells you the number of records in the view. For a more detailed definition of the view contents, issue:

   SHOWPosi

which causes a pop-up window to overlay the information display panel. To remove the pop-up window, press PF3.

The SHOWPosi pop-up window contains the following information about the view:

Maximizing and restoring windows

When you are working with multiple windows, you can expand one of those windows to fill the display area. A maximized window can later be restored to its previous position and size in the window configuration.

To expand the current window to its maximum size, issue the command:

   MAXimize

The other windows in the display area remain active, but are hidden behind the maximized window.

While the window is maximized:

To restore the maximized window and redisplay all open windows in their previous configuration, issue the command:

   RESTore

The window that is maximized at the time you issue the RESTore command becomes the current window. Also , the data in any window whose status is W (waiting) is refreshed.

Note that, in some circumstances, the END display command can have the same effect as the RESTore command. For more information about the END display command, see Redisplaying views and forms of views.

Setting the context and scope

The context and scope of a window determine which CICSPlex SM or CICS® resources are affected by commands directed to that window. The window information line identifies a window’s current context and scope.

When you begin a CICSPlex SM session, the context and scope for all windows are set to one of the following:

At any time during the session, you can change the context and scope settings of individual windows or of all windows opened or cleared subsequently. You can also change the default context and scope values that are to be in effect when a session is next started.

Changing the context of an existing window

To change the context of an existing window, issue the command:

   CONtext name [product [server]]

If you are performing any of the functions made available to you by option 2 (CICSPlex SM) of the CICSPlex System Manager entry panel:

name
is the identifier of a CMAS or of a CICSplex. If you are using the CICSPlex SM interface to manage the CICSPlex SM environment itself using the CONFIG views (as described in CICSPlex System Manager Administration), name identifies a CMAS. For other uses of CICSPlex SM, name identifies a CICSplex.
product
is CPSM. If the window information line is currently displaying the product value CPSM, you can specify an asterisk (*) as the product value.
server
is valid only when the name value identifies a CICSplex. It is the name of a CMAS to which the CICSplex is defined. If you are happy to work with any CMAS involved in managing the CICSplex, you can omit this value.

For example:

  1. To change the context of the current window to CMAS EYUCMS01 when the product identifier in the window information line is already CPSM, issue:
       CON EYUCMS01 *
  2. To change the context of window 4 to CICSplex EYUPLX02 and nominate CMAS EYUCMS02 as the CMAS with which you want to work, issue:
       W4.CON EYUPLX02 CPSM EYUCMS02

If you are performing any of the CAS-management tasks accessible via option 1 (PLEXMGR) of the CICSPlex System Manager entry panel:

name
identifies a system that is running PLEXMGR (that is, a CAS). To select the CAS that you are currently signed on to, specify a name value of asterisk (*). To select a different system, which must be connected to the system you are signed on to and be running PLEXMGR, specify its MVS™ sysid.
product
is PLEXMGR. If the window information line is currently displaying the product value PLEXMGR, you can specify an asterisk (*) as the product value.
server
is not valid.

For example:

  1. To set the context in window 3 to the CAS you are currently signed on to in order to perform PLEXMGR tasks, issue:
       W3.CON * PLEXMGR
  2. To set the context in the current window to CAS SYSC for PLEXMGR tasks, issue:
       CON SYSC PLEXMGR
  3. To set the context in the current window to the CAS you are currently signed on to when the product value in the window information line is already set to PLEXMGR, issue:
       CON * *

Notes:
  1. If the PlexManager extended security message option is turned on at your enterprise, message BBMSS201I is displayed each time you open a new window or change the context of a window. You can press Enter to clear the message. For more information about PlexManager diagnostic facilities, refer to the CICSPlex System Manager Problem Determination book.
  2. When the CONtext command is successful, the view currently on display in the window is automatically updated to reflect the change. Be aware, however, that if you change the context from a CICSplex to a CMAS and the view that was displayed required a context of CICSplex, an error message is issued. The same observation applies when the context is changed from a CMAS to a CICSplex. Similarly, if you change the product value from CPSM to PLEXMGR, the view in the affected window will not be recognized. To avoid such errors, you can name the view that you want displayed in the same command string as the CONtext command. For example, the command:
     W2.CON EYUPLX02 CPSM *; MLOCTRAN QAB*
    changes the context of window 2 to CICSplex EYUPLX02 and displays in that window a general view of all monitored local transactions whose names begin with the characters QAB.

Changing the scope of an existing window

To change the scope of an existing window, issue the command:

   SCOpe name

where name is the name of a CICS system or CICS system group associated with the current CICSplex, or is the name of the CICSplex itself. The scope value is ignored if the context is not a CICSplex.

When you issue this command, the window is automatically updated to reflect the change. That is, the contents of any view displayed in the window are updated to reflect the new scope.

Changing both context and scope of an existing window

To change both the context and the scope of an existing window in either CICSPlex SM or PlexManager, issue the command:

   SET

Figure 30 shows the input panel displayed when you issue the SET command.

Figure 30. The SET command input panel
----------- SET WINDOW CONTEXT, PRODUCT, SERVER, SCOPE AND VIEW ----------------
COMMAND ===>
 
  Window Parameters:
 
  Context     ===> EYUPLX01
  Product     ===> CPSM
  Server      ===> *
  Scope       ===> EYUPLX01
  View        ===> MENU
 
 
  Type End to Set Window Parameters
       Cancel to quit without setting
 
Context
For CICSPlex SM, the name of either the CICSplex or the CMAS that is to become the context.

For PlexManager, an asterisk (*), meaning the system you are currently using, or the name of any system in which PlexManager is available.

Product
CPSM or PLEXMGR for CICSPlex SM or PlexManager, respectively.
Server
For CICSPlex SM, a CMAS to which the CICSplex is defined. It can be set to an asterisk (*), meaning that any valid CMAS is acceptable.

For PlexManager, an asterisk (*).

Scope
For CICSPlex SM, any CICS system or CICS system group associated with the CICSplex, or the name of the CICSplex itself. (When the context is a CMAS, scope is ignored.)

For PlexManager, an asterisk (*).

View
For CICSPlex SM, the name of any view that is valid for the context and scope.

For PlexManager, the name of any PlexManager view.

This causes the window to contain the specified view, qualified by the new context and scope.

Changing context and scope for the rest of the session

To change:

issue the command:

   SETD

Figure 31 shows the input panel that is displayed when you issue the SETD command.

Figure 31. The SETD command input panel
-------------------- SET DEFAULT CONTEXT, PRODUCT AND SCOPE --------------------
COMMAND ===>                                                    SCROLL ===> PAGE
 
  Please confirm Default Parameters:
 
  Context     ===> EYUPLX01
  Product     ===> CPSM
  Scope       ===> EYUCSG01
 
 
  Type End to Set Default Parameters
       Cancel to quit without setting
 

Context
is the name of either a CICSplex or a CMAS.
Product
is CPSM.
Scope
is any CICS system or CICS system group associated with the CICSplex, or is the CICSplex itself. (When the context is a CMAS, scope is ignored.)

The values you specify on the SETD input panel come into effect for any window that is subsequently opened or cleared. They also become the default values, and will appear on the CICSPlex System Manager entry panel when a session is next started. SETD has no effect on windows that are currently open. The new values remain in effect until you next change them using SETD, CONtext, SCOpe, or SET2

Notes:
  1. You can use the SETD command to make the PlexManager product and context values the defaults. That is, the product value could be PLEXMGR, and the context value could be an MVS sysid. However, to have these values as defaults would be the exception rather than the rule.
  2. As SETD has no effect on the current context and scope settings, the values you specify are not validated until you next open a window (as described in Opening additional windows) or clear a window (as described in Clearing a window).

Saving and reusing screen configurations

You can save a configuration of windows and views so that they can be reused. To save the current configuration, issue the command:

   SAVEScr

This command causes an input panel to be displayed, into which you enter a name for the configuration (1 through 8 characters) and, optionally, a description (1 through 30 characters).

The saved screen configuration consists of:

The saved screen configuration does not include:

Screen configuration definitions are stored in the screen repository. The data set containing this repository is usually allocated to your TSO user ID when you start a CICSPlex SM session. If the data set is not available, you receive a message stating the reason. If this happens, contact your system administrator for assistance.

The ability to save screen configurations effectively enables the CICSPlex SM environment to be tailored for less skilled users, for example, or to support routine and repeated tasks. For example, if, in your environment, four windows are created at the start of every CICSPlex SM session, with the same context and scope each time, the CICSPlex SM operator does not have to create that configuration from scratch each time: it can be created once, then saved. To use a saved screen configuration, issue the command:

   SCReen name

where name identifies an existing configuration. For example, issuing the command SCR SAMPLE causes the configuration named SAMPLE to replace the current configuration.

The total height and width of the windows that make up a configuration must be equal to or less than the size of the display area in which the configuration is used. For example, a configuration created from a 43-line screen cannot be used on a 24-line screen.

To display a view that lists previously saved configurations, issue the command:

   SCREENS

An example of the resulting view is shown in Figure 32.

Figure 32. An example of the SCREENS view
 27FEB2005  16:19:45 ----------- INFORMATION DISPLAY ---------------------------
 COMMAND  ===>                                                 SCROLL ===> PAGE
 CURR WIN ===> 1        ALT WIN ===>
  W1 =SCREENS===========EYUPLX01=EYUCSG01=27FEB2005==16:19:45=CPSM==========3===
 C Name      Description                     Userid
 - --------  ------------------------------  ----------
   SCR02     Two windows - PROGRAM and FILE  USER01
   SCR03     Three windows                   USER01
   W3H1V2    Three windows - one over two    USER02
 

From the resulting view you can:

You can select screen configurations created by other users, but note that the "sign-on" message is displayed when you select such a configuration.

SAVEScr, SCReen, and SCREENS cannot be issued when a window is maximized.

Once a screen configuration has been invoked, issuing the END command ends the current view and redisplays the previous view in that screen configuration. Any views displayed prior to invoking the screen configuration are discarded.

Closing windows

You can close one or more windows at any time during a CICSPlex SM session.

If the status code of any of the affected windows is P (pending) when you issue the CLOse, RESet, or Quit command, or the ISPF command RETURN, the command that is currently processing in each of those windows is completed. Other outstanding commands are discarded.


2.
Initiating a hyperlink to a different window may cause the context and scope in the second window to change to match those of the first window. For additional information, see How hyperlinks affect context and scope values.

[[ Contents Previous Page | Next Page Index ]]