SysWorks©

SysWorks
User Guide


Previous Contents Index

SYLOGIN.COM

The SYLOGIN procedure is executed by the LOGINOUT image after setting up the process information, but before executing the users LOGIN.COM procedure (or or any other procedure as specified by the users authorization LGICMD attribute). It is defined by the system logical name SYS$SYLOGIN which is normally defined as

SYS$MANAGER:SYLOGIN.COM.

This procedure includes access to a number of user definable hooks as follows: User Procedure Usage LOGICALS.COM Define user based logicals in either the process, job or user logical name tables. dw-appl-code_ENTER.COM Enter procedure for the specified DECwindows application. dw-appl-code_EXIT.COM Exit procedure for the specified DECwindows application. dw-appl-code_LOGIN.COM Login procedure for the specified DECwindows application. The user procedures are described in further detail below.

4.3 Logical Names

This section describes the logical names that may be defined (typically in the users LOGICALS.COM procedure) to control the SysWorks interfaces.

appl_DEVELOPER_STYLE

A code indicating the style of the environment for an application. This is only relevant for development environment types. The following values are used: Style Usage COMMON Each developer edits in their own work sub-directory, but compiles, links, and runs are performed in the applications directories. INDIVIDUAL Each developer edit, compiles, links, and runs in their own work sub-directory.

appl_STATE

The state of the application. The following values are used: State Usage ARCHIVED ARCHIVING AVAILABLE BACKEDUP BACKINGUP BOOTED BOOTING BUILDING BUILT INSTALLED INSTALLING RECOVERED RECOVERING RESTORED RESTORING SHUTDOWN SHUTTINGDOWN STARTED STARTING STOPPED STOPPING UNAVAILABLE

SWRK_DECW_LOG_FILE_ACTION

This logical has a code indicating what action to take with regard to log files for DECwindows applications as its equivalence. The valid codes include: Code Usage LOG Create a log file and delete it if it is empty after the application runs down. SAVE Create a log file and always save its. Note that the log files will have a filename of image-name.LOG where image-name is the name of the DECwindows application image. The log file is placed in DECW$USER_DEFAULTS which is defined as DISK_USER:[user.DECW] or SYS$LOGIN:.

SWRK_REMOTE_WINDOW_APPLICATIONS

This logical name has a list of DECwindows application image names and optional remote nodes as its equivalence. The format of the equivalence is: appl-name[=node-name][\appl-name[=node-name][\...]] where each appl-name is the name of a DECwindows application image, and node-name is the name of the remote node on which to startup the application. By default, the remote node specified by the SWRK_REMOTE_WINDOW_NODE logical name is used.

For example:


$ DEFINE/TABLE=LNM$USER SWRK_REMOTE_WINDOW_APPLICATIONS -
_$ DECW$BOOKREADER=JHIA01\DECW$CALENDAR\DECW$MAIL

This command defines the logical such that the DECwindows Bookreader application will run on JHIA01 and the Calendar and Mail applications will run on the default remote node (See SWRK_REMOTE_WINDOW_NODE).

SWRK_REMOTE_WINDOW_NODE

This logical name has the default node for remote window applications as its equivalence.

SWRK_TELL_ALL_TYPE

This logical name has a code as its equivalence which indicates the types of nodes to send a remote command to with the NETTERM ALL, RW ALL, RWI ALL, RWX ALL and TELL ALL commands. See one of the indicated commands for details on the possible equivalence codes.

4.4 Symbols

This section describes the symbols defined by the SysWorks SYLOGIN.COM procedure.

CMD_DEVICE

This global symbol is defined by SYLOGIN.COM and has a value reflecting the primary command device.

CMD_TERMINAL

This global symbol is defined by SYLOGIN.COM and has a logical value reflecting whther the command stream is a terminal. This is set to true when SYS$COMMAND is a terminal (i.e. DEVCLASS is a terminal).

CMD_VT300

This global symbol is defined by SYLOGIN.COM and has a logical value reflecting whether the terminal is a VT300. This is set to true when SYS$COMMAND is a VT300 series terminal (i.e. when DEVCLASS is a terminal and DEVTYPE is VT300 series).

CMD_WINDOW

This global symbol is defined by SYLOGIN.COM and has a logical value reflecting whether the process is a window process. This is set to true when SYS$COMMAND is a mailbnox or a TWAn: terminal (i.e. when DEVCLASS is a mailbox or DEVCLASS is a terminal and DEVNAM starts with TW).

CUR_APP

This global symbol is defined by SYLOGIN.COM and the CONTEXT command and has as its value the name of the users current application. If the CUR_TYP symbol doesn't have a value of APPLICATION, this symbol should be blank.

CUR_ARC

CUR_ENV

This global symbol is defined by SYLOGIN.COM and the CONTEXT command and has as its value the name of the environment of the users current application. If the CUR_TYP symbol doesn't have a value of APPLICATION, this symbol should be blank.

CUR_GRP

This global symbol is defined by SYLOGIN.COM and the GROUP command and has as its value the name of the users current group. If the CUR_TYP symbol doesn't have a value of GROUP this symbol should be blank.

