Differences

This shows you the differences between two versions of the page.

--- novo_motion_schema_editor [2021/02/03 21:35]
dlm
+++ novo_motion_schema_editor [2021/06/08 14:16] (current)
mah update @variables
@@ Line 1: / Line 1: @@
+[[main_page|NovoMotion Outbound Menu]]
 ====== NovoMotion Schema Editor ======
 The NovoMotion Schema Editor is used to create or maintain the definition of the elements of a schema generator used with the the SQL environment.  Once the user has logged in through the [[novo_motion_u2_login|NovoMotion U2 Login]], the user will access the Schema Editor through the U2 Options view.
+\\
 ==== NovoMotion Schema Editor - U2 Options Tab - SA Map Example ====
@@ Line 14: / Line 12: @@
-{{:novoschema1.jpg?400|}}
+{{:file:novoschema1.jpg|}}
@@ Line 58: / Line 55: @@
-  * U2 dictionary is the name of the base dictionary item (for the selected file) within the U2 environment. (I descriptors are also supported. I-descriptors that use the SUBR keyword or that execute a TRANS to translate to another file should be used with caution.  Warnings are sent to the user if they chooses an I-descriptor that uses one of these types.) Note that there are also a number of keywords associated with this column.
+  * U2 dictionary is the name of the base dictionary item (for the selected file) within the U2 environment. (I-descriptors are also supported. I-descriptors that use the SUBR keyword or that execute a TRANS to translate to another file should be used with caution. Warnings are sent to users if they choose an I-descriptor that uses one of these types.) Note that there are also a number of keywords associated with this column:
+^ **Key Word**^ **Description** |
+|@MULTIVALUEID |Current suggestion is to use multiple primary keys instead of this. However, it is used to explode the controlling attribute of a multi-valued set @MULTIVALUEID:part1:part2  |
+|@ORDINAL |Assigns a numeric sequence to the value - @ORDINAL:mvinfo. See Ordinal considerations below. |
+|@ACTION | Used to specify a delete or insert event  |
+|@LITERAL | Used to pass static data through the schema - @LITERAL:1 |
+|@FIELD | Field based on info  - @FIELD:info:delimiter:occurrence:numberOfOccurrences|
+|@FIELDS | Field for multi-value array.  Same as @FIELD |
+|@TM | Allows selection of a specific table master - @TM:tablenbr |
+|@CHANGE | Used to change a specific string from one literal to another - @CHANGE:info:from:to |
+|@CONVERT | Used to change multiple characters from one character to another -  @CONVERT:info:from:to |
+|@ICONV | Used to convert a string to internal format  - @ICONV:mvinfo:conversion|
+|@OCONV | Used to convert a string to external format  - @OCONV:mvinfo:conversion|
+|@FMT | Used to format a string  - @FMT:mvinfo:statment|
+|@NOT | The reverse of a string evaluation - @NOT:mvinfo |
+|@TRIM | Removes errant spaces from a string  - @TRIM:mvinfo |
+|@NULL | Returns a null character - @NULL |
+|@BLOAT | TBD |
+|@USER | Sends the U2 user ID who caused the record change event, or load event |
+|@SWAP | Used to change string from one string to another -  @SWAP:info:from:to |
+|@CAT | Use U2 CATS to combine two arrays of data together - @CAT:info1:info2 |
+|@TIMESTAMP | transmit a record timestamp for when change / load event happened in U2. This is both date and time in SQL. |
-  * @MULTIVALUEID - Current suggestion is to use multiple primary keys instead of this. However, it is used to explode the controlling attribute of a multi-valued set @MULTIVALUEID:part1:part2
-  * @ORDINAL - Assigns a numeric sequence to the value - @ORDINAL:mvinfo. See Ordinal considerations below.
-  * @ACTION - Used to specify a delete or insert event
-  * @LITERAL - Used to pass static data through the schema - @LITERAL:1
-  * @FIELD - Field based on info  - @FIELD:info:delimiter:occurrence:numberOfOccurrences
-  * @TM - Allows selection of a specific table master - @TM:tablenbr
-  * @CHANGE - Used to change a specific string from one literal to another - @CHANGE:info:from:to
-  * @CONVERT - Used to change multiple characters from one character to another -  @CONVERT:info:from:to
-  * @ICONV - Used to convert a string to internal format  - @ICONV:mvinfo:conversion
-  * @OCONV - Used to convert a string to external format  - @OCONV:mvinfo:conversion
-  * @FMT - Used to format a string  - @FMT:mvinfo:statment
-  * @NOT - The reverse of a string evaluation - @NOT:mvinfo
-  * @TRIM - Removes errant spaces from a string  - @TRIM:mvinfo
-  * @NULL - Returns a null character - @NULL
+  * In SWAP CONVERT etc above, @AM @VM @SVM can be specified as IN or OUT strings.
   * Ordinal considerations: The precision and scale assigned to the ordinal are taken from the mvinfo dictionary. Because an ordinal is a number, the precision and scale should be changed to numeric with a scale of 3 or 4.
