|
All of the FOCUS features described in the FOCUS documentation are available under MSO, except as documented in this section. TABLE, MAINTAIN, MODIFY, Dialogue Manager, TED, FOCCALC, and the Talk Technologies are present in MSO. |
In this section: |
In addition to the standard profiles executed by FOCUS (See FOCUS for S/390 Overview and Operating Environments), two additional profiles are executed when running MSO (See the OS/390 and MVS Installation Guide). The profiles follow the execution of SHELPROF in the following order:
In the JCL used to start MSO, the partitioned data set allocated to ddname MSOPROF may have a member PROFILE. If this member is present it will be executed for all users who log on. This profile is executed in the MSO environment only.
In the JCL used to start MSO, the partitioned data set allocated to ddname MSOPROF may have members with different userids as the member names. The member corresponding to the MSO security userid will be executed for that user. This profile is executed in the MSO environment only.
In the partitioned data set allocated to FOCEXEC by the user, there may be a member PROFILE, which will be executed for the user. This is a standard FOCUS profile.
The ddname FOCEXEC may be allocated in the MSO JCL or by a standard FOCUS PROFILE. If the partitioned data set userid.FOCEXEC.DATA exists and the FOCEXEC ddname has not been allocated, the FOCEXEC ddname will be allocated by default to this data set. The same is true for the MASTER ddname.
In the JCL used to start MSO, the partitioned data set allocated to ddname FOCEXEC has a member SHELPROF that will be executed for all users who log on. This is a standard FOCUS profile, which is described further in FOCUS for S/390 Overview and Operating Environments.
MSO FOCUS is a full-screen-only product. MSO FOCUS users are always in the Terminal Operator Environment (TOE), which provides windows for various terminal activities such as data input, output, and errors. The Terminal Operator Environment is described in detail in FOCUS for S/390 Overview and Operating Environments.
The figure on the following page shows the default Terminal Operator Environment screen with three windows: the Output window, the FOCUS Command window, and a History window. All input is done in the Command window. You can navigate between windows using the TAB key or the PF12 key.
If the keyboard is locked, the cursor may not be properly positioned on the Command window. The RESET and TAB keys can be used to position the cursor correctly in the Command window.
All output is sent to the Output window. If the output is too large to fit in the Output window, you must press the ENTER key or PF8 to display the rest of the output. When there is no more output to display, the cursor returns to the Command window.
Errors are displayed in a dynamically created window positioned in the Output window. The command that caused the error remains in the Command window. To clear the Error window, just erase the command (by blanking it out or pressing the Erase EOF key) and press ENTER. Alternatively, you can correct the command in error and press ENTER.
+ Output--------------------------------------------------------------->+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+----------------------------------------------------------------------+
+ History------------>+
| |
+ FOCUS Command-----------------------------------------------------+
| |
| |
| |
| |
+----------------------------------------------------------------------+
FOCUS attempts to draw the TOE windows with solid borders on terminals that are capable of displaying them. Otherwise, broken lines, drawn with standard 3270 characters, are used to create the window borders.
MSO issues a query command to the terminal to determine whether the terminal is capable of drawing solid lines. In some cases, a terminal will erroneously report the ability to display solid lines, resulting in various errors, most commonly PROGnnn communications errors or incorrectly drawn boxes. In this case, the command
SET SBORDER=OFF
may be issued, either from the terminal, or in a profile (see Profile Operation). This command may also be used if you prefer broken borders to solid borders.
It is also possible that a terminal will reply that it cannot display solid lines when it actually can. In this situation, the command
SET SBORDER=ON
may be issued.
Please note that some PC-based terminal emulators require enabling the APL character set in order to activate this capability.
Note: The TOE output screen will buffer any output messages during FOCEXEC program execution until control is returned to command level FOCUS. If the TOE output buffer fills to capacity, the screen will appear, even if control is still within a FOCEXEC. The window command
WINDOW SET CONTINUE ON
prevents this from happening.
A full set of commands is available for manipulating and customizing the Terminal Operator Environment. Refer to FOCUS documentation for a complete description of TOE and the TOE commands.
MSO sessions can be terminated by pressing an attention key in VTAM, CICS, and TSO.
From a VTAM, CICS, or TSO terminal, use the 3270 Attention key to interrupt a FOCUS command or end an MSO session.
Under CICS, MSO allows sites to specify a session termination key via the CICSBREAK parameter in the MSO configuration file. See The MSO Configuration File for further details. When you press the designated key, the MSO session is terminated and all the session resources are freed as if there was a normal exit from FOCUS.
Note: To exit from FOCUS normally, use the FIN command rather than the attention key.
The DYNAM command can be used to allocate and free MVS data sets. For information about the DYNAM Command consult the FOCUS for S/390 Overview and Operating Environments documentation.
MSO may be used in different ways. There are users who run production applications and use the Global allocations for the MSO region as a whole. There are also users who need to allocate their own MASTER or FOCEXEC PDSs. These users can use PRIVATEDD to perform allocations of PDSs for their exclusive use.
PRIVATEDD allows users to put their allocations in front of, in back of, or override the allocations for the MSO region. Applications can be tested, or new ones put into production without affecting the region as a whole.
To send output to a remote printer, use the DYNAM command. With DYNAM, the DEST parameter can be specified to cause a file to be sent to a JES printer.
The INDEX option of REBUILD must be executed as a batch job, using DD statements for the sort files. The sort files cannot be allocated via the DYNAM command.
For an example of REBUILD/INDEX, see FOCUS for S/390 Maintaining Databases.
GDDM graphics support is not available under MSO.
Submitting batch jobs via TED is supported in MSO. Enter TED to edit or view the JCL to be submitted, and issue the TED command:
SUBMIT
Simultaneous Usage (SU) is supported in MSO. The SU needs to be allocated either in the MSO startup JCL or via a DYNAM command. Once this is done, access to SU applications is exactly as described in FOCUS for S/390 Maintaining Databases.
The MSOINFO subroutine returns information on the environment in which it is run. The subroutine passes two parameters: the entity being requested and a return field where the results are placed.
MSOINFO is described in Site-Specific Customizations.
| Information Builders |