Page 1

Product Information

Product name	Product number
USER ENVIRONMENT version D07	210518D

Description of Product

USER ENVIRONMENT is a supplement to the operating system. It provides security functions and a personal user environment for high-level ND systems.

Among the security functions are login control for users and servers, access control, log facilities and a user group concept.

The personal user environment includes tailormade menu systems, language handling (the user will run products in their own language) and personal setups in subsystems (e.g. default printer in NOTIS-WP).

User information in USER ENVIRONMENT version D may be shared by several machines.

Reasons for New Version/Revision

+--------------------------------------------------+
| Easier maintenance of the profiles in USER       |
| ENVIRONMENT.                                     |
|                                                  |
| Improved security in local networks.             |
|                                                  |
| Meet requirements from other products.           |
|                                                  |
| Make it possible to use Remote Shell with USER   |
| ENVIRONMENT.                                     |
+--------------------------------------------------+

Table of Contents

Section	Page
Prerequisites	2
Dependencies	4
Documentation	4
Installation procedure	5
Modifications	12
Errors corrected	15
Errors known but not corrected	16

---

Page 2

Product Information

Date	ND ServiceTeam A.S	Page
91.12.13		2 of 16

Product name	Product number
USER ENVIRONMENT version D07	210518D

1 Prerequisites

The following is required in order to use this product.

1.1 Hardware Prerequisites

The following hardware must be present:

CPU type (any of the following)

• Any ND-100 (100, 110, 120) with CX instruction set.

Floating format: All

1.2 Software Prerequisites

The following software must be available on the system before the product is installed:

Operating system:

Name	Version/Revision
SINTRAN	K VSX (any generation and patchfile) (or later versions)

Other software:

Product name	Product number
XMSG	210373 (any version)
UE-ERRORS	210586 D07 or later

ND-895256EN.1A

---

Page 3

Product Information

Date: 91.12.13
ND ServiceTeam A.S
Page 3 of 16

---

Product Name

USER ENVIRONMENT version D07

Product Number

210518D

---

1.3 Other Prerequisites

The following are necessary for this product to be used.

Minimum Permanent Mass Storage:

User Area	Space (pages)	Number of Files
USER-ENVIRONMENT¹	2000	48
SYSTEM	20	1

	Minimum	Maximum
Number of segments (ND-100)²	9	13
Number of RT descriptions	1	1
Number of XMSG ports³	3	3

Space required on segment files: 1025 pages

XMSG variable 'Max. buffer space owned by a task in bytes' (X5MTS) should be set to 32000.

---

Notes

¹ Extra space and files are needed:

• For each additional language: about 240 pages, 15 files
• For the database file(s): If the existing database is for the C version, about 3 times the size of existing database, 2 files.
• For a temporary file when you create Local Domains: about the size of a database file, 1 file.

² All segments are named.

³ Each user process opens an XMSG port when accessing UE. Only one XMSG port is named.

---

ND-895256EN.1A

---

Page 4

Product Information

Date: 91.12.13
ND ServiceTeam A.S
Page: 4 of 16

Product name	Product number
USER ENVIRONMENT version D07	210518D

2 Dependencies

In addition to the above listed hardware and/or software prerequisites, the following dependencies exist between this and other products. The hardware and software listed below may, for example, be necessary to use the product’s full functionality.

2.1 Software Dependencies

There are dependency relationships between this product and the following software:

Product name	Product number
COSMOS Basic Module F03 (or later)	210374F
(for SINTRAN version L)
Alternatively:
COSMOS Basic Module E04 with	210374E
patch for 'No such page' problem
(SIS report number 5)
or later revisions (for SINTRAN version K)

Nature of dependency
COSMOS is needed to connect computers together in a Local Domain.

3 Documentation

Included (distributed free with product)

Title	Number
User Environment User Guide	860320.1
User Environment Reference Manual	860194.4

Optional (must be purchased)

Title	Number
User Environment Library Routines	860261.2

ND-895256EN.1A

