They don't, but sometimes they do. We have several data management rules in place for HLQ1 datasets, i.e. no backups, which wouldn't carry over if the dataset was copied to HLQ2.
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, June 28, 2019 8:45 AM, Bill Johnson <[email protected]> wrote: > If they have access to HLQ1.data and the encryption key. Why would they need > to copy it to another dataset? > > Sent from Yahoo Mail for iPhone > > On Friday, June 28, 2019, 7:39 AM, Mark Jacobs > [email protected] wrote: > > Outside of using dataset conditional access rules is there anyway to prevent > someone from copying encrypted dataset HLQ1.data to HLQ2.data? They have > access rights to both HLQ's and the encryption key. > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get&[email protected] > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
