Please note that the SQL Anywhere software that was installed with SAP/Sybase PowerBuilder is a Developer edition. It cannot be used with deployed applications. The only deployment license that ever was included with PowerBuilder was the Runtime Edition. It was name rtengX.dll where X is the major version of SQL Anywhere. The Runtime Edition was deprecated some time ago.
You can continue to use SQL Anywhere 12 (albeit it has been end of maintenance for some time) subject to your licensing. For example, you may continue to use the SQL Anywhere 12 Developer Edition with PowerBuilder 2017 for development work.
If you simply want to continue to use SQL Anywhere 12, access to historical software updates remain on the SAP Software Downloads site under Archived Products. Updates can be applied to all Editions including an active Trial Edition.
If you want to move to a newer Developer edition, please visit SQL Anywhere Developer Edition. This edition is a full feature product except that it cannot be used in production. It will have features and capabilities that may not be available is all production licenses. For example, High Available is not available in the Workplace license but is available in the Developer Edition.
There is also a limited time Trial Edition. The Trial Edition is no longer made available as a separate download. If you install without a registration key (you will be supplied a key for the Developer Edition), the software defaults to the Trial Edition which I believe is a 60 day period.
Thanks, your reply helped: after I'd added the 32bit version of SQLAnywhere via PB12.5 installer, PB2017R3 setup wizard listed the 64bit (!) version and I was able to select it. After installation I connected to PB Demo DB from PB2017 and the 64bit SQLAnywere engine started successfully. Chris, to me it looks like an obvious glitch in the Setup program, but do you think I need to mark your reply as Answer for the same of the forum?
Best regards,
Konstantin
Yes, it sounds like a bit of a "hole" in the installer that checks for installed instances of SA but not whether both bitnesses of the SA "DB Client" have been installed. Even the pre-installation section within the PB Install section of PB documentation does not seem to address the bitness requirements either.
FYI: https://www.appeon.com/support/documents/appeon_online_help/pb2017r3/installation_guide_for_pb/ch03s03.html
Regards ... Chris