Natural Secured Menus Maintenance System
Functional Specifications

Computing Services
University of Arkansas

Melinda Mays Bowman
Kathryn Cantrell
W. David Wimberly

Revision 6, January 2001


Table of Contents

Introduction

Online Menus and Functions

Miscellaneous


Figures

  1. Main Menu
  2. List All Available Commands
  3. Menu Hierarchy of Available Commands
  4. CDCD Desk Selection window
  5. CDCD Desk Information window
  6. LOGon to another Natural application
  7. FINish, logoff Natural
  8. Desk Administrator's Menu
  9. Desk maintenance
  10. Desk Assignment maintenance
  11. List Desks for a Budgetary unit
  12. List Users for a Desk
  13. List Applications for a Desk
  14. List Historical Desk Assignments
  15. List Positions for a Budgetary Unit and Date
  16. List User IDs for a User
  17. Initialization and Setup Menu
  18. User maintenance, screen 1
  19. User maintenance, screen 2
  20. Application maintenance, screen 1
  21. Application maintenance, screen 2
  22. Menu maintenance
  23. List Applications of an Analyst
  24. List Value security group for Desk administrator's BU
  25. Application Administrator Menu
  26. Command Security group maintenance
  27. Value Security group maintenance
  28. Application Desk maintenance
  29. Application Default Access maintenance
  30. Application Notice maintenance
  31. Application Lock/unlock and Reason
  32. Command Security group Lock/unlock and Reason
  33. List Users of an Application
  34. List Desks for a Command security group
  35. List Desks for a Value security group
  36. List Desks for an Application
  37. List Applications of an Owner
  38. Command Sequence maintenance

Introduction


Document Information

The Functional Specifications for the Natural Secured Menus Maintenance System (NSM-MS) document the functions and features of this system. The NSM-MS system is used to maintain the Adabas files necessary for applications that are developed using the Natural Secured Menus Architecture (NSM-A).


System and Revision Identification

Draft versions of this document were released April 21, 1988 and June 21, 1988. The first version of this document was released July 5, 1988. Revision 1 was made to reflect changes and corrections as a result of the actual development of the system and was released March 15, 1989. Revision 2 incorporated changes to sections shared by the NSM Architecture documentation and added the screen definitions section, released November 27, 1989. Revision 3 added list functions, documentation for the job management facilities and converted the document to IBM's DCF format. It was released October 30, 1990. Changes to the Menu maintenance function were made in May 1991 to allow function modules to reside on the system library and be named UAOxxxx. Revision 4 was released in November of 1992 to incorporate the conversion of the system to version 2 of the NSM Architecture, maintenance of additional application and user elements, and the addition of a new list function (List Applications of an Analyst - LAA). Additionally, Revision 4 removed text concerning job management facilities since they had become a separate NSM application. Revision 5, released in January of 1994, incorporated changes made to the system when desk-based security was implemented in September, 1993. Revision 6 occurred in January 2001 when the document was converted to HTML and the system was updated to support the change to position based desk assignments.

Purpose of this Document

The Functional Specifications are prepared in order to provide a clear and concise definition of the system. This document is prepared initially to ensure that the system meets the intended needs and requirements of those requesting its development. On an ongoing basis, the specifications serve as the primary reference regarding the functions and use of the system. Errors or omissions should be brought forward as they are identified so that corrections can be made.


Concepts


Desk Definition

A desk, identified by a Desk ID, represents an individual's job, specifically those tasks related to the use of computerized administrative systems. Desks are associated with and defined within budgetary units. The department heads, or individuals they choose to designate (refered to as "Departmental Desk Adminstrators"), are responsible for the creation and definition of the specific desks within their department. The definition of a desk includes an optional description of the functions or responsibilities of the desk, as defined and to the extent desired by the department. The departmental desk administrators then associate employees within their budgetary units to the desks they created.

The desk concept permits several individuals to be associated with the same desk when they perform the same job (e.g., registration data entry operators). However, the norm is one desk is associated with one individual since most jobs are unique. In addition, one employee is typically associated with only one desk. That desk is the employee's primary desk. An interim desk may be assigned in exceptional cases when an individual is asked to perform two jobs on a temporary basis. A user who is assigned to two desks is required to explicitly identify which desk he will be working at any one time. It is recommended that this dual desk feature only be used in situations where there are true interim assignments.

The association of an employee with a desk is based upon the type of employee and the type of user ID. For appointed employees with one primary user ID this is accomplished by assigning the desk to the PSB position the individual is filling or hired into. Some appointed employees have secondary or temporary user IDs for the purpose of loaning those IDs out to temporary employees on a short term basis. Desks for these IDs are assigned directly to the User IDs. Similarly, desks for hourly employees and non-University employees that require access are also assigned directly to their User IDs.


Desk Function

Application access privileges and required electronic transaction review and approval are determined by the employee's desk assignment. A discussion of these two separate uses of desks follow:

Application Access

Desk-based security allows the access rights to all necessary applications to remain the same, regardless of who is filling a position (assigned a desk). The department head requests access to an application for a desk. The application owner establishes and maintains the access rights for a desk to an application. The department head can assign as many employees as desired to work that desk. When a user signs in with his individualized ID, the system automatically makes the association of that user/employee with the established desk assignment. The access rights and privileges of that user are those established for that desk.

Transaction Approval

For the purpose of routing electronic transactions for approval, a desk may be established as a review point for those transactions. The necessary routing definitions for electronic transactions are determined by the University administration, and are rather complex and voluminous in nature. The use of a desk ID to define a review point for a transaction permits the reassignment of personnel to be accommodated without requiring the redefinition of the routing information.


User ID and its Status

A user of online Natural applications must be issued a CICS ID. This User ID is assigned to the individual employee and should not be shared or assigned to someone else. When your department hires a new University employee who requires access to Natural applications, a CICS ID must be requested from Computing Services. This ID provides an audit trail of the activity performed, such as who updated a record, who initiated a transaction, and who reviewed a transaction.

A User ID can have one of three possible codes for its status: active, inactive, or temporary. Active status indicates the user is an active employee on the University's payroll system. (There is an exception for certain individuals who are not employees but have been granted access to University administrative systems.) Inactive status is set for a user who is no longer active on payroll and is therefore no longer authorized to access computer applications. Of course, desks cannot be assigned to inactive users. Temporary IDs are special types of IDs that are designed to fill the need of temporary workers. Temporary IDs are assigned to be the responsiblity of a supervisor in the department. That supervisor then distributes the ID and its password to the temporary worker. When the temporary worker leaves, the supervisor changes the password so that security is maintained. The supervisor is responsible for the actions performed by users of temporary IDs.

Active and temporary User IDs are associated with a budgetary unit based upon their type of employment, either appointed or hourly. Appointed employees are hired into a position which has been allocated to a budgetary unit. Hourly employees must have an active wage rate established for the budgetary unit in which they work. This budgetary unit association plays a significant role in the desk assignment process.


Desk Assignments

A desk is created for and designated as belonging to a specific budgetary unit. It may then be assigned to either a PSB (Personal Services/Budget) position (for appointed employees) or to a user ID (for hourly employees, temporary User IDs, or non-employees) which is associated with the same budgetary unit. These desk assignments are time stamped -- each has a designated beginning point in time and ending point in time (12/31/2099 designates an undefined ending period). Future assignments can be entered or changed, while historical assignments are frozen in order to provide an historical record of all desk assignments. The user's desk for a session is then determined by the system at signon using these desk assignments. This determination is based upon the status of the User ID according to the following steps.

Active users
  1. If the user is not on the University's Employee file, the desk ID (if any) associated with the user is assigned. If there is no desk for the user, the user is only permitted default access.
  2. The system determines if an employee is filling (appointed in) a PSB position on that date.
  3. If appointed, the desk ID assigned to the position at that point in time is assigned to the user. If there is also an interim desk assignment, the user is given the choice of which desk to be assigned. If there is no desk for the position, the user is only permitted default access.
  4. If not appointed, the desk ID associated with the user is assigned as long as the employee has an active hourly wage rate in the BU of the Desk. Otherwise, no desk is assigned and the user is only permitted default access.
Temporary users
  1. If the user is not on the University's Employee file, no desk ID is assigned and only default access is permitted.
  2. The system determines if an employee is filling (appointed in) a PSB position on that date.
  3. If appointed, the BU of the appointment (position) is checked against the BU associated with the desk designated for the user. It these are the same, that desk is assigned to the user.
  4. If not appointed or the BU of the appointment does not match that of the desk, no desk is assigned and the user is only permitted default access.
Inactive users
Normally, inactive user IDs will not be permitted to signon to the administrative system since the user ID should have been inactivated within the operating system. If a user flagged as inactive does reach Natural, it will not be assigned a desk and will only be permitted default access.

This system has the primary advantage that for appointed employees, no maintenance is required when an employee leaves and the position is later filled by another individual (other than obtaining a CICS User ID if necessary). Further, access is automatically discontinued upon termination or transfer within the University, either for an appointed employee no longer assigned to a position or an hourly employee whose wage rate is inactivated.


Application Information


Background

Early in the development of Natural 1.2 applications at the University of Arkansas, we reviewed the Command-Driven, Menu-Augmented architecture (CDMA) document developed by John Wheat at the University of Texas. We first decided to implement this design in the development of the General Ledger Front end for Financial Affairs. CDMA was also used in the development of the Student Inquiry System.

With the installation of Natural 2, we sought to improve and eliminate the shortcomings of the Command-Driven, Menu-Augmented design that we implemented in Natural 1.2. The new and improved design is the Natural Secured Menus Architecture (NSM-A). During the winter of 1988, the Financial Aid Tracking System was developed. This system was the first Natural 2 application at the university and the NSM architecture was incorporated into the FINAID design.

The NSM Architecture is also 'Command-Driven and Menu-Augmented' but includes other features. The NSM Maintenance System provides NSM Architecture applications an alternative method for performing security maintenance functions other than Software AG's Natural Security. The NSM design was developed to distribute security functions to the users and to simplify security maintenance. See the NSM Architecture functional specifications for complete information.


Purpose

The purpose of the Natural Secured Menus Maintenance System is to provide maintenance facilities for the files used to establish users, applications, and the access parameters for applications which use the NSM architecture.


Data Requirements

The NSM Architecture utilizes nine logical files. These files are defined within the Predict Data Dictionary. Detail information from the data dictionary has been made available in the file and data element definition and the file and element summary. A summary description of these files follows.

File

Description

APPLICATION

Contains information related to the online applications: application ID, application name, main menu command, notices, valid actions and security levels, application owners, etc.

APPLICATION-DESK

Identifies the desks that have explicit access to the application and the type of access: security level, command security group, value security group, and job classes permitted.

APPLICATION-USER

Identifies the users that have accessed an application and the last date of access.

COMMAND-SECURITY

Identifies the command security groups that have been defined for an application and their associated command restrictions. All desks defined to access an application must be assigned to a command security group.

DESK

Contains information related to desks which are created by departments to define the roles or computer usage needs of their personnel. Information contained here includes desk ID, budgetary unit, and short and long descriptions.

DESK-ASSIGNMENT

Contains time stamped (beginning and ending effective date and time) desk assignments for positions or user IDs.

MENU-COMMAND

Contains the information for each menu within an application: the menu command and description, and the commands, descriptions and required fields for each command on the menu.

USER

Contains information related to users of the online systems: user ID, name, SSN, preferred field attributes and colors, etc.

VALUE-SECURITY

Identifies the value security groups, if any, that have been defined for an application and their associated value restrictions. The use of value security is an optional feature. If used, all desks established with access to the application must be assigned to a value security group.

Note: The file VALUE-SECURITY is maintained by the NSM-MS system. However, since security by value maintenance will be different for each application, the maintenance for this file will be defined and developed as needed for each application.

These NSM files comprise the primary data requirements for the NSM Maintenance System. Since this application itself is an NSM Architecture application, the same files maintained by the application are required for its operation.


System Overview

The NSM-MS system is developed in Natural using the Natural Secured Menus Architecture. Since the NSM Architecture is "command driven", anyone using the NSM-MS System is able to move from any function to any other function, within their security constraints, by entering the desired command. The basic screen format is the same for all functions within the system. The message line is where prompts, errors and warnings are displayed. The user can select the position of the message line as either the top or the bottom line of the screen. The title and program information, normally displayed as the second line of the screen, contains the program name, program level, function title, and the current date and time. This line will be temporarily overridden by confirmation messages following the completion of most activities. The next two lines are reserved for the display and entry of key fields, the inputs used to specify what data is to be operated on and what is to be done with it. The bottom two lines of the screen are reserved for displaying available PFkeys and their associated functions.

NSM-MS provides online maintenance to the files required to utilize the NSM architecture. This maintenance is performed by three separate groups of users based upon their normal role and function.

The application owners are established by associating up to five different desks with a specific NSM application. They typically will be positions within the department that have primary responsibility for access to the application's data. Up to five Computing Services personnel are assigned as the application as analysts. Desk Administrators are defined by the access privileges granted within NSM-MS, including value security definitions which designate the specific Budgetary Units for which they are responsible.

Application administrators (owners) will directly control access to the data viewed and maintained by their systems. Therefore, they will be primarily responsible for data security, not Computing Services.


Menu Hierarchy

The commands available within the NSM-MS System can be divided by the functional responsibilities of Computing Services, application administrators, and desk administrators. Computing Services is responsible for maintaining Users, Applications, and Menu-Commands for all applications. The application administrators for a specific application are responsible for maintaining the access of desk to their application, command and value security groups, application notices, application locks, command security group locks, and command sequence lists. Desk administrators define and maintain desks as well as assign positions and users within their budgetary unit to these desks. The menu hierarchy for NSM-MS includes a main menu and three sub menus, one for each of these three types of users.

Graphic of the NSM-MS menu hierarchy

General System Features

The following sections describe features and facilities of the NSM Maintenance System which apply to the entire application or are common to all functions.


Security

