Establishing Signon Processing › Defining Signon Requirements › CA Ideal Environment Functionality › CA Ideal User Definition

CA Ideal User Definition

The next step in the process is to determine the most efficient way to define your CA Ideal users. This step requires steps that are similar to the TP monitor signon.

When you define the user signon procedures, ask yourself the following:

• Do you care who the individual CA Ideal user is?
• Do you want to enable a group of users to share a single CICS user definition and also enable multiple CICS users to share?
• Do you want to enable a single CA Ideal user definition or for each of them to have their own definition, allowing individuals to set up a default user for a transaction or an environment that anyone can use?

For example, in a development environment, it is usually very important that each person be assigned his own TP monitor user definition and CA Ideal user definition. Because a programmer is updating entities in CA Ideal, you want to be able to identify the actual person who is signed on and what entities he last updated and compiled. Whereas, if a group definition or default user was set up, some of these items would no longer be distinguishable.

It is more likely that in a production environment, where it is not important to know the exact identity of a user who is signed on, that you share CICS and CA Ideal user definitions. An example might be a read-only application of non-confidential data. On the other hand, a production application that is allowing updating of more secured data is more likely to require that the exact identity of the user be known.