[Scanned by Jonny Oddene for Sintran Data © 2024]

---

Page 5

Product Information

Date	ND ServiceTeam A.S	Page 5 of 16
Product name	Product number
USER ENVIRONMENT version D07	210518D

4 Installation Procedure

4.1 Automatic Installation

The system may be delivered on:

• 1.2 Mbyte, 8 inch or 5¼ inch double-sided diskettes

You may install the complete UE, or add extra languages to an existing UE.

ADP Segment

Before the installation, please decide if you want to use the ADP segment on your machine. If you do, make sure that it is turned on by calling the SINTRAN III Configuration program. Choose the background option and "MON ADP" should be 1. If you change it from 0 to 1, you must perform a cold-start to activate it.

If you are using the ADP-segment, UE needs one system LAMU for each terminal. Choose the LAMU option in SINTRAN III Configuration program to determine this.

Old UE Versions

If the old database are version C, the installation program will convert the existing C version database to the D version format.

If the old database are version B and you still want to transfer all users to the D version, you must install the C version of User Environment before the D version. And finally if you have A version database, you first have to install the B version, then the C version before installing the D version of User Environment.

However, if you have the B version (or the A version) we recommend that you delete the old database files and define all users again. You should then delete the files:

(USER-ENVIRONMENT)UE-USER-PROFILE:DATA
(USER-ENVIRONMENT)UE-TERM-PROFILE:DATA

SINTRAN Extended Security

If you are using the forced password option of the extended security data field in SINTRAN-SERVICE (bit 4 in EXSECURITY set to one), and if the SINTRAN user area USER-ENVIRONMENT is not yet created, you must create this user area and give it a password before you start the installation.

ND-895256EN.1A

[Scanned by Jonny Oddene for Sintran Data © 2024]

---

Page 6

Product Information

Date	ND ServiceTeam A.S	Page
91.12.13		6 of 16

Product name	Product number
USER ENVIRONMENT version D07	210518D

Name on Local Machine

The local machine MUST have a name before you start installation. If this is not done, enter XMSG-COMMAND program and define it using the command DEFINE-REMOTE-NAME.

This name should NOT be changed while UE is running. If you want to change it, you must run the program UE-CHCPU (see 5.4). If the installation is performed without a name on the local machine, it will not be possible to edit the UE-FUNC,SUPERVISE MACHINE menu. To correct the problem, you must stop UE, define a local machine name, and use the UE-CHCPU program, giving a as input when the machine name is asked for.

XMSG must be running when the installation program is started.

How to Start the Installation

Install User Environment from a terminal with the same terminal type as most users will use later on. This will save one second at startup of every UE module, because the terminal tables (DDB-tables) will not have to be read again.

The installation must be run from SINTRAN, not from a menu! If UE is running, you should either be logged in, or the installation must be run from terminal number 1.

• Log in as SINTRAN user SYSTEM.

• Insert the diskette containing the directory name 210518D07-<lg>-01D into the diskette station
  • NOTE! <lg> means language suffix ('EN' for English)

• Execute these commands (operator input is underlined and parameters are enclosed in angle brackets).

@ENTER-DIRECTORY,210518D-<lg>-01D~
DEVICE NAME: FLOPPY-DISC-<controller-no>~
DEVICE UNIT: <floppy-unit>~
@(210518D-<lg>-01D:FLOPPY-USER)IN-UE-<lg>-D~

The installation procedure has now started, it is self-explanatory.

After installation, check the file IN-UE--D:LOGG, to see if any errors have occurred.

If everything went OK, skip the next section and read "4.3 Updating the mode jobs" on page 10.

ND-895256EN.1A

[Scanned by Jonny Oddene for Sintran Data © 2024]

---

Page 7

Product Information

Date	ND ServiceTeam A.S	Page
91.12.13		7 of 16

Product name	Product number
USER ENVIRONMENT version D07	210518D

If the installation failed

If installation failed before copying was complete, or if you have installed with the ADP-segment, you should start all over again.