The Natural Secured Menus Maintenance System is an NSM Architecture application. The architecture provides three forms of security that have been incorporated into the NSM-MS System.
  1. Command Security

    Command security provides a means of restricting a desk or group of desks from accessing one or more commands within an application. This is accomplished by associating desks with a command security group and specifying which commands may be executed (allowed), which commands may not be executed (disallowed), or which commands will be executed with the designated security level with view only access granted to all non-listed commands (selective). Commands which are not available to a user are not displayed on the menus presented to that desk. Command security is inherent in all NSM Architecture applications.

  2. Security Levels

    The NSM-A also provides security levels which may be used to limit or restrict the functions performed within a command. The security levels allowed within the Natural Secured Menus Maintenance System follow. Security levels are enforced according to the order of the values, from most restrictive to most permissive.

    Level Restrictions Enforced
    2 Inquiry only with field restrictions
    4 Inquiry only without field restrictions
    6 Inquiry and Add only (cannot update existing records)
    7 Update (cannot delete)
    9 Delete

    Inquiry with field restrictions would allow a user to view a screen but selected fields would not be displayed. A restricted field in NSM-MS is USER-SSN.

    Each desk of an application is assigned a security level by the application administrator. That value determines the maximum privilege that will be granted to the desk. Additionally, an administrator may designate a more restrictive security level for specific commands a desk is allowed to execute. The lower, more restrictive Security Level is always used. The NSM Architecture provides each function module (command) with the current security level, and, through common code, the application program interprets and enforces the restrictions associated with that security level.

  3. Security by Value

    The NSM Architecture provides security by value in a fashion similar to that of security levels. Value restrictions, if used by an application, are read from the VALUE-SECURITY file and provided to the application program. The value restrictions to be applied must be defined for each application and are unique to that application. Desks are associated with a group code which identifies a particular set of value restrictions. The restriction or enforcement of that security is performed at the function module (command) level and is the responsibility of each application.

    NSM-MS incorporates this form of value security in the maintenance of desks -- desk management functions may only be performed when the operator has been authorized for the budgetary unit associated with the desk and position or user. The system also restricts the applications that may be operated on to those users who have been identified as owners, or in some cases analysts, of the application. Computing Services maintains data in the APPLICATION, USER, and MENU-COMMAND files. Departmental Desk administrators define and update data for the DESK file, as well as the assignments of desks to positions and users on the DESK-ASSIGNMENT file. The application administrators, or owners, update the information on the APPLICATION-DESK file, establish the Command Security Group and Value Security Group data, lock/unlock the command security groups, and maintain application default access ability and security. Application notices may be entered by either owners or analysts of the application, and both groups may also lock/unlock the application. The restriction of these functions to only owners or analysts of an application is a special form of value security that is built into the NSM-MS.


Online Help

Online help is available at the application level, the screen or function level, and the element level. Access to each of these help facilities is as follows:

In addition to these system-wide help facilities, each specific function may provide additional help. Some functions provide the use of PF4 for DeCode. The de-code function will return descriptions associated with coded values on the screen or retrieve additional associated data. This feature will be described in the command description when it is available, and the PF4 function will be labeled on the bottom of the screen.


[an error occurred while processing this directive]

List Functions

There is a special class of NSM functions designed to list information from the data base. These are inquiry only functions (no update capability) which allow browsing and selecting data online. There are several variations of these list functions, but they all share the following features and characteristics.

  1. Key fields are required to be specified to define what data is to be listed. The key fields may either define specific data to be listed (all employees in BU HIST) or, more commonly, define a starting point from which data is listed sequentially (employees in BU Hist with names starting with Williams).
  2. PF8 (Forwd) is permitted to page forward through the data sequentially and PF5 (Rstrt) will restart the list. Most lists also support PF7 (Back) to page backward.
  3. The screen will display a count of the number of entries displayed from the starting key value, and in some cases will indicate how many total entries exist. This will appear as:
    Employees 11 thru 20 of 39 displayed
    
    The starting keys used to retrieve the data are also displayed immediately below the banner.
  4. Entries from the list may be selected so that they might be operated upon further. The selection may be performed by marking (entering a non-blank character in the input field preceding each entry) or by merely placing the cursor on the line containing an entry and pressing ENTER. The effect of selecting an entry is that the key fields from the entry (those fields which are intensified) will be placed into the banner keys so that they will become the operands of other functions. For example, from the list of employees in a BU, the entry for employee 101202 could be marked. That Emp ID would be placed into the banner key and when a function is accessed that requires an Employee ID, information for that employee would be retrieved and displayed.
  5. The ability to mark entries is very powerful when combined with the suspend feature of NSM. Multiple entries may be marked, a new command entered (one that operates on the keys that will be selected from the list) and PF2 pressed. The effect is that the keys for the marked entries are selected and the new command invoked. Within that command, PF8 is labeled "Q/Nxt" so that it will quit that function and return to the list so that the next marked entry can be selected. This represents a very fast and efficient way to process, in detail, selected entries from a list. To elaborate on the above example, selected employees could be marked from the list and the user could request to suspend to a function enter leave data, enter hourly time, or view detail position information. This data could then be updated or viewed sequetially those selected employees by pressing PF8.

[an error occurred while processing this directive]
[an error occurred while processing this directive]
[an error occurred while processing this directive]

Online Menus and Functions

Complete documentation for the menus and online functions of the NSM Maintenance System is provided within this document. Menus are presented and then functions are listed in the sequence of their appearance on those menus.


MM - nsm maintenance system Main Menu

The Main Menu is always the first screen displayed when entering the application. The complete menu appears in the Main Menu Figure, or view an actual image of the NSM Main Menu screen in a separate window. This menu contains the commands to access the three NSM-MS sub menus and the utility functions listed.

Figure: Main Menu


Enter, mark or position cursor to desired command                             
 NSOMENU 1 TEST       nsm maintenance system Main Menu - MM      01/08/01 16:30
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:                                                  
-------------------------------------------------------------------------------
   CMD  Command description                      Required key fields           
   ---- ---------------------------------------- ------------------------------
 _ LAAC List All Available Commands              Command ID                    
 _ MHAC Menu Hierarchy of Available Commands                                   
 _ DAM  Desk Administrator's Menu                                              
 _ ISM  Initialization and Setup Menu                                          
 _ AAM  Application Administrator's Menu                                       
 _ CDCD Change desk/Display Current Desk info                                  
 _ LOG  LOGon to another natural application                                   
 _ FIN  FINish your session (sign off natural)                                 
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help        Quit                                                          

LAAC - List All Available Commands

The following sections document the LAAC function:

"Purpose"
"Key fields"
"Related topics"

The List All Available Commands figure is an example of the LAAC function, or view an actual image of the LAAC screen in a separate window.

Figure: List All Available Commands


Select an entry, PF8 to page forward, or enter new keys                       
 NSOLAAC 1 TEST        List All Available Commands - LAAC        01/05/01 15:12
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:          Starting Cmd: D                         
-------------------------------------------------------------------------------
 List of NSM-MS commands starting from Cmd: D                                  
                                                              On               
   Cmd   Command Description                       Type      Menu              
 _ MM    application main menu                     Menu      n/a               
 _ D     Desk                                      Function  DAM               
 _ DA    Desk Assignment                           Function  DAM               
 _ DAM   Desk Administrator's Menu                 Menu      MM                
 _ FIN   FINish your session (sign off natural)    ApIndCmd  MM                
 _ HELP  nsm-ms system level HELP                  Function  MM                
 _ ISM   Initialization and Setup Menu             Menu      MM                
 _ LAA   List Applications of an Analyst           Function  ISM               
 _ LAAC  List All Available Commands               Function  MM                
 _ LAD   List Applications for a Desk              Function  DAM               
 _ LAO   List Applications of an Owner desk        Function  AAM               
 _ LDA   List Desks for an Application             Function  AAM               
                                                                               
                 Commands     1 thru    12 are displayed                       
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt RKeys       Forwd                          

Purpose

The LAAC function is used to list all of the commands available to a user within an application. It may be useful in reviewing the available commands or in finding a command whose ID and menu is not known. A command can be selected from the list and Enter pressed to move that selection to the banner or PF2 pressed to suspend to that function (you cannot suspend to a menu).

A starting command ID may be specified in the banner, in which case the list of commands will be those equal or greater, alphabetically, to that specified. However, the main menu command for the application is always displayed as the first command in the list.

Along with the command ID, the list includes a description of the command, identifies the command as a menu or an application function, and shows the menu on which the command is defined. Note that some commands may exist within the application but not be available to a user for security reasons. Therefore, this list may be different for different users of the same application.

Key fields

Starting Cmd A starting command ID can be specified for the list, or all commands will be listed if this field is left blank.

Related topics


MHAC - Menu Hierarchy of Available Commands

The following sections document the MHAC function:

"Purpose"
"Key fields"
"Related topics"

The Menu Hierarchy of Available Commands figure is an example of the MHAC function, or view an actual image of the MHAC screen in a separate window.

Figure: Menu Hierarchy of Available Commands


Please enter new key fields                                                   
 NSOMHAC 1 TEST    Menu Hierarchy of Available Commands - MHAC   01/05/01 16:50
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:                                                  
-------------------------------------------------------------------------------
                NSM-MS - Natural Secured Menus - Maintenance Sys               
                  Desk Administrator's Menu                                    
 MM   Cmd    Cmd  Description                                                  
      MHAC   D    Desk                                                         
      MHAC   DA   Desk Assignment                                              
    x DAM    LDB  List Desk for a Budgetary Unit                               
      ISM    LUD  List Users (desk assignments) for a Desk                     
      AAM    LAD  List Applications for a Desk                                 
      HELP   LHDA List Historical Desk Assignments                             
      CDCD   LPBD List Positions for a BU and Date                             
      LOG    LUU  List User IDs for a User                                     
      FIN                                                                      
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt GoTo                                                                 

Purpose

The MHAC function is used to list commands on a menu while still seeing the menu hierarchy used to reach the menu of interest. Initially the display is of only the main application menu. The menu commands listed are available to be marked or selected. The first menu marked or selected is then expanded to the right, with the menu commands on that menu available for selection. Thus, each column of command IDs displayed represents a menu, with new columns opened to the right as deeper selections are made. The menu command that had been selected from each of these columns is intensified or displayed in a different color providing a visual map of the menus traversed to reach any particular command or menu. Note that only one selection will be acted upon each time Enter is pressed: the left most menu selected has first precedent and then the top most selection. Commands representing application functions may not be selected, only menu commands may be exploded. A description of the commands on a menu is provided only for the deepest menu selected.

The cursor may placed on any command and PF6 pressed to select that command ID and place it in the banner. If it is a function command, PF2 may be pressed to suspend to that function. Enter may be pressed to navigate to that command, whether it is a menu or a function.

Key fields

There are no key fields used by the MHAC function.

Related topics


[an error occurred while processing this directive]
[an error occurred while processing this directive]
[an error occurred while processing this directive]

DAM - Desk Administator's Menu

The Desk Administrator's Menu contains the commands used to perform desk administration: defining desks, making desk assignments, and various list functions to display related information. The complete menu appears in the Desk Administrator's Menu Figure, or view an actual image of the Desk Administrator's Menu screen in a separate window.

Figure: Desk Administrator's Menu


Enter, mark or position cursor to desired command                             
 NSOMENU 1 TEST          Desk Administrator's Menu - DAM         01/09/01 13:19
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:                                                  
-------------------------------------------------------------------------------
   CMD  Command description                      Required key fields           
   ---- ---------------------------------------- ------------------------------
 _ D    Desk                                     Desk                          
 _ DA   Desk Assignment                          Assignment Type, ID & Time    
 _ LDB  List Desk for a Budgetary Unit           Budgetary Unit & Desk         
 _ LUD  List Users (desk assignments) for a Desk Desk & Time                   
 _ LAD  List Applications for a Desk             Desk & Appl                   
 _ LHDA List Historical Desk Assignments         Assignment TYpe, ID & Time    
 _ LPBD List Positions for a BU and Date         Budgetary Unit, Occ Cd & Date 
 _ LUU  List User IDs for a User                 User                          
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help        Quit                                                                                                                   

D - Desk maintenance

The following sections document the Desk maintenance function:

"Purpose"
"Key fields"
"Actions"
"Special validations"
"Related topics"

The Desk maintenance figure is an example of the Desk maintenance function, or view an actual image of the desk maintenance screen in a separate window.

Figure: Desk maintenance


Please enter new key fields
 NSOD    1                    Desk maintenance - D               07/05/94 11:43
 Command:      Action: V  Desk: FSTC      Appl:           Cmd Sec Grp:
 Val Sec Grp:           Parm:
-------------------------------------------------------------------------------
  Action: V  Desk ID: FSTC
 
   Name: Financial Systems Training Coordinator
   BU:   AVCF  ASSO VICE CHAN FINAN
 
   Description of Desk Responsibilities:
   Train everyone and write documentation for BASIS systems. This position
   requires access to all BASIS applications, such as LEAVE, PSB, UPS,
   GJIM. Access to NSM-MS is also included. This position is not an owner
   of any of these applications.
 
 
 
 
 
 
 Entered: 08/19/93 Updated: 01/12/94 by: KATHRYN
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode                   NextR

Purpose

The Desk maintenance function is used to maintain Desk IDs. Desk IDs are associated with a specific budgetary unit. The head of the Department or his/her representative (desk administrator) can add, modify, or delete desk IDs for that budgetary unit. This person can also assign positions and users to the desk IDs under his/her budgetary unit by using the function DA, Desk Assignment.

Key fields

Action Possible values for action include V (View), A (Add), U (Update), and D (Delete). See topic "Actions" for descriptions of these types of processing.
Desk ID A list of Desk IDs can be obtained by pressing PF1 (Help) while the cursor is positioned on this field. This list is in sequence of the name of the individual assigned to the desk. A list of all Desk IDs for a budgetary unit may be displayed by accessing the function LDB.

Actions

The following actions are possible for this function. Use of some actions may be restricted for some users. No data will be created, modified, or deleted until PF10 is pressed.

View (Display existing Desks)

To view an existing Desk, enter in the banner a 'V' in the Action field and the desired Desk ID.

