Document revision date: 10 November 2000 | |
Previous | Contents | Index |
You must use the Start Session screen for logging in to DECwindows, but you can substitute your own logo for the Digital logo by running an application that displays your logo.
To do this, you need to define a global symbol in the DECW$PRIVATE_APPS_SETUP.COM file and create a DCL command file that contains the commands to display your logo.
To display your own logo on the login screen, you need to:
To create a custom logo, execute the following steps:
$ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE - _$ SYS$SPECIFIC:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM/LOG |
$ DECW$LOGINLOGO == "SYS$MANAGER:MYLOGO.COM" |
$ RUN DECW$EXAMPLES:ICO |
$ @SYS$STARTUP:DECW$STARTUP RESTART |
Restarting the DECwindows server disconnects all current client processes. |
If you are a system manager, you can set up user accounts to run only certain applications. For example, you might want users to use only the Bookreader application.
This section describes the following three methods for setting up dedicated DECwindows accounts:
You can define the global symbol DECW$SESSIONCOM in the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file so that when a user logs in, LOGINOUT runs a command file other than DECW$STARTSM.COM. This action bypasses Session Manager altogether.
In Example 4-1, DECW$SESSIONCOM is defined in DECW$PRIVATE_APPS_SETUP.COM to point to the private command procedure SYS$MANAGER: PRIVATE_SESSIONCOM.COM. The default command file is SYS$MANAGER:DECW$STARTSM.COM.
Because DECW$SESSIONCOM is defined in the system logical name table, it affects Session Manager startup for every user name. Your private command file must check the user name under which it is running and run the normal DECW$STARTSM.COM procedure for nondedicated accounts.
With this method, the following startup command procedures (normally executed from DECW$STARTSM.COM) do not run: SYLOGIN.COM, LOGIN.COM, DECW$SYLOGIN.COM, and DECW$LOGIN.COM. |
To modify the Session Manager command procedure:
Example 4-1 Using a Private Session Manager Command File |
---|
$ CREATE SYS$MANAGER:PRIVATE_SESSIONCOM.COM $! $! Check to see whether this is the dedicated DECwindows account. $! If it isn't, run the normal procedure to start Session Manager. $! $ username = F$USER() $ IF F$LOCATE("BOOK_READER", username) .NE. F$LENGTH(username) - THEN GOTO dedicated $! $! Normal, nondedicated DECwindows login $! $ @SYS$MANAGER:DECW$STARTSM $ EXIT $! $! Dedicated DECwindows login. Run Bookreader and then exit. $! $ dedicated: $! $ RUN SYS$SYSTEM:DECW$WSINIT $ display = F$TRNLNM("DECW$DISPLAY") $ RUN/DETACHED/OUTPUT='display' SYS$SYSTEM:DECW$MWM (1) $ RUN SYS$SYSTEM:DECW$BOOKREADER $ endsession := $DECW$ENDSESSION (2) $ endsession -noprompt (3) $ STOP/ID=0 (4) |
$ DECW$SESSIONCOM :== SYS$MANAGER:PRIVATE_SESSIONCOM.COM |
$ COPY SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE - _$ SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM |
$ @SYS$MANAGER:DECW$STARTUP RESTART |
You can define DECW$SESSIONMAIN in the SYS$MANAGER: DECW$PRIVATE_APPS_SETUP.COM file so that DECW$STARTSM.COM runs the specified command file instead of DECW$SESSION.EXE. Session Manager reads resource files and executes login command files but does not display the Session Manager menu bar. With this method, ensure that the End Session command does not prompt for confirmation.
When DECW$STARTSM.COM starts (that is, if DECW$SESSIONCOM has its default value), it starts Session Manager by executing the DCL command that is stored in the logical name DECW$SESSIONMAIN. To define this logical name, edit SYS$MANAGER: PRIVATE_APPS_SETUP.COM so that it defines the global symbol DECW$SESSIONMAIN as the DCL command to execute.
This method is similar to the one described in the Section 4.3.3.1 except that, with this method, DECW$STARTSM.COM executes the SYLOGIN.COM, LOGIN.COM, DECW$SYLOGIN.COM, and DECW$LOGIN.COM command procedures. Also, DECW$STARTSM.COM executes DECW$WSINIT.EXE, so the private command procedure does not need to do so.
To modify the Session Manager executable file:
Example 4-2 Modifying the Session Manager Executable File |
---|
$ CREATE SYS$MANAGER:PRIVATE_SESSIONMAIN.COM $! $! Check to see whether this is the dedicated DECwindows account. $! If it isn't, run the normal procedure to start Session Manager. $! $ username = F$USER() $ IF F$LOCATE("BOOK_READER", USERNAME) .NE. F$LENGTH(USERNAME) - THEN GOTO dedicated $! $! Normal, nondedicated DECwindows login $! $ RUN SYS$SYSTEM:DECW$SESSION $ EXIT $! $! Dedicated DECwindows login. Run Bookreader and then exit. $! $ dedicated: $! $ display = F$TRNLNM("DECW$DISPLAY") $ RUN/DETACHED/OUTPUT='display' SYS$SYSTEM:DECW$MWM (1) $ RUN SYS$SYSTEM:DECW$BOOKREADER $ endsession := $DECW$ENDSESSION (2) $ endsession -noprompt (3) $ STOP/ID=0 (4) |
$ DECW$SESSIONMAIN :== @SYS$MANAGER:PRIVATE_SESSIONMAIN.COM |
$ COPY SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE - _$ SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM |
$ @SYS$MANAGER:DECW$STARTUP RESTART |
After entering the user name and password of the dedicated account,
Bookreader starts and the Session Manager menu bar is not displayed.
When the user exits Bookreader, the PRIVATE_SESSIONMAIN.COM procedure
performs an End Session operation and then logs out. The End Session
command displays a DECwindows Start Session screen.
4.3.3.3 Modifying the Session Manager Profile File
This method starts Session Manager normally, but the system manager customizes its menus to remove any applications that are not started automatically. By removing certain applications, you can limit user access to applications.
With this method, the Session Manager menu bar is displayed, and the user can interact with whatever dialog boxes the system manager does not disable.
To modify the Session Manager profile file:
Do not remove Window Manager from the automatic startup list. |
Automatic Startup...
Menus...
Menu Bar...
Save Session Manager
To test your changes, log in to the dedicated account from the DECwindows login box. Bookreader and Session Manager should start up by default, and you should not be able to start any other application. To log out, choose End Session from the Session Manager menu.
If you decide to make the account nondedicated again, or if you want to
make changes in a dialog box that you have removed from the system menu
bar, delete or rename the file VUE$PROFILE.VUE$DAT in the dedicated
account's SYS$LOGIN directory.
4.4 Modifying Session Manager Behavior
You can modify the behavior of the DECwindows Session Manager by using several logical names. These logicals are not normally used; however, they may help in special circumstances, such as running two Session Managers on the same system. Table 4-2 lists the logicals and their meaning.
Logical Name | Meaning |
---|---|
DECW$VUENOAUTOSTART | Prevents applications in the Session Manager autostart list from being started. |
DECW$VUENORESET | Prevents Session Manager from resetting the display server when Session Manager exits. |
DECW$VUELOGINOUTPUT | Saves any output from the login command files (SYSLOGIN, LOGIN, DECW$LOGIN) as applications start up from Session Manager. You can access this information by clicking on the SHOW OUTPUT button in the Work in Progress dialog box, which is located in the Session menu in the Session Manager window. |
You can define these logicals in a DECterm or in the login command files (SYSLOGIN, LOGIN, DECW$LOGIN). To set any of these logical, define the logical name to any value, as in the following example:
$ DEFINE DECW$VUENOAUTOSTART 1 |
Most DECwindows applications provide dialog boxes that contain options for customizing your DECwindows environment and saving your settings. For example, using Session Manager Options menu, you can look at many predefined settings and then choose and save new settings.
However, not all applications provide dialog boxes for changing and saving settings. For example, some applications let you change and save the size or location of the application's main window and others do not. To change and save settings that are not available from dialog boxes, you can specify resources in a DECW$XDEFAULTS.DAT file.
Use extreme caution when modifying resources for the following reasons:
|
To use resources to change application settings, create a file (DECW$XDEFAULTS.DAT) in the directory specified by the logical name DECW$USER_DEFAULTS. In this file, specify the resources for the application settings you want to change. Alternatively, if your changes are specific to one application, you can modify that application's resource file (for example, DECW$MAIL.DAT).
Note that each resource specification in the DECW$XDEFAULTS.DAT file follows explicit syntax rules. For more information about the resource syntax, see the VMS DECwindows Guide to Xlib (Release 4) Programming: MIT C Binding or X Window System.
See Using DECwindows Motif for OpenVMS for resource information for the following applications:
This section describes how to define print formats and lists the logical names and associated print formats for DECwindows Motif software. Depending on your configuration, DECwindows Motif customization tasks can include defining logical names to specify print formats.
Before you start up the system, edit the OpenVMS startup procedure to
define the logical names that associate print queues with print
formats. This startup procedure will subsequently call the
DECwindows Motif startup procedure. You can also add these logicals to
your login command file.
4.6.1 Defining Print Formats
Many DECwindows Motif applications use the Print dialog box to queue files or screens to a printer. By default, all printing devices on the system are displayed in the Printer list box. However, print queues can be associated with print formats through the definition of logical names. You define the logical name in the OpenVMS startup command procedure before the call to the DECwindows Motif startup procedure. Separate the list of print queues with commas or spaces, with the first queue being the default choice.
You can customize the list of printer queues displayed in the Print dialog box by defining any of the logical names in Table 4-3. This method is faster than making the Print dialog box derive the names of all the queues on the system, most of which do not apply to the print format under consideration. The following example shows how to define logical names for print formats in the OpenVMS startup files:
$ Define DECW$PRINTER_FORMAT_TEXT "CLUSTER_LN03,CLUSTER_PRINT, - _$ ANSI_ARTWRK,ANSI_PROTON" $ Define DECW$PRINTER_FORMAT_LINE "CLUSTER_PRINT" $ Define DECW$PRINTER_FORMAT_ANSI2 "CLUSTER_LN03,ANSI_ARTWRK,ANSI2_PROTON" $ Define DECW$PRINTER_FORMAT_ANSI "CLUSTER_LN03,ANSI_ARTWRK,ANSI_PROTON" $ Define DECW$PRINTER_FORMAT_PS "PS_ARTWRK,PS_PROTON" $ Define DECW$PRINTER_FORMAT_REGIS "SYS$NULL" |
For example, if DECW$PRINTER_FORMAT_ANSI2 is defined as CLUSTER_LN03,
ANSI_ARTWRK, ANSI2_PROTON, then when you select ANSI2 from the Print
Format list box, only CLUSTER_LN03, ANSI_ARTWRK, and ANSI2_PROTON are
shown in the Printer list box, with CLUSTER_LN03 being the default
choice.
4.6.2 Logical Names and Print Formats
Table 4-3 lists the logical names and the associated print formats in the DECwindows Motif product.
Logical Name | Print Format |
---|---|
DECW$PRINTER_FORMAT_DEFAULT | Default |
DECW$PRINTER_FORMAT_TEXT | Text |
DECW$PRINTER_FORMAT_LINE | Line printer |
DECW$PRINTER_FORMAT_TERM | Terminal |
DECW$PRINTER_FORMAT_ANSI2 | ANSI2 |
DECW$PRINTER_FORMAT_ANSI | ANSI |
DECW$PRINTER_FORMAT_PS | PostScript |
DECW$PRINTER_FORMAT_REGIS | ReGIS |
DECW$PRINTER_FORMAT_TEK | TEKTRONIX |
DECW$PRINTER_FORMAT_DDIF | DDIF |
You can define the logical names in systemwide logical name tables and users can override the logicals when necessary.
Previous | Next | Contents | Index |
privacy and legal statement | ||
6300PRO_006.HTML |