USER (DDDL Compiler)
USER statements document users in the dictionary by relating users to systems and to other users, assigning users the authority to access secured products and entity types and to perform secured operations, and supporting attribute/entity relationships and documentation entries.
idmscu19
USER statements document users in the dictionary by relating users to systems and to other users, assigning users the authority to access secured products and entity types and to perform secured operations, and supporting attribute/entity relationships and documentation entries.
The system generation compiler can be used in conjunction with the DDDL compiler to complete user definitions. For additional information, refer to
CA IDMS Administrating section
. If the SET OPTIONS statement specifies SECURITY FOR IDD IS ON, the user must be assigned the proper authority to issue USER statements.
Syntax
USER statement
►►─┬─ ADD ─────┬─ USEr name isuser-id───────────────────────────────────────► ├─ MODify ──┤ ├─ REPlace ─┤ └─ DELete ──┘ ►─┬─────────────────────────────────────────────────────────┬────────────────► └─┬─ PREpared ─┬─ byuser-id──┬────────────────────────┬─┘ └─ REVised ──┘ └─ PASsword ispassword─┘ ►─┬────────────────────────────────────────┬─────────────────────────────────► └─ MAPtype ─┬─ is ─┬─┬─map-type-name─┬─┘ └─ = ──┘ └─ NULl ──────────┘ ►─┬────────────────────────────────┬─────────────────────────────────────────► └─ FULl name isfull-user-name──┘ ┌────────────────────────────────────────────────────────────────────────── ►─▼─┬────────────────────────────────────────────────────────────────────────►─ └─┬─ INClude ◄ ──┬─ OF ─┬─ SYStem ────┬─system-name──────────────────── └─ EXClude ────┘ └─ SUBSYstem ─┘ ───────────────────────────────────────────────────────────────────┐ ─►────────────────────────────────────────────────────────────────┬──┴────────► ─┬───────────────────────────────────┬─┬──────────────────────┬─┘ └─ Version is ─┬─version-number─┬─┘ └─ TEXt isuser-text──┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘ ┌─────────────────────────────┐ ►─▼─┬─────────────────────────┬─┴────────────────────────────────────────────► └─ SAMe AS USEruser-id──┘ ┌──────────────────────────────────────────────────────────┐ ►─▼─┬──────────────────────────────────────────────────────┬─┴───────────────► └─ COPy ─┬─ ALL COMment TYPes ──┬─ FROm useruser-id──┘ ├─ COMments ───────────┤ ├─ DEFinition ─────────┤ ├─ ATTributes ─────────┤ ├─ USERS ──────────────┤ ├─┬─ SYStems ────┬─────┤ │ └─ SUBSYstems ─┘ │ ├─ WIThin USEr ────────┤ ├─comment-key────────┤ └─relational-key─────┘ ►─┬────────────────────────────┬─────────────────────────────────────────────► └─ NEW NAMe isnew-user-id──┘ ►─┬─────────────────────────────────────────┬────────────────────────────────► └─ user DEScription isdescription-text──┘ ►─┬──────────────────────────────┬───────────────────────────────────────────► └─ PASsword is ─┬─┬─ NULl ─┬─┬─┘ │ └─ '' ───┘ │ └─password─┘ ┌────────────────────────────────────────────────────────────────────────── ►─▼─┬────────────────────────────────────────────────────────────────────────►─ └─┬─ INClude ◄ ─┬─ AUThority ──┬──────────────────────┬────────────────── └─ EXClude ───┘ └─ for ─┬─ UPDate ◄ ─┬─┘ ├─ ADD ──────┤ ├─ MODify ───┤ ├─ REPlace ──┤ ├─ DELete ───┤ └─ DISplay ──┘ ────────────────────────────────────────────────────┐ ─►──────────────────────────────────────────────────┬─┴───────────────────────► ┌───────────────────────────┐ │ ─── is ─┬───┬─▼─┬─ ALL ─────────────────┬─┴─┬───┬─┘ └ ( ┘ ├─ PASsword ────────────┤ └ ) ┘ ├─ CULprit ─────────────┤ ├─ OLQ ─────────────────┤ ├─ ADS ─────────────────┤ ├─ LOAd MODUle ─────────┤ ├─ CLAss and ATTribute ─┤ ├─ CLAss ───────────────┤ ├─ ATTribute ───────────┤ ├─ DC ──────────────────┤ ├─ DEStination ─────────┤ ├─ LINe ────────────────┤ ├─ LOGical-terminal ────┤ ├─ MAP ─────────────────┤ ├─ MESsage ─────────────┤ ├─┬─ PANels ──┬─────────┤ │ └─ SCReens ─┘ │ ├─ PHYsical-terminal ───┤ ├─ QUEue ───────────────┤ ├─ TASk ────────────────┤ ├─ IDD ─────────────────┤ ├─ ELEment ─────────────┤ ├─ ENTRy point ─────────┤ ├─ FILe ────────────────┤ ├─ MODUle ──────────────┤ ├─ PROCess ─────────────┤ ├─ QFIle ───────────────┤ ├─ TABle ───────────────┤ ├─ PROgram ─────────────┤ ├─ RECord ──────────────┤ ├─ REPOrt ──────────────┤ ├─ TRAnsaction ─────────┤ ├─┬─ SYStem ────┬───────┤ │ └─ SUBSYstem ─┘ │ ├─ USEr ────────────────┤ ├─ IDMs ────────────────┤ ├─ SCHema ──────────────┤ └─ SUBSChema ───────────┘ ►─┬──────────────────────────────────────────────────────────────────────────►─ └─┬─ INClude ◄ ─┬─ SIGnon PROfile ismodule-name────────────────────────── └─ EXClude ───┘ ─►───────────────────────────────────────────────────────────────┬────────────► ─┬───────────────────────────────────┬─ LANguage islanguage──┘ └─ Version is ─┬─version-number─┬─┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘ ►─┬───────────────────────────────────┬──────────────────────────────────────► └─ IDD SIGnon is ─┬─ ALLowed ◄ ───┬─┘ └─ NOT ALLowed ─┘ ┌────────────────────────────────────────────────────────────────────────┐ ►─▼─┬────────────────────────────────────────────────────────────────────┬─┴─► └─┬─ INClude ◄ ─┬─ ACCess to ─┬─ SYStem ────┬─system-specification─┘ └─ EXClude ───┘ └─ SUBSYstem ─┘ (expandedsystem-specificationsyntax follows this syntax diagram) ►─┬──────────────────────────────────┬───────────────────────────────────────► └─┬─ INClude ◄ ─┬─ ACCess to ASF ──┘ └─ EXClude ───┘ ►─┬──────────────────────────────────┬───────────────────────────────────────► └─┬─ INClude ◄ ─┬─ ACCess to IDB ──┘ └─ EXClude ───┘ ►─┬──────────────────────────────────────────────┬───────────────────────────► └─ DEFAult for PUBlic access is ─┬─ ALL ◄ ───┬─┘ ├─ NONe ────┤ ├─ UPDate ──┤ ├─ MODify ──┤ ├─ REPlace ─┤ ├─ DELete ──┤ └─ DISplay ─┘ ┌────────────────────────────────────────────────────────────────────────── ►─▼─┬────────────────────────────────────────────────────────────────────────►─ └─┬─ INClude ◄ ─┬─ ACCess to FILefile-name───────────────────────────── └─ EXClude ───┘ ──────────────────────────────────────────────────────────────────┐ ─►────────────────────────────────────────────────────────────────┬─┴─────────► ─┬───────────────────────────────────┬─┬──────────────────────┬─┘ └─ Version is ─┬─version-number─┬─┘ └─ TEXt isuser-text──┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘ ┌────────────────────────────────────────────────────────────────────┐ ►─▼─┬────────────────────────────────────────────────────────────────┬─┴─────► └─┬─ INClude ◄ ─┬─ ACCess to SUBSChemasubschema-specification──┘ └─ EXClude ───┘ (expandedsubschema-specificationsyntax follows this syntax diagram) ►─┬────────────────────────────────┬─────────────────────────────────────────► └─ OLQ ACCess is ─┬─ IDMs sql ─┬─┘ └─ OLQ ◄ ────┘ ►─┬──────────────────────────────────────────────────────────────────────────►─ └─┬─ INClude ◄ ─┬─ ACCess to QFIleqfile-name───────────────────────────── └─ EXClude ───┘ ─►───────────────────────────────────────┬────────────────────────────────────► ─┬───────────────────────────────────┬─┘ └─ Version is ─┬─version-number─┬─┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘ ►─┬──────────────────────────────────────┬───────────────────────────────────► └─ OLQ MENu-mode is ─┬─ ALLowed ◄ ───┬─┘ ├─ NOT ALLowed ─┤ └─ ONLy ────────┘ ►─┬──────────────────────────────────┬───────────────────────────────────────► └─ olq QFIle is ─┬─ ALLowed ◄ ───┬─┘ ├─ NOT ALLowed ─┤ └─ ONLy ────────┘ ►─┬───────────────────────────────────────┬──────────────────────────────────► └─ OLQ QFIle SAVe is ─┬─ ALLowed ◄ ───┬─┘ └─ NOT ALLowed ─┘ ►─┬────────────────────────────────┬─────────────────────────────────────────► └─ olq MRR is ─┬─ ALLowed ◄ ───┬─┘ └─ NOT ALLowed ─┘ ►─┬─────────────────────────────────────┬────────────────────────────────────► └─ olq ─┬─ OPTional ◄ ─┬─ interrupt ──┘ └─ MANdatory ──┘ ►─┬─────────────────────────────────┬────────────────────────────────────────► └─ olq SORt is ─┬─ ALLowed ◄ ───┬─┘ └─ NOT ALLowed ─┘ ►─┬───────────────────────────────────────────┬──────────────────────────────► └─ culprit OVErrides are ─┬─ ALLowed ◄ ───┬─┘ └─ NOT ALLowed ─┘ ►─┬───────────────────────────────────────────────────────────────────┬──────► │ ┌───────────────────────────────┐ │ └ olq DEFault OPtions are ─ ( ─▼─┬─── HEAder ◄ ──────────────┬─┴─ ) ┘ ├─┬─ ECHo ◄ ──┬─────────────┤ │ └─ NO ECHo ─┘ │ ├─┬─ ALL ◄ ─┬───────────────┤ │ └─ NONe ──┘ │ ├─┬─ NO FILler ◄ ─┬─────────┤ │ └─ FILler ──────┘ │ ├─┬─ INTerrupt ◄ ──┬────────┤ │ └─ NO INTerrupt ─┘ │ ├─┬─ WHOle ◄ ─┬─────────────┤ │ └─ PARtial ─┘ │ ├─┬─ FULl ◄ ─┬──────────────┤ │ └─ SPArse ─┘ │ ├─┬─ NO OLQ HEAder ◄ ─┬─────┤ │ └─ OLQ HEAder ──────┘ │ ├─┬─ COMments ◄ ──┬─────────┤ │ └─ NO COMments ─┘ │ ├─┬─ NO CODe TABle ◄ ─┬─────┤ │ └─ CODe TABle ──────┘ │ ├─┬─ NO PATH STAtus ◄ ─┬────┤ │ └─ PATH STAtus ──────┘ │ ├─┬─ NO EXTernal PICture ◄ ─┤ │ └─ EXTernal PICture ──────┤ └─┬─ VERbose ◄ ─┬───────────┘ └─ TERse ─────┘ ┌───────────────────────────────────────────────────────────────────┐ ►─┴─┬───────────────────────────────────────────────────────────────┬─┴──────► └─┬─ INClude ◄ ─┬─ WIThin USEruser-id─┬─────────────────────┬─┘ └─ EXClude ───┘ └─ TEXt isuser-text─┘ ┌────────────────────────────────────────────────────────────────────────┐ ►─▼┬──────────────────────────────────────────────────────────────────────┬┴─► └─┬─ INClude ◄ ─┬─class-nameisattribute-name─┬────────────────────┬┘ └─ EXClude ───┘ └ TEXt isuser-text─┘ ┌────────────────────────────────────────────────────────────────────────┐ ►─▼─┬────────────────────────────────────────────────────────────────────┬─┴─► └─┬─ INClude ◄ ─┬─relational-keyisuser-id─┬────────────────────┬─┘ └─ EXClude ───┘ └ TEXt isuser-text─┘ ┌───────────────────────────────────────────────────────────────┐ ►─▼─┬───────────────────────────────────────────────────────────┬─┴──────────► │ ┌────────────────────┐ │ └─ EDIt ─┬─ COMments ────┬───▼─edit-instruction─┴─ QUIT ──┘ ├─ DEFinition ──┤ └─comment-key─┘ ┌──────────────────────────────────────────────────┐ ►─▼─┬─────────────────────────────────────────────┬──┴───────────────────────►◄ └─┬─ COMments ─────┬── is ─┬─ NULl ─────────┬─┘ ├─ DEFinition ───┤ └─comment-text─┘ └─comment-key──┘Expansion ofsystem-specification►►──system-name─┬───────────────────────────────────┬───────────────────────► └─ Version is ─┬─version-number─┬─┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘ ►─┬───────────────────────────────────────────┬──────────────────────────────► └─ INStallation code ischaracter-literal──┘ ►─┬───────────────────────────────────┬──────────────────────────────────────► └─ PRIority is ─┬─ 0 ◄ ───────────┬─┘ └─user-priority─┘ ►─┬────────────────────────────────────────────────────────────────────┬─────►◄ │ ┌─────────────────┐ │ └─ SECurity classes is ─┬─ ADD ◄ ──┬─┬ ( ──▼─security-code─┴ ) ──┬─┘ └─ DELete ─┘ └─ ALL ───────────────────────┘Expansion ofsubschema-specification►►──subschema-nameof SCHemaschema-name────────────────────────────────────► ►─┬───────────────────────────────────┬──────────────────────────────────────► └─ Version is ─┬─version-number─┬─┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘ ►─┬────────────────────────────────────────────────────────────────────┬─────►◄ └─ SIGnon QFile isqfile-name─┬───────────────────────────────────┬─┘ └─ Version is ─┬─version-number─┬─┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘DISPLAY/PUNCH USER statement (for a single user)►►─┬─ DISplay ─┬─ USEr name isuser-id───────────────────────────────────────► └─ PUNch ───┘ ►─┬──────────────────────────────────────────────────┬───────────────────────► └─ PREpared byuser-id─┬────────────────────────┬─┘ └─ PASsword ispassword─┘ ┌─────────────────────────────────────────────────────────┐ ►─▼─┬─────────────────────────────────────────────────────┬─┴────────────────► │ ┌──────────────────────────────────┐ │ ├─ WITh ──────┬──▼──┬─ ALL ───────────────────────┬─┴─┘ ├─ ALSo WITh ─┤ ├─ ALL COMment TYPes ─────────┤ └─ WITHOut ───┘ ├─ ATTributes ────────────────┤ ├─ COMments ──────────────────┤ ├─ DEFinitions ───────────────┤ ├─ DEStinations ──────────────┤ ├─ DETails ───────────────────┤ ├─ ELements ──────────────────┤ ├─ ENTRy points ──────────────┤ ├─ FILes ─────────────────────┤ ├─ HIStory ───────────────────┤ ├─ LINes ─────────────────────┤ ├─ LOGical-terminals ─────────┤ ├─ MAPS ──────────────────────┤ ├─ MODules ─┬─────────┬───────┤ │ └─ ONLy ──┘ │ ├─ NONe ──────────────────────┤ ├─┬─ PANels ──┬───────────────┤ │ └─ SCReens ─┘ │ ├─ PHYsical-terminals ────────┤ ├─ PROCesses ─────────────────┤ ├─ PROgrams ──────────────────┤ ├─ QFIles ────────────────────┤ ├─ QUEues ────────────────────┤ ├─ RECords ───────────────────┤ ├─ REPorts ───────────────────┤ ├─ SAMe AS ───────────────────┤ ├─ SCHemas ───────────────────┤ ├─ SUBSChemas ────────────────┤ ├─┬─ SYStems ────┬────────────┤ │ └─ SUBSYstems ─┘ │ ├─ TABles ────────────────────┤ ├─ TASks ─────────────────────┤ ├─ TRAnsactions ──────────────┤ ├─ USErs ─────────────────────┤ ├─┬─ USEr DEFINED COMments ─┬─┤ │ └─ UDCs ──────────────────┘ │ ├─┬─ USEr DEFINED NESts ─┬────┤ │ └─ UDNs ───────────────┘ │ ├─ WHEre USED ────────────────┤ └─ WITHIn USEr ───────────────┘ ►─┬──────────────────────────────────────────────────────────────────────────►─ └─ TO ─┬─ SYSpch ────────────────────────────────────────────────────────── └─ MODulemodule-name─┬───────────────────────────────────┬──────── └─ Version is ─┬─version-number─┬─┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘ ─►──────────────────────────────────────────────────────────────────────────┬─► ─────────────────────────────────────────────────────────────────────────┬┘ ─┬──────────────────────┬┬──────────────────────────────────────────────┬┘ └ LANguage islanguage┘└ PREpared byuser-id┬───────────────────────┬┘ └ PASsword ispassword─┘ ►─┬──────────────────────┬──┬─────────────────────┬──────────────────────────►◄ └─ VERB ─┬─ DISplay ─┬─┘ └─ AS ─┬─ SYNtax ───┬─┘ ├─ PUNch ───┤ └─ COMments ─┘ ├─ ADD ─────┤ ├─ MODify ──┤ ├─ REPlace ─┤ └─ DELete ──┘DISPLAY/PUNCH USER statement (for multiple users)►►─┬─ DISplay ─┬─┬─ ALL ──────────────────────────┬─ USErs ───────────────────► └─ PUNch ───┘ └─┬─ FIRst ─┬─┬─ 1 ◄ ──────────┬─┘ ├─ NEXt ──┤ └─entity-count─┘ ├─ LASt ──┤ └─ PRIor ─┘ ►─┬──────────────────────────────────────────────────┬───────────────────────► └─ PREpared byuser-id─┬────────────────────────┬─┘ └─ PASsword ispassword─┘ ►─┬─────────────────────────────────┬────────────────────────────────────────► └─ WHEreconditional-expression──┘ (for completeconditional-expressionsyntax, see WHERE clause) ►─┬──────────────────┬───────────────────────────────────────────────────────► └─ BY ─┬─ SET ◄ ─┬─┘ └─ AREa ──┘ ►─┬──────────────────────────────────────────────────────────────────────────►─ └─ TO ─┬─ SYSpch ────────────────────────────────────────────────────────── └─ MODulemodule-name─┬───────────────────────────────────┬──────── └─ Version is ─┬─version-number─┬─┘ ├─ HIGhest ────────┤ └─ LOWest ─────────┘ ─►──────────────────────────────────────────────────────────────────────────┬─► ─────────────────────────────────────────────────────────────────────────┬┘ ─┬──────────────────────┬┬──────────────────────────────────────────────┬┘ └ LANguage islanguage┘└ PREpared byuser-id┬───────────────────────┬┘ └ PASsword ispassword─┘ ►─┬──────────────────────┬──┬──────────────────────────────────────┬─────────►◄ └─ VERB ─┬─ DISplay ─┬─┘ └─ AS ─┬─ SYNtax ───┬──┬─────────────┬─┘ ├─ PUNch ───┤ └─ COMments ─┘ └─ RECursive ─┘ ├─ ADD ─────┤ ├─ MODify ──┤ ├─ REPlace ─┤ └─ DELete ──┘
Parameters
- USEr name isuser-idIdentifies a new user to be established in the dictionary, or an existing user to be modified, replaced, deleted, displayed, or punched.User-idmust specify a 1- through 32-character alphanumeric value and must be unique in the dictionary.
- MAPtype is/=map-type-name/NULlMAPTYPE has no meaning for CA IDMS since Release 12.0. It does not give an error so that migration can run without changes. MAPTYPE is now processed with DCUF SET MAPTYPE or with a PROFILE as specified in the MAPPING FACILITIES manual. For further information, seeAdvantage ™ CA-IDMS™ Mapping Facility.
- FULl name isfull-user-nameSpecifies a 1- through 32-character name that clarifies or supplementsuser-nameor supplies the full name for an abbreviated user name.
- OF SYStem/SUBSYstemsystem-nameEstablishes (INCLUDE) or removes (EXCLUDE) a documentation relationship between the named user and the requested system or subsystem.
- SAMe AS USEruser-idCopies the following options from the definition of the named user: user nests, attributes, systems associated with the user by means of the OF SYSTEM/SUBSYSTEM clause, and comments.
- NEW NAMe isnew-user-idSpecifies a new name for the requested user. This clause changes only the name specification; it does not alter or delete any previously defined relationships in which the named user participates. Subsequent references to the user must specify the new name.New-user-idmust be a 1- through 32-character value that does not duplicate the name of an existing user.
- PASsword is NULl/passwordEstablishes, replaces, or deletes a password for the named user.passwordmust be a 1- through 8-character alphanumeric value. Specify PASSWORD IS NULL or PASSWORD IS '' to delete a password. This password must appear whenever the user name appears in an IDD SIGNON statement or in a PREPARED BY or REVISED BY clause.If the SET OPTIONS statement specifies INDIVIDUAL PASSWORD SECURITY OVERRIDE IS ON and the USER statement is modifying the issuing user's password, neither AUTHORITY FOR UPDATE IS PASSWORD nor AUTHORITY FOR MODIFY IS USER need be specified; the AUTHORITY clause is described below. However, if the SET OPTIONS statement specifies INDIVIDUAL PASSWORD SECURITY OVERRIDE IS OFF, the issuing user must be assigned PASSWORD authority as well as the appropriate USER entity-type authority.
- AUThority for UPDate/ADD/MODify/REPlace/DELete/DISplayAssigns to (INCLUDE) or removes from (EXCLUDES) the named user the authority to access a secured product or entity type or to perform a secured operation. (Security must have been previously enabled by means of a SET OPTIONS statement SECURITY clause.)This clause also specifies the verbs that the named user can issue for entities within secured products:
- UPDATE specifies that the user can issue all verbs (ADD, MODIFY, REPLACE, DELETE, and DISPLAY/PUNCH). UPDATE is the default.
- ADD specifies that the user can issue only ADD and DISPLAY/PUNCH verbs.
- MODIFY specifies that the user can issue only MODIFY and DISPLAY/PUNCH verbs.
- REPLACE specifies that the user can issue only REPLACE and DISPLAY/PUNCH verbs.
- DELETE specifies that the user can issue only DELETE and DISPLAY/PUNCH verbs.
- DISPLAY specifies that the user can issue only DISPLAY/PUNCH verbs.
- ALLAssigns the user the authority to access all products and entity types and in order to perform all secured operations. AUTHORITY FOR UPDATE IS ALL is required to establish default processing options for a specified dictionary by issuing the SET OPTIONS FOR DICTIONARY statement. This authority is also required to use the FIRST/SECOND/THIRD/FOURTH ALTERNATE PICTURE KEYWORD clause of the SET OPTIONS statement. Finally, AUTHORITY FOR UPDATE IS ALL is required to turn off entity-occurrence security with the REGISTRATION OVERRIDE clause.The IDD installation procedure establishes one user with the AUTHORITY FOR UPDATE IS ALL attribute. This user is named 'CULL DBA' and assigned the password DBAPASS. After the installation, rename 'CULL DBA' and modify the password. Create a backup by adding another user with AUTHORITY IS ALL; if the new name of the DBA is inadvertently forgotten or lost, the backup user can be used.
- PASswordAllows the user to assign or change passwords for other users and to issue the AUTHORITY FOR PASSWORD clause for other users. A user with password authority can update the AUTHORITY clause ofanyuser ID, including his own, to any level. Note that if PASSWORD is selected, the keyword UPDATE must be specified in the FOR clause (described above).
- CULpritAllows the user to access files and subschemas to run CA Culprit reports, change record layouts and file definitions (if the named user is assigned the CULPRIT OVERRIDES ARE ALLOWED option), and to generate DDR reports (if the named user is assigned the CULPRIT OVERRIDES ARE ALLOWED option and is authorized to access subschema IDMSNWKA of schema IDMSNTWK, version 1). This parameter allows the user to perform CA Culprit-related activities when the default processing options for the session include SECURITY FOR CULPRIT IS ON. Note that if CULPRIT is selected, the keyword UPDATE must be specified in the FOR clause (described above).
- OLQAllows the user to code USER statement clauses that control access to CA OLQ files and subschema views and assign OLQ command authorities and processing/reporting options when the default processing options for the session include SECURITY FOR OLQ IS ON. If OLQ is specified, the keyword UPDATE must be specified in the FOR clause (described above).
- ADSAllows the user to generate CA ADS dialogs when the default processing options for the session include SECURITY FOR ADS IS ON. If the keyword UPDATE is specified in the FOR clause (described above), either MODIFY or REPLACE allows the user to modify CA ADS dialogs.
- LOAd MODUleAllows the user to access load modules when the default processing options for the session include SECURITY FOR LOAD MODULE IS ON.
- CLAss and ATTributeAllows the user to access classes, attributes, and user-defined entities when the default processing options for the session include SECURITY FOR CLASS AND ATTRIBUTE IS ON. Note that the keywords CLASS and ATTRIBUTE can be issued separately to assign individual authority for classes or attributes (user-defined entities).
- DCAllows the user to access teleprocessing entities (DESTINATION, LINE, LOGICAL-TERMINAL, MAP, MESSAGE, PANEL, PHYSICAL-TERMINAL, QUEUE, and TASK) when the default processing options for the session include SECURITY FOR IDMS-DC IS ON. Note that the keywords DESTINATION, LINE, LOGICAL-TERMINAL, MAP, MESSAGE, PANEL, PHYSICAL-TERMINAL, QUEUE, and TASK can be issued to assign authority for the specified entity type only.
- IDDAllows the user to access IDD entities (ELEMENT, ENTRY POINT, FILE, MODULE, PROCESS, PROGRAM, QFILE, RECORD, REPORT, TRANSACTION, SYSTEM, TABLE, and USER) when the default processing options for the session include SECURITY FOR IDD SIGNON and/or IDD IS ON. Note that the keywords ELEMENT, ENTRY POINT, FILE, MODULE, PROCESS, PROGRAM, QFILE, RECORD, REPORT, TRANSACTION, SYSTEM, TABLE, and USER can be issued to assign authority only for the specified entity type.
- IDMsAllows the user to access CA IDMS entities (SCHEMA, SUBSCHEMA, and DMCL) when the default processing options for the session include SECURITY FOR IDMS IS ON. Note that the keywords SCHEMA, SUBSCHEMA, and DMCL can be issued to assign authority only for the specified entity type.
- SIGnon PROfile ismodule-nameAssociates (INCLUDE) or disassociates (EXCLUDE) a module that has been defined for use as a signon profile.Module-namemust reference an existing module. The LANGUAGE parameter is required;languagespecifies the language of the signon profile; for example, OLQ or DC. All languages, including user-defined languages, can be specified.When the named user signs onto an application, the commands within the signon profile module are executed automatically. These profiles are not executed when signing onto a DC SYSTEM.
- IDD SIGnon isSpecifies whether the named user is authorized to sign on to and execute the online or batch DDDL compiler when the SET OPTIONS statement specifies SECURITY FOR IDD IS ON.Note that the issuing user must be assigned IDD SIGNON authority.
- ALLowedAuthorizes the user to sign on to the DDDL compiler. ALLOWED is the default.
- NOT ALLowedProhibits the user from signing on to the DDDL compiler.
- ACCess to SYStem/SUBSYstemsystem-nameEstablishes (INCLUDE) or removes (EXCLUDE) a system access privilege. If this clause is specified in a non CA IDMS environment, the user/system relationship is documentation.You must have IDMS-DC authority to use this clause.
- INStallation code ischaracter-literalSpecifies an installation code for the named user. This code can be accessed at runtime by user exits or programs to provide additional security.Character-literalmust be a 1- through 32-character alphanumeric symbol specified as an absolute expression.
- PRIority is 0/user-prioritySpecifies the dispatching priority for the named user. DC/UCF uses the dispatching priority in combination with task and logical terminal priorities to establish a run-time dispatching priority for tasks initiated by the named user.User-prioritymust be an integer in the range 0 through 255; the default for ADD operations is 0. A high number indicates a high dispatching priority.
- SECurity classes isAdds or deletes securityclass codes for the named user; the user can execute only programs and tasks with matching security classes.
- ADD/DELeteSpecifies that the named security classes are added to or deleted from the user definition; ADD is the default for ADD operations.
- security-code/ALLSpecifies that the named security classes or all security classes are the object of the ADD or DELETE request.Security-codemust be an integer in the range 1 through 255; multiple values must be enclosed in parentheses and separated by blanks.
- ACCess to ASFSpecifies that the named user has (INCLUDE) or does not have (EXCLUDE) access to the CA IDMS ASF
- ACCess to IDBSpecifies that the named CA IDMS or Information Center Management System (ICMS) user has (INCLUDE) or does not have (EXCLUDE) access to the Information Database (IDB).
- DEFAult for PUBlic access isAssigns a default public access specification to the named user. This feature, for ASF users only, is used to identify the public access level to be established by the user when storing entity-occurrence definitions in the dictionary through ASF. If an option other than ALL is specified, ASF automatically generates the appropriate registration option within the entity definition.
- ACCess to FILefile-nameSpecifies that the named CA Culprit user has access to the named file. Note that if CA Culprit security is enabled, the requested user must be assigned CULPRIT authority in order to access the named file.
- ACCess to SUBSChemasubschema-nameof SCHemaschema-nameSpecifies that the named CA OLQ or CA Culprit user has access to (INCLUDE) or does not have access to (EXCLUDE) the named subschema.Subschema-namemust identify a subschema view associated withschema-name. If CA OLQ or CA Culprit product security has been enabled in the SET OPTIONS statement SECURITY clause, the issuing user must be assigned OLQ or CULPRIT authority.
- SIGnon QFIle isqfile-nameAssociates an existing qfile with the named subschema and establishes access privilege to that qfile for the named CA OLQ user. The named qfile is invoked automatically when the user signs on to OLQ and names the associated subschema.The qfile access privilege does not permit the named user to execute qfiles; the qfile execution privilege is established separately by means of the OLQ QFILE clause described below.
- OLQ ACCess isIndicates an CA OLQ user's type of qfile access.
- IDMs sqlSpecifies qfile access using the functionality available with the CA IDMS SQL, providing the CA IDMS SQL is installed. IDMs sql, IDMssql, and IDMS-SQL are synonyms and can be used interchangeably.More information: For more information on CA IDMS SQL, see theCA IDMS SQL Reference section.
- OLQSpecifies qfile access using the functionality available with CA OLQ. OLQ is the default for OLQ ACCESS.
- ACCess to QFIleqfile-nameSpecifies that the named CA OLQ user has access to (INCLUDE) or does not have access to (EXCLUDE) the named qfile. Note that the qfile access privilege does not permit the named user to execute qfiles; qfile execution privilege is established separately by means of the OLQ QFILE clause described below.
- OLQ MENu-mode isSpecifies whether the named user is authorized to access CA OLQ in menu mode. If the SET OPTIONS statement specifies SECURITY FOR OLQ IS ON, the issuing user must be assigned OLQ authority.
- ALLowedAuthorizes the CA OLQ user to access CA OLQ in menu mode. ALLOWED is the default.
- NOT ALLowedProhibits the CA OLQ user from accessing CA OLQ in menu mode.
- ONLySpecifies that the CA OLQ user is allowed to access CA OLQ in menu mode only.
- OLQ QFIle isSpecifies whether the named user is authorized to execute CA OLQ qfiles. If the SET OPTIONS statement specifies SECURITY FOR OLQ IS ON, the issuing user must be assigned OLQ authority.
- ALLowedAuthorizes the CA OLQ user to execute qfiles. ALLOWED is the default.
- NOT ALLowedProhibits the CA OLQ user from executing qfiles.
- ONLySpecifies that the CA OLQ user is authorized to access CA OLQ only through qfiles.
- OLQ QFIle SAVe isSpecifies whether the named CA OLQ user is authorized to save paths and CA OLQ command groups as qfiles. If the SET OPTIONS statement specifies SECURITY FOR OLQ IS ON, the issuing user must be assigned OLQ authority.
- ALLowedAuthorizes the CA OLQ user to save paths and groups of commands as qfiles. ALLOWED is the default.
- NOT ALLowedProhibits the CA OLQ user from saving paths and groups of commands as qfiles.
- olq MRR isSpecifies whether the named CA OLQ user is authorized to retrieve multiple record occurrences with a single CA OLQ command. If the SET OPTIONS statement specifies SECURITY FOR OLQ IS ON, the issuing user must be assigned OLQ authority.
- ALLowedAuthorizes the CA OLQ user to retrieve multiple record occurrences with a single OLQ command. ALLOWED is the default.
- NOT ALLowedProhibits the CA OLQ user from retrieving multiple record occurrences with a single CA OLQcommand.
- olq OPTional/MANdatory interruptSpecifies whether the named CA OLQ user is authorized to select the OLQ NOINTERRUPT option (described below). If the SET OPTIONS statement specifies SECURITY FOR OLQ IS ON, the issuing user must be assigned OLQ authority.
- OPTionalAuthorizes the CA OLQ user to select the OLQ NOINTERRUPT option.
- MANdatoryRequires that the OLQ INTERRUPT be enabled at all times for the user.
- olq SORt isSpecifies whether the named CA OLQ user can issue the CA OLQ SORT command. If the SET OPTIONS statement specifies SECURITY FOR OLQ IS ON, the issuing user must be assigned OLQ authority.
- ALLowedAuthorizes the CA OLQ user to issue the CA OLQ SORT command. ALLOWED is the default.
- NOT ALLowedProhibits the CA OLQ user from issuing the CA OLQ SORT command.
- culprit OVErrides areSpecifies whether the named CA Culprit user is authorized to define file attributes and records. If the SET OPTIONS statement specifies SECURITY FOR CULPRIT IS ON, the issuing user must be assigned CULPRIT authority.
- ALLowedAuthorizes the CA Culprit user to code file attributes and REC parameters. ALLOWED is the default.
- NOT ALLowedProhibits the CA Culprit user from coding file attributes and REC parameters.
- olq DEFAult OPTions areSpecifies the CA OLQ processing control and display options that will be in effect when the named user signs on to CA OLQ. If the SET OPTIONS statement specifies SECURITY FOR OLQ IS ON, the issuing user must be assigned OLQ authority.
- HEAder/NO HEAderSpecifies whether CA OLQ report files will contain a header line. This option has no effect on single-record-occurrence retrieval displays. The default for ADD is HEADER.
- ECHo/NO ECHoSpecifies whether a user-entered command will be repeated by CA OLQ on the output device. The default for ADD is ECHO.
- ALL/NONeSpecifies whether the default internal field list for all records retrieved during the named user's CA OLQ session will contain all or none of the fields. The default for ADD is ALL.
- NO FILler/FILlerSpecifies whether filler field values will be displayed. The default for ADD is NO FILLER.
- INTerrupt/NO INTerruptSpecifies whether the processing interrupt feature for multiple record retrievals will be enabled or disabled. The default for ADD is INTERRUPT.The OLQ MANDATORY INTERRUPT specification takes precedence over NO INTERRUPT.
- WHOle/PARtialSpecifies the content of displayed path retrieval report lines. WHOLE displays only those lines containing a retrieved occurrence for every record type in a path definition. PARTIAL displays all lines, whether or not they contain data for every path record type. The default for ADD is WHOLE.
- FULl/SPArseSpecifies the format of displayed path retrieval report lines. FULL displays data associated with a record type once for each retrieved occurrence. SPARSE displays data associated with a record type only once, regardless of how many associated record occurrences are retrieved. The default value for ADD is FULL.
- NO OLQ HEAder/OLQ HEAderSpecifies whether the CA OLQ report file contains a header line. This option has no effect on single-record-occurrence retrieval displays. The default for ADD is NO OLQ HEADER.
- COMments/NO COMmentsSpecifies whether comments will accompany the output from HELP RECORDS, HELP SUBSCHEMAS, and HELP QFILE requests. The default for ADD is COMMENTS.
- NO CODe TABle/CODe TABleSpecifies whether CA OLQ will access a code table to encode and decode data. The default for ADD is NO CODE TABLE.
- NO PATH STAtus/PATH STAtusSpecifies the conditions under which CA OLQ will retrieve a logical record. NO PATH STATUS requests CA OLQ to retrieve a logical record only when the path status of LR-FOUND is returned. PATH STATUS requests CA OLQ to retrieve a logical record when any DBA-defined path status is returned. The default for ADD is NO PATH STATUS.
- NO EXTernal PICture/EXTernal PICtureSpecifies whether CA OLQ will use external pictures for displaying data. The default for ADD is NO EXTERNAL PICTURE.
- VERbose/TERseControls the amount of information displayed following record and field-level breaks. The default for ADD is VERBOSE.
- WIThin USEruser-idAssociates (INCLUDE) the user with or disassociates (EXCLUDE) the user from the user identified byuser-id.
- WITh/ALSo WITh/WITHOutIncludes or excludes the specified options when the named user is displayed or punched. Detailed information for each DISPLAY/PUNCH option is under SET OPTIONS Syntax. The options that are listed below present special considerations for this entity type.
- DETailsIncludes the following specifications:
- DESCRIPTION
- PASSWORD IS ASSIGNED
- FULL NAME
- AUTHORITY
- OLQ MENU-MODE
- OLQ QFILE
- OLQ MRR
- OLQ INTERRUPT
- OLQ SORT
- OLQ DEFAULT OPTIONS
- CULPRIT OVERRIDES
- IDD SIGNON
- USErsIncludes all the users related by the WITHIN USER clause or relational-key clause.
Usage
If you specify REPLACE
If you specify REPLACE, the DDDL compiler initializes to defaults and/or excludes the following:
- FULL NAME
- DESCRIPTION
- OLQ DEFAULT OPTIONS
- OLQ options
- CULPRIT OVERRIDES
- USER REGISTERED FOR
- PUBLIC ACCESS
- COMMENTS/DEFINITIONS/comment-key
- AUTHORITY
- ACCESS TO SUBSCHEMA
- ACCESS TO SYSTEM/SUBSYSTEM
- ACCESS TO QFILE
- WITHIN USER
- ATTRIBUTES
The following relationships that include the named user or that the user is related to or registered for are not affected:
- Attributes
- Destinations
- Elements
- Files
- Lines
- Logical terminals
- Modules
- Panels
- Physical terminals
- Processes
- Programs
- qfiles
- Queues
- Records
- Systems (subsystems)
- Tables
- Tasks
- Users to which the named user is related
Additionally, the following definitions are not affected:
- User definitions built by other CA IDMS components
- Users that are related to other users
If you specify DELETE
If you specify DELETE, the DDDL compiler disassociates the named user from all entity occurrences, unless the user is the last user assigned the REGISTERED FOR ALL option; see PUBLIC ACCESS Clause for further details.
Default public access (ASF)
The default public access for entity occurrences stored by the named user through ASF is assigned as follows:
- ALL specifies that unregistered users are allowed to issue all verbs and perform all secured operations. ALL is the default.
- NONE specifies that unregistered users are not allowed to access the entity occurrence.
- UPDATE specifies that unregistered users are allowed to issue all verbs.
- MODIFY specifies that unregistered users are allowed to issue only MODIFY and DISPLAY/PUNCH verbs.
- REPLACE specifies that unregistered users are allowed to issue only REPLACE and DISPLAY/PUNCH verbs.
- DELETE specifies that unregistered users are allowed to issue only DELETE and DISPLAY/PUNCH verbs.
- DISPLAY specifies that unregistered users are allowed to issue only DISPLAY/PUNCH verbs.
USER AUTHORITY considerations
Consider the following points regarding user authority:
- Authority for IDD (or for a specific entity) is required to access abasicentity.
- Authority for CA IDMS (or for a specific entity) is required to access adatabaseentity.
- Authority for IDD or MODULE is required before INCLUDE clauses can be processed.
- Authority for DC only applies to IDD usage. If a DC component was built or is owned by the system generation compiler and the DDDL compiler processes the component, only dictionary security is checked, not the central security used by system generation.
- Authority for MODULE includes authority for QFILE, TABLE, and PROCESS.
- ELEMENT authority isnotrequired to:
- Associate an existing element with a record.
- Delete an existing element by using DELETE RECORD if the element doesn't exist in another record.
- RECORD authority isnotrequired to associate an existing record with a schema if you use the SHARE STRUCTURE parameter of the schema RECORD statement.
- LOAD MODULE authority isnotrequired to generate tables, subschemas, or DC/UCF systems. Itisrequired to use LOAD MODULE with the subschema and DDDL compilers.
- CLASS and ATTRIBUTE authority arenotrequired to associate an attribute with an automatic class (a class defined as AUTOMATIC PLURAL).
- ATTRIBUTE authority isnotrequired to associate an existing user-defined comment or nest with an entity.
Example
In the following example, the ADD statement defines user DGS as a user of the systems INVENTORY and STOCK-UPDATE, supplying a full name, a password, and a description. The ACCESS TO SUBSCHEMA clauses assign access to two versions of a subschema and two signon qfiles.
The ACCESS TO SYSTEM clauses allow the user to access the systems INVENTORY and STOCK UPDATE through DC/UCF.
Additional clauses authorize DGS to change the OLQ INTERRUPT option and grant DGS IDMS authority. The OLQ DEFAULT OPTIONS clause specifies display of FILLER fields and PARTIAL lines. The class/attribute clause associates the LIBRARY class with the attribute PRIVATE. The relational-key clause associates user MRS with user DGS.
add user name is dgs prepared by dba password is 'ice 9' password is sgd full name is 'dianna g. smith' user description is programmer within user development of system inventory of system stock-update access to subschema invbasea of schema invbase version 2 signon qfile is invon version 2 access to subschema invbasea of schema invbase signon qfile is invon access to system inventory access to system stock-update optional interrupt olq default options filler partial authority for display is idms authority for update is password library is private 'other developer' is mrs.
The MODIFY statement changes the password for the user DGS:
modify user dgs prepared by dgs password is sgd password is gsd.