SET FULLSCREEN

Read syntax diagramSkip visual syntax diagram SET FULLSCREen1 ONOFFSUSPENDRESUME(CLear(NOCLear )
Notes:
  • 1 A special command that can be used in the FULLSCREEN environment is #WM.

Authorization

General User

Purpose

Use the SET FULLSCREEN command to control whether CMS uses windowing support (virtual screens and windows) for command input and output, messages, and warnings.

Operands

ON
initializes full-screen CMS. SET FULLSCREEN ON defines the default virtual screens and windows for CMS. Output that is generally displayed by CP is trapped by CMS (by the IUCV Message All System Service) so messages and VM output are displayed in windows.
OFF
returns CMS to line mode operation.
SUSPEND
specifies CMS should temporarily return to line mode operation. CMS discontinues trapping I/O (by severing the *MSGALL connection) so CP displays messages and VM output. This option could be used by applications that perform their own full-screen management, such as those that use DIAGNOSE Code X'58'.
RESUME
returns a CMS session to the state that preceded a SET FULLSCREEN SUSPEND command.

Options

CLear
clears the screen and enters full-screen CMS when used with ON or RESUME. The screen is not placed in a MORE... status. CLEAR is the default.
NOCLear
does not clear the screen when used with ON or RESUME. The screen is placed in a MORE... status, and any messages remain on the screen until the Clear key is pressed. The NOCLEAR option is particularly useful when SET FULLSCREEN ON or SET FULLSCREEN RESUME is issued from an exec or program that displays messages.

Initial Setting

FULLSCREEN OFF

Things You Should Know about Full-Screen CMS

  1. When you issue SET FULLSCREEN ON, CMS is placed in full-screen mode with the default and user-defined windows and features (for example: CMSPF Keys, Command Line, Status Area, and so forth) being displayed.
  2. When entering full-screen CMS:
    • All default virtual screens you have not defined are defined, such as a virtual screen for CMS and CP output, and virtual screens for messages, network messages, warnings from the operator, and status information.
    • All reserved areas are written for the default virtual screens.
    • All default windows you have not defined are defined.
    • Default windows are connected to appropriate virtual screens.
    • CMSPF key definitions are established.
    • A connection to the IUCV Message All System Service is established and various classes of output are routed to virtual screens.
    • Logging is started for the MESSAGE and WARNING virtual screens.
    • The cursor is set in the CMS virtual screen.
    • The CP TERMINAL BRKKEY NONE command is issued.
  3. When returning to full-screen CMS after it has been suspended:
    • The CMS window is shown.
    • The STATUS window is displayed.
    • A connection is reestablished to the IUCV Message All System Service.
    • Window and virtual screen definitions, logging, message routing, and the CP TERMINAL BRKKEY setting are not affected.
  4. You must SET FULLSCREEN to OFF or SUSPEND to allow an APPC/VM application to connect to a private resource in your virtual machine. If FULLSCREEN is ON, CMS rejects any private resource connection requests.

    Your virtual machine may be logged on automatically if it processes private resource connection requests. If SET FULLSCREEN is ON, private resource managers are not invoked. If your virtual machine processes private resource connection requests, put the statement SET FULLSCREEN OFF or SET FULLSCREEN SUSPEND in your PROFILE EXEC to make sure CMS does not reject any private resource connection requests.

    For more information, see z/VM: Connectivity.

  5. When lines are written to a virtual screen sequentially, such as in the CMS virtual screen, lines are added to the virtual screen starting at the virtual screen top. Once the virtual screen is full and you scroll forward, the oldest lines that have been scrolled are deleted, new lines are appended at the bottom, and the lines are renumbered. (Lines that have not been scrolled are not deleted.) Because the lines are renumbered, the scroll location information may appear to remain the same as you scroll forward.

    When the virtual screen is full and new information is waiting to be added, scrolling the virtual screen forward or entering one of the these commands: WINDOW CLEAR, VSCREEN CLEAR, WINDOW SHOW, or WINDOW HIDE, allows the virtual screen to be updated. That is, the oldest information that has been scrolled is deleted off the top so the newest information can be added at the bottom. This updating process occurs even if the window connected to the virtual screen is hidden or overlaid by other windows.

  6. When you receive the status area message Scroll forward for more information in vscreen vname and there are multiple windows showing the specified virtual screen, it is recommended you scroll forward the window closest to the top of the ordered list of windows. This enables data that is in the virtual screen queue to be written to the virtual screen and displayed.
  7. When you SET FULLSCREEN OFF, all information that has not been updated to a virtual screen before execution of the command will be typed out in line mode. Any default windows and virtual screens defined by full-screen CMS will be deleted.

    In addition, the CP TERMINAL BRKKEY remains as NONE. To reset it to PA1 (the initial setting), use the CP TERMINAL command.

  8. Commands can be entered only in the CMS virtual screen and the WM window. Commands entered in the CMS virtual screen are always echoed in the CMS virtual screen regardless of the routing of the CMS message class.
  9. You must always have a window showing the CMS virtual screen when using full-screen CMS. If you hide all the windows showing the CMS virtual screen, the CMS window is automatically shown at the top of the CMS virtual screen. The CMS window is on top of all other windows, including the STATUS window. You should then issue the WINDOW POP STATUS command.
  10. The WM window is automatically displayed in full-screen CMS when the window or windows showing the active virtual screen are not visible on the screen. (The active virtual screen is the one in which a command or response is requested.) For example, you may maximize a window that is not showing the active virtual screen so it covers the window or windows showing the active virtual screen. Because you cannot enter commands in the active virtual screen, the WM environment is automatically entered; the WMPF keys and WM command line are available to manipulate all windows. You can choose to press the PF3 key (if the setting of WMPF key 3 has not been changed from the initial value) or issue the command WINDOW DROP WM to pop all windows showing the active virtual screen and exit the WM environment.
    In addition, the WM window is automatically displayed in full-screen CMS when you run an application that uses the CONSOLE macro to perform I/O and one of the following occurs:
    • The CMS virtual screen is updated.
    • Any virtual screen (other than CMS) is updated and a pop-type window is showing it.

    The WMPF keys and a command line are available. Issuing the WINDOW DROP WM command (default WMPF 3) returns you to the application.

  11. SET FULLSCREEN must be ON in order for CMS to recognize double-byte character set (DBCS) strings, and for them to be displayed. XEDIT also recognizes DBCS characters. For more information, see z/VM: XEDIT Commands and Macros Reference.

System Defaults for Full-Screen CMS

  1. The default windows for full-screen CMS are:
    Table 1. Default Windows
    Wname Lines Cols Psline Pscol Options
    STATUS 1 Pscr -1 1
    Fixed
    Noborder
    Nopop
    Notop
    CMS Pscr Pscr 1 1
    Fixed
    Border
    Nopop
    Top
    NETWORK 8 71 -12 7
    Variable
    Border
    Nopop
    Top
    WARNING 6 71 3 3
    Variable
    Border
    Pop
    Top
    MESSAGE 8 71 11 3
    Variable
    Border
    Pop
    Top
    WM 5 Pscr -1 1
    Fixed
    Border
    Nopop
    Notop
    CMSOUT 8 75 9 3
    Variable
    Border
    Pop
    Top
    Where:
    Pscr
    size of the physical screen
    Psline
    the line on the physical screen where the upper (when psline is positive) or lower (when psline is negative) edge of the window is placed.
    Pscol
    the column on the physical screen where the upper left corner of the window is placed.
    Variable
    indicates the number of lines in the window may vary depending on the amount of scrollable data displayed.
    Fixed
    indicates the number of lines in the window is always constant.
    Border
    indicates the borders are displayed when possible. For the CMS window, the borders are on but you cannot see them because the window is the size of the physical screen.
    Noborder
    indicates borders are not displayed.
    Pop
    specifies the window is displayed on top of all other windows when the virtual screen the window is showing is updated.
    Nopop
    specifies there is no effect on the window's position in the ordered list of windows when the virtual screen the window is showing is updated.
    Top
    specifies the window may qualify as the topmost window.
    Notop
    specifies the window cannot qualify as the topmost window
    Note: Although the WM window is a default window, it is not defined when you enter full-screen CMS. The WM window is defined when you issue the command WINDOW POP WM, when you press the PA1 key when CMS is the active virtual screen, or when the WM window is automatically displayed.

    All default windows are SYSTEM windows, which means the window is retained when the system abnormally ends (abends) or when the HX (halt execution) command is issued.

  2. The default virtual screens for full-screen CMS are:
    Table 2. Default Virtual Screens
    Vname Lines Cols Rtop Rbot Color Protected
    WM 1 Pscr 0 5 White No
    STATUS 1 Pscr 0 0 White Yes
    NETWORK 16 70 2 0 Blue Yes
    WARNING 4 70 2 0 Red Yes
    MESSAGE 20 70 2 0 White Yes
    CMS 120 Pscr 2 5 Green No
    Where:
    Pscr
    physical screen size. For terminals with a screen size of 80 columns or less, the CMS virtual screen contains 81 columns. For terminals with a screen size greater than 80 columns, the CMS virtual screen contains the same number of columns as the physical screen. The STATUS and WM virtual screens always contain the same number of columns as the physical screen.
    Rtop
    the number of top reserved lines
    Rbot
    the number of bottom reserved lines
    Color
    data color
    Protected
    if protected, you cannot type into the window(s) connected to the virtual screen
    Note: Although the WM virtual screen is a default virtual screen, it is not defined when you enter full-screen CMS. The WM virtual screen is defined when you issue the command WINDOW POP WM, press the PA1 key, or when the WM window is automatically displayed.

    All default virtual screens are TYPE and SYSTEM virtual screens. TYPE means data is moved to the virtual screen when the virtual screen is updated. SYSTEM means the virtual screen is retained when the system abnormally terminates (abend) or when the HX (halt execution) command is issued.

  3. Default windows are connected to default virtual screens in this manner:
    Table 3. Default Windows and Virtual Screens
    Window Virtual Screen Description
    CMS CMS Displays CMS and CP output
    CMSOUT CMS Displays CMS and CP output while in XEDIT
    MESSAGE MESSAGE Displays user messages and SCIF messages
    NETWORK NETWORK Displays network messages
    STATUS STATUS Displays status messages
    WARNING WARNING Displays warnings
    WM WM Provides the capability to enter windowing commands
  4. When SET FULLSCREEN is ON, the various message classes are routed to virtual screens as:
    Table 4. Default Settings for Message Routing
    Message Class Virtual Screen Options
    CMS CMS NOALARM NONOTIFY
    CP CMS NOALARM NONOTIFY
    MESSAGE MESSAGE ALARM NOTIFY
    WARNING WARNING ALARM NOTIFY
    SCIF MESSAGE NOALARM NONOTIFY
    NETWORK NETWORK NOALARM NOTIFY
    Where:
    ALARM
    sounds the alarm when a message is received.
    NOALARM
    does not sound the alarm.
    NOTIFY
    displays the message class name in the status area when you receive a message.
    NONOTIFY
    will not display the virtual screen name in the status area when you receive a message.

    For more information on changing the default message routing, see VSCREEN ROUTE.

    Commands entered in the CMS virtual screen are always echoed in the CMS virtual screen regardless of the routing of the CMS message class.

  5. Any messages or warnings received during your full-screen CMS session are displayed in windows and logged into files. Messages are logged into a file called MESSAGE LOGFILE, and warnings are logged into a file called WARNING LOGFILE.
  6. Pressing the PA1 key when CMS is the active virtual screen displays the WM window. The PA2 key and Clear key scroll the topmost window forward. For more information on the default settings for the CMSPF keys, see SET CMSPF.

    In the WM window, the PA2 key and Clear key also scroll the topmost window forward. When there is no more data in the window to scroll, you automatically exit the WM environment.

Considerations for Applications in Full-Screen CMS

  1. If an application performs full-screen management while in full-screen CMS and it does not use the CONSOLE macro, the output written to full-screen CMS is not displayed until the application completes. Before running the application, issue the SET FULLSCREEN SUSPEND command; when the application completes, issue the SET FULLSCREEN RESUME command.
  2. When returning to full-screen CMS from an application that performs its own full-screen management (such as DIAGNOSE Code X'58'), your screen may contain mixed data. Press Clear to scroll forward and refresh the screen.

    Alternatively, issue the SET FULLSCREEN SUSPEND command, run the application, and then issue SET FULLSCREEN RESUME when the application completes.

  3. SET FULLSCREEN SUSPEND and SET FULLSCREEN RESUME can be nested. For example, suppose full-screen CMS is ON and an application called MYPROG issues SET FULLSCREEN SUSPEND and calls another application, TESTPROG. TESTPROG also issues SET FULLSCREEN SUSPEND. When TESTPROG completes, it issues SET FULLSCREEN RESUME and control returns to MYPROG. SET FULLSCREEN is still in the SUSPEND state and MYPROG continues to execute. Upon completion MYPROG issues SET FULLSCREEN RESUME, which returns FULLSCREEN to the ON state.

    To preserve the nesting, do not issue ON or OFF between SUSPEND and RESUME. If an application issues SET FULLSCREEN ON or OFF, the nesting is cleared and FULLSCREEN status changes to ON or OFF. Use the QUERY FULLSCREEN command to determine the FULLSCREEN status.

  4. If full-screen CMS has never been set to ON, and either SET FULLSCREEN OFF, SET FULLSCREEN SUSPEND, or SET FULLSCREEN RESUME is issued, no action is taken.
  5. The following messages are not trapped by the IUCV Message All System Service and are sent directly to the terminal:
    • Asynchronous CPCONIO, including TRACE events
    • EMSGs not generated as part of a DIAGNOSE code X'08' operation instruction
    • Accounting messages
  6. The IUCV Message All System Service can stack up to 255 messages at any one time. If this limit is exceeded, any additional incoming messages are sent directly to the terminal.
  7. When SET FULLSCREEN is ON, most CMS console output is not passed to CP. In addition, applications that use the IUCV Message System Service (*MSG) and SET VMCONIO to IUCV will not trap all CMS output when using full-screen CMS. Before using such applications, it is recommended to issue SET FULLSCREEN SUSPEND.
  8. You must SET FULLSCREEN to OFF or SUSPEND to allow an APPC/VM application to connect to a private resource in your virtual machine. If FULLSCREEN is ON, CMS rejects any private resource connection requests.

    Your virtual machine may be logged on automatically if it processes private resource connection requests. If your virtual machine processes private resource connection requests, put the statement SET FULLSCREEN OFF or SET FULLSCREEN SUSPEND in your PROFILE EXEC to make sure CMS does not reject any private resource connection requests.

  9. When developing an application to be used with full-screen CMS, you may want to reset the CP TERMINAL BRKKEY to PA1 (it is set to NONE in full-screen CMS). Then, you can enter CP mode to debug the application.
  10. SET FULLSCREEN controls only the use of windowing by CMS. Whether FULLSCREEN is ON or OFF, you may define and use your own virtual screens and windows.

#WM - A Special Command Used in the Full-Screen Environment

The #WM command is a special command that can only be used in the CMS virtual screen in full-screen CMS. Use the #WM command to execute a command immediately from the CMS virtual screen.

Read syntax diagramSkip visual syntax diagram #WM wmcommand

#WM operands:

wmcommand
specifies the command you want to execute. For more information on the commands you can specify with #WM, see Usage Note 2.

#WM usage notes:

  1. The pound sign (#) represents the default logical line end symbol for full-screen CMS. If you have redefined the line end symbol to another character (using the SET LINEND command), #WM is a not valid command; you must substitute your line end symbol for the pound sign to use the command.

    The #WM command is independent of the CP logical line end symbol.

  2. You can enter any of these commands with #WM:
    • CP
    • PSCREEN PUT
    • SET RESERVED
    • SET WINDOW
    • WINDOW MAXIMIZE
    • WINDOW MINIMIZE
    Note: The HELP is not a valid command with #WM; however, it is a valid command in the WM environment.
  3. For an example of the screen you see when you SET FULLSCREEN ON, see z/VM: CMS User's Guide.

Messages and Return Codes

  • DMS109S Virtual storage capacity exceeded [RC=104]
  • DMS914E The maximum number of IUCV connections has been reached [RC=256]
  • DMS926E Command is only valid on a display terminal [RC=88]
  • DMS927E The physical screen must contain at least 20 lines and 80 columns [RC=24]
  • DMS639E Error in NUCXLOAD routine; return code was nnn [RC=24]
  • DMS931E Invalid WM command: command
  • DMS1125E command is not allowed as an immediate command

Additional system messages may be issued by this command. The reasons for these messages and their location are:

Reason Location
Errors in command syntax Command Syntax Error Messages