Manual data set creation


To manually create history data sets, perform the following steps. These steps must be repeated for each managed region.


  1. Copy the BBSAMP member CMRDDTL to your UBBSAMP data set.Ensure the new member name conforms to your site's naming conventions.

  2. Using the comments in the member, edit the member. 
    When you define more than two CMRDETL files, you must ensure that you create a file with the specified prefix in Dataset I and  appropriate suffix for all files to be used. For example, if you are planning to use 5 CMRDETL files, you must create the files with these names: prefix.D01, prefix.D02, prefix.D03, prefix.D04, and prefix.D05. Do not skip any suffix numbers.

  3. Replace the line that begins with the following text with a valid job statement for your site:

    //CMRDDTL JOB
  4. Calculate the primary record extent that is required for the CMRDETL data sets by estimating the number of CICS transactions to be stored on a single data set.For more information. see Calculate-primary-record-specification.

  5. Replace all occurrences of CMR.CICS1 with prefix.cicsName where cicsName is the name of the IBM CICS region. This step creates unique data sets for each CICS region.

  6. Replace all occurrences of CICSMGR with the prefix of the BBLINK data set name.
  7. Replace all occurrences of ?????? with the ID of the volume where the CMRDETL data sets are located.

  8. Replace RECORDS(15000 0) with RECORDS( primary 0), where primary is the primary record allocations that were calculated in Step 4.The secondary allocation should always be 0.

Submit the job.

Note

Do not change any other VSAM attributes in the JCL. The VSAM data set must be a regular single volume VSAM KSDS with no secondary allocations defined. The data set can be in extended format with extended addressability but it cannot have VSAM attributes or be under any DASD management that involves any of the following attributes:

  • Data striping
  • Compression of any kind
  • Buffer optimization of any kind such as SMS system-managed buffering (SMB)
  • Partial release of free space
  • Retention restriction
  • Any other management attribute that will manipulate the data or affect the availability of the data set


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*