Add (Create new Desks)

To create a new Desk, enter in the banner an 'A' in the Action field and the new Desk ID. Enter the appropriate values for Desk Name and Budgetary Unit. The Desk Description is optional.

Update (Modify existing Desks)

To modify an existing Desk, enter in the banner a 'U' in the Action field and the desired Desk ID. Enter or replace valid values for the desired fields.

Delete (Delete existing Desks)

To delete an existing Desk, enter in the banner a 'D' in the Action field and the desired Desk ID. In order to delete a Desk, that Desk must not:

Special validations

To add, modify, or delete a Desk, the user's desk must be authorized to the budgetary unit of that specific Desk. If the desk administrator changes the desk's budgetary unit, the new budgetary unit must be one authorized for that administrator. Any user whose desk has access to the Desk function may view any Desk ID in any budgetary unit.

Related topics


DA - Desk Assignment maintenance

The following sections document the Desk Assignment maintenance function:

"Purpose"
"Key fields"
"Actions"
"Special validations"
"Related topics"

The Desk Assignment maintenance figure is an example of the Desk Assignment maintenance function, or view an actual image of the desk assignment screen for a position or the desk assignment screen for a user in a separate window.

Figure: Desk Assignment maintenance


Make changes and press ENTER to validate                                      
 NSODA   1 TEST               Desk Assignment - DA               12/12/00 09:42
 Command:      Action: U  Desk: CHAOS     Appl:           Cmd Sec Grp:         
 Val Sec Grp:          Assignment Type: P ID: 08057    Time: 12/12/2000 09:42  
-------------------------------------------------------------------------------
  Action: U  Desk Assignment Type: P ID: 08057    Effective: 12/12/2000 09:42  
                                                       thru: 12/31/2099 23:59  
                                                                               
 Position filled by Emp: 128828 Wimberly, David                                
 Appointed Position: 8057  COMP Computing Services        Effective: 07/01/2000
                Loc: FAY  SubLoc: ADMN Appt Period: 12 Type: R thru: 12/31/2099
              Title: Project/Program Director                                  
 Hourly Wage Rate(s):                                       Ends:              
                                                                               
                                                                               
                                                                               
                                                                               
 Primary Desk: CHAOS                                                           
 Interim Desk:                                                                 
                                                                       Program 
 Updated: 11/29/2000 15:52 by: wdw                                     NSBDC7  
 Ended:                                                                        
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             NextR       Save               

Purpose

The Desk Assignment maintenance function is used to assign desks to either Positions or User IDs effective at a specific point in time. The budgetary unit of the desk must match the allocated BU of the position as of the effective date of the assignment (for position type assignments) or must match the BU associated with the user based upon the type of User ID. If an active User ID, the user must have an active hourly wage rate in that BU or not be a Unverity employee. If a temporary User ID, the ID must be assigned to an appointed employee and the desk BU must match the allocated BU of his position. The effective time of all assignments must be current or future times (changes cannot be made retroactive). For position type assignments only, two desks may be specified representing a primary and an interim desk assignment. The head of the Department or his/her representative (desk administrator) can add, modify, or delete desk assignments only for his/her budgetary units. The desk administrator can also maintain Desk IDs under his/her budgetary unit by using the function D, Desk maintenance.

Key fields

Action Possible values for action include V (View), A (Add), U (Update), and D (Delete). See topic "Actions" for descriptions of these types of processing.
Assignment Type The assignment type is either P for a position type or U for a user type assignment.
Assignment ID The assignment ID is either a 5 digit PSB position number for a position type assignment or an active or temporary User ID for a user type assignment. An error will occur if the operator is not authorized for the BU associated with the position or user.
Time The date and time the assignment is to begin must be specified for adds and updates. For viewing or deleting this date and time is used to locate the desired assignment. The time value may be entered in several formats including: mm/dd/yyyy hh:mm, mmddyyyyhhmm, mm/dd/yy hh:mm, or mmddyyhhmm.

Actions

The following actions are possible for this function. Use of some actions may be restricted for some users. No data will be created, modified, or deleted until PF10 is pressed.

View (Display existing Desk Assignments)

To view an existing assignment, enter in the banner a 'V' in the Action field and the desired Assignment Type, ID, and date/time.

Add (Create new Desk Assignments)

To create a new assignment, enter in the banner an 'A' in the Action field and the Assignment Type, ID and the future date/time you wish the assignment to be effective. Enter the appropriate values for Desk.

Update (Modify existing Assignments)

To modify or change an existing assignment effective at a future time, enter in the banner a 'U' in the Action field and the desired Assignment Type, ID and the future date/time you wish the assignment to be effective. Enter or replace the Desk.

Delete (Delete existing future Assignments)

To delete a future assignment, the desk ID must be blank (it must have been previously removed). Enter in the banner a 'D' in the Action field and the desired Assignment Type, ID and the future date/time identifying the assignment to be deleted. In most cases it is not necessary to delete assignments, rather you only need to remove the desk (leave it blank) within a new assignment. After removing the desk, you can then delete the future assignment if desired.

Special validations

To add, modify, or delete an Assignment, the operator must be authorized for the budgetary unit associated with the assignment either based upon the position or the employment status of the user. Further, the budgetary unit of the desk being assigned must likewise match the BU of the position or of the user.

Related topics


LDB - List Desks for a Budgetary unit

The following sections document the List Desks for a Budgetary unit function:

Purpose
Key fields
Related topics

The List Desks for a Budgetary unit figure is an example of the List Desks for a Budgetary unit function, or view an actual image of the LDB screen in a separate window.

Figure: List Desks for a Budgetary unit


Select an entry, PF7 to page back, PF8 to page forward, or enter new keys     
 NSOLDB  1 TEST       List Desk for a Budgetary Unit - LDB       12/15/00 10:42
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:           BU: COMP                               
-------------------------------------------------------------------------------
   List for BU: COMP  Computing Services                                       
         starting from Desk:                                                   
                                                         Appl  Appl    Target  
   Desk     Desk Name                          Assigned Access Owner  Reviewer 
 _ ATLAS    Don Barnett                           X       X      X       X     
 _ ATREUS   BASIS development desk                X       X      X             
 _ ATROPOS  Converted for Elmond Orwig            X       X      X             
 _ AURORA   Converted for Eugenia Schein          X       X      X             
 _ AUSTER   BASIS II Programmer Analyst - MF              X              X     
 _ AVERNUS  Programmer Analyst on BASIS           X       X      X       X     
 _ BACCHUS  BASIS Programmer for LEAVE            X       X      X       X     
 _ BOREAS   Converted for Paula Waters                    X                    
 _ BRIAREUS Warlock for the Wizard                X       X      X       X     
 _ BRISEIS  Converted for Polly Croak             X       X      X             
                                                                               
                 Desks    11 thru    20 of    54 are displayed                 

Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt       Back  Forwd                          

Purpose

The List Desks for a Budgetary unit function is used to display desks assigned to a specific budgetary unit. These desks are listed in sets of ten and include the desk ID and name, as well as indicators that show if the desk is assigned to a user, has access to an application, is an application owner, and is a Target reviewer. Use PF8 to scroll forward through the list of desks. The display near the bottom of the screen indicates which set of desks is displayed and the total number of desks. PF5 will restart the list with the first set of desks. Desk IDs may be marked for selection and further processing.

Desks are created, modified, and deleted through the Desk maintenance (D) function.

Key fields

BU Budgetary unit. A list of Budgetary units can be obtained by pressing PF1 (Help) while the cursor is on this field.
Desk ID Desk ID is used as a starting value. A list of assigned Desk IDs displayed in user name order may be obtained by pressing PF1 (Help) while the cursor is on this field.

Related topics


LUD - List Users for a Desk

The following sections document the List Users for a Desk function:

The List Users for a Desk figure is an example of the List Users for a Desk function, or view an actual image of the LUD screen in a separate window.

Figure: List Users for a Desk


Select an entry, or enter new keys                                            
 NSOLUD  1 TEST  List Users (desk assignments) for a Desk - LUD  12/15/00 13:33
 Command:      Action: V  Desk: CHECKIT   Appl:           Cmd Sec Grp:         
 Val Sec Grp:          Assignment Type:   ID:          Time: 12/15/2000 13:33  
-------------------------------------------------------------------------------
 List of Desk Assignments as of: 12/15/2000 13:33                              
            for Desk: CHECKIT  for changing bu security in HMRS                
                                                                               
       Assignment                                       User    Employment     
   Cmd Typ ID       Name or Title                       Status  Status and BU  
 _ DA   P  02301    Carey, Jennifer C.                          Appt'd in HMRS 
 _ DA   P  03312    Shoemaker, Becky                            Appt'd in HMRS 
 _ DA   P  07714    Ray, Richard G                              Appt'd in HMRS 
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
               Desk Assignments     1 thru     3 are displayed                 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt                                            

Purpose

The List Users for a Desk is used to display the desk assignments (and users) for a Desk ID as of a specific point in time. These assignments are listed in sets of ten and include the assignment type and ID, user's name (or title if an unfilled position), user status if a user type assignment, and employment status and BU for the user or position. Use PF8 to scroll forward through the list. The display near the bottom of the screen indicates which set of users is displayed. PF5 will restart the list with the first set of desk assignments/users. Desk assignments may be marked for selection and further processing, navigating to the DA function by default.

Desk assignments are maintained using the Desk Assignment, DA, function.

Key fields

Desk ID Identifies the desk for which the list of users/desk assignments is to be generated. A list of the Desk IDs for a BU can be viewed using command LDB. A list of Desk IDs that have been assigned can be obtained by pressing PF1 (Help) while the cursor is on this field. This list is in sequence of the name of the user assigned to the desk.
Time Identifies the point in time for which the list of desk assignments is to be generated.

Related topics


LAD - List Applications for a Desk

The following sections document the List Applications for a Desk function:

The List Applications for a Desk figure is an example of the List Applications for a Desk function, or view an actual image of the LAD screen in a separate window.

Figure: List Applications for a Desk


Select an entry, PF8 to page forward, or enter new keys                       
 NSOLAD  1 TEST        List Applications for a Desk - LAD        12/15/00 15:13
 Command:      Action: V  Desk: CHAOS     Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:                                                  
-------------------------------------------------------------------------------
   List for Desk: CHAOS     Wizard of the Realm                                
              starting from Appl:                                              
                                              Sec Command    Value    Job Sec  
   Appl ID  Application Name                  Lvl Sec Grp   Sec Grp    Class   
 _ BIS      Balance Inquiry System             5  DCCF      NO04              
 _ CS-ACCT  Computing Services Accounting      9  ALL                 ABC     
 _ DA-GRADS Dev & Alumni - Gift Recording & D  9  ALLTBL              AD      
 _ DART     Departmental Accounting            9  ALL       COMP              
 _ FMLIB    Facilities Management System Lib   9  ALL                         
 _ FORUM    Feedback Or Request from Users of  7  ALL                         
 _ GJIM     General Journal Interface Module   6  ALL                         
 _ HRLY-TS  Hourly Time Sheets                 9  ALL       ALL               
 _ INRS     Institutional Research Applicatio  9  ALL                 A       
 _ JOBS     Job Submission Application         9  COMPUSER                    
                                                                               
          Applications 1     thru 10    of 30    are displayed                 
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             Forwd                          

Purpose

The List Applications for a Desk function is used to display applications to which a specific Desk has been granted access. These applications are listed in sets of ten and include the application ID and name, as well as the desk's security level, command security group, value security group, and job security class for that application. Use PF8 to scroll forward through the list of applications. The display near the bottom of the screen indicates which set of applications is displayed and the total number of applications. PF5 will restart the list with the first set of applications. Application IDs, command security groups, and value security groups, may be marked for selection and further processing.

Desks are granted access to applications through the Application-Desk (AD) function. Some applications provide "default access". This means that any user may access the application without his desk being explicitly granted access to the application and even without being assigned a desk. The default access grants the user a specific level of security within the application, usually view-only. A user's desk may, however, be granted access to the application with a greater level of security and perhaps to more commands than default access provides. Applications defined as "default access" may not be listed by LAD because this lists only those applications to which the desk has specifically been granted access. To see if an application provides default access, use the ADA, Application Default Access, command.

Key fields

Desk ID Identifies the desk for which the list of applications is to be generated. A list of Desk IDs by user name can be obtained by pressing PF1 (Help) while the cursor is on this field. This list is in sequence of the name of the individual assigned to the desk.

Decode processing

PF4 is used to decode selected entries. To obtain additional information about the application, mark the desired application and press PF4. The application's total number of desks, command security groups, and value security groups and the date of the last notice for the application are displayed in a window.

Related topics


LHDA - List Historical Desk Assignments

The following sections document the List Historical Desk Assignments for an assignment type and ID function:

The List Historical Desk Assignments figure is an example of the List Historical Desk Assignments function, or view an actual image of the LHDA screen in a separate window.

Figure: List Historical Desk Assignments


Select an entry, or enter new keys                                            
 NSOLHDA 1 TEST      List Historical Desk Assignments - LHDA     12/15/00 16:33
 Command:      Action: U  Desk: NEWBIE    Appl:           Cmd Sec Grp:         
 Val Sec Grp:          Assignment Type: U ID: EBRYANT  Date: 12/15/2000        
-------------------------------------------------------------------------------
 List of Historical Desk Assignments on or after: 12/15/2000                   
   of Type: U for ID: EBRYANT  Evelyn Bryant                                   
                                                                               
   Cmd  __Period Begin__ ___Period End___         Desk ID                      
 _ DA   11/29/2000 15:52 12/15/2000 16:32 Primary CARS                         
 _ DA   11/29/2000 15:52 12/15/2000 16:32 Interim NEWBIE                       
 _ DA   12/15/2000 16:33 12/31/2099 23:59 Primary CARS                         
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
               Desk Assignments     1 thru     3 are displayed                 
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt                                            

Purpose

