[nsadm62a:~] setup_new_env ERROR: Arguments required: Usage: setup_new_env [-[blncfst]] env-name db-type [db-server db-name] [build-descriptor] Usage: setup_new_env -v[bln] env-name host-env build-descriptor where: -v = Visitor environment -t = Test driver environment [-v & -t require build-descriptors] -n = No client info display -f = Foreign (non-LeasePak) database -c = Closed to visitor -l = Links used to populate exe dir -b = Build-id used for live -s = No end-user code objects A build descriptor is 'live', 'host', or a build name ('bld#.##.####', e.g., 'bld5.01.1126') PARAMETERS: [-flags] - various combinations of '-' + [dblncfst] or of '-v' + [dbln] where d=use dev startup files no d=use runtime startup files b=tie environment to the current build-id of the associated build (live or dlvy) no b=environment configured with $live or $dlvy if determined by other factors l=create environment with an exe ($uexe) directory and populate it with links to the executables in the associated build no l=create $uexe as a symlink to the exe directory of the associated build n=do not display info needed to configure a PC client for this environment no n=info is displayed c=environment is closed to visiting environments; environements with the -v flag are not allowed to reference the subject environment no c=environment can be visited by -v visitor environments f=database associated with the environment is not a LeaesPak database no f=database associated with the environment is a LeaesPak database s=environment is created such that it cannot load user code objects; ucql points to usql and uprg points to ulib no s=environment is created to allow use of user code objects; ucql and uprg point to the user-provided $CSTDIR for the associated build t=environment is created as a test environment no t=environment is created as a production (no -v) or visitor (-v) environment v=environment is created as a visitor environment no v=environment is created as a production (no -t) or test (-t) environment depending on the presence or absence of "-v" in the flags, one of two usages are required: Without -v: environment-name - name of new environment. Must be a valid UNIX directory name and must contain no capital letters or periods (".") or hyphens ("-"), and must not currently be a subdirectory of $TOPDIR/env. Various other restrictions on the name apply. database-type - the 3-character abbreviation for the DBMS under which the environment's database is to be created: "dbt" = DB2, "ora" = Oracle and "syb" = Sybase. Can be "none" if not database will be created. Should be used even if database is a non-LeasePak database ("-f" flag). database-server - the name by which processes desiring to be clients of the environment's database can locate the running instance of the DBMS that serves that database. These are the database alias in DB2, the net service name in Oracle, and the dataserver in Sybase. They may refer to instances running on other machines on the network, provided they are configured properly in a local instance of the DBMS for remote access. database-name - the name of the Logical LeasePak Database (LLDB): a schema in DB2 or Oracle, or a database in Sybase. If Strict Naming is in force, then the name must begin with "lpr". Various other restrictions apply. This does not cause the database to be created, it merely indicates what the database will be named when it is created. The database may already exist in a different release; using such a database name means that connecting to this environment will connect to that database even in a different LeasePak release. build-descriptor - in a test database only: the build to which the environment's shared directories are to be pointing. The descriptor is a build name, such as bld#.##.####, or a "link point", where a build is fulfilling a particular role in the release as the "live" build (this is the only link point available in run-time releases) or as the "dlvy" build (this link point is only available in development releases). The build name is a subdirectory of $bld ($TOPDIR/bld); live and dlvy will always point to a build in the build directory with a build name of the pattern bld#.##.####. The shared directories in an environment are: bin, conv, cql, dsets, exe, lib, prg and sql. The non-shared directories are data, eop, err, and etc. With -v: environment-name - as without the -v flag host-environment - the name of an existing environment (directory under $TOPDIR/env) whose database the environment wishes to access as a guest. build-descriptor - as without the -v flag; "host" is a link point available to visitor environments; it refers to the build to which the host environment is pointing.