CUR_SCP

CUR_TYP

This global symbol is defined by SYLOGIN.COM and the APPLICATION, GROUP, HOME and USER commands and has as its value the type of the users users current environment. The values are listed in Table 4-3.

Table 4-3 CUR_TYP Values
Code Usage
APPLICATION Application environment. CUR_APP and CUR_ENV will have non-blank values.
GROUP Group environment. CUR_GRP will have a non-blank value.
HOME Users home environment. CUR_USR will have a value of the users username.
USER User personal development environment. CUR_USR will have a non-blank value (should be the users username).

CUR_USR

This global symbol is defined by SYLOGIN.COM and the HOME and USER commands and has as its value the username of the user. If the CUR_TYP symbol doesn't have a value of USER, this symbol should be blank.

CUR_VAR

CUR_VSN

4.5 Editing

SysWorks supports the standard OpenVMS editors with various modes as indicated in Table 4-4. It extends the use of these editors with the function keys indicated in Table 4-6.

Table 4-4 Editors and Modes
Editor Direct Subprocess Window
EDT Yes No No
EVE Yes Yes Yes
LSEDIT Yes Yes Yes, with DCL connection

4.5.1 Direct

In direct mode, the editor image is activated in the users current process each time the EDIT command is issued.

4.5.2 Subprocess

In subprocess mode, a subprocess is created when the EDIT command is first used, and subsequent uses of the EDIT command attach to that subprocess rather than having to reactivate the editor image for each command is being editor has been kept as a subprocess, the LOGOUT command will not permit the user to logout until the editor subprocess is wound down, typically by issuing an EXIT command frm within the editor.

4.5.3 Window

In window mode, a subprocess or detached process is started from the session manager using UtilitiesJ EVE or UtilitiesJ LSEDIT items. If LSEDIT is started this way, an EDIT command issued from DCL on a local DECterm or terminal will pass the edit request through to the window process, and cause it o grab focus on the screen.

Note that as per Table 4-1, when EVE or LSEDIT are started from the session manager or by the DO/MOVE command a CONTEXT APPLICATION, GROUP or USER command may be issued prior to starting the editor image.

Table 4-5 Editor Key Mode Differences
Mode Key Semantics
Direct F10, Gold-E Close all buffers and exit back to DCL.
  Gold-Q Delete all buffers and exit back to DCL.
Subprocess F10, Gold-E Close current buffer and return to DCL.
  F17 Return to DCL.
  Gold-Q Delete current buffer and return to DCL.
Window   Selection causes implied APPLICATION command.
  F10, Gold-E Write current buffer.
  Gold-Q Delete current buffer.

Table 4-6 Editor Key Extensions
Key Action
F10 Exit - behavior depends upon mode.
F17 Return to DCL - only used with the subprocess mode
Gold-= Toggle between one window and split windows
Gold-+ Split the current window.
Gold-- Remove the current window
Gold-[ Move window one screen to the left.
Gold-{ Move window to left of the buffer.
Gold-' Move window to cursor.
Gold-} Move window to right of the buffer.
Gold-] Move window one screen to the right.
Gold-B Toggle between the current buffer and the list of buffers.
Gold-C Close the current buffer.
Gold-D Delete the current buffer.
Gold-E Same as F10.
Gold-F Fill the currently selected region or paragraph.
Gold-M Toggle between the current buffer and the message buffer.
Gold-Q Quit - behavior depends upon mode.
Gold-S Toggle between the current buffer and the list of system buffers.
Gold-T Toggle between narrow and wide windows.
Gold-W Write out the current buffer.

4.5.4 EDIT

Same as the GOTO FILE command in LSE. May be abbreviated to ED or EDI.

4.5.5 F10

If in a subprocess, write the current buffer, close it and then attach back to the parent process. If in DECwindows, write the current buffer and close it. In all other cases just exit as per the EXIT command. This is the same behavior as Gold-E.

4.5.6 Gold_[

Shift the window to the current buffers left edge i.e column 1.

4.5.7 Gold_{

Shift the window one window width to the left in the current buffer.

4.5.8 Gold_'

Shift the window within the current buffer so that the cursor is visible.

4.5.9 Gold_}

Shift the window one window width to the right in the current buffer.

4.5.10 Gold_]

Shift the window to the current buffers right edge.

4.5.11 Gold_B

A toggle between showing user buffers and the current buffer.

4.5.12 Gold_C

Close the current buffer.

4.5.13 Gold_E

If in a subprocess, write the current buffer, close it and then attach back to the parent process. If in DECwindows, write the current buffer and close it. In all other cases just exit as per the EXIT command. This is the same behavior as F10.

4.5.14 Gold_F

Fill the current paragraph. (EVE only)

4.5.15 Gold_L

Convert selected object (or next word) to lowercase.

4.5.16 Gold_M

A toggle between the message buffer and the current buffer.

4.5.17 Gold_Q

If in a subprocess, close the current buffer and then attach back to the parent process. If in DECwindows, close the current buffer. In all other cases just quit as per the QUIT command.

4.5.18 Gold_S

