utlediupdt (Command to import management information)
When you use the utlediupdt command to register or change management information, you must specify an export file that stores management information. You can use a text file created with a text editor as the export file. The content of the export file will be used to register or change DataMagic management information.
Furthermore, you can collectively register or change multiple items of management information by writing them to an export file.
When optional products (Excel Option and DB Connection Option) are not installed to DataMagic, if you attempt to import management information from the optional products, not installed, the import operation completes successfully but an error with End Code 99 occurs during data processing.
Grade |
User type for DataMagic |
Business group settings for management information(#1) |
Access rights |
Executability |
---|---|---|---|---|
DataMagic Server |
Superuser |
- |
- |
Executable |
General user (#1) |
Omit specification of rights (#2) |
- |
Executable |
|
Specify rights |
View and refresh |
Executable |
||
Other than the above |
Not executable |
|||
DataMagic Desktop |
- |
- |
- |
Executable (#3) |
#1 |
: |
For the DataMagic Server grade, general users cannot register and update user information and business group information. |
#2 |
: |
Indicates that user rights are not specified for business groups but they will be used as filtering conditions. |
#3 |
: |
For the DataMagic Desktop grade, you cannot import user information as well as user information included in business group information. |
Commands
utlediupdt -f filename [-r|-m] [-k {E|S|8}]
Parameters
-f filename
Specify the name of the export file you want to register. (This parameter cannot be omitted.)
-r|-m
Specify whether to update IDs that have already been registered. (This parameter can be omitted.)
- -r
-
: Updates IDs that have already been registered.
- -m
-
: Does not update IDs that have already been registered.
If there is any ID that has already been registered, a warning message is displayed but this is not an error.
An error occurs if this parameter is omitted when one or more IDs are registered.
-k {E|S|8}
Encode for the export file (This parameter can be omitted.)
If you omit this parameter, the following value is applied to the processing.
- For Windows
-
:Shift JIS
-
Note that UTF-8 will be applied if the character code (system locale) in Windows is UTF-8.
- For UNIX
-
:Value of the Local host kanji code type (knjcode) in the system environment settings file (huledenv.conf)
(1) Export file format
The export file is written in the following format:
-
The export file is written in CSV format. Commas (,) are used as delimiters, and enclosure characters are not used.
-
The first field of each line is always a fixed character string.
-
An END line represents the end of an entry of management information.
-
Lines that begin with a hash mark (#) are comments.
-
Field content is case insensitive, but field names and comments are case sensitive.
-
Fields in square brackets can be omitted.
a) Data processing information format
For details about each field, see Data processing information.
PRMID,ID-character-string #ACCOUNT,name-of-updating-user …… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] ENCFNAME,__PRMID_FILE__ data-processing-schema [IDLIST,ID list] [COMMENT,comment] #STIME,date-and-time-of-last-update END
For the export file whose information will be registered, you can edit only PRMID, GRPID, and COMMENT. Do not edit ENCFNAME or IDLIST.
b) CSV information format
For details about each field, see CSV information.
CSVID,ID-character-string #ACCOUNT,name-of-updating-user …… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] TOKEN,enclosure-character,delimiter ………………… Use hexadecimal figures to enter enclosure characters and delimiters. [COMMENT,comment] #STIME,date-and-time-of-last-update ITEM,field-name [ITEM_COMMENT,field-comment]…If there are multiple ITEM lines, make sure that you specify this field immediately after each ITEM line. END
c) Format information format
For details about each field, see Format information.
FMTID,ID-character-string #ACCOUNT,name-of-updating-user ……… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] SIGN,zone-sign,output-external-sign-(positive),output-external-sign-(negative), output-internal-sign-(positive),output-internal-sign-(negative) ……… Use hexadecimal character strings to specify the zone, output external signs (positive and negative), and output internal signs (positive and negative). [SIGN_IN,input-external-sign-(positive),input-external-sign-(negative),input-internal-sign-(positive),input-internal-sign-(negative)] ……… Use hexadecimal character strings to specify the input external signs (positive and negative) and input internal signs (positive and negative). If you omit this tag, the settings for the output signs specified in the SIGN line are referenced. [COMMENT,comment] #STIME,date-and-time-of-last-update ITEM,field-name,validity,[parent-field],number-of-occurrences],number-of-bytes,[digits-after-decimal-point],field-type ……… Validity (0 = disabled, 1 = enabled) Specify the parent field by using the field name. (If you omit the parent field, no parent" is assumed.) [ITEM_COMMENT,field-comment] ……… If there are multiple ITEM lines, make sure that you specify this field immediately after each ITEM line. ITEMD,field-name,validity,[parent-field],[number-of-occurrences],delimiter-(input),delimiter-(output),field-type,addition-upon-output, addition-upon-input,[digits-after-decimal-point] ……… Validity (0 = disabled, 1 = enabled) Specify the parent field by using the field name. (If you omit the parent field, "no parent" is assumed.) Specify the parent field by using the field name. (If you omit the parent field, "no parent" is assumed.) Addition upon output/input (0 = do not add, 1 = add) [ITEM_COMMENT,field-comment] ……… If there are multiple ITEM lines, make sure that you specify this field immediately after each ITEM line. ITEMR,field-name,validity,[parent-field],[number-of-occurrences],reference-field,multiple,field-type,constant,[digits-after-decimal-point] ……… Validity (0 = disabled, 1 = enabled) Specify the parent field by using the field name. (If you omit the parent field, "no parent" is assumed.) [ITEM_COMMENT,field-comment] ……… If there are multiple ITEM lines, make sure that you specify this field immediately after each ITEM line. END
-
ITEM is used to specify the fixed length. You can specify multiple fixed lengths.
-
ITEMD is used to specify the variable length delimiters. You can specify multiple variable-length delimiters.
-
ITEMR is used to specify the variable field reference. You can specify multiple variable-field references.
d) Multi format information format
For details of each field, see Multi format information.
MFMTID,ID-character-string #ACCOUNT,name-of-updating-user ……… This is not output in the DataMagic Desktop grade. #Type,Settings type(0:Unified settings, 1:Separate settings) TYPE,Settings type ……… Settings type (0:Unified settings, 1:Separate settings) (If you omit this field, 0 is assumed.) [GRPID,business-group-name] KEY,key-start-position,key-length [key-category] ……… Displayed when unified settings is used. ……… Key category (0 = character, 1 = binary) (If you omit this field, 0 is assumed.) [DEFAULT,default-format-ID] [COMMENT,comment] #STIME,date-and-time-of-last-update #ITEM,key-value,format-ID ITEM,key-value,format-ID ……… Displayed when unified settings is used. ……… If the key category is binary, specify the key value by using hexadecimal digits. [ITEM_COMMENT,field-comment] ……… If there are multiple ITEM lines, make sure that you specify this field immediately after each ITEM line. #ITEMI,format-ID,conditional logic formula #ITEMIV,start position,key category(0:Character 1:Binary 2:Extension),scope of keys,key value ITEMI,format-ID,conditional logic formula ……… Displayed when separate settings is used. ……… If the key category is binary, specify the key value by using hexadecimal digits. [ITEM_COMMENT,comment] ……… If there are multiple lines of ITEMI and/or ITEMIV in the file, specify the command line immediately after the target ITEMI line. ITEMIV,start position,key category,scope of keys,key value ITEMIV,start position,key category,scope of keys,key value : [ITEMI,format-ID,conditional logic formula] [ITEM_COMMENT,comment] [ITEMIV,start position,key category,scope of keys,key value] END
-
KEY is used when the unified settings is selected.
-
ITEM is used when the unified settings is selected. ITEMI and ITEMIV are used when the separate settings is selected.
e) Hierarchy format information format
For details about each field, see Hierarchy format information.
HFMTID,ID-character-string #ACCOUNT,name-of-updating-user ……… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] [COMMENT,comment] #STIME,date-and-time-of-last-update RECORD,field-name,[parent-field],format-ID,occurrence-condition,key-start-position,key-value,no-hit-behavior ……… Specify the parent field by using the field name. (If you omit the parent field, "no parent" is assumed.) Occurrence condition (N = no conditions, A = key match, B = key match (binary)) No-hit behavior (E = error, D = use the default value, P = treat as normal and use previous value) [ITEM_COMMENT,field-comment] ……… If there are multiple ITEM lines, make sure that you specify this field immediately after each ITEM line. GROUP,field-name,[parent-field],maximum-number-of-occurrences,escape-condition,key-start-position,key-value ……… Specify the parent field by using the field name. (If you omit the parent field, "no parent" is assumed.) Specify the maximum number of occurrences by using either a numeric value or the name of a reference field. You can specify a numeric value from 1 to 999999999. 0 indicates infinity. To specify the reference field name, use the format &field-name&format-ID-field. Escape condition (N = no conditions, A = key match, B = key match (binary)) [ITEM_COMMENT,field-comment] ……… If there are multiple ITEM lines, make sure that you specify this field immediately after each ITEM line. END
The format ID specified in RECORD must either be described in the export file prior to this description or be registered in the format information ahead of time.
f) XML information format
For details about each field, see XML information.
XMLID,ID-character-string #ACCOUNT,name-of-updating-user …… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] SCHEMA,category ... Category (X = XML schema, D = DTD) FNAME,import-file-name ENCFNAME,__XMLID_IMPORT_FILE encoded-import-file [COMMENT,comment] #STIME,date-and-time-of-last-update END
-
The import file name is XMLID. edxml. If the target XML schema imports or includes one or more other files, the imported or included files are created in the current folder. These files are also required when the utlediupdt command is executed by using an export file from another host.
-
A method exists for writing the XML data format in cases where the schema or DTD is encoded in base64 and then imported into the export file, but this format cannot be created through editing. If you intend to edit data, use the XML data format above.
g) Excel information format
For details about each field, see Excel information.
EXCELID,ID-character-string #ACCOUNT,name-of-updating-user ……… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] MST_BOOK,management-Excel-file-name SHEETNAME,target-sheets IN_PARAM,target-sheets,handling-of-cells-with-errors,inital-row-number-for-table-read-operation, table-read-operation-end-condition,detailed-read-conditions ……… Target sheets (A: all sheets, S: specified sheets, I: ignore specified sheets) Handling of cells with errors (E: error, I: ignore) Initial row number for table read operation (a value from 1 to 1048576 or 0) (If you omit this field, 0 is assumed.) Table read operation end condition (1: end of data 2: empty record 3: empty row in a specified column 4: specified row 5: row containing an empty cell) Detailed read conditions (If the table read operation condition is 2, specify the end row number (initial row number to 1048576). If the table read operation condition is 4, specify the column number (A to XFD). If the condition to end table read operation is not 2 or 4, do not specify any value (enter only a comma)). OUT_PARAM,target-sheets,initial-row-number-of-table,wheter-to-use-template ……… Target sheets (S = single, M = multiple) Initial row number of table (Specify a value from 1 to 1048576.) Whether to use a template (Y = use, N = do not use) TEMPLATE_FILENAME,template-file-name TEMPLATE_SHEETNAME,template-sheet-name [COMMENT,comment] #STIME,date-and-time-of-last-update ITEM,field-type,cell-number,field-name ……… Field type (Z, M, or D) Cell number (a value from A to XFD for table specification, a value from A1 to XFD1048576 for cell specification) [ITEM_COMMENT,field-comment] END
h) Database table information format
For details about each field, see Database table information.
DBID,ID-character-string #ACCOUNT,name-of-updating-user ……… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] DBCID,database-connection-ID [COMMENT,comment] #STIME,date-and-time-of-last-update OUT_PARAM,update-method,table-name ……… Update method (I: insert, B: BULK INSERT (Oracle: INSERT by using direct path loading function, ODBC/BULK INSERT (only supported for Redshift or Snowflake), others not supported) M: update the rows that have the same key, and insert the rows that do not have the same key) OUT_SQL_POLICY,update-method ……… Update method (0: execute only OUT_SQL, 1: execute OUT_SQL and OUT_SQL2, 2: execute OUT_SQL2 if OUT_SQL1 failed) OUT_SQL_START SQL-statement-used-for-writing UT_SQL_END OUT_SQL2_START SQL-2-used-for-writing OUT_SQL2_END IN_PARAM,table-name,sort-order,field-name-to-use-for-sorting ……… Sort order (N = do not sort, D = ascending, R = descending) IN_SQL_START SQL-statement-used-for-import IN_SQL_END BEFORE_SQL_START SQL-executed-before-processing BEFORE_SQL_END SUCCESS_SQL_START SQL-executed-after-successful-processing SUCCESS_SQL_END ITEM,validity,field-name,fixed/variable-length,size,field-type,concatenation-sequence,Key,use-in-SQL-2 ……… Validity (1 = enabled, 0 = disabled) Fixed/variable length (F = fixed length, V = variable length) Size represents the field size for fixed-length fields, and the maximum size for variable-length fields. For variable-length fields, if you enter 0, the size is unlimited. Field type (B (binary), F (floating point), I (image, unconverted), M (variable-length characters), N (double-byte graphic characters), D (date), Z (numeric character string), W (unicode character string)) Key (0 = not a key, 1 = a key)Valid when M (merge) is specified for OUT_PARAM. Use in SQL 2 (0 = do not use, 1 = use)Valid when OUT_SQL2_START through OUT_SQL2_END are specified, and 1 or 2 is specified for OUT_SQL_POLICY. [ITEM_COMMENT,field-comment] ……… If there are multiple ITEM lines, make sure that you specify this field immediately after each ITEM line. END
-
The database connection ID specified in DBCID must either be described in the export file prior to this description or be registered in the database connection information ahead of time.
-
Specify one of the following: OUT_PARAM through OUT_PARAM_WHERE_END, OUT_SQL_POLICY through OUT_SQL2_END, IN_PARAM, or IN_SQL_START through IN_SQL_END.
-
You can omit the ITEM line only if you specify either IN_PARAM or IN_SQL_START through IN_SQL_END.If you omit the ITEM line, all fields are specified via database query.
i) Database connection information format
For details about each field, see Database connection information.
DBCID,database-connection-ID #ACCOUNT,name-of-updating-user ……… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] DBTYPE,product-type……… Product type (0 = SQLite3, 1 = Oracle, 2 = SQL Server#, 3 = DB2, 6 = PostgreSQL,7 = ODBC#,8 = Excel) [INIT_CODE,character-encoding] ……… Character encoding (ASCII, SJIS, EUC, UTF-8, UTF-16, UTF-16BE, UTF-16LE) (If you omit this field, "undefined" is assumed.) Specify the character encoding to be used in the time between connecting to the database and determining the encoding. [COMMENT,comment] #STIME,date-and-time-of-last-update [USER,user] [ATTESTATION,authentication-method]# ……… Authentication method (0 = SQL Server authentication, 1 = Windows authentication) (If you omit this field, SQL Server authentication is assumed.) [PASSWD,password] [PASSWD_ENC,encrypted-password] DATABASE,database-name,host-name,port-number DSN,DSN-name,host-name,port-number ……… DSN name (if the database is Oracle,TNS name) END
#: For Windows only.
-
We do not recommend using database connection information to access an Excel file. To access an Excel file, we recommend that you use Excel information.
-
Specify either PASSWD or PASSWD_ENC.
- PASSWD
-
: This tag is used to change the password. Specify the new password in plain text.
- PASSWD_ENC
-
: This tag is used to set the registered password as the password as it is. Enter the output of the utledigen command without changing it.
-
Specify either DATABASE or DSN.
To connect via ODBC, specify DSN.
j) Common components information format
For details about each field, see Common components information.
PONID,ID-character-string #ACCOUNT,name-of-updating-user ……… This is not output in the DataMagic Desktop grade. [GRPID,business-group-name] [NEEDINPUT,whether-to-perform-input-mapping] ………………… Whether to perform input mapping (0 = do not perform input mapping, 1 = perform input mapping) (If you omit this field, 0 is assumed.) [NARGS,number-of-arguments (0 to 5)] …… (If you omit this field, 0 is assumed.) [CAST,output-type] ………………………… I, M, 9, D, or 0x00 If you do not want to specify the output type, you can omit this field. [ARGTYPES,argument-type] ………………… Argument type (M or 9) Specify as many argument types as the number of arguments. For three arguments, there are the following eight patterns MMM, MM9, M9M, M99, 999, 99M, 9M9, 9MM [ARG1COMMENT,comment-for-argument-1] ……… Comment for common components argument 1 [ARG2COMMENT,comment-for-argument-2] ……… Comment for common components argument 2 [ARG3COMMENT,comment-for-argument-3] ……… Comment for common components argument 3 [ARG4COMMENT,comment-for-argument-4] ……… Comment for common components argument 4 [ARG5COMMENT,comment-for-argument-5] ……… Comment for common components argument 5 [COMMENT,comment] #STIME,date-and-time-of-last-update COMPONENT,component-type,returned-character-string ……… Component type (D = Date, T = Time, M = Fixed character string, 9 = Fixed numeric character string, F = Function, V = Virtual query, v = Virtual query (for initial processing), L = Lua script (only actual functions), L = Lua script (for initial processing)) [ITEM_COMMENT,comment-for-data-part] DEF_START : : : DEF_EN DEND
k) User information format
For details on each field, see DataMagic Operation Manual.
In the case of the DataMagic Desktop grade, user information cannot be used.
USERID,user-ID #ACCOUNT,name-of-updating-user DOMAIN,domain-name ………………… Specify this tag if you are using Windows. [DISPNAME,displayed-name] AUTHTYPE,authentication-method ………………… Authentication method (O = OS authentication, P = Product authentication) USERTYPE,user-type ………………… User type (A = Administrator, G = General user) PASSWD,plain-text-password PASSWD_ENC,encrypted-password #STIME,date-and-time-of-last-update [COMMENT,comment] END
-
If the authentication method is product authentication, specify either PASSWD or PASSWD_ENC.
- PASSWD
-
: This tag is used to change the password. Specify the new password in plain text.
- PASSWD_ENC
-
: This tag is used to set the registered password as the password as it is. Enter the output of the utledigen command without changing it.
-
For the DataMagic Server grade, if the user ID of the user who starts DataMagic is "root" (in UNIX) or "SYSTEM" (in Windows), user information about the user cannot be imported.
l) Business group information format
For details on each field, see DataMagic Operation Manual.
GRPID,business-group-name #ACCOUNT,name-of-updating-user [COMMENT,comment] [OMITAUTH,omit-to-specify-permissions (0 = do not omit, 1 = omit)] ((If you omit this field, "0" is applied.) …… In the DataMagic Desktop grade, "1" is set even if "0" is specified. #STIME,date-and-time-of-last-update [USER,user-ID,management-information-access-rights,execution-right] …… This cannot be used in the DataMagic Desktop grade. …… Management information access rights (N = no access, V = can view only, U = view and update) Execution right (N = cannot execute, X = can execute) END
(2) Sample code
FMTID,FMT0001 #ACCOUNT,admin #SIGN,zone-sign,output-external-sign-(positive),output-external-sign-(negative),output-internal-sign-(positive),output-internal-sign-(negative) SIGN,3,4,5,4,5 #SIGN_IN,input-external-sign-(positive),input-external-sign-(negative),input-internal-sign-(positive),input-internal-sign-(negative) SIGN_IN,4,5,4,5 COMMENT,HR data file Key "1111" format #STIME,2011/07/01 12:00:00.000000 #ITEM,field-name,validity,parent-field,number-of-occurrences,number-of-bytes,digits-after-decimal-point,field-type ITEM,KEY1LEN,1,,1,1,0,9 ITEM_COMMENT,001 ITEM,KEY2LEN,1,,1,1,0,9 ITEM_COMMENT,002 ITEM,KEY3LEN,1,,1,1,0,9 ITEM_COMMENT,003 ITEM,KEY1,1,,1,4,0,X ITEM_COMMENT,004 ITEM,KEY2,1,,1,4,0,X ITEM_COMMENT,005 ITEM,KEY3,1,,1,8,2,9 ITEM_COMMENT,006 ITEM,NOUSE,1,,1,8,0,N ITEM_COMMENT,007 END MFMTID,MFMT0001 #ACCOUNT,admin #TYPE,settings type(0:unified settings, 1:separate settings) TYPE,0 #KEY,key-start-position,key-length,key-category (0 = character, 1 = binary) KEY,1,4 #DEFAULT,default-format-ID DEFAULT,FMT0003 COMMENT,HR data file #STIME,2011/07/01 12:00:00.000000 #ITEM,key-value,format-ID ITEM,1111,FMT0001 ITEM_COMMENT,001 ITEM,2222,FMT0002 ITEM_COMMENT,002 END CSVID,CSV0001 #ACCOUNT,admin #TOKEN,enclosure-character,delimiter TOKEN,0x00,0x2 CCOMMENT,HR data file CSV output #STIME,2011/07/01 12:00:00.000000 #ITEM,field-name ITEM,AAA ITEM_COMMENT,001 END XMLID,XML0001 #ACCOUNT,admin #SCHEMA,category (X = XML schema, D = DTD) SCHEMA,X #FNAME,import-file-name FNAME,0006.edxml COMMENT,HR data file XML output #STIME,2011/07/01 12:00:00.000000 END HFMTID,HFMT0001 #ACCOUNT,admin COMMENT, #STIME,2011/07/01 12:00:00.000000 #RECORD,field-name,parent-field,format-ID,occurrence-condition-(NAB),key-start-position, key-value,no-hit-behavior-(EDP) #GROUP,field-name,parent-field,maximum-number-of-occurrences (1 though 999999999, 0 (infinity), or &Field name&Format ID field), escape-condition-(NAB),key-start-position,key-value RECORD,FILE_HEAD,,00038_02,N,0,,E ITEM_COMMENT,001 GROUP,GROUP1,,&FILE_HEAD&NEW1,N,0, ITEM_COMMENT,002 RECORD,RECORD1,GROUP1,00038_01,A,1,NAME,E ITEM_COMMENT,003 RECORD,RECORD2,GROUP1,00038_01,A,1,VALUE,E ITEM_COMMENT,004 GROUP,GROUP2,,3,N,0, ITEM_COMMENT,005 RECORD,RECORD3,GROUP2,00038_01,N,0,,E ITEM_COMMENT,006 END EXCELID,ExcelOut1 #ACCOUNT,admin GRPID,G_GROUP MST_BOOK,C:\template\template.xlsx SHEETNAME,Sheet1 IN_PARAM,A,E,1,1, OUT_PARAM,S,1,N TEMPLATE_FILENAME,C:\template\template.xls TEMPLATE_SHEETNAME,Sheet1 COMMENT,Excel-output-management-information #STIME,2016/07/01 12:00:00.000000 ITEM,D,A1,order-date ITEM,Z,B,order-detail-line-number ITEM_COMMENT,comment END DBCID,DBC0001 #ACCOUNT,admin #DBTYPE,product-type (0 = SQLite3, 1 = Oracle, 2 = SQL Server, 3 = DB2, 6 = PostgreSQL, 7 = ODBC 8 = Excel) DBTYPE,1 COMMENT, #INIT_CODE,character-encoding (ASCII, SJIS, EUC, UTF-8, UTF-16, UTF-16BE, UTF-16LE) INIT_CODE,ASCII #STIME,2011/07/01 12:00:00.000000 USER,user001 PASSWD,xxxxxxxx #DATABASE,database-name,host-name,port-number DATABASE,ORACLE9I,ORACLE9I,1521 END DBID,DB #ACCOUNT,admin DBCID,DBC0001 COMMENT, #STIME,2011/07/01 12:00:00.000000 #IN_SQL,SQL-statement-used-for-input #IN_PARAM,table-name,sort-order (N = do not sort, D = ascending, R = descending),field-name-used-for-sorting IN_SQL_START select * from table IN_SQL_END #ITEM,validity (1 = enabled, 0 = disabled),field-name,(V = variable length,F = fixed length),size,field-type,concatenation-sequence,used-only-in-WHERE-clause,used-in-SQL-2 ITEM,1,no,F,9999,B,1,0,0 ITEM_COMMENT,001 ITEM,1,db_rowversion,F,9999,I,1,0,0 ITEM_COMMENT,002 ITEM,1,db_sysname,F,9999,M,1,0,0 ITEM_COMMENT,003 END
This sample code is written based on the following conditions. Executing the registration command by using this sample code in an environment where the conditions are not met might result in an error.
-
XML schema file 0006.edxml, which is generated from the export file, exists in the folder from which the registration command is executed.
-
The format ID referenced in the sample code has been registered ahead of time.
PRMID,EDID #ACCOUNT,admin GRPID,GRP0001 ENCFNAME,__PRMID_FILE ... IDLIST,C:CSV001;X:XML001; COMMENT, #STIME,2011/07/01 12:00:00.000000 END PONID,SAISON_TOUPPER #ACCOUNT,admin GRPID,GRP0001 #NEEDINPUT, require map input (0: Not required 1: Required) NEEDINPUT,1 #NARGS, number of arguments (0 to 5) NARGS,0 #CAST, output type (I, M, 9, D, or omitted) CAST,M COMMENT,Converts lowercase characters of the input character string to uppercase. #STIME,2016/04/22 12:20:52 #COMPONENT, category (D: Date, T: Time, M: Fixed string, 9: Fixed numeric string, F: Function, V: Virtual query, v: Virtual query (for initial processing), L: Lua script, l: Lua script (for initial processing)), Return string (0 to 5) COMPONENT,V,0 ITEM_COMMENT,Converts lowercase characters of the input character string to uppercase. #DEF_START component definition DEF_END DEF_START SELECT UPPER($ARG0); DEF_END END USERID,USER0001 #ACCOUNT,admin DOMAIN,d-domain.com #AUTHTYPE,authentication-method (O = OS authentication, P = product authentication) AUTHTYPE,O #USERTYPE,user-type (A = administrator, G = general user) USERTYPE,A PASSWD,xxxxxxxx #STIME,2011/07/01 12:00:00.000000 END GRPID,GRP0001 #ACCOUNT,admin OMITAUTH,0 COMMENT, #STIME,2011/07/01 12:00:00.000000 #USER,user-ID,management-information-access-rights,execution-right USER,user001,U,X END