HP System Dictionary/XL Utilities HP 3000 MPE/iX Computer Systems Edition 1 Manufacturing Part Number: 32256-90003 U0588 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction to SDDBD Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2. Running the SDDBD Program Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDDBD Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Input File . . . . . .
Contents 6. Running the SDDBC Program Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 SDDBC Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 The Input File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 The Log File . . . . . . . . . . . . . . . . . .
Contents Alias Name Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Schema File Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 9. Introduction to SDVPD 10. Running the SDVPD Program SDVPD Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input File . . . . . . . . . .
Contents C. SDDBC Error Messages File System Messages (4001–4074) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 Initialization Messages (4075–4099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 Driver/Validator Messages (4100–4124). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Scanner/Parser Messages (4125–4199) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Manual Organization This manual is the standard reference manual for users of the System Dictionary utilities listed below. It includes both reference information and step-by-step operating instructions for these utilities. 1. IMAGE/V Database Definition Loader Utility (SDDBD) 2. IMAGE/V Database Creation Utility (SDDBC) 3. VPLUS/V Forms Definition Loader Utility (SDVPD) The manual is organized as follows: Chapter 1 Introduction to SDDBD This chapter provides an overview of the SDDBD utility.
information on how VPLUS definitions are mapped into System Dictionary. Appendix A SDDBD Error Messages This appendix is a complete list of SDDBD errors, and includes at least one possible cause of each error and a recommended action for each cause. Appendix B SDDBD Command Abbreviations This appendix includes a list of SDDBD command words and their abbreviations.
32216-90005 HP SQL Database Administration Guide 30000-90079 VPLUS Reference Manual 30000-90042 QUERY/XL Reference Manual 36216-90003 KSAM Reference Manual 32247-90001 Transact/V Reference Manual 5953-7553 HP 3000 General Information Manual 32650-90003 MPE XL Commands Reference Manual 32650-90028 MPE XL Intrinsics Reference Manual 32650-90010 Program Design and Optimization 32650-90011 Programmer’s Utilities and Tools 32650-90022 Native Language Support Reference Manual 03000-90012 ED
1 Introduction to SDDBD Product Overview The System Dictionary IMAGE/V Database Definition Loader Utility loads structure information about an IMAGE/V database into System Dictionary from an IMAGE/V database root file. This manual describes the operation of this utility. Chapter 2, “Running the SDDBD Program,” describes the files used by SDDBD, the run options, error handling, and other information you may need when executing the utility.
Introduction to SDDBD Product Overview 12 Chapter 1
2 Running the SDDBD Program Introduction The program called SDDBD loads the IMAGE/V database information into System Dictionary from an IMAGE/V database root file. This chapter explains how to define files used in conjunction with the program and run SDDBD in either session mode or batch mode.
Running the SDDBD Program SDDBD Files SDDBD Files The Input File SDDBD accepts input from the file, SDIN. It can also take input from another MPE file by redirecting SDIN with a file equation prior to issuing the RUN command: :FILE SDIN=input file If SDIN does not exist, or has not been redirected to another file, $STDINX (or your terminal) will be used as the input file. The log file (see “The Log File” below) can be saved and renamed and then used as the input file the next time SDDBD is run.
Running the SDDBD Program SDDBD Files Record Attribute Format. The attributes for records are formatted as follows: () Action Report. SDOUT report lists the action that occurred for each entity as it was encountered during the loading process. The Action column in the report may show one of the values listed below: SKIPPED The new definition was skipped because a SKIP was requested for conflict occurrences.
Running the SDDBD Program SDDBD Run Options SDDBD Run Options When SDDBD is run, one of several run options may be specified through use of the PARM parameter of the RUN command. This parameter allows you to control SDDBD’s error handling. Using this parameter, you may specify the exact number of errors that may be encountered before the program is aborted. If, for example, two errors are acceptable, but more than two errors is not, then the PARM parameter will specify the number 3.
Running the SDDBD Program Error Handling Error Handling SDDBD recognizes three different categories of errors: 1) syntax errors, 2) operational errors, and 3) fatal errors. SDDBD responds to these errors in different ways, depending upon the category. Syntax errors are errors caused either by mistyping a command or by specifying an illegal command construction. When these errors are detected, a caret pointer is displayed pointing to the location of the error, along with an error message.
Running the SDDBD Program Control Y Handling Control Y Handling [[CONTROL]] Y is enabled in session mode when any of the following is true: • When SDDBD is expecting a command • When SDDBD is in the REDO command • When SDDBD is displaying HELP messages If [[CONTROL]] Y is entered, SDDBD displays: < Control Y > and reissues the first level command prompt (>). Once the loading process starts, [[CONTROL]] Y is disabled until the completion of the loading.
Running the SDDBD Program Session Mode vs. Batch Mode Session Mode vs. Batch Mode SDDBD can be run either in session mode or in batch mode. Some differences exist, however, between the two modes. When running in batch mode, both [[CONTROL]] Y and the REDO command are disabled. When running in session mode, any run option other than 0 or -1 is ignored. The default value of the OPTION parameter is also different between sessions and jobs.
Running the SDDBD Program Running the Program Running the Program The program is located in the file SDDBD.PUB.SYS. The program can be loaded and run by issuing the command: RUN SDDBD.PUB.SYS No file equates are needed. If the program is successfully loaded, it will print out the banner: HP System Dictionary SDDBD HP32256v.uu.ff - (C) Hewlett Packard Co.
3 SDDBD Commands Introduction This chapter includes descriptions of all SDDBD commands with their syntax, parameters, and examples. These commands are listed alphabetically for your ease of use. A HELP command is provided for a quick reference to SDDBD commands. Using this command, you can either get a list of all available commands, or a detailed description of a particular command.
SDDBD Commands MPE Commands MPE Commands MPE commands can be issued without leaving SDDBD. Whenever the caret prompt (>) for a command is present, an MPE command is issued by entering a colon (:) followed by the desired command. SDDBD passes the command on to the operating system to be processed. After the command has been completed, control is returned and the user is again prompted with the caret prompt (>) to continue.
SDDBD Commands COMMENT Command COMMENT Command The COMMENT command provides the means to enter description text into the command stream. It allows the use of text to document what is happening in the job stream without having any affect on the operation of the utility. COMMENT may be used whenever the command prompt (>) is present. The command is a very simple one. It consists of the command word COMMENT followed by zero or more characters.
SDDBD Commands DEFINE Command DEFINE Command Before the database definition can be loaded, dictionary must be opened. When opening the dictionary for the first time, the scope name and scope password are required. Syntax DEFINE [;DICTIONARY=dictionary-filename] [;SCOPE=scope-name] [;PASSWORD=[scope-password]] [;OPEN-MODE=open-mode] [;NAME-MODE=name-mode] [;DOMAIN=[domain-name]] [;VERSION=[version-name]] {.} Parameters dictionary-filename: Filename of the dictionary to be opened.
SDDBD Commands DEFINE Command Specifies which mode to open the dictionary with. The valid choices are: open-mode: shared-update exclusive-update Default is to open the dictionary in shared-update mode. If the dictionary is opened in exclusive-update mode, you will have exclusive access to the dictionary and others will be denied access. Specifies which group of names (internal or external) the user wishes to use.
SDDBD Commands EXIT Command EXIT Command To terminate SDDBD, enter EXIT. The EXIT command closes the dictionary and other opened files before terminating the program. Syntax EXIT [.] Parameters: None Example: > EXIT.
SDDBD Commands HELP Command HELP Command For a quick reference of SDDBD commands, a HELP command is available. The HELP command can be used either to get a list of all available SDDBD commands or to get a detailed description of a specific command. Syntax HELP [command] [.] Parameters: command: Name of the command If more HELP messages are requested than can fit on one screen, the following message is displayed: Continue (Y/N)? > Respond “Y” if you wish to see more messages.
SDDBD Commands HELP Command Example 2. Syntax for the DEFINE command > HELP DEFINE. The output of the above command will look like this: HELP MESSAGES FOR DEFINE <DEF> COMMAND: The DEFINE command enables you to open the System Dictionary.
SDDBD Commands IMAGE Command IMAGE Command The IMAGE command is used to specify the IMAGE database whose definitions are to be loaded into the dictionary. Syntax IMAGE [;DATABASE=data-base-name] [;PASSWORD=[password]] [;OPEN-MODE=open-mode] [;BACK-REFERENCE=back-reference-flag] [;SENSITIVITY=sensitivity] [;COMPATIBILITY-LEVEL=compatibility-option] [;OPTION=flow-control-option] [;QUIET] [;VERBOSE] {.} Parameters: data-base-name: Name of the IMAGE database whose definitions are to be loaded.
SDDBD Commands IMAGE Command System Reference Manual (32215-90003) for more information on the available IMAGE database open modes. back-reference-flag: Sets the value of the back-reference-flag attribute on the record contains element relationship. Valid values are: ON OFF If BACK-REFERENCE = ON, then the back-reference-flag attribute is set to true. If BACK-REFERENCE = OFF, back-reference-flag is set to false. The default is ON.
SDDBD Commands IMAGE Command COMPLETE If IMAGE-COMPATIBILITY is selected, then SDDBD will check only the count, byte-length, and element-type attribute values for compatibility. If COMPLETE is selected, then SDDBD will also check the display-length attribute value for compatibility. The default is IMAGE-COMPATIBILITY. flow-control-option: Determines the manner in which loading will be handled when conflicts arise.
SDDBD Commands LOAD Command LOAD Command The LOAD command starts the definition loading process. Syntax LOAD [.
SDDBD Commands REDO Command REDO Command The REDO command allows you to correct errors or to make changes to the last command you issued. When you issue the REDO command, you will enter an editing mode and the first line of the command will be displayed for modification. To modify the command, position the cursor using the space bar, under the character to be modified and enter one of the subcommands listed below. SDDBD interprets any character other than the ones listed below as a replacement character.
SDDBD Commands REDO Command [[RETURN]] Places you on the next line of the command you are editing, if you are not currently on the last line of the command. If you are on the last line, executes the command as it has been edited. Example: > DEFINE DICTIONARY=sysdic; >> SCOPPE=manager; >> PASSWORD=Mgr*; >> OPEN-MODE=shared-update.
SDDBD Commands RESET Command RESET Command This command resets all the DEFINE and IMAGE parameters to the initial state. If a parameter has a default value, the default value is assigned to it. If a parameter has no default value, the parameter value becomes void (as represented by ‘***’ in the SHOW command). The dictionary and the IMAGE database are both closed. Syntax RESET [.
SDDBD Commands SHOW Command SHOW Command SHOW displays the values of all the DEFINE and IMAGE parameters. Default values are displayed for those parameters that are not specifically assigned a value. If a parameter does not have an existing default value (e.g., the DATABASE parameter for the IMAGE command) and no value has been specifically assigned to the parameter, asterisks (***) are displayed. Syntax SHOW [.
4 Loading of IMAGE Definitions The process described below assumes that OPTION = PROMPT was specified. When other values are specified (for example, OPTION = SKIP), operation is identical to responding with an appropriate answer at the option prompt for each conflict (for example, “S” for OPTION = SKIP). When loading the database definitions, SDDBD does not load any of the image-class related information, because the IMAGE intrinsics do not provide the information.
Loading of IMAGE Definitions IMAGE Database Name IMAGE Database Name SDDBD will load the database definitions as image-database entities in the System Dictionary. For databases, a conflicting entity is defined as an entity whose definition is incompatible to the existing definition in the dictionary. Hence, SKIP, REPLACE, TERMINATE, and NEW options are effective only for the databases that have an incompatible definition in the dictionary.
Loading of IMAGE Definitions IMAGE Data Items IMAGE Data Items SDDBD will load the data items defined in the IMAGE database as element entity type in the System Dictionary.
Loading of IMAGE Definitions IMAGE Data Items Each time a data item in the IMAGE database is found to be incompatible with an existing System Dictionary element, the result is determined by the value of the OPTION parameter of the IMAGE command.
Loading of IMAGE Definitions IMAGE Data Sets IMAGE Data Sets After loading the definitions of the data items into System Dictionary, SDDBD will load the definitions of the data sets in the IMAGE/V database. The utility first creates an entity of type IMAGE-DATASET with the IMAGE/V data set name.
Loading of IMAGE Definitions IMAGE Data Sets After the successful loading of the new IMAGE data set definition or the discovery of a compatible definition, SDDBD creates the image-database contains image-dataset relationship.
Loading of IMAGE Definitions IMAGE Paths IMAGE Paths For each access path in the database, SDDBD creates the image-dataset element image-dataset image-database CHAINS relationship. The first IMAGE-DATASET is the detail data set. The first element is the search item. The second element is the sort item. If no sort item exists for the path, the blank entity (/) is assigned to the second element. The second IMAGE-DATASET is for the master data set, and the IMAGE-DATABASE is the database.
Loading of IMAGE Definitions IMAGE Paths 44 Chapter 4
5 Introduction to SDDBC Product Overview The System Dictionary IMAGE Database Creation Utility is a program which creates an IMAGE/V database schema and root file using IMAGE database definitions defined in System Dictionary. This manual describes the operation of this utility. Chapter 6, “Running the SDDBC Program,” describes the files used by SDDBC, the run options, user input rules, and other information you may need when executing the utility.
Introduction to SDDBC Product Overview 46 Chapter 5
6 Running the SDDBC Program Introduction The program called SDDBC creates an IMAGE/V data base schema and root file using IMAGE data base definitions defined in System Dictionary. This chapter explains how to define files used in conjunction with the program and run SDDBC in either session mode or batch mode.
Running the SDDBC Program SDDBC Files SDDBC Files SDDBC uses the formal file designators SDIN as the input file and SDLOG as the log file. File equates are allowed for both files. The Input File SDDBC accepts input from the file SDIN. The default for SDIN is $STDINX. Redirecting SDIN to a file, whether in session or batch mode, causes SDDBC to accept input from the specified file. The specified file must be an unnumbered file or SDDBC will not execute correctly.
Running the SDDBC Program Run Options Run Options When SDDBC is run, one of several options may be specified through the use of the PARM parameter. These options deal with the processing of the commands and the handling of any errors encountered.
Running the SDDBC Program Job Control Word Job Control Word Upon exiting from SDDBC, the Job Control Word (JCW) is set according to the termination condition of the system: 0 - Program terminated normally with EXIT FATAL - Program terminated abnormally before an EXIT This allows the batch mode user to test for the termination condition and act accordingly. JCW is set to FATAL (equivalent to -32768) whenever the system must terminate before executing an EXIT statement.
Running the SDDBC Program Running the Program Running the Program The SDDBC program may be run in session or batch mode. This section describes how to run SDDBC. Running SDDBC in Session Mode To run the program in session mode, enter the following MPE command: RUN SDDBC.PUB.SYS SDDBC will respond with the banner: HP System Dictionary SDDBC HP32256v.uu.ff - (C) Hewlett-Packard Co. 1985 A prompt character (>) is displayed, indicating that SDDBC is ready for a command.
Running the SDDBC Program Running the Program The PARM parameter is used to specify the action of the job if an error is encountered. In the above example, the program is aborted if 10 errors are found. Refer to the heading in this chapter, “Run Options”, for more details on the PARM parameter. Finally, the Job Control Word (JCW) shows whether the system executed successfully or terminated abnormally.
Running the SDDBC Program User Input Rules User Input Rules Special Character Responses The following characters have special meanings when used in response to an SDDBC prompt: CHARACTER DESCRIPTION [[CONTROL]] X Ignores the line on which the [[CONTROL]] X was typed. The system types three exclamation points (!!!) and then waits for the user to reenter the data for the line. [[CONTROL]] Y Returns to the highest prompt (>) level. In response to the >> prompt, terminates the command without executing.
Running the SDDBC Program User Input Rules User Input Rules Special Character Responses The following characters have special meanings when used in response to an SDDBC prompt: CHARACTER DESCRIPTION [[CONTROL]] X Ignores the line on which the [[CONTROL]] X was typed. The system types three exclamation points (!!!) and then waits for the user to reenter the data for the line. [[CONTROL]] Y Returns to the highest prompt (>) level. In response to the >> prompt, terminates the command without executing.
Running the SDDBC Program System Dictionary Command Language System Dictionary Command Language The general format of the System Dictionary Command Language for SDDBC is: • a command • one or more keyword clauses (if required) The System Dictionary Command Language is free formatted, which means the command and keyword clauses may appear on the same or different lines. Commands and keyword clauses are considered to be phrases and the order of these phrases is important.
Running the SDDBC Program System Dictionary Command Language invalid characters embedded); otherwise, it is required. [[ ]] Blanks must be used to separate a command and its keyword clauses. Any number of blanks may appear between any name and any punctuation character. [[RETURN]] Treated the same as a blank. Wherever a blank is legal, a [[RETURN]] is legal. (Except within a quoted scope password.
7 SDDBC Commands Introduction This chapter includes descriptions of all SDDBC commands with their syntax, parameters, and examples. These commands are listed alphabetically for your ease of use. A HELP command is provided for a quick reference to SDDBC commands. Using this command, you can either get a list of all available SDDBC commands, or a detailed description of a particular command.
SDDBC Commands MPE Commands MPE Commands MPE commands can be issued without leaving SDDBC. Whenever the prompt for a command (>) is present, an MPE command is issued by entering a colon (:) followed by the command desired. SDDBC passes the command on to the operating system to be processed. After the command has been completed, control is returned and the user is prompted (>) to continue. MPE commands that can be issued from SDDBC are the ones which are supported by the MPE COMMAND intrinsic.
SDDBC Commands COMMENT Commands COMMENT Commands The COMMENT command provides the means to enter description text into the command stream. It allows the use of text to document what is happening in the job stream without having any affect on the operation of the utility. COMMENT may be used whenever the command prompt (>) is present. The command is a very simple one. It consists of the command word COMMENT followed by zero or more characters.
SDDBC Commands CREATE Command CREATE Command Starts the schema and root file creation process. In order for this command to execute, the dictionary must be opened by using the DEFINE command and the database for which a schema and root file are to be created must be specified by using the IMAGE command. ([[CONTROL]] Y is disabled.) Syntax CREATE [.
SDDBC Commands DEFINE COMMAND DEFINE COMMAND Before the schema and root file for an Image database can be created, the dictionary must be opened. When opening the dictionary, the scope name and scope password are required. Once the dictionary is opened, one can redefine other options to change the environment while in a session.
SDDBC Commands DEFINE COMMAND Default is to open the dictionary in read-only mode. After the dictionary is opened, this parameter can be used to change the open mode. name-mode: Specifies which group of names (internal or external) the user wishes to use. The valid choices are: internal external Default is to use the external name mode. domain-name: Name of the dictionary domain to be used for creating or retrieving definitions. If not specified, the default is the common domain.
SDDBC Commands EXIT Command EXIT Command To terminate SDDBC enter EXIT. The EXIT command closes the dictionary and other opened files before terminating the program. Syntax EXIT [.] Parameter: None Example: > EXIT.
SDDBC Commands HELP Command HELP Command For a quick reference of SDDBC commands, a HELP command is available. The HELP command can be used either to get a list of all available SDDBC commands or to get a detailed description of a specific command. Syntax HELP [command] [.] Parameters: command: Name of the command Example 1.
SDDBC Commands HELP Command Example 2. Syntax for the DEFINE command > HELP DEFINE. The output of the above command will look like this: Define/Redefine the dictionary environment SYNTAX: DEFINE [;DICTIONARY = dictionary-name] [;SCOPE = scope-name] [;PASSWORD = [scope-password]] [;OPEN-MODE = open-mode] [;NAME-MODE = name-mode] [;DOMAIN = [domain-name]] [;VERSION = version-name] [;STATUS = version-status] .
SDDBC Commands IMAGE Command IMAGE Command The IMAGE command is used to specify the database and the information used by the schema processor when generating a schema and root file. Syntax IMAGE [;DATABASE=data-base-name] [;CONTROL=(control-list)] [;SCHEMA=schema-file-name] [;OUTPUT=output-listing] [;NAME=primary-or-alias] [;CONFLICT=action-on-conflict] [;COMMENT=comment-option] [;ORDER=order-by-set-type-option] {.
SDDBC Commands IMAGE Command output-listing: Specifies where the output listing of the schema generated by DBSCHEMA should be sent. Valid values are: TERMINAL sends the listing to the terminal. PRINTER sends the listing to the line printer. NULL suppresses the listing. filename sends the listing to the specified file. If the file does not exist, a new file is created. If the file exists, you will be asked for permission to overwrite it.
SDDBC Commands IMAGE Command anything, the default is SUBSTITUTE. Option to generate comment lines or not. Valid values are: comment-option: TRUE FALSE If not specified, default is TRUE. order-by-set-type-option: Option to generate data sets by data set type in the order of AUTOMATIC, MANUAL, and DETAIL. The valid values are: TRUE FALSE If not specified, the default is TRUE. If this option is set to FALSE, the data sets will be generated in the order they are retrieved.
SDDBC Commands REDO Command REDO Command The REDO command allows you to correct errors or to make changes to the last command you issued. When you issue the REDO command, you will enter an editing mode and the first line of the command will be displayed for modification. To modify the command, position the cursor using the space bar, under the character to be modified and enter one of the subcommands listed below. SDDBC interprets any character other than the ones listed below as a replacement character.
SDDBC Commands REDO Command [[RETURN]] Places you on the next line of the command you are editing, if you are not currently on the last line of the command. If you are on the last line, executes the command as it has been edited. Example: > DEFINE DICTIONARY=sysdic; >> SCOPPE=manager; >> PASSWORD=Mgr*; >> OPEN-MODE=shared-update.
SDDBC Commands RESET Command RESET Command This command resets all the information specified by the DEFINE and IMAGE commands to their initial state. If a parameter has a default value, then the default value is reassigned to it. The dictionary is closed. Syntax RESET Parameter: [.] None Example: > RESET.
SDDBC Commands Show Command Show Command Show the current state of the environment. All the information that can be specified by the DEFINE and IMAGE commands is listed. Syntax SHOW [.
8 Schema Generation Process This chapter describes how SDDBC creates the schema based on definitions in the System Dictionary. The description is organized in a fashion that follows the overall schema structure. If you are not familiar with schema structure, refer to the section in the Turbo IMAGE/V Reference Manual (32215-90050) entitled “Defining a Database.
Schema Generation Process Database Database SDDBC searches the IMAGE-DATABASE entity for the database specified in the IMAGE command. This entity is used as the database name in the schema. The attribute value of image-database-type is used to determine if the database is a TurboIMAGE database. Passwords To get the user classes and passwords for the database, SDDBC searches the IMAGE-DATABASE contains IMAGE-CLASS relationships.
Schema Generation Process Database Data Sets SDDBC gets the data sets and all related data items within each data set from System Dictionary as described previously under “Items”. Based upon the ORDER option, the data sets are generated in the order of either AUTOMATIC, MANUAL, and DETAIL, or in the order of retrieval. If data sets are generated by set type order, within each type they are generated in the order they were retrieved.
Schema Generation Process Schema Comment Lines Schema Comment Lines When generating the schema, SDDBC uses the variable length attribute description as comment lines whenever possible to document the definitions as they are generated. These include descriptions about the database entity, IMAGE-DATABASE contains IMAGE-CLASS relationships, element entities, dataset entities, and RECORD contains ELEMENT relationships.
Schema Generation Process Alias Name Option Alias Name Option If name option is ALIAS, data names are generated from the dictionary as described below. For database name, the IMAGE-ALIAS name of the database entity is used. If IMAGE-ALIAS name does not exist, then the primary name will be used. For data item name, the IMAGE-ALIAS name from relationship of relationship-type RECORD contains ELEMENT is used.
Schema Generation Process Schema File Processing Schema File Processing If there is no error when the schema is generated, SDDBC will automatically invoke the Schema Processor IMAGE utility, DBSCHEMA, to process the schema. Refer to the IMAGE/V Reference Manual (32215-90003) for details about schema processing. If you only want to create a schema but not the root file, you can enter a NOROOT option in the IMAGE command using the CONTROL keyword.
9 Introduction to SDVPD The System Dictionary VPLUS/V Forms Definition Loader Utility loads information about VPLUS/V forms into System Dictionary from a VPLUS/V forms file. This manual describes the operation of this utility. Chapter 10, “Running the SDVPD Program,” describes the files used by SDVPD, the run options, error handling, and other information you may need when executing the utility.
Introduction to SDVPD 80 Chapter 9
10 Running the SDVPD Program The System Dictionary VPLUS/V Forms Definition Loader, SDVPD, loads the VPLUS/V forms information into System Dictionary from the VPLUS/V forms file. This chapter explains how to run SDVPD, defines the files used by the SDVPD program, and explains the available run options.
Running the SDVPD Program SDVPD Files SDVPD Files Input File SDVPD accepts input from the file, SDIN. It can also take input from another MPE file by redirecting SDIN with a file equation prior to issuing the RUN command: :FILE SDIN=input file If SDIN does not exist, or has not been redirected to another file, $STDINX (or your terminal) will be used as the input file. The log file (see “The Log File” below) can be saved and renamed and then used as the input file the next time SDVPD is run.
Running the SDVPD Program SDVPD Files TERMINATED The loading process terminated at this entity because of a conflict. The entity with the TERMINATED action was not loaded. ERROR An error has occurred while loading the definition. This usually represents a more serious error. OLD USED A compatible entity definition was found in the dictionary, and the new entity definition was not loaded. The relationships were still established using the old definition.
Running the SDVPD Program Run Options Run Options When SDVPD is run, one of several run options may be specified through use of the PARM parameter of the RUN command. This parameter allows you to control SDVPD’s error handling. Using this parameter, you may specify the exact number of errors that may be encountered before the program is aborted. If, for example, two errors are acceptable, but more than two errors is not, then the PARM parameter will specify the number 3.
Running the SDVPD Program Error Handling Error Handling SDVPD recognizes three different categories of errors: 1) syntax errors, 2) operational errors, and 3) fatal errors. SDVPD responds to these errors in different ways, depending upon the category. Syntax errors are errors caused either by mistyping a command or by specifying illegal command construction. When these errors are detected, a caret pointer is displayed pointing to the location of the error, along with an error message.
Running the SDVPD Program Control Y Handling Control Y Handling [[CONTROL]] Y is enabled in session mode when any of the following is true: • When SDVPD is expecting a command • When SDVPD is in the REDO command • When SDVPD is displaying HELP messages If [[CONTROL]] Y is entered, SDVPD displays: < Control Y > and reissues the first level command prompt (>). Once the loading process starts, [[CONTROL]] Y is disabled until the completion of the loading.
Running the SDVPD Program Running the Program Running the Program The SDVPD program is located in the PUB group of the SYS account. The program can be loaded and run by issuing the command: RUN SDVPD.PUB.SYS No file equates are needed. If the program is successfully loaded, it will print out the banner: HP System Dictionary SDVPD HP32256v.uu.ff -(C) Hewlett Packard Co. 1985 Session Mode vs. Batch Mode SDVPD can be run either in session mode or in batch mode.
Running the SDVPD Program Running the Program 88 Chapter 10
11 SDVPD Commands This chapter includes descriptions of each SDVPD command with their syntax, parameters, and examples. These commands are listed alphabetically for your ease of use. A command is provided for a quick reference to SDVPD commands. Using this command, you can either get a list of all available SDVPD commands, or a detailed description of a particular command.
SDVPD Commands MPE Commands MPE Commands MPE commands can be issued without leaving SDVPD. Whenever the caret prompt (>) for a command is present, an MPE command is issued by entering a colon (:) followed by the desired command. SDVPD passes the command on to the operating system to be processed. After the command has been completed, control is returned and the user is again prompted with the caret prompt (>) to continue.
SDVPD Commands DEFINE Command DEFINE Command Before the forms file definitions can be loaded, the dictionary must be opened. When opening the dictionary for the first time, the scope name and scope password are required. Syntax DEFINE [;DICTIONARY=dictionary-filename] [;SCOPE=scope-name] [;PASSWORD=[scope-password]] [;OPEN-MODE=open-mode] [;NAME-MODE=name-mode] [;DOMAIN=[domain-name]] [;VERSION=[version-name]] {.} Parameters: dictionary-filename: Filename of the dictionary to be opened.
SDVPD Commands DEFINE Command shared-update exclusive-update Default is to open the dictionary in shared-update mode. If the dictionary is opened in exclusive-update mode, you will have exclusive access to the dictionary and others will be denied access. name-mode: Specifies which group of names (internal or external) the user wishes to use. The valid choices are: internal external Default is to use the external name mode.
SDVPD Commands EXIT Command EXIT Command To terminate SDVPD, enter EXIT. The EXIT command closes the dictionary and other opened files before terminating the program. Syntax EXIT [.] Parameters: None Example: > EXIT.
SDVPD Commands HELP Command HELP Command For a quick reference of SDVPD commands, a HELP command is available. The HELP command can be used either to get a list of all available SDVPD commands or to get a detailed description of a specific command. Syntax HELP [command] [.] Parameters: command: Name of the command If more HELP messages are requested than can fit on one screen, the following message is displayed: Continue (Y/N)? > Respond “Y” if you wish to see more messages.
SDVPD Commands HELP Command Example 2. Syntax for the DEFINE command > HELP DEFINE. The output of the above command will look like this: HELP MESSAGES FOR DEFINE COMMAND: The DEFINE command enables you to open the System Dictionary. SYNTAX: DEFINE [;DICTIONARY = dictionary-name ] [;SCOPE = scope-name ] [;PASSWORD = [scope-password]] [;DOMAIN = [domain-name] ] [;VERSION = [version-name] ] [;OPEN-MODE = open-mode ] [;NAME-MODE = name-mode ] .
SDVPD Commands LISTFORMS Command LISTFORMS Command LISTFORMS lists the names of the forms contained in the currently open forms file. The form name, form number, and the number of fields in the form are listed for each form. If no form file is open, any attempt to list form names produces an error. Syntax LISTFORMS {.
SDVPD Commands LOAD Command LOAD Command The LOAD command starts the VPLUS forms file definition loading process. To load specific forms from the forms file, specify the form names after the command. To load all forms definitions from the forms file, issue the command with no forms names following it. Syntax LOAD [ formname1formname2... formname3] {.
SDVPD Commands REDO COMMAND REDO COMMAND The REDO command allows you to correct errors or to make changes to the last command you issued. When you issue the REDO command, you will enter an editing mode and the first line of the command will be displayed for modification. To modify the command, position the cursor using the space bar, under the character to be modified and enter one of the subcommands listed below. SDVPD interprets any character other than the ones listed below as a replacement character.
SDVPD Commands REDO COMMAND [[RETURN]] Places you on the next line of the command you are editing, if you are not currently on the last line of the command. If you are on the last line, executes the command as it has been edited. Example: > DEFINE DICTIONARY=sysdic; >> SCOPPE=manager; >> PASSWORD=Mgr*; >> OPEN-MODE=shared-update.
SDVPD Commands RESET Command RESET Command This command resets all the DEFINE and VPLUS parameters to the initial state. If a parameter has a default value, the default value is assigned to it. If a parameter has no default value, the parameter value becomes void (as represented by '***' in the SHOW command). The dictionary and the VPLUS forms file are both closed. Syntax RESET [.
SDVPD Commands SHOW Command SHOW Command SHOW displays the values of all the DEFINE and VPLUS parameters. Default values are displayed for those parameters that were not specifically assigned a value. If a parameter without an existing default value (e.g., FORMSFILE parameter for the VPLUS command) has not been initialized, asterisks (***) are displayed. Syntax SHOW [.
SDVPD Commands VPLUS Command VPLUS Command The VPLUS command is used to specify the VPLUS forms file whose definitions are to be loaded into System Dictionary, plus other parameters related to the definition loading process. Syntax VPLUS [;FORMSFILE=formsfile-name] [;SENSITIVITY=sensitivity] [;CHAR=char-conv-option] [;HYPHEN=hyphen-option] [;COMPATIBILITY-LEVEL=compatibility-option] [;CHECK-ELEM-TYPE=check-elem-type-option] [;OPTION=flow-control-option] [;QUIET] [;VERBOSE] {.
SDVPD Commands VPLUS Command When “9” is selected, all fields of VPLUS character type DIG that are in the dictionary are converted to type “9” and all other VPLUS fields are converted to type “X”. When 9 is selected, the byte-length attribute value is also set to that of the display-length attribute value. The default is OFF. hyphen-option: Enables conversion of underscores to hyphens.
SDVPD Commands VPLUS Command Terminate (S/R/N/T)? > SKIP The new definition is skipped and not loaded. REPLACE The new definition will replace the old definition. The old definition and all the relationships involving it will be permanently deleted. NEW A prompt for a new name is issued. The name entered will become the name of the entity and the original name is assigned to the vplus-alias attribute. TERMINATE The loading process terminates immediately.
12 Loading VPLUS/V Definitions The process described below assumes that OPTION = PROMPT was specified. Operation when other values are specified is obvious from the explanations below because, in a sense, the PROMPT option includes all other options. For example, OPTION = SKIP is identical to specifying “S” at the option prompt for each conflict.
Loading VPLUS/V Definitions VPLUS/V Forms File VPLUS/V Forms File At first, SDVPD creates an entity of type FORMSFILE, using the name of the VPLUS/V forms file. Each formsfile is used in creating the subsequent FORMSFILE contains FORM relationship.
Loading VPLUS/V Definitions VPLUS/V Forms File the VPLUS command. Element type is determined from the table below: VPLUS/V Data Type System Dictionary/XL Element Data Type DIG (1 <= s <= 9) I+ DIG (9 < s) P+ IMPn (1 <= s <= 10) I IMPn (10 < s) P NUMn (1 <= s <= 10) I NUMn (10 < s) P NUM R CHAR X DATE X where s is the size of the VPLUS field and n the decimal places.
Loading VPLUS/V Definitions VPLUS/V Forms File Each field is related to its form through the FORM contains ELEMENT relationship. The attributes field-enhancement, field-type, display-length, element-type, field-number, decimal, and byte-offset are initialized for the relationship. Compatible and Incompatible Elements.
A SDDBD Error Messages The following is a complete listing of SDDBD errors listed in order by error number. The list includes at least one possible cause of the error and a recommended action for each cause. The list is divided into the following groups: Message Number Error Type 2501–2602 SDDBD Warning Messages 2601–2821 SDDBD Error Messages Some System Dictionary error messages list a cause as “An unexpected subsystem error has occurred.
SDDBD Error Messages SDDBD WARNING Messages (2501–2602) SDDBD WARNING Messages (2501–2602) 2501 MESSAGE: Image database ! already defined in dictionary (SDWARN 2501) CAUSE: A database definition with the same name already exists in the dictionary. ACTION: None necessary. SDDBD will take the action specified in the OPTION clause of the IMAGE command.
SDDBD Error Messages SDDBD WARNING Messages (2501–2602) 2508 MESSAGE: Compatible definition for database ! used (SDWARN 2508) CAUSE: A database definition of the same type already exists in the dictionary. ACTION: None necessary. SDDBD will use the existing entity definition in the dictionary instead of trying to create it, and then will continue processing.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) SDDBD ERROR MESSAGES (2601–2821) 2601 MESSAGE: Unknown SDDBD command (SDERR 2601) CAUSE: The user has given SDDBD an unrecognizable command. ACTION: The user should give a command that SDDBD recognizes; these commands are listed in the manual, and can also be obtained by entering the HELP command. 2603 MESSAGE: Expecting 'Y' or 'N' answer (SDERR 2603) CAUSE: The user entered a response other than Y or N to the prompt. ACTION: Enter Y or N.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2620 MESSAGE: Unknown DEFINE parameter (SDERR 2620) CAUSE: The parameter being specified is not recognizable by SDDBD. ACTION: Use the HELP DEFINE command to list the set of valid parameters, or look under the DEFINE command in the manual for the valid parameters. 2621 MESSAGE: Expecting dictionary name (SDERR 2621) CAUSE: The dictionary name was not supplied in the DICTIONARY parameter.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2635 MESSAGE: Illegal sensitivity value (SDERR 2635) CAUSE: The value supplied for the sensitivity PARAMETER is not valid. ACTION: The valid values are READ, MODIFY or PRIVATE. 2636 MESSAGE: Illegal option specification (SDERR 2636) CAUSE: The value supplied for the OPTION parameter is not valid. ACTION: The valid values are PROMPT, SKIP REPLACE, NEW or TERMINATE.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2712 MESSAGE: No database open (SDERR 2712) CAUSE: No IMAGE database has been specified to load the definitions from. ACTION: Specify an IMAGE database using the IMAGE command. 2713 MESSAGE: Error while retrieving data set list (MODE 203, SDERR 2713) CAUSE: An IMAGE error was encountered in retrieving the list of data sets in the IMAGE database. (DBINFO mode 203) ACTION: Notify the Database Administrator.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2730 MESSAGE: Unknown IMAGE data item type (SDERR 2730) CAUSE: An invalid data item type was found on an IMAGE data item. ACTION: Notify the Database Administrator. 2731 MESSAGE: Error while retrieving master set’s key item (MODE 302, SDERR 2731) CAUSE: The password and open mode with which the IMAGE database was opened does not give access to the manual set's key item.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2736 MESSAGE: Error while creating new SDLOG. Logging disabled (SDERR 2736) CAUSE: A MPE file system error was detected when attempting to create a new SDLOG file. ACTION: The commands you enter will not be logged, as the logging is disabled. If the command logging is important, exit the program immediately, take care of the problem, and reenter SDDBD. If a more serious problem is suspected, notify the System Manager.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2741 MESSAGE: Error while reading from message buffer file (SDREDO:SDERR 2741) CAUSE: An MPE file system error is encountered while reading from the message buffer file. ACTION: SDDBD will immediately stop processing this multi-line message. If a serious problem is suspected, notify the System Manager.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2752 MESSAGE: Duplicate internal database name ! found in external name mode (SDERR 2752) CAUSE: While attempting to create the IMAGE-DATABASE definition, SDDBD found an old definition with the same internal name. However, because the current name mode is external, SDDBD cannot retrieve the old definition.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) ACTION: Check the intrinsic error message(s) and notify the Dictionary Administrator or the System Manager if a serious error is suspected. See if you have read access to the old element. 2760 MESSAGE: Duplicate internal ELEMENT name ! found in external name mode (SDERR 2760) CAUSE: While attempting to create the ELEMENT definition, SDDBD found an old definition with the same internal name.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) ACTION: Because SDDBD cannot retrieve the old definition, SDDBD will skip the step to determine if the old definition is compatible with the new. Instead, SDDBD will take action immediately according to the value of the OPTION parameter. 2766 MESSAGE: Error while loading record definition for ! (SDERR 2766) CAUSE: SDDBD could not load the record definition.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2773 MESSAGE: Command line out of range. Ignored (SDERR 2773) CAUSE: The +/- REDO subcommand issued results in a line outside of the bounds of the currently edited command. ACTION: Make sure that the number specified with the +/- subcommand is within the bounds of the edited command. 2774 MESSAGE: Illegal command after delete. Ignored (SDERR 2774) CAUSE: Only the I subcommand is allowed after the D subcommand.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) ACTION: Notify the System Manager. 2797 MESSAGE: Entity ! inaccessible or owned by other scope in other version (SDERR 2797) CAUSE: The entity exists and you do not have read access to it. ACTION: None necessary. SDDBD will use the OPTION parameter of the IMAGE command to determine what to do. CAUSE: The entity exists in another version of the domain and is owned by a different scope. ACTION: None necessary.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2806 MESSAGE: Error while reading from SDOUT. Program aborted (SDERR 2806) CAUSE: A disc error occurred while reading from temporary SDOUT to output the report onto the $STDLIST. ACTION: Check the file system error message. Notify the System Manager if a serious disc error is suspected. 2807 MESSAGE: Error while writing to SDOUT. Program aborted (SDERR 2807) CAUSE: A disc error occurred while writing to SDOUT.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2814 MESSAGE: Error while reading from temporary file SDREDO. Program aborted (SDERR 2814) CAUSE: A disc error occurred while reading from temporary file SDREDO. SDDBD reads from SDREDO when the user enters E or [[CONTROL]] Y while in REDO. ACTION: Check the file system error message, and notify the Dictionary Administrator or the System Manager if a serious error is suspected. 2815 MESSAGE: Error while writing to temporary file SDREDO.
SDDBD Error Messages SDDBD ERROR MESSAGES (2601–2821) 2821 MESSAGE: Exceeded max number of tries for a valid DB password. Prog aborted (SDERR 2821) CAUSE: A correct password was not entered at the DB password prompt in three tries. Because the program was running in batch mode, the program will be aborted. ACTION: Edit your input file and re-stream the job. None MESSAGE: Message catalog (SDCAT.PUB.SYS) open error CAUSE: SDCAT.PUB.SYS message catalog does not exist.
B SDDBD Command Abbreviations SDDBD accepts abbreviations of the command key words. The table underneath lists each SDDBD key word and the corresponding abbreviation.
SDDBD Command Abbreviations Keyword Abbreviation COMPATIBILITY-LEVEL CL IMAGE-COMPATIBILITY IC COMPLETE C OPTION OP PROMPT PR SKIP SK REPLACE RE TERMINATE T NEW N QUIET Q VERBOSE V LOAD L HELP H SHOW SH REST R REDO REDO COMMENT COM EXIT E 128 Appendix B
C SDDBC Error Messages The following is a complete listing of SDDBC errors listed in order by error number. The list includes at least one possible cause of the error and a recommended action for each cause.
SDDBC Error Messages Some of these messages, as shown in this manual, include an exclamation point (! ). This character serves as a substitution character, and stands for a parameter (such as a file name) which will be displayed as part of the actual message instead of the ! .
SDDBC Error Messages File System Messages (4001–4074) File System Messages (4001–4074) 4001 0MESSAGE: Dictionary cannot be opened (SDERR 4001) CAUSE: The dictionary could not be opened with the specified DEFINE command. ACTION: Refer to the associated error and correct the indicated problem. 4002 0MESSAGE: Dictionary cannot be closed (SDERR 4002) CAUSE: The dictionary could not be closed. ACTION: Refer to the associated error and correct the indicated problem.
SDDBC Error Messages File System Messages (4001–4074) 4011 0MESSAGE: Input file recsize too long. All lines trunc to 80 chars (SDWARN 4011) CAUSE: The input file has a record size greater than 80 characters. All input lines are a maximum of 80 characters so all lines will be truncated to 80 characters. ACTION: If the commands in the input file do not take up more than 80 characters per line, no action is needed.
SDDBC Error Messages File System Messages (4001–4074) 4020 0MESSAGE: Unable to rewind temporary file ! (SDERR 4020) CAUSE: Could not reset the file pointer of the specified temporary file to the beginning of the file. ACTION: Contact the DA (remember to get the associated file error). Internal Error. 4021 0MESSAGE: Unable to reposition name file to record number ! (SDERR 4021) CAUSE: Could not reset the file pointer of the name file to the specified record number.
SDDBC Error Messages File System Messages (4001–4074) ACTION: Contact the DA (remember to get the associated file error). Internal Error. 4031 0MESSAGE: Unable to open the $STDINX file (SDERR 4031) CAUSE: Unable to open the $STDINX file to read the prompted scope password. ACTION: Contact the DA (remember to get the associated file error). Internal Error.
SDDBC Error Messages Initialization Messages (4075–4099) Initialization Messages (4075–4099) 4075 0MESSAGE: Unable to find the Banner message in the catalog (SDERR 4075) CAUSE: The banner message could not be retrieved from the message catalog. ACTION: Contact the DA to get a new copy of the catalog with the banner message in it. 4076 0MESSAGE: The number is not a 16 bit integer (SDERR 4076) CAUSE: The indicated number is greater than 32767. ACTION: Change the number so it is less than or equal to 32767.
SDDBC Error Messages Initialization Messages (4075–4099) 4083 0MESSAGE: SDDBC and Dictionary Intrinsics versions not compatible (SDERR 4083) CAUSE: The version of the SDDBC program and the System Dictionary intrinsics are not compatible. ACTION: Contact the DA to get a new copy of the SDDBC program that is compatible with the version of the intrinsics that is on the system.
SDDBC Error Messages Driver/Validator Messages (4100–4124) Driver/Validator Messages (4100–4124) 4100 0MESSAGE: Exceeded maximum number of allowed errors (SDWARN 4100) CAUSE: The program encountered the number of errors specified as the maximum in the PARM option. ACTION: Correct the error(s) found and either rerun or finish running the job. 4101 0MESSAGE: Logging has been disabled (SDWARN 4101) CAUSE: Logging has been disabled because the user does not want the program to overwrite an existing log file.
SDDBC Error Messages Driver/Validator Messages (4100–4124) 4107 0MESSAGE: Command not valid when the dictionary is not open (SDERR 4107) CAUSE: The command entered is not allowed before the dictionary is opened. ACTION: Issue a command that is valid before the dictionary is opened or open the dictionary and then issue the command.
SDDBC Error Messages Scanner/Parser Messages (4125–4199) Scanner/Parser Messages (4125–4199) 4125 0MESSAGE: Missing close quote on a character string (SDERR 4125) CAUSE: There is no closing quote on the character string specified. ACTION: Insert a closing quote in the specified location. 4126 0MESSAGE: Invalid character found (SDERR 4126) CAUSE: A character not allowed in the local language was found. ACTION: Remove the indicated character from the command string.
SDDBC Error Messages Scanner/Parser Messages (4125–4199) CAUSE: There is a token missing at the indicated position. ACTION: Review the command syntax and insert the token at the indicated position. 4132 0MESSAGE: Characters found after the end of the command (SDERR 4132) CAUSE: Characters were found after the period ending the command. ACTION: Remove the extra characters that follow the period from the command.
SDDBC Error Messages Scanner/Parser Messages (4125–4199) 4142 0MESSAGE: Invalid output destination (SDERR 4142) CAUSE: The specified output destination value is invalid. ACTION: Correct the output destination value so it is valid. 4143 0MESSAGE: Invalid version status (SDERR 4143) CAUSE: The specified version status value is invalid. ACTION: Correct the version status value so it is valid. 4144 0MESSAGE: Unexpected quoted value (SDERR 4144) CAUSE: A quoted value is not allowed at the indicated position.
SDDBC Error Messages Scanner/Parser Messages (4125–4199) 4152 0MESSAGE: Invalid control (SDERR 4152) CAUSE: The specified control value is invalid. ACTION: Correct the control value so it is valid. 4153 0MESSAGE: Invalid comment (SDERR 4153) CAUSE: The specified comment value is invalid. ACTION: Correct the comment value so it is valid.
SDDBC Error Messages Define Messages (4200–4209) Define Messages (4200–4209) 4200 0MESSAGE: Both VERSION and STATUS were specified. STATUS is ignored (SDWARN 4200) CAUSE: Both the VERSION and STATUS keywords cannot be specified in the same command. Either VERSION for a specific version, or STATUS for the last version of the given status, should be used. ACTION: Do nothing and the version will be used and the status ignored.
SDDBC Error Messages Help Messages (4210–4224) Help Messages (4210–4224) 4210 0MESSAGE: Expected a command or a period (SDERR 4210) CAUSE: The characters after the HELP command must be either a command or a period. ACTION: Remove the unexpected characters and replace them with a command, a period or blanks. 4211 0MESSAGE: Expected a period (SDERR 4211) CAUSE: A period was expected in the indicated position. ACTION: Remove the unexpected characters and replace them with a period or blanks.
SDDBC Error Messages Redo Messages (4225–4249) Redo Messages (4225–4249) 4225 0MESSAGE: Cannot REDO a REDO command (SDERR 4225) CAUSE: The REDO command cannot be used to change a command into a REDO command. ACTION: Do not change the command being edited into REDO. 4226 0MESSAGE: REDO only allowed when input is interactive (SDERR 4226) CAUSE: The REDO command is only allowed when the program is run interactively. Input can be coming from $STDIN or from a redirected $STDIN.
SDDBC Error Messages Redo Messages (4225–4249) 4232 0MESSAGE: + and -NOT allowed in a number (SDERR 4232) CAUSE: The numbers used to move within the redo buffer cannot involve a + or -. ACTION: Remove the + or -from the number specifying how far to move and simply use the appropriate command to specify direction (+ to move forward and -to move backward).
SDDBC Error Messages Image Messages (4250–4299) Image Messages (4250–4299) 4250 0MESSAGE: Image database name truncated to 6 characters (SDWARN 4250) CAUSE: The indicated name is too long to be an IMAGE database name. It was truncated to 6 characters. ACTION: No action is needed. 4251 0MESSAGE: Exceeded the maximum size for a control list (SDERR 4251) CAUSE: The inputted control list is longer than 80 characters. 80 characters is the maximum size for a control list in this program.
SDDBC Error Messages Image Messages (4250–4299) 4259 0MESSAGE: Unable to close the schema list file (SDERR 4259) CAUSE: The schema list file could not be closed. ACTION: Contact the DA (remember to get the associated file error). Internal Error. 4260 0MESSAGE: Unable to create the schema list file (SDERR 4260) CAUSE: The schema list file could not be created. ACTION: Contact the DA (remember to get the associated file error). Internal Error.
SDDBC Error Messages Image Messages (4250–4299) 4269 0MESSAGE: Unable to open schema file to retrieve the actual file name (SDERR 4269) CAUSE: The schema file could not be opened to retrieve the actual file name. ACTION: Contact the DA (remember to get the associated file error). Internal Error. 4270 0MESSAGE: Unable to open list file to retrieve the actual file name (SDERR 4270) CAUSE: The schema list file could not be opened to retrieve the actual file name.
SDDBC Error Messages Create Messages (4300–4399) Create Messages (4300–4399) 4300 0MESSAGE: Database to be created is not defined (SDERR 4300) CAUSE: The database to be created has not yet been defined by the IMAGE command. ACTION: Use the IMAGE command to define the database to be created. 4301 0MESSAGE: Cannot do file equate for DBSTEXT (SDERR 4301) CAUSE: Unable to issue the file equate for the textfile for DBSCHEMA through the Command intrinsic.
SDDBC Error Messages Create Messages (4300–4399) 4307 0MESSAGE: Cannot get image-database contains image-class relationship (SDERR 4307) CAUSE: Unable to retrieve information about the specified image-database and image-class relationship. ACTION: Contact the DA (remember to get the associated SD intrinsic error). Internal Error.
SDDBC Error Messages Create Messages (4300–4399) 4314 0MESSAGE: Cannot find image-dataset contains record relationship (SDERR 4314) CAUSE: Unable to retrieve information about image-dataset contains record relationship. ACTION: Contact the DA (remember to get the associated SD intrinsic error). Internal Error. 4315 0MESSAGE: Cannot get image-dataset contains record relationship (SDERR 4315) CAUSE: Unable to retrieve information about image-dataset contains record relationship.
SDDBC Error Messages Create Messages (4300–4399) 4322 0MESSAGE: Cannot get element entity (SDERR 4322) CAUSE: Unable to retrieve information about an element entity. ACTION: Contact the DA (remember to get the associated SD intrinsic error). Internal Error. 4323 0MESSAGE: Cannot get element primary name (SDERR 4323) CAUSE: Unable to retrieve the primary name of the element. ACTION: Contact the DA (remember to get the associated SD intrinsic error). Internal Error.
SDDBC Error Messages Create Messages (4300–4399) 4330 0MESSAGE: Image alias does not exist for element !. Primary name used (SDWARN 4330) CAUSE: The specified element does not have an alias. Therefore, the primary name was used. ACTION: No action is needed. 4331 0MESSAGE: Image alias does not exist for data set !. Primary name used (SDWARN 4331) CAUSE: The specified data set does not have an alias. Therefore, the primary name was used. ACTION: No action is needed.
SDDBC Error Messages Create Messages (4300–4399) ACTION: Use the User Interface or other means to correct the element-type attribute value. Also change the edit value for this attribute to conform with HP standard. 4338 0MESSAGE: Sort error. Number is ! (SDERR 4338) CAUSE: Unable to sort the element names. ACTION: Contact the DA (remember to get the associated error). Internal Error. 4339 0MESSAGE: Sort end error. (SDERR 4339) CAUSE: Unable to end the element name sort. ACTION: Contact the DA.
SDDBC Error Messages Create Messages (4300–4399) 4346 0MESSAGE: Name truncated to 16 characters (SDWARN 4346) CAUSE: A name was truncated because it exceeded 16 characters. ACTION: No action is needed. 4347 0MESSAGE: Cannot find image data set uses device class relationship (SDERR 4347) CAUSE: Unable to retrieve information about IMAGE data set uses device class relationship. ACTION: Contact the DA (remember to get the associated SD intrinsic error). Internal Error.
SDDBC Error Messages Create Messages (4300–4399) ACTION: Use the User Interface or other means to correct the byte length attribute value for the element. See manual on how sub item length is computed based on the element type. 4355 0MESSAGE: Element name ! already used (SDERR 4355) CAUSE: Another element in the database already uses the specified name. ACTION: Enter a name that is unique among all the elements in the database.
SDDBC Error Messages Create Messages (4300–4399) 4363 0MESSAGE: Element ! has exceeded number of write class list (SDERR 4363) CAUSE: The specified element has more than 63 write classes. ACTION: Use the User Interface to delete some of the write classes from the specified element. 4364 0MESSAGE: Data set ! has exceeded number of read class list (SDERR 4364) CAUSE: The specified data set has more than 63 read classes.
SDDBC Error Messages Create Messages (4300–4399) 4371 0MESSAGE: Rel alias for element ! conflict. Primary name used (SDWARN 4371) CAUSE: The specified element has two relationship aliases which conflict. The element does not have an entity alias so its primary name was used. ACTION: No action is needed. 4372 0MESSAGE: Rel alias for element ! conflict. Primary alias used (SDWARN 4372) CAUSE: The specified element has two relationship aliases which conflict. The element's entity alias was used.
SDDBC Error Messages Miscellaneous Messages (4400–4449) Miscellaneous Messages (4400–4449) 4400 0MESSAGE: Catalog error ! encountered during catalog read (SDERR 4400) CAUSE: An error was encountered while retrieving information from the message catalog. ACTION: Contact the DA (remember to supply the catalog error number). Internal Error. 4401 0MESSAGE: Could not find message set ! in the catalog (SDERR 4401) CAUSE: The indicated message set could not be found in the message catalog.
SDDBC Error Messages Miscellaneous Messages (4400–4449) 4409 0MESSAGE: MPE command is too long (SDERR 4409) CAUSE: The entered MPE command is too long. ACTION: Limit the MPE command to 256 characters and reenter it. 4410 0MESSAGE: Invalid MPE command (SDERR 4410) CAUSE: The specified MPE command is not a legal MPE command. ACTION: Enter a legal MPE command. CAUSE: The specified MPE command is not allowed to be issued from within this program.
SDDBC Error Messages Miscellaneous Messages (4400–4449) 162 Appendix C
D SDDBC Command Abbreviations Abbreviations provide a short-hand for specifying commands in SDDBC. All command words in the system have an abbreviated form (some have the entire word as the abbreviation).
SDDBC Command Abbreviations Booleans Booleans BOOLEAN ABBREVIATION TRUE T FALSE F 164 Appendix D
SDDBC Command Abbreviations Commands Commands COMMAND ABBREVIATION COMMENT COM CREATE C DEFINE DEF EXIT E HELP H IMAGE IM REDO REDO RESET R SHOW SH Appendix D 165
SDDBC Command Abbreviations Name Conflicts Name Conflicts NAME CONFLICT ABBREVIATION PROMPT P TERMINATE T SUBSTITUTE S 166 Appendix D
SDDBC Command Abbreviations Keywords Keywords KEYWORD ABBREVIATION COMMENT COM CONFLICT CON CONTROL C DATABASE DB DICTIONARY DICT DOMAIN D NAME N NAME-MODE NM OPEN-MODE OM ORDER ORD OUTPUT OUT PASSWORD P SCHEMA SC SCOPE S STATUS STAT VERSION V Appendix D 167
SDDBC Command Abbreviations Names Names NAME ABBREVIATION PRIMARY P ALIAS A 168 Appendix D
SDDBC Command Abbreviations Name Modes Name Modes NAME MODE ABBREVIATION INTERNAL INT EXTERNAL EXT Appendix D 169
SDDBC Command Abbreviations Open Modes Open Modes OPEN MODE ABBREVIATION READ-ALLOW-READ RAR READ-ONLY RO SHARED-UPDATE SU EXCLUSIVE-UPDATE EU 170 Appendix D
SDDBC Command Abbreviations Output Destination Output Destination DESTINATION ABBREVIATION TERMINAL TERM PRINTER PRINT NULL NULL Appendix D 171
SDDBC Command Abbreviations Responses Responses RESPONSE ABBREVIATION YES Y NO N 172 Appendix D
SDDBC Command Abbreviations Version Status Version Status STATUS ABBREVIATION TEST T PRODUCTION P ARCHIVAL A Appendix D 173
SDDBC Command Abbreviations Version Status 174 Appendix D
E SDVPD Error Messages The following is a complete listing of SDVPD errors listed in order by error number. The list includes at least one possible cause of the error and a recommended action for each cause. The list is divided into the following groups: Message Number Error Type 3001–3101 SDVPD Warning Messages 3100–3458 SDVPD Error Messages Some System Dictionary error messages list a cause as “An unexpected subsystem error has occurred.
SDVPD Error Messages SDVPD Warning Messages (3001–P3101) SDVPD Warning Messages (3001–P3101) 3001 0MESSAGE: Forms file ! already defined in dictionary (SDWARN 3001) CAUSE: A FORMSFILE with the same name already exists in the dictionary. ACTION: None necessary. SDVPD will take action as specified by the OPTION parameter of the VPLUS command. 3002 MESSAGE: Form ! already exists (SDWARN 3002) CAUSE: A FORM with the same name already exists in the dictionary. ACTION: None necessary.
SDVPD Error Messages SDVPD Warning Messages (3001–P3101) 3020 MESSAGE: Logging disabled (SDWARN 3020) CAUSE: SDVPD will not log the user's command, because it could not open SDLOG. ACTION: None necessary. If command logging is essential for you, exit the program immediately, correct any problem, and reinvoke the program. 3021 MESSAGE: New log file ! is temporary. Save it for future use (SDWARN 3021) CAUSE: SDVPD is informing the user that the log file is temporary.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) SDVPD ERROR MESSAGES (3100–3458) 3100 MESSAGE: Unknown SDVPD command (SDERR 3100) CAUSE: The command issued is not a valid SDVPD command. ACTION: Check your command and see if it is one of the SDVPD commands. 3102 MESSAGE: Expecting 'Y' or 'N' answer (SDERR 3102) CAUSE: You entered something other than 'Y' or 'N' at a yes/no question. ACTION: Answer with 'Y' or 'N' at the question.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) misspelled. 3111 MESSAGE: Expecting dictionary name (SDERR 3111) CAUSE: The DICTIONARY parameter is specified with no actual dictionary name. ACTION: Issue the REDO command to insert the dictionary name. 3112 MESSAGE: Expecting scope name (SDERR 3112) CAUSE: The SCOPE parameter is specified with no actual scope name. ACTION: Issue the REDO command to insert the scope name.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) ACTION: Issue the REDO command to format the LOAD command as follows: LOAD [ ... ] 3126 MESSAGE: Illegal compatibility-level value (SDERR 3126) CAUSE: The COMPATIBILITY-LEVEL parameter of the VPLUS command is assigned an illegal value. ACTION: Issue the REDO command to replace the COMPATIBILITY-LEVEL parameter value to either VPLUS-COMPATIBILITY or COMPLETE.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) 3210 MESSAGE: Could not close the forms file (SDERR 3210) CAUSE: Vcloseformf intrinsic invocation failed. ACTION: Notify the Dictionary Administrator or the System Manager of this problem. 3211 MESSAGE: Could not open the forms file (SDERR 3211) CAUSE: Vopenformf intrinsic invocation failed. Some other user is accessing the file exclusively. ACTION: Check the file equate, if any, and see if the forms file actually exists.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) ACTION: Since SDOUT report information is collected and reported to $STDLIST, you do not have to take any action. However, if the report information needs to be saved away in a disc file, exit the program immediately, locate and remedy the problem, and then reinvoke the program. 3223 MESSAGE: Error while creating new SDOUT. Report defaulting to $STDLIST (SDERR 3223) CAUSE: Insufficient disc space. ACTION: Build a smaller SDOUT. CAUSE: Some other error.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) 3240 MESSAGE: Error occurred while replacing entity ! (SDERR 3240) CAUSE: An error has been detected while deleting an old entity definition and creating a new one. Make sure that you have the modify access to the definition. Check the System Dictionary intrinsic error message(s). ACTION: Take action according to the intrinsic error message(s).
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) 3248 MESSAGE: Duplicate external ELEMENT name ! found in internal name mode (SDERR 3248) CAUSE: When attempting to create the ELEMENT definition, a duplicate external name is found. However, because the current name mode is internal, the old definition cannot be retrieved. ACTION: The call to SDGetEnt will be skipped. SDDBD will act according to the value of the OPTION parameter.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) 3261 MESSAGE: REDO is not allowed in non-interactive mode (SDERR 3261) CAUSE: REDO is issued in a non-interactive program environment. Remember that REDO is not allowed in a non-interactive environment. ACTION: Do not issue REDO in a non-interactive environment. 3262 MESSAGE: Illegal use of REDO (SDERR 3262) CAUSE: The REDO command is issued to edit the command into another REDO. ACTION: Do not edit your command into “REDO” through REDO.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) command key word. ACTION: Check the subject name pointed by “^”, and see if it is misspelled. 3271 MESSAGE: Illegal parameter for the MPE command (SDERR 3271). Error code:! CAUSE: An MPE command is issued with an illegal argument. ACTION: Check the command argument, and see if it is incorrect. 3272 MESSAGE: No such MPE command (SDERR 3272). Error code: ! CAUSE: An unknown MPE command is issued.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) 3421 MESSAGE: Error while closing SDLOG. Program aborted (SDERR 3421) CAUSE: A disc error occurred while closing SDLOG. ACTION: Check the file system error message. Notify the Dictionary Administrator or the System Manager if a serious disc error is suspected. 3430 MESSAGE: Error while reading from SDOUT. Program aborted (SDERR 3430)E CAUSE: A disc error occurred while reading from temporary SDOUT to output the report onto the $STDLIST.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) 3454 MESSAGE: Error while opening temporary file SDREDO. Program aborted (SDERR 3454) CAUSE: A disc error occurred while opening SDVPD temporary file, SDREDO. ACTION: Check the file system error message, and notify the Dictionary Administrator or the System Manager if a serious error is suspected. 3455 MESSAGE: Error while reading from temporary file SDREDO.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) None MESSAGE: Message catalog (SDCAT.PUB.SYS) illegally formatted CAUSE: SDCAT.PUB.SYS is not in accordance with the NL message catalog format. ACTION: Notify the Dictionary Administrator of this problem. None MESSAGE: Message catalog (SDCAT.PUB.SYS) internal error CAUSE: SDCAT.PUB.SYS contains an internal error. ACTION: Notify the Dictionary Administrator and System Manager of this problem.
SDVPD Error Messages SDVPD ERROR MESSAGES (3100–3458) 190 Appendix E
F SDVPD Command Abbreviations SDVPD accepts abbreviations of the command key words. The table underneath lists each SDVPD key word and the corresponding abbreviation.
SDVPD Command Abbreviations Keyword Abbreviation X X 9 9 CHAR CH HYPEN HY CHECK-ELEM-TYPE CET ON ON OFF OFF OPTION OP PROMPT PR SKIP SK REPLACE RE TERMINATE T NEW N QUIET Q VERBOSE V LISTFORMS LF LOAD L HELP H SHOW SH RESET R REDO REDO COMMENT COM EXIT E 192 Appendix F
