HP 3000 Manuals

CHANGE ITEMSECURITY [ DBChange Plus User's Guide ] MPE/iX 5.0 Documentation


DBChange Plus User's Guide

CHANGE ITEMSECURITY 

Changes user class access to a data item.

Syntax 

                                                     {R}
CHA[NGE] ITEMSE[CURITY] DataItemName UserClassNumber {W}
                                                     {N}

Parameters 

DataItemName        is the name of a data item whose security is to be
                    changed.

UserClassNumber     is a user class number defined in the PASSWORD part
                    of the schema.  User class numbers are used in the
                    schema security lists to define access to each data
                    set and data item.

R                   allows read-only access to the data item.

W                   allows write access (and implied read access) to the
                    data item.

N                   denies any access to the data item.

Description 

Use this command to change user class access to a data item.  To deny all
users access, create a null (or empty) list (/), which allows only the
creator access to the data item.  When making changes to data item
security, remember that access to data items within data sets may be
further allowed or restricted by data set security.

Example 

     >change itemsecurity quantity 18 w 

     >change itemsecurity quantity 14 r 

     >change itemsecurity credit-rating 14 n 

In this example, user class 18 is given write access to the data item
QUANTITY. User class 14 is given read access to the data item QUANTITY
and is denied any access to the data item CREDIT-RATING.

Before the change, the ITEMS part of the schema looks like this:

     ITEMS:
       ACCOUNT         , J2(0,11,12,13,14,18/);
       BINNUM          , Z2(/13);
       CITY            , X12(12,13,14,/11);
       CREDIT-RATING   , R2(/14);                <---- security to be changed 
       DATE            , X6(0,11,12,13,14,18/);
       DELIV-DATE      , X6(/14);
       DESCRIPTION     , X20(0,11,12,13,14,18/);
       FIRST-NAME      , X10(14/11);
       INITIAL         , U2(14/11);
       LAST-NAME       , X16(14/11);
       LASTSHIPDATE    , X6(12/);
       ONHANDQTY       , J2(14/12);
       PRICE           , J2(14/);
       PURCH-DATE      , X6(11/14);
       QUANTITY        , I1(/14);                <---- security to be changed 
       STATE           , X2(12,13,14,/11);
       STOCK#          , U8(0,11,12,13,14,18/);
       STREET-ADD      , S26(12,13,14/11);
       SUPPLIER        , X16(12,13/);
       TAX             , J2(14/);
       TOTAL           , J2(11,14);
       UNIT-COST       , P8(/12);
       ZIP             , X6(12,13,14/11);

After the change, the ITEMS part of the schema looks like this:

     ITEMS:
       ACCOUNT         , J2(0,11,12,13,14,18/);
       BINNUM          , Z2(/13);
       CITY            , X12(12,13,14,/11);
       CREDIT-RATING   , R2(/);                  <---- security changed 
       DATE            , X6(0,11,12,13,14,18/);
       DELIV-DATE      , X6(/14);
       DESCRIPTION     , X20(0,11,12,13,14,18/);
       FIRST-NAME      , X10(14/11);
       INITIAL         , U2(14/11);
       LAST-NAME       , X16(14/11);
       LASTSHIPDATE    , X6(12/);
       ONHANDQTY       , J2(14/12);
       PRICE           , J2(14/);
       PURCH-DATE      , X6(11/14);
       QUANTITY        , I1(14/18);              <---- security changed 
       STATE           , X2(12,13,14,/11);
       STOCK#          , U8(0,11,12,13,14,18/);
       STREET-ADD      , S26(12,13,14/11);
       SUPPLIER        , X16(12,13/);
       TAX             , J2(14/);
       TOTAL           , J2(11,14);
       UNIT-COST       , P8(/12);
       ZIP             , X6(12,13,14/11);



MPE/iX 5.0 Documentation