The List Historical Desk Assignments function display the desk assignments for an assignment type and ID on or after a specified date. These assignments are listed in sets of ten and include the beginning and ending time period for each assignment and the primary and/or interim desk. Use PF8 to scroll forward through the list. The display near the bottom of the screen indicates which set of assignments is displayed. PF5 will restart the list with the first set of desk assignments. Desk assignments may be marked for selection and further processing, navigating to the DA function by default.

Desk assignments are maintained using the Desk Assignment, DA, function.

Key fields

Assignment Type The assignment type is either P for a position type or U for a user type assignment.
Assignment ID The assignment ID is either a 5 digit PSB position number for a position type assignment or a User ID for a user type assignment.
Date Identifies the date for which the list of desk assignments is to be generated -- those effective on or after that date.

Related topics


LPBD - List Positions for a Budgetary Unit and Date

The following sections document the List Positions for a Budgetary Unit and Date function:

The List Positions for a BU and Date figure is an example of the LPBD function, or view an actual image of the LPBD screen in a separate window.

Figure: List Positions for a BU and Date


Select an entry, PF7 to page back, PF8 to page forward, or enter new keys     
 NSOLPBD 1 TEST      List Positions for a BU and Date - LPBD     12/18/00 11:33
 Command:      Action: U  Desk:           Appl: NSM-MS    Cmd Sec Grp: DM-ONLY 
 Val Sec Grp:           Parm:           BU: COMP Occ Cd:      Date: 12/18/2000
-------------------------------------------------------------------------------
   List Positions for BU: COMP effective 12/18/2000 starting from Occ Cd       
                                                                               
   ____________Occupation__________ ________Position_________                  
   Code             Title           Number Begin      End     Emp ID Desk ID   
 _ D051 Comp Support Spec III - Ins 2653  07/01/00 12/31/2099 101451           
 _ D059 Systems Programmer I - Inst 733   04/01/98 12/31/2099                  
 _ D060 Systems Programmer II - Ins 4667  07/01/00 12/31/2099 104038 ARTEMIS   
 _ D062 Systems Analyst III - Inst  7089  07/01/00 12/31/2099 101123 POKER     
 _ D062 Systems Analyst III - Inst  7090  07/01/00 12/31/2099 101190           
 _ D062 Systems Analyst III - Inst  7091  07/01/00 12/31/2099 116352 CHAPTER   
 _ D062 Systems Analyst III - Inst  7092  07/03/00 12/31/2099                  
 _ D062 Systems Analyst III - Inst  7093  07/01/00 12/31/2099 105937 ARES      
 _ D062 Systems Analyst III - Inst  7094  07/01/00 12/31/2099 115000           
 _ D062 Systems Analyst III - Inst  7095  07/01/00 12/31/2099 105245 BRIAREUS  
Default command selected: DA                                                   
 Position records    51 thru    60 displayed;   72 accessed but not effective  
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt       Back  Forwd                          

Purpose

The List Positions for a BU and Date function displays the PSB positions for a budgetary unit as of a specified date starting from an occupation code (optional). The occupation code, title, position number, and beginning/ending effective date of the position entry are displayed. If the position is filled as of that date, the Employee ID is displayed. If the position has a desk assignment as of that date, the primary desk ID is displayed. This information is displayed in sets of ten. However, since not all records accessed are effective on the specified date the list may be interrupted periodically and only a partial set displayed. The message indicating this has occurred is: Processing interrupted after nn records accessed; press PF8 to continue search. PF8 may be pressed to continue accessing additional positions and is also used to scroll forward once the screen is full. The display near the bottom of the screen indicates which set of positions is displayed. PF5 will restart the list with the first set of positions. Positions may be marked for selection and further processing (as a desk assignment type of P and assignment ID of the position number), navigating to the DA function by default.

Key fields

BU The Budgetary Unit for which positions are to be listed. A list of Budgetary units can be obtained by pressing PF1 (Help) while the cursor is on this field.
Date Identifies the date for which the list of positions is to be generated -- those effective on that date.
Occ Cd An optional starting occupation code within the selected budgetary unit. PF1 may be used to select an occupation code from the table of allowable values.

Related topics


LUU - List User IDs for a User

The following sections document the List User IDs for a User function:

Purpose
Key fields
Related topics

The List User IDs for a User figure is an example of the List User IDs for a User function, or view an actual image of the LUU screen in a separate window.

Figure: List User IDs for a User


Select an entry, PF8 to page forward, or enter new keys                       
 NSOLUU  1 TEST       List User IDs for a User (SSN) - LUU       12/15/00 15:27
 Command:      Action: V  Desk: CHAOS     Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:           User: PCAMPBE                          
-------------------------------------------------------------------------------
 List User IDs for a User (SSN): PCAMPBE  Campbell, Pete                       
  Employee ID: 133552 Name: Campbell, Pete                                     
  Appointed Position: 8185  BU: PW   Pete's World             Eff: 12/01/2000  
            Loc: FAY  SubLoc: ADMN Appt Period: 12 Type: R   Thru: 12/31/2099  
          Title: Project/Program Manager                                       
  Hourly Wage Rate(s):                                       Ends:             
                                                                               
                                                                               
                                                                               
                                                                               
                                                      Assignment               
   Cmd  User ID  User Name                       Stat Type ID                  
 _ DA   PCAMPBE  Campbell, Pete                    A    P  08185               
 _ DA   GLTST01  Campbell - GL Temp ID I, Pete     T    U  GLTST01             
 _ DA   GLTST02  Campbell - GL Temp ID II, Pete    T    U  GLTST02             
 _ DA   GLTST03  Campbell - GL Temp ID III, Pete   T    U  GLTST03             
              Desk IDs     1 thru     4 of    21 are displayed                 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt             Forwd                          

Purpose

The List User IDs for a User displays all User IDs assigned to the same individual based upon the social security number associated with each user ID. (An individual can have one active ID and several temporary IDs.) Any current desk assignment is displayed along with each ID, plus basic employee and current employment information for the individual.

Key fields

User ID Identifies the user for which the list of user IDs is to be generated. A list of User IDs ordered by last name can be obtained by pressing PF1 (Help) while the cursor is on this field.

Related topics


ISM - Initialization and Setup Menu

This menu contains the functions used by Computing Services to define a new application or perform maintenance functions for existing applications. The complete menu appears in the Initialization and Setup Menu figure, or view an actual image of the Initialization and Setup Menu screen in a separate window.

Figure: Initialization and Setup Menu


Enter, mark or position cursor to desired command                             
 NSOMENU 1 TEST        Initialization and Setup Menu - ISM       01/12/01 15:45
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:                                                  
-------------------------------------------------------------------------------
   CMD  Command description                      Required key fields           
   ---- ---------------------------------------- ------------------------------
 _ U    User maintenance                         User                          
 _ A    Application maintenance                  Appl                          
 _ M    Menu maintenance                         Appl, Menu Cmd                
 _ LAA  List Applications of an Analyst          Appl, User                    
 _ LVDB List Value sec grp for a Desk admin's BU Budgetary Unit                
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help        Quit                                                         

U - User maintenance

The User maintenance, screen 1 figure is an example of the first screen of the User maintenance function, or view an actual image of the first User maintenance screen in a separate window.

Figure: User maintenance, screen 1


Press PF8 to view next screen or enter new keys                               
 NSOU    1 TEST               User maintenance - U               01/12/01 16:06
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:           User: WDW                              
-------------------------------------------------------------------------------
  Action: V  User ID: WDW                                         Screen 1 of 2
                                                                               
                                                                               
     Status: A                                                                 
     SSN:    465-96-2408 Emp ID: 128828 on Employee                            
                           Name: Wimberly, David                               
     Name:   Wimberly, David                                                   
             Last Comma First and Middle                                       
     BU:     COMP Computing Services       (Sync'd up monthly)                 
                                                                               
     Case Translation: L                                                       
                                                                               
                                                                               
                                                                               
                                                                               
     Entered:          Updated: 09/01/00 by: WDW                               
                                             David Wimberly                    
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode                   NextS                          

Purpose and Usage

The User maintenance function is used to add, view, or update information about Natural users. The permitted Action codes are: A, V, or U respectively. Values for User ID and Action are always required.

To add or update a user, enter or replace valid values for the required fields. To view, only the desired User ID is necessary. PF10 is required to confirm Actions A and U.

This is a two screen function. The first screen contains user attributes that are maintained by the system administrator. The second screen contains optional elements that may be maintained by the user through the user profile (available from the LOGON application). The field validations and special processing associated with the second screen are documented separately.

The remaining sections address:

"Field Validations, screen 1"
"Special Processing, screen 1"
"Data Base Changes"

Field Validations, screen 1

The following edits are performed on the input data for screen one. Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

A

User ID must not exist on the USER file and must not already exist on the NATURAL-SECURITY file.

V,U

User ID must exist on the USER file.

A,U

Status must be A (Active), I (Inactive), or T (Temporary).

A,U

SSN must uniquely identify a record on the USER file if the ID's status is A (Active).

A,U

User Name must be non-blank and contain only alpha characters, one comma, periods or dashes. User Name is in the format last name, comma (required), first and/or middle names or initials.

A,U

Case Translation, if entered, must be either 'U' (Upper) or 'L' (Lower).

Special Processing, screen 1

Action

Special Processing

A

Case Translation is defaulted to 'U'.

A,U

The User Name is not translated to upper case on input.

A

The User is added to Natural Security.

V

User SSN is a restricted field and will be conditionally displayed based upon the security level in effect (must be greater than 2).

Data Base Changes

Data base changes are only performed if all data is valid and PF10 is entered.

Action

Effect on Data Base

A

A new record is stored on the USER file with the corresponding logical field assignments. Additional assignments include: DATE-OF-ENTRY and DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

U

The existing record on the USER file is updated with the corresponding logical field assignments. Additional assignments include: DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.


U - User maintenance, Screen 2

The User maintenance, screen 2 figure is an example of the second screen of the User maintenance function, or view an actual image of the second User maintenance screen in a separate window.

Figure: User maintenance, screen 2


Please enter new key fields                                                   
 NSOU    1 TEST               User maintenance - U               01/12/01 17:00
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:         
 Val Sec Grp:           Parm:           User: WDW                              
-------------------------------------------------------------------------------
  Action: V  User ID: WDW      Wimberly, David                    Screen 2 of 2
                                                                               
   Email Address: wdw@comp.uark.edu                                            
   CMS ID:        DW85047  @ UAFSYSB      Campus Mail Bldg:    ADSB Room: 220 
   Print Dest:    A-DW85047               Default Application:                 
   PF-Key Format  N     Message Line: T   Terminal Type:       3279            
                                                                               
  Color Assignments for 3279 terminals:                                        
                       Modifiable:    Protected:                               
    Default Intensity:     GR             NE         PFKey Name:     GR        
    Intensified:           TU             YE         PFKey Function: TU        
    Reverse Video:         GR             NE         Message Line:   RE        
    Underline:             TU             YE         Override Flag:  N (Y/N)   
  NSM Field options: Modifiable default:      V      Color: NE                 
                     Modifiable intensified:  V             YE                 
                     Conditionally protected: D             TU                 
                     Previous value:          V             GR                 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit                    PrevS NextR                          

Purpose and Usage

Screen two of the User maintenance function is used to view or maintain user profile parameters. This is an optional screen and contains the same elements also maintained by the user profile function available at LOGON.

The remaining sections address:

"Field Validations, screen 2"
"Special Processing, screen 2"

Field Validations, screen 2

The following edits are performed on the input data for screen two. Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

A,U

If CMS id is entered, it must be the complete id, including the node (e.g., UAFSYSB).

A,U

PF-Key format must be either 'N' or 'S'.

A,U

Terminal type must be '3270', '3278', or '3279'.

A,U

Message Line position must be either 'T' or 'B'.

A,U

Color assignments for all field types, message line, and PF-Keys are available only for 3279-type terminals. If entered, the color entered must be one of the Natural color codes: BL, GR, NE, PI, RE, TU, and YE.

A,U

The Override Flag, to override program assigned colors with those defined by the user, must be either 'Y' or 'N'.

A,U

The attribute code for NSM fields must be one of the Natural attribute codes: D, V, I, U, C, or B.

Special Processing, screen 2

Action

Special Processing

A

Default values for the user profile are established as follows: Terminal type is '3270', PF-Key format is 'N', Message line position is 'T', NSM modifiable default fields' attribute is 'V', NSM modifiable intensified fields' attribute is 'I', NSM conditionally protected fields' attribute is 'D', and NSM previous value fields' attribute is 'V'.

A,U

When the user enters color codes and field attributes, the corresponding fields on the screen which are defined with those attributes reflect the user's choices. For example, when a user selects the color code 'BL' for the PF-Key name and presses ENTER, the PF-Key names at the bottom of the screen are displayed in Blue.


A - Application maintenance

The Application maintenance, screen 1 figure is an example of the first screen of the Application maintenance function, or view an actual image of the first Application maintenance screen in a separate window.

Figure: Application maintenance, screen 1


All entries are valid, press PF10 to Save
 NSOA    1                 Application maintenance - A           01/11/94 17:06
 Command:      Action: U  Desk:           Appl: NSM-DEMO  Cmd Sec Grp:
 Val Sec Grp:           Parm:
-------------------------------------------------------------------------------
       Action: U  Application ID: NSM-DEMO                        Screen 1 of 2
 
       Application Name: NSM Demonstration Application
 Owner
 Desk ID  Desk Name                      Analyst   Analyst Name
 CHAOS    Converted for W. David Wimbe   WDW      Wimberly, W. David
 AVERNUS  Converted for Kathryn Cantre
 ASTRAEA  Converted for Lonnie Deavens
 ATLAS    Don Barnett
 
 
     Library: NSM-DEMO  Application Lock: U   X NSM Application
    Application Prefix: ND Application Prefix for Predict 'Fields':
    Value Security Maintenance Program:          Main Menu Command: MENU
 
 
 Entered: 08/03/92 Updated: 10/28/93 By: KATHRYN
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             NextS       Save

Purpose and Usage

The Application maintenance function is used to add, view, update or delete information about Natural Applications. The permitted Action codes are: A, V, U or D respectively. Values for Application ID and Action are always required. To add or update information for an application, enter or replace valid values for the required fields. To view or delete, only the desired Application ID is necessary. PF10 is required to confirm Actions of A, U or D.

This is a two screen function. The first screen contains the primary application attributes. The second screen is used to define security levels and action attributes for NSM applications. The field validations and special processing associated with the second screen are documented separately.

The remaining sections address:

"Field Validations, screen 1"
"Special Processing, screen 1"
"Data Base Changes"

Field Validations, screen 1

The following edits are performed on the input data for screen one. Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

V,U,D

Application ID must exist on the APPLICATION file.

A

Application ID must not exist on the APPLICATION file.

A,U

Library is required.

A,U

Application Name must be non-blank.

A,U

Owner Desk IDs must be valid desks, and Analyst IDs must be valid users.

A,U

At least one valid Owner Desk ID and one valid Analyst ID are required. The primary owner responsible for the Application should be entered as the first Owner Desk ID and similarly for Analyst.

A,U

Application Prefix and Main Menu Command are required if the NSM Application switch is set to true.

D

No references to this application must exist in the MENU-COMMAND, APPLICATION-DESK, COMMAND-SECURITY, or VALUE-SECURITY files.

Special Processing, screen 1

Action

Special Processing

A

The NSM Application switch defaults to true.

A,U

Application Name is not translated to upper case on input.

A,U

Whenever an Owner Desk ID is entered, all of the Owner IDs' Names are retrieved from the DESK file and displayed.

A,U

Whenever an Analyst is entered, all of the Analysts' Names are retrieved from the USER file and displayed.

V,U,D

When PF4 is pressed, all the Owners' names, Analysts' names, and the Last Updated By name are retrieved from the appropriate files and displayed.

Data Base Changes

Data base changes are only performed if all data is valid and PF10 is entered.

Action

Effect on Data Base

A

A new record is stored on the APPLICATION file with the corresponding logical field assignments. Additional assignments include: APPLICATION-LOCK = U, DATE-ENTERED = current date, DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

U

The existing record on the APPLICATION file for the specified Application ID is updated with the corresponding logical field assignments. Additional assignments include DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

D

The record on the APPLICATION file for the specified Application ID is deleted.


A - Application maintenance, Screen 2

The Application maintenance, screen 2 figure is an example of the second screen of the Application maintenance function, or view an actual image of the second Application maintenance screen in a separate window.

Figure: Application maintenance, screen 2


All entries are valid, press PF10 to Save
 NSOA    1                 Application maintenance - A           01/11/94 17:06
 Command:      Action: U  Desk:           Appl: NSM-DEMO  Cmd Sec Grp:
 Val Sec Grp:           Parm:
-------------------------------------------------------------------------------
 Action: U  Application Id: NSM-DEMO                              Screen 2 of 2
 Security  1 = View                          Act Action Desc       MSL  Prot
 Levels &  2 = Add                            V  View               1    X
 Comments: 3 = Update                         A  Add                2
           4 = Delete                         U  Update             3
                                              D  Delete             4    X
                                              C  Copy               3
                                              R  Review             1    X
                                              W  Withdraw txn       1    X
 
 
 
 
 
 
 
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt       PrevS NextR       Save

Purpose and Usage

Screen two of the Application maintenance function is used to view or maintain security level and action information for NSM applications. If security levels are used, they must be entered in the Security Levels & Comments area in the format:

v = description
The v denotes a one character security level value which must be followed by an equal sign. The actions must then be entered in list form accompanied by an action description, the minimum security level required by a user to perform that action (MSL) and a flag indicating whether the body of the screen should be protected from entry for that action (Prot).

The remaining sections address:

"Field Validations, screen 2"
"Special Processing, screen 2"

Field Validations, screen 2

The following edits are performed on the input data for screen two. Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

A,U

All minimum security levels (MSL) specified in the action list must occur in the Security Levels & Comments area followed by an equal sign.

Special Processing, screen 2

Action

Special Processing

A,U

The data base field VALID-SECURITY-LEVELS is constructed by concatenating all security level values parsed from the Security Levels & Comments area. This parsing is done by taking the first non-blank character from each line that contains an equal sign.


M - application Menu maintenance

The Menu maintenance figure is an example of the Menu maintenance function, or view an actual image of the Menu maintenance screen in a separate window.

Figure: Menu maintenance


Make changes and press ENTER to validate                                      
 NSOM    1 TEST               Menu maintenance - M               01/15/01 11:43
 Command:      Action: U  Desk:           Appl: NSM-MS    Cmd Sec Grp:         
 Val Sec Grp:           Parm:           Menu Cmd: MM                           
-------------------------------------------------------------------------------
  Action: U Appl: NSM-MS   Menu Cmd ID: MM      Entered:          Upd: 01/08/01
 Menu Cmd Desc: nsm maintenance system Main Menu                   By: WDW     
 Cmd  Description                              Required Keys                  T
 LAAC List All Available Commands              Command ID                     F
 MHAC Menu Hierarchy of Available Commands                                    F
 DAM  Desk Administrator's Menu                                               M
 ISM  Initialization and Setup Menu                                           M
 AAM  Application Administrator's Menu                                        M
 CDCD Change desk/Display Current Desk info                                   U
 LOG  LOGon to another natural application                                    U
 FIN  FINish your session (sign off natural)                                  U
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt EdOpt       NextR       Save               

Purpose and Usage

The application Menu maintenance function is used to add, view, update, delete or copy information about the Natural Application's menus. The permitted Action codes are: A, V, U, D, or C respectively. Values for Appl ID, Menu Cmd ID, and Action are always required.

To add or update a menu command for an Appl ID, enter or replace valid values for the required fields. To view or delete, only the desired Application ID and Menu Command are necessary. To copy menu information from a record to either a new menu or an existing one, first display a source menu (a menu from which values will be copied). Next enter 'C' in the Action field and the Application ID and Menu Command ID to which values will be copied and press ENTER. PF10 is required to confirm and effect any change.

The remaining sections address:

"Field Validations"
"Special Processing"
"Data Base Changes"

Field Validations

Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

A,C

Appl ID must exist as APPLICATION-ID on the APPLICATION file.

A

Appl ID and Menu Cmd ID must not exist as APPLICATION-ID and MENU-COMMAND-ID on the MENU-COMMAND file.

A

Menu Cmd ID must not exist as a function on another menu within the Application.

V,U,D

Appl ID and Menu Cmd ID must exist as APPLICATION-ID and MENU-COMMAND-ID on the MENU-COMMAND file.

A,U,C

Menu Cmd ID Description is required.

A,U,C

At least two Cmds are required per menu.

A,U,C

Cmds must be unique and may not appear on multiple menus.

A,U,C

T (Command Type) must be 'M', 'F' or 'U'.

A,U,C

Cmd must already exist as a menu if T is 'M' and must not exist as a menu if T is 'F' or 'U'.

A,U,C

Command Description is required for function modules (command types F or U). If T is 'M', MENU-COMMAND-DESCRIPTION is retrieved from the MENU-COMMAND file via Appl Id and Menu Cmd Id and displayed in the Description field.

D

A Menu Cmd ID may not be deleted if it exists as a COMMAND-ID within Appl ID on the MENU-COMMANDS file.

A,U,C

A Cmd may not be the same as the MENU-COMMAND it resides on.

Special Processing

Action

Special Processing

A,U,C

Menu Cmd ID description, Description, and Required Keys fields are not translated to upper case on input.

Data Base Changes

Data base changes are only performed if all data is valid and PF10 is entered.

Action

Effect on Data Base

A

A new record is stored on the MENU-COMMAND file with the corresponding logical field assignments. Additional assignments include: DATE-OF-ENTRY and DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

U

All the values for Cmd, Description, Required Keys, T, and Menu Cmd Id description are updated for the existing record on MENU-COMMAND. Additional assignments include: DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

D

The existing record for the Appl ID and Menu Cmd ID are deleted.

C

If the Menu Cmd ID already exists for the Appl ID, the effective action of the Copy is an Update. If the Menu Cmd ID does not exist, the effective action is an Add. Data base changes are as noted above for the respective effective action.


LAA - List Applications of an Analyst

The following sections document the List Applications of an Analyst function:

"Purpose"
"Key fields"
"Decode processing"
"Related topics"

The List Applications of an Analyst figure is an example of the List Applications of an Analyst function, or view an actual image of the LAA screen in a separate window.

Figure: List Applications of an Analyst screen


Select an entry, press PF8 to page forward, or enter new keys
 NSOLAA  1            List Applications of an Analyst - LAA      01/12/94 09:23
 Command:      Action: U  Desk:           Appl: BIS       Cmd Sec Grp:
 Val Sec Grp:           Parm:           User: WDW       End Appl: 99999999
-------------------------------------------------------------------------------
   List for User: WDW        Wimberly, W. David
       starting from Appl: BIS      thru Appl: 99999999
 
             Application ID   Application Name
              _ BIS           Balance Inquiry System
              _ BOQSS         Batch Oasis Query Submission Sys
              _ BUDGET        UAF Budget System
              _ CS-ACCT       Computing Services Accounting
              _ DA-GRADS      Dev & Alumni - Gift Recording & Dues Sys
              _ DA-JOBS       Batch job library for DA-GRADS
              _ DA-RPTS       Dev/Alumni Report Library
              _ DHYATT        David Hyatt's Library
              _ DW85047       David Wimberly's library
              _ GJIM          General Journal Interface Module
 
          Applications 1     thru 10    of 32    are displayed
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             Forwd

Purpose

The List Applications of an Analyst function is used to display applications for which a given user is an analyst. These applications are listed in sets of ten and include the application ID and name. Use PF8 to scroll forward through the list of applications. The display near the bottom of the screen indicates which set of applications is displayed and the total number of applications. PF5 will restart the list with the first set of applications. Application IDs may be marked for selection and further processing.

Users are defined as analysts of an application through the Application maintenance (A) function.

Key fields

User ID Identifies the user for which the list of applications is to be generated. A list of User IDs by user name can be obtained by pressing PF1 (Help) while the cursor is on this field. This list is in sequence of the name of the individual assigned to the ID.
Application ID Application ID is used as a starting search value for the list.
Ending Application ID Identifies the ending value for the list of applications. This field defaults to high values, but may be changed by the user.

Decode processing

PF4 is used to decode selected entries. To obtain additional information about the application, mark the desired application and press PF4. The application's total number of desks, command security groups, and value security groups and the date of the last notice for the application are displayed in a window.

Related topics


LVDB - List Value sec grp for Desk admin's BU

The following sections document the List Value security group for Desk administrator's BU function:

"Purpose"
"Key fields"
"Related topics"

The LVDB figure is an example of the List Value security group for Desk administrator's BU function, or view an actual image of the LVDB screen in a separate window.

Figure: List Value security group for Desk administrator's BU


Select an entry or enter new keys
 NSOLVDB 1        List Value sec grp for Desk admin's BU - LVDB  08/19/94 11:35
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:
 Val Sec Grp:           Parm:           BU: COMP
-------------------------------------------------------------------------------
   List for BU: COMP  COMPUTING SERVICES
 
         Appl      Value Sec
   Cmd   ID        Group     Value Security Group Description
 _ LDV   NSM-MS    COMP      Computing Services desks
 
 
 
 
 
 
 
 
 
 
        Value Security Groups      1 thru      1 are displayed
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt


Purpose

The List Value security groups for Desk administrator's Budgetary unit is intended to aid the user in identifying the desk administrators of a given budgetary unit. LVDB will list the Value Security Groups which have been established to define the desk administrators for a specified budgetary unit. From this list the user can select an entry and suspend to the function LDV (List Desks for a Value security group), which provides the user with a list of the desks assigned to the specified Value Security Group. From the LDV function the user can then select a desk id and suspend to LUD (List Users for a Desk) to view the user id(s) assigned to the desk, and thus identify the desk administrator(s).

In most instances there will only be one Value Security Group listed by LVDB for a budgetary unit; however, up to ten entries may be displayed. Use PF8 to scroll through the list in those instances when there are more than ten. LVDB includes within the list the LDV command, the NSM-MS application ID, the Value Security group, and the Value Security Group Description. The LDV command, the NSM-MS application ID, and the Value Security Groups may be marked for selection and further processing. The display near the bottom of the screen numerically indicates the group of Value Security Groups displayed. PF5 will restart and reset the marked entries with the first set of Value Security Groups.

Key fields

Budgetary Unit Code Identifies the budgetary unit for which the list of associated Value Security Groups will be generated. A list of valid budgetary unit codes can be obtained by pressing the PF1 key (Help) while the cursor is on this field.

Related topics


AAM - Application Administrator Menu

This menu contains the functions used by application administrators to grant access to applications, post notices for users of applications, temporarily restrict access to applications or to review these definitions in effect. The complete menu appears in Application Administrator Menu figure, or view an actual image of the AAM screen in a separate window.

Figure: Application Administrator Menu


Enter, mark or position cursor to desired command
 NSOMENU 1            Application Administrator Menu - AAM       01/11/94 10:28
 Command:      Action: V  Desk:           Appl:           Cmd Sec Grp:
 Val Sec Grp:           Parm:
-------------------------------------------------------------------------------
   CMD  Command description                      Required key fields
   ---- ---------------------------------------- ------------------------------
 _ CS   Command Security group maintenance       Appl & Cmd Sec Grp
 _ VS   Value Security group maintenance         Appl & Val Sec Grp
 _ AD   Application-Desk maintenance             Desk & Appl
 _ ADA  Application Default Access               Appl
 _ AN   Application Notice maintenance           Appl
 _ ALR  Application Lock/unlock & Reason         Appl
 _ CSLR Cmd Security group Lock/unlock & Reason  Appl & Cmd Sec Grp
 _ LUA  List Users of an Application             Appl & User
 _ LDC  List Desks for a Command security group  Appl & Cmd Sec Grp
 _ LDV  List Desks for a Value security group    Appl & Val Sec Grp
 _ LDA  List Desks for an Application            Desk & Appl
 _ LAO  List Applications of an Owner Desk       Desk & Appl
 _ CSQ  Command SeQuence list maintenance        Appl & Cmd Seq Name
 
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help        Quit

CS - application Command Security maintenance

The Command Security figure is an example of the Command Security group maintenance function, or view an actual image of the Command Security group maintenance screen in a separate window.

Figure: Command Security group maintenance


Make changes and press ENTER to validate
 NSOCS   1 TEST      Command Security group maintenance - CS     10/23/96 12:05
 Command:      Action: U  Desk:           Appl: NSM-MS    Cmd Sec Grp: SPEC
 Val Sec Grp:           Parm:
-------------------------------------------------------------------------------
  Action: U  Application Id: NSM-MS   Natural Secured Menus - Maintenance Sys
Cmd Sec Grp: SPEC     Desc: Test of the S -- as Specified -- Cmd A/D/S
Commands Allowed, Disallowed, or as Specified (A,D or S): S
 Cmd SL  Cmd SL  Cmd SL  Cmd SL  Cmd SL  Cmd SL  Cmd SL  Cmd SL  Cmd SL  Cmd SL
 ------  ------  ------  ------  ------  ------  ------  ------  ------  ------
 D    -
 UD   -
 LUD  -
 U    2
 ADA  2
 CS
 AD
 
 
 
 
Entered: 10/22/96 Updated: 10/23/96 By: WDW
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt ShowC       NextR       Save

Purpose and Usage

The application Command Security maintenance function is used to add, view, update, delete, or copy information about Natural Applications' Command Security Groups. The permitted Action codes are: A, V, U, D, or C respectively. Values for Application ID, Command Security Group, and Action are always required.

To add or update a Command Security Group, enter or replace valid values for the required fields. To view or delete, only the desired Application ID and Command Security Group are necessary. To copy command security group information to either a new command security group or an existing group, first view the source command security group (or enter values on the screen to be copied). Then enter 'C' in the Action field and the destination Command Security Group to which the screen values are to be copied and press ENTER. PF10 is required to confirm and effect any change.

The remaining sections address:

"Command Allowed, Disallowed, or as Specified"
"Field Validations"
"Special Processing"
"Data Base Changes"

Command Allowed, Disallowed, or as Specified

Command security is designed to provide the greatest flexibility possible to the application administrator while requiring a minimum of effort. This is accomplished by providing three options for defining command restrictions, which is indicated by the value entered into the Commands Allowed, Disallowed, or as Specified field.

A

An A indicates that the list of commands provided will be an inclusive list of all commands allowed. Any command not listed will not be available to users (desks) assigned this command security group. Further, a Security Level may be specified for selected commands. If provided (non-blank), that security level will be assigned to the user within that function if that level is less than the user's (desk's) normal security level.

