Skip to end of metadata
Go to start of metadata

Purpose

Changes to jConnect output from sp_version

Overview

Changes in the installmaster affect the jConnect MDA script version showing from the sp_version command. This describes the change and when it changed.

Installmaster changes to sp_version for jConnect

A decision was made from engineering to change on the script number system. The only time number will change is when there is an update to the MDA scripts for jConnect.
When you run the installmaster on an ASE after an upgrade or if you build a new ASE. The installmaster will put the current version of the jConnect MDA scripts.
Here are a couple of tables so you can see what versions the changes were made in with the dates the files were made for the $sybase/ASE-***/scripts/installmaster and the $sybase/jConnect***/sp/sql_server16.0.sql.

 

ASE VersionDate of installmaster sp_versionSDK includedDate of sql_server16.xx.sqlsp_version
 16.0 SP03 PL08Feb 20 2020JDBC(TM)/1014 16.0 SP03 PL08Jan. 12, 2020JDBC(TM)/16.0 SP03 PL08
 16.0 SP03 PL07May 21 2019

JDBC(TM)/1014

16.0 SP03 PL07April 25, 2019JDBC(TM)/16.0 SP03 PL07 
16.0 SP03 PL06Sept. 25, 2018JDBC(TM)/101316.0 SP03 PL06Nov. 4, 2018JDBC(TM)/16.0 SP03 PL06
16.0 SP03 PL05May 10, 2018JDBC(TM)/101216.0 SP03 PL05July 16, 2018JDBC(TM)/16.0 SP03 PL05
16.0 SP03 PL04Feb. 7, 2018JDBC(TM)/101116.0 SP03 PL04April 11, 2018JDBC(TM)/16.0 SP03 PL04
16.0 SP03 PL03Aug. 28, 2017JDBC(TM)/101016.0 SP03 PL02 one-offAug. 28, 2017JDBC(TM)/16.0 SP03 PL02
16.0 SP03 PL02Aug. 28, 2017JDBC(TM)/101016.0 SP03 PL02Aug. 28, 2017JDBC(TM)/16.0 SP03 PL02
16.0 SP03 PL01Mar. 5, 2017JDBC(TM)/100916.0 SP 03 PL01July 10, 2017JDBC(TM)/16.0 SP03 PL01
16.0 SP03Mar. 5, 2017JDBC(TM)/1009 16.0 SP03May 7, 2017 JDBC(TM)/16.0 SP03
16.0 SP02 PL08Sept. 25, 2018JDBC(TM)/100816.0 SP02 PL08Nov. 22, 2018 JDBC(TM)/16.0 SP02 PL08
16.0 SP02 PL07July 24, 2017JDBC(TM)/100616.0 SP02 PL07Sep. 26, 2017 JDBC(TM)/16.0 SP02 PL07
16.0 SP02 PL06Sept. 21, 2016JDBC(TM)/100516.0 SP02 PL06Mar. 15, 2017 JDBC(TM)/16.0 SP02 PL06
16.0 SP02 PL05Sept. 21, 2016JDBC(TM)/100516.0 SP02 PL05Sep. 21, 2016 JDBC(TM)/16.0 SP02 PL05
16.0 SP02 PL04Apr. 24, 2016JDBC(TM)/100416.0 SP02 PL04May 12, 2016JDBC(TM)/16.0 SP02 PL04
16.0 SP02 PL03Sept. 13, 2015JDBC(TM)/100216.0 SP02 PL03Jan. 26, 2016JDBC(TM)/16.0 SP02 PL03
16.0 SP02 PL02Sept. 13, 2015JDBC(TM)/100216.0 SP02 PL02Oct. 9, 2015JDBC(TM)/16.0 SP02 PL02
16.0 SP02 PL01May 28, 2015JDBC(TM)/100116.0 SP02 PL01July 29, 2015JDBC(TM)/16.0 SP02
16.0 SP02May 28, 2015JDBC(TM)/100116.0 SP02 PL00July 29, 2015JDBC(TM)/16.0 SP02
16.0 SP01 PL03Sept. 13, 2015JDBC(TM)/100216.0 SP01 PL03Oct. 25, 2015JDBC(TM)/16.0 SP01 PL03
16.0 SP01 PL02May 28, 2015JDBC(TM)/100116.0 SP01 PL02May 21, 2015JDBC(TM)/16.0 SP01 PL02
16.0 SP01 PL01Nov. 12, 2014JDBC(TM)/16.0 PL 05 (Build 27151)16.0 SP01 PL01Jan. 23, 2015JDBC(TM)/16.0 SP01
16.0 SP00 PL05Nov. 12, 2014

JDBC(TM)/16.0 PL 05 (Build 27151)

16.0 SP00 PL05 

 

 ASE VersionDate of installmaster sp_version SDK includedDate of sql_server16.xx.sql sp_version
 15.7 SP141Sept. 25 2018 JDBC(TM)/1008 15.7 SP141

Mar. 12, 2019

 JDBC(TM)/7.0.7 SP141
 15.7 SP140Feb. 7, 2018JDBC(TM)/1007 15.7 SP140Apr. 26, 2018 JDBC(TM)/7.07 SP 140
 15.7 SP139July 24, 2017JDBC(TM)/1005 15.7 SP139July 27, 2017 JDBC(TM)/7.07 SP 139
 15.7 SP138Apr. 24 2016JDBC(TM)/1004 15.7 SP138Aug. 17, 2016 JDBC(TM)/7.07 SP 138
 15.7 SP137Apr. 24, 2016JDBC(TM)/1004 15.7 SP137Apr. 24, 2016 JDBC(TM)/7.07 SP 137
 15.7 SP136Sept. 13, 2015JDBC(TM)/1002 15.7 SP136Sep. 1, 2015 JDBC(TM)/7.07 SP 136
 15.7 SP135May 28, 2015JDBC(TM)/1001 15.7 SP135Mar. 26, 2015 JDBC(TM)/7.07 SP 133
 15.7 SP134Mar. 11, 2015JDBC(TM)/1000 15.7 SP134Mar. 26, 2015 JDBC(TM)/7.07 SP 133
 15.7 SP133Mar. 11, 2015JDBC(TM)/1000 15.7 SP133July 21, 2014 DBC(TM)/7.07 SP 130
 15.7 SP132July 19, 2014JDBC(TM)/7.07 SP 130 (Build 27074) 15.7 SP132July 21, 2014JDBC(TM)/7.07 SP 130

Changing the sp_version to the old naming

If the new naming coming from the ASE installmaster is confusing you, you can change it. Where the ASE resides look in the $Sybase/jConnect/sp folder. This is from the SDK piece that gets installed with the ASE. Pick the appropriate .sql for your ASE and run it. This will give you the old naming convention that is still part of the SDK install.

Related Documents

Software Developer Kit for ASE driver versions
Installing the MDA scripts for the drivers

 


__________________________________________________________________________________________________________

Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.

  • No labels