Definition for a dataset
Use this element to define or delete a dataset profile.
<namespace:dataset name=”datasetName” generic=”yes|no” volume=”volid" operation=”set|del” requestid=”reqid” run=”yes|no” override="yes|no|force">
- name – Dataset name. (1-44 characters). This is a fully qualified dataset name. The userid is not prepended to this dataset name as high level qualifier. The dataset name can be generic or not. Dataset name must be specified, or else an error occurs.
- generic – Default is no. If yes, dataset is treated as a generic, even if it contains no generic characters.
- volume – A single volume name for this dataset. If multiple volumes are needed, the XML must contain multiple <dataset > definitions, each specifying the current volume, with another volume to be added with the <volume> field filled in. Only one <volume> can be specified per <dataset> definition. Volume is optional. If generic=”yes” is specified, volume is ignored by RACF®.
- operation – Action to apply to definition. Value must be all lowercase. One of:
- set → Define the dataset and set all specific data contained with in the <dataset..>.. </dataset> tags.
- del → Delete the dataset profile from the system
- requestid – An optional label which identifies the security definition. This is used so a caller can more easily locate the results of this particular security definition in the in the result.
- run – Default=yes. If set to 'no', the security definition is skipped.
- override – Default=”yes”. Works in conjunction with the '00000002'x – PRECHECK option.
Ignored if operation is not “set”.
- If the PRECHECK option is set, an attempt is made to locate the dataset in the RACF database.
- If the dataset is found, processing depends on the value of the override attribute:
- yes – An alter command is generated to update the dataset with the data contained in the XML.
- no – The dataset is not updated at all
- force - An add command is generated, followed by an alter command to update the dataset with the data contained in the XML.
- If the dataset is not found, an add command is generated, followed by an alter command to update the dataset with the data contained in the XML.
- If the dataset is found, processing depends on the value of the override attribute:
- If the PRECHECK option is not set, an add command is generated, followed by an alter command to update the dataset with the data contained in the XML.
- If the PRECHECK option is set, an attempt is made to locate the dataset in the RACF database.
Segments and fields are specified as documented for a <user>. The segment and field names can be found in the Data set administration in Reference documentation tables.