D

D indicates that the list of commands provided are to be disallowed for the user. The user will be permitted access to all commands other than those listed, always with the user's normal security level.

S

S indicates that access to commands is provided as specified or with view only access when not specified. Any command not listed will be accessible by the user but with the most restrictive security level available within the application (normally this would be View only). Three additional options are available for those commands listed based upon the associated Security Level specification:

  • If left blank, access will be provided to the command with the user's normal security level.
  • If a valid Security Level is entered, access will be provided to the command with the lower value of either that security level or the user's normal security level. (The more restrictive of the two possibilities is used.)
  • If a '-' is entered (minus sign), access to the command is denied.
Using the as specified option offers the administrator the greatest flexibility since the only commands required to be listed are those where the user requires update access or from which the user should be denied access all together (even from view access).

Field Validations

Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

A

Appl (Application ID) and Cmd Sec Grp (Command Security Group) must not exist on the COMMAND-SECURITY file.

A,C

Appl (Application ID) must exist on the APPLICATION file.

V,U,D

Appl (Application ID) and Cmd Sec Grp (Command Security Group) must exist on the COMMAND-SECURITY file.

A,U,D

The desk ID of the operator must be an Application-Owner-Desk-ID on the APPLICATION file for this Application ID.

A,U.C

Desc (Command Security Group Description) is required, it cannot be left blank.

A,U,C

Cmd (commands) must be unique, a command cannot be repeated within this list.

A,U,C

Cmd (commands) must exist as valid Command-IDs on the MENU-COMMAND file for this Application Id.

A,U,C

Commands Allowed, Disallowed, or as Specified (A,D or S) is a required field and must be an A, D or S. On an Add, it is initialized to 'D'. If the action requested is a Copy, this field's value is copied from the source. The value S is only permitted for NSM version 2 applications (BASIS applications or any others generated using the UAF Program Generator).

A,U,C

SL (security level) can only be entered if Commands Allowed, Disallowed, or as Specified is an A or S. This value must be a valid security level for the application, as defined on screen 2 of the Application maintenance function (command A). Further, if Commands Allowed, Disallowed, or as Specified is S, this value may be an '-' indicating that this command is not allowed. See "Command Allowed, Disallowed, or as Specified" for additional information.

A,U,C

The Main-Menu-Command-ID for the application must be allowed or not disallowed.

D

A Command Security Group may not be deleted if any desk provided access to the application on the APPLICATION-DESK file (via command AD) has this same value.

Special Processing

Action

Special Processing

A,U,C

Cmd Sec Grp Desc is not translated to upper case on input.

A,U,C

PF6 is labeled as ShowC for show commands. When pressed, all commands defined for the application are retrieved and placed in the list of commands available on the screen. If modifications have been made on the screen and not saved, a warning message is displayed when PF6 is pressed that notifies the user that commands previously listed and any associated security levels are erased. Selected commands can then be blanked out as necessary. This function is useful when an application contains a large a number of commands that might be difficult to remember and enter.

V,U

When PF4 is pressed, the name of the user to last update the Command Security Group is retrieved from the USER file and displayed.

Data Base Changes

Data base changes are only performed if all data is valid and PF10 is entered.

Action

Effect on Data Base

A

A new record is stored on the COMMAND-SECURITY file with the corresponding field assignments. Additional assignments include: COMMAND-GROUP-LOCK = U, DATE-OF-ENTRY and DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

U

The existing record on the COMMAND-SECURITY file is updated with the corresponding field assignments. Additional assignments include: DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

D

The existing record on the COMMAND-SECURITY file is deleted.

C

If the Command Security Group exists for the Application ID, the effective action of the Copy is an Update. If the Command Security Group does not exist, the effective action is an Add. Data base changes are as noted above for the respective effective action.


VS - application Value Security maintenance

The Value Security maintenance figure is an example of the Value Security group maintenance function, or view an actual image of the Value Security maintenance screen in a separate window.

Figure: Value Security group maintenance


Please enter new key fields
 NSOVS   1            Value Security group maintenance - VS      08/30/93 09:37
 Command:      Action: V  Desk:           Appl: NSM-MS    Cmd Sec Grp: DM-ONLY
 Val Sec Grp: AVCF      Parm:
-------------------------------------------------------------------------------
  Action: V  Appl: NSM-MS    Val Sec Grp: AVCF
+-----------------------------------------------------------------------------+
| Press ENTER or PF3 to specify new keys                                      |
|                                                                             |
| Group description: Financial Affairs                                        |
|                                                                             |
| Permit unrestricted access (Y/N): N                                         |
|                                                                             |
| Restrict access to budgetary unit(s):                                       |
|  AVCF ASSO VICE CHAN FIN                                                    |
|                                                                             |
|                                                                             |
|                                                                             |
|                                                                             |
| Last updated: 08/19/93 By: WDW                                              |
|                                                                             |
| Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--    |
|                   Quit                                                N 3 V |
+-----------------------------------------------------------------------------+

Purpose and Usage

The Value Security maintenance function is used to add, view, update, or delete information about NSM applications' Value Security Groups on the VALUE-SECURITY file. The permitted Action codes are: A, V, U, or D respectively. Values for Application ID, Value Security Group, and Action are always required.

To add or update a Value Security Group, enter or replace valid values for the required fields. To view or delete, only the desired Application ID and Value Security Group are necessary. PF10 is required to confirm and effect any change.

Since value security requirements differ for all applications, value security maintenance is performed within a window which fills the main body of the screen. This window is presented and processed by different subprograms for each application. Because a subprogram handles the user inputs, the main program does not issue the standard warning when data is modified and the user's action will result in loss of those changes. Each subprogram must be customized for an application so that the fields needed by the application to apply record level restrictions can be defined. NSM accesses these restrictions at the time of user signon and passes this information to the function modules so that they can restrict access as necessary.

The remaining sections address:

"Field Validations"
"Special Processing"
"Data Base Changes"

Field Validations

Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

A

Application ID and Value Security Group must not exist on the VALUE-SECURITY file.

A

Application ID must exist on the APPLICATION file

V,U,D

Application ID and Value Security Group must exist on the VALUE-SECURITY file.

A,U,D

The desk of the operator must be an APPLICATION-OWNER-DESK-ID on the APPLICATION file for this Application ID.

A,U

Group description is required.

A,U

The fields used to define value based security for an application may have specific edit requirements which are enforced. The error messages displayed for these fields and help information available should adequately describe the necessary inputs.

D

A Value Security Group may not be deleted if any APPLICATION-DESK on the APPLICATION-DESK file has this same value in their VALUE-SECURITY-GROUP field.

Special Processing

Action

Special Processing

A,U

Group description is not translated to upper case on input.

Data Base Changes

Data base changes are only performed if all data is valid and PF10 is pressed.

Action

Effect on Data Base

A

A new record is stored on the VALUE-SECURITY file with the corresponding logical field assignments. Additional assignments include: DATE-OF-ENTRY and DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

U

The existing record on the VALUE-SECURITY file is updated with the corresponding logical field assignments. Additional assignments include: DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.

D

The existing record on the VALUE-SECURITY file is deleted.


AD - Application Desk maintenance

The following sections document assignment of Desks to Applications.

"Purpose"
"Key fields"
"Actions"
"Decode processing"
"Related Topics"

The Application Desk maintenance figure is an example of the Application Desk maintenance function, or view an actual image of the AD screen in a separate window.

Figure: Application Desk maintenance


Press PF8 to view more records or enter new keys                              
 NSOAD   1 TEST         Application-Desk maintenance - AD        01/15/01 14:29
 Command:      Action: V  Desk:           Appl: LEAVE     Cmd Sec Grp:         
 Val Sec Grp:           Parm:                                                  
-------------------------------------------------------------------------------
  Action:  V  Appl: LEAVE    Leave Accounting                                  
              Desk:                                                            
                                            Sec    Job      Command     Value  
  Desk Id    Name                           Lvl Sec Class  Sec Group  Sec Group
                                                                               
  ACHERON    Converted for Eric Robinson     9              USERTEST   ER      
  ADMETUS    Converted for Cathy Renner      9              USERTEST   CR      
  AETHER     Converted for Lisa Danley       7              DEPTREP    COMP    
  APPLE      Desk for Wilma Carr             9              USERTEST   WC      
  ARACHNE    Programmer on Basis             9   A          ALL        COMP    
  ARES       Converted for Allen Fields      9   A          ALL        COMP    
  ARGUS      Duchess of Time Travel          9   A          ALL        COMP    
  ASH        Desk for GLTST06                9              DEPTREP    LVADMIN 
  ASTRAEA    Converted for Lonnie Deavens    9              ALL        COMP    
  ATLAS      Don Barnett                     9              ALL        COMP    
                                                                               
                                                                               
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode                   Forwd                          

Purpose

The Application Desk maintenance function is used to maintain the assignments of desks to Natural Secured Menus (NSM) applications. An assignment of a desk to an application consists of granting access and establishing security for that desk within the application. This screen has been designed so that more than one record may be updated at one time. A maximum of ten desks are displayed on a screen.

Key fields

Action Possible values for action include V (View), A (Add), U (Update), and D (Delete). Only an owner of the Application may Add, Update, or Delete Application-Desk assignments. See "Actions" for descriptions of these types of processing.
Application ID A list of valid Application IDs may be obtained by pressing PF1 (Help) while the cursor is positioned on this field.
Desk ID Desk ID is required to Add or Delete a specific assignment of the Desk to the Application. To View or Update, Desk ID is used as a starting value so that up to ten records may be viewed or updated at one time. A list of Desk IDs by user name may be obtained by pressing PF1 (Help) while the cursor is positioned on this field.

Actions

The following actions are possible for this function. Use of some actions may be restricted for some users. No data will be created, modified, or deleted until PF10 is pressed.

View (Display existing Application-Desk assignments)

To view Application-Desk assignments, enter in the banner a 'V' in the Action field and a valid Application ID. If desired, a starting value for Desk ID may be entered. All Application-Desk records found after that starting value for the specified Application will be displayed. PF8 may be used to scroll forward to view the remaining Desks assigned to that Application.

Add (Create a new Application-Desk assignment)

To assign a Desk to an Application, enter in the banner an 'A' in the Action field, the Desk ID, and the Application ID. Only one Desk assignment can be created at a time. The first line of the list will contain the Desk ID that is being assigned access to the specified Application. This will be the only line where data entry is permitted. If there are Desks assigned to the Application that fall alphabetically after the new Desk ID, they will be listed but will be protected from entry. Enter the desired values for the remaining fields. Job Security Class and Value Security Group are only required if the Application uses these types of security.

Update (Modify existing Application-Desk assignments)

To update existing Application-Desk assignments, enter in the banner a 'U' in the Action field and the Application ID for which desk assignments have been made. If desired, a starting value for Desk ID may also be entered. Up to ten Desk IDs will be displayed, beginning with the Desk ID entered in the banner, and all those listed may be modified. PF8 may be used to scroll through records on an Update, but PF10 must be pressed prior to pressing PF8 to save any changes made to the Application-Desk records displayed.

Delete (Delete an existing Application-Desk assignment)

To delete an existing Application-Desk assignment, enter in the banner a 'D' in the Action field, the required Application ID, and Desk ID. As with Add, only one Application-Desk assignment can be deleted at a time.

Decode processing

To see additional information about the Application-Desk assignment, position the cursor anywhere on the line of the desired entry and press PF4. A window will display the date of entry, date of last update, and the Natural ID of the user who last updated the Application-Desk assignment. Additionally, descriptions for the command security group and value security group will be shown.

