How can I demonstrate that a CA View Database, and its tapes, are encrypted?
Article ID: 133053
Updated On:
Products
Issue/Introduction
The client has a CA View database that has been encrypted for the past 2 years, and all tapes have been newly created since that date, to ensure they too are encrypted.
They were asked to prove or demonstrate the CA-View database is, in fact, encrypted.
What ways can be used to demonstrate that encryption is in place?
Environment
Release :
Component : CA View
Resolution
If there is SARINIT parameter of ENCRYPT=ICSF,nnn, there should be the following message in the related SARSTC task:
IEF403I SARSTC - STARTED - TIME=02.09.34
SARSTC42 Encryption enabled for VIEW.SYSTEM1
. The purpose of database encryption is that someone would not be able to see anything in the database if a non-View product is used.
. A way to demonstrate that a View database is encrypted is to:
. . Use the IDCAMS PRINT statement, where view.dataset is the full name of the View database data set (extent), for example VIEW.SYSTEM1.SARDBASE.D0000001
. . COUNT(nnn) identifies the number of blocks.
. . For example, use COUNT(100) to print 100 blocks.
. . Include DUMP on the PRINT statement, to indicate to print in DUMP format.
//JOBNAME JOB ...
//IDCAMS EXEC PGM=IDCAMS
//IN1 DD DISP=SHR,DSN=view.dataset
//SYSPRINT DD SYSOUT=X
//SYSIN DD *
PRINT INFILE(IN1) DUMP COUNT(n)
//
. A way to demonstrate that a View tape is encrypted is to:
. . Use the IDCAMS PRINT statement, where view.dataset is the full name of the View tape, for example VIEW.SYSTEM1.SARTAPE.T0000001
. . COUNT(n) identifies the number of blocks.. . For example, use COUNT(100) to print 100 blocks.
. . Include DUMP on the PRINT statement, to indicate to print in DUMP format.
//JOBNAME JOB ...//IDCAMS EXEC PGM=IDCAMS
//IN1 DD DISP=SHR,DSN=view.dataset
//SYSPRINT DD SYSOUT=X
//SYSIN DD *
PRINT INFILE(IN1) DUMP COUNT(n)
//
. On both the outputs, samples of report data will show to not have printable characters, as the data is encrypted.Feedback
