How to install DATACOM SQL option in an existing Datacom 11.0 z/VSE environment?
Datacom
Before you start the SQL product installation find out how large the z/VSE partition is where the Multi-User is running and how much GETVIS is still free in this partition when all URTs have been opened in CICS. You can run z/VSE console command GETVIS xx where xx is the partition-id where the Multi-User is running to check out the LARGEST FREE size.
Adding SQL requires a minimum of 6M of GETVIS.
We recommend a minimum MUF partition size of 16M (depending on the number of buffers specified in the MUF startup 16M might be too small) for Datacom version 11.0 and for version 12.0 32M is recommended. Datacom SQL version 12.0 uses IBM C and requires more.
Check via CA? on the z/VSE console what version and service pack of Datacom you are running.
Of course you can also check message DB00215I when the MUF enables.
Example : DB00215I - Datacom/DB r11 at service pack: SP05
The service pack levels for DB and SQL need to be the same.
SQL requires system tables in areas MSG and SIT in DBID 015. Those areas were not created when you ran the Datacom/DB installation.
Our Datacom installation guide for z/VSE documents the steps to install SQL but nothing is mentioned about these needed system tables for SQL.
Define these 2 areas by running:
*** step one ***
Stop all activity on DBID 2 and 15.
*** step two - DEFINE SIT015 AND MSG015 (DBID015 FILE) ***
Run DDUPDATE using
-USR DATACOM-INSTALL,NEWUSER
-UPD DATABASE,DDD-DATABASE(PROD,DD)
1000 RESTORE,T001
-END
--- cards from attached DBID015.TXT file ---
*** step 3 - SET AND VERIFY ***
Run DDUPDATE using
-USR DATACOM-INSTALL,NEWUSER
-UPD DATABASE,DDD-DATABASE(T001,DD)
1000 SET
1000 VERIFY
-END
note that the VERIFY will give DDWKEY0013 SIGNED NUMERIC FIELD IN KEY but those messages are OK
*** step 4 - COPY THE DATABASE FROM T001 TO PROD ***
Run DDUPDATE using
-USR DATACOM-INSTALL,NEWUSER
-CPY DATABASE,DDD-DATABASE(T001,DD),PROD
*** step 5 - BUILD THE DDD-DATABASE ***
// ASSGN SYS023,DISK,VOL=xxxxxx,SHR
// DLBL DDCFBLD,'&D11PFX..CFMWORK',,SD
// EXTENT SYS023,xxxxxx,,,1,60
// EXEC DDCFBLD,SIZE=320K
-USR DATACOM-INSTALL,NEWUSER
-CXX BUILD,DATABASE,DDD-DATABASE(PROD,DD,PRIV)
*** step 6 - PERFORM CXXMAINT to update the CXX ***
// ASSGN SYSnnn,DISK,VOL=xxxxxx,SHR
// DLBL DDCFBLD,'&D11PFX..CFMWORK',,SD
// EXTENT SYSnnn,xxxxxx
// EXEC DBUTLTY,SIZE=512K
COMM OPTION=CLOSE,DBID=015
CXXMAINT OPTION=DDPROD,DEVICE=DISK,DTFNAME=DDCFBLD
*** step 7 - add files in Standard Labels ***
--- ADD THESE FILES TO standard labels ---
// DLBL SIT015,'&D11PFX..SIT015',9999,DA
// EXTENT SYSnnn,xxxxxx,1,0,????,400
// DLBL MSG015,'D&D11PFX..MSG015',9999,DA
// EXTENT SYSnnn,xxxxxx,1,0,????,250
--- END standard labels ADD ---
/*
*** step 8 initialize the new areas ***
Run DBUTLTY
INIT AREA=SIT,DBID=015
INIT AREA=MSG,DBID=015
LOAD AREA=SIT,DBID=015,FORMAT=NONE
LOAD AREA=MSG,DBID=015,FORMAT=NONE
/*
*** step 9 bounce the Multi-User ***
Shutdown and restart the MUF gracefully
Now follow the SQL installation steps as documented in the Datacom Installation Guide.
5.3.1 Datacom SQL Option
The external disk files are required for this option.
Retrieve member BEINS01S.Z from the CAI110.SAMPJCL library. Select the parameters for the SQL option and submit. The following members are produced.
BEINS04A.Z
BEINS14A.Z
BENEW05A.Z
BEIVP02.Z
BEIVP03.Z
After downloading the SQL product code from tape (or AWS) by running BEINS04A it is recommended to install all published PTFs on top of the service pack level that you are running. You can find them on CA Support Online - Datacom product page - click on Maintenance Grid for z/VSE.
Run BEINS14A and BENEW05A.
You have now installed SQL DBIDs 16 and 17.
Modify the Datacom Multi-User startup JCL by adding the DLBL/EXTENT cards for all areas in DBID 16 and 17 (or put them in Standard Labels) and add following MUF startup cards:
DATACOM SQL
SQLDEFAULT 16,CASQLDEFAULT
SQLOPTION YES,17,DATACOM,120,NO,NO
Start the Multi-User.
You should see message DB00212I - SQL ENVIRONMENT ESTABLISHED.
Now that you have the MUF enabled with SQL you can run the SQL installation verification job BEIVP02. BEIVP03 is optional.