A toggle between showing all buffers and the current buffer.

4.5.19 Gold_T

Toggle the screen width between 80/96 columns and 132 columns. In windows mode, also changes between normal and condensed font.

4.5.20 Gold_U

Convert selected object (or next word) to uppercase.

4.5.21 Gold_W

Write out the current buffer.


Chapter 5
Groups

The name of a group must be between 2 and 6 characters long.


Chapter 6
Applications

The name of an application must be between 2 and 6 characters long. Each application has a common area along with specific envionments. Each application environment may be considered to be much like the intersection between an application and an environment. The application environment has a name of the form appl_envr where appl is the name of the application and envr is the name of the environment. Physically, the application environment consists of a set of directories based on a rooted logical. Some of these are used to build the application during development maintenance and testing, others are used at runtime to contain data and reports etc.

Note that SysWorkstm uses an environment before application model for physical storage. That is, many applications share the same environment codes. This is useful in that application versions in the same phase of development may share the same environment code and each others definitions. For example, the FIN application in development may use the CORP application in development's data definitions, while FIN in maintenance uses CORP in maintenance's definitions.


Chapter 7
Disks

This section briefly describes the various disk objects used by SysWorkstm.

7.1 Disk Device

Each disk device is of a particular disk device type.

7.2 Disk Device Type

Each disk device type describes certain characteristics about the disks such as size, cluster size etc. Examples include RA92, RF73 and RZ58.

7.3 Disk Volume

A disk volume is built on a disk device, disk shadow set or disk striping set.

7.4 Disk Volume Set

One or more disk volumes may form a disk volume set. The resulting disk volume set has a size of the sum of the sizes of the individual disk volumes. OpenVMS allocates files and file extents on individual disk volumes within the volume set. A disk volume set should be backed up and restored as a single entity to maintain total integrity.

7.5 Disk Shadow Set

Between two and eight disk devices of the same disk device type may form a disk shadow set. The resulting disk shadow set has a size the same as its member disk devices. Disk shadow sets provide extremely high availability and integrity, whith a slight write preformance degradation, and an improved average read performance.

7.6 Disk Striping Set

Two, four or eight disk ,devices of the same disk device type may form a disk striping set. The resulting disk striping set has a size of the sum of the size of the individual disk devices. Disk striping sets provide improved I/O throughput, with the same access time.

7.7 Logical Disk

A SysWorkstm logical disk is a view of some disk(s) as perceived by a user or application. Each SysWorkstm environment has a corresponding logical disk view in the form of a search list of all logical sub-disks related to the environment. Other types of logical disk include Pathworks disk and file services (since these appear to the client PC or Macintosh as a disk), and InfoServer disk sets. The logical name used to point to each logical disk has the form DISK_logical-disk-name. The logical disks which are always present are described in Table 7-1

Table 7-1 Minimum Logical Disks
Logical Name Usage
DISK_APPL Search list of application common environment root directories across all mounted disk volumes.
DISK_GROUP Search list of group root directories acros all mounted disk volumes.
DISK_PROD Search list of application production environment root directories across all mounted disk volumes.
DISK_USER Search list of user root directories across all mounted disk volumes.

A typical set of logical disks are described in Table 7-2.

Table 7-2 Typical Logical Disks
Logical Name Usage
DISK_DEV Search list of application development environment root directories across all mounted disk volumes.
DISK_DTST Search list of application maintenance environment root directories acros all mounted disk volumes.
DISK_MNT Search list of application development testing environment root directories across all mounted disk volumes.
DISK_MTST Search list of application maintenance testing environment root directories across all mounted disk volumes.
DISK_CDBIN Search list of all consolidated distribution disks mounted on an InfoServer.
DISK_CDDOC Search list of all online documentation disks mounted on an InfoServer.

In a private or public installation of SysWorkstm these logical names must be defined in the site specific startup or login procedure.

In a system or turnkey installation, they are defined when the system is booted, or when a new environment is created.

7.8 Logical Sub-Disk

For logical disks based on OpenVMS rooted directory search lists, each root directory is represented by a logical sub-disk logical name. Logical sub-disk names are formed by suffixing a logical disk name with a digit. For example


$ show logical disk_user/full
   "DISK_USER" [exec] = "NEVER:" (LNM$SYSTEM_TABLE) 
        = "DISK_USER2:" 
        = "DISK_USER3:" 
1 "DISK_USER2" [exec] = "$1$DUA2:[USER_2.]" [concealed,terminal] (LNM$SYSTEM_TABLE) 
1 "DISK_USER3" [exec] = "$1$DUA3:[USER_3.]" [concealed,terminal] 
(LNM$SYSTEM_TABLE)

In a private or public installation of SysWorkstm these logical names must be defined in the site specific startup or login procedure.

In a system or turnkey installation, the root directory names of the form [envr_nn] are required at system boot time. As each disk volume is mounted, its master file directory is searched for directories of this form for inclusion in the logical disk search lists.

An illustration of all the disk layouts is contained in Figure 7-1.

Figure 7-1 Overall Disk Layouts



Previous Next Contents Index