1. technology and computing
2. computer security
3. network security

Quintessential School Systems
U ser Maintenance
and Security:
How to Use Maintain
User Data (MEN020)
Copyright © 2000 by Quintessential School Systems
2 0 E 20 t h Av e n ue , S a n M a t e o C A 9 44 0 3 - - - Vo ic e 6 5 0/ 3 7 2 -0 2 0 0 - - - F ax 6 5 0 / 3 72 - 3 38 6 - - - ww w. q s s . c o m
Published: July, 2000
Copyright Notice
Copyright © 2000
Quintessential School Systems
This document contains proprietary information which is protected by copyright. All
rights are reserved. No part of this document may be photocopied, reproduced, or
translated to another language without the prior written consent of Quintessential
School Systems.
The information contained in this document is subject to change without notice.
QUINTESSENTIAL SCHOOL SYSTEMS MAKES NO WARRANTY OF ANY
KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. Quintessential School Systems shall not be liable for errors contained herein or use of this material.
Table of Contents
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview of Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Security Settings and Security Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Global, District, and User Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Combining the Three Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Include Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Option Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Add, Change, or Inspect a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Select a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Maintain User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Maintain Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Delete a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Change Global Security File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Security File Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Select File to Maintain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Maintain the File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Copy a User File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Purpose
User Profile
Purpose
Maintain User Data (MEN020) allows you to define the following for authorized
users of QSS/OASIS software:
♦ User Profile
♦ Security Settings
User Profile
Every logon ID that allows a user to run the QSS/OASIS must be defined in two
places:
♦ An MPE user and account name that allows logging onto the HP e3000.
♦ As a user profile for the Menu System defined with Maintain User Data
(MEN020).
The user profile for QSS/OASIS includes the following information:
♦
♦
♦
♦
♦
♦
♦
♦
Password for report job streams
First Menu System screen that displays when the user logs on
Whether to allow access to QSS/OASIS programs
Whether the user is a standard or super user
Printer device for reports
District and site for the logon ID
Fiscal year for the logon ID
User-level JCWs for controlling program options
Security Settings
There are three levels of security settings:
♦ Global default security for all districts
♦ Default security for each district
♦ User-level security settings
Each level of security settings is contained in a separate file that can contain up to 960
lines. Each line contains a security matrix that controls options for a particular program. For example, the security matrix for the TC Screen controls whether a user can
add new accounts while filling in time card data.
Each security matrix has two parts:
07/2000
Copyright © QSS, 2000
1
User Maintenance and Security
How to Use Maintain User Data (MEN020)
♦ The program name identifies the program to which the matrix applies. For example, PP0010I0 is the name for an option that allows you to specify which screens a
user can maintain with Update Per/Pay Master Files (PP0010).
♦ The parameters is a list up to 60 characters long. It is different for each security
matrix. For PP0010I0, the parameters are a list of screen codes for master file. For
other matrices, the parameters are a list of flags for various levels of access. Each
security matrix has its own list of parameters.
Each user’s access permissions are based upon combining all three levels of files.
User security matrices take precedence over district and global matrices, and district
matrices take precedence over global. If the security matrix for a program is not
defined at any level, the defaults for the program apply. When a user logs on, the
Menu System builds a temporary file for each session that contains a composite of
security matrices from all three levels.
You can use include files to simplify maintenance of security matrices. An include
file is a file that contains a series of security matrices. With a special one-line command, you can incorporate the entire contents of one or more include files into any of
the three levels of security settings.
2
Copyright © QSS, 2000
07/2000
Overview of Security Settings
Security Settings and Security Matrices
Overview of Security Settings
This overview looks at the following aspects of security settings:
♦
♦
♦
♦
Security Settings and Security Matrices
Global, District, and User Security Settings
Combining the Three Levels
Include Files
Security Settings and Security Matrices
Security settings allow you to define a set of user options for each logon ID. Security
settings are defined in security files that can contain up to 960 lines. Each line contains a security matrix that allows you to define options for how a particular program
works. There are two parts to each security matrix: a program name and a list of
parameters.
♦ Program Name. Each user option has a program name that is usually 6 or 8 characters long. For example, PP02TC is the program name for the security matrix that
controls the options for the TC Screen of Employee Maintenance (PP0002). Similarly, PP0010X0 is the program name for the security matrix that allows you to
block a user’s access to specified master files when using Update Per/Pay Master
Files (PP0010).
♦ Parameters. Each security matrix has up to 60 characters of parameters. For
example, the parameters for the program name PP02TC control a variety of
options for updating retirement base pay and adding accounts while a payroll clerk
is doing time card entry. But the parameters for the program name PP0010X0 are a
list of 2-character codes for master files that a user is blocked from maintaining
with Update Per/Pay Master Files (PP0010).
A security settings file can contain security matrices for many different programs.
Security matrices are used in many parts of the QSS/OASIS Financial System, such
as Payroll, Stores, Budgeting, General Leader, Budget Development, and Accounts
Payable. The security settings for all modules of the Financial System are contained
in the same security file.
Global, District, and User Security Settings
Maintain User Data (MEN020) allows you to define three levels of security matrices:
global, district, and user.
♦ Global: There is one global security file which contains the default security matrices for all users.
07/2000
Copyright © QSS, 2000
3
User Maintenance and Security
How to Use Maintain User Data (MEN020)
♦ District: There is one district security file for each district. This file contains the
default security matrices for a district. These defaults apply to all users who log
into the district. If the security matrix for a program is in both the district and global files, the district-level security matrix prevails.
♦ User: Each logon ID can have a user-level security file that has the same name as
the user ID. If you create a user-level security file, any security matrices in that file
take precedence over those in the global and district files.
You can use the user file to create exceptions for individual users. For example, the
district defaults contains security matrices for fifty different programs. A supervisory employee needs exceptions to the access permissions in four of those programs. You can create a user-level security file for that supervisor with entries for
just those four programs. The district-level defaults continue to apply for the other
46 programs.
All three levels of security settings are optional. Each program has a set of default
options that apply if there is no security matrix. If you are satisfied with the defaults
for a program, there is no need to define its security matrix.
You can copy security profiles. The X (copy user) option allows you to copy settings
from one user to another. Thus, for example, you can set up the user profile and security settings for one accounting clerk, then copy those settings to other user IDs that
have identical or very similar user profiles. After completing the copy, you can make
any needed adjustments.
Combining the Three Levels
The security settings for each logon ID are a combination of all three levels. When a
user logs into the QSS/OASIS software, the Menu System reads the global, district,
and user security settings, then combines all three into a temporary file that contains
composite security settings. This composite file lasts only as long as each session. It is
created every time a user logs on, and it is purged when the user logs off.
The following rules describe what happens when the three levels of security settings
are combined:
♦ User takes precedence over district and global.
If a user-level security file contains a security matrix, that security matrix governs
for the user. For example, the logon ID FRANCIS.QSSUSER has a user-level
security file that includes a security matrix for PP02TC. These user-level settings
apply to Francis when he enters time card data on the TC Screen. This user-level
security overrides any global or district-level security matrix for PP02TC.
4
Copyright © QSS, 2000
07/2000
Overview of Security Settings
Include Files
♦ District takes precedence over global.
If the same security matrix is in both the district and global security file, the district
security matrix prevails. For example, the logon ID GEORGE.QSSUSER in District 71 does not have a user-level setting for the PP02TC security matrix. However, that security matrix is part of both the global security file and the file for
District 71. In this case, the security matrix PP02TC in the district security controls
George’s options.
♦ Global applies only when district and user are not defined.
The global security settings define the defaults for all users. But these defaults
apply only when they are not overridden with user or district security. For example, the logon ID MARY.QSSUSER is associated with District 58. There is no
security matrix for PP02TC in Mary’s user-level security settings, nor is there any
such matrix in the global settings for District 58. But there is a PP02TC security
matrix in the global security file. In this case, the global security file’s options for
PP02TC apply to Mary.
♦ If you do not define any security matrices, the defaults prevail.
If you do not define a security matrix, the default settings for a program prevail.
For example, the logon BOB.QSSUSER belongs to a county where the PP02TC
security matrix is not defined for at any level: global, district, or user. Thus, the TC
screen functions according to its default capabilities, which means that Bob cannot
update retirement base pay or add accounts while entering time card data.
Include Files
An include file is a security file that you can incorporate by reference. You can define
a set of security settings, then save it in a file. You can incorporate a saved file in any
global, district, or user security file with a $INCLUDE line.
For example, there are about a dozen standard security matrices for payroll clerks.
You can put those security matrices in a separate security file, then save it with a
name like PAYCLERK. To apply those settings to a particular user, all you need do is
type $INCLUDE as the program name, the file name PAYCLERK as the parameter.
This $INCLUDE line causes all of the security matrices in the PAYCLERK file to be
applied to the user.
Include files can simplify change management. Any changes that you make in an
include file are reflected everywhere the include file is used. For example, you need
to change one security matrix and add a new one to the PAYCLERK file. These
changes apply to every user whose security settings have a $INCLUDE line with the
PAYCLERK file.
07/2000
Copyright © QSS, 2000
5
User Maintenance and Security
How to Use Maintain User Data (MEN020)
However, you cannot make a $INCLUDE command part of an include file. A global,
district, or user security file can call an include file. But an include file cannot call
another include file.
Changes to an include file have no effect on users who are already logged on at the
time you make the changes. However, the new or changed security matrices apply to
everyone who logs on after you save the changes to the include files.
6
Copyright © QSS, 2000
07/2000
Option Screen
Option Screen
Figure 1 illustrates the Option Screen for Maintain User Data (MEN020). The list of
options displays after you type H in the Option field and press <ENTER>. This
screen allows you to select an option for maintaining the security profile associated
with a logon ID.
Figure 1: Option Screen for Maintain User Data (MEN020)
Option (R)
Type a code from the following list.
OPTION
SEE PAGE
A - Add a user
9
C - Change a user
9
D - Delete a user
19
I - Inspect a user
9
G - Change global security file
20
S - Security file maintenance
23
X - Copy a user file
28
E - Exit program
n/a
NOTE: The X option allows you to create new user profiles
based on an existing one.
<ENTER>
07/2000
Press <ENTER> to execute the Option.
Copyright © QSS, 2000
7
User Maintenance and Security
8
How to Use Maintain User Data (MEN020)
<Start Over>
Press <Start Over> to type the Option again.
<Return to Menu>
Press <Return to Menu> to stop maintaining users and return
to the Menu System.
Copyright © QSS, 2000
07/2000
Add, Change, or Inspect a User
Select a User
Add, Change, or Inspect a User
These instructions tell how to use the add, change, and inspect options of Maintain
User Data (MEN020). These instructions are combined because the options are so
similar.
These instructions focus on three areas:
♦ Select a User
♦ Maintain User Profile
♦ Maintain Security Settings
Select a User
Figure 2 illustrates the first screen for adding, changing, or inspecting a user’s security profile and security settings. This screen allows you to create a new user profile
or to modify or inspect an existing one.
Figure 2: Select a user to add, change, or inspect
User.acct (R)
Type the MPE logon ID for which you want to create or
maintain a Menu System security profile or security matrix.
♦ To add, type a logon ID for which you have not yet
defined a Menu System profile.
♦ To change or inspect, type a logon ID for which there is
an existing Menu System profile.
There are two parts to each logon ID: user and account.
07/2000
Copyright © QSS, 2000
9
User Maintenance and Security
How to Use Maintain User Data (MEN020)
♦ User. The first part is an 8-character user name.
For the add option, type a user name for which you
have not defined a user profile.
For the change or inspect option, type a user name
for which a user profile already exists.
♦ Account. This field is filled in with QSSUSER, which
is the typical account for logging into the QSS/OASIS
Financial System. You can type another account name
if needed.
10
<ENTER>
Press <ENTER> to continue filling in the screen.
<Start Over>
Press <Start Over> to retype the User.acct.
<Return to Menu>
Press <Return to Menu> to return to the Menu System.
Copyright © QSS, 2000
07/2000
Add, Change, or Inspect a User
Maintain User Profile
Maintain User Profile
Figure 3 illustrates the screen for adding, changing, or inspecting a user profile. This
profile defines important information, such as the audit ID, fiscal year, site, and district number for each authorized Menu System user.
NOTE: For the inspect option, this entire screen is display-only.
Figure 3: Add, change, or inspect a user profile
User.acct (D)
The user and account selected on the previous screen.
User password (O)
Type the password to be inserted in the job streams that this
user ID launches.
This password must match the user password that the user
types in when logging on to the HP e3000. If this password is wrong, this user’s report and batch update jobs
will not be able to log on.
NOTE: This password may not be needed if you are using
job management software that allows you to launch jobs
without embedding passwords in the stream files or if the job
security level on your HP e3000 has been adjusted so that
these passwords are not required. For example, some sites
use VESOFT’s products to eliminate the need to embed
passwords in job streams.
07/2000
Copyright © QSS, 2000
11
User Maintenance and Security
System (R)
How to Use Maintain User Data (MEN020)
Type a system name in this field.
This field is no longer used by the standard QSS software.
You can simply type SYSTEM here. If you prefer something more descriptive of the type of software being used,
you can type something like STUDENT or FINANCE. You
must type something in this field to update the screen.
User id/name (O)
This free-form field allows you to type up to 30 characters.
You can use this field for noting the name or job title of the
person assigned to the logon ID or other such information.
User audit id (R)
Type a 4-character code for keeping track of who changed
records in the database.
Some programs keep track of when information was
changed. They record the User audit id for the user who
changed the information, along with the time and date. If
you want to keep an accurate audit trail, each logon ID
should have a unique User audit id.
First screen (O)
Type the name of the first Menu System screen that displays
when this user logs on.
NOTE: If you leave this field blank, the user has access to
the MPE operating system prompt, which is essentially the
same thing as making this logon ID a super user. Access to
the MPE prompt should be reserved only for members of the
data processing staff.
Allow access (R)
Type Y or N for yes.
♦ Type Y to allow the user to sign onto Menu System and
gain access to the QSS/OASIS programs.
♦ Type N to block the user from using the Menu System
to run QSS/OASIS programs. When the user logs on to
the HP e3000, the session will be logged off, and the
screen displays the following message: Access is
not allowed at the present time.
12
Copyright © QSS, 2000
07/2000
Add, Change, or Inspect a User
Level (O)
Maintain User Profile
Leave blank, or type SU for a super user.
♦ Leave blank for almost all users. Standard users can
select QSS/OASIS and STUDENT/3000 programs
from the Menu System. The Menu System runs automatically when they log on to the HP e3000, and they
are logged off when they exit the Menu System.
♦ Type SU to make this user a super user. Very few people
should be super users. Super users have special capabilities. They can issue commands that are not available
to standard users.They can also gain direct access to the
MPE command prompt. Normally, the only people with
this capability are system administrators and support
specialists.
Local printer (R)
Type a number from the following list.
This number sets the value for the job control word (JCW)
called PRINTX, which controls the printer for reports that
the user ID launches.
PRINTX
0
MEANING
The file equation in the stream file specifies the
device. The line in the stream file looks like this:
FILE PRINTER;DEV=[printer device]
If the stream file does not contain a file equation
for the printer device, the report may not print, or
else it may print at an unexpected place.
07/2000
1
Reports print on the system line printer (device
LP).
3
Reports are routed through LSPOOL. You can
view the reports on your screen, then select the
printer to which to route the reports. This is the
most common setting. It is recommended for
most logon IDs.
70 - 89
Reports are printed on a remote spooled device
called RPxx, where ‘xx’ is the PRINTX value.
For example, setting the PRINTX to 76 sends
reports to device RP76.
90 - 99
Reports are printed on a remote spooled device
with the class name RLPx, where ‘x’ is the ones
digit of the PRINTX. For example, setting the
PRINTX to 93 sends reports to device RLP3.
Copyright © QSS, 2000
13
User Maintenance and Security
District (R)
How to Use Maintain User Data (MEN020)
Type the district number associated with the logon ID.
Almost all records in the financial and student databases
are keyed by district. The District that you type in this
field tells the software what district to look in when this
user requests financial or student data.
Site (R)
Type the 4-digit site number associated with the logon ID or
0000 when none is necessary.
This field is particularly important for logon IDs that will
be accessing STUDENT/3000, remote purchase requisitions, or the stores warehouse/inventory software. Please
refer to the documentation for each of these systems for
the appropriate use of this field.
Fiscal year (R)
Type the last 2 digits of the fiscal year, such as 01 for fiscal
year 2000-2001.
Almost all records are keyed by year. The Fiscal year that
you type in this field tells the software the proper fiscal
year for financial records or the school year for student
data.
NOTE: At the start of each fiscal or school year, update the
Fiscal year field so that users are able to maintain data for
the current year.
User jcw values (R)
Fields 1. through 10. allow you to define USERJCW1
through USERJCW0.
These JCWs are used for setting up options for some programs. For example, they can be used to control access to
screens in Employee Maintenance (PP0002).
<ENTER>
Press <ENTER> to verify the information on the screen.
If the screen is unable to process a field, that field is highlighted, and the Message Line explains why the field is
highlighted. Make any needed changes, then press
<ENTER> again.
<Start Over>
14
Press <Start Over> to return to the Option Screen without
updating the screen.
Copyright © QSS, 2000
07/2000
Add, Change, or Inspect a User
Maintain Security Settings
<Print Screen>
Press <Print Screen> to print a copy of this screen on the
printer assigned to your logon ID.
<Start Over>
Press <Start Over> to return to the Option Screen without
updating the screen.
<Security Settings>
Press <Security Settings> to maintain the user-level security
settings for the current user.
Any security matrices that you define on this screen override district and global security matrices. See
<Update Data>
Press <Update Data> to save the changes to the user profile.
After the update completes, the Option Screen displays
again.
<Return to Menu>
Press <Return to Menu> to cancel any additions or changes
and return to the Menu System.
Maintain Security Settings
Figure 4 illustrates the screen for maintaining the security settings for a user. This
screen displays after you press the <Security Settings> key. The security matrices on
this screen override the global and district default security files. See page 3 for an
explanation of how the global, district, and user security settings are related.
This screen allows you to add, change, or delete individual lines in the security settings file.
To add a security matrix:
♦ Locate a screen where there is an empty line. You may need to press <Page Forward> several times.
♦ Type the Program and its parameters.
♦ Press <ENTER> to process the changes on the screen. After you are through with
all changes to the security settings file, press <Update Data> to update the security
settings file.
To change a security matrix:
♦ Locate the line you want to change. You may need to press <Page Forward> or
<Page Backward> to find the line.
♦ Make any changes to the line.
♦ Press <ENTER> to process the changes on the screen. After you are through with
all changes to the security settings file, press <Update Data> to update the security
settings file.
07/2000
Copyright © QSS, 2000
15
User Maintenance and Security
How to Use Maintain User Data (MEN020)
To delete a security matrix:
♦ Locate the line you want to change. You may need to press <Page Forward> or
<Page Backward> to find the line.
♦ Use the space bar or <Delete> key to erase the Program name.
♦ Press <ENTER> to process the changes on the screen. After you are through with
all changes to the security settings file, press <Update Data> to update the security
settings file.
After you update the security settings, the changes take effect the next time a user
who is subject to these security settings logs in. The changes have no effect on users
who are already logged in at the time you maintain the security file.
NOTE: For the inspect option, this entire screen is display-only.
Figure 4: Maintain security settings for a user
Program (O)
[parameters] (O)
To implement a security matrix, type the Program name and
parameters.
DEFINING SECURITY MATRICES. Each security
matrix has two parts: a program name and a parameter list.
♦ Program. Type a Program name, which is usually 6 or
8 characters long.
♦ Parameters. Type up to 60 characters of parameters.
See the technical notes for the Program name for
instructions on filling in the parameters. Each security
matrix has its own list of parameters.
16
Copyright © QSS, 2000
07/2000
Add, Change, or Inspect a User
Maintain Security Settings
INCLUDE FILES. You use an include file to incorporate
the contents of another file into any global, district, or
user-level security matrix. See page 23 for instruction on
creating an include file.
To incorporate an include file:
♦ Type the word $INCLUDE or $INC in the Program
field.
♦ Type the name of the include file in the first 8 characters of the [parameters].
COMMENT LINES: Any line where the Program name
is $COMMENT or $COM is treated as a comment line. You
can use the [parameters] columns to write notes or explanations to make the security file easier to read or maintain.
The Menu System ignores comment lines when building
the combined security matrix for a user.
NOTE: The screen does not prevent you from typing the
same security matrix twice. If there are duplicate security
matrices for the same Program name, the second matrix
prevails. For example, a security settings file includes a
security matrix for TCPYMT in lines 12 and 48. The parameters for line 48 take precedence.
<ENTER>
Press <ENTER> to process the changes on the screen.
To include the changes on the current screen in the
updated file, press <ENTER> before pressing either <Page
Backward> or <Page Forward>.
<Start Over>
Press <Start Over> to return to the Option Screen without
updating the user-level security matrix.
<Print Screen>
Press <Print Screen> to print a copy of the screen on the
printer assigned to your logon ID.
<User Data>
Press <User Data> to return to maintaining the user profile as
described on page 11.
<Load Global>
Press <Load Global> to copy the global security file into the
user’s security file.
The load process overwrites any existing security matrices
that you have defined for the user.
07/2000
Copyright © QSS, 2000
17
User Maintenance and Security
<Page Backward>
<Page Forward>
How to Use Maintain User Data (MEN020)
Press <Page Forward> and <Page Backward> to see the next
or previous 16 lines of the security file.
Each security file has up to 960 lines, or 60 screen pages.
<Update Data>
Press <Update Data> to save the changes to the user’s security settings.
After the update completes, the program displays the
Option Screen. See page 7 for instructions.
<Return to Menu>
18
Press <Return to Menu> to cancel the changes to the security
file and return to the Menu System.
Copyright © QSS, 2000
07/2000
Delete a User
Maintain Security Settings
Delete a User
Figure 5 illustrates the screen for deleting a logon ID from the Menu System. This
action removes a logon ID from the list of authorized users of the QSS/OASIS Menu
System. However, this screen does not delete the MPE logon ID. To delete a logon ID
from the HP e3000’s list of authorized users, use the MPE command PURGEUSER.
Figure 5: Delete a Menu System User
Option (D)
The delete option chosen on the previous screen.
User.acct (R)
Type the user ID to delete from the Menu System user list.
<ENTER>
Press <ENTER> to delete the user.
After the deletion, the screen clears and prompts for
another option.
NOTE: When you press the <ENTER> key, the user ID is
deleted from the Menu System database. Be certain that you
have typed the user ID that you want to delete, as the screen
does not ask for any confirmation, nor is there any undelete
or undo key.
07/2000
<Start Over>
Before pressing <ENTER>, press <Start Over> to cancel the
deletion and return to the Option Screen.
<Return to Menu>
Before pressing <ENTER>, press <Return to Menu> to cancel the deletion and return to the Menu System.
Copyright © QSS, 2000
19
User Maintenance and Security
How to Use Maintain User Data (MEN020)
Change Global Security File
Figure 6 illustrates the screen that allows you to change the global security file. This
screen allows you to define the default security matrices for the all users in all districts. It contains the defaults for all modules of the QSS/OASIS Financial System.
You can override these global defaults with the district default or user-level security
settings.
This screen allows you to add, change, or delete individual lines in the security settings file.
To add a security matrix:
♦ Locate a screen where there is an empty line. You may need to press <Page Forward> several times.
♦ Type the Program and its parameters.
♦ Press <ENTER> to process the changes on the screen. After you are through with
all changes to the security settings file, press <Update Data> to update the security
settings file.
To change a security matrix:
♦ Locate the line you want to change. You may need to press <Page Forward> or
<Page Backward> to find the line.
♦ Make any changes to the line.
♦ Press <ENTER> to process the changes on the screen. After you are through with
all changes to the security settings file, press <Update Data> to update the security
settings file.
To delete a security matrix:
♦ Locate the line you want to change. You may need to press <Page Forward> or
<Page Backward> to find the line.
♦ Use the space bar or <Delete> key to erase the Program name.
♦ Press <ENTER> to process the changes on the screen. After you are through with
all changes to the security settings file, press <Update Data> to update the security
settings file.
After you update the security settings, the changes take effect the next time a user
who is subject to these security settings logs in. The changes have no effect on users
who are already logged in at the time you maintain the security file.
20
Copyright © QSS, 2000
07/2000
Change Global Security File
Maintain Security Settings
Figure 6: Change global security file
Program (O)
[parameters] (O)
To implement a security matrix, type the Program name and
up to 60 characters of parameters.
DEFINING SECURITY MATRICES. Each security
matrix has two parts: a program name and a parameter list.
♦ Program. Type a Program name, which is usually 6 or
8 characters long.
♦ Parameters. Type up to 60 characters of parameters.
See the technical notes for the Program name for
instructions on filling in the parameters. Each security
matrix has its own list of parameters.
INCLUDE FILES. You can use include files to incorporate the contents of another file into any global, district, or
user-level security matrix. See page 23 for instruction on
creating an include file.
To incorporate an include file:
♦ Type the word $INCLUDE or $INC in the Program
field.
♦ Type the name of the include file in the first 8 characters of the [parameters].
07/2000
Copyright © QSS, 2000
21
User Maintenance and Security
How to Use Maintain User Data (MEN020)
COMMENT LINES: Any line where the Program name
is $COMMENT or $COM is treated as a comment line. You
can use the [parameters] columns to write notes or explanations to make the security file easier to read or maintain.
The Menu System ignores comment lines when building
the combined security matrix for a user.
NOTE: The screen does not prevent you from typing the
same security matrix twice. If there are duplicate security
matrices for the same Program name, the second matrix
prevails. For example, a security settings file includes a
security matrix for TCPYMT in lines 12 and 48. The parameters for line 48 take precedence.
<ENTER>
Press <ENTER> to process the changes on the screen.
To include the changes on the current screen in the
updated file, press <ENTER> before pressing either <Page
Backward> or <Page Forward>.
<Start Over>
Press <Start Over> to return to the Option Screen without
updating the user-level security matrix.
<Print Screen>
Press <Print Screen> to print a copy of the screen on the
printer assigned to your logon ID.
<Page Backward>
<Page Forward>
Press <Page Forward> and <Page Backward> to see the next
or previous 16 lines of the security file.
Each security file has up to 960 lines, or 60 screen pages.
<Update Data>
Press <Update Data> to save the changes to the user’s security settings.
After the update completes, the program displays the
Option Screen. See page 7 for instructions.
<Return to Menu>
22
Press <Return to Menu> to cancel the changes to the security
file and return to the Menu System.
Copyright © QSS, 2000
07/2000
Security File Maintenance
Select File to Maintain
Security File Maintenance
The Security File Maintenance screen allows you to maintain any of the four different
types of security files: global, district, user, and include. There are two steps in maintaining this file:
♦ Select File to Maintain
♦ Maintain the File
Select File to Maintain
Figure 7 illustrates the screen that displays after you select the S option. This screen
allows you to select which security file to maintain.
Figure 7: Security File Maintenance (1 of 2)
<Start Over>
Press <Start Over> to return to the Option Screen without
maintaining a file.
<Global>
Press <Global> to maintain the global security file.
This file defines the default security settings for all districts. You can override these settings with a district or
user security file.
See page 25 for instructions.
07/2000
Copyright © QSS, 2000
23
User Maintenance and Security
<District>
How to Use Maintain User Data (MEN020)
Press <District> to maintain the district default file.
This security file defines the default security settings for
all users in a district.
To continue filling in the screen:
♦ Type the District number for which you want to maintain the default security settings.
♦ Press <ENTER> to fill in the screen as described on
page 25.
<User>
Press <User> to maintain security settings for a user. The
security matrices in this file override any district and global
default security settings.
To continue filling in the screen:
♦ Type the 8-character user name to select the logon ID
for which to maintain user-level security settings.
♦ Press <ENTER> to fill in the screen as described on
page 25.
<Include>
Press <Include> to maintain an include file. This file contains
a group of settings that you can include in any global, district,
or user security settings. See page 5 for a discussion of
include files.
To continue filling in the screen:
♦ Type an Include file name up to 8 characters long.
♦ Press <ENTER> to fill in the screen as described on
page 25.
<Return to Menu>
24
Press <Return to Menu> to return to the Menu System.
Copyright © QSS, 2000
07/2000
Security File Maintenance
Maintain the File
Maintain the File
Figure 8 illustrates the screen that allows you to define the selected security file. This
option allows you to maintain all levels of security files: global, district, user, and
include files.
Figure 8: Security File Maintenance (2 of 2)
Program Security
Matrix (D)
The top of the screen identifies kind of security matrix
selected on the previous screen, such as ( User:
Frances ) for the user-level security matrix for
FRANCES.QSSUSER.
In other cases, the top of the screen may identify the district number for district-level security, the name of a
$INCLUDE file, or the global security file.
Program (O)
[parameters] (O)
To implement a security matrix, type the Program name and
up to 60 characters of parameters.
DEFINING SECURITY MATRICES. Each security
matrix has two parts: a program name and a parameter list.
♦ Program. Type a Program name, which is usually 6 or
8 characters long.
♦ Parameters. Type up to 60 characters of parameters.
See the technical notes for the Program name for
instructions on filling in the parameters. Each security
matrix has its own list of parameters.
07/2000
Copyright © QSS, 2000
25
User Maintenance and Security
How to Use Maintain User Data (MEN020)
INCLUDE FILES. You can use include files to incorporate the contents of another file into any global, district, or
user-level security matrix.
To incorporate an include file:
♦ Type the word $INCLUDE or $INC in the Program
field.
♦ Type the name of the include file in the first 8 characters of the [parameters].
COMMENT LINES: Any line where the Program name
is $COMMENT or $COM is treated as a comment line. You
can use the [parameters] columns to write notes or explanations to make the security file easier to read or maintain.
The Menu System ignores comment lines when building
the combined security matrix for a user.
NOTE: The screen does not prevent you from typing the
same security matrix twice. If there are duplicate security
matrices for the same Program name, the second matrix
prevails. For example, a security settings file includes a
security matrix for TCPYMT in lines 12 and 48. The parameters for line 48 take precedence.
<ENTER>
Press <ENTER> to process the changes on the screen.
To include the changes on the current screen in the
updated file, press <ENTER> before pressing either <Page
Backward> or <Page Forward>.
<Start Over>
Press <Start Over> to return to the Option Screen without
updating the user-level security matrix.
<Print Screen>
Press <Print Screen> to print a copy of the screen on the
printer assigned to your logon ID.
<Page Backward>
<Page Forward>
Press <Page Forward> and <Page Backward> to see the next
or previous 16 lines of the security file.
Each security file has up to 960 lines, or 60 screen pages.
26
Copyright © QSS, 2000
07/2000
<Update Data>
Press <Update Data> to save the changes to the user’s security settings.
After the update completes, the program displays the
Option Screen. See page 7 for instructions.
<Return to Menu>
07/2000
Press <Return to Menu> to cancel the changes to the security
file and return to the Menu System.
Copyright © QSS, 2000
27
User Maintenance and Security
How to Use Maintain User Data (MEN020)
Copy a User File
Figure 9 illustrates the screen that displays after you select the X option. This screen
allows you to copy user profiles and security matrices. You can use this screen to create new user profiles based on an existing user.
Figure 9: Copy a User File
Option (R)
The copy option selected from the previous screen.
Copy from User.acct Type the name of the user ID to copy from.
(R)
To make copying a series of users easier, the name that
you type here remains the next time you use the option.
Copy to User.acct (R) Type the name of the user ID to copy to or create.
User definition (R)
Leave the Y as is, or type N for yes.
♦ Leave the Y as is to copy the user profile for the logon
ID. See Figure 3 on page 11 for an illustration of the
information that is copied.
If you answer Y, the copy process creates the user ID in
the Copy to User.acct field if it does not already exist.
♦ Type N to skip copying the user definition.
28
Copyright © QSS, 2000
07/2000
Copy a User File
If you answer N, the user ID to which you are copying
must already exist. The copy process will not create it
for you.
Security settings (R) Leave the Y as is, or type N for yes.
♦ Leave the Y as is to copy the user security settings to
the target user ID.
♦ Type N to skip copying the user-level security settings.
<ENTER>
Press <ENTER> to copy the user ID.
After the copy completes, the screen clears and prompts
for another option. See page 7 for instructions.
07/2000
<Start Over>
Press <Start Over> to return to the Option Screen without
copying any users. See page 7 for instructions.
<Return to Menu>
Press <Return to Menu> to return to the Menu System.
Copyright © QSS, 2000
29
User Maintenance and Security
How to Use Maintain User Data (MEN020)
Index
A
L
allowing access to programs 12
annual maintenance of fiscal year 14
audit ID 12
comment lines 17, 22, 26
levels of security settings
combining 4–5
overview of 3–4
levels of users 13
local printer 13
location 14
logon district 14
logon site (location) 14
logon year 14
LSPOOL, routing reports through 13
D
M
default security 4, 5
disabling access to programs 12
district security
defining 23–27
precedence over global 5
district, logon 14
Maintain User Data (MEN020)
add user option 9–18
change global security file option 20–22
change user option 9–18
copy user option 28–29
delete user option 19
inspect user option 9–18
option screen 7–8
security file maintenance option 23–27
MEN020. See Maintain User Data (MEN020)
MPE logon ID 1, 9–10
B
batch update jobs, password for 11
C
E
Employee Maintenance (PP0002) 14
F
N
first Menu System screen 12
fiscal year 14
name (description) of user ID 12
G
P
global security
application to district and user security 5
defining 20–22, 23–27
parameters
defined 3
district security 25
global security 21, 25
include file 25
user security 16, 25
PRINTX value 13
program name
defined 3
district security 25
global security 21, 25
include files 25
user security 16, 25
I
include files
defining 23–27
district security 17
global security 17, 21
overview of 5–6
user security 17
initial Menu System screen 12
30
Copyright © QSS, 200007/2000
07/1000
Index
R
U
report jobs, password for 11
user profile
allowing access to programs 12
audit ID 12
deleting 19
disabling access to programs 12
district 14
first screen 12
fiscal year 14
levels of users
standard 13
super user 13
local printer (PRINTX value) 13
MPE logon ID 9–10
name (description) 12
password 11
routing reports through LSPOOL 13
site (location) 14
system 12
user and account 9–10
USERJCW1 through USERJCW0 14
user security
defining 15–18, 23–27
precedence over district and global 4
USERJCW1 through USERJCW0 14
S
security matrices
defining 15–18, 20–22, 23–27
and security settings 3
security settings
combining levels of 4–5
default 4
deleting 19
levels of 3–4
and security matrices 3
user security 15–18
site 14
standard users 13
super users 13
system 12
07/2000
Copyright © QSS, 2000
31