Functionality
This command can perform upload and download in Environment Setup > Users and Sections of main menu.
Record format
dtpmast.exe | /s|/d|/g /m Type /f File Name [/e Error File Name] |
Option
Specify upload (register, update), upload (delete) or download of Master data.
/s: upload (register/update)
/d: upload (delete)
/g: download
Specify the type of Master data.
e: user management information
g: section management information
b: building management information
Specify the name of the file to be uploaded during uploading (/s, /d), and specify the name of the file to be output during downloading (/g).
Specify the output file with absolute path, and when the path contains space, enclose the whole path in quotes. In addition, apart from the quotes, the maximum string of 128 fullwidth characters or 256 halfwidth characters can be specified.
An error file is created when an upload (/s, /d) is specified, and of the master data described in the file specified using /f, only the master data that failed to upload is output to the file.
Moreover, an error details file (file with the extension ".dtl" appended to the error file name) is output together with the error file. The error details file contains the error causes of the master data output to the error file.
Refer to "Execution result/output format" for details on the file format of the error details file.
This option cannot be omitted when specifying uploads (/s, /d). When specifying downloads (/g), this option is not required, and will be ignored even if specified.
Specify the error file with absolute path and when the path contains space, enclose the whole path in quotes. In addition, apart from quotes, the maximum string of 128 fullwidth characters or 256 halfwidth characters can be specified.
You cannot specify ".dtl" as the extension of the error file name.
Return value
0: ended normally
Other than 0: ended abnormally
Command saving location
The following folder in CS:
CS Installation Directory \bnserv\bin |
Authority required for execution/executing environment
This command must be executed by the user who ran the Operating Environment Maintenance Guide.
This command must be executed on CS.
Cautions
If the output file has existed, overwrite it or delete it when an exception occurs. When the file created previously is required, modify the file name or move this file to another location before executing this command.
The output order of error files when uploading the section management information may be different from the input order of the Master data file.
Command execution example
When downloading user management information to C:\mast\emp.csv
"C:\Program Files\Fujitsu\Systemwalker Desktop Patrol\bnserv\bin\dtpmast.exe" /g /me /fC:\mast\emp.csv |
Execution result/output format
The format of error file is in the same format of Master data file. By referring to the error details file (error file's extension is ".dtl"), and managing and modifying the corresponding position of the error file, for the Master data that failed to be registered, updated or deleted, the error file can be used for file uploading next time.
The example of error details file is shown as follows:
Comment line Comment line 3, User Name, Invalid Data 4, E-mail Address, Length of item is wrong |
File format
No. | Item | Description |
|---|---|---|
1 | Line Number | Line number of error file |
2 | Item | Item name of exceptional causes |
3 | Contents | Exceptional contents |
Error contents
Exceptional Contents | Cause | Resolution |
|---|---|---|
Integrity of double quotation marks | Double quotes are not used correctly to enclose the items. | Enclose each item with double quotes correctly. |
Invalid Data |
|
|
Length of item is wrong | The item length is not correct. Or though it is required item, the item record is still blank. | Confirm the item length and items, and modify it as correct ones. |
Range Error | The section level is over 100. | Including management targets, modify section level to be less than 100. |
No Key Data | The user ID, section code or building code are not specified. | Confirm whether the item is correct and record the required items. |
No Corresponding Data | The item of update object and deletion object do not exist. | Confirm whether the items as deletion objects are correct. If it is no longer required, delete the corresponding line in the error file. |
Excluded from the target | Specify the section code of an object that is registered or updated in the upstream section. | Confirm the upstream section code and modify it as the correct one. |
Section level loop error | The section level is specified as a circle. | Confirm the upstream section code and modify it as the correct one. |
Computer exists | The PC Inventory has existed on PC of user management to be deleted, so it cannot be deleted. | Confirm the users to be deleted and then modify them as correct users. Normally, delete Inventory of PC as required. |
Current License Management exists | The License has existed on PC of user management to be deleted, so it cannot be deleted. | Confirm the users to be deleted and then modify them as correct users. Normally, delete Inventory of PC when it is required to delete License first. |
All content excluding the bottom level | Attempted to delete the section outside of the bottom. | The subordinate sections of the deletion object should also be added to the deletion target list. |
Cannot be deleted | Attempted to delete the system account or section management account user, or there is no authority for deleting the object section. | Unable to delete the system account or section management account user. Check if the user targeted for deletion is correct, and if so, delete the role allocations. In addition, confirm whether the section of deletion object is correct. If it is no longer required, delete the corresponding line in the error file. |
Database Error | An exception may occur in the database. | Confirm whether an exception occurred in the database, and exclude the causes of exception. |
Cannot be update | Attempted to update or delete a user ID that is logging on. | Try again after the user logs off or wait a while. |
When the processing failed, a message indicating failure will be output. Refer to "3.3.1 Messages Output in Master Data Construction Command" for details.
