i agree, Mike, i wouldn't discourage anyone from just trying it out. but even the simplest installation of Caché presents choices that have lots of significant implications, for example 8-bit vs. unicode and security settings. it doesn't add a lot of overhead to have the documentation open so you can read along with the procedure as you execute it, and at the least it may save you the trouble of having to uninstall and start over again.
thank you, Eric. i should have been more specific about the new file attribute command. internally we tend to focus on the most recent releases, i will remember next time that there are plenty of sites using older kits.
The Documentation that Eduard provided has all of the details for installing cache, but the simple answer, for someone looking for a quick tip is here:
We provide distribution packages available on our distribution page:
Login in with your wrc direct account and download the package that is the correct version you want, and that is correct for your operating system. The packages are named such that their version on os should be clear.
Windows: The package will be an executable like so:
Download this to a location on your system that is not in the pathway where you want to install. Double click and it will start the installation wizard. From there is will prompt with questions you answer about how you want to install cache. If you are not sure of some of those answers the document that Edward pointed out will have lots of answers. When the installation is complete there will be a blue cube on the dashboard from which you can access cache.
Unix and Mac: The package will be a zipped tar file like so:
When done it will expand several files that are part of the distribution. Start the installation script like so:
#./cinstall
It will prompt you with answers to questions about the install. If you have questions about this you can refer to the documentation that Edward posted. When done it will tell you the url to use to access the instance with the system management portal. You can use csession <instance name> to get into cache.
vms: This is similar in install to unix, but opening the kit up is a bit different. The package will be a bck file like so:
Note, you will have to put the appropriate disk and directory designation. The ... following the directory name is necessary so that it properly expands the directories. You will have to get into the directories that it creates to get to the cinstall executable. There type @cinstall in order to start the installation. Again it will prompt for answers just like with unix.
While this overview is accurate and helpful, I strongly recommend consulting the Caché Installation Guide before beginning the installation process, and having it at hand while installing.
OpenVMS note: the SET FILE/ATTRIB command cited by Richard, which may be necessary to restore to the install package attributes that were stripped when it was conveyed to the target system, was recently updated, as follows:
Bob, I fully agree with you about the more complete installation guide. However, for someone who is new, and does not understand the terms used, and just wants to see what Caché is all about on their own PC, I feel the more compact install guide may be a better fit. And if they have trouble or questions, they can always consult the more complete guide.
I just wanted to add some additional details re the $ set file/attrib command mentioned above for OpenVMS kits to clarify which command is the appropriate one to use and when.
In order to make the file sizes of the OpenVMS Caché kits smaller to save on storage space and speedup transfer times, from Caché version 2015.2.0 upwards we use the OpenVMS backup qualifier "/DATA_FORMAT=COMPRESS" which can make the kits around 50% smaller in size.
So for Caché versions prior to 2015.2.0 to set the correct file attributes use:
$ set file/attrib=(rfm:fix,lrl=32256)
and for versions of Caché from 2015.2.0 upwards use:
$ set file/attrib=(rfm:var,mrs:32256,lrl=32256,rat=none)
I hope you’re well and that you may not remember me from Systime field engineering 1980-1986 then ICM until 2007. You worked with Neil Turner & Brian Lindley I recall.
Could you drop me a line at meakin2003 at gmail.com or call me on 07802 491155 to discus some OVMS support work we’re about to undertake? It involves my working with Chris Walker whom you may recall adapted the Vax780 to address 4Mb before DEC released the 785? We need more guys like him and you right now.
Here's the documentation detailing the process.
Or do you have more specific questions?
i agree, Mike, i wouldn't discourage anyone from just trying it out. but even the simplest installation of Caché presents choices that have lots of significant implications, for example 8-bit vs. unicode and security settings. it doesn't add a lot of overhead to have the documentation open so you can read along with the procedure as you execute it, and at the least it may save you the trouble of having to uninstall and start over again.
thank you, Eric. i should have been more specific about the new file attribute command. internally we tend to focus on the most recent releases, i will remember next time that there are plenty of sites using older kits.
Adam,
you can download it directly from your WRC account.
For a simplified version, see NewBie's Corner Session 1
The Documentation that Eduard provided has all of the details for installing cache, but the simple answer, for someone looking for a quick tip is here:
We provide distribution packages available on our distribution page:
https://wrc.intersystems.com/wrc/Distribution.csp
Login in with your wrc direct account and download the package that is the correct version you want, and that is correct for your operating system. The packages are named such that their version on os should be clear.
Windows: The package will be an executable like so:
cache-2016.1.0.656.0-win_x64.exe
Download this to a location on your system that is not in the pathway where you want to install. Double click and it will start the installation wizard. From there is will prompt with questions you answer about how you want to install cache. If you are not sure of some of those answers the document that Edward pointed out will have lots of answers. When the installation is complete there will be a blue cube on the dashboard from which you can access cache.
Unix and Mac: The package will be a zipped tar file like so:
cache-2016.1.0.656.0-ppc64.tar.gz
Download and place in a pathway where you are not installing cache. Unzip this with:
#gunzip cache-2016.1.0.656.0-ppc64.tar.gz
then untar it like so:
#tar -xvf cache-2016.1.0.656.0-ppc64.tar
When done it will expand several files that are part of the distribution. Start the installation script like so:
#./cinstall
It will prompt you with answers to questions about the install. If you have questions about this you can refer to the documentation that Edward posted. When done it will tell you the url to use to access the instance with the system management portal. You can use csession <instance name> to get into cache.
vms: This is similar in install to unix, but opening the kit up is a bit different. The package will be a bck file like so:
cache-2016.1.0.657.0-alphavms.bck
Set the attributes of the file correctly so that it can be opened:
$ SET FILE/ATTRIB=(RFM:FIX,LRL=32256) cache-2016.1.0.657.0-alphavms.bck
expand the bck file like so:
backup cache-2016.1.0.657.0-alphavms.bck/save DISK:[dir...]
Note, you will have to put the appropriate disk and directory designation. The ... following the directory name is necessary so that it properly expands the directories. You will have to get into the directories that it creates to get to the cinstall executable. There type @cinstall in order to start the installation. Again it will prompt for answers just like with unix.
Hope this helps.
Please provide link for cache-2016.1.0.656.0-win_x86.exe
While this overview is accurate and helpful, I strongly recommend consulting the Caché Installation Guide before beginning the installation process, and having it at hand while installing.
There are a number of things to consider for each platform (Windows, OpenVMS, UNIX®/Linux, and Mac) before you install; the install guide covers general preparation in the chapter for each platform, and also includes appendixes on system parameters for OpenVMS and UNIX®/Linux, preparing for Caché security, and file system and storage recommendations. (There is also a chapter on upgrading Caché.)
There are also a lot of options to choose among during the installation process and it useful to have the explanations available when deciding.
Finally, the install guide offers alternatives to interactive installation, including unattended installation on Windows and on UNIX®/Linux systems and the use of the %Installer class with an installation manifest.
OpenVMS note: the SET FILE/ATTRIB command cited by Richard, which may be necessary to restore to the install package attributes that were stripped when it was conveyed to the target system, was recently updated, as follows:
Bob, I fully agree with you about the more complete installation guide. However, for someone who is new, and does not understand the terms used, and just wants to see what Caché is all about on their own PC, I feel the more compact install guide may be a better fit. And if they have trouble or questions, they can always consult the more complete guide.
I just wanted to add some additional details re the $ set file/attrib command mentioned above for OpenVMS kits to clarify which command is the appropriate one to use and when.
In order to make the file sizes of the OpenVMS Caché kits smaller to save on storage space and speedup transfer times, from Caché version 2015.2.0 upwards we use the OpenVMS backup qualifier "/DATA_FORMAT=COMPRESS" which can make the kits around 50% smaller in size.
So for Caché versions prior to 2015.2.0 to set the correct file attributes use:
$ set file/attrib=(rfm:fix,lrl=32256)
and for versions of Caché from 2015.2.0 upwards use:
$ set file/attrib=(rfm:var,mrs:32256,lrl=32256,rat=none)
Hi Eric,
I hope you’re well and that you may not remember me from Systime field engineering 1980-1986 then ICM until 2007. You worked with Neil Turner & Brian Lindley I recall.
Could you drop me a line at meakin2003 at gmail.com or call me on 07802 491155 to discus some OVMS support work we’re about to undertake? It involves my working with Chris Walker whom you may recall adapted the Vax780 to address 4Mb before DEC released the 785? We need more guys like him and you right now.
Many thanks
Colin.