Data Management Library ENABLE Reference Manual ™ Abstract Part Number This manual describes the operation of ENABLE and the syntax of the ENABLE commands. This manual is intended for all users of ENABLE.
Document History Edition Part Number Operating System Version Date First Edition 82560 A00 GUARDIAN B00 March 1985 New editions incorporate any updates issued since the previous edition. Copyright All rights reserved. No part of this document may be reproduced in any form, including photocopying or translation to another language, without the prior written consent of Tandem Computers Incorporated. Copyright 1985 Tandem Computers Incorporated.
CONTENTS SECTION 1. INTRODUCTION .................................... 1-1 Applications Generated by ENABLE .......................... 1-2 ENABLE Components ......................................... 1-4 ENABLE Compiler ......................................... 1-4 Program Generator ....................................... 1-4 General Server .......................................... 1-5 Application Program Skeleton File ....................... 1-5 PATHCOM Command Skeleton File ...........................
CONTENTS RESET Command ............................................. 3-21 SET Command ............................................... 3-26 SHOW Command .............................................. 3-31 SECTION 4. ENABLE ATTRIBUTES ............................... 4-1 BOXTITLE Attribute ....................................... 4-8 CHECKDATA Attribute ...................................... 4-11 DATAFILE Attribute ....................................... 4-13 DELETE Attribute ...................................
CONTENTS SECTION 6. APPLICATION EXECUTION ........................... Executing the Obey File ................................... Starting a PATHWAY System After a SHUTDOWN ................ Establishing a PATHWAY System for Two or More Users ....... 6-1 6-4 6-4 6-5 SECTION 7. ENABLE SCREENS .................................. 7-1 Standard Screen Formats .................................. 7-1 Standard Screen Format for a Single-File Application .... 7-3 Standard Screen Format for a Multifile Application ...
CONTENTS 1-4. Overview of Application Execution ................... 1-10 2-1. 2-2. 2-3. 2-4. 2-5. 2-6. 2-7. 2-8. 2-9. 2-10. 2-11. Example of Attribute Table When You Start ENABLE .... Current Value for a Box Attribute ................... Override Value for a Box Attribute .................. Default Value for a Box Attribute ................... Attribute Table After ADD BOX Command ............... Current Value for an Application Attribute .......... Override Value for an Application Attribute .........
CONTENTS 7-1. 7-2. 7-3. 7-4. 7-5. 7-6. Record Description and ENABLE Commands for a Sample Single-File Application ..................... 7-3 Sample Standard Terminal Screen for a Sample Single-File Application ............................ 7-4 Record Descriptions and ENABLE Commands for a Sample Multifile Application ...................... 7-11 Sample Standard Terminal Screen for a Sample Multifile Application ............................. 7-12 First HELP Screen ...................................
PREFACE This manual describes the syntax of ENABLE, a product that is part of the ENCOMPASS distributed data base management system. ENABLE allows you to build simple applications that execute within a PATHWAY system.
SYNTAX CONVENTIONS IN THIS MANUAL The following list summarizes the conventions for syntax notation in this manual. Notation Meaning UPPERCASE LETTERS Uppercase letters represent keywords and reserved words; you must enter these items exactly as shown. Lowercase letters within angle brackets represent variables that you must supply. Brackets [] Brackets enclose optional syntax items.
GENERATING AN IMMEDIATE SINGLE-FILE APPLICATION Enter the commands exactly as shown to create a data base file and an application that can be used to enter employee data.
GENERATING AN IMMEDIATE MULTIPLE-FILE APPLICATION Enter the following commands exactly as shown to create two data base files and an application that can be used to enter data in the files. PARTS-INFO Page 1/1 * PARTNUM * PRIMKEY LOCATION-NUM QUANTITY-ON-HAND REORDER-LEVEL + PARTNAME PRICE .00 Ready for input... (1) CREATE A DATA DICTIONARY :EDIT ddlsrc2 *ADD 1 RECORD PARTS. 2 FILE IS parts 3 02 PARTNUM 4 02 PARTNAME 5 02 PRICE 6 KEY 0 IS PARTNUM 7 KEY “pn” IS PARTNAME. 8 END 9 10 RECORD INVENTORY.
GENERATING AN APPLICATION WITH A TABULAR SCREEN Enter the commands as shown to create a telephone book file and generate an application that displays the following screen: TELEPHONE LIST SCREEN Page 1/1 * Name >>>>>>>>>>>>>>>>>>>>> Phone Number >>>>>>>>>>>>>> _____________________ _____________________ _____________________ _____________________ _____________________ _____________________ _____________________ _____________________ _____________________ _____________________ ____ ____ ____ ____ ____ ___
SECTION 1 INTRODUCTION ENABLE builds an interactive update application that executes under the PATHWAY transaction processing system. Like other applications defined and developed for the PATHWAY environment, an ENABLE application implements transactions that originate at a terminal and access a data base.
INTRODUCTION Generated Applications For a description of the individual tasks necessary to create an application, refer to the ENABLE User's Guide. APPLICATIONS GENERATED BY ENABLE Figure 1-1 shows the screen displayed by a sample ENABLE application. You could use this application to retrieve and update the information in a single data base file.
INTRODUCTION Generated Applications • Define the method used to maintain the integrity of the file To generate a single-file application, you use the ENABLE commands described in Section 3. Figure 1-2 shows the screen displayed by a sample application that you could use to retrieve or update records in two data base files. Because applications similar to this sample application can access two or more files, these types of applications are sometimes called multifile applications.
INTRODUCTION ENABLE Components You generate a multifile application by using the ENABLE commands described in Section 3. ENABLE COMPONENTS To generate an application, ENABLE uses the following components: the ENABLE compiler, the program generator, and a General Server. ENABLE provides two skeleton files: a SCREEN COBOL application program skeleton and a PATHCOM command file skeleton.
INTRODUCTION PATHCOM Command Skeleton File • Uses the information in the object table to transform the PATHCOM skeleton file into a PATHCOM command file General Server The General Server, ENABLEGS, accesses and updates the data base files. ENABLEGS can access up to 32 data base files. Although ENABLEGS is an integral part of the ENABLE environment, it is available for use as a server with other applications. Details regarding individualized use of ENABLEGS appear in Appendix E.
INTRODUCTION Dictionary Files Dictionary Files ENABLE accesses DDL data dictionary files to extract information about the data base files to be used by an application. The dictionary must contain a record description of each file to be used. The record description must be compatible with SCREEN COBOL representation capabilities. Specifically, this means that the DDL statements and clauses used to create the record description must conform to the following rules: • A TYPE clause must be CHARACTER or BINARY.
INTRODUCTION Overview of Application Generation • If a VALUE clause appears, ENABLE accepts an initial value of up to 30 characters in length. Longer values are discarded. OVERVIEW OF APPLICATION GENERATION You can generate an ENABLE application by supplying ENABLE with: 1. A data dictionary that describes the files to be accessed by your application 2.
INTRODUCTION Overview of Application Generation ENABLE Supplies You Supply The Compiler (ENABLE) BOX Employee APPL Emp-Prog :ENABLE %SET RECORD employee %ADD BOX employee %SET APPL TREE (01 employee) %SET APPL PATHCOMFILE enabpath %ADD APPL emp-prog %GENERATE APPL emp-prog ENABLE Commands Object Table The Program Generator (ENABLOBJ) SCREEN COBOL Skeleton File (ENABAPPS) PATHCOM Skeleton File (ENABPATS) RECORD Employee. FILE IS EMPLOY...
INTRODUCTION Application Execution APPLICATION EXECUTION To execute an application generated by ENABLE, you must: 1. Supply the data base files to be accessed by the application 2. Establish a PATHWAY system to execute the application Figure 1-4 illustrates the tasks that you perform to establish a PATHWAY system and execute an application. To establish a PATHWAY system and execute an application, you enter a series of commands described in Section 5.
INTRODUCTION Application Execution :PATHMON/NAME $one, CPU 0, NOWAIT, OUT log 1/ PATHMON $one :PATHCOM/IN enabpath/$one PATHCOM Command File (enabpath) PATHCOM PATHMON $one PATHCTL PATHMON $one PATHCTL General Server Employ :PATHCOM $one;RUN employ-prog 1 PATHCOM 2 SCREEN COBOL Object File for Emp-Prog TCP Legend 1 RUN EMPLOY-prog 2 run employ-prog S5043-004 Figure 1-4.
INTRODUCTION Summary of Tasks SUMMARY OF TASKS REQUIRED TO GENERATE AND EXECUTE AN APPLICATION To generate and execute an ENABLE application, you must: 1. Use DDL compile Utility used in to create the appropriate record descriptions and to them into a dictionary. DDL can also create File Program (FUP) file creation source code that can be step 2. 2. Use FUP to create the physical files if the files do not already exist. 3. Call ENABLE and issue appropriate commands to generate the application. 4.
SECTION 2 RUNNING ENABLE You start ENABLE by entering the ENABLE command in response to the command interpreter prompt. The syntax of the ENABLE command is: ----------------------------------------------------------------| | | ENABLE [ / [ , ] ... / ] | | [ ] [ ; ] ... | | | | is: | | | | IN | | | | specifies a file from which commands are to be read.
RUNNING ENABLE ENABLE Command ----------------------------------------------------------------| | | NAME $ | | | | identifies a symbolic process name to be assigned to the | | new ENABLE process. | | | | CPU | | | | identifies a processor where the ENABLE process will | | run. | | | | PRI | | | | specifies execution priority of the ENABLE components. | | | | MEM | | | | defines the maximum number of data pages allocated to | | ENABLE.
RUNNING ENABLE Interactive Mode • If the OUT file specification is a magnetic tape, ENABLE specifies that two consecutive file marks are written just before the file is closed. INTERACTIVE MODE ENABLE functions in interactive mode when you enter commands from a terminal keyboard. ENABLE prompts for a command by displaying the percent symbol (%); for example: :ENABLE ENABLE - T9155B00 - (01APR84) % SYSTEM \XYZ When you enter a command, ENABLE executes the command and issues another prompt.
RUNNING ENABLE Noninteractive Mode NONINTERACTIVE MODE ENABLE functions in noninteractive mode when you enter commands through a command file; for example: :ENABLE /IN enabcomm, OUT $s/ In this example, ENABLE reads commands from an edit-type file named "enabcomm." When ENABLE encounters an end-of-file or an EXIT command in the command file, ENABLE terminates and control returns to the command interpreter.
RUNNING ENABLE Operating Commands--Functional Overview The syntax of the PARAM command is: ----------------------------------------------------------------| | | PARAM EXTPAGES | | | | | | | | is the number of extended memory pages that you want to | | allocate. must be an integer in the range of | | 1 to 32765. The default is 500 pages.
RUNNING ENABLE Operating Commands--Functional Overview Table 2-1. Operating Command Summary (Continued next page) ----------------------------------------------------------------| | | Command Description | |_______________________________________________________________| | | | CMDSYS Sets the default system name for expansion | | of any file names except obey file names. | | This command overrides a preceding SYSTEM | | command for all file names except obey file | | names.
RUNNING ENABLE ENABLE Commands--Functional Overview Table 2-1. Operating Command Summary (Continued) ----------------------------------------------------------------| | | Command Description | |_______________________________________________________________| | | | SYSTEM Sets the default system name for expansion | | of any file names including CMDSYS and | | OBEYSYS names. This command overrides a | | preceding CMDSYS or OBEYSYS command.
RUNNING ENABLE ENABLE Commands--Functional Overview • The name of the record description that describes the file • The operations (delete, insert, read, or update) that the application can perform on the file All of the ENABLE commands that apply to boxes contain an optional keyword, BOX. When you start ENABLE the default object type for all commands is APPL.
RUNNING ENABLE ENABLE Commands--Functional Overview Table 2-3. Functional Summary of Application Attributes ----------------------------------------------------------------| | | Attribute Function | |_______________________________________________________________| | | | PATHCOMFILE Identifies the name of the PATHCOM command | | file. | | | | PATHCOMSKELETON Identifies the name of the PATHCOM | | skeleton file.
RUNNING ENABLE ENABLE Commands--Functional Overview Table 2-4. Functional Summary of Box Attributes (Continued next page) ----------------------------------------------------------------| | | Attribute Function | |_______________________________________________________________| | | | BOXTITLE 1 Identifies optional text that can appear | | BOXTITLE 2 on the screen with records from a file.
RUNNING ENABLE ENABLE Commands--Functional Overview Table 2-4. Functional Summary of Box Attributes (Continued) ----------------------------------------------------------------| | | Attribute Function | |_______________________________________________________________| | | | INSERT Indicates whether the application can, or | | cannot, insert records in a file. | | | | NONSTOP Indicates whether the General Server does, | | or does not, run as a NonStop process | | pair.
RUNNING ENABLE ENABLE Commands--Usage Overview ENABLE Commands--Usage Overview The following paragraphs discuss using the ENABLE commands. Generally, you use these commands to: • Describe an object • Add the object to the object table • Generate an application Suppose, for example, that you want to generate an application that can access a data base file named "parts." To do this, you: 1. Describe a box that is to represent this file 2.
RUNNING ENABLE ENABLE Commands--Usage Overview Figure 2-1 illustrates the attribute table when you start ENABLE and shows the starting values of some attributes; for information about the starting values of all the application and box attributes, refer to the discussion of the SET command in Section 3.
RUNNING ENABLE ENABLE Commands--Usage Overview %SET BOX RECORD parts ENABLE Sample Application Attributes Starting Value: Sample Box Attributes TITLE TREE PATHCOMFILE RECORD DELETE DATAFILE Null Null Null Null ON Null Current Value: PARTS Override Value: Default Value: S5043-006 Figure 2-2. Current Value for a Box Attribute Now suppose that you want to restrict the application to only insert, read, and update operations on a file; that is, you do not want to allow delete operations.
RUNNING ENABLE ENABLE Commands--Usage Overview %ADD BOX parts-box, DELETE OFF ENABLE Sample Application Attributes Starting Value: Sample Box Attributes TITLE TREE PATHCOMFILE RECORD DELETE DATAFILE Null Null Null Null ON Null Current Value: Override Value: PARTS OFF Default Value: S5043-007 Figure 2-3. Override Value for a Box Attribute When you enter an ADD BOX command, ENABLE assumes that you have completed your description of a box.
RUNNING ENABLE ENABLE Commands--Usage Overview Suppose, for example, that you have entered the ENABLE commands described earlier in this section: SET RECORD parts ADD BOX parts-box, DELETE OFF Figure 2-3 showed the contents of the attribute table after these commands are entered.
RUNNING ENABLE ENABLE Commands--Usage Overview When ENABLE adds a box to the object table, it removes any override or default values for the box attributes from the attribute table. ENABLE does not remove a current value for a box attribute unless you set a new current value with another SET command, enter a RESET command to reset the attribute to its starting value, or exit from ENABLE. Figure 2-5 illustrates the partial contents of the attribute table after ENABLE adds "parts-box.
RUNNING ENABLE ENABLE Commands--Usage Overview Describing an Application The values of the application attributes describe global characteristics of an application. Suppose, for example, that you want to identify "enabpath" as the file to which ENABLE is to write the PATHCOM commands for an application. You can identify this file by supplying a value for the PATHCOMFILE attribute.
RUNNING ENABLE ENABLE Commands--Usage Overview Now suppose that you want to identify "parts-box" as the box to be used by the application. You identify the boxes used by an application by supplying a value for the TREE attribute. You could supply a value for this attribute when you enter the ADD APPL command that names and adds the application.
RUNNING ENABLE ENABLE Commands--Usage Overview When you enter an ADD APPL command, ENABLE assumes that you have completed your description of the application. ENABLE then examines the contents of the attribute table to determine that description. ENABLE evaluates the values in the attribute table as follows: • An override value, if present, takes precedence over a current or starting value. • A current value, if present, takes precedence over a starting value.
RUNNING ENABLE ENABLE Commands--Usage Overview %ADD APPL parts-in, TREE (01 parts-box) ENABLE Sample Application Attributes Starting Value: TITLE TREE PATHCOMFILE RECORD DELETE DATAFILE Null Null Null Null ON Null ENABPATH PARTS Current Value: Override Value: Default Value: Sample Box Attributes (01 PARTS-BOX) PARTS-IN S5043-012 Figure 2-8.
RUNNING ENABLE ENABLE Commands--Usage Overview When you enter an ADD BOX command, ENABLE examines the contents of the attribute table, determines the description of the box, and adds the box to the object table. Figure 2-9 illustrates this process.
RUNNING ENABLE ENABLE Commands--Usage Overview %ADD APPL parts-in, TREE (01 parts-box) ENABLE Sample Application Attributes Starting Value: TITLE TREE PATHCOMFILE RECORD DELETE DATAFILE Null Null Null Null ON Null ENABPATH PARTS Current Value: Override Value: Default Value: Sample Box Attributes (01 PARTS-BOX) PARTS-IN Object Table Parts-in Parts-box PATHCOMFILE enabpath DATAFILE parts TREE (01 parts-box) DELETE OFF ••• ••• S5043-014 Figure 2-10.
RUNNING ENABLE ENABLE Command Conventions ENABLE COMMAND CONVENTIONS The following paragraphs describe some of the conventions that apply to the ENABLE commands. Multiline Commands Two or more commands can be grouped and separated by semicolons (;): %command-1; command-2 is equivalent to: %command-1 %command-2 Command Line Continuation Generally, the maximum length of an ENABLE command line is 132 characters.
RUNNING ENABLE Reserved Words Comments Comments are useful only as documentation within a command file. You can include comments with all commands. Comments must be delimited by the double hyphen (--) symbol.
RUNNING ENABLE Field Name Qualification Field Name Qualification To avoid ambiguity, several of the ENABLE commands require you to use unique field names. If a field name is not unique, you must qualify it. The syntax used to qualify a field name is as follows: ----------------------------------------------------------------| | | | | { [ . ... ] .
RUNNING ENABLE Field Name Qualification Consider the record description shown in Figure 2-11. ----------------------------------------------------------------| | | RECORD events. | | FILE IS event KEY-SEQUENCED. | | 02 event-key ... | | 02 event-desc ... | | 02 predicted-dates. | | 04 starting. | | 06 day ... | | 06 month ... | | 06 year ... | | 04 ending. | | 06 day ... | | 06 month ... | | 06 year ... | | 02 actual-dates. | | 04 starting. | | 06 day ... | | 06 month ... | | 06 year ... | | 04 ending.
RUNNING ENABLE String Literals This record description contains several groups; for example: "predicted-dates" and "actual-dates." Nested within both of these groups are other groups: "starting" and "ending." If you want to refer to the field named year indicated in the following portion of this record description: 02 predicted-dates. 04 starting. 06 day ... 06 month ... 06 year ... 04 ending. 06 day ... 06 month ... 06 year ...
SECTION 3 ENABLE COMMANDS ENABLE commands permit you to control and describe objects within the ENABLE subsystem. They allow you to specify attributes that define two types of objects: applications and boxes. Refer to Section 2 for more information about these objects. This section describes the syntax of the ENABLE commands and the function that each command performs. Generally, you use the ENABLE commands as follows: 1.
ENABLE COMMANDS Command Order ----------------------------------------------------------------| | | 1. Use the SET BOX RECORD command to set a value for the | | box attribute that identifies the record description of | | the data base file. | | | | 2. Optionally, use the SET BOX command to describe other | | attributes of the box. | | | | 3. Use the ADD BOX command to name the box that represents | | the data base file and to add the description of the | | box to the object table. | | | | 4.
ENABLE COMMANDS Command Order ENABLE Commands: SET BOX RECORD employee ADD BOX employee-box SET APPL TREE (01 employee-box) SET APPL PATHCOMFILE enabpath ADD APPL employee-prog GENERATE employee-prog Terminal Screen: EMPLOYEE-PROG Page 1/1 * EMPNUM + EMPNAME + DEPT REGNUM BRANCHNUM JOB AGE SALARY VACATION ______ _______________________ ______ ______ __________________ ___ _________ .00 ___ Ready for input F3 for Help, shift F16 to exit S5043-015 Figure 3-2.
ENABLE COMMANDS Command Order ----------------------------------------------------------------| | | 1. Use the SET BOX RECORD command to set a value for the | | box attribute that identifies the name of the record | | description associated with a particular data base | | file. | | | | 2. Optionally, use the SET BOX command to set a value for | | the other box attributes. | | | | 3.
ENABLE COMMANDS Command Order ENABLE Commands: SET BOX RECORD parts SET BOX BOXTITLE 1 "Parts Box:" ADD BOX parts RESET BOX * SET BOX RECORD inventory ADD BOX inventory SET APPL TREE (01 parts 02 inventory LINK partnum TO OPTIONAL partno) SET PATHCOMFILE multipath ADD APPL stock-control GENERATE APPL stock-control Terminal Screen: STOCK-CONTROL Page 1/1 Parts Box: * PARTNUM _____ * PRIMKEY LOCATION-NUM ______ QUANTITY-ON-HAND ______ REORDER-LEVEL ______ + PARTNAME PRICE ______________________ _________
ENABLE COMMANDS ADD Command ADD Command The ADD command names an object and enters its description in the object table. Optionally, the ADD command also supplies override values for the attributes that describe an object. The syntax of the ADD command is: ----------------------------------------------------------------| | | ADD [ APPL ]
ENABLE COMMANDS ADD Command ----------------------------------------------------------------| | | 5. For an application name, the name must not be a | | PATHCOM reserved word when truncated to 15 | | characters. | | | | 6. For a box name, the name must not be the same as any | | field name in the record description associated with | | that box. | | | | LIKE | | | | sets the attributes of the object to be added to those of | | .
ENABLE COMMANDS ADD Command ----------------------------------------------------------------| | | | | | | is any legal value for the specified attribute. | | | | When you supply a value for an attribute with an ADD | | command, you override any value set for the same attribute | | with a SET command or a LIKE clause. The value only applies | | to the object being added; this command does not change the | | current value of the attribute in the attribute table.
ENABLE COMMANDS ADD Command Adding a Single-File Application. To preserve compatibility with previous versions of ENABLE, a single-file application can be added based on the current value of the RECORD box attribute. You do not have to add a box to represent the file or supply a value for the TREE attribute for a single-file application.
ENABLE COMMANDS ADD Command Examples Consider the ADD commands in the following series of ENABLE commands: SET RECORD parts ADD BOX parts <-----------------Box added: PARTS SET APPL PATHCOMFILE newpart SET APPL TREE (01 parts) ADD APPL parts-info <-----------Application added: PARTS-INFO adds a box named "parts" adds an application named "parts-info" to the object table The following ADD BOX command adds a box and supplies a value for the RECORD attribute: ADD BOX parts, RECORD parts <---- adds a box n
ENABLE COMMANDS ASSUME Command ASSUME Command The ASSUME command establishes a default object type for subsequent ENABLE commands. The default object type applies to any command that omits the keywords: APPL or BOX. The syntax of the ASSUME command is: ----------------------------------------------------------------| | | ASSUME { APPL } | | { BOX } | | | | APPL | | | | is a keyword that identifies APPL as the default object | | type.
ENABLE COMMANDS ASSUME Command Example Consider the following series of commands: ASSUME BOX <------------------- SET RECORD employee SET SCREENFORMAT COMPRESSED ADD employ <------------------ASSUME APPL 3-12 <------------------ establishes BOX as the default object type for subsequent commands adds a box named "employ" establishes APPL as the default object type for subsequent commands
ENABLE COMMANDS DELETE Command DELETE Command The DELETE command removes a previously added object from the object table. The syntax of the DELETE command is: ----------------------------------------------------------------| | | | | DELETE [ APPL ] { } | | [ BOX ] { * } | | | | APPL | | | | is a keyword that identifies application as the type of | | object being deleted. If APPL is the default object type, | | you can omit this keyword when you delete an application.
ENABLE COMMANDS DELETE Command associated with an application entry, ENABLE issues an error message. Deleting All Objects. stating: If ENABLE issues a warning message Very low on extended memory; please DELETE unwanted objects you might want to delete some objects and then generate the remaining applications.
ENABLE COMMANDS GENERATE Command GENERATE Command The GENERATE command causes ENABLE to generate one or more applications. The syntax of the GENERATE command is: ----------------------------------------------------------------| | | GENERATE [ APPL ] [ ] | | [ * ] | | | | [ , ] ... | | | | APPL | | | | is a keyword that identifies application as the type of | | object being generated.
ENABLE COMMANDS GENERATE Command ----------------------------------------------------------------| | | | | | | is either an application attribute, or a box attribute. | | When BOX is the object type in effect you can specify | | only box attributes. When APPL is in effect you can | | specify both application and box attributes.
ENABLE COMMANDS GENERATE Command • If the application uses a box or boxes that you have previously added to the object table, ENABLE ignores values for box attributes supplied with a GENERATE command. If you use the following form of the GENERATE command: GENERATE APPL * without previously adding any applications, ENABLE ignores the command.
ENABLE COMMANDS INFO Command INFO Command The INFO command displays contents of the object table. syntax of the INFO command is: The ----------------------------------------------------------------| | | INFO [ APPL ] {
ENABLE COMMANDS INFO Command ----------------------------------------------------------------| | | DETAIL | | | | If APPL is the object type, ENABLE displays: | | | | • The application name (or names if you used the * | | option) | | | | • All application attributes and the values that were in | | effect when the application was added, including any | | starting, default, and null values | | | | • The names of all boxes listed in the TREE attribute | | | | • Under each box name, all box attributes and value
ENABLE COMMANDS INFO Command Examples To display a list of the attributes that describe an application, include the application name when you enter the INFO APPL command option; for example, if an application named "emp-program" has been added, the command: INFO APPL emp-prog causes ENABLE to display: ------------------------------------------------------Application EMP-PROG ------------------------------------------------------Pathcomfile $XYZ.PDQ.MYPATH Pathcomskeleton $SYSTEM.SYSTEM.
ENABLE COMMANDS RESET Command RESET Command The RESET command resets the current value of an attribute (or set of attributes) to its starting value. The syntax of the RESET command is: ----------------------------------------------------------------| | | RESET [ APPL ] { [ ] } | | [ BOX ] { [ ABILITY ] } | | { [ FORMAT ] } | | { [ INTEGRITY ] } | | { [ OTHER ] , ... } | | { * } | | | | APPL | | | | is a keyword that identifies application as the type of | | attribute being reset.
ENABLE COMMANDS RESET Command ----------------------------------------------------------------| | | Box Attributes: | | | | BOXTITLE EXCLUDE INSERT SERVERCLASS | | CHECKDATA FILL NONSTOP SIZE | | DATAFILE FLAG READ TMF | | DELETE HEADINGS RECORD UPDATE | | DICTIONARY INCLUDE SCREENFORMAT VALUES | | | | Application and box attributes are described in | | Section 4.
ENABLE COMMANDS RESET Command ----------------------------------------------------------------| | | * | | | | If APPL is object type, this symbol indicates that ENABLE | | is to reset all box and application attributes to their | | starting values. | | | | If BOX is the object type, this symbol indicates that | | ENABLE is to reset all box attributes to their starting | | values.
ENABLE COMMANDS RESET Command Sample Application Attributes Starting Value: Sample Box Attributes TITLE TREE PATHCOMFILE RECORD DELETE DATAFILE Null Null Null Null ON Null ENABPATH PARTS OFF OFF Current Value: Override Value: Default Value: ENABLE %RESET APPL * Sample Application Attributes Starting Value: TITLE TREE Null Null PATHCOMFILE Null Sample Box Attributes RECORD DELETE DATAFILE Null ON Null Current Value: Override Value: Default Value: S5043-017 Figure 3-5.
ENABLE COMMANDS RESET Command The following example resets both box and application attributes: SET BOX FILL ON SET BOX DELETE OFF SET BOX UPDATE OFF SET BOX RECORD employee ADD BOX employee SET APPL SCOBOLOBJECT SET APPL SCOBOLSOURCE newsrc SET APPL PATHCOMFILE mypath ADD APPL employee-prog RESET APPL SCOBOLOBJECT, ABILITY <- resets the application attribute SCOBOLOBJECT to its starting value "POBJ"; also resets the box attributes DELETE, FILL, INSERT, and UPDATE to their starting values 3-25
ENABLE COMMANDS SET Command SET Command The SET command supplies a current value for an attribute. When you use the SET command, the value you supply remains current until you supply another value with a subsequent SET command, reset the attribute to its starting value with a RESET command, or exit from ENABLE. The syntax for the SET command is: ----------------------------------------------------------------| | | SET [ APPL ] | | [ BOX ] | | | | [ , ] ...
ENABLE COMMANDS SET Command ----------------------------------------------------------------| | | Application Attributes: | | | | PATHCOMFILE SCOBOLOBJECT TITLE | | PATHCOMSKELETON SCOBOLSKELETON TREE | | SCOBOLCOMPILER SCOBOLSOURCE | | SCOBOLLIST TERMINAL | | | | (You cannot specify application attributes when BOX is | | the object type in effect.
ENABLE COMMANDS SET Command If you supply a current value for an application attribute, ENABLE uses that value to determine the description of an application added to the object table (unless you supply an override value for the same attribute when you enter an ADD command). If you supply a current value for a box attribute, ENABLE uses that value to determine the description of a box added to the object table (unless you supply an override value for the same attribute when you enter an ADD command).
ENABLE COMMANDS SET Command TREE ENABLE uses "(01 -BOX)" as the default value of this attribute. ENABLE obtains this value by appending the four characters -BOX to the application name specified in the ADD APPL command. Note that ENABLE uses the value of the TREE attribute to determine which box is associated with an application. If ENABLE supplies a default value for the TREE attribute, ENABLE checks to see if a box with the default name exists.
ENABLE COMMANDS SET Command Examples The following example sets a value for the box attributes RECORD and DATAFILE: SET BOX RECORD parts, DATAFILE part1 To set a value for the application attributes PATHCOMFILE and TITLE, you can enter: SET APPL PATHCOMFILE mypath, TITLE "Entry Screen" 3-30
ENABLE COMMANDS SHOW Command SHOW Command The SHOW command displays the contents of the attribute table. The syntax of the SHOW command is: ----------------------------------------------------------------| | | SHOW [ APPL ] [ ] | | [ BOX ] [ ABIlITY ] | | [ FORMAT ] | | [ INTEGRITY ] | | [ OTHER ] | | [ * ] | | | | APPL | | | | is a keyword that identifies application as the type of | | object whose attribute values are to be displayed.
ENABLE COMMANDS SHOW Command ----------------------------------------------------------------| | | Box Attributes: | | | | BOXTITLE EXCLUDE INSERT SERVERCLASS | | CHECKDATA FILL NONSTOP SIZE | | DATAFILE FLAG READ TMF | | DELETE HEADINGS RECORD UPDATE | | DICTIONARY INCLUDE SCREENFORMAT VALUES | | | | Application and box attributes are described in | | Section 4.
ENABLE COMMANDS SHOW Command ----------------------------------------------------------------| | | * | | | | indicates that the current values of all attributes for | | the named or default object type are to be displayed. | | | | If you do not specify an attribute or set of attributes, | | ENABLE displays current or default values for attributes | | of the object type in effect. Attributes with null values | | are omitted from display.
ENABLE COMMANDS SHOW Command Examples To obtain the value of the application attribute TREE, enter: SHOW APPL TREE ENABLE returns: TREE ?? To obtain the value of the box attribute RECORD, enter: SHOW BOX RECORD To display the values of all application attributes including those for which you have supplied values, those for which ENABLE can supply default values, and those which have non-null starting values, enter: SHOW APPL To obtain the values of all the application attributes including those that retai
SECTION 4 ENABLE ATTRIBUTES ENABLE attributes specify the characteristics of applications and boxes. Values are assigned to attributes using the commands described in Section 3. Table 4-1 summarizes the attributes that describe applications. Table 4-2 summarizes the attributes that describe boxes. The syntax, function, and possible values for all ENABLE attributes are described in alphabetical order on the pages that follow.
ENABLE ATTRIBUTES Summary of Attributes Table 4-1. Summary of Application Attributes (Continued next page) ----------------------------------------------------------------| | | Attribute Characteristic Starting Value | |_______________________________________________________________| | | | PATHCOMFILE Identifies the name Null (No PATHCOM | | of the PATHCOM file is | | command file. produced.) | | | | PATHCOMSKELETON Identifies the name ENABPATS on the | | of the PATHCOM volume and | | skeleton file.
ENABLE ATTRIBUTES Summary of Attributes Table 4-1. Summary of Application Attributes (Continued) ----------------------------------------------------------------| | | Attribute Characteristic Starting Value | |_______________________________________________________________| | | | TERMINAL Identifies the type The type of | | of terminal on terminal from | | which the which you enter | | application will the ENABLE commands | | run.
ENABLE ATTRIBUTES Summary of Attributes Table 4-2. Summary of Box Attributes (Continued next page) ----------------------------------------------------------------| | | Attribute Name Function Starting Value | |_______________________________________________________________| | | | Box Attributes That Affect Screen Format | |_______________________________________________________________| | | | BOXTITLE 1 Identifies text Null (No text | | BOXTITLE 2 that appears within Null appears.
ENABLE ATTRIBUTES Summary of Attributes Table 4-2. Summary of Box Attributes (Continued) ----------------------------------------------------------------| | | Attribute Name Function Starting Value | |_______________________________________________________________| | | | Box Attributes That Affect Screen Format (Continued) | |_______________________________________________________________| | | | VALUES Indicates whether OFF | | initial values from | | the record | | description appear | | within a box.
ENABLE ATTRIBUTES Summary of Attributes Table 4-2.
ENABLE ATTRIBUTES Summary of Attributes Table 4-2. Summary of Box Attributes (Continued) ----------------------------------------------------------------| | | Attribute Name Function Starting Value | |_______________________________________________________________| | | | Other Box Attributes | |_______________________________________________________________| | | | DATAFILE Identifies the name Null (A default value | | of a data base --from the DDL | | file.
ENABLE ATTRIBUTES BOXTITLE Attribute BOXTITLE Attribute The BOXTITLE attribute identifies up to three lines of text that are to appear within a box on the screen. The syntax of the BOXTITLE attribute is: ----------------------------------------------------------------| | | BOXTITLE { 1 } | | { 2 } | | { 3 } | | | | BOXTITLE 1 | | | | indicates that the associated is to | | appear on the first line of the box.
ENABLE ATTRIBUTES BOXTITLE Attribute Considerations When you specify a value for one of the BOXTITLE attributes, the text that you specify appears left-justified within the box on the screen. If the box is continued across several pages of the screen, the text appears at the top of the box on each screen page.
ENABLE ATTRIBUTES BOXTITLE Attribute Example If you generate an application by including the following series of commands: SET BOX BOXTITLE 1 " SET BOX BOXTITLE 2 " " SET BOX RECORD parts ADD BOX parts-1 SET APPL TREE (01 parts-1) SET APPL PATHCOMFILE newpath ADD APPL parts-show GENERATE APPL parts-show Part Information" the screen displayed by the application appears as shown in Figure 4-1. PARTS-SHOW Page 1/1 Part Information * PARTNUM _____ PARTNAME ______________________ .
ENABLE ATTRIBUTES CHECKDATA Attribute CHECKDATA Attribute The CHECKDATA attribute indicates whether the application does, or does not, contain special code that verifies the data type of data read from numeric fields in a data base file.
ENABLE ATTRIBUTES CHECKDATA Attribute Example The following command sets the value of the box attribute CHECKDATA to OFF: SET BOX CHECKDATA OFF 4-12
ENABLE ATTRIBUTES DATAFILE Attribute DATAFILE Attribute You can use the DATAFILE attribute to identify the data base file that a box represents. The syntax of the DATAFILE attribute is: ----------------------------------------------------------------| | | DATAFILE | | | | | | | | is the name of the file that the box represents and must | | have the following form: | | | | [\.][$.][.
ENABLE ATTRIBUTES DATAFILE Attribute Consideration ENABLE uses the value of the DATAFILE attribute when generating the PATHCOM command file. When you set a value for DATAFILE, you preclude any file name identified in the record description from being used. Examples Suppose that the following record description identifies more than one data base file: RECORD manager. FILE IS "employ" KEY-SEQUENCED. 02 empnum PIC 9(4). 02 empname PIC 9(18). 02 dept-id PIC 9(4). KEY 0 IS empnum. KEY "di" IS dept-id.
ENABLE ATTRIBUTES DELETE Attribute DELETE Attribute The DELETE attribute indicates whether the application can, or cannot, delete records from the file that a box represents. The syntax for the DELETE attribute is: ----------------------------------------------------------------| | | DELETE { ON } | | { OFF } | | | | ON | | | | indicates that the application can delete records from the | | data base file. | | | | OFF | | | | indicates that the application cannot delete records from | | the data base file.
ENABLE ATTRIBUTES DELETE Attribute Example Consider the value of the DELETE attribute in the following series of ENABLE commands: SET BOX DELETE OFF <----SET BOX RECORD parts ADD BOX parts-detail sets DELETE to OFF An application that uses the "parts-detail" box cannot delete records from the file that the box represents.
ENABLE ATTRIBUTES DICTIONARY Attribute DICTIONARY Attribute The DICTIONARY attribute identifies the location of the data dictionary from which ENABLE is to obtain a record description. The syntax of the DICTIONARY attribute is: ----------------------------------------------------------------| | | DICTIONARY { } | | { $. } | | { \.$. } | | | | | | | | identifies the subvolume where the dictionary resides.
ENABLE ATTRIBUTES DICTIONARY Attribute Examples The following commands obtain record descriptions from two different dictionaries within an ENABLE session. SET BOX DICTIONARY $mkt.sample1 SET BOX RECORD parts ADD BOX part-1 SET BOX DICTIONARY $mkt.
ENABLE ATTRIBUTES EXCLUDE Attribute EXCLUDE Attribute The EXCLUDE attribute identifies fields from a record description to be excluded from display within a box. The syntax of the EXCLUDE attribute is: ----------------------------------------------------------------| | | EXCLUDE { } | | { ( [ , ... ] ) } | | | | | | | | is the name of a field to be excluded.
ENABLE ATTRIBUTES EXCLUDE Attribute ENABLE cannot use a box for an application if you exclude: • All of the fields described in a record description. If you try to exclude all fields, ENABLE issues an error message stating that "All fields have been excluded from this box." • For any box except the box at the first level of the tree structure, all fields except the join field.
ENABLE ATTRIBUTES EXCLUDE Attribute Excluding an Elementary Item From a Group Key. If a group item is an alternate key field and you exclude the first elementary item from that group, the application will not use the group item as an alternate key. For example, consider the following record description: RECORD employee. FILE IS ... KEY-SEQUENCED. 02 empnum PIC 9(4). ... 02 dept. <-------------------04 regnum PIC 9(4). <--04 branchnum PIC 9(4). ... KEY 0 IS empnum. KEY "dp" IS dept.
ENABLE ATTRIBUTES EXCLUDE Attribute In this record description, the group A is a key field. Normally, the application would display this field as follows: * A AA AAA AAB AB AC ACA ACB where the asterisk (*) identifies A as a primary key field. In this case, the application can use the entire group as a key field. If you exclude ACB, for example, the application will display these fields as follows: A * AA AAA AAB AB AC ACA In this case, the application uses AA as a key field.
ENABLE ATTRIBUTES EXCLUDE Attribute Examples The following example excludes a single field: SET BOX EXCLUDE price The following example excludes several fields: SET BOX EXCLUDE (street, city, state, zipcode, telephone-number) 4-23
ENABLE ATTRIBUTES FILL Attribute FILL Attribute The FILL attribute indicates whether the application does, or does not, automatically read a record (or records) for a box under the conditions described below. The syntax of the FILL attribute is: ----------------------------------------------------------------| | | | | FILL { ON } | | { OFF } | | | | ON | | | | indicates that, under certain circumstances, the | | application is to perform an automatic read operation | | on the file that the box represents.
ENABLE ATTRIBUTES FILL Attribute • If the box has ON as the value of the VALUES attribute, the application, upon execution, automatically reads a record or records from the data base file by using the initial values in the record description as a starting point. If there are no records in the file, the application displays the initial values on the screen.
ENABLE ATTRIBUTES FILL Attribute Control Boxes. If a record description contains a DDL VALUE clause, you can use the box that represents this file as a control box. To do this, supply ON for both the FILL and the VALUES attributes, and identify the box as being at the highest level of the tree structure (the outermost box). For example, consider the the following partial record descriptions: RECORD region. FILE IS region KEY-SEQUENCED. 02 regnum PIC 9(4) VALUE IS 4.
ENABLE ATTRIBUTES FILL Attribute the application, upon execution, performs an initial read operation on the file represented by "region-box." If that file contains a record for region 4, the application retrieves that record. Because READ is set to OFF, the record for region 4 is the only record that the application can access. Because the application can only read one record for "region-box," it can only read records for "branch-box" if their join field value is 4.
ENABLE ATTRIBUTES FLAG Attribute FLAG Attribute You can use the FLAG attribute to set values for flags that can be referred to in the application skeleton. You can modify the application skeleton through special commands that ENABLE uses to test and act upon the value of a user flag.
ENABLE ATTRIBUTES FLAG Attribute Examples The following command sets user flag number 1 to 79: SET BOX FLAG 1 79 In the skeleton program, user flags have values from 101 to 200. The preceding command references flag number 101 in the skeleton program.
ENABLE ATTRIBUTES HEADINGS Attribute HEADINGS Attribute The HEADINGS attribute indicates the source of any screen-field labels that are to appear within the box. If screen-field labels are to appear, the value of this attribute indicates whether headings or field names from the record description are used as screen labels.
ENABLE ATTRIBUTES HEADINGS Attribute For compatibility with previous versions, ENABLE also supports the following values for the HEADINGS attribute: ON is synonymous with DDLHEADINGS OFF is synonymous with DDLFIELDNAMES Example If you generate an application by including the following commands: SET BOX RECORD parts SET BOX HEADINGS DDLHEADINGS
ENABLE ATTRIBUTES INCLUDE Attribute INCLUDE Attribute The INCLUDE attribute identifies fields from a record description that the application is to display within a box. This attribute also specifies the order in which the fields are to appear. Fields appear in the same order that you list them, and any field that you do not explicitly list with this attribute is omitted from the display.
ENABLE ATTRIBUTES INCLUDE Attribute • You must include any join fields for a box. (Refer to the TREE attribute for an explanation of a join field.) If a join field is a group field, you cannot reorder the items that make up that group. • If the value of the INSERT attribute is ON, you must include the primary key of a key-sequenced file or a unique alternate key for any file type.
ENABLE ATTRIBUTES INCLUDE Attribute In the "zip" record description, "abc" is a composite alternate key field made up of the elementary fields "a," "b," and "c." If you add a box with the following commands: SET BOX RECORD zip SET BOX INCLUDE (aaa,c, a, b) ADD BOX zipper the fields for box "zipper" will appear on the screen displayed by the application as: * AAA ABC C + A B _ ____ ____ ____ Notice that a plus sign appears before the screen label for field "A.
ENABLE ATTRIBUTES INCLUDE Attribute you reorder the elementary fields of both "aa" and "bb." Because these fields are reordered, an application that uses box "zing" displays these fields as follows: ABC BB DDD _ + AA BBB _ CCC _ BB EEE _ Notice that the application can use field "bbb," the first elementary field of the composite key "ABC," as an alternate key field.
ENABLE ATTRIBUTES INSERT Attribute INSERT Attribute The INSERT attribute indicates whether the application can, or cannot, add a record to the data base file represented by a box. The syntax of the INSERT attribute is: ----------------------------------------------------------------| | | INSERT { ON } | | { OFF } | | | | ON | | | | indicates that the application can add records to a data | | base file. | | | | OFF | | | | indicates that the application cannot add records to a data| | base file.
ENABLE ATTRIBUTES NONSTOP Attribute NONSTOP Attribute The NONSTOP attribute indicates whether the General Server is, or is not, to run as a NonStop process pair when accessing the data base file represented by a box. The syntax of the NONSTOP attribute is: ----------------------------------------------------------------| | | NONSTOP { ON } | | { OFF } | | | | ON | | | | indicates that the General Server is to run as a NonStop | | process pair.
ENABLE ATTRIBUTES NONSTOP Attribute Example If you generate an application by including the following commands: SET BOX NONSTOP ON SET BOX SERVERCLASS e-nonstop SET BOX RECORD parts ADD BOX parts-1 BOX RECORD orders ADD BOX orders RESET BOX NONSTOP SET BOX SERVERCLASS tmf-serve SET BOX TMF ON SET BOX RECORD supplier ADD BOX supplier-1 RESET BOX * a copy of the General Server identified by the name "e-nonstop" accesses the files represented by the "parts-1" and "orders" boxes.
ENABLE ATTRIBUTES PATHCOMFILE Attribute PATHCOMFILE Attribute The PATHCOMFILE attribute identifies the file to which ENABLE writes the set of PATHCOM commands it produces. These PATHCOM commands are used to configure a PATHWAY system under which the application runs.
ENABLE ATTRIBUTES PATHCOMFILE Attribute ENABLE issues an error message if: • A file named already exists but you do not specify the ! symbol. • You specify the ! symbol but is not an edit-type file.
ENABLE ATTRIBUTES PATHCOMSKELETON Attribute PATHCOMSKELETON Attribute The PATHCOMSKELETON attribute identifies the file that ENABLE is to use as the PATHCOM skeleton. (ENABLE uses this file when generating the PATHCOM command file.) The syntax of the PATHCOMSKELETON attribute is: ----------------------------------------------------------------| | | PATHCOMSKELETON | | | | NOTE: APPL must be the object type in effect when you | | supply a value for this application attribute.
ENABLE ATTRIBUTES PATHCOMSKELETON Attribute Example The following example identifies "$mkt.sample.pathskel" as the name of the file to be used as the PATHCOM skeleton: SET APPL PATHCOMSKELETON $mkt.sample.
ENABLE ATTRIBUTES READ Attribute READ Attribute The READ attribute indicates whether the application can read a record or records from the data base file represented by the box. The syntax for the READ attribute is: ----------------------------------------------------------------| | | READ { ON } | | { OFF } | | | | ON | | | | indicates that the application can read a record or | | records from the data base file.
ENABLE ATTRIBUTES READ Attribute Example An application generated with the following commands cannot read records for the "parts-1" box, but can read records for the "supplier-1" and "order" boxes: SET BOX DELETE OFF, UPDATE OFF SET BOX READ OFF <----------SET RECORD parts ADD BOX parts-1 RESET BOX READ <------------SET BOX RECORD supplier ADD BOX supplier-1 SET BOX RECORD orders ADD BOX order 4-44 sets READ to OFF resets READ to ON
ENABLE ATTRIBUTES RECORD Attribute RECORD Attribute The RECORD attribute identifies the name of the record description used for the box. ENABLE uses the record description to determine the record, fields, and structure of the data base file represented by a box. The syntax of the RECORD attribute is: ----------------------------------------------------------------| | | RECORD | | | | | | | | is the name of the record description.
ENABLE ATTRIBUTES RECORD Attribute Example The following command identifies a record description named "parts": SET BOX RECORD parts 4-46
ENABLE ATTRIBUTES SCOBOLCOMPILER Attribute SCOBOLCOMPILER Attribute The SCOBOLCOMPILER attribute identifies the SCREEN COBOL compiler that produces object code for an application. The syntax of the SCOBOLCOMPILER attribute is: ----------------------------------------------------------------| | | SCOBOLCOMPILER [ ] | | | | NOTE: APPL must be the object type in effect when you | | supply a value for this application attribute.
ENABLE ATTRIBUTES SCOBOLCOMPILER Attribute Example The following command specifies the SCREEN COBOL compiler "$mkt.sample.scobolx." SET APPL SCOBOLCOMPILER $mkt.sample.
ENABLE ATTRIBUTES SCOBOLLIST Attribute SCOBOLLIST Attribute The SCOBOLLIST attribute identifies the file to which ENABLE directs a compilation listing of the SCREEN COBOL program. The syntax of the SCOBOLLIST attribute is: ----------------------------------------------------------------| | | SCOBOLLIST [ [!] ] | | | | NOTE: APPL must be the object type in effect when you | | supply a value for this application attribute.
ENABLE ATTRIBUTES SCOBOLLIST Attribute Example The following command identifies "$mkt.sample.list" as the file to which the SCREEN COBOL compilation listing is to be directed: SET APPL SCOBOLLIST $mkt.sample.
ENABLE ATTRIBUTES SCOBOLOBJECT Attribute SCOBOLOBJECT Attribute The SCOBOLOBJECT attribute identifies the object file to which the SCREEN COBOL compiler directs the compiled SCREEN COBOL program. The syntax of the SCOBOLOBJECT attribute is: ----------------------------------------------------------------| | | SCOBOLOBJECT [ ] | | | | NOTE: APPL must be the object type in effect when you | | supply a value for this application attribute.
ENABLE ATTRIBUTES SCOBOLOBJECT Attribute Consideration If you want to obtain SCREEN COBOL source code before using the application, you can set a value for SCOBOLSOURCE and enter the SCOBOLOBJECT attribute without a value for the parameter. If you do this, you must compile the SCREEN COBOL source code and edit the generated PATHCOM file before you execute the application. Example The following command identifies "$mkt.sample.
ENABLE ATTRIBUTES SCOBOLSKELETON Attribute SCOBOLSKELETON Attribute The SCOBOLSKELETON attribute identifies the file that ENABLE is to use as the SCREEN COBOL skeleton. The syntax of the SCOBOLSKELETON attribute is: ----------------------------------------------------------------| | | SCOBOLSKELETON | | | | NOTE: APPL must be the object type in effect when you | | supply a value for this application attribute. | | | | | | | | is the name of a SCREEN COBOL application skeleton.
ENABLE ATTRIBUTES SCOBOLSKELETON Attribute Example The following command identifies "$mkt.sample.scobskel" as the name of the file that ENABLE is to use as the SCREEN COBOL skeleton file: SET APPL SCOBOLSKELETON $mkt.sample.
ENABLE ATTRIBUTES SCOBOLSOURCE Attribute SCOBOLSOURCE Attribute The SCOBOLSOURCE attribute identifies a file to which ENABLE writes the SCREEN COBOL source code. The syntax for the SCOBOLSOURCE attribute is: ----------------------------------------------------------------| | | SCOBOLSOURCE [!] | | | | NOTE: APPL must be the object type in effect when you | | supply a value for this application attribute.
ENABLE ATTRIBUTES SCOBOLSOURCE Attribute To compile the SCREEN COBOL source code, you can enter the SCREEN COBOL COMPILER command from the command interpreter using the following syntax: ----------------------------------------------------------------| | | SCOBOLX /IN , OUT , MEM 64, | | NOWAIT/ | | | | | | | | is the name of the file that contains the modified | | SCREEN COBOL source code.
ENABLE ATTRIBUTES SCOBOLSOURCE Attribute Example The following command identifies "$mkt.sample.scsource" as the name of the file to which ENABLE is to write the SCREEN COBOL source code: SET APPL SCOBOLSOURCE $mkt.sample.
ENABLE ATTRIBUTES SCREENFORMAT Attribute SCREENFORMAT Attribute The SCREENFORMAT attribute indicates the screen layout scheme for a box. The syntax for the SCREENFORMAT attribute is: ----------------------------------------------------------------| | | SCREENFORMAT { UNCOMPRESSED } | | { COMPRESSED } | | | | | | UNCOMPRESSED | | | | indicates that each screen line in the box is to display | | at most one screen field.
ENABLE ATTRIBUTES SCREENFORMAT Attribute For example, consider the following record description: RECORD employee. FILE IS employee KEY-SEQUENCED. 02 empnum PIC 9(4). 02 empname PIC X(18). 02 dept. 04 regnum PIC 99. 04 branchnum PIC 99. 02 job PIC X(12). 02 age PIC 99. 02 salary PIC 9999V99. 02 vacation PIC 99. KEY 0 IS empnum. KEY "en" IS empname. KEY "dp" IS dept.
ENABLE ATTRIBUTES SCREENFORMAT Attribute EMPLOYEE-COMPRES Page 1/1 * EMPNUM ________ * EMPNAME ____________ + DEPT REGNUM ______ BRANCHNUM ______ .00 JOB _________________ AGE ___ SALARY _______ Ready for input VACATION ___ F3 for Help, shift F16 to exit S5043-019 Figure 4-2. Sample Screen With SCREENFORMAT COMPRESSED Notice that the screen labels and fields for "regnum" and "branchnum" appear on the screen line following the label for the "dept" group.
ENABLE ATTRIBUTES SCREENFORMAT Attribute Example The following command sets SCREENFORMAT to COMPRESSED: SET BOX SCREENFORMAT COMPRESSED 4-61
ENABLE ATTRIBUTES SERVERCLASS Attribute SERVERCLASS Attribute The SERVERCLASS attribute identifies the name of the server class to which the General Server belongs. The syntax of the SERVERCLASS attribute is: ----------------------------------------------------------------| | | SERVERCLASS | | | | | | | | identifies the name of a server class. ENABLE uses this | | name in the generated SCREEN COBOL program and in the | | PATHCOM command file.
ENABLE ATTRIBUTES SERVERCLASS Attribute • For some boxes used by the application the value of TMF is ON, and for other boxes used by the application the value of NONSTOP is ON (indicating that the General Server is to run as a NonStop process pair). • For some boxes used by the application the value of NONSTOP is ON, and for other boxes the value of NONSTOP is OFF.
ENABLE ATTRIBUTES SIZE Attribute SIZE Attribute The SIZE attribute specifies the number of records that the application displays within a box on the screen. The syntax of the SIZE attribute is: ----------------------------------------------------------------| | | SIZE | | | | | | | | is a positive integer that defines the number of records | | that the application can display within the box.
ENABLE ATTRIBUTES SIZE Attribute Multifile Considerations. If you want to display more than one record in a box for a multifile application, consider the relationship between the records in the parent and child boxes when you supply a value for SIZE: • If a one-to-one relationship exists between the parent and child box, a value of one should be supplied for both parent and child. A one-to-one relationship exists if one record for a child box has the same join field value as one record for a parent box.
ENABLE ATTRIBUTES TERMINAL Attribute TERMINAL Attribute The TERMINAL attribute identifies the type of terminal upon which the application can run. The syntax of the TERMINAL attribute is: ----------------------------------------------------------------| | | TERMINAL | | | | NOTE: APPL must be the object type in effect when you | | supply a value for this application attribute. | | | | | | | | identifies the type of terminal upon which the | | application can run.
ENABLE ATTRIBUTES TERMINAL Attribute Example The following command sets the TERMINAL attribute to T16-653x: SET APPL TERMINAL T16-6530 4-67
ENABLE ATTRIBUTES TITLE Attribute TITLE Attribute The TITLE attribute specifies the title that appears left-justified on the first line of each screen. The syntax of the TITLE attribute is: ----------------------------------------------------------------| | | TITLE | | | | NOTE: APPL must be the object type in effect when you | | supply a value for this application attribute. | | | | | | | | is the screen title.
ENABLE ATTRIBUTES TMF Attribute TMF Attribute The TMF attribute indicates whether the data base file represented by the box is, or is not, audited by the Transaction Monitoring Facility (TMF). The syntax of the TMF attribute is: ----------------------------------------------------------------| | | TMF { ON } | | { OFF } | | | | ON | | | | indicates that the data base file is audited by TMF. | | | | OFF | | | | indicates that the data base file is not audited by TMF.
ENABLE ATTRIBUTES TMF Attribute For the same box, you cannot supply ON as the value for both TMF and NONSTOP. ENABLE allows you to generate an application that uses some boxes with TMF ON and other boxes with TMF OFF. If you do this, the value of the SERVERCLASS attribute must be different for both categories of boxes.
ENABLE ATTRIBUTES TREE Attribute TREE Attribute The TREE attribute associates a box, or set of boxes, with an application. It specifies a hierarchical relationship between the boxes. Based on this logical structure, the application determines the access path to records for display within a child box. The syntax of the TREE attribute is: ----------------------------------------------------------------| | | TREE ( | | | | [ ] ...
ENABLE ATTRIBUTES TREE Attribute ----------------------------------------------------------------| | | | | | | is one of: | | | | LINK TO OPTIONAL | | | | or | | | | LINK TO OPTIONAL VIA | | | | The associates a parent box with | | a child box, and is further described under | | Considerations.
ENABLE ATTRIBUTES TREE Attribute ----------------------------------------------------------------| | | The starting value of the TREE attribute is null. For | | single-file applications, ENABLE uses | | "( 01 -BOX )" as the default value of the | | TREE attribute, where is the name | | specified when you enter either an ADD APPL or a GENERATE | | command.
ENABLE ATTRIBUTES TREE Attribute The tree structures for several multifile applications are symbolically represented in Figure 4-3.
ENABLE ATTRIBUTES TREE Attribute What is a LINK? A link is the portion of a tree structure that defines the logical connection between two boxes. While a tree structure can contain multiple links that connect the same box to several other boxes, a single link connects only two boxes.
ENABLE ATTRIBUTES TREE Attribute The order that you define with a LINK OPTIONAL establishes a dependency between the records associated with both boxes. When you define a LINK OPTIONAL, you indicate that the application is to use the join field value of a record from one box to read or insert a record in the other box. Thus, the records in the second box can be said to depend on a matching record in the first box for access by the application. Records match if their join field values are the same.
ENABLE ATTRIBUTES TREE Attribute EMPLOYEE-EXAMPLE Page 1/1 * EMPNO ________ Read a record for employee number 0003 DEPENDENT-NAME ___________________ AGE ____ SEX ____ + EMPNAME DEPT REGNUM BRANCHNUM JOB AGE SALARY VACATION ________________________ _____ _____ ____________ _____ .
ENABLE ATTRIBUTES TREE Attribute The screen displayed by an application reflects the parent-child relationship established by a LINK OPTIONAL. On the screen, an application always displays the join field of the parent box on the screen line that directly precedes the child box. The application does not display the join field of the child box. Figure 4-6 shows the screen displayed by an application that uses "employee-box" as the parent and "depend-box" as the child.
ENABLE ATTRIBUTES TREE Attribute Determining Appropriate Join Fields. To find potential join fields, examine the record descriptions associated with both boxes. These record descriptions must describe matching fields. Fields match if they have compatible data types. You obtain the data type of a associated with that field in data types of both fields are potential join fields. Table types. Table 4-3. field from the PIC clause the record description.
ENABLE ATTRIBUTES TREE Attribute To determine if potential join fields are appropriate, consider the data values that the fields represent. Appropriate join fields should represent the same data values. Although ENABLE will allow you to link two boxes whose join fields represent different kinds of data values, avoid doing this because an application generated with such a link might not operate in the manner you expect.
ENABLE ATTRIBUTES TREE Attribute Choosing the Parent and Child Box. To determine which box is to be the parent box and which box is to be the child box, consider the purpose for which you are generating the application. Under most circumstances, you should make the box associated with the records in which you are most interested the parent box. Remember, the application cannot read or insert a record for the child box unless a matching record exists for the parent box.
ENABLE ATTRIBUTES TREE Attribute 2. The join field of a child box must be a primary key field, an alternate key field, a courtesy key field, or the leading (leftmost) portion of a composite key field. Alternate keys are not recognized within child boxes. To provide a key for the subset of records that match the join field within the child box, use the leftmost portion of a composite key field for the parent join field. Use the entire composite key field for the child join field.
ENABLE ATTRIBUTES TREE Attribute Since you connect the levels of the tree structure with links, you must define the level of a parent box as being lower than its corresponding child box. Depending on how you define the links and levels within your tree structure, a box can be the parent of several boxes at a higher level of the tree structure and the child of a box in a lower level of the tree. Although a box can be the parent of several other boxes, a box cannot be the child of more than one box.
ENABLE ATTRIBUTES TREE Attribute • The level for the box at the first level of the tree structure must be lower in value than any other level that appears in the tree structure. • When you define a level for the box at the first level of the tree, do not include the LINK OPTIONAL. • When you define level numbers for boxes at subsequent levels of the tree structure, these level numbers must be higher in value than any box defined at a lower level in the tree structure.
ENABLE ATTRIBUTES TREE Attribute Suppose, for example, that you want to generate an application that displays information about departments and the employees that belong to those departments.
ENABLE ATTRIBUTES TREE Attribute Since the application is to display information about departments and the employees assigned to those departments, "depart-box" should be the parent box and "employ-box" the child box. The join fields of these boxes are "dept-no" and "dept-num" respectively. To build a tree structure for this application, set a value for the TREE attribute as follows: 1.
ENABLE ATTRIBUTES TREE Attribute This value for the TREE attribute builds the tree structure shown in Figure 4-9. Level 1 Depart-box dept-no dept-name dept-loc Logical Link Between Boxes Level 2 Employ-box empnum empname dept-num S5043-025 Figure 4-9.
ENABLE ATTRIBUTES TREE Attribute DEPT-EMPLOY Page 1/1 * DEPT-NO EMPNUM EMPNAME + DEPT-NAME DEPT-LOC _______ _______ ___________________ ____________ ________________________ Join field for depart-box Labels and fields for employ-box Remaining labels and fields for depart-box Ready for input F3 for Help, shift F16 to exit S5043-026 Figure 4-10.
ENABLE ATTRIBUTES TREE Attribute • "employ-box," which represents a file that contains information about employees • "depends-box," which represents a file that contains information about the dependents of employees Figure 4-11 shows part of the record descriptions for these boxes and also shows the partial contents of the files represented by the boxes. Join Fields for Employ-box and Depart-box Join Fields for Depend-box and Employ-box RECORD dependents FILE IS depend ...
ENABLE ATTRIBUTES TREE Attribute Depending on the purpose of the application, any of the three boxes could be at the first level of the tree structures. These boxes could be at the first level because appropriate join fields exist to link the boxes together. Because the main purpose of the application is to display information about departments, "depart-box" should be at the first level of the tree structure.
ENABLE ATTRIBUTES TREE Attribute 5. Identify "depends-box" as being at the third level of the tree: SET APPL TREE (02 depart-box 04 employ-box LINK dept-no TO OPTIONAL dept-num 06 depends-box 6. Provide the LINK OPTIONAL that connects "depends-box" to "employ-box": LINK employ-box TO OPTIONAL depends-box VIA empnum | | | | | Name of join | | field for both | | boxes | | | Name of child box | Name of parent box 7.
ENABLE ATTRIBUTES TREE Attribute Level 1 Depart-box dept-no dept-name dept-loc Link Between Boxes Level 2 Employ-box empnum empname dept-num Link Between Boxes Level 3 Depends-box depent-key empnum dep-no dep-name S5043-028 Figure 4-12.
ENABLE ATTRIBUTES TREE Attribute Upon execution, the "dept-detail" application will display the screen shown in Figure 4-13.
ENABLE ATTRIBUTES TREE Attribute Since the purpose of this application is to display information about departments, "depart-box" should be at the first level of the tree structure. "Employ-box" must be at the second level of the tree because this is the only box used by the application that can be linked to "depart-box." (The other boxes do not have appropriate join fields.) Both "depends-box" and "benefits-box" have join fields that would allow you to link them either to "employ-box" or to each other.
ENABLE ATTRIBUTES TREE Attribute RECORD department FILE IS depart ... 02 dept-no PIC 9(6) 02 dept-name ... 02 dept-loc ... KEY 0 IS dept-no KEY "dp" IS dept-name END Partial Contents of File Represented by Depart-Box dept-no 0001 0002 0003 0004 0005 ••• ••• ••• ••• ••• ••• ••• ••• ••• ••• ••• RECORD employee FILE IS employee ... 02 empnum PIC 9(4) 02 empname ... 02 dept-num PIC 9(6) KEY 0 IS empnum KEY "dn" IS dept-num END RECORD dependents FILE IS depend ...
ENABLE ATTRIBUTES TREE Attribute To build this tree structure for an application, you set a value for the TREE attribute as follows: 1. Identify "depart-box" as being at the first level of the tree structure: SET APPL TREE (02 depart-box 2. Identify "employ-box" as being at the second level of the tree structure: SET APPL TREE (02 depart-box 04 employ-box 3.
ENABLE ATTRIBUTES TREE Attribute 7. Include the LINK OPTIONAL in Step 6 with the part of the TREE value that defines a level for "depends-box": SET APPL TREE (02 depart-box 04 employ-box LINK dept-no TO OPTIONAL dept-num 06 depends-box LINK employ-box TO OPTIONAL depends-box VIA empnum 8. Identify the level of "benefits-box": SET APPL TREE (02 depart-box 04 employ-box LINK dept-no TO OPTIONAL dept-num 06 depends-box LINK employ-box TO OPTIONAL depends-box VIA empnum 06 benefits-box 9.
ENABLE ATTRIBUTES TREE Attribute Level 1 Depart-box dept-no dept-name dept-loc Link Between Boxes Level 2 Employ-box empnum empname dept-num Links Between Boxes Level 3 Level 3 Depends-box depent-key empnum dep-no dep-name Benefits-box emp-no coverage-type S5043-031 Figure 4-15.
ENABLE ATTRIBUTES TREE Attribute You could generate an application that uses the tree structure shown in Figure 4-15 by entering the following ENABLE commands: ADD ADD ADD ADD SET SET BOX depart-box, RECORD department BOX employ-box, RECORD employee BOX depends-box, RECORD dependents BOX benefits-box, RECORD benefits APPL PATHCOMFILE p7 APPL TREE (02 depart-box 04 employ-box LINK dept-no TO OPTIONAL dept-num 06 depends-box LINK employ-box TO OPTIONAL depends-box VIA empnum 06 benefits-box LINK empnum TO OP
ENABLE ATTRIBUTES TREE Attribute More TREE Attribute Examples. The following TREE attribute associates a box with a single-file application: SET APPL TREE (02 employee) Consider the following TREE attribute, which identifies three boxes for a multifile application: "odetail," "order," and "parts.
ENABLE ATTRIBUTES TREE Attribute The following TREE attribute identifies the level number of each box and the join field that links each box to a higher level box.
ENABLE ATTRIBUTES UPDATE UPDATE Attribute The UPDATE attribute indicates whether the application can, or cannot, update records in the data base file represented by the box. The syntax of the UPDATE attribute is: ----------------------------------------------------------------| | | UPDATE { ON } | | { OFF } | | | | ON | | | | indicates that the application can update records in the | | data base file. | | | | OFF | | | | indicates that the application cannot update records in | | the data base file.
ENABLE ATTRIBUTES VALUES Attribute VALUES Attribute The VALUES attribute indicates that the application is, or is not, to display initial values from the record description on the base screen (the screen that appears when you first execute the application) within a box.
SECTION 5 OPERATING COMMANDS The ENABLE operating commands perform the following functions: • Stop ENABLE (EXIT) • Display the syntax of the ENABLE commands (HELP) • Direct the output listing to a specified file (OUT) • Edit or repeat a command line (FC) • Display the current setting of the environmental parameters (ENV) • Enter commands from a specified file (OBEY) • Set the default system, volume, and subvolume for expansion of file names (CMDSYS, CMDVOL, OBEYSYS, OBEYVOL, SYSTEM, and VOLUME
OPERATING COMMANDS File Name Expansion FILE NAME EXPANSION To refer to Tandem files, use either "local," or "network" file names. Local File Names The local form identifies files on a single Tandem system. If the file is not in your current subvolume or volume, you must qualify the name with a specific subvolume or volume. The syntax for local file names is: ----------------------------------------------------------------| | | [$.][.
OPERATING COMMANDS Network File Names Network File Names The network form identifies files on remote systems. for network file names is: The syntax ----------------------------------------------------------------| | | \.$.. | | | | identifies a specific system within a | | network. This name may be up to seven | | characters long. | | | | identifies a physical disc pack mounted | | on a disc drive.
OPERATING COMMANDS Network File Names The file system identifies devices (such as tape drives or printers) in a similar manner; for example: \tsb.$tape1 specifies the tape drive "$tape1" on system "\tsb." Although the file system uses expanded file names internally, you can specify a partial name when entering commands. At a minimum, you must supply the to identify a file on the default system, volume and subvolume associated with your command interpreter.
OPERATING COMMANDS CMDSYS Command CMDSYS Command The CMDSYS command sets the default system for expansion of file names other than obey file names. The syntax of the CMDSYS command is: ----------------------------------------------------------------| | | CMDSYS [ \ ] | | | | | | | | is a GUARDIAN system name. | | | | The initial CMDSYS setting is the system in effect when you | | start ENABLE.
OPERATING COMMANDS CMDVOL Command CMDVOL Command The CMDVOL command sets the default volume and subvolume names for expansion of file names other than obey file names. The syntax of the CMDVOL command is: ----------------------------------------------------------------| | | CMDVOL { $ } | | { $. } | | { } | | | | | | | | is a GUARDIAN volume name. | | | | | | | | is a GUARDIAN subvolume name.
OPERATING COMMANDS CMDVOL Command Examples The following are examples of the CMDVOL command: CMDVOL $mkt.
OPERATING COMMANDS ENV Command ENV Command The ENV command displays the current settings of program environment parameters.
OPERATING COMMANDS EXIT Command EXIT Command The EXIT command stops ENABLE.
OPERATING COMMANDS FC Command FC Command The FC command lets you edit or repeat a command line. syntax of the FC command is: The ----------------------------------------------------------------| | | FC | | | ----------------------------------------------------------------When this command is used, it displays up to 132 characters of the previous command line and then prompts for input with a period (.). To repeat the previous command, press RETURN after the period prompt (.).
OPERATING COMMANDS FC Command If you want to specify more than one subcommand on a line, you can separate the subcommands by entering a double slash. For example: %set boz record eemployee . x// d <---- The character "z" is replaced by "x," since replacement is the default subcommand. The extra "e" is deleted After you edit the line, FC displays the modified command line and prompts for another subcommand. FC terminates when you enter only a carriage return in response to the prompt.
OPERATING COMMANDS FC Command %set boz recordemployee . i <------ %set boz record employee . rx <-------------%set box record employee . <---------------------- 5-12 A blank is inserted by pressing the space bar following the I subcommand. The letter "z" is replaced by the letter x. The RETURN key indicates that editing is complete. ENABLE accepts the edited command.
OPERATING COMMANDS HELP Command HELP Command The HELP command displays the syntax of ENABLE commands. syntax of the HELP command is: The ----------------------------------------------------------------| | | HELP [ ] | | [ {<}{>} ] | | | | | | | | is the name of an ENABLE command for which the syntax is | | to be displayed. | | | | | | | | is any symbol that is enclosed in angle brackets when | | displayed by the option.
OPERATING COMMANDS OBEY Command OBEY Command The OBEY command causes commands to be read from a specified file. The syntax of the OBEY command is: ----------------------------------------------------------------| | | OBEY | | | | | | | | is a Tandem file name. | | | ----------------------------------------------------------------- Considerations If you do not supply a complete file name, ENABLE expands the obey file name with the default OBEYSYS and OBEYVOL settings.
OPERATING COMMANDS OBEY Command If the original input file for ENABLE was a terminal, ENABLE issues a prompt to the terminal. If the input file was not a terminal, ENABLE terminates. Example To tell ENABLE to read commands from a file named "enabcom" on a subvolume named "abc," enter: OBEY abc.
OPERATING COMMANDS OBEYSYS Command OBEYSYS Command The OBEYSYS command sets the default system for expansion of obey file names. The syntax of the OBEYSYS command is: ----------------------------------------------------------------| | | OBEYSYS [ \ ] | | | | | | | | is a GUARDIAN system name. | | | | The initial OBEYSYS setting is the system in effect when | | you start ENABLE.
OPERATING COMMANDS OBEYVOL Command OBEYVOL Command The OBEYVOL command sets the default volume and subvolume for expansion of obey file names. The syntax of the OBEYVOL command is: ----------------------------------------------------------------| | | OBEYVOL { $ } | | { $. } | | { } | | | | | | | | is a GUARDIAN volume name. | | | | | | | | is a GUARDIAN subvolume name.
OPERATING COMMANDS OBEYVOL Command Example The following OBEYVOL command identifies "$mkt.abc" as the default volume and subvolume with which obey file names are to be expanded: OBEYVOL $mkt.
OPERATING COMMANDS OUT Command OUT Command The OUT command directs the output listing to a specified file. The syntax of the OUT command is: ----------------------------------------------------------------| | | OUT | | | | or | | | | /OUT / | | | | | | | | is a Tandem file name. | | | | | | | | is an ENABLE command or an ENABLE Operating command. | | | | | | | | is a valid parameter for that command.
OPERATING COMMANDS OUT Command • ENABLE cannot open . Examples The following OUT command permanently directs the ENABLE output listing to the file "enabout." OUT enabout In the following example, output is temporarily directed to the spooler: HELP/OUT $s.
OPERATING COMMANDS SYSTEM Command SYSTEM Command The SYSTEM command sets the default system for expansion of all file names. The syntax of the SYSTEM command is: ----------------------------------------------------------------| | | SYSTEM [ \ ] | | | | | | | | is a GUARDIAN system name. | | | | The initial SYSTEM setting is the system in effect when you | | start ENABLE.
OPERATING COMMANDS VOLUME Command VOLUME Command The VOLUME command sets the default volume and subvolume for expansion of all file names. The syntax of the VOLUME command is: ----------------------------------------------------------------| | | VOLUME { $ } | | { $. } | | { } | | | | | | | | is a GUARDIAN volume name. | | | | | | | | is a GUARDIAN subvolume name.
OPERATING COMMANDS VOLUME Command A subsequent command of "VOLUME x" yields: $v1.x for OBEYVOL, and $v2.x for CMDVOL. ENABLE displays an error message and does not change the default OBEYVOL setting under the following conditions: • Either $ or is an invalid name. • Either $ or is invalid when expanded using the current defaults.
SECTION 6 APPLICATION EXECUTION After you generate an application, you must establish a PATHWAY system to execute the application. To establish a PATHWAY system, you enter commands that: • Create a PATHWAY Monitor (PATHMON) process, which is the central controlling process of a PATHWAY system • Create a PATHCOM process.
APPLICATION EXECUTION Establishing a PATHWAY System ----------------------------------------------------------------| | | PURGE , | | CREATE | | ASSIGN PATHCTL, | | PATHMON/NAME , NOWAIT, CPU 0, OUT / | | PATHCOM/IN / | | PATHCOM ;RUN | | PATHCOM ; SHUTDOWN, WAIT | | | | | | | | is a file to which PATHMON can report errors and ch
APPLICATION EXECUTION Establishing a PATHWAY System ----------------------------------------------------------------| | | | | | | is the name of the PATHCOM command file created by | | ENABLE. ENABLE creates this file if you supply a value | | for the PATHCOMFILE attribute when you generate an | | application. | | | | | | | | is the name of the generated application.
APPLICATION EXECUTION Executing the Obey File PATHCOM ; RUN Executes an application. PATHCOM ; SHUTDOWN, WAIT Stops the PATHWAY system. Figure 6-2 shows a sample obey file that uses these commands.
APPLICATION EXECUTION Establishing a PATHWAY System for Two or More Users To avoid the time involved in configuring the PATHWAY system, you can start PATHWAY in a cool state by entering the commands shown in Figure 6-3. A cool state is one in which a previous PATHWAY configuration exists. When you start PATHWAY in a cool state, PATHMON uses the configuration information stored in the existing assigned PATHCTL file.
APPLICATION EXECUTION Establishing a PATHWAY System for Two or More Users ----------------------------------------------------------------| | | PURGE log1, enabctl | | CREATE log1 | | ASSIGN PATHCTL, enabctl | | PATHMON/ NAME $one, NOWAIT, CPU 0, OUT log1/ | | PATHCOM/ IN enabpath/$one | | | ----------------------------------------------------------------Figure 6-4.
SECTION 7 ENABLE SCREENS Standard ENABLE screens: applications display the following terminal • A screen through which you can retrieve or update records stored in data base files • A screen that displays text that briefly describes the way you use an ENABLE application STANDARD SCREEN FORMATS The following paragraphs describe the format of the standard screens through which you can retrieve and update records using both single-file and multifile applications.
ENABLE SCREENS Standard Screen Formats HEADINGS The value of this attribute indicates the type of labels, if any, that the application uses to identify fields on the screen. The starting value of this attribute is DDLFIELDNAMES, meaning the application displays field names from the record description as screen labels. INCLUDE The value of this attribute identifies the order in which the application displays screen field and label pairs.
ENABLE SCREENS Standard Screen Format for a Single-File Application Standard Screen Format for a Single-File Application Figure 7-1 shows a record description and a series of ENABLE commands used to generate a single-file application. ----------------------------------------------------------------| | | Record Description: | | | | RECORD employee. | | FILE IS employee KEY-SEQUENCED. | | 02 empnum PIC 9(4). | | 02 empname PIC X(18). | | 02 dept. | | 04 regnum PIC 9(2). | | 04 branchnum PIC 9(2).
ENABLE SCREENS Standard Screen Format for a Single-File Application ----------------------------------------------------------------| | | EMPLOYEE-PROG (1) | | Page 1/1 (2) | | * EMPNUM ____ (3) | | + EMPNAME ____________________ (4) | | + DEPT (5) | | REGNUM __ (6) | | BRANCHNUM __ (7) | | JOB __________ (8) | | AGE __ (9) | | SALARY .00 (10) | | VACATION ___ (11) | | . | | . | | .
ENABLE SCREENS General Format of the Standard Screen ----------------------------------------------------------------| | | (5-7) The screen label and field pairs for a group: | | | | + DEPT | | REGNUM __ | | BRANCHNUM __ | | | | Notice that: | | | | • A screen field does not appear with the group | | label (DEPT). | | | | • The elementary items (REGNUM and BRANCHNUM) | | of the group appear on the screen lines | | following the group label.
ENABLE SCREENS General Format of the Standard Screen Line 2 also displays a message when the application has performed a successful read operation. The message indicates the type of read operation performed and the name of the key field that was used. You can use this information to determine how the application will process a READ NEXT operation. • Lines 3 through 20 display screen label and field pairs. • Line 23 displays a message whenever the application successfully completes an operation.
ENABLE SCREENS General Format of the Standard Screen • Each new level of a nested group field appears indented two screen columns. If the leftmost character of a label reaches screen column 30, the remaining group items begin in the same screen column as the label for which the leftmost character reached column 30. • An asterisk (*) that appears to the left of a screen label identifies the primary key of a key-sequenced file and the courtesy key (the record number) of other file types.
ENABLE SCREENS General Format of the Standard Screen Field as Defined in a Record Description Resulting Data Type Field as Displayed on the Screen_____ 02 sex Alphabetic SEX 02 location PIC X(3). Alphanumeric LOCATION ___ 02 age Numeric AGE __ 02 emp-no PIC 9(8) USAGE IS COMP. Numeric EMP-NO __________ 02 vacation PIC S9(2). Numeric VACATION ___ PIC A. PIC 99. _ For T16-651x terminals, underscore characters (_) indicate field length.
ENABLE SCREENS General Format of the Standard Screen • Numeric Noninteger (PIC 9 V) You can enter digits and a decimal point character in these fields. When you enter digits, you must align them with the decimal point. For all fields, you can enter up to the number of characters identified by the UNDERLINE attribute or underscore characters. For the Record Number field of entry-sequenced, relative, or unstructured files, you can enter up to eight digits.
ENABLE SCREENS General Format of the Standard Screen When you enter a value in the last screen field, the cursor returns to the first screen field. For applications generated for T16-652x, T16-653x, and IBM-327x terminals, the cursor does not automatically tab to the next screen field when positioned in a key field, the last subentry of a group key field, or the last field of a nested box.
ENABLE SCREENS Standard Screen Format for a Multifile Application Standard Screen Format for a Multifile Application Figure 7-3 shows the record descriptions and ENABLE commands used to generate a sample multifile application. ----------------------------------------------------------------| | | Record Descriptions: | | | | RECORD parts. | | FILE IS parts KEY-SEQUENCED. | | 02 partnum PIC 9(4). | | 02 partname PIC X(20). | | 02 price PIC 999999V99. | | KEY 0 IS partnum. | | KEY "pn" IS partname.
ENABLE SCREENS Standard Screen Format for a Multifile Application The line numbers that appear to the right of this figure do not appear on the actual screen; these line numbers appear in a table that follows the screen.
ENABLE SCREENS Standard Screen Format for a Multifile Application ----------------------------------------------------------------| | | Notice that PARTNUM is also the join field | | of the parts box. | | | | (4) A series of tilde (~) characters identifies | | the beginning of a box. The box is aligned | | with the join field label (PARTNUM) of the | | parent box.
ENABLE SCREENS Standard Screen Formats for IBM-327x Terminals With certain exceptions and additions, the rules described previously for the standard screens displayed by single-file applications also apply to the standard screens displayed by multifile applications. These exceptions and additions are: • The number of boxes that appear on a single screen page affect the number of screen lines available for screen label and field pairs.
ENABLE SCREENS HELP Screens If you generate an application that cannot perform certain operations (delete, insert, read, or update), the HELP screens do not display information about these operations. In addition, if you generate an application that can only display one record in each box, the box operations do not appear on the HELP screens.
ENABLE SCREENS HELP Screens PROGRAM-NAME The DISPLAY/CLEAR F16 key works as follows: Pressing F16 alternates the values of the screen between those most recently read or written, and a set of initial values. Read by key (FIRST/EXACT/APPROXIMATE/GENERIC) works as follows: The key field in which the cursor is positioned is selected to be the retrieval key, using the entered value, if any. If the cursor is not positioned in a key field a read by the default key for this record will be assumed.
SECTION 8 ENABLE FUNCTION KEYS An ENABLE application displays a screen through which you can read, insert, update or delete records stored in data base files. To request the operation you want, press the appropriate function key on the terminal keyboard. If you use an ENABLE application on a T16-6510, T16-6520, or T16-6530 terminal, you can place an ENABLE template, which identifies the function key operations, across the top of the terminal keyboard. Figure 8-1 illustrates this ENABLE template.
ENABLE FUNCTION KEYS Function Key Assignments This section discusses the ENABLE function keys and the operations assigned to each. Operations on T16-6510, T16-6520, and T16-6530 terminal types are assigned to function keys 1 through 8, 10, 12, 14, and 16, and to shifted function keys 1, 2, 4, 5, 10, and 12 through 16. ENABLE reserves two function keys, SF3 and SF6, for users. Operations on the IBM-3270 terminal type are assigned to program function keys 1 through 12 and program attention key 2.
ENABLE FUNCTION KEYS Function Key Assignments Table 8-1. Function Keys (Continued Next Page) ----------------------------------------------------------------| | | T16-6510/ | | T16-6520/ Template | | T16-6530 IBM 3270 Desig| | Function Key PF/PA Key nation Operation | |_______________________________________________________________| | | | F1 PF1 PREVIOUS Display the previous | | PAGE screen page or HELP | | screen.
ENABLE FUNCTION KEYS Function Key Assignments Table 8-1. 8-4 Function Keys (Continued) T16-6510/ T16-6520/ T16-6530 Function Key IBM 3270 PF/PA Key Template Designation F4 shifted Enter, PF4 DEFINE PRINTER Define printer. F5 PF5 READ NEXT READ NEXT by key selected by previous read operation. F5 shifted ENTER, PF5 PRINT Print display screen. F6 PF6 READ APPROX READ APPROXIMATE with indicated key. F6 shifted ENTER, PF6 F7 PF7 READ EXACT READ EXACT with indicated key.
ENABLE FUNCTION KEYS Function Key Assignments Table 8-1. Function Keys (Continued) ----------------------------------------------------------------| | | T16-6510/ | | T16-6520/ Template | | T16-6530 IBM 3270 Desig| | Function Key PF/PA Key nation Operation | |_______________________________________________________________| | | | F12 PF11 DELETE Delete a record. | | | | F12 shifted ENTER, PF11 DELETE Delete record(s) | | BOX from the current | | box.
ENABLE FUNCTION KEYS Key Fields KEY FIELDS Many of the operations that you can perform with an ENABLE application involve entering values in key fields. Each record in a key-sequenced file can have: • A primary key field. The value of a primary key field uniquely identifies a record within a file; for this reason, an ENABLE application will not allow you to enter a value in a primary key field if that value already exists in another record in the file. • Alternate key fields.
ENABLE FUNCTION KEYS Single-File READ Operations An ENABLE application identifies key fields by placing a special symbol to the left of the label for the field. The application uses an asterisk (*) to identify a primary key field and a plus sign (+) to identify an alternate key field. FILE OPERATIONS The following paragraphs describe the operations that you can perform on the data base files accessed by an ENABLE application.
ENABLE FUNCTION KEYS Single-File READ Operations READ NEXT (F5) A READ NEXT operation reads the next record according to your position within the file. You must have established a position within a file by previously performing a READ operation. READ APPROX (F6) A READ APPROX operation reads the first record in the file that has a key value equal to or greater than the value you have entered.
ENABLE FUNCTION KEYS Single File INSERT Operations READ GENERIC (F8) A READ GENERIC operation reads the first record (or records) having a key value that matches the partial value you enter. You cannot perform a READ GENERIC operation on the record number field of a relative, entry-sequenced, or unstructured file. If a key field is defined as USAGE IS COMP or TYPE BINARY in the record description, performing a READ GENERIC operation might return misleading results.
ENABLE FUNCTION KEYS Single-File DELETE Operations INSERT (F10) An INSERT operation inserts one record in a file. If an application displays more than one record, you must place the cursor within the record to be inserted when you request the INSERT operation. INSERT BOX (SF10) An INSERT BOX operation inserts one or more records in a file. When you perform an INSERT BOX operation, you must enter values for at least one record.
ENABLE FUNCTION KEYS Single-File DELETE Operations • DELETE BOX--To delete several records at one time (Normally, you use this type of DELETE operation only for applications that display screen pairs for more than one record.) You can reverse a DELETE operation by requesting an UNDO operation. Refer to the description of the UNDO operation for more information. DELETE (F12) A DELETE operation removes a single record from a file.
ENABLE FUNCTION KEYS Single-File UPDATE Operations If you restore a record to its initial values (either spaces, zeros, or initial values from the record description), a DELETE BOX operation ignores the record; the application does not try to delete a record with initial values. Single-File UPDATE Operations You must read a record before you can request an UPDATE operation. When you request an UPDATE operation, the General Server verifies that the record has not been changed since you read it.
ENABLE FUNCTION KEYS Multifile Operations If an error occurs during an UPDATE BOX operation, the application: • Issues a message identifying the problem • Highlights the fields of the record in error • Displays a prompt at the top of the screen that asks whether you want to continue processing When this prompt appears you must type either the letter Y or the letter N and press the indicated function key.
ENABLE FUNCTION KEYS Multifile Operations MANY-BOX Page 1/1 * PARTNUM _________ LOCATION-NUM ____ QUANTITY-ON-HAND ________ REORDER-LEVEL ________ SUPPNAME _____________________________ _______________________________ .00 _________ Ready for input Nested box Nested and containing box * PART-SUPP-KEY SUPPNUM _____ + PARTNAME PRICE Label from outermost box Nested box Labels from outermost box F3 for Help, shift F16 to exit S5043-036 Figure 8-2.
ENABLE FUNCTION KEYS Multifile INSERT Operations Multifile READ Operations You can read a record for an outermost box by requesting any READ operation (READ APPROX, READ EXACT, READ FIRST, READ GENERIC, or READ NEXT) described earlier in this section. If you want to read a record for a nested box, you must first request either a READ or INSERT operation for its containing box.
ENABLE FUNCTION KEYS Multifile UPDATE Operations You must also insert a record in a containing box before you can insert any records in nested boxes. Multifile DELETE Operations When you request a DELETE operation, delete the record (or records) from a nested box before you delete any records from its containing box.
ENABLE FUNCTION KEYS Multifile UPDATE Operations Undo (SF13) Operations You can undo a file operation (DELETE, DELETE BOX, INSERT, INSERT BOX, UPDATE, or UPDATE BOX) by requesting an UNDO operation. To undo a DELETE opertion, the application must insert the deleted record. The application can undo a DELETE operation if another file operation has not intervened between the DELETE operation and the UNDO request. To undo an UPDATE operation, the application must replace the old record.
ENABLE FUNCTION KEYS Special Operations DEFINE PRINTER (SF4) A DEFINE PRINTER operation defines the terminal, printer, or process that is to receive the current screen image. When you request a DEFINE PRINTER operation, the application displays a prompt on line 2 of the screen. You must then enter the name of the terminal, printer, or process and press SF4 again.
APPENDIX A SYNTAX SUMMARY This appendix summarizes the syntax of ENABLE commands, attributes and operating commands. A page reference accompanies each item. ENABLE Commands: ADD [ APPL ]
SYNTAX SUMMARY Attributes RESET [ APPL ] { [ [ BOX ] { [ { [ { [ { [ { * ABILITY FORMAT INTEGRITY OTHER ] ] ] ] ] , ... } } } } } } SET [ APPL ] [ BOX ] 3-21 3-26 [ , ] ... or SET [ APPL ] LIKE
SYNTAX SUMMARY Attributes EXCLUDE { } { ( [ , ... ] ) } 4-19 FILL { ON } { OFF } 4-24 FLAG { } { * } 4-28 HEADINGS { DDLFIELDNAMES { DDLHEADINGS { NULL 4-30 INCLUDE { { } } } } ( [ , ...
SYNTAX SUMMARY Attributes SCOBOLSKELETON 4-53 SCOBOLSOURCE [!] 4-55 SCREENFORMAT { UNCOMPRESSED } { COMPRESSED } 4-58 SERVERCLASS 4-62 SIZE 4-64 TERMINAL 4-66 TITLE 4-68 TMF { ON } { OFF } 4-69 TREE ( 4-71 [ ] ...
SYNTAX SUMMARY Operating Commands Operating Commands: CMDSYS [ \ ] 5-5 CMDVOL { $ } { $. } { } 5-6 ENV [ [ [ [ [ [ 5-8 CMDSYS CMDVOL OBEYSYS OBEYVOL SYSTEM VOLUME ] ] ] ] ] ] EXIT FC 5-9 5-10 R I D HELP [ ] [ {<}{>} ] 5-13 OBEY 5-14 OBEYSYS [ \ ] 5-16 OBEYVOL { $ } { $.
SYNTAX SUMMARY Operating Commands OUT 5-19 or /OUT / 5-21 VOLUME { $ } { $.
APPENDIX B ENABLE MESSAGES This appendix lists error and warning messages that may be issued in response to ENABLE commands during application generation, or during execution of an ENABLE application. Unless specifically noted as a warning, all messages are error messages. Error messages signify that an error in processing has occurred. A warning message signifies that a questionable condition exists.
ENABLE Messages ENABLE Error and Warning Messages Messages may also be received from the GUARDIAN operating system. Refer to the GUARDIAN Operating System Programmer's Guide for information about these messages. Table B-1 lists the messages that ENABLE might issue in response to commands or during application generation. Table B-1.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | An item size exceeds the Either a PIC or a TYPE clause | | maximum supported in the record description | | identifies a field that is | | more than 256 bytes long.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Could not obtain extended The GUARDIAN operating system | | memory (ALLOCATESEGMENT) could not obtain the number | | error: of extended memory pages | | requested for the object and | | attribute tables.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Dictionary file number mmmm The indicated I/O error | | File name : occurred on the named | | File management error code = dictionary file.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Exclude and Include cannot ENABLE does not allow you to | | both be selected supply a value for both the | | EXCLUDE and INCLUDE | | attributes. Reset the value | | of one of these attributes.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Garbled PATHCOM skeleton -The PATHCOM skeleton file | | Edit line nbr = aaaa.bbb does not conform to its | | expected structure. If you | | did not modify the PATHCOM | | skeleton file, notify your | | system analyst.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Invalid APPL parameter ENABLE does not recognize the | | specified application | | attribute. Check your | | spelling of this attribute. | | | | Invalid BOX command The object type of a GENERATE | | command must not be BOX.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Invalid name - PATHCOM You used a PATHCOM reserved | | reserved word word as a name. PATHCOM | | reserved words are illegal in | | certain constructs when a | | PATHCOM command file is being | | generated.
ENABLE Messages ENABLE Error and Warning Messages Table B-1.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Linked field is not a key The join field of a child box | | field: must be a primary key field, | | an alternate key field, a | | courtesy key field, or the | | leading (leftmost) portion of | | a composite key.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Linking field must not be If a join field is a group | | reordered or incomplete: field, the elementary items | | of that group must not be | | reordered.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Supply a value for the | | SERVERCLASS attribute to | | identify a different copy of | | the General Server for boxes | | with different integrity | | attribute values.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | No SCOBOL object code was Warning message. ENABLE did | | generated not generate object code | | because you omitted the | | parameter when | | you supplied a value for the | | SCOBOLOBJECT attribute.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | PATHCOM file already exists The value of the PATHCOMFILE | | attribute identifies an | | existing file, but you did | | not include the exclamation | | point symbol (!) to force an | | overwrite.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Same box already used in The named box appears more | | TREE: than once as the value of the | | TREE attribute.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | SCOBOL source file already You supplied the name of an | | exists existing file as the value of | | the SCOBOLSOURCE attribute, | | but you did not include the | | exclamation point symbol (!) | | to force an overwrite.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | The generated PATHCOM file Warning message. You must | | must be edited. edit the PATHCOM file before | | using it to configure a | | PATHWAY system.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Unable to access dictionary ENABLE either could not find | | File name : the dictionary files or could | | File management error code = not access them. | | identifies the cause of the | | error.
ENABLE Messages ENABLE Error and Warning Messages Table B-1. ENABLE Error and Warning Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Wrong version of SCOBOL The SCREEN COBOL skeleton file | | skeleton does not match the current | | ENABLE product version.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued next page) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Alternate key is gone. You tried to read a file | | using an alternate key and | | the General Server cannot | | find, open, or read the | | alternate key file.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Fatal error occurred during During I/O to the print | | printout device, a GUARDIAN file error | | code indicating a fatal error | | condition was returned. | | Reenter the name of the | | printer and try the operation | | again.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | File OPEN error. No ASSIGN naming the | | File name was not assigned. logical record referred to | | was supplied to the called | | server class. Check the | | PATHCOM command file for a | | SET SERVER ASSIGN command.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Files must not be changed You tried a delete operation | | prior to DELETE. after changing some value in | | a field of the record. | | | | INSERT failed.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | INSERT OK, but DELETE on old You tried to update a record | | image failed. and change the primary key.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Invalid numeric field(s) If you have just read a record | | displayed as zero: data and this message appears, the | | is corrupt highlighted fields contain | | invalid data that the | | application displays as | | zeros.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | No base screen was displayed Modifications to either the | | SCREEN COBOL skeleton or the | | SCREEN COBOL source code | | resulted in the omission of a | | required DISPLAY BASE | | statement. The current | | screen is undefined.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | Nothing to update. You tried to update a record | | without previously reading | | the record from the data | | base. | | | | OPEN error: The specified error occurred | | File system error on open for the named file.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | SEND Error status value = A PATHWAY error has occurred. | | nnn Record the error and see your | | data administrator for | | interpretation of the error | | code associated with the | | PATHWAY SEND verb.
ENABLE Messages Application Run-Time Error Messages Table B-2. Application Run-Time Error Messages (Continued) ----------------------------------------------------------------| | | Message Meaning | |_______________________________________________________________| | | | UPDATE failed. File error A GUARDIAN-ENSCRIBE file | | code = nnnn management error occurred. | | Record the error and see your | | data administrator. | | | | UPDATE failed.
APPENDIX C RESERVED WORDS This appendix lists the reserved words in three categories: ENABLE reserved words, SCREEN COBOL reserved words, and PATHWAY reserved words. Figure C-1 lists the ENABLE reserved words. words as either box or application names. You cannot use these ----------------------------------------------------------------| | | ENABLE Reserved Words | | | | APPL BOX KEY | | | ----------------------------------------------------------------Figure C-1.
RESERVED WORDS SCREEN COBOL Reserved Words Figure C-2 lists the SCREEN COBOL reserved words. these words as application names. You cannot use SCREEN COBOL Reserved Words ABORT ABORT-INPUT ABORT-TRANSACTION ABSENT ACCEPT ACCESS ADD ADVANCING ADVISORY AFTER ALARM ALL ALPHABETIC ALSO ALTER ALTERNATE AND APPROXIMATE ARE AREA AREAS ASCENDING ASSIGN AT ATTR AUDIBLE AUTHOR BASE BE BEFORE BEGIN-TRANSACTION BLANK BLOCK BOTTOM BY CALL CANCEL CD CF CH CHARACTER CHARACTERS CHARACTER-SET CHECKPOINT Figure C-2.
RESERVED WORDS SCREEN COBOL Reserved Words FOR FROM FULL GENERATE GENERIC GIVING GO GREATER GROUP GROUP-SEPARATOR HEADING HIGH-VALUE HIGH-VALUES I-O I-O-CONTROL I-O-ERROR IDENTIFICATION IF IN INDEX INDEXED INDICATE INITIAL INITIATE INPUT INPUT-OUTPUT INSPECT INSTALLATION INTO INVALID IS JUST JUSTIFIED KEY LABEL LAST LEADING LEFT LENGTH LESS LIKE LIMIT LIMITS LINAGE LINAGE-COUNTER LINE Figure C-2.
RESERVED WORDS SCREEN COBOL Reserved Words REPORTS RERUN RESERVE RESET RESTART-COUNTER RESTART-INPUT RESTART-TRANSACTION RETURN REVERSED REWIND REWRITE RF RH RIGHT ROUNDED RUN SAME SCREEN SCREEN-CONTROL SCROLL SD SEARCH SECTION SECURITY SEGMENT SEGMENT-LIMIT SELECT SEND SENTENCE SEPARATE SEQUENCE SEQUENTIAL SET SHADOWED SHARED SIGN SIZE SKIP SKIPPING SORT SORT-MERGE SOURCE SOURCE-COMPUTER SPACE SPACES SPECIAL-NAMES SPACES STANDARD STANDARD-1 START STARTBACKUP STATUS STOP STOP-MODE STRING SUB-QUEUE-1 SUB-Q
RESERVED WORDS PATHWAY Reserved Words Figure C-3 lists the PATHWAY reserved words. these words as application names.
APPENDIX D MODIFYING THE SCREEN COBOL SKELETON FILE You can modify a copy of the SCREEN COBOL skeleton file provided by ENABLE and use this modified version to generate an application. The SCREEN COBOL skeleton file contains source text for a SCREEN COBOL program that is complete except for the data items defined by DDL record descriptions and options included by the ENABLE compiler. Special command lines in the skeleton drive the ENABLE processing. These command lines are interspersed with text lines.
SCREEN COBOL SKELETON 1. You can replace literals in the text. For example, you can modify the skeleton so that the application will display messages in a language other than English. If the modified literal is longer than the original, you might need to modify the affected SCREEN COBOL data items. 2. You can remove the T9155- prefix from the variables in the skeleton provided no name conflict will result.
SCREEN COBOL SKELETON If you make modifications to the skeleton that are suitable for all users at your installation, you can replace ENABAPPS with the modified version, which thus becomes the default skeleton. CAUTIONS If you replace the default skeleton with a modified version, you do so AT YOUR OWN RISK. Any skeletons modified for use with previous versions of ENABLE cannot be used with the present version of ENABLE.
APPENDIX E CHARACTERISTICS OF THE GENERAL SERVER The General Server is a server that can be called from any requester requiring access to a data base file.
THE GENERAL SERVER Use With a User-Written Requestor SET SERVER (PARAM ALLFILES ON) Indicates that the General Server must open all assigned files before processing any requests. If the General Server cannot open an assigned file, it terminates. SET SERVER (PARAM WHOLEFILES ON) Indicates that the General Server is to issue an error message if it cannot open an alternate key file or a partition of a data file.
THE GENERAL SERVER Providing File Assignments To start the General Server outside of a PATHWAY environment, you use the command interpreter RUN command. Refer to the GUARDIAN Operating System User's Guide information about this command. Providing File Assignments The General Server can open up to 32 data base files. You must provide ENABLEGS with the assign specifications that it needs to open these files.
THE GENERAL SERVER Providing Paramters • When not running under PATHWAY, the ID is the user ID of the user who started the ENABLEGS process. Providing Parameters for the General Server The General Server recognizes the following parameters: • ALLFILES [ ON ] [ OFF ] ON indicates that ENABLEGS must open all assigned files before processing any requests. If ENABLEGS cannot open one of the assigned files, it terminates.
THE GENERAL SERVER Locking Records ON indicates that the data base files to be accessed by ENABLEGS are audited by TMF. A data base file audited by TMF is flagged for special handling in preparation for recovery efforts. For use under PATHWAY, all the files accessed by a given server class must either be audited by TMF or be non-audited files. OFF indicates that none of the data base files to be accessed by ENABLEGS is audited by TMF. The default for this parameter OFF.
THE GENERAL SERVER General Server Requirements GENERAL SERVER REQUIREMENTS You can use the General Server with requester programs that you have written. These programs must conform to the external specifications detailed in the following paragraphs. Opening the General Server You can open the General Server with a nowait depth of 0 or 1 and a sync depth of 0 or 1.
THE GENERAL SERVER Request Format ----------------------------------------------------------------| | | | | DEF PW-HEADER. | | 02 REPLY-CODE PIC S9(4) COMP. | | 02 APPLICATION-CODE PIC XX. (not used) | | 02 FUNCTION-CODE PIC XX. | | 02 TRANS-CODE PIC 99. | | 02 TERM-ID PIC X(15). (not used) | | 02 LOG-REQUEST PIC X. (not used) | | END | | | | DEF GS-HEADER. | | | | 02 ERROR-STATUS. | | 03 ERROR-CODE PIC S9(4) COMP. | | 03 ERROR-SUB-CODE PIC S9(4) COMP. | | 03 FILE-ERROR-CODE PIC S9(4) COMP.
THE GENERAL SERVER Request Format Table E-1. Transaction Codes ----------------------------------------------------------------| | | Code Value Transaction | | | | | | 0 OPEN | | 1 READ | | 2 UPDATE | | 3 DELETE | | 4 INSERT | | | ----------------------------------------------------------------The first transaction that you request from the General Server must be an OPEN to obtain FILE-NUMBER. There is no close-file transaction.
THE GENERAL SERVER Usage-Dependent Fields ENABLEGS ignores fields that are not required. For example, ENABLEGS will ignore COMPARE-LENGTH except on a random READ (TRANS-CODE =1). Usage-Dependent Fields As Figure E-2 shows, nine fields in the prefix are associated with transaction codes.
THE GENERAL SERVER Usage-Dependent Fields For INSERT operations, the value supplied can be any of the following: blank EX LA INSERT in the first available space INSERT at the indicated record key position (relative files only) INSERT at the end of the file (relative files only) FILE-NAME Field This field applies to all transaction codes. For an open operation, the requester must supply the 30-character logical name of the data file to be opened.
THE GENERAL SERVER Usage-Dependent Fields KEY-SPECIFIER Field This field applies to a READ operation (code 1), UPDATE operation (code 2), and DELETE operation (code 3). The requester must supply the two-byte key specifier for the current key of reference in this field. Supplying binary zero indicates the primary key. COMPARE-LENGTH Field This field applies to a random READ operation (code 1). A random READ operation is one with a FUNCTION-CODE equal to EX, AP, AG, or GN.
THE GENERAL SERVER Context Buffer An open operation sets this field to the expected value of RECORD-AREA-LENGTH. If the requester sets this field to zero subsequent to the open operation, the General Server uses and returns the expected value. The expected value for this field is the value of RECORD-LENGTH if RECORD-LENGTH is an even number or RECORD-LENGTH + 1 if RECORD-LENGTH is an odd number.
THE GENERAL SERVER Variable Portion of the Request ----------------------------------------------------------------| | | | | RECORD-IMAGE PIC X(n) (codes 1,2,3,4) | | | | RECORD-IMAGE-2 PIC X(m) (code 2) | | | | The presence of record images is dependent on specific | | transactions; relevant transaction codes are shown in | | parentheses. RECORD-IMAGE-2, for example, is present only | | on UPDATE (TRANS-CODE=2). | | | | You do not need to supply RECORD-IMAGE for code 0.
THE GENERAL SERVER Variable Portion of the Request • UPDATE (TRANS-CODE=2): --The requester must supply the old record image in RECORD-IMAGE. --The requester must supply the new record image in RECORDIMAGE-2. The new record follows the old record but always begins on a word boundary. --The requester must supply the byte length of the old record image in RECORD-AREA-LENGTH. This might not be the length of the record itself if padding of one byte is necessary to position RECORD-IMAGE-2 on a word boundary.
THE GENERAL SERVER SEND Processing SEND Processing Table E-3 shows the fields and corresponding values that must be supplied for SEND processing. The table is divided according to the operation requested. Table E-3.
THE GENERAL SERVER SEND Processing Table E-3. Values Expected by the General Server for SEND Processing (Continued) ----------------------------------------------------------------| | | Operation Field or Record Value | |_______________________________________________________________| | | | KEY-SPECIFIER Two-byte specifier | | (key-sequenced for the current key | | files only) of reference | | (binary zero for | | the primary key), | | if access is by | | key.
THE GENERAL SERVER SEND Processing Table E-3. Values Expected by the General Server for SEND Processing (Continued) ----------------------------------------------------------------| | | Operation Field or Record Value | |_______________________________________________________________| | | | COMPARE-LENGTH Byte length of the | | leading portion of | | the value to be | | used for | | positioning. | | | | RECORD-IMAGE The key value in | | the appropriate | | position.
THE GENERAL SERVER SEND Processing Table E-3. Values Expected by the General Server for SEND Processing (Continued) ----------------------------------------------------------------| | | Operation Field or Record Value | |_______________________________________________________________| | | | UPDATE TRANSACTION-CODE 02 | | | | RECORD-IMAGE The old record image.| | | | RECORD-IMAGE-2 The new record | | image (must begin | | on a word | | boundary).
THE GENERAL SERVER Response Format GENERAL SERVER RESPONSE FORMAT General Server responses consist of a fixed prefix common to all types of transactions and a variable portion dependent on the entry in REPLY-CODE. REPLY-CODE is equal to 0 or 1 as follows: REPLY-CODE=0 REPLY-CODE=1 Prefix only returned Prefix plus RECORD-IMAGE returned The prefix consists of the 24-byte PATHWAY header, the 54-byte General Server header, and the 96-byte context buffer.
THE GENERAL SERVER Error Codes GENERAL SERVER ERROR CODES The General Server can return error codes during initialization and at run time. During initialization, the General Server returns error codes as replies to system messages. If a fatal initialization condition occurs, the General Server calls ABEND. At run time, the General Server returns errors in ERROR-CODE of the General Server header. Table E-4 lists the codes and their interpretations.
THE GENERAL SERVER Error Codes Table E-4. General Server Run-Time Errors ----------------------------------------------------------------| | |ERROR-CODE | | Value Interpretation | |_______________________________________________________________| | | | 1 The TRANS-CODE value was out of bounds. | | | | 2 The FUNCTION-CODE was unknown. | | | | 3 The data file identified in the request was not | | known or was not accessible. | | | | 4 The record could not be found.
THE GENERAL SERVER Error Codes When the General Server receives an error issued by the file system, it returns the file-system error code in FILE-ERROR-CODE of the General Server header. The General Server reserves the ERROR-SUB-CODE field for codes to identify further the location in ENABLEGS at which the error condition was detected. The only meaningful ERROR-SUB-CODE is 96, which corresponds to the INSERT OK, but DELETE on old image failed error message.
THE GENERAL SERVER Error Codes Table E-5. General Server File-Open Transaction Errors ----------------------------------------------------------------| | | FILE-ERROR-CODE Interpretation | | Value | |_______________________________________________________________| | | | 300 The number of keys specified by the open | | transaction does not match the number | | actually found in the file. | | | | 301 The record-length parameter was missing | | from the ASSIGN for the file. | | | | 302 TMF mode mismatch.
APPENDIX F ENABLE VERSIONS COMPARISON This appendix describes the difference between ENABLE B00 (the version described in this manual) and ENABLE A00 (the previous version of ENABLE). Table F-1 lists the differences between the terminal screens displayed by applications generated with ENABLE A00 and the terminal screens displayed by applications generated with ENABLE B00.
VERSIONS COMPARISON Display Screen Differences Table F-1.
VERSIONS COMPARISON Display Screen Differences Table F-1. Application Display Screen Differences (Continued) ----------------------------------------------------------------| | | ENABLE A00 ENABLE B00 | |_______________________________________________________________| | | | The application checks a The application does not use | | variable that shadows the another variable to shadow | | Record Number field for the Record Number field.
VERSIONS COMPARISON Application Operation Differences Table F-2. Application Operation Differences ----------------------------------------------------------------| | | ENABLE A00 ENABLE B00 | |_______________________________________________________________| | | | The application does not The application supports | | support the NEXT PAGE and the NEXT PAGE and PREV PAGE | | PREV PAGE keys (found only keys. They perform the same | | on T16-652x, and T16-653x function as F2 and F1, | | Terminals).
VERSIONS COMPARISON Differences During Generation Table F-3 lists generation discrepancies for the two versions of ENABLE. Table F-3. Differences During Application Generation (Continued next page) ----------------------------------------------------------------| | | ENABLE A00 ENABLE B00 | |_______________________________________________________________| | | | The starting value of the The starting value for the | | VALUES attribute is ON. VALUES attribute is OFF.
VERSIONS COMPARISON Differences During Generation Table F-3. Differences During Application Generation (Continued) ----------------------------------------------------------------| | | ENABLE A00 ENABLE B00 | |_______________________________________________________________| | | | If SCOBOLOBJECT is null IF SCOBOLOBJECT is null, | | (indicating that compilation ENABLE issues the message: | | is not to take place), "Generated Pathcomfile must | | ENABLE issues the warning: be edited.
VERSIONS COMPARISON Differences During Generation Table F-3.
APPENDIX G GLOSSARY Access. The right of an application to open, read, or update information in a data base file. Access path. records. An established order in which an application reads Alphanumeric data. Data that consists of uppercase and lowercase letters of the alphabet, digits, blanks, and special characters. Alternate key. A key field that identifies a record in a key-sequenced, entry-sequenced, or relative file; alternate keys need not have unique values. APPL.
GLOSSARY Attribute Table Attribute table. An internal table that ENABLE uses to store attribute values. Audited file. A data file that is flagged for auditing by TMF; auditing is the monitoring of transactions in preparation for recovery efforts. BOX. A keyword that identifies the type of object that represents a data base file and its attributes within an application. Box. An element displayed by an application on the terminal screen. A box contains a record (or records) from a specific data base file.
GLOSSARY File Utility Program Data base. A collection of data that is described and controlled within a computer system. Data dictionary. A set of files that provide information about each file in a data base. Data type. A category that identifies the kind of data that a field represents. Four broad categories of data types exist: alphabetic, alphanumeric, numeric integer, and numeric noninteger. Data values. The actual values stored in a data base file. Default attribute value.
GLOSSARY General Server General Server. The Tandem proprietary process, supplied by the ENABLE subsystem, that provides access and updates data base files. Generic mode. A positioning mode that provides record access by a key value matching a supplied partial key value. Group. A field in a record description made up of two or more contiguous elementary fields. GUARDIAN. The Tandem operating system. Heading.
GLOSSARY Positioning Mode NONSTOP. An ENABLE attribute used to specify whether the General Server is to operate as a NonStop process pair. Numeric data. Data that consists of digits (0-9); leading and trailing blanks; and possibly a decimal point and a minus sign. Obey file. input. A file that serves as an alternate source for command Object. An application or a box. An object table entry that describes an application or a box. Object table.
GLOSSARY Primary Key Primary key. The key field that uniquely identifies a record in a file; a primary key cannot be duplicated. Program generator. The component of ENABLE that generates SCREEN COBOL source code. Record. Depending on the context in which it is used, a record is either related data stored in a data base file or a record description. Record description. A entity stored in a data dictionary that describes the organization and structure of a data base file. Record number.
GLOSSARY Unstructured File Sync ID. A value used by the operating system to provide automatic path error recovery for disc files. TCP. A program supplied by Tandem that interprets SCREEN COBOL object code and sends messages to server processes; synonymous with requester process. Terminal. A device capable of sending and receiving information over communication lines. Transaction Monitoring Facility (TMF).
INDEX ABILITY attributes defined 3-22 DELETE 4-15 displaying current values 3-31 INSERT 4-36 READ 4-43 resetting to starting values 3-22 UPDATE 4-102 ADD APPL command, see ADD command 5-8 ADD BOX command, see ADD command ADD command considerations 3-8 detailed description 3-6 example override application attribute value 2-19 example override box attribute value 2-14 examples 2-22, 3-10 summary description 2-8 supplying an override attribute value 2-12 syntax 3-6 Adding a box examples 2-22, 3-10 summary des
INDEX Alphanumeric data 7-8 Alternate key fields and file operations 8-6 excluding from the screen 4-21, 4-34 reordering 4-34 screen identifier 7-7 APPL default object type 3-11 term defined 2-7 Application adding 2-23, 3-10 defining boxes to be used 4-71 definition 2-7 deleting 3-13 describing with a GENERATE command 3-15 with a SET command 3-26 with an ADD command 2-19, 3-6 displaying in the object table 3-18 generating 2-23, 3-15 identifying a terminal type 4-66 See also multifile application See also si
INDEX TREE 4-71 Application execution detailed instructions 6-1 overview 1-7 Application generation described 3-15 overview 1-7 Application program skeleton file description 1-4 identifying 4-53 modifying D-1 setting flags for 4-28, D-2 ASSUME command detailed description 3-11 example 3-12 summary description 2-8 syntax 3-11 Attribute table and starting attribute values 2-12 contents after an ADD BOX command 2-17 current application attribute values 2-16 current box attribute values 2-14 default application
INDEX current values defined 2-12 supplying 3-26 DATAFILE 4-13 default values defined 2-12 supplied by ENABLE 2-15, 4-2 DELETE 4-15 DICTIONARY 4-17 displaying current values 3-31 EXCLUDE 4-19 FILL 4-24 FLAG 4-28 FORMAT defined 3-22 resetting 3-22 HEADINGS 4-30 INCLUDE 4-32 INSERT 4-36 INTEGRITY defined 3-22 resetting 3-22 NONSTOP 4-37 OTHER defined 3-22 resetting 3-22 override values defined 2-12 supplying 3-6 PATHCOMFILE 4-39 PATHCOMSKELETON 4-41 READ 4-43 RECORD 4-45 resetting to their starting values 3-2
INDEX UPDATE VALUES 4-102 4-103 Binary data items 1-6 Box adding to the object table 2-22, 3-9, 3-15 associating with an application 4-71 child 4-76 containing 8-13 defined 2-7 deleting 3-13 dependency conditions 4-76 describing overview 2-13 with a GENERATE command 3-17 with a SET command 3-26 with an ADD command 3-9 displayed on multifile screen 7-12 displaying in the object table 3-18 maximum number of records displayed 4-64 nested 8-13 outermost 8-13 parent 4-76 providing text within on the screen 4-8
INDEX READ 4-43 RECORD 4-45 resetting to starting values 3-21 SCREENFORMAT 4-58 SERVERCLASS 4-62 setting a value 3-26 SIZE 4-64 starting values resetting to 3-21 starting values summary 4-4 TMF 4-69 UPDATE 4-102 VALUES 4-103 BOX keyword identifying an object type 3-11 used to identify a new default object type 3-11 BOXTITLE attribute considerations 4-9 detailed description 4-8 example 4-10 resetting 3-22 resetting as an FORMAT attribute 3-22 summary description 2-10 syntax 4-8 BREAK key 2-3 Central processo
INDEX summary description 2-6 syntax 5-6 Command file and the ENABLE run command 2-1 in noninteractive mode 2-4 Command interpreter current input file 2-1 current output file 2-1 ENABLE run command 2-1 PARAM command 2-5 Commands conventions and reserved words 2-25 comments 2-24 continuation lines 2-28 field name qualification 2-25 multiline 2-24 string literals 2-24 editing a command line 5-10 ENABLE ADD 3-6 ASSUME 3-11 DELETE 3-13 GENERATE 3-16 INFO 3-18 operating commands 2-6 RESET 3-21 SET 3-26 SHOW 3-31
INDEX reordering 4-34 Compressing the format of the screen 4-58 Configuring a PATHWAY system 6-1 Containing box defined 8-13 DELETE operations 8-16 INSERT operations 8-15 READ operations 8-15 UPDATE operations 8-16 Context buffer of the General Server E-12 Continuation lines 2-24 Control boxes 4-26 Controlling the ENABLE environment 2-5 Courtesy key acceptable values 7-7 and file operations 8-6 and the INSERT attribute 4-36 CPU identifying for ENABLE 2-2 identifying for PATHMON 6-2 CPU option 2-2 Current at
INDEX default value supplied by ENABLE 2-15, 4-7 detailed description 4-13 examples 4-14 resetting as an OTHER attribute 3-22 summary description 2-10 syntax 4-13 DDL dictionary 1-6 HEADING clause maximum length 1-6 syntax requirements for record descriptions 1-6 using HEADINGS clauses as screen labels 4-30 VALUES clause 4-103 Decimal points in screen data 7-8 Default attribute values described 2-12 example for a box attribute 2-15 example for an application attribute 2-20 for the TREE attribute 3-9 removed
INDEX summary description 2-8 syntax 3-13 DELETE operations DELETE 8-11 DELETE BOX 8-11 multifile 8-16 providing for an application 4-15 Deleting a box 3-13 all objects 3-14 an application 3-13 Dependency condition between boxes 4-76 Describing a data base file within an application 2-7 global characteristics of an application 2-7 overview of application description 2-16 Dictionary and the DDL compiler 1-4 and the ENABLE compiler 1-4 definition of 1-6 ENABLE requirements 1-6 identifying multiple 4-17 identi
INDEX command file 2-1 command syntax summary A-1 commands overview 2-7 syntax 3-1 to define objects 2-4 with the run command 2-2 components application program skeleton file 1-5 compiler 1-4 General Server 1-4 PATHCOM command skeleton file 1-5 program generator 1-4 controlling commands 2-7 displaying commands 5-13 displaying the environment 5-8 header 2-3 identifying a central processor for 2-2 interactive mode 2-3 list file 2-1 noninteractive mode 2-4 operating commands 5-1 product description 1-1 prompt
INDEX detailed description 3-18 summary description 2-8 RESET command detailed description 3-21 summary description 2-8 SET command detailed description 3-26 summary description 2-8 SHOW command detailed description 3-31 summary description 2-8 summary list 2-8 usage information 3-1 usage overview 2-12 ENABLE compiler and the object table 2-4 described 1-4 ENABLE prompt 2-3 ENABLE RUN command CPU option 2-2 IN option 2-1 MEM option 2-2 NAME option 2-2 NOWAIT option 2-2 OUT option 2-1 PRI option 2-2 ENABLEGS
INDEX detailed description 4-19 examples 4-23 resetting 3-22 resetting as an FORMAT attribute 3-22 summary description 2-10 syntax 4-19 Excluding fields from the screen 4-19 Execution priority for ENABLE 2-2 EXIT command detailed description 5-9 summary description 2-6 syntax 5-9 Exiting from ENABLE 5-9 Extended memory allocating 2-4 reclaiming 3-14 reducing number allocated 2-4 EXTPAGES parameter 2-4 FC command and the BREAK key 2-3 considerations 5-11 detailed description 5-10 example 5-11 subcommands 5-1
INDEX READ 4-43 UPDATE 4-102 multifile DELETE 8-16 general description 8-13 INSERT 8-15 READ 8-15 UPDATE 8-16 reversing 8-17 single-file DELETE 8-11 DELETE BOX 8-11 INSERT 8-10 INSERT BOX 8-10 READ APPROX 8-8 READ EXACT 8-8 READ FIRST 8-7 READ GENERIC 8-9 READ NEXT 8-8 UPDATE 8-12 UPDATE BOX 8-12 FILE-NAME field E-10 FILE-NUMBER field E-10 FILE-POSITION field E-10 FILL attribute and multifile READ operations 8-15 and the READ attribute 4-43 considerations 4-24 detailed description 4-24 examples 4-27 resetti
INDEX Formatting the screen compressing the screen format 4-58 defining the order in which boxes appear displaying inital values 4-103 excluding fields 4-19 identifying screen labels 4-30 identifying the number of records to appear in a box 4-64 providing a screen title 4-68 providing text within a box 4-8 reordering screen fields 4-32 Function keys assigned 8-2 user determined 8-18 FUNCTION-CODE field E-9 General Server and file locking E-5 and the NONSTOP attribute 4-37 and the TMF attribute 4-69 characte
INDEX detailed description 4-30 example 4-31 resetting 3-22 resetting as an FORMAT attribute summary description 2-10 syntax 4-30 HELP command consideration 5-13 detailed description 5-13 examples 5-13 summary description 2-6 syntax 5-13 Help screens 7-14 3-22 IBM-3270 terminals and the TERMINAL attribute 4-66 cursor position 7-10 program function key assignments 8-3 program function key usage 8-3 screen formats 7-14 Identifying a CPU for ENABLE 2-2 a file name 4-13 SCREEN COBOL compiler 4-47 text to appe
INDEX resetting 3-22 resetting as an ABILITY attribute 3-22 summary description 2-11 syntax 4-36 INSERT BOX 8-10 INSERT operations acceptable values for record numbers 7-8 defining the order for multifile applications 4-82 multifile 8-15 reversing 8-9 single-file INSERT 8-10 INSERT BOX 8-10 supplying for an application 4-36 Inserting records 8-9 INTEGRITY attributes CHECKDATA 4-11 defined 3-22 displaying current values 3-32 NONSTOP 4-37 resetting to starting values 3-22 TMF 4-69 Interactive mode BREAK key 2
INDEX and the EXCLUDE attribute and the INCLUDE attribute primary key 8-6 KEY-SPECIFIER field E-11 Keywords APPL 2-7 BOX 2-8 KEY 2-26 4-20 4-33 Labels default 7-6 on a standard multi-file screen 7-14 on a standard single-file screen 7-6 Level numbers 4-71 Levels of the tree structure described 4-82 purpose 4-82 rules for 4-82 Limits application name length 3-6 command line length 2-24 DDL HEADING clause length 1-6 for excluding fields 4-20 level numbers 4-71 maximum number of data base files 1-5 maximum v
INDEX MEM option 2-2 Multifile applications adding 3-9 and the INSERT attribute 4-36 automatic READ operations 4-24 BOXTITLE considerations 4-9 DELETE operations 8-16 dependency condition between boxes 4-76 examples 4-84 identifying a single dictionary 4-17 a terminal type 4-66 several dictionaries 4-17 INSERT operations 8-15 many-to-one relationships 4-65 one-to-many relationships 4-65 one-to-one relationships 4-65 overview 1-3 PATHCOM command file 4-39 READ operations 8-10 standard screen format 7-12 UPDA
INDEX NOWAIT option 2-2 Numeric data determining screen field length 7-8 entering on the screen 7-8 invalid 4-11 with embedded decimal points 7-8 OBEY command considerations 5-14 detailed description 5-14 example 5-15 summary description 2-6 syntax 5-14 Obey files executing from the command Interpreter 6-4 expansion of system names 5-14, 5-16 expansion of volume names 5-17 for ENABLE commands 5-14 samples 6-2, 6-5 to establish a PATHWAY system 6-2 OBEYSYS command considerations 5-16 detailed description 5-1
INDEX explicitly 3-9 implicitly 3-9, 3-15 overview 2-21 application 2-7 box 2-7 defined 2-7 deleting 3-14 describing 2-12 removing 3-13 Obtaining SCREEN COBOL source code 4-55 OCCURS clause displayed as screen fields 7-6 ENABLE requirements for DDL syntax 1-6 One-to-many relationships 4-65 One-to-one relationships 4-65 Opening the General Server E-6 Operating commands CMDSYS detailed description 5-5 summary description 2-6 CMDVOL detailed description 5-6 summary description 2-6 ENV detailed description 5-8
INDEX VOLUME detailed description 5-22 summary description 2-7 Operations automatic READ 4-24 DELETE 4-15 identifying for an application 7-1 INSERT 4-36 READ 4-43 UPDATE 4-102 OTHER attributes DATAFILE 4-13 defined 3-22 DICTIONARY 4-17 displaying current values 3-32 FLAG 4-28 RECORD 4-45 SERVERCLASS 4-62 OUT command and ENABLE tables 2-4 considerations 5-13 detailed description 5-13 examples 5-13 summary description 2-6 syntax 5-13 OUT option in the ENABLE RUN command 2-1 rules for 2-1 Outermost box defined
INDEX described 4-81 displayed on the terminal screen 4-85 requirements for size of join field 4-82 PATHCOM creation 6-1 description 1-9 PATHCOM command file identifying 4-39 providing new parameters E-2 role in application execution 1-9 skeleton 1-5 using in a PATHWAY system 6-3 PATHCOM command skeleton file description 1-5 identifying 4-41 PATHCOMFILE application attribute considerations 4-39 detailed description 4-39 example 4-40 examples 2-18 resetting to starting value 3-22 summary description 2-9 synt
INDEX PATHMON creation 6-1 description 1-9 reserved words C-5 role of the General Server 1-9 role of the SCREEN COBOL program 1-9 starting after a shutdown 6-5 tasks to establish 1-9 TCP 1-9 POBJ file 4-51 PRI option 2-2 Primary key fields and file operations 8-6 excluding from the screen 4-20, 4-33 reordering 4-33 screen identifier 7-6 PRINT operations 8-18 Processes, terminating ENABLE 2-3 PATHWAY system 6-6 Program Generator allocating extended memory for the object table 2-4 Program generator descriptio
INDEX READ FIRST 8-7 READ GENERIC 8-9 READ NEXT 8-8 READ operations automatic 4-24 multifile 8-15 order for multifile applications 4-81 single-file READ APPROX 8-8 READ EXACT 8-8 READ FIRST 8-7 READ GENERIC 8-9 READ NEXT 8-8 supplying for an application 4-43 values returned to record number field 7-9 Reading records 8-7 RECORD attribute considerations 4-45 detailed description 4-45 example of supplying a current value 2-13, 4-46 resetting as an OTHER attribute 3-22 summary description 2-11 syntax 4-45 Recor
INDEX a box from the object table 3-13 all objects 3-14 an application from the object table 3-13 Repeating a command line 5-10 Request format of the General Server E-6 Reserved words and application names 3-6 and box names 3-6 ENABLE C-1 PATHWAY C-5 SCREEN COBOL C-2 summary information 2-25 RESET command considerations 3-23 detailed description 3-21 examples 3-24 summary description 2-8 Resetting attribute values 3-21 the default object type 3-11 Response format of the General Server E-19 Reversing a DELET
INDEX resetting to starting value 3-22 summary description 2-9 syntax 4-51 SCOBOLSKELETON application attribute considerations 4-53 detailed description 4-53 example 4-54 summary description 2-9 syntax 4-53 SCOBOLSOURCE application attribute considerations 4-55 detailed description 4-55 example 4-57 resetting to starting value 3-22 summary description 2-9 syntax 4-55 SCOBOLX compiling SCREEN COBOL source code 4-56 SCREEN COBOL compiler identifying 4-47 Screen customizing 7-1 SCREEN COBOL compiling source co
INDEX and the BOXTITLE attribute 7-1 and the EXCLUDE attribute 7-1 and the HEADINGS attribute 7-2 and the INCLUDE attribute 7-2 and the SCREENFORMAT attribute 7-2 and the SIZE attribute 7-2 and the TITLE attribute 7-2 and the TREE attribute 4-85 and the VALUES attribute 7-2 description of standard 7-1 general format of standard screen 7-5 labels and fields 7-6 Screen format attributes BOXTITLE 4-8 EXCLUDE 4-19 HEADINGS 4-30 INCLUDE 4-32 SCREENFORMAT 4-58 SIZE 4-64 TITLE 4-68 VALUES 4-103 Screen messages aft
INDEX and the NONSTOP attribute 4-37 identifying 4-62 SET command detailed description 3-26 effect of 3-27 general considerations 3-27 general examples 3-30 overriding a value established by 3-30 summary description 2-8 supplying a current application attribute value 2-18 supplying a current box attribute value 2-12 SHOW command and attribute table 2-8 considerations 3-33 detailed description 3-31 examples 3-34 summary description 2-8 syntax 3-31 Single-file applications adding 3-9 automatic READ operations
INDEX Starting attribute values description 2-12, 4-2 in the attribute table 2-12 summary for application attributes summary for box attributes 4-4 String literals described 2-28 with the BOXTITLE attributes 4-8 with the TITLE attribute 4-68 Summary application attributes 2-10 box attributes 2-9 ENABLE commands 2-8 operating commands 2-5 syntax A-1 Syntax summary A-1 SYSTEM command considerations 5-21 detailed description 5-21 examples 5-21 summary description 2-7 syntax 5-21 4-2 T16-6510 terminals and th
INDEX Terminal screens, see screen formats Terminal type, identifying 4-66 Terminating ENABLE 5-9 TITLE application attribute considerations 4-68 default value supplied by ENABLE 4-3 detailed description 4-68 example 2-20, 4-68 resetting to starting value 3-22 summary description 2-9 syntax 4-68 TMF 4-69 TMF attribute and the NONSTOP attribute 4-37 and the SERVERCLASS attribute 4-62 considerations 4-69 detailed description 4-69 examples 4-38, 4-70 resetting 3-22 resetting as an INTEGRITY attribute 3-22 summ
INDEX and courtesy key field 8-9 and the DELETE attribute 4-15 and the INSERT attribute 4-36 INSERT operations 8-9 values returned to record number field 7-9 UPDATE attribute and the READ attribute 4-43 consideration 4-102 detailed description 4-102 example 4-102 resetting 3-22 resetting as an ABILITY attribute 3-22 summary description 2-11 syntax 4-102 UPDATE operations multifile 8-16 providing for an application 4-102 single-file UPDATE 8-12 UPDATE BOX 8-12 VALUES attribute and a DDL VALUE clause 4-26 and
INDEX WHOLEFILES parameter ZZENLnnn file ZZENSnnn file E-2, E-5 4-49 4-55 Index-33
