Creating CA-Ideal Users In Batch


Article ID: 28323


Updated On:


CA Datacom CA Datacom - AD CA Ideal CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware



I need a way to add multiple CA Ideal users in batch.  What is the best practice to do this?


Created a new CA Ideal system. Now I need to add the users.  What is the best practice to add multiple users in batch?




The usual method to create CA-Ideal users is to use the CA-Ideal CREATE USER command. However, adding large numbers of users this way can be a time-consuming process. This article describes a method for solving that problem by creating CA-Ideal users with batch Datadictionary (DDUPDATE).

A valid CA-Ideal user definition consists of the following Datadictionary entity-occurrences:

    • A PERSON entity-occurrence.

    • An ALIAS for the PERSON entity-occurrence, which must match the PERSON userid attribute.

    • One or more RELATIONSHIP occurrences between the PERSON and the four CA-Ideal AUTHORIZATION profiles and (optionally) one of the DD AUTHORIZATION profiles:
      $$ID-ADM IDEAL Administrator
      $$ID-DVW DVW Administrator
      $$PR-ADM PRINT Administrator
      $$ID-USE IDEAL User


  • One or more RELATIONSHIP occurrences between the PERSON and the defined CA-Ideal SYSTEM entity-occurrence(s). The intersection data (INTER-DATA) of this relationship occurrence must contain the following information:

    Pos Contents
    1-3 $ID (constant)
    4 One byte of bit settings for the authorization
    level in the related system, as follows:
    1... .... - Control
    .1.. .... - Update
    ..1. .... - Read
    ...1 .... - Run-Prod
    .... 1... - Not Used
    .... .1.. - Not Used
    .... ..1. - Update-Report
    .... ...1 - Update-Panel

Following is a sample set of DDUPDATE transactions to add a new user to CA-Ideal:

  1. -ADD PERSON,long-user-name
  2. 1003 RELT,SYSTEM,system-name(ver),PER-SYS-ACCESS
  3. 1003 DATA,$IDx
  4. 1010 ADD $$ID-ADM
  5. 1010 ADD $$ID-DVW
  6. 1010 ADD $$PR-ADM
  7. 1010 ADD $$ID-USE
  8. 1014 pppppppppppp uuu
  9. -END
  10. -UPD PERSON,long-user-name(001),PROD
  11. -END


    1. The -ADD transaction is a header transaction. It adds the PERSON entity-occurrence for user 'long-user-name' (from 1 to 15 characters).
    2. The 1003 RELT, SYSTEM transaction relates the user 'long-user-name' to the system 'system-name(ver)'. The new user can be related to a maximum of 99 SYSTEMs.
    3. There must be a matching 1003,DATA transaction for each 1003 RELT, SYSTEM transaction. The 1003 DATA transaction gives the user authorization within the system specified in the corresponding 1003 RELT, SYSTEM transaction. The authorization bit setting ('x') is determined using the following table:
      /--- AUTH IN SYS: TYPE:             HEX   CHAR|                 ---------------   ---   ----|                 CTL + RUN-PROD     F3     3 |                 CTL                E3     T |                 UPD + RUN-PROD     7B     # |                 UPD                6C     % |                 READ + RUN-PROD    30       |                 READ               20       |                 RUN-PROD           10       |                                             ------------------------------------------
    4. The 1010 ADD transaction assigns the user a privilege title: {IDEAL-ADMIN, DATAVIEW-ADMIN, PRINT-ADMIN, IDEAL-USER}.

      For example, to define an IDEAL-USER, only supply the following transaction:

      1010 ADD $$ID-USE

  1. The 1014 transaction defines a password and the userid for the 'long-user-name'. If a password is not desired, the 1014 transaction must still be included to add the userid. Note that the userid MUST start in column 19.
  2. The -END transaction marks the conclusion of each transaction group.
  3. The -UPD transaction marks the 'long-user-name' definition to PROD status.
  4. The -END transaction marks the conclusion of each transaction group.

When these transactions have been successfully executed, the new CA-Ideal user is ready to sign on.

Additional Information:

For information on creating CA uses via batch, please see the CA Ideal Administration Guide

For additional information on using batch transactions to maintain CA-Ideal user definitions, refer to the CA Ideal Administration Guide



Release: ESBIDL99000-14-Extended Support Basic-for CA Ideal