IGEM Engineering Data Library

....

c , '/

7/\ ; .... v

IGEM Engineering Data Library

Data Base Administrator's Manual <52>

CONTR.OL DATA

60458880

(

c

(

(

c c

leEM

ENGINEERING DATA LIBRARY

DATA BASE ADMINISTRATOR'S MANUAL

This product is intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features and parameters.

Publication Number 60458880

MANUAL HISTORY

Revision F documents ICEM EDL Version 1.2.3, printed October 1985. This edition obsoletes all previous editions.

Previous Product

Revision Level Date

A 1.0 May 1982

B 1.1 November 1983

C 1.1 January 1984

D 1.13 June 1984

E 1.2 February 1985

@ 1982, 1983, 1984, 1985 by Control Data Corporation All rights reserved

Printed in the United States of America

2

- - - " ----~---.-.-~-~~-'-_r-' -

60458880 F

(

(

(

(

c c

I

I

CONTENTS

About This Manual ••••••••••••••••••••••••••• 5 Audience •••••••••••••••••••••••••••••••• 5 Organization •••••••••••••••••••••••••••• 6 Conventions •••••••••••••••••••••••••••••

o

Related Publications •••••••••••••••••••• 7 Equipment Required •••••••••••••••••••••• 8 Ordering Manuals •••••••••••••••••••••••• 8 Submitting Comments ••••••••••••••••••••• 8

EDL and the DBA's Customizing

Functions ••••••••••••••••••••••••••••••• l-l Introduction •••••••••••••••••••••••••• l-l The DBA's Tools to Customize EDL •••••• 1-3

Summary of the DBA's Responsibilities ••••• 2-1

EDL Conventions Review •••••••••••••••••••• 3-1 Tasks ••••••••••••••••••••••••••••••••• 3-1 Kinds of Menus •••••••••••••••••••••••• 3-1 Menu Selections ••••••••••••••••••••••• 3-7 Menu Queuing (Type-Ahead) ••••••••••••• 3-8 Dialog Delimiters ••••••••••••••••••••• 3-8 String Delimiters ••••••••••••••••••••• 3-8 Menu Display •••••••••••••••••••••••••• 3-9 Field Length on Prompts •••••••••••••• 3-10 Online Help •••••••••••••••••••••••••• 3-10

Updating the Message and Task Data

Base •••••••••••••••••••••••••••••••••••• 4-1 Applying Transaction Data ••••••••••••• 4-1 Task Security ••••••••••••••••••••••••• 4-1 Transaction Record Format ••••••••••••• 4-2 Examples •••••••••••••••••••••••••••••• 4-8

User Management Task •••••••••••••••••••••• 5-1 List Users •••••••••••••••••••••••••••• 5-2 Add Users ••••••••••••••••••••••••••••• 5- 3 Delete Users •••••••••••••••••••••••••• 5-8 Change a User Profile •••••••••••••••• 5-13 Reactivate a User •••••••••••••••••••• 5-17

60458880 F

Group Administration Task ••••••••••••••••• 6-1 List Groups ••••••••••••••••••••••••••• 6-2 Group Management •••••••••••••••••••••• 6-3 Member Management ••••••••••••••••••••• 6-6 Task Access Management •••••••••••••••• 6-1

Release Administration Task ••••••••••••••• l-l List Release Procedures ••••••••••••••• l-l Add Release Procedures •••••••••••••••• 7-l Delete Release Procedures ••••••••••••• 1-3 Manage Releasers •••••••••••••••••••••• 7-4 Manage Reviewers •••••••••••••••••••••• 7-7

Part, Family, and Vendor Management

Task •••••••••••••••••••••••••••••••••••• 8-1 Part Number Management •••••••••••••••• 8-1 Family Management ••••••••••••••••••••• ~-5

Part Family Relationship

Management •••••••••••••••••••••••••• 8-7 Vendor Management •••••••••••••••••••• 8-10 Part Vendor Relationship

Management ••••••••••••••••••••••••• 8-13

GLOSSARY •••••••••••••••••••••••••••••••••• A-l

ERROR MESSAGES •••••••••••••••••••••••••••• B-l

INDEX ••••••••••••••••••••••••••••••••• lndex-l

3

FIGURES

1-1 Design Packages Managed by EDL ••••••• l-l 1-2 Summary of the DBA's Tools ••••••••••• 1-5 1-3 System Administrator Tasks and

Secondary Menus •••••••••••••••••••• 1-6

1-4 Local Administrator Tasks and

Secondary Menus •••••••••••••••••••• 1-7

TABLES

5-1

1

^{5-2 5-3}

4

Prompts for the ADD USERS

Option •••••••••••••••.••••••••••••• 5-5 Prompts for the DELETE INFORMATION

ABOUT THEIR FILES Option •••••••••• 5-10 Prompts for the TRANSFER OWNERSHIP

OF THEIR FILES Option ••••••••••••• 5-12

5-4 Prompts for the CHANGE A USER'S

PROFILE Option •••••••••••••••••••• 5-15

1

5-5 Prompt for the REACTIVATE A

USER Option ••••••••••••••••••••••• 5-17 6-1 Prompts for the ADD GROUPS

Option ••••••••••••••••••••••••••••• b-4

60458880 F

(

(

c c

ABOUT THIS MANUAL

The CONTROL DATA®Integrated Computer-Aided Engineering and Manufacturing (ICEM) Engineering Data Library (EDL) is a data base for the storage and security of engineering designs. EDL maintains information on all types of engineering data: mechanical drawings, solid models,

finite element (FE) models, and electronic circuit models.

In addition to the storage and retrieval functions, EDL facilitates entry into the

computer-aided design (CAD) packages needed to create designs: CDC®ICEM Design/Drafting/

Numerical Control, the CDC ICEM Solid Modeler, and CDC UNISTRUC II can all be accessed through EDL.

The EDL functions are described in the Engineering Data Library Version 1 Reference Manual.

It is the EDL data base administrator's (DBA's) job to ensure the best use of these functions. This manual discusses the DBA's functions.

AUDIENCE

This reference manual describes how the DBA can tailor EDL to the needs of an individual design group.

You can divide the job of the data base administrator into two jobs: system administrator and local administrator. The system administrator's duties would be to update the task and option menus, prompts, and messages that EDL produces. The local administrator's duties would be to allow users access to EDL, assign users to groups, assign and control release and review procedures, and control part numbers, part families, vendors, and their

relationship to each other.

The CDC Network Operating System (NOS) controls EDL; therefore, the system administrator must be familiar with NOS interactive commands and NOS procedures. The Query Update program must be used to customize EDL for a particular site, so it is assumed that the system

administrator is familiar with Query Update. The NOS login procedure and instructions are found in the NOS Version 2 Reference Set, Volume 1, Introduction to Interactive Usage. NOS procedures are described in the NOS Version 2 Reference Set, Volume 3, System Commands.

Query Update is described in the DMS-170 Query Update Version 3 Reference Manual.

60458880 E 5

ORGANIZA TION

This manual is organized into three introductory chapters and five chapters that explain the DBA's menu options in the order that they appear.

• EDL and the DBA's Customizing Functions (chapter 1)

Reviews the major EDL features and introduces the DBA's tools.

• Summary of the DBA's Responsibilities (chapter 2)

Introduces the DBA's responsibilities and explains the EDL initiation procedures.

• EDL Conventions Review (chapter 3)

Reviews EDL standard conventions for the use of delimiters, menus, and online help.

• Updating the Message and Task Data Base (chapter 4)

Describes the menu for creating, changing, and deleting EDL menus and messages.

• User Management Task (chapter 5)

Discusses initiating a new EDL user and modifying EDL's record of a user.

• Group Administration Task (chapter 6)

Describes the menu for creating groups, assigning users to groups, and assigning task security categories to groups.

• Release Administration Task (chapter 7)

Describes the menu for controlling release procedures, reviewers, and releasers.

• Part, Family, and Vendor Management Task (chapter 8)

Describes the functions that allow the local administrator to edit information on parts, families, or vendors.

CONVENTIONS

All text that the system displays in menus or prompts is shown in uppercase letters.

Examples of text that the user enters are shown in lowercase letters. Both are printed in a typeface that simulates computer output. For example:

ENTER THE EDL ID FOR THE NEW USER OR CR TO EXIT

? jane

In all examples, a blank line following a question mark indicates a carriage return.

I

New features, as well as changes, deletions, additions to information in this manual, are indicated by bars in the margins or by a dot near the page number if the entire page is affected. A bar by the page number indicates pagination rather than content has changed.

6 60458880 F

( (

^, . . - P ^{:: .}

(

(

(;

~

RELA lED PUBLICA liONS

The following manuals contain information that is related to the EDL applications described in this manual.

Manual Title Publication Number

DMS-170 DDL Reference Manual Version 3, Volume 3

(Query Update Subschema Definition) 60482100

DMS-170 Query Update Version 3 Programming User's Guide 60499000 DMS-170 Query Update Version 3 Reference Manual 60498300

DMS-170 Query Update Version 3 User's Guide 60387700

Engineering Data Library (EDL) Version 1 Reference Manual 60459740

ICEM Advanced Design 60461430

ICEM DDN Instant 60457140

ICEM Design/Drafting Basic Construction 60461420

ICEM Design/Drafting Data Management 60461410

ICEM Design/Drafting Drafting Functions 60461440

ICEM Design/Drafting GRAPL Programming Language 60461460

ICEM Design/Drafting Introduction and System Controls 60457130

ICEM Design/Drafting User's Guide 60459660

ICEM GPL 60462520

ICEM Numerical Control 60461450

ICEM Schematics Reference Manual 60456540

ICEM Solid Modeler Reference Manual 60460530

ICEM Reference Manual 60463050

NOS Full Screen Editor User's Guide 60460420

NOS Version 2 Reference Set, Volume 1, Introduction to Interactive Usage 60459660 NOS Version 2 Reference Set, Volume 3, System Commands 60459680

PATRAN Reference Manual, Volume 1 60459330

PATRAN Reference Manual, Volume 2 60459340

UNIPLOT Version 3.2 User's Guide/Reference Manual 84003490

UNISTRUC II User's Guide 60457550

XED IT Version 3 Reference Manual 60455730

60458880 F 7

I

I

I

I

EQUIPMENT REQUIRED

Any alphanumeric terminal can be used for EDL. Extended terminal capabilities, such as graphics. are needed only if you access an application that requires them (for example, the lCEK Solid Modeler application requires a graphics capability).

ORDERING MANUALS

Control Data manuals are available through Control Data sales offices or through:

Control Data Corporation

Literature Distribution Services 308 North Dale Street

St. Paul, Minnesota 55103

SUBMITTING COMMENTS

The last page of this manual is a comment sheet. Please use it to give us your opinion of the manual's usability, to suggest specific improvements, and to report any errors. If the comment sheet has already been used. you can mail your comments to:

Control Data Corporation

Publications and Graphics Division ARH219 4201 Lexington Avenue North

St. Paul, Minnesota 55126-6198

Please indicate whether you would like a written response.

8 60458880 F

~

^{~ jj}

I

~.

=

o o

o

o

o

o

EDL AND THE DBA'S CUSTOMIZING FUNCTIONS

Introduction •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 1-1 The DBA's Tools to Customize EDL •••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 1-3

1

__ = ...

4,*=:.1"*" H§9iL;;.~ 4A#¢0tt:

o o

o o

o

o o

(

(

(

C

(,

EDL AND THE DBA'S CUSTOMIZING FUNCTIONS 1

INTRODUCTION

Control Data's shared data base for drawing, storing, and managing engineering designs is called the ICEM Engineering Data Library (EDL). ICEM EDL, like a standard library, is a base for sharing and managing information. The shared information is the part geometry that designers can retrieve. The managed information is the series of design packages available through ICEM EDL. These design packages (see figure 1-1) are:

• ICEM Design/Drafting/Numerical Control (ICEM DDN) for automated design and drafting.

ICEM DDN was formerly called CD/2000.

•

ICEM Solid Modeler for three-dimensional design.

• UNISTRUC II for finite element (FE) modeling.

•

PATRAN for finite element (FE) modeling with color postprocessing capabilities.

•

ICEM Schematics for drawing schematics of electrical circuits.

•

UNIPLOT for plotting data.

DESIGN

• DESIGN AND MANUFACTURING

MANUFACTURING

• DESIGN SUPPORT

Figure 1-1. Design Packages Managed by EDL

60458880 F 1-1

I

I

I

I

I

ICEM EDL loads the design packages into the designer's workspace and allows the designer to create, store, and secure the part in his/her user name. If people in other departments need to share the part geometry, the designer can make the part individually or universally available. After completing the design work and exiting the design package, the designer returns to EDL, and the design information is updated.

Following are more detailed descriptions of the design packages.

Design Package ICEM DDN

ICEM Solid Modeler

UNISTRUC II

PATRAN

ICEM Schematics

UNIPLOT

Description

Provides a CAD package for creating two-dimensional and

three-dimensional engineering designs. This is an automated method for designing, correctly dimensioning, and analyzing a mechanical drawing.

Provides a CAD package for designing and viewing three-dimensional models. It transforms a design idea into a detailed solid model.

Once designed, the solid model can be viewed from many angles.

Creates FE models of designs described to it. It generates the data needed to structurally analyze the model with the STARDYNE, NASTRAN, or ANSYS programs. When structural analysis is complete,

UNISTRUC II graphically displays the results.

Creates FE models of designs described to it. It generates the data needed to structurally analyze the model with the ABAQUS and

MSC/NASTRAN programs. When structural analysis is complete, PATRAN graphically displays the results, optionally in color.

Provides a CAD package for creating electrical and logical schematics drawings from a graphics terminal.

Provides neutral picture subroutines that application programs can use as a plotting subsystem and a device-dependent postprocessor.

For brevity, ICEM EDL is called EDL throughout the rest of the manual.

1-2 60458880 F

\1. jJ

(

(

(

c

(C

THE DBA'S TOOLS TO CUSTOMIZE EDL

The shared data base features of EDL are discussed in detail in the EDL Reference Manual.

The primary concern of this manual is to describe how you, the data base administrator, can change those features to tailor EDL to the needs of users at your site.

As described earlier, you can divide the job of the data base administrator into two jobs:

system administrator and local administrator.

The system administrator's duties are associated with the tasks in the System Administrator Tasks menu, shown next. Access this menu by using the command SYSADMIN.

SYSTEM ADMINISTRATOR TASKS 1. EXIT

2.

UPDATE THE MESSAGE AND TASK DATABASE

3.

UPDATE THE DATABASE WITH BATCH QU INPUT

4.

INTERACTIVE QUERY UPDATE

ENTER TASK

E,EXIT MENUMGMT QUBATCH QU

The following summary describes the individual tasks on the System Administrator Tasks menu:

Task Name EXIT

UPDATE THE MESSAGE AND TASK DATABASE

UPDATE THE DATABASE WITH BATCH QU INPUT

INTERACTIVE QUERY UPDATE

60458880 F

Function

Terminates EDL processing of the current task and returns control to the previous task.

Allows you to customize tasks and messages. Chapter 4 discusses this task.

Allows you to update the application data base with Query Update in batch mode.

Allows you to update the application data base with Query Update interactively.

1-3

•

The local administrator's tasks are associated with the Administrator Tasks menu, shown next. Access this menu by using the command ADMIN.

ADMINISTRATOR TASKS 1. EXIT

2. USER MANAGEMENT 3. GROUP ADMINISTRATION 4. RELEASE ADMINISTRATION

5. PART, FAMILY, AND VENDOR MANAGEMENT

E,EXIT USERMGMT GROUPADMIN RELADMIN PARTM

The following summary describes the individual tasks on the Administrator Tasks menu:

1-4

Task Name EXIT

USER MANAGEMENT

GROUP ADMINISTRATION

RELEASE ADMINISTRATION

PART, FAMILY, AND VENDOR MANAGEMENT

Function

Terminates task processing and returns control to the previous task.

Allows you to list all users and all information about selected users, add new users, delete users, modify user's profiles, and reactivate users. Refer to chapter 5 for more information.

Allows you to define and delete groups, change group information, add or delete group members, and allow or deny group access to task categories. Refer to chapter 6 for more information.

Allows you to list existing release procedures, add or delete release procedures, and add reviewers and releasers to or delete them from release procedures.

Refer to chapter

7

for more information.

Allows you to add or delete part numbers, family codes, and vendors, and to add or delete part/family and part/vendor relationships. Refer to chapter 8 for more information.

60458880 E

(~­

c

(,c

(

c

(~

Figure 1-2 summarizes these tools.

MANAGEMENT OF GROUPS

OF USERS

CONTROL OVER

DESIGN RELEASE ... I---I~

MANAGEMENT OVER EDL SECURITY

INITIATION OF NEW USERS

CONTROL OVER MESSAGES AND

PROMPTS

CREATION OF NEW MENUS

Figure 1-2. Summary of the DBA's Tools

Figure 1-3 is a map of the System Administrator Tasks menu and the secondary menus that appear when you select one of the tasks in the main menu.

Figure 1-4 is a map of the Local Administrator Tasks menu and the secondary menus that appear when you select one of the tasks in the main menu.

60458880 E 1-5

SYSTEM ADMINISTRATOR TASKS

1. EXIT E,EXIT

F 2. UPDATE THE MESSAGE AND TASK DATABASE MENUMGMT

~3.

UPDATE THE DATABASE WITH BATCH QU INPUT QUBATCH

4. INTERACTIVE QUERY UPDATE

Q~

SELECT DATA RETRIEVAL METHOD QUERY UPDATE 3.4

1.

EXIT E,EXIT (interactive Query Update prompts)

2.

DATA NAME N,NAME

3.

CREATOR OF THE DATA C,CREATOR

4.

DATA TITLE KEYWORD T,TITLE

5.

DESCRIPTOR D,DESCRIPTOR

6.

STATUS S,STATUS

7.

ENGINEERING CATEGORY CAT

8.

APPLICATION DATA TYPE ADT

•

^9.

FILE INFORMATION F,FILE

10.

OWNER OF THE FILE O,OWNER

rr

^11•

PART INFORMATION P,PART

DATES DATES

[12.

SELECT PART INFORMATION TYPE +

1.

EXIT E,EXIT

2.

PART NUMBER N,NUMBER

3.

PART FAMILY F,FAMILY

4.

PART VENDOR V, VENDOR

5.

PART TITLE KEYWORD T,TITLE

SELECT DATE INFORMATION TYPE

1.

EXIT E,EXIT

2.

CREATION DATE C,CREATION

3

DATE LAST MODIFIED M,MODIFY

4.

DATE LAST ACCESSED A,ACCESS

5.

RELEASE DATE R,RELEASE

Figure 1-3. System Administrator Tasks and Secondary Menus

1-6 60458880 F

( (--

(

(

r

~

60458880 E -

ADMINISTRATOR TASKS 1. EXIT

r - - - 2. USER MANAGEMENT

~3. GROUP ADMINISTRATION

1.

2.

3.

5.

6.

[ 4.

USER MANAGEMENT EXIT

LIST USERS ADD USERS DELETE USERS

CHANGE A USER'S PROFILE REACTIVATE A USER

DELETE USERS 1. EXIT

2. DELETE INFORMATION ABOUT THEIR FILES 3. TRANSFER OWNERSHIP OF THEIR FILES

GROUP ADMINISTRATION

t

1. EXIT

2. LIST GROUPS

r-- 3. GROUP MANAGEMENT

r-~ 4. MEMBER MANAGEMENT

r----_{I -}5. TASK ACCESS MANAGEMENT

~ GROUP MANAGEMENT 1. EXIT

2. LIST ALL INFORMATION ABOUT A GROUP 3. ADD GROUPS

4. DELETE GROUPS

5. GHANGE GROUP INFORMATION

L...,.- MEMBER MANAGEMENT

1. EXIT

2. LIST GROUP MEMBERS 3. ADD G ROUP MEMBERS 4. DELETE GROUP MEMBERS

~ TASK ACCESS MANAGEMENT 1. EXIT

2. LIST AUTHORIZED TASK CATEGORIES 3. ALLOW ACCESS TO TASK CATEGORIES 4. REMOVE ACCESS TO TASK CATEGORIES

E ,EXIT L,LIST A ,ADD D,DELETE C,CHANGE R, REACTIVATE

E,EXIT N,NOTRANS T, TRANS

E ,EXIT LISTGROUPS GROUPMGMT GROUPMEM GROUP TASKS

E,EXIT L,LIST A,ADD D,DELETE C,CHANGE

E,EXIT L,LIST A,ADD D,DELETE

E,EXIT L,LIST A ,ALLOW R,REMOVE

4. RELEASE ADMINISTRATION

5. PART, FAMILY AND VENDOR MANAGEMENT RELEASE ADMINISTRATION

t

1. EXIT

2. LI ST RELEASE PROCEDURES 3. ADD RELEASE PROCEDURES 4. DELETE RELEASE PROCEDURES ,--5. MANAGE RELEASERS

. - 1 - -6. MANAGE REV IEWERS

Y- MANAGE RELEASERS 1 • EXIT

2. LI ST RELEASERS 3. ADD RELEASERS 4. DELETE RELEASERS

~ MANAGE REVIEWERS 1. EXIT

2. LIST REVIEWERS 3. ADD RE V IE WERS 4. DELETE REV IEWERS

E,EXIT USERMGMT GROUPADMIN RELADMIN=

PARTM----~---+---~l

E,EXIT L,LIST A ,ADD D ,DELETE REL ,RELEASERS REV, REVIEWERS

E,EXIT L,LIST A,ADD D,DELETE

E,EXIT L, LIST A ,ADD D,DELETE

PART, FAMILY AND VENDOR MANAGEMENT 1. EXIT

- 2. PART NUMBER MANAGEMENT - - 3. FAMILY MANAGEMENT

r-++--- 4. PART FAMILY RELATIONSHIP MANAGEMENT r+-+-+- 5. V ENDOR MANAGEMENT

...+-+-1-+- 6. PART VENDOR RELATIONSHIP MANAGEMENT

PART NUMBER MANAGEMENT 1. EXIT

2. ADD PART NUMBERS 3. DELETE PART NUMBERS 4. CHANGE PART NUMBER TITLES

~ FAMILY MANAGEMENT l . EXIT

2. ADD FAMILY CODES 3. DELETE FAMILY CODES 4. CHANGE FAMILY NAMES

PART FAMILY RELATIONSHIP MANAGEMENT 1. EXIT

2. ADD PART FAMILY RELATIONSHIPS 3. DELETE PART FAMILY RELATIONSHIPS

[4.

LIST PART FAMILY RELATIONSHIPS PART FAMILY RELATIONSHIP L:ST 1. EXIT

2. LIST "BY P ART NUMBERS 3. LIST BY FAMILY CODES

VENDOR MANAGEMENT 1. EXIT

2. ADD V ENDOR CODES 3. DELETE VENDOR CODES 4. CHANGE VENDOR INFORMATION

PART VENDOR RELATIONSHIP MANAGEMENT 1. EXIT

2. ADD PART VENDOR RELATIONSHIPS 3. DELETE PART VENDOR RELATIONSHIPS

[4.

LIST PART VENDOR RELATIONSHIPS PART VENDOR RELATIONSHIP LIST 1. EXIT

2. LIST BY PART NUMBERS 3. LIST BY VENDOR CODES

Figure 1-4. Local Administrator Tasks and Secondary Menus

E,EXIT PART FAMILY PARTF VENDOR PARTV

E,EXIT A,ADD D,DELETE C,CHANGE

E,EXIT A,ADD D,DELETE C,CHANGE

E,EXIT A,ADD D,DELETE L,LIST

E,EXIT P,PART F ,FAMILY

E,EXIT A,ADD D,DELETE C,CHANGE

E,EXIT A,ADD D,DELETE L,LIST

E ,EXIT P,PART V ,VENDOR

I!

1-7/1-8

o 0)

o

o

o

o

SUMMARY OF THE DBA'S RESPONSIBILITIES 2

,Qat.:.;,;U 4#.4.,.1 }~;4; M,hEne'L ; .4

o

D

o o o

o o

(

(

(

c

(~

SUMMARY OF THE DBA'S RESPONSIBILITIES

As a DBA, you may undertake all or only a few of the functions described in this manual.

However, you should take on the following responsibilities:

• Become familiar with the EDL files. These files should be available to the EDL users in your group. [The files are described in the System Release Bulletin (SRB) and in a file on the release tape.]

• Reload your new EDL version with the data from your existing data base. Reload only if you had an earlier EDL version. (The reloading process is described in the SRB and on a file on the release tape.)

•

Check the terminal configuration set for your site under EDL identifier EDLID and change the settings if necessary. For information on this function, refer to Terminal

Configuration in the EDL Reference Manual (listed in the preface).

• Initiate other designers as new EDL users (using the User Management task described in chapter 5 and assign design reviewers (using the Release Administration task described in chapter 7).

• Add or delete menu items and modify task security categories to customize EDL (using the System Administration task described in chapter 4).

•

Register the file names and the customized design applications (using the System Administration task described in chapter 4), and the part numbers, part families, and vendors that designers reference (using the Part, Family and Vendor Management task described in chapter 8).

• Assign users to groups and allow group access to tasks (using the Group Administration task described in chapter 6).

2

60458880 E 2-1

o o

o o c

EDL CONVENTIONS REVIEW 3

Tasks ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-1 Kinds of Menus •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-1 Task Menus •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-2 Opt ion Menus •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-3 Special Commands •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-3 NOTE Task Command ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-4 Send a Note ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-4 Read a Note ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-5 Global Commands ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-6 Menu Selections ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-7 Menu Queuing (Type-Ahead) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-8 Dialog Delimiters ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-8 String Delimiters ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-8 Menu Display •••••••••••••••••••••••••••••••••••••••••••••••••••.••••••••••••••••••••••••••• 3-9 Field Length on Prompts •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-10 Online Help •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-10

=U:;CJi( , MP.A6t.%¥. $9

I

+E~!4f#j!H£

o o

o o

o

o o

( (

^{I " .;..~ .}

(

(,.

(

C

(;

EDL CONVENTIONS REVIEW

This chapter reviews the EDL conventions for menu selection and command entry that are described in the EDL Reference Manual. They are included in this manual for your convenience.

EDL is a menu- and/or command-driven system: If you select an item from a main menu, a second menu of functions is displayed. In some cases, if you select a function from the second menu, a third menu appears. When you make a selection, EDL executes a task or an option, depending upon the menu type.

TASKS

An EDL task is an action taken by EDL in response to a menu selection or command entry. A task consists of the execution of an ordered sequence of processes. A process can be one of the following:

•

Display of an EDL task menu.

•

Execution of another EDL task.

•

Execution of a NOS procedure.

•

Execution of an EDL overlay capsule.

•

Execution of a standard unoverlaid EDL function.

When a task menu is displayed, you can invoke another task either by entering a line item choice from the current display or by entering a task command. A task command always invokes the same task, regardless of which task menu is displayed. However, several different synonymous commands may be used to invoke the same task. Similarly, many different task menu line items may invoke the same task, but choosing any line directly invokes only one task.

KINDS OF MENUS

There are two general classifications of menus you will use within EDL. The two menu classifications are task menus and option menus. Although these menus are very similar in appearance, the selections that you can enter at each menu differ depending on which level of menu is displayed. These menu classifications and the differences in them are discussed in the following sections of this chapter.

3

60458880 E 3-1

TASK MENUS

The task menus are command level menus. A typical task menu is the Administrator Tasks menu shown next. It is usually the first menu that is displayed for the local administrator.

ADMINISTRATOR TASKS 1. EXIT

2. USER MANAGEMENT 3. GROUP ADMINISTRATION 4. RELEASE ADMINISTRATION

5. PART, FAMILY, AND VENDOR MANAGEMENT ENTER TASK

E,EXIT USERMGMT GROUPADMIN RELADMIN PARTM

On the left side of the display, the task menu lists the task selections available. Each task is prefaced with an index number. On the right side of the display are the commands that correspond to each selection listed on the left side of the display. Some commands have abbreviations listed first, separated from the command by a comma. Either the command or its abbreviation may be used.

The prompt after the selection list is ENTER TASK. You may enter anyone of the index numbers (in this case, 1 through 5) to select that task, or you may enter the command for that task. The prompt, ENTER TASK, is the only visible difference between the task menu display and the option menu display.

Task menus differ from option menus (option menus tasks operate at a command level. As long as you command for any task whether it is listed on that the same task regardless of which menu is active.

listed on any menu. These are discussed later.

are discussed in the next section) in that are at a task menu, you may enter the menu or not. A command will always invoke

There are also some commands that are not

In the Administrator Tasks menu, for example, you can enter either the index number 3 or the command GROUPADMIN and get the same result, which is to access the Group Administration menu display. This command, GROUPADMIN, will access the Group Administration menu when entered while any task menu is active. The Group Administration menu is also a task menu (note that the prompt is ENTER TASK); therefore, an index number or any command can be entered from the task menu.

When you choose to exit from a task menu, EDL displays the task menu that was previously active. However, if you exit all the active task menus, EDL displays the following menu:

CHOOSE NEXT TASK TO BE EXECUTED 1. CHOOSE NEXT TASK

2. BEGIN YOUR FIRST TASK 3. QUIT THIS EDL SESSION ENTER TASK

?

F,FIRST Q,QUIT,STOP

This feature protects you from inadvertently exiting from EDL if you enter too many carriage returns. You must explicitly exit from EDL by entering

Q,

QUIT, STOP, or by selecting the third task from this menu.

3-2 60458880 F

(

(

(

c

(

OPTIONS MENUS

Option menus are a level below task menus. The only difference in format appearance is the prompt, which reads SELECT OPTION rather than ENTER TASK. Option menus request input in a manner similar to the requests by interactive prompts from EDL for text, integers, or YIN (yes/no) responses. EDL will accept only responses relevant to that particular prompt or menu.

In all option menus, you make your selection by entering an index number or by entering the keyword (or its abbreviation) that is listed on the right side of the display. Although the display resembles the displays for task menus, the list of words on the right side of the menu displays are keywords rather than commands. You may enter only a keyword from the displayed menu. Index numbers and keywords are the only input that option menus will accept. Commands cannot be entered on the option menu level. You can, however, use the type-ahead feature (described later in this chapter under Menu Queuing) for responses to the prompts that appear after the option is selected, as long as the responses are in the same sequence as the prompts that would normally appear.

SPECIAL COMMANDS

I

^NOTE

I

If the menu you are working with prompts with

SELECT OPTION

you must begin the response line with an index number or a keyword from the currently displayed menu.

There are six commands that do not appear on any particular menu. These commands, listed

I

next, can be entered from any task menu.

STOP QUIT or Q FIRST or F TASKS COMMANDS NOTE

The STOP and QUIT or Q commands both stop the EDL program and return you to NOS.

The FIRST or F command clears all pending tasks and returns you to the first task specified for your EDL user name, typically the Administrator Tasks menu for a local administrator or the User menu for a designer.

The TASKS and COMMANDS commands display the names of the commands that call tasks and a short description of the task that each command calls.

Use of the NOTE command is more extensive and is covered in the following section.

60458880 F 3-3

I

I

I

NOTE Task Command

The NOTE task command does not appear on any task menu. However, you can enter it from any task menu. This task provides you with a simple means of exchanging information with other EDL users. There are some limitations to the NOTE task. There is no editing capability and notes can be sent only on the local host.

The NOTE facility consists of two tasks which appear on the following menu when you enter NOTE:

NOTE TASKS 1. EXIT

2. SEND A NOTE 3. READ A NOTE ENTER TASK

?

E,EXIT SEND READ

The two NOTE tasks, SEND and READ, are explained in the following sections. As with other task commands, you can enter SEND or READ from any task menu.

Sencla Not.

If you enter 2 or SEND, EDL prompts you for the last name of the user to whom you wish to send a note.

ENTER THE LAST NAME OF THE RECIPIENT, LIST, OR CR TO RETURN

If you enter any characters except LIST, EDL prompts for a first name, as follows:

ENTER THE FIRST NAME OR CR FOR ALL

If you enter a first name, EDL prompts for a middle initial, as follows:

ENTER THE MIDDLE INITIAL OR CR TO CONTINUE

EDL then lists all users whose last names begin with the characters you entered and whose first names and middle initial match the characters you entered.

If you enter LIST in response to the prompt for the name of a recipient, EDL prompts you for more information as follows:

ENTER A PARTIAL LAST NAME OR CR TO RETURN

If you enter any characters here, EDL displays a selection list of all users whose last names begin with the characters you entered, and prompts you to select one of the entries.

After you make your selection, EDL displays the following prompt:

ENTER THE NAME OF ANOTHER RECIPIENT, LIST, OR CR TO CONTINUE

EDL continues to prompt you for additional recipients until you enter only a carriage return. Then EDL prompts you as follows:

ENTER THE TEXT OF YOUR MESSAGE. ENTER JUST CR TO END YOUR MESSAGE

• 3-4 60458880 F

(

l

(

(

(

(~

(

^{' ...••} -.; ^,

EDL displays an underline of 77 characters for your note. Each time you enter a carriage return for a new line, EDL displays another 77 character underline. When you have completed your note, enter a carriage return at the beginning of a line. EDL then displays the

following prompt:

DO YOU WANT TO CANCEL THIS MESSAGE?

ENTER YES OR NO (YIN)

?

If you enter N, NO, or a carriage return, EDL stores the note to be read by the recipient(s) and displays the following message:

***

THE MESSAGE HAS BEEN SENT

***

Read a Note

If you have any notes stored in EDL that you have not read, EDL displays the following message at the beginning of every task menu you access:

YOU HAVE A NOTE. ENTER READ TO READ YOUR NOTE(S)

Any time you enter the READ command, EDL checks to see if you have any notes. If not, EDL displays the following message:

YOU DO NOT HAVE ANY MESSAGES

If you do have notes, EDL displays a list first of your unread notes, then those that you have read before. EDL displays this list in the format shown in the following example:

2 SELECTIONS DATE

1. 85/08/20.

2. 85/08/21.

TIME 09.14.30 13.32.23

***

END OF LIST

***

SENDER OLSON, O.L.

SMITH, R.A.

ENTER A NUMBER, E OR EXIT, OR CR FOR MORE

After you select a note, EDL displays the selected note in the format shown in the following example:

SENDER DATE

OLSON, O.L.

85/08/20. 09.14.30

TOM, PLEASE REVIEW DRAWING D3 ON FILE SUB12 ON ACCOUNT MACH37.

After each note, EDL prompts as follows:

WOULD YOU LIKE TO DELETE THIS MESSAGE?

ENTER YES OR NO (YIN)

?

If you enter Y or YES, EDL deletes the message. If you enter N, NO, or a carriage return, EDL marks the message as read and saves it. EDL then relists your remaining notes in the format shown earlier.

60458880 F 3-5 •

~ I

If there are no more notes, EDL returns to the previous task menu.

f

f

GLOBALCO~ANDS

There are two global EDL commands that can be entered at any time during the menu displaying process, for both option and task menus. These commands are the HELP or ? command and the toggle command, M. The toggle command is discussed under Menu Display later in this chapter. The HELP command is described under Online Help later in this chapter.

3-6 60458880 F

( (

(

c c

MENU SELECTIONS

You can use the index number listed next to each menu item or you can use the command or keyword on the right side of the menu to make menu selections. In the following example, GROUP ADMINISTRATION (function 3) is selected from the Administrator Tasks menu, and the menu for that item is displayed.

ADMINISTRATOR TASKS 1. EXIT

2. USER MANAGEMENT 3. GROUP ADMINISTRATION 4. RELEASE ADMINISTRATION

5. PART, FAMILY, AND VENDOR MANAGEMENT ENTER TASK

E,EXIT USERMGMT GROUPADMIN RELADMIN PARTM

? 3

GROUP ADMINISTRATION 1. EXIT

2. LIST GROUPS 3. GROUP MANAGEMENT 4. MEMBER MANAGEMENT 5. TASK ACCESS MANAGEMENT ENTER TASK

E,EXIT LISTGROUPS GROUPMGMT GROUPftlEM GROUPTASKS

?

60458880 F

I

^NOTE

I

When a menu is displayed, a carriage return automatically activates the first menu item.

Since the first menu item is usually an EXIT, a carriage return usually redisplays the previous menu.

3-7

I

MENU QUEUING (TYPE-AHEAD)

To maneuver quickly through the menus, you can enter a series of menu selections, either by line number or by command or keyword. For example, if the Administrator Tasks menu is on the screen and you want to use the Group Management task (an itea in the Group Administration menu) to list all information about a group XYZ, you can enter the menu selections separated by slashes (the slash is a dialog delimiter and is described in the next section of this chapter).

Example:

GROUPMGMT/L/XYZ

This type-ahead feature temporarily turns off the menu display, and only the information for the final selection is displayed. In the example, the inforaation for group XYZ would be displayed.

If EDL encounters an error during execution of a type-ahead line, the remaining data is discarded and EDL prompts you for the next response after the error aessage.

DIALOG DELIMITERS

A dialog delimiter separates entries in your command, such as tbe user's identifier (ID) and password and queued menu selections (queuing of menu selections is described immediately preceding this section, under Menu Queuing). The slash is the default EDL dialog

delimiter. You can change an individual user's dialog deliaiter When adding the user ID to EDL.

Exaaple: NEW/USER Exa.ple: 2/3/2

STRING DELIMITERS

I

NOTE

I

The dialog delimiter in effect When logging in to EDL is always the slash. For e~le,

if you enter your EDL 10, password, and a task command in a string, the iteas aust be separated by slashes regardless of what yoo have specified as your dialog deliaiter.

You can use a dialog delimiter as a character in a name by placing string delimiters around the entire line. For example, in

"DEPT/CAD"

the quotation marks direct EDt to view the slash as a character and not as a dialog delimiter between two names. The quotation marks are the default string delimiters for EDL. You can change an individual user's string delimiter when adding the user ID to EDL.

I 3-8 60458880 F

(

(

(

c

C','-',"','

^{, '" "}

MENU DISPLAY

The M keyword works like a three-way toggle switch, producing full menus, brief menus, or menu headers only. Full menus are turned on by default. Entering the keyword

M

the first time turns on the brief menu, which shows the menu header, line numbers, and keywords.

Entering M the second time displays only the menu header and the prompt for entering a task or option. Entering

M

the third time returns the complete menu display. The following example shows the use of the three menu displays:

Brief menu, selection 3

ADMINISTRATOR TASKS 1. EXIT

2. USER MANAGEMENT 3. GROUP ADMINISTRATION 4. RELEASE ADMINISTRATION

5. PART, FAMILY, AND VENDOR MANAGEMENT ENTER TASK

? m/groupadmin

GROUP ADMINISTRATION

E,EXIT USERMGMT GROUPADMIN RELADMIN PARTM

1(E,EXIT) 2(LISTGROUPS) 3(GROUPMGMT) 4(GROUPMEM) 5(GROUPTASKS) ENTER TASK

Menu header only, ? m/3 selection 3

Full menu, selection 1

60458880 F

GROUP MANAGEMENT SELECT OPTION

? m/1

GROUP ADMINISTRATION 1. EXIT

2. LIST GROUPS 3. GROUP MANAGEMENT 4. MEMBER MANAGEMENT 5. TASK ACCESS MANAGEMENT ENTER TASK

E,EXIT LISTGROUPS GROUPMGMT GROUPMEM GROUPTASKS

3-9

I

FIELD LENGTH ON PROMPTS

Each prompt for input displays a string of underscores that indicate the maximum length of

I

the data acceptable to the prompt. If the acceptable length of the input data exceeds one line, only one line of underscores is displayed. If you enter data that exceeds the maximum length, EDL truncates the data to the maximum length, issues a message, and continues

processing. With dialog delimiters, you can enter a string of commands, keywords, and responses that exceed the underscores. Truncation rules apply to individual elements in the string.

ONLINE HELP

For assistance, you can interrupt any prompt by entering either HELP or a question mark character. The following example shows a help request entered during the USER MANAGEMENT task:

, 3-10

USER MANAGEMENT 1. EXIT

2. LIST USERS 3. ADD USERS 4. DELETE USERS

5. CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION

?

3

ENTER THE EDL ID FOR THE NEW USER OR CR TO EXIT

?

jane

E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE

ENTER THE EDL PASSWORD FOR THE NEW USER OR CR TO RETURN

?

cad

?

help

ENTER THE NEW USER'S NOS USER NAME OR CR TO RETURN

ENTER THE 7 CHARACTER CODE WHICH IS THE NOS USER NAME THE USER HAS BEEN ASSIGNED. THIS IS THE NOS USER NAME THEY SHOULD ALWAYS RUN EDL FROM.

60458880 F

()

o

o

o o

o o

hAA

UPDATING THE MESSAGE AND TASK DATA BASE 4

Applying Transaction Data ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-1 Task Security ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-1 Transaction Record Format ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-2 Message Information (MI) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-3 Message Help (MIl) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-3 Option Menu Lines (OM) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-4 Option Keywords (OK) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-4 Option Values (OV) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-5 Task Information (rI) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-5 Task Commands (TC) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-6 Task Menu Lines (TM) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-6 Task Processes (TP) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-7 Task Parameter Values (TV) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-7 Examples •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-8

1.«. Am ."* 4,4. 04 $ .. Z iu. ^1* 4J ._

o

I 0

I

o o

o

o o

( (

(

(

(

[~

(

UPDATING THE MESSAGE AND TASK DATA BASE

The task to update the message and task data base allows you to customize tasks and messages in EDL to meet the needs of your site. The task reads transaction records from a sequential input file, which you have prepared using a text editor such as the Full Screen Editor or XEDIT. You should save any transaction files that you have applied to the default menu data base, so that they may be reapplied when you install a new version of EDL.

APPLYING TRANSACTION DATA

EDL uses the standard data selection task (SELECT DATA RETRIEVAL METHOD) to select the transaction file to be applied to the current running data base. You must have previously saved the file in EDL with the file type UPPER CASE TEXT FILE and the application data type EDL MDB TRANSACTIONS. Refer to the EDL Reference Manual for information on saving files in EDL.

After you specify the transaction data set, EDL updates the menu data base and displays the following messages:

*** FINISHED PROCESSING MOB TRANSACTIONS ***

*** PROCESSING DETAILS ARE ON LOCAL FILE MDBLIST ***

You should check the messages on file MDBLIST. To check the messages, either use a text editor or route the file to a printer so you can review a hard copy.

T ASK SECURITY

This feature allows you to tailor your system to control task access. You can specify a task security code for each task in EDL (refer to Task Information later in this chapter).

If you specify a security code for a task, only users who are associated with a group that has access to tasks with that code can access that task. However, since an individual user may be a member of more than one group, that individual can have a wide range of task accesses. Individual users can access any task that does not have a security code associated with it.

4

60458880 E

4-1

TRANSACTION RECORD FORMAT

The transaction file consists of records in a specific format. All records have an action code in the first pOSition (called column 1 for simplicity). The following action codes are recognized:

A Add new records.

C Change records that already exist.

D

Delete existing records.

Columns 3 and 4 contain a 2-character record identifier (that is, the transaction type).

The various identifiers are included in the headings of the following sections of this chapter.

COlumns 11 through 120 contain the data items. Character fields are left-justified on 10- character boundaries; integer fields are right-justified in 10-digit fields. Therefore, tab settings of 3, 11, 21, 31, 41, 51, 61, and 71 will facilitate entering the data correctly using the Full Screen Editor or XEDIT. Comment lines are indicated with a blank or asterisk in column 1.

The information in the follOwing sections describes what should appear on the transaction file for each type of record. The column headed Field shows the name used by the external schema

EDLMENUW.

The column headed Type contains C for character fields or I for integer fields.

The column headed Constraints shows the information that may appear in the field. There are several kinds of constraints.

Unique Subset

Value

Only one record with the same value in the field may exist in the data base.

The record may not exist unless the field value matches another field value in another type of record. These are indicated by capital letters not enclosed in quotation marks.

One of the values enclosed in quotation marks must be in the field.

Examples of transaction records for a task and an option follow the format descriptions.

4-2 60458880 E

( (

(.

(

(

c c

MESSAGE INFORMATION (MI)

The se record s are the header records for all prompts, menus, and error messages.

Format:

Field _~ Length DescriEtion Constraints

Ac tion C 1 Action code "A" , "C", "D"

blank 1

ID C 2 Record ID "MI"

blank 6

MIMNA C 10 Message name Unique

MITYP C 10 Type "PROMPT" , "MESSAGE", "ERROR",

"OPTION" , "TASK MENU"

MITTL C 70 Title text

MESSAGE HELP (MH)

I

These records specify the help text for the message.

Format:

Field ~ ^Len~th DescriEtion Constraints

Ac tion C 1 Ac tion code "A" , "C", liD"

blank 1

ID C 2 Record ID "Mil"

blank 6

MHMNA C 10 Message name MIMNA

MilLIN I 10 Line nunber Unique within the menu

MHl'XI C 70 Message text

60458880 F

4-3

OPTION MENU UNES

(OM)

These records specify the text to be displayed on option menu lines.

Format:

Field Type _I£n

a

^th Description Constraints

Action C 1 Action code "A" , "C", "DII

blank 1

ID C 2 Record ID "OM"

blank 6

OMMNA C 10 Message name MIMNA

OMMLN I 10 Line number Unique within the menu

OMTXT C 40 Message text

OPTION KEYWORDS

(OK)

These records specify the keywords that may be used to choose an option menu line.

Format:

Field

.'!U!.

^I£nsth Descri2tion Constraints

Action C 1 Action code "A", "C", liD"

blank 1 ~

ID C 2 Record ID "OK"

blank 6

OKMNA C 10 Message name OMMNA

OKMLN I 10 Menu line OMMLN

OKKEY C 10 Keyword Unique within the menu

4-4 60458880 E

( (

(

(

C

(F

OPTION VALUES (OV)

These records specify the value that is returned to the program when the user picks an option from the option menu.

Format:

Field Type Length DescriEtion Constraints

Action C 1 Action code "A", "C", "D"

blank 1

ID C 2 Record ID "OV"

blank 6

OVMNA C 10 Message name OMMNA

OVMLN I 10 Menu line OMMLN

OVPOS I 10 Value position Usually 1, except when the

option menu must return two more values to the program

OVVAL C 40 Value

TASK INFORMATION (TI)

These records are the headers for EDL tasks. You should create new, similar tasks when customizing EDL rather than change the standard tasks provided in the released system.

You should also modify the security category to control group access to tasks.

Format:

Field _~ Length Description Constraints

Action C 1 Action code

"A", "e", "D"

blank 1

ID C 2 Record ID "TI"

blank 6

TITNA C 10 Task name Unique

TISEC C 10 Security category Site defined

or

TITYP C 10

TIDSC C 70

Task type

Description of

MASTER for tasks which cannot

I

be run on a subordinate data base in a network

the task

60458880 F 4-5

TASK COMMANDS (Te)

These records specify the commands that may be used to invoke tasks.

Format:

Field _~ lA!nlth DescriEtion Constraints

Action C 1 Action code

"A",

"C",

"n"

blank 1

ID

C 2 Record ID "TC"

blank 6

TCTNA C 10 Task name TITNA

TCCMD C 10 Co1IIDand Unique

TASK MENU UNES (TM)

These records specify which task is invoked when the user enters a task menu line number.

Format:

Field _~ Lenlth Description Constraints

Action C 1 Action code

"A", "c" , "n"

blank 1

ID C 2 Record ID "TH" _{'Q !}

blank 6

TMMNA

C 10 Message name MIHNA

TMMLN I 10 Menu line number Unique within the menu

TMTXT C 40 Text

TMTNA C 10 Task name TITNA

4-6 60458880 E