K Option - IBM Cognos User Manual

The -j form of this option publishes only new PowerCubes and keeps the
previously published cubes unchanged. A data source connection for the
PowerCube is published if a connection with the same name does not already
exist. If the data source connection is successfully published, the associated
package is also created if a package with the same name does not already exist.
The -ju form of this option updates previously published PowerCubes and cube
groups in addition to publishing PowerCubes that were not previously published.
The following example shows how to publish a cube or a cube group named
National. The cube is built and the categories are generated.
cogtr -j National -n2 National.mdl
The following example shows how to publish one cube named MA in the cube
group named National. The cube is not generated.
cogtr -j National/MA -ox -n2 National.mdl
The following example shows how to update the data sources or packages
associated with the MA and CA cubes in the cube group named National.
cogtr -ju National/MA -ju National/CA -n2 National.mdl

-k option

This option supplies the signon information needed to establish one or more
database connections during batch processing.
It provides an alternative to storing the information in the Signons list or
retrieving user IDs and passwords from the configured authentication source. This
is especially useful when used with .mdl files which, by default, do not use verb
MDL and so do not store signon passwords.
For databases referenced in an Impromptu Query Definition (IQD) file, the signon
is the logical database name that appears in the related gateway.ini file. Multiple
IQD data sources can use the same signon object.
Note: You can view these signons in the Cognos Transformer user interface, but
you cannot change them.
The syntax for using the -k option is as follows:
cogtr -ksignon=
userid/password -p
filename.py?|-mfilename.mdl
No spaces may appear between -k and its argument, and the signon name cannot
be empty. Also, the signon name cannot contain the ASCII equals (=) character, and
the user ID cannot contain a forward slash (/), because both characters are
reserved for the parameter syntax.
The following Windows example opens the Field3.mdl file and grants access to the
required database using the signon named field, user ID CarlosR, and password
pw462. Assuming that the signon matches that defined in the model, the process
runs in batch mode, creating the cubes as defined in the model.
cogtr -n -kfield=CarlosR/pw462 Field3.mdl
The following UNIX example reads the data source for model Xyzsales.mdl from
an Oracle database using an IQD file, confirms the security information, and
227
Appendix A. Command Line Options