This page attempts to answer some of the most frequently asked questions about upgrading to Version 6 or 7 of CoolSpools.
If you are running an earlier version of any software licensed from ariadne, please read these notes carefully before attempting to migrate to Version 6 or 7.
Basically, CoolSpools Version 6 or 7 replaces CoolSpools PLUS V5.
The different modules which used to make up CoolSpools PLUS V5 (CoolSpools, Slipstream, CommuniquÃ© and CoolTools) are still available, they just now been given different names and re-packaged as product options of CoolSpools Version 6/7.
|CoolSpools V6 – TABLE A|
|Product name||Product ID||Product name||Product ID||Product Option|
|CoolSpools PLUS||5COOLSP V5R1M0||CoolSpools V6||6COOLSP V6R1M0||All product options listed below|
|CoolSpools||5CVTSPL V5R1M0||CoolSpools V6||6COOLSP V6R1M0||Option 1 – Spool Converter|
|CommuniquÃ©||1CMNQUE V1R1M0||CoolSpools V6||6COOLSP V6R1M0||Option 2 – Email|
|CoolTools||2SPLTLS V2R1M0||CoolSpools V6||6COOLSP V6R1M0||Option 3 – Spool Admin|
|Slipstream||4STMEXP V4R1M0||CoolSpools V6||6COOLSP V6R1M0||Option 4 – Database|
|CoolSpools V7 – TABLE B|
|Product name||Product ID||Product name||Product ID||Product Option|
|CoolSpools PLUS||5COOLSP V5R1M0||CoolSpools V7||7COOLSP V7R1M0||All product options listed below|
|CoolSpools||5CVTSPL V5R1M0||CoolSpools V7||7COOLSP V7R1M0||Option 1 – Spool Converter|
|CommuniquÃ©||1CMNQUE V1R1M0||CoolSpools V7||7COOLSP V7R1M0||Option 2 – Email|
|CoolTools||2SPLTLS V2R1M0||CoolSpools V7||7COOLSP V7R1M0||Option 3 – Spool Admin|
|Slipstream||4STMEXP V4R1M0||CoolSpools V7||7COOLSP V7R1M0||Option 4 – Database|
So, if you are a Slipstream customer, don’t worry, you are not being forced to buy the full CoolSpools suite if you don’t want to. All of the great functionality you had before from Slipstream is still available, plus more besides, but now Slipstream has a new name: CoolSpools Database .
The minimum OS/400 release for Version 6 is OS/400 V5R3M0 and for Version 7 is OS/400 V6R1M0. If you are running OS/400 V5R2M0 or any earlier version of OS/400, you will not be able to install Version 6/7.
If you are running OS/400 V6 or OS/400 V7, either CoolSpools Version 6/7 will install and run without problems on these releases. The CoolSpools version does not have to mirror the OS version,for example CoolSpools V7 will run on OS/400 V6. No special version is required .
Whilst all earlier versions of CoolSpools PLUS, CoolSpools, Slipstream, CommuniquÃ© and CoolTools were also compatible with OS/400 V6 and OS/400 V7 so there is no obligation to upgrade to Version 6/7 of CoolSpools simply because you are upgrading OS/400 to one of those releases. However, please note that October 31st 2014 was the end of support date for the earlier versions and licence keys are no longer available for earlier versions.
you are entitled to upgrade free of charge to the corresponding replacement product shown in Tables A/B above.
It doesn’t. Prices for both licenses and support/maintenance are unchanged. You pay exactly the same for the equivalent functionality in the new version as you did before.
We have stipulated that customers are expected to purchase a separate licence for each logical partition (LPAR) for several years now. Discounts have been available for licences for partitions after the first on already licensed systems.
Prior to this new release this policy was not enforceable because our licence keys were not specific to an LPAR, but that has now changed. Licence keys for V6/7 are tied to the partition number as well as the serial number. This means that the licence key we give you for LPAR 1 will not work in LPAR 2 and so on.
If you have fewer licences that the number of partitions you wish to run Version 6/7 on, for whatever reason, please contact us and we will try to resolve the situation in a way that is acceptable to both parties.
Since the licence key is tied to the LPAR number, it is also very important that you notify us accurately of the LPAR number you wish to licence when asking us for a licence key. You can use CoolSpools V6/7’s DSPPRDINF (Display Product Information) command to view the serial number and LPAR number we need.
If you wish to install Version 6 or 7, you just download the software and install it following the instructions linked to there for your chosen installation method.
Yes, you’ll need a licence key for each product option you want to use.
The software will run for 30 days without a licence key when first installed, but you can email firstname.lastname@example.org at any time and ask for temporary license keys, or, if you meet the upgrade requirements shown above, you can just ask for your permanent licence keys.
When requesting licence keys, please quote:
Starting with CoolSpools V6, you’ll also need a support key if you want to install fix packs (PTFs). The support key validates your support and maintenance with Ariadne and your eligibility to install fixes. If you have current support and maintenance with Ariadne, you will be sent a support key along with your licence keys for V6/7 and a new support key will be emailed to you every time you renew your support and maintenance. You should use the SAVSUPKEY (Save Support Key) command to save the support key on the system so you don’t have to remember it and key it in when you come to install fixes.
Refer to the Maintenance Guide for further details.
Yes. CoolSpools Version 6/7 is a separate licensed program (6COOLSP / 7COOLSP) from all of the previous products and installs into a separate product library. This means that you can install it on the same system as any of the products it replaces without affecting the functioning of that earlier product.
This makes it entirely possible to test Version 6/7 before using it for your live applications. You can switch an application from using one version to using another simply by changing the library list of the job to include the appropriate version library or by specifying a different library name when you run your commands. Hence it is quite a simple matter to test your applications using the new version while continuing to run the older version in production until you are confident the new version gives the same results as before.
There are some special considerations for testing CoolSpools Spool Admin alongside CoolTools or CoolSpools PLUS on the same machine. See the Version 6 Memo To Users for details or See the Version 7 Memo To Users.
We recommend strongly that all production applications are re-tested thoroughly using the new version in your development environment before you switch over to running the new version live in your production environment.
Please note that while ariadne makes every effort to ensure that CoolSpools functions in the same way with the same parameters from one version to the next, it is not possible to guarantee this. This is why you should re-test your applications against a new version before going live with. Make sure you check your output is correct as well as testing that jobs run to completion normally.
ariadne software accepts no responsibility for any damage, expense or loss of income incurred as a result of unforeseen and unwanted effects resulting from installing new versions of its software or applying PTFs.
Yes. We try really hard to keep these to a minimum but sometimes it’s unavoidable.
Before going live, you must make sure that you have taken into account the changes specified in the Version 6 Memo To Users and Version 7 Memo To Users and have made any modifications to your code that these require.
There are utilities (IMPEMLDTA – Import Email Data – and IMPADMDTA – Import Spool Admin Data) to assist with migrating setup and log information from the old systems to the new. See the Version 6 Memo To Users for details or Version 7 Memo To Users for details.
All product options of CoolSpools V6 or CoolSpools V7 install into the single version specific product library COOLSPV6R1 or COOLSPV7R1. This means that you no longer have to manage multiple product libraries for the separate modules that made up CoolSpools PLUS V5R1M0 (Slipstream, CommuniquÃ©, CoolSpools etc.)
You will probably need to change library lists in job descriptions and other system objects in order to pick up the new version of the code rather than the old.
This change of library name has the advantage that it allows you to run both V6 / V7 and the earlier versions on the same machine. You are therefore able to test V6 / V7 before swapping your production applications over to the new version, as we strongly advise you to do.