@@ Line 118: / Line 97: @@
-{{file_novo_schema2.jpg}}
+{{:file:novo_schema2.jpg|}}
@@ Line 133: / Line 112: @@
-==== NovoMotion Schema Editor - SQL Options tab - SA map example ====
+==== NovoMotion Schema Editor - SQL Options tab - SA Map Example ====
+{{:file:novoschema3.jpg|}}
-{{file_novo_schema3.jpg}}
@@ Line 159: / Line 137: @@
-==== NovoMotion Schema Editor - Post Job Options tab - SA Map example ====
+==== NovoMotion Schema Editor - Post Job Options Tab - SA Map Example ====
-{{file_novo_schema4.jpg}}
+{{:novoschema4.jpg|}}
@@ Line 183: / Line 161: @@
-The function contains the following drop down menus:
+==== NovoMotion Schema Editor - Drop Down Menus ====
-  * **File**
+=== File ===
@@ Line 206: / Line 186: @@
-  * **Edit**
+=== Edit ===
@@ Line 216: / Line 197: @@
-  * **Tools**
+=== Tools ===
@@ Line 229: / Line 210: @@
-**Note:**  The Generate SQL Script is used when one wants to generate script to create the SQL table (See the Creating a SQL script information) to avoid the necessity of creating the SQL table by hand.  This is often used multiple times during the development of new schema to perfect the information between U2 and SQL.
+Note:  The Generate SQL Script is used when one wants to generate script to create the SQL table (see [[creating_a_sql_script|Creating a SQL Script]]) to avoid the necessity of creating the SQL table by hand.  This is often used multiple times during the development of new schema to perfect the information between U2 and SQL.
-The SQL script can be pasted into SQL Management Studio and executed. It will drop any existing SQL table of the name defined in the schema and re-create it with the columns defined in the schema. It does this for both the base SQL table and - if an @ACTION row exists - for the parallel SQL trigger table.  See the [[sql_server_management_studio_example]] if you would like to review notes about the SQL Server tasks.
+The SQL script can be pasted into SQL Management Studio and executed. It will drop any existing SQL table of the name defined in the schema and re-create it with the columns defined in the schema. It does this for both the base SQL table and - if an @ACTION row exists - for the parallel SQL trigger table.  See the [[sql_server_management_studio_example|SQL Server Management Studio Example]] if you would like to review notes about the SQL Server tasks.
+If a SQL table has already been established and the schema needs to change, the user has the following options:
+  - Generate the SQL script through the Schema Editor, copy it, paste it into SQL Management Studio, and execute the script.  This will drop the existing table  and replace the existing SQL column definitions.  Then use [[load_bci.action|LOAD.BCI.ACTION]]  to reload the data into the SQL table.
+  - Change, add, or delete the desired information in the schema via the Schema Editor, then make the same changes to the SQL table via SQL tools.  Next use [[load_bci.action|LOAD.BCI.ACTION]]  to reload the data into the SQL table.  This can be used when the SQL table has data that cannot be regenerated from the U2 server because the data has already been purged from that server or because the table is large and the data being added is new.
-**Additional Usage Notes:**  If a SQL table has already been established and the schema needs to change, the user has the following options:
-  - Generate the SQL script through the Schema Editor, copy it, paste it into SQL Management Studio, and execute the script.  This will drop the existing table  and replace the existing SQL column definitions.  Then use [[load_bci.action]]  to reload the data into the SQL table.
-  - Change, add, or delete the desired information in the schema via the Schema Editor, then make the same changes to the SQL table via SQL tools.  Next use [[load_bci.action]] to reload the data into the SQL table.  This can be used when the SQL table has data that cannot be regenerated from the U2 server because the data has already been purged from that server or because the table is large and the data being added is new.
+=== Help ===
-  * **Help**
@@ Line 247: / Line 227: @@
+\\
+[[main_page|NovoMotion Outbound  Menu]]

NovoRoi Systems DokuWiki

User Tools

Site Tools

Differences

Page Tools