If it failed after copying was complete, and if you are not using the ADP-segment, you can skip parts 2 and 3 of the installation program. Run part 1 and answer NO to the question:

Do you want to copy the files from floppy?

After part 1 is completed, enter part 4 directly.

Changes in installation procedure from C version

Some questions that had to be answered in installation of C version are removed. This is because the relevant configuration parameters now can be changed while UE is running (see the manual).

4.2 Manual Installation

Manual installation may be troublesome and should only be done by experienced operators, e.g. ND service personnel. All details cannot be presented, but correct states during installation are presented below.

Start by performing the same initializations described in the section "Automatic Installation".

When using the expression "... on the form UE-XX ...", it concerns any name (file, segment, etc.) which matches the pattern where 'X' is any character(s). When using "", it means the language currently being installed, e.g. "EN" for English.

A) Stop UE.

If the C version is currently running, remove all reentrant subsystems on the form UE-XX-C, and enter the RT-LOADER to clear and delete the segment UESEG, UEMEUT and UEPMEX.

---

ND-895256EN.1A

---

Page 8

Product Information

Date	ND ServiceTeam A.S	Page
91.12.13		8 of 16

Product name	Product number
USER ENVIRONMENT version D07	210518D

Instructions

B)

Delete all files on user area USER-ENVIRONMENT belonging to the C-version of UE (files on the form UE-XX-C and UE-XX-<1g>-C) except:

• UE-USER-PROFILE:DATA,
• UE-TERM-PROFILE:DATA,
• UE-ENABLE:MODE
• Customized menu systems

The following files should always be deleted:

• BE-USER-PROFILES:DATA
• BE-TERM-PROFILES:DATA

Rename the file UE-LOGFILE:DATA to UE-DATABASE:LOG.

Ensure that the user area USER-ENVIRONMENT has (at least) 1900 free pages, and that user area SYSTEM has (at least) 230 free pages.

Note: In addition to these requirements, user area USER-ENVIRONMENT needs some space for the database files. The space needed is approximately 1.5 times the size of the old database files. Furthermore, you need the same amount of space for the backup file.

C)

Copy the file DDBTABLES-E09 from the floppies to user area SYSTEM if necessary. There should at this point only be one DDBTABLES-E file on SYSTEM.

D)

Copy the rest of the files to user area USER-ENVIRONMENT except:

files on the form IN-UE-<1g>-D:YY (3 or 4) and UE-ENABLE:MODE (if this file already exists, else copy).

E)

If ADP segment is wanted:

• Use the Sintran III Configuration program to ensure that ADP is available (see automatic installation)
• @Delete-File UE-LOAD:MODE
• @Rename-File UE-ADP:MODE, UE-LOAD
• Enable the ADP-patch in UE-PATCH:MODE (see this)

If ADP is not wanted:

• @Delete-File UE-ADP:MODE

---

ND-895256EN.1A

[Scanned by Jonny Oddene for Sintran Data © 2024]

---

Page 9

Product Information

Date	ND ServiceTeam A.S	Page
91.12.13		9 of 16

Product name	Product number
USER ENVIRONMENT version D07	210518D

F) If there are existing C-version databases to be converted to D version:

• Enter user area SYSTEM
• Run (U-E)UE-DB-CONV,,,
• Check that this was OK (no error messages)

G) Run (USER-ENVIRONMENT)UE-LOAD:MODE and check the output for errors.

• ("NO SUCH NAME", "ILLEGAL SEGMENT NAME", etc. is accepted, but not error messages like "SEGMENT IN USE" and "NO MORE SPACE")

H) Do @UE-FUNC START-SERVER

I) Go to "DUMPING NEW STANDARD LANGUAGE AND DDBTABLES" described below.

Installing New Language

When UE version D is running and you want to install a new language, do the following:

A) Enter the diskette with directory 210518D--XX.

B) Copy the rest of the language files to user area USER ENVIRONMENT. (All files on the form UE-XX--D where is the language code.)

