Maybe one is SMS-Managed and one isn't. On 2019-06-28 08:52, Mark Jacobs wrote: > 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com&data=02%7C01%7C%7C066837fc672f4ee955c408d6fbc79957%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636973232047520378&sdata=kA7QOlpjhFP6%2BD%2BydzRdsA2RsAz0XfP3n9tuChWk49I%3D&reserved=0 > > ‐‐‐‐‐‐‐ 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com&data=02%7C01%7C%7C066837fc672f4ee955c408d6fbc79957%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636973232047520378&sdata=kA7QOlpjhFP6%2BD%2BydzRdsA2RsAz0XfP3n9tuChWk49I%3D&reserved=0 >> >> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> >> 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 > . >
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
