Setting the DMDB variable to DMDB=< BaseDB >@<SID > should stop Dimensions prompting for a password. This has to be in a Dimensions server installation only and it doesn't work for Dimensions client installation. Also you can modify the dimensions.rc
For projects: it is advised to removing the directory item in each case using u141check fix_conflicts and - if desired - adding it back with a different path afterwards using AIWS with the /WS_FILENAME qualifier in the DMCLI client.
When the Dimensions System Administrator (DSA) creates a Dimensions base database , an operating-system account is assigned to act as the initial Dimensions Tool Manager for that base database . A Tool Manager is essentially a normal Dimensions user to whom special privileges have been extended so as to enable them to perform base database specific tasks with respect to other Dimensions users.
Then it is possible to execute the output file containing all the UIA commands with dmcli as follow : dmcli -user <user-id> -pass <pswd> -host <server> -dbname < db -id> -dsn <dsn-name> -file c:\output.txt
Which directories Unix checks depends on its configuration. Each Unix account can have its own configuration information and thus potentially its own unique list of directories in which to look for commands. Make sure the command's directory is listed in the environment's path.
In the readme file of the 12.2.2.2 patch, a new command called LAST is available and documented as follows in the readme file : The List Area Structure (LAST) Command
1. Create a deployment area based upon your Global Stage Lifecycle (GSL) and assign it to a project or stream. This can be done either directly in Admin Console or by DMCLI using the command of CA, similar to the following:
