[?29h[0"z 1. Miscellaneous   1.1 Sample Screens  Conventions used: o Any underlined item is one that the user must type in. If it is in lowercase, he must type in the field described; if it is in uppercase he must type in the field exactly as shown. o Any bolded item on a screen will be shown in reverse video.  Miscellaneous Page 1   1.1.1 Login Screen  user types a carriage return Username: username Password: password  Miscellaneous Page 2   1.1.2 Sample System Menu  + - - - - - - - - - + ! M a i n M e n u ! + - - - - - - - - - + 1) Payroll 2) Personnel 3) Bill of Materials Command (Number, Go back a screen, Transaction menu, Exit): _ G T E _  Miscellaneous Page 3   1.1.3 Sample Option Menu  + - - - - - - - - - - - - - - - - - + ! B i l l o f M a t e r i a l s ! + - - - - - - - - - - - - - - - - - + 1) Generate Cutting List (BOMCUTLST) 2) Generate Design Change List (BOMDCLST) 3) Online Bill Of Materials Display (BOMDISP) Command (Number, Go back a screen, Transaction menu, Exit): _ G T E _  Miscellaneous Page 4    1.1.4 Sample Transaction Menu  + - - - - - - - - - - - - - - - - + ! T r a n s a c t i o n M e n u ! + - - - - - - - - - - - - - - - - + BOMCUTLST: Bill of Materials Cutting List BOMDCLST: Bill of Materials Design Change List BOMDISP: Bill of Materials Display PAYINQ: Payroll Inquiry PAYUPD: Payroll Update Command (Transaction name, Go back a screen, Exit): _________ G E _________  Miscellaneous Page 5   1.2 How To Write A Transaction   1.2.1 Defining The Form(s)  This part is optional. It is only necessary if the user must supply information to the User Interface (see section 4.2.1, "Accept Parameters Phase"). Use FDU (the TDMS Forms Definition Utility) to specify any form or forms that will be used to gather information from the user. You can include any simple validation of input fields and per field help lines or full help screens, if desired. For further information, see the "VAX-11 TDMS Forms Manual".  1.2.2 Writing The Request  This part is optional. It is only necessary if there are any variable parameters in the transaction procedure file. The main purpose of the TDMS request in the context of the User Interface is to build a symbol table which will be used to substitute hardcoded information for any variable parameters in the transaction procedure file. The request can also be used to do inter-field validation on any fields input by the user. The request must specify the forms that it will be  Miscellaneous Page 6   working with and the CDD record for the symbol table, which will probably look as follows: 01 SYMBOL-TABLE-RECORD. 05 SW-END-OF-REQUEST PIC X(1). 88 END-OF-REQUEST VALUE "T". 05 SYMBOL-TABLE OCCURS 1 TO 100 TIMES DEPENDING ON NUMBER-OF-SYMBOLS. 10 SYMBOL-NAME PIC X(31). 10 SYMBOL-VALUE PIC X(31). The request will be called repeatedly until END-OF- REQUEST is true. At this point the entire symbol table record must be filled in with all the symbol names (and their values) that appear in the transaction command file. There is one special symbol, TRANSACTION_MODE. If present it will be checked to see what it contains. If it contains an "I", the transaction will be run interactively. If it contains anything else, the transaction will be submitted to the batch queue on the user's behalf and the symbol's value will be used as the switch settings for the batch. For further information on writing request please see the "VAX-11 TDMS Request Manual".  1.2.3 Writing The Transaction Command Procedure  This part is not optional. This is the actual command procedure which will be used to process the transaction. The only difference between this command procedure and a DCL command procedure is that it may contain variable parameters which will have a hardcoded value substituted for them when the transaction is run. Any variable parameters in the transaction command procedure must be enclosed in apostrophes and defined in the symbol table (see "Writing The Request"). For further information please read the "VAX/VMS Guide To Writing Command Procedures" and the section on "Sample Transaction Command Procedures" in this document.  Miscellaneous Page 7   1.3 Sample Transaction Command Procedures   1.3.1 Sample Interactive Command Procedure  $ ! This command procedure runs an interactive $ ! program and needs no parameters from the $ ! user. $ ! $ DEFINE/USER SYS$INPUT SYS$COMMAND $ RUN BOM500 !A fictitious interactive update $ EXIT  1.3.2 Sample Batch Command Procedure  $ ! This command procedure uses variable $ ! parameters. It must have a request and $ ! probably a form associated with it. The $ ! request must not return a value of "I" in $ ! the symbol TRANSACTION_MODE! $ ! $ RUN BOM600 'AS_OF_DATE' 'PART_NUMBER' $ ! $ EXIT  1.3.3 Sample Hybrid Procedure  $ ! This command procedure will allow the user $ ! to update a file interactively and then $ ! submit a batch to provide a hardcopy record $ ! of the updates. $ ! $ DEFINE/USER SYS$INPUT SYS$COMMAND $ RUN BOM500 !Interactive update $ ! $ SUBMIT BOMHRDCPY $ ! $ EXIT  Miscellaneous Page 8