CA VISION:Results and CA Datacom Database Transparency Option for VSAM

Products

• Vision:Results
• Vision:Sixty

Issue/Introduction

CA VISION:Results and CA Datacom Database Transparency Option for VSAM

Environment

Release:
Component: V:RSLT

Resolution

To set up CA VISION:Results to interface with the CA Datacom Database Transparency Option for VSAM, please note:

Our software development team has created a custom modification to enable use of the CA Datacom Database Transparency Option for VSAM. You can get the custom modification from our Support Team at 1-800-328-7463. You must apply this custom modification as a patch to the CA VISION:Results software product.

Although the CA VISION:Results programs you have created remain unchanged, you must add JCL pointing to various CA Datacom databases, files and libraries to the CA VISION:Results execution JCL stream. Here's a z/OS JCL example showing the additional JCL statements in bold lettering:

//STEP1    EXEC PGM=DYL280
//STEPLIB  DD DSN=your.results.loadlib,DISP=SHR
//         DD DSN=your.datacom.install.CUSLIB,DISP=SHR
//         DD DSN=your.datacom.install.CAILIB,DISP=SHR
//         DD DSN=your.ca90s.loadlib,DISP=SHR
//CUSTMR   DD DISP=SHR,SUBSYS=(ssss,'VUTNM=DVVUTPR')
//DB$VSAMT DD DSN=your.VSAM.transparency.model,DISP=SHR 
//SYSCOPY  DD DSN=your.results.copylib,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYS004   DD UNIT=VIO,SPACE=(TRK,(5,5))
//SYSOUT   DD SYSOUT=*
//SYS280R  DD SYSOUT=*
//SYSIN    DD *
FILE CUSTMR KSDS F 153
       $COBOL
       01  CUS-RECORD.
        05  CUS-ID.
         10   IND-CD         PIC X(01).
         10   CUST-NO        PIC 9(04).
        05  CUS-NAME         PIC X(30).
        05  CUS-ADDR-1       PIC X(30).
        05  CUS-ADDR-2       PIC X(30).
        05  CUS-CITY         PIC X(15).
        05  CUS-STATE        PIC X(02).
        05  CUS-ZIP.
         10  CUS-ZIP-5       PIC X(05).
         10  CUS-ZIP-4       PIC X(04).
        05  CUS-CREDIT-IND   PIC X(01).
        05  CUS-PHONE.
         10   CUS-PHONE-AREA PIC X(03).
         10   CUS-PHONE-EXCH PIC X(03).
         10   CUS-PHONE-NUMB PIC X(04).
        05  CUS-OPEN-DOLLAR  PIC S9(7)V99 USAGE IS COMP-3.
        05  CUS-YTD-SALES    PIC S9(7)V99 USAGE IS COMP-3.
         10   ACT-YR         PIC X(02).
         10   ACT-MO         PIC X(02).
         10   ACT-DAY        PIC X(02).
        05  SLMN-ID          PIC X(05).
       $ECOBOL
REPORT 132 WIDE
LIST CUS_ID CUS_NAME CUS_YTD_SALES
/*
//

• $COBOL and $ECOBOL must be coded in column 8 or later to include COBOL definition statements directly (without the use of COPY).
• The dataset 'your.results.loadlib' is your CA VISION:Results loadlib.
• The datasets 'your.datacom.install.CUSLIB', and 'your.datacom.install.CAILIB' are your install datasets for CA Datacom.
• The dataset 'your.ca90s.loadlib' is required for the LMP key.
• The DDNAME 'CUSTMR' is a sample VSAM definition against CA Datacom.
• The subsystem id 'ssss' should be replaced with your installed CA Datacom VSAM Transparency Option subsystem ID.
• DVVUTPR is the CA Datacom VSAM Transparency Option interface table (VIT) containing the VSAM files that have been converted to CA Datacom.
• The DDNAME 'DB$VSAMT' is a VSAM model file required for each step using the CA Datacom VSAM Transparency Option.