Related Topics


ADA - Application Default Access

The following sections document the Application Default Access function:

"Purpose"
"Key fields"
"Actions"
"Decode Processing"
"Related topics"

The Application Default Access figure is an example of the Application Default Access maintenance function, or view an actual image of the ADA screen in a separate window.

Figure: Application Default Access maintenance


All entries are valid, press PF10 to Save
 NSOADA  1              Application Default Access - ADA         08/30/93 09:40
 Command:      Action: U  Desk:           Appl: BIS       Cmd Sec Grp: DM-ONLY
 Val Sec Grp: AVCF      Parm:
-------------------------------------------------------------------------------
  Action: U  Appl: BIS       Balance Inquiry System
 
 
      Default Access Permitted? (Y/N)  Y
      Default Security Level: 5
      Default Command Security Group: NORM
                                      Command security for normal users
      Default Value Security Group: NO04
                                    No 04 companies
 
 
 
 
 
 
   Entered:          Updated: 03/04/93 By: EORWIG
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             NextR       Save

Purpose

The Application Default Access function is used to establish or eliminate default access for an application. Only an application owner can determine if the application can have default access and assign the security definitions for that access. If an application has been defined by this function as allowing default access, then any user may logon to the application. The user's security and the accessible commands are based upon the assignments defined in this function.

Key fields

Action Possible values for action are V (View) and U (Update). See "Actions" for descriptions of these types of processing.
Application ID A list of valid Application IDs may be obtained by pressing PF1 (Help) while the cursor is positioned on this field.

Actions

The following actions are possible for this function. Use of the Update action may be restricted for some users. No data will be modified until PF10 is pressed.

View (Display Application Default Access information)

To view information about an application's default access availability and default security definitions, enter in the banner a 'V' in the Action field and the desired Application ID.

