There have been two different methods for using the CA-IDMS SQL Option and CA-IDMS Server without the licence.
This document describes them both and their respective requirements and limitations.
CA IDMS, all supported releases.
1. Regardless of the means you decide to use to implement SQL and Server, you need to set up the database environment to support SQL.
Any dictionary containing network schemas against which you will want to perform SQL access, must have a catalog component segment in it.
The procedure to do this is described in general terms here: Defining New Dictionaries.
Alternatively, this can be done to APPLDICT (and SYSTEM if required) with the configuration jobs.
This is described here: Setup SQL Web Connect for z/OS - SQL Usage.
For more information on how to do this with the installation jobs, see KB000109289.
Even if your original install did not include the SQL option, a catalog segment called CATSYS will have been included in your SYSTEM dictionary.
If you want to be able to use SQL against schemas defined in the SYSTEM dictionary, you will also need to make the following changes to CATSYS.
You must DROP and re-CREATE CATSYS, but with the following attributes:
CATSYS must have FOR SQL and not FOR NONSQL.
Areas DDLCAT and DDLCATLOD must be "STAMP BY AREA".
Area DDLCATX must be "STAMP BY TABLE".
The DROP CATSYS command will remove it from any DMCLs which included it, so it must be re-added to those DMCLs.
2. Portfolio Simplification or SQL Web Connect?
You must determine whether you will use Portfolio Simplification or SQL Web Connect.
Portfolio Simplification offers full access to the CA-IDMS SQL Option and CA-IDMS/Server.
You must enable the following options in RHDCPINT:
Users on r18.5 will require LMP Keys for CA-IDMS SQL Option and CA-IDMS/Server but they can now be acquired free of charge.
Users on r19.0 can avoid the need for LMP Keys by applying APAR RO96807.
If for some reason you are unable to use Portfolio Simplification, you will need to use SQL Web Connect which limits you to two concurrent sessions of SQL and Server per LPAR.
Other limitations and requirements for SQL Web Connect are documented here: SQL Web Connect Considerations.
The RHDCPINT options are not required for SQL Web Connect.