C) If the new language is to be the standard language, continue with "DUMPING NEW ...."

Dumping New Standard Language and DDBTables

If you want to change the modules’ standard language or the standard DDBTABLES, do the following from the most common terminal type:

A) Enter user area USER-ENVIRONMENT and execute the following commands (push when asked for file name, is code for new language):

@UE-FUNC ;(USER-ENVIRONMENT)UE-FUNC-<lg>
@UE-PMAN ;(USER-ENVIRONMENT)UE-PMAN-<lg>
@(UE-LOGIN ;(USER-ENVIRONMENT)UE-LOGIN-<lg>
@(UE-RUN ;(USER-ENVIRONMENT)UE-STDHIE-<lg>
@(UE-MEMAIN ;(USER-ENVIRONMENT)UE-ME-<lg>

ND-895256EN.1A

---

Page 10

Product Information

Date	ND ServiceTeam A.S	Page 10 of 16
	Product Information

Product name	Product number
USER ENVIRONMENT version D07	210518D

---

B) Enter user area SYSTEM and run (USER-ENVIRONMENT)UE-LOAD:MODE.
Please check the output as previously.

4.3 Updating the Mode Jobs

The cold start mode job (usually called HENT-MODE:MODE) should contain the following somewhere after entering directories:

@MODE (USER ENVIRONMENT)UE-LOAD:MODE,,
@MODE (USER ENVIRONMENT)UE-ENABLE:MODE,,

The warm start mode job (usually called LOAD-MODE:MODE) should contain the following somewhere after starting XMSG, but before starting NOTIS-DS and NOTIS-ID.

@UE-FUNC START

There should exist a mode job to shut down the machine smoothly (e.g. STOP-MODE:MODE). The following should be included somewhere after all terminals are stopped:

@UE-FUNC STOP

4.4 Correct State When UE is Running

After a normal installation and UE is running, the following segments, RT-program and subsystems should exist.

RT-program
UEXPS should have state "IN TIME QUEUE" (can be "ACTIVE" but never "PASSIVE" only).

---

ND-895256EN.1A

Scanned by Jonny Oddene for Sintran Data © 2024

---

Page 11

PRODUCT INFORMATION

Date: 91.12.13
Page: 11 of 16
Company: ND ServiceTeam A.S

Product Details

Product name	Product number
USER ENVIRONMENT version D07	210518D

Segments and Subsystems

UEXPS uses the segments:

Segments	Subsystems using segments
UESEGM	UE-FUNC-D UEFUMA
UESEGB	UEFUEX
UESEGD	UE-LOGIN-D UEDLOG
	UE-PMAN-D UEPMAN1
	UEPMAN2
	UEPMAN3
	UE-MENU-D UEDMENU
	UE-EDIT-D UEMEMA
	UEMEUT
	UE-RUN-D UEDRUN

Customization

If a smaller variant of UE is wanted, you can edit the file (USER-ENVIRONMENT)UE-LOAD:MODE. The following changes are possible:

• If menu systems are not used (or no new menu systems are to be made), UE-EDIT-D (in version C called UE-ME-C) can be removed with the segments UEMEMA and UEMEUT.

• The subsystems UE-RUN-D, UE-LOGIN-D and UE-MENU-D do not need names on their segments. Thus the segment names UEDRUN, UEDLOG and UEDMENU may be deleted. NOTE: Only delete the names, not the segments. In UE-LOAD, you can remove the segment names as they appear as third parameters in the command @DUMP-PROGRAM-REENTRANT.

• If necessary, it is possible to remove subsystem UE-LOGIN-D. The startup time during login, e.g. the time from pushing escape to receiving the login picture, may be a little longer after this.

• If running Local Domain, it is possible to remove UE-PMAN (with its three segments) on slave machines with too little space (on disk or segment files). UE-PMAN must then be entered at other machines. NOTE: It will no longer be possible to edit terminal profile attributes.

• If no one enters the menu system from SINTRAN, UE-MENU can be removed. We do not recommend this, because UE-MENU takes only one page on the segment file.

UE-FUNC and UE-RUN should not be removed.

---

ND-895256EN.1A

---

Page 12

Product Information

Date	ND ServiceTeam A.S	Page 12 of 16
Product name	Product number
USER ENVIRONMENT version D07	210518D

5 Modifications Since Version C

5.1 New Functions/Commands

There are four major additions in USER ENVIRONMENT version D. These are:

The Local Domain concept. Machines may be connected to form a cluster which is called a Local Domain (LD). In an LD, the profiles are common for all the machines. A tool for defining/deleting an LD and including/removing machines in the LD is included.

The UE-PMAN. The profile manager (UE-PMAN) has become an advanced tool for maintaining the profiles in UE.

The UDO concept. The concept of "User Defined Object" (UDO) is introduced. A UDO may be used for access control by other products and program systems.

The generalized login. By using the program library, other process types may log in, several processes may run the same session and one process may log in several times.

Please refer to the manuals for more detailed descriptions.

5.2 Changed Functions/Commands

Error codes. The meaning of some of the error codes are slightly modified. E.g. the error message "No profile found for this user or terminal" is changed to "No profile found". It will be returned to most calls which involve reference to any non-existing profile, that is: user profile, terminal profile, user group profile, UDO profile, and so on.

Authorization. The number of authorization levels is expanded from two to six: Guest, Public, Operator, Server, Programmer and Supervisor.

ND-895256EN.1A

---

Page 13

Product Information

Date	ND ServiceTeam A.S	Page
91.12.13		13 of 16

Product name	Product number
USER ENVIRONMENT version D07	210518D

Start up

When starting UE (@UE-FUNC Start) the starting process (usually warm start (LOAD-MODE:MODE)) will automatically be logged in to UE with Operator access. If the UE database is empty, the login process will get Supervisor access. Then after starting UE for the first time, it will be possible to start @UE-PMAN directly to define users. The automatic login in to UE may cause problems when trying to start Multi-Machine Operator-Environment, and it is therefore recommended to include the following line before you start it:

@(USER-ENVIRONMENT)UE-PLIB-TEST,LOGOUT

UE-FUNC Start-Server

UE-FUNC Start-Server will not wait for the server to start before it returns. This may cause problems in the start up of the machine (in LOAD-MODE) if subsystems depending on User-Environment is started immediately after the command UE-FUNC Start-Server. A program called WAIT-FOR-UE:PROG on user User-Environment may be used to wait for the server to start. The following may be put into the LOAD-MODE job after @UE-FUNC START:

@(USER-ENVIRONMENT)WAIT-FOR-UE

The UE-FUNC Change-User-Area previously made it possible to specify a user area which was unique with respect to a user’s alternative areas. Now, the user area specified must be unique on the given machine.

Default user area

This is NOT the same as Main user area used in previous versions. That a user has a default user area does NOT mean that he has access to this user area. To give a user access to a user area, the user area has to be in the users list of Legal user areas.

Please refer to the manuals for more details.

5.3 Removed Functions/Commands

• Security codes in user groups are removed.
• The possibility to go to the User-Area-Manager from UE-PMAN is removed.

---

ND-895256EN.1A

---

Page 14

Product Information

Date 91.12.13	ND ServiceTeam A.S
Page 14 of 16
Product Name	Product Number
USER ENVIRONMENT version D07	210518D

5.4 Other Modifications

The menu editor is renamed from UE-ME-C to UE-EDIT-D.

Changing of CPU Number

UE will no longer do an automatic change of CPU-number on its database if the CPU number is changed (or the database are moved to a new machine). If a CPU number is to be changed, or the database are moved from one machine to another, a program called UE-CHCPU (which is copied to the user area USER-ENVIRONMENT) is required. YOU MUST RUN THIS PROGRAM BEFORE YOU START THE UE PROFILE SERVER. This program asks for the name of the database, the name and CPU number of the old machine, and converts all information related to that old machine, so that it corresponds to the current machine (i.e. the machine the program is running on). The UE-CHCPU program must be executed from user area SYSTEM.

Verification of UE Database

A problem that may occur with the UE database (file: UE-DATABASE:DATA), is that the number of pages in the object entry does not correspond with the number of pages in the file. If you have an LD, it will make the distributed copies of the database become inconsistent. A symptom on this problem, is that you get the error message 'database has been corrected, information may be lost’, after verification of the database on the slave machine(s).

A way of checking if this is the case and correcting it, is to run the program (USER-ENVIRONMENT)UE-EX-VER-D:PROG. This program will ask for the database file name and check if the number of pages in the object entry corresponds with the number of pages in the file. If the numbers are equal, it returns with OK, and ask if you want to perform a UNLOAD/LOAD of the database, which may decrease the size of the database file. If the numbers are unequal, a UNLOAD/LOAD of the database will automatically be started.

In the UNLOAD/LOAD process, the program requires a file to make a temporary copy of the database.

You will be asked for this file with the question 'Unload File name:'. The program will report some ISAM information about the database file, ask for Unload File name:, and then do what is called UNLOAD and LOAD in ISAM, i.e. the content of the database file will be copied to the 'Unload File' without indexes, and then loaded back to the database file.

ND-895256EN.1A

---

Page 15

Product Information

Date	ND ServiceTeam A.S	Page 15 of 16
Product name	Product number
USER ENVIRONMENT version D07	210518D

USER ENVIRONMENT version D07 and Remote Shell

In order to integrate Remote Shell and UE, some patches must be made to UE. These patches are described in the file UE-PATCH-D:MODE. The files UE-LOGIN-D:PROG and UE-PSER-DATA-D:PROG should be patched.

Database-file on another user area

It is possible in USER ENVIRONMENT version D07 to put the database files on a user area different from USER-ENVIRONMENT. By running the mode-file UE-TP-PATCH:MODE (@MODE UE-TP-PATCH:MODE), the user area UE-DATABASE-USER will be assumed as the user area where the database files reside. If the database should be moved to another user area, you must first install UE normally, then UE should be stopped, UE-TP-PATCH:MODE should be run, the database files should be moved (UE-DATABASE:xxxx and UE-1575B-POOL:DATA) to user UE-DATABASE-USER, UE-LOAD:MODE should be run (@MODE UE-LOAD:MODE), and then UE may be started.

Starting UE without taking backup

In USER ENVIRONMENT version D07 it is possible to shorten the start up time of the UE server, by not taking any backup of the UE-DATABASE:DATA file when the server is started. This is described in the UE-PATCH:MODE file. If this is done, you must ensure that a backup of the UE-DATABASE:DATA file is taken periodically in some other way.

6 Errors Corrected

The problem with the monitor call 310 (In8AndFlag) in UE-RUN and in UE-LOGIN, is corrected.

The problem of overwritten UE segments, causing uncontrolled stops of the RT program UEXPS, is corrected.

The internal table, causing a problem with "NO MORE SPACE ON USER USER-ENVIRONMENT", is expanded.

The possibility of editing the password of the default user, is removed.

The problem that a login takes very long time when the ASCII form of a CPU-number contains a Space or a #, is fixed.

ND-895256EN.1A

---

Page 16

Date	ND ServiceTeam A.S	Page 16 of 16
Date 91.12.13	PRODUCT INFORMATION

Product name	Product number
USER ENVIRONMENT version D07	210518D

7 Errors Known But Not Corrected

Using 'Task-in-user-area' to start some products (e.g. NOTIS-WP) may cause the wrong user area to be present after the task is completed. This has not been corrected.

A workaround for this problem is to start NOTIS-WP with the option of clearing the scratch file:

@NOTIS-WP %<drawer>,<folder>,<document>

When Stop-Terminal/Timeout happens and the user is in a UE-Menu, the UE Scratch file is not reset.

ND-895256EN.1A

---