Using CA Tape Encryption in Your z/OS Environment › Business-to-Business Encryption Using Code Books › Define a Code Book

Define a Code Book

You must define a code book for each non-z/OS business partner with whom you want to share your encrypted data.

To define a code book

1. Find the <B2BCodeBooks> section of the B2BBOOKS parmlib member.
2. Add a CodeBook= statement for each code book you want to define, for example:

   <B2BCodeBooks>
     CodeBook = CompanyABook
     CodeBook = ACMECorpBook
   

   The name of each code book can be a maximum of 26 alphanumeric characters, and may contain the following special characters: $, #, @.

   Note: Any spaces that come before the first non-space character will be discarded.

3. Create a section named after the code book that contains a Rebuild= statement for each code book you defined. This statement indicates how often the code book should be rebuilt, for example:

   <CompanyABook>
     Rebuild = weekly
   

   <ACMECorpBook>
     Rebuild = monthly
   

   The following values are available:

   Weekly

   Specifies that the code book is rebuilt every Monday at 6:00 a.m. local time.

   Monthly

   Specifies that the code book is rebuilt on the first Monday of every month at 6:00 a.m. local time.

   Yearly

   Specifies that the code book is rebuilt on the first Monday of the year at 6:00 a.m. local time.

   Default: Monthly

   Note: CA Tape Encryption checks for the need to rebuild code books and performs the rebuild logic every Monday at 6:00 a.m. local time. If the BES address space is not active when a code book is scheduled to be rebuilt, the code book will be rebuilt the next time the address space is active.

4. Issue the REFRESH=CODEBOOKS operator command.

   The CA Tape Encryption subsystem dynamically reloads the B2BBOOKS parmlib member and the code books are created.

Note: For more information on the <B2BCodeBooks> section of the B2BBOOKS member, see the sample member in the parmlib.