Update (Modify an Application's Default Access information)

To modify an application's default access availability and default security definitions, enter in the banner a 'U' in the Action field and the desired Application ID. To allow default access for the application, enter 'Y' in the Default Access Permitted field. A security level and command security group are required so that default security can be properly defined. If the application uses security by value, a default value security group is also required. To eliminate default access for the application, enter an 'N' in the Default Access Permitted field. The remaining fields that assign default security definitions will be reset to blank because they are not needed if default access is not permitted.

Decode Processing

PF4 (DCode) can be used to display the names of the command security and value security groups that have been defined for default access.

Related topics


AN - Application Notice maintenance

The Application Notice maintenance figure is an example of the Application Notice maintenance function, or view an actual image of the AN screen in a separate window.

Figure: Application Notice maintenance


Please enter new key fields
 NSOAN   1             Application Notice maintenance - AN       08/30/93 09:42
 Command:      Action: V  Desk:           Appl: DA-GRADS  Cmd Sec Grp:
 Val Sec Grp: AVCF      Parm:
-------------------------------------------------------------------------------
Action: V Appl: DA-GRADS Dev & Alumni - Gift Recording & D Eff Date: 01/19/1990
   *
   *
   *    The DA-GRADS application is now in production.  You have accessed
   *    the TEST system.  To access production, enter CICSPROD from the
   *    VMVTAM menu.  The test system is available for testing.
   *
   *
 
 
 
 
 
 
 
 
Entered:          Last Updated: 08/17/93 By: WDW
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode                   NextR

Purpose and Usage

The Application Notice maintenance function is used to add, view, update, delete, or copy a Notice associated with a specific existing Natural Application on the APPLICATION file. This notice will be automatically displayed to any user when they logon to the application if their DATE-LAST-LOGGED-ON on the APPLICATION-USER file is before the DATE-NOTICE on the APPLICATION.

The permitted Action codes are: A, V, U, D, or C respectively. Values for Application ID and Action are always required.

To add or update, enter or replace valid values for the required fields. To view or delete, only the desired Application ID is necessary. To copy a notice to another application, display the source application's notice and enter 'C' in the Action field and the Application ID to which the notice is to be copied. The effective action of a Copy is always an Update. PF10 is required to confirm and effect any change.

The remaining sections address:

"Field Validations"
"Special Processing"
"Data Base Changes"

Field Validations

Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

A,V,U,D,C

Appl ID must exist on the APPLICATION file

A,U,C

The notice text must be non-blank.

A,U,C

Eff Date (Effective Date) must be greater than or equal to the current system date.

A,U,D,C

Only an owner whose desk is one of the APPLICATION-OWNER-DESK-IDs or an analyst whose user ID is an APPLICATION-ANALYST on the APPLICATION file for this Application ID may update/delete the notice Eff Date or text.

Special Processing

Action

Special Processing

A,U,C

Notice text is not translated to upper case on input.

V,U,C,D

When PF4 is pressed, the name of Last Updated By (UPDATED-BY-USER) is retrieved from the USER file and displayed.

Data Base Changes

Data base changes are only performed if all data is valid and PF10 is entered.

Action

Effect on Data Base

A,U,C

The DATE-NOTICE and the NOTICE fields on the APPLICATION file for the Application ID entered are updated with the contents of Eff Date and the notice text. Additional assignments include: DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID, and DATE-OF-ENTRY = current date (for an Add).

D

The existing values for DATE-NOTICE and NOTICE on the APPLICATION file are updated with blanks and zeros respectively. Additional assignments include: DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.


ALR - Application Lock/unlock Reason maintenance

The Application Lock/unlock Reason figure is an example of the Application Lock/unlock and Reason maintenance function, or view an actual image of the ALR screen in a separate window.

Figure: Application Lock/unlock and Reason


All entries are valid, press PF10 to Save
 NSOALR  1           Application Lock/unlock & Reason - ALR      08/30/93 09:43
 Command:      Action: U  Desk:           Appl: DA-GRADS  Cmd Sec Grp:
 Val Sec Grp: AVCF      Parm:
-------------------------------------------------------------------------------
   Action: U   Appl: DA-GRADS  Dev & Alumni - Gift Recording & Dues Sys
   Lock/Unlock:  L
   Reason for locking the application:
 
    Sample explanation of why an application may
 
    be locked up and when it will again become
 
    available.
 
 
 
 
 
     Entered:           Last Updated: 08/17/93
                                  By: WDW
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             NextR       Save

Purpose and Usage

The Application Lock/unlock and Reason maintenance function is used to view or update lock/unlock data associated with a specific existing Natural Application on the APPLICATION file. The reason text should contain an estimated date/time for the application to be unlocked. The permitted Action codes are: V or U, respectively. Values for Application ID and Action are always required.

To update, replace the desired fields with valid values. To view, only the desired Application ID is necessary. PF10 is required to confirm and effect any change.

The remaining sections address:

"Field Validations"
"Special Processing"
"Data Base Changes"

Field Validations

Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

V,U

Application ID must exist on the APPLICATION file.

U

The desk of the operator must be a valid APPLICATION-OWNER-DESK-ID or the operator's user ID must be an APPLICATION-ANALYST on the APPLICATION file for this Application ID.

U

If Lock/unlock is 'L', the Reason for locking the application cannot be blank.

U

If Lock/unlock is 'U' the REASON-APPLICATION-LOCKED will be blanked on update to the APPLICATION file for the Application ID.

Special Processing

Action

Special Processing

U

The Reason for locking the application text is not translated to upper case on input.

V,U

When PF4 is pressed, the name of Last Updated By (UPDATED-BY-USER) is retrieved from the USER file and displayed.

Data Base Changes

Data base changes are only performed if all data is valid and PF10 is entered.

Action

Effect on Data Base

U

If Lock/unlock is 'L' the APPLICATION-LOCKED and REASON-APPLICATION-LOCKED fields are updated on the APPLICATION file with Lock/unlock and 'Reason' text for the Application ID. If Lock/unlock is 'U' the APPLICATION-LOCKED field is updated with 'U' and the REASON-APPLICATION-LOCKED field is updated with blanks on the APPLICATION file for the Application ID. The corresponding logical field are always updated DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.


CSLR - Command Security group Lock/unlock and Reason

The Command Security group Lock/unlock and Reason figure is an example of the Command Security group Lock/unlock and Reason function, or view an actual image of the CSLR screen in a separate window.

Figure: Command Security group Lock/unlock and Reason


Specified key does not exist; make changes and press ENTER to validate
 NSOCSLR 1       Cmd Security group Lock/unlock & Reason - CSLR  08/30/93 09:44
 Command:      Action: U  Desk:           Appl: DA-GRADS  Cmd Sec Grp:
 Val Sec Grp: AVCF      Parm:
-------------------------------------------------------------------------------
   Action: U   Appl: DA-GRADS   Dev & Alumni - Gift Recording & Dues Sys
 
         Cmd-Sec-Grp  Lock/Unlock     Cmd-Sec-Grp  Lock/Unlock
          ALL              U
          ALLTBL           U
          NOMAD            l
 
 
 
          Reason Command Security Groups Locked:
          Sample of locking one command security group
          out of an application.
 
 
 
 
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit        RStrt UnLok                   Save

Purpose and Usage

The Command Security group Lock/unlock and Reason function is used to view or update information about Natural Applications' Command Security Groups lock/unlock status and reason for the lock. This information is contained on the COMMAND-SECURITY file and APPLICATION file respectively for an Application ID. The permitted Action codes are: V or U, respectively. A value for Application ID is always required.

To update, replace the desired fields with valid values. To view, only the desired Application ID is necessary. A maximum of 10 Cmd Sec Grps are displayed on a screen, and PF8 can be used to scroll through the Cmd Sec Grps for the specified Application Id. PF10 is required to confirm and effect any change.

The remaining sections address:

"Field Validations"
"Special Processing"
"Data Base Changes"

Field Validations

Invalid entries will result in an error and must be corrected before any data base change is allowed.

Action

Validation

V,U

Application ID must exist on the COMMAND-SECURITY file.

V,U

Cmd Sec Grp, if entered in the command-key area and if it exists on the COMMAND-SECURITY file for this Application ID, will be the first of the ten Cmd Sec Grps listed to be locked or Unlocked. If the Cmd Sec Grp entered does not exist, the first ten existing COMMAND-SECURITY-GROUPS within the Application ID after the specified Cmd Sec Grp will be listed.

V,U

At least one COMMAND-SECURITY-GROUP must exist for this Application Id on the COMMAND-SECURITY file.

U

The desk of the operator must be an APPLICATION-OWNER-DESK-ID on the APPLICATION file for this Application.

U

Lock/Unlock is a required field and must be L or U for all listed Cmd Sec Grps.

U

Reason Command Security Groups Locked text is required.

Special Processing

Action

Special Processing

U

Reason Command Security Groups Locked text is not translated to upper case on input.

U

When PF6 is pressed, all the Cmd Sec Grps will be assigned an Unlock status.

U,V

Cmd Sec Grps will be displayed in groups of ten starting with the first COMMAND-SECURITY-GROUP within the Application ID or the Cmd Sec Grp entered. Pressing PF8 will page forward through the Cmd Sec Grps.

Data Base Changes

Data base changes are only performed if all data is valid and PF10 is entered.

Action

Effect on Data Base

U

The existing records on the COMMAND-SECURITY file for the Application Id and Cmd Sec Grps are updated with the corresponding COMMAND-GROUP-LOCK = Lock/Unlock.

The existing record on the APPLICATION file for the Application ID is updated with REASON-CSG-LOCKED = Reason Command Security Groups Locked text.

The COMMAND-SECURITY file is updated with the corresponding logical field assignments: DATE-LAST-UPDATED = current date and LAST-UPDATED-BY = current Natural user ID.


LUA - List Users of an Application

The following sections document the List Users of an Application function:

"Purpose"
"Key fields"
"Decode processing"
"Related topics"

The List Users of an Application figure is an example of the List Users of an Application function, or view an actual image of the LUA screen in a separate window.

Figure: List Users of an Application


Select an entry, press PF8 to page forward, or enter new keys
 NSOLUA  1             List Users of an Application - LUA        08/30/93 09:45
 Command:      Action: U  Desk:           Appl: GJIM      Cmd Sec Grp:
 Val Sec Grp: AVCF      Parm:           User:
-------------------------------------------------------------------------------
  List for Appl: GJIM     starting from
 
 
         User        LastLogon   Name                               BUNIT
       _ AP001                   Lester, Tina                       AVCF
       _ AP04                    Omohundro, Doris                   AVCF
       _ AVCF001     08/19/93    Briney, Colleen                    AVCF
       _ AVCF002     05/21/93    Danley, Lisa                       AVCF
       _ AVCF01      06/29/93    Stolfi, Larrie                     AVCF
       _ AVCF02      08/18/93    Bronaugh, Jim                      AVCF
       _ AVCF07      08/13/93    Shaw, Phyllis                      AVCF
       _ BKENNED     07/28/93    Kennedy, Bobbie                    AVCF
       _ BMOODY                  Moody, Bill                        CAUD
       _ BROMLEY     08/12/93    Bromley, Katrina                   COMP
 
                    Users 1     thru 10    displayed
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             Forwd

Purpose

The List Users of an Application function is used to display users of an application, anyone that has ever logged onto the application. These users are listed in sets of ten and include the user ID and the date of the last logon to the application. Use PF8 to scroll forward through the list of users. The display near the bottom of the screen indicates which set of users is displayed and the total number of users. PF5 will restart the list with the first set of users. User IDs may be marked for selection and further processing.

Users are created through the User maintenance (U) function.

Key fields

Application ID Identifies the application for which the list is generated. A list of valid application IDs may be obtained by pressing PF1 (Help) while the cursor is on this field.
User ID User ID is used as a starting search value such that all users with an ID equal to or greater than that value are listed. A blank ID will obtain a complete list of the users of the application. A list of assigned User IDs displayed in user name order may be obtained by pressing PF1 (Help) while the cursor is on this field.

Decode processing

PF4 is used to decode all entries in the list. To obtain the user name and the budgetary unit to which the ID is assigned, press PF4.

Related topics


LDC - List Desks for a Command security group

The following sections document the List Desks for an Command security group function:

"Purpose"
"Key fields"
"Decode processing"
"Related topics"

The List Desks for a Command security group figure is an example of the List Desks for a Command security group function, or view an actual image of the LDC screen in a separate window.

Figure: List Desks for a Command security group


Select an entry, press PF8 to page forward, or enter new keys
  Desk name and BUNIT decoded                               LDC  07/28/94 10:16
 Command:      Action: V  Desk:           Appl: LEAVE     Cmd Sec Grp: ALL
 Val Sec Grp:           Parm:
-------------------------------------------------------------------------------
  Appl: LEAVE    Cmd Sec Grp: ALL      Allow access to all commands
 
              Sec  Value
     Desk     Lvl Sec Grp   Desk Name                                 BU
   _ ARGUS     9  COMP      Converted for Katrina Bromley             COMP
   _ AUSTER    9  LVADMIN   Converted for Joy Steely                  COMP
   _ CHAOS     9  COMP      Converted for W. David Wimberly           COMP
   _ AVERNUS   9  COMP      Converted for Kathryn Cantrell            COMP
   _ ATLAS     9  COMP      Don Barnett                               COMP
   _ COCYTHUS  9  LVADMIN   Converted for Bill Overby                 HMRS
   _ BRIAREUS  9  COMP      Converted for Paul Bixby                  COMP
   _ CEPHALUS  9  COMP      Converted for Sandra Twiggs               COMP
   _ ARACHNE   9  COMP      Converted for Ava Findahl                 COMP
   _ FSTC      9  LVADMIN   Financial Systems Training Coordinator    AVCF
 
             Desks 1     thru 10    of 12    displayed
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             Forwd

Purpose

The List Desks for a Command security group function is used to display desks with a given command security group for the specified application. These desks are listed in sets of ten and include the desk ID, security level, and value security group. Use PF8 to scroll forward through the list of desks. The display near the bottom of the screen indicates which set of desks is displayed and the total number of desks. PF5 will restart the list with the first set of desks. Desk IDs may be marked for selection and further processing.

Desks are granted access to applications through the Application-Desk (AD) function.

Key fields

Application ID Identifies the application for which the list is generated. A list of valid application IDs may be obtained by pressing PF1 (Help) while the cursor is on this field.
Command Security Group Identifies the command security group of the specified application for which the list is generated.

Decode processing

PF4 is used to decode all entries in the list. To obtain the desk name and the budgetary unit associated with the desk, press PF4.

Related topics


LDV - List Desks for a Value security group

The following sections document the List Desks for an Value security group function:

"Purpose"
"Key fields"
"Decode processing"
"Related topics"

The List Desks for a Value security group figure is an example of the List Desks for a Value security group function, or view an actual image of the LDV screen in a separate window.

Figure: List Desks for a Value security group


Select an entry or enter new keys
 NSOLDV  1         List Desks for a Value security group - LDV   08/30/93 09:47
 Command:      Action: U  Desk:           Appl: NSM-MS    Cmd Sec Grp: CORETEAM
 Val Sec Grp: AVCF      Parm:
-------------------------------------------------------------------------------
  Appl: NSM-MS   Val Sec Grp: AVCF     Financial Affairs
 
              Sec   Cmd
     Desk     Lvl Sec Grp   Desk Name                                 BUNIT
   _ FSTC      7  AA+DM     Financial Systems Training Coordinator    AVCF
 
 
 
 
 
 
 
 
 
 
             Desks 1     thru 1     of 1     displayed
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt

Purpose

The List Desks for a Value security group function is used to display desks with a given value security group for the specified application. These desks are listed in sets of ten and include the desk ID, security level, and command security group. Use PF8 to scroll forward through the list of desks. The display near the bottom of the screen indicates which set of desks is displayed and the total number of desks. PF5 will restart the list with the first set of desks. Desk IDs may be marked for selection and further processing.

Desks are granted access to applications through the Application-Desk (AD) function.

Key fields

Application ID Identifies the application for which the list is generated. A list of valid application IDs may be obtained by pressing PF1 (Help) while the cursor is on this field.
Value Security Group Identifies the value security group of the specified application for which the list is generated.

Decode processing

PF4 is used to decode all entries in the list. To obtain the desk name and the budgetary unit associated with the desk, press PF4.

Related topics


LDA - List Desks for an Application

The following sections document the List Desks for an Application function:

"Purpose"
"Key fields"
"Related topics"

The List Desks for an Application figure is an example of the List Desks for an Application function, or view an actual image of the LDA screen in a separate window.

Figure: List Desks for an Application


Select an entry, press PF8 to page forward, or enter new keys
 NSOLDA  1             List Desks for an Application - LDA       08/30/93 09:48
 Command:      Action: U  Desk:           Appl: GJIM      Cmd Sec Grp: CORETEAM
 Val Sec Grp: AVCF      Parm:
-------------------------------------------------------------------------------
  List for Appl: GJIM     starting from
 
            Sec  Value      Cmd
   Desk ID  Lvl Sec Grp   Sec Grp   Desk Name                             BUNIT
 _ ADONIS    6            CORETEAM  Converted for Craig A. Brown          AVCB
 _ AEACUS    6            CORETEAM  Converted for Donna Carter            AVCB
 _ AEETES    6            CORETEAM  Converted for Daniel Jones            AVCB
 _ AEGEUS    6            CORETEAM  Converted for William Rains           AVCB
 _ AEGYPTUS  6            CORETEAM  Converted for Tina Lester             AVCF
 _ AEOLUS    6            CORETEAM  Converted for Doris Omohundro         AVCF
 _ AESON     6            CORETEAM  Converted for Colleen Briney          AVCF
 _ AETHER    6            CORETEAM  Converted for Lisa Danley             AVCF
 _ AGIAIA    6            CORETEAM  Converted for Larrie Stolfi           AVCF
 _ AJAX      6            CORETEAM  Converted for Jim Bronaugh            AVCF
 
                    Desks 1     thru 10    displayed
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             Forwd

Purpose

The List Desks for an Application function is used to display desks that have been granted access to an application. These desks are listed in sets of ten and include the desk ID, desk name, and the desk's budgetary unit. Use PF8 to scroll forward through the list of desks. The display near the bottom of the screen indicates which set of desks is displayed and the total number of desks. PF5 will restart the list with the first set of desks. Desk IDs may be marked for selection and further processing.

Desks are granted access to applications through the Application-Desk (AD) function.

Key fields

Desk ID Desk ID is used as a starting value. A list of assigned Desk IDs displayed in user name order may be obtained by pressing PF1 (Help) while the cursor is on this field.
Application ID Identifies the application for which the list is generated. A list of valid application IDs may be obtained by pressing PF1 (Help) while the cursor is on this field.

Related topics


LAO - List Applications of an Owner

The following sections document the List Applications of an Owner function:

"Purpose"
"Key fields"
"Decode processing"
"Related topics"

The List Applications of an Owner figure is an example of the List Applications of an Owner function, or view an actual image of the LAO screen in a separate window.

Figure: List Applications of an Owner


Select an entry, press PF8 to page forward, or enter new keys
 NSOLAO  1          List Applications of an Owner desk - LAO     01/12/94 09:49
 Command:      Action: U  Desk: CHAOS     Appl: C         Cmd Sec Grp:
 Val Sec Grp:           Parm:
-------------------------------------------------------------------------------
   List for Desk: CHAOS     Converted for W. David Wimberly
              starting from Appl: C
 
             Application ID   Application Name
              _ DA-GRADS      Dev & Alumni - Gift Recording & Dues Sys
              _ DA-JOBS       Batch job library for DA-GRADS
              _ DA-RPTS       Dev/Alumni Report Library
              _ DHYATT        David Hyatt's Library
              _ DW85047       David Wimberly's library
              _ GJIM          General Journal Interface Module
              _ HRLY-TS       Hourly Time Sheets
              _ HRMS          Human Resource Management System
              _ INRS          Institutional Research Application
              _ JOBS          Job Submission Application
 
          Applications 1     thru 10    of 35    are displayed
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode RStrt             Forwd

Purpose

The List Applications of an Owner function is used to display applications for which a given desk is an owner. These applications are listed in sets of ten and include the application ID and name. Use PF8 to scroll forward through the list of applications. The display near the bottom of the screen indicates which set of applications is displayed and the total number of applications. PF5 will restart the list with the first set of applications. Application IDs may be marked for selection and further processing.

Desks are defined as owners of an application through the Application maintenance (A) function.

Key fields

Desk ID Identifies the desk for which the list of applications is to be generated. A list of Desk IDs by user name can be obtained by pressing PF1 (Help) while the cursor is on this field. This list is in sequence of the name of the individual assigned to the desk.
Application ID Application ID is used as a starting search value for the list.

Decode processing

PF4 is used to decode selected entries. To obtain additional information about the application, mark the desired application and press PF4. The application's total number of desks, command security groups, and value security groups and the date of the last notice for the application are displayed in a window.

Related topics


CSQ - Command SeQuence maintenance

The following sections document the Command Sequence function:

"Purpose"
"Key fields"
"Actions"
"Special validations"

The Command Sequence maintenance figure is an example of the Command SeQuence maintenance function, or view an actual image of the CSQ screen in a separate window.

Figure: Command Sequence maintenance


Please enter new key fields
  De-coding has been performed                              CSQ  07/28/94 14:43
 Command:      Action: V  Desk:           Appl: GJIM      Cmd Sec Grp:
 Val Sec Grp:           Parm:           Cmd Seq: TESTACT
-------------------------------------------------------------------------------
 Action: V Appl: GJIM     Command Sequence: TESTACT
 Command Sequence Description: Testing the Action Field
 
                Action  Cmd                 Description
                   V    JEM    Journal Entry Maintenance
                   U    JEM    Journal Entry Maintenance
                   V    JETP   Journal Entry TARGET Processing
                        JEM    Journal Entry Maintenance
 
 
 
 
 
 
 
    Entries   1 thru   4 of   4 displayed; maximum allowed:  10
 
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help  Suspd Quit  DCode                   NextR

Purpose

The Command SeQuence maintenance function is used to create and maintain a series of two or more commands that are used in conjunction with each other to accomplish a particular task. Multiple command sequences are allowed within an application and the commands in those sequences are performed via the List Command SeQuence (LCSQ) function that exists in each application. Normally all commands in a sequence operate on the same banner key (or group of keys). The objective of this function is to prevent repetitive command entry for each new key entered in the banner.

An example of how this function might be used is when data for a particular entity (e.g. Personnel ID, Vendor Number, etc.) is to be maintained and there are multiple functions required to access all of the fields. The entity's banner key is entered one time and then LCSQ is used to access all of the required commands with the indicated action (in the order listed). Upon return to the list a new key is entered in the banner and the sequential execution of commands is repeated. Note that because the commands are sequential executed in LCSQ, it is important that are listed in the order in which they are to be executed.

Key fields

Action Possible values for action include V (View), A (Add), U (Update) and D (Delete). See topic "Actions" for descriptions of these types of processing.
Appl A list of Application IDs can be obtained by pressing PF1 (Help) while the cursor is positioned on this field. This list is in alphabetical order.
Cmd Seq The Command Sequence Name is a unique name given to each command sequence within an application.

Actions

The following actions are possible for this function. Use of some actions may be restricted for some users. No data will be created, modified, or deleted until PF10 is pressed.

View (Display existing Command SeQuences)

To view an existing command list, enter in the banner a 'V' in the Action field and the desired Application ID and Command Sequence Name.

Add (Create new Command SeQuences)

To create a new command sequence, enter in the banner an 'A' in the Action field, the desired Application ID, and the new Command Sequence Name. Enter the command sequence Description and valid Command IDs.

Update (Modify existing Command SeQuences)

To modify an existing command sequence, enter in the banner a 'U' in the Action field, the desired Application ID, and the Command Sequence Name. Modify the command sequence Description and/or enter (or change) Command IDs.

Delete (Delete existing Command SeQuences)

To delete an existing command list, enter in the banner a 'D' in the Action field, the desired Application ID, and the Command Sequence Name.

Special validations

To add, modify, or delete a command list, the Application ID must exist and the operator's desk must be an APPLICATION-OWNER for the application entered. Any desk, however, that has access to the Command SeQuence function may view any command sequence in any application.

A Command Sequence Name must be unique within a given application.


Miscellaneous


Procedures

There are three distinct groups of users for this system, Computing Services,the application administrators, and the departmental desk administrators. The following procedures will be required by each group to use the NSM-MS System.

First, Computing Services will design the online application to conform to the requirements of the NSM Architecture. The functional specifications available for the NSM Architecture provide the necessary information. Also, Computing Services will be responsible for adding and maintaining Users, Applications, and Application Menu Command data on the Natural Secured Menu files via the NSM-MS System. Finally, Computing Services will enforce security within each application command by designing and coding the appropriate restrictions into the function module programs.

Departmental desk administrators will be responsible for defining and maintaining desks under their budgetary unit(s). The assignment of individuals to those desks is also a responsibility of the desk administrator.

Each NSM application administrator will be responsible for establishing and maintaining the security data required by the application via the NSM Maintenance System. This will include establishing and maintaining valid Application-Desks, Command-Security-Groups, and Value-Security-Groups. The owner will be responsibile for maintaining application default access availability and the associated default security definitions for such access. Also, the administrator will be allowed to Lock/Unlock Applications and Command-Security-Groups as well as enter the associated reason/messages. Last, the administrator can maintain an Application-Notice to communicate pertinent information to all Users that logon to their application.


Data Entry Sequence

Data validation requirements within NSM-MS mandate that data be established in a certain order. For example, the application owner (administrator) must exist in the User file before an Application can be added. The list of functions provided below identifies the required sequence for setting up new users in a new application.
U User maintenance
A Application maintenance
M application Menu maintenance
D Desk maintenance
UD User Desk maintenance
CS application Command Security maintenance
VS application Value Security maintenance (optional)
AD Application Desk maintenance
The first three steps must be performed by Computing Services. The next two steps, which deal with desk definition and assignment, must be completed by the departmental desk administrator. The remaining steps are the responsibility of the application administrator (owner).