To load the Enterprise Database Server schema
On the Schema menu, click Load.
The Load Schema to Repository dialog box appears.
Select Data Manager Type as DMSII from the drop-down list.
Enter the host name or host IP address and the port number in the respective fields.
If there are multiple network adapters / addresses, enter the host IP address instead of the host name to avoid name resolution issues. When a host name is used, Data Exchange acquires the first available IP address from Domain Name System (DNS) when the Administrative Service starts.
Enter the following fields:
Description File: Enter the description file in the following format:
(USER NAME)DATABASE NAME ON PACK NAME
Login User and Password: The following table displays the format in which the usercode and the associated accesscode or chargecode need to be entered in the Login User box along with their corresponding passwords in the Password box.
Login User | Password |
Usercode/Accesscode | Usercode password/Accesscode password |
Usercode/Accesscode/Chargecode | Usercode password /Accesscode password |
Usercode/Chargecode | Usercode password |
Notes:
The Login User can be the usercode under which the database is created. Alternatively, it can be a different usercode with privileges to access the database.
To control security and restrict access to the database while loading the Enterprise Database Server schema, the usercode might be associated with either an accesscode or a chargecode, or both.
Select "Remember Me" to save your credentials for automatic login the next time you load the schema.
(Optional) Click Verify Connection to ensure that a connection can be established with the database.
If the connection is successful, a success notification appears. If the connection fails, an error message appears.
Click OK.
After the schema is loaded successfully, a status message is shown in the DDW status bar. The time taken to load a schema depends on its size.
You can click Cancel to cancel the process.
Notes:
By loading schemas, Data Exchange loads the description file that was created by Data and Structure Definition Language (DASDL).
You must add the keyword DATAEXCHANGE in the Audit Trail Specification of the DASDL file or in the Database DEFAULTS or at the data set level. You can view this value on the Properties pane, under Miscellaneous. If the value is False for a data set, you can only run a BDT for that data set. If you add this setting for a schema that is already loaded, then you must do a DM Control Update on the MCP host, and then reload the schema.
Data Exchange does not support loading an Enterprise Database Server schema with kanji names.
When loading a schema, Data Exchange calls the command LogonCheck, if SecuritySupport is configured in MCP. LogonCheck captures logon attempts for all MCP usercodes. For more information on LogonCheck, refer to the *SYMBOL/SECURITYSUPPORT file.