-
Locating the Distribution Files
On your workstation, create a Connect CDC (SQData) directory and a Version/Release specific sub-directory. We recommend a directory structure similar to the following for this and future releases.
D:\SQData The base product directory D:\SQData\V4nnnn A ver-rel-build specific sub-directory
Connect CDC (SQData) for z/OS is available for download from Precisely https://www.precisely.com/support. Download the seven Connect CDC (SQData) distribution files into newly created version-release sub-directory. If necessary, unzip the sqdata-zos-4.nn.nn.zip distribution to yield the terse files.
-
Upload Distribution Files to z/OS
Upload the Connect CDC (SQData) distribution terse files, in binary, to your z/OS system. Make sure that you upload these files to datasets with a format of FB 1024.
You may be able to use a windows Batch file to FTP the distribution files. Copy and paste the following lines into an new file named UpLoadSQD.bat; save the file and execute at the command line:
echo off rem **************************************************************** rem * Command Script to Upload the SQDATA Distribution Terse Files* rem **************************************************************** rem ---------------------------------------------------------------- rem Modify the following as required for your environment below rem ---------------------------------------------------------------- rem SDIR: the name of the source Windows directory rem V: the Version number rem R: the Release number rem B: the Build number rem HOST: the name or IP address of the z/OS host system rem USER: a valid z/OS userid for the target host system rem PSWD: a valid z/OS password for the target host system rem HLQ: High level library Qualifier on target host system rem ---------------------------------------------------------------- rem **************************************************************** rem * Dynamically create an FTP script file and upload all the * rem * TERSE files to the target host SQDATA High Level Qualifier* * rem **************************************************************** set /p SDIR="Enter your Download Directory: " dir %SDIR% set /p V="Enter single digit Version: " set /p R="Enter two digit Release: " set /p B="Enter two digit Build: " set /p HOST="Enter your zOS Host name or IP Address: " set /p USER="Enter your zOS User-ID: " set /p PSWD="Enter your zOS Password: " set /p HLQ="Enter the High level library Qualifier eg:TEST: " echo %user% > u.ftp echo %pswd% >> u.ftp echo prompt >> u.ftp echo binary >> u.ftp echo quote site recfm=fb lrecl=1024 blksize=27648 cy pri=10 sec=10 >> u.ftp echo cd '%HLQ%' >> u.ftp echo put %SDIR%/%V%.%R%.%B%/SQDATA.*.CNTL.TERSE SQDATA.V%V%%R%%B%.CNTL.TERSE >> u.ftp echo put %SDIR%/%V%.%R%.%B%/SQDATA.*.DBRMLIB.TERSE SQDATA.V%V%%R%%B%.DBRMLIB.TERSE >> u.ftp echo put %SDIR%/%V%.%R%.%B%/SQDATA.*.ISPFLIB.TERSE SQDATA.V%V%%R%%B%.ISPFLIB.TERSE >> u.ftp echo put %SDIR%/%V%.%R%.%B%/SQDATA.*.PARMLIB.TERSE SQDATA.V%V%%R%%B%.PARMLIB.TERSE >> u.ftp echo put %SDIR%/%V%.%R%.%B%/SQDATA.*.PGMOBJ.TERSE SQDATA.V%V%%R%%B%.PGMOBJ.TERSE >> u.ftp echo put %SDIR%/%V%.%R%.%B%/SQDATA.*.PROCLIB.TERSE SQDATA.V%V%%R%%B%.PROCLIB.TERSE >> u.ftp echo put %SDIR%/%V%.%R%.%B%/SQDATA.*.SAMPLIB.TERSE SQDATA.V%V%%R%%B%.SAMPLIB.TERSE >> u.ftp echo quit >> u.ftp ftp -s:u.ftp %host% echo you may delete this file > u.ftp echo File transfer complete
-
Unterse the Distribution ISPFLIB file
Using the following JCL as an example, create the SQDATA.V4nnnn.ISPFLIB library by untersing the distribution ISPFLIB.TERSE file.
//UNTERSE EXEC PGM=AMATERSE,PARM='UNPACK' //SYSPRINT DD SYSOUT=* //SYSUT1 DD DISP=SHR,DSN=SQDATA.V4nnnn.ISPFLIB.TERSE //SYSUT2 DD DSN SQDATA.V4nnnn.ISPFLIB, // DCB=(RECFM=FB,LRECL=80,BLKSIZE=32720), // DISP=(,CATLG,DELETE),UNIT=SYSALLDA,DSNTYPE=LIBRARY, // SPACE=(TRK,(60,15,1))
-
Execute the ISPF Installer
Execute the installer using the ISPFLIB data set and one of the following methods:
Edit the ISPFLIB data set listed in ISPF option 3.4 (DSLIST), locate the SSLSETUP member, type ex next to SSLSETUP, then press Enter.
- From an ISPF command line, enter: TSO EX 'SQDATA.V4nnnn.ISPFLIB(SSLSETUP)'
-
The Installer Main Menu
The Connect CDC (SQData) Installer main menu displays the steps required to unload the product libraries and prepare SQDATA to run in your environment.
------------------- SQData z/OS Installation ------------------ Command ===> Install product libraries. Select each option in order. Status _ Unterse distribution data sets Not run _ Link load modules Not run _ Bind DB2 packages Not run Define the daemon. _ Create UNIX directories Not run _ Create Daemon Agents and ACL files Not run Generate SAMPLE jobs for planning. _ Create Started Task and Admin userids (SAMPLE) Not run _ Create System Logger LogStreams (SAMPLE) Not run Select an option to continue or F1 for help or F3 to return.
For the initial CDC installation, all steps must be completed in order.- Complete the steps in the Install product libraries section to install the SQDATA data sets, link the SQDATA load modules, and Bind the SQDATA DB2 package.
- Complete the steps in the Define the daemon section to create the UNIX (OMVS) sample files that define a listener daemon.
- The final two options Generate SAMPLE jobs to review with your systems and security staff. Resource planning, additional customization, and special authorization is usually required to complete these steps.
- To apply maintenance or upgrade to a new version, only the steps in the first section are required.
-
Install the product libraries
Complete the steps in this section to:
- Unpack the Connect CDC (SQData) distribution data sets
- Link the Connect CDC (SQData) load modules
- Bind the Connect CDC (SQData) DB2 package
Unpack the distribution data setsTab to the Unterse distribution data sets option, type s and press Enter.Confirm the names of the input and output data sets. Input data sets are the product distribution libraries in Terse format. They will be unpacked into the output data sets shown on the panel.------------------- SQData z/OS Installation ------------------ Command ===> Specify data set names (from/to): DBRM: SQDATA.V40030.DBRMLIB.TERSE to: SQDATA.V40030.DBRMLIB CNTL SQDATA.V40030.CNTL.TERSE to: SQDATA.V40030.CNTL PARMLIB SQDATA.V40030.PARMLIB.TERSE to: SQDATA.V40030.PARMLIB PROCLIB SQDATA.V40030.PROCLIB.TERSE to: SQDATA.V40030.PROCLIB SAMPLIB SQDATA.V40030.SAMPLIB.TERSE to: SQDATA.V40030.SAMPLIB PGMOBJ SQDATA.V40030.PGMOBJ.TERSE to: SQDATA.V40030.PGMOBJ Press ENTER to continue or F1 for help or F3 to return.
Note:- The default names are derived from the ISPF installation dialog data set name. Therefore, you must change the names as necessary for your environment.
- Only the input data sets must already exist. The output data sets must not exist since they are created by the unpack job.
- It is possible to override both the input and output names if required.
- The file names will be verified, input files that they exist, and the opposite for output files.
- The installation cannot proceed if errors are found. A pop-up window will appear for each error.
Confirm or correct the names of new data sets that are created by the unpack job.Press Enter to continue to the next panel.------------------- SQData z/OS Installation ------------------ Command ===> Specify data set names (create new) FAILJCL SQDATA.V40030.FAILJCL LOADLIB SQDATA.V40030.LOADLIB SMS Storage Class for new data sets (Optional): STORCLAS <Confirm>__ Press ENTER to continue or F1 for help or F3 to return.
Note:- These data sets must not already exist.
- The default names are derived from the ISPF installation dialog data set name. Therefore, change the names as necessary for your environment.
-
Confirm the STORCLAS because the size of the PGMOBJ Library may exceed system defaults. While the size of the Tersed file is approximately 70 MB you should anticipate the untersed file may take over 400 Cylinders and the LOADLIB created by the subsequent Link Job more than 100 Cylinders.
File name Contents Tersed File Size SQDATA.ZOS.V4nnnn.PBMOBJ.TERSE Object modules for the Base Product 70 MB Confirm or correct the names of new data sets.Press Enter to continue.At this point a job is built with all names and file sizes, etc., and is prepared for submission. This will define each output file and execute the terse steps. You should review and verify that the generated JCL and parameters are correct.
Type SUBMIT on the command line and press ENTER to run the job, confirm that it was successful before continuing.Link the Load ModulesTab to the Link Connect CDC SQData load modules option, type s and press Enter.------------------ SQData z/OS Installation ------------------ Command ===> The following data set names must be completed and valid. CDC Object Lib.....: SQDATA.V40030.PGMOBJ CDC Load Lib.......: SQDATA.V40030.LOADLIB CDC Proc Lib.......: SQDATA.V40030.PROCLIB LE Runtime Lib.....: CEE.SCEELKED CSS Runtime Lib....: SYS1.CSSLIB Link List Lib......: SYS1.LINKLIB TCP/IP Runtime Lib.: TCPIP.SEZACMTX USS Rexx Exec LIb..: SYS1.SBPXEXEC The following are optional. Erase name if not required. CICS Loadlib.......: CICSTS54.CICS.SDFHLOAD CICS Excilib.......: CICSTS54.CICS.SDFHEXCI IMS Reslib.........: IMS15.IMSTG1.SDFSRESL DB2 Loadlib........: DSNCC10.SDSNLOAD Press ENTER to continue or F1 for help or F3 to return.
Note:- The data set names displayed are referenced in subsequent installation jobs.
The system data set names displayed on this panel are generic and may not be correct for your environment. Therefore, you should change the name to suit your system requirements.
- The files in the first group are mandatory.
The second group of files are optional, depending on the features that you plan to use. If for example, the current site only has DB2, then you can erase the CICS and IMS file name and only DB2 will be linked.
Press Enter to continue.At this point a job is built to link all of the Load Modules. You should review and verify that the generated JCL and parameters are correct.
Type SUBMIT on the command line and press ENTER to run the job, confirm that it was successful before continuing.
Bind the Db2 PackageTab to the Bind CDC DB2 package option, type s and press Enter.------------------- SQData z/OS Installation ------------------ Command ===> Install product libraries. Select each option in order. Status .------------------------ *** DB2 Bind *** ---------------------. | | | DBRM Library..: WWCDKR.SQDCDC.DBRMLIB.Vnnnnn | S | | | DB2 Loadlib...: DSNCC10.SDSNLOAD | Defi | DB2 SSID......: DBCG | | | | Press F1 for help or ENTER to continue. | | | '---------------------------------------------------------------' Generate SAMPLE jobs for planning. Create Started Task and Admin userids (SAMPLE) Not run Create System Logger LogStreams (SAMPLE) Not run
Note:- Specify the name of the data set that contains the DBRM modules (DB2 Database Request Module).
Specify the subsystem ID and load library of the DB2 to Bind the CDC DB2 package to.
- The permissions required by the Bind Job may require intervention.
Press Enter to continue.At this point a job is built to Bind the Db2 Package. You should review and verify that the generated JCL and parameters are correct.
Type SUBMIT on the command line and press ENTER to run the job, confirm that it was successful before continuing.
-
Define the Listener Daemon
Complete the steps in the "Define the daemon" section to create sample files that define a listener daemon.Create UNIX directoriesTab to the Create UNIX directories option, type s and press Enter.
Specify the starting path name and permission mask for the SQDATA UNIX files and directories. The maximum length of the starting path name is 56 characters.
- The permission mask consists of three octal digits to define owner, group, and world access.
------------------- SQData z/OS Installation ------------------ Command ===> Specify the UNIX directory path name Directory: /u/<SQDATA_user>/ Permissions: 755 Press ENTER to continue or F1 for help or F3 to return.
Note: You may want to confirm the User_ID to be used for execution of the product.
Press Enter to continue.At this point a job is built to create the OMVS directory structure. You should review and verify that the generated JCL and parameters are correct.
Type SUBMIT on the command line and press ENTER to run the job, confirm that it was successful before continuing.
Create Daemon Agents and ACL Files
Tab to the Create Daemon Agents and ACL files option, type s and press Enter.
If the UNIX directory path and file permission were provided on the Create UNIX File System Directories panel, that information will be used again for the Create Daemon Agents and ACL files option.
However, if you skip the Create UNIX directories option and proceed directly to the Create Daemon Agents and ACL files option, which you might do if the UNIX directories already exist, you will be prompted for that information on the same Create File System Directories panel used for UNIX directories.------------------- SQData z/OS Installation ------------------ Command ===> Specify the UNIX directory path name Directory: /u/home/ Permissions: 755 Press ENTER to continue or F1 for help or F3 to return.
Press Enter to continue.
At this point a job is built to create the OMVS directory structure. You should review and verify that the generated JCL and parameters are correct.
Type SUBMIT on the command line and press ENTER to run the job, confirm that it was successful before continuing.
-
Generate Sample Jobs for planning
The final two options on the main menu generate SAMPLE jobs to review with your systems and security staff. Resource planning, additional customization, and special authorization is usually required to complete these steps.
Create Started Task and Admin Userids
This panel collects information used to generate a sample RACF command job to define userids for a capture task, a daemon, and a product administrator. It is not intended to be submitted as-is and must be modified to conform to your security environment.
Security requirements should be discussed with your RACF administrator. The sample definitions generated in this step can help to facilitate that discussion.------------------- SQData z/OS Installation ------------------ Command ===> Verify/Modify the following names: DB2 Capture Agent.......: CDCDB2C z/OS Listener Daemon....: CDDAEMON Administrative User.....: WWCDKR Owner...................: SYS1 Default Group...........: START2 Additional Connect Group: SYS1 Contact.................: Your name here? Press ENTER to continue or F1 for help or F3 to return.
Press Enter to continue.
At this point a job is built to create the OMVS directory structure. You should review and verify that the generated JCL and parameters are correct.
Make a note of the Member created ISPFLIB(SSLJRACF) because you may not have adequate permissions to run this job, which is required before you will be able to execute a Capture.
Create System Logger LogStream
Specify the name of the System Logger LogStream for the CDC publisher. The maximum length is 26 characters. This step is necessary for the VSAM or IMS capture. It is not required for DB2.
Discuss System Logger requirements with your coupling facility resource owners and systems programming staff.
The generated sample job is not intended to be submitted as-is. Special authority is required to update and activate a CFRM policy when using structure-based log streams, and to define log streams in the LOGR policy.------------------- SQData z/OS Installation ------------------ .--------------------- *** LogStream name *** ---------------------. | | | Enter the name of the log stream for VSAM or IMS capture. | | Omit this step for DB2. | | | | LogStream name: CDC.LOG | | | | | | Press ENTER to continue or F1 for help. | | | '-------------------------------------------------------------------'
Press Enter to continue.
At this point a job is built to create a z/OS System Logger LogStream. You should review and verify that the generated JCL and parameters are correct.
Make a note of the Member created ISPFLIB(SSLJIXCM) because you may not have adequate permissions to run this job, which is required before you will be able to execute a VSAM or IMS capture.
-
APF Authorize the Load Library
Important: The SQD LOADLIB must be APF authorized. Initially, this can be done via the operator’s console via the SETPROG APF command.
The list of currently APF authorized files can be viewed using the z/OS ISPF/SDSF facility. First, enter "/D PROG, APF" at the SDSF command prompt to generate the list. Next, enter "LOG" at the SDSF command prompt, scroll to the bottom of the log to display the results of the previous command and then back up and to the right to view the complete listing of the command.
Make sure that the APF authorization is made a permanent part of the IPL APF authorization procedure prior to attempting to run Connect CDC SQData.
The Connect CDC (SQData) uses an ISPF Installer included in the ISPFLIB_TERSE distribution file.