Source members no longer being shipped with the next IDMS

Discussion created by ca.portal.admin on Jul 22, 2010
release currently referred to as release 18

We are sending this email to let everyone know that in our current plans
for CA IDMS r18 there are several source members that we longer plan on
shipping. We would like to hear from you if you believe this is going
to cause you any problems. Please understand that these are our plans
currently and are subject to change. =20



List of members:










With respect to IDMSINTL. We have enhanced IDMSINTL to provide a new
""OPTIXIT"" for dynamic routing of requests.
IDMS 3rd-party providers forum


Update To: Source members no longer being shipped with the next IDMS release currently referred to as release 18
"I just wanted to update this message to address some of the questions
and concerns raised by the original message below.

All of the macros listed below will be delivered in Release 18. The
macros will be invoked using the same parameters as earlier releases
with minor exceptions. The main difference is that these macros will
generate almost no executable code. Instead each macro will generate an
option table that will be linked with a small stub module. The
resultant stub load module will contain only enough executable code to
pass the options to a common load module where essentially all of the
executable code will reside. No source will be distributed for the
common module.

This will change the installation procedure somewhat for release 18, but
it will deliver a major benefit for subsequent updates. Because the
common load module is separated from the stub load module, you will
almost never need to regenerate the options table nor relink your stub
load module when you apply maintenance. When you apply maintenance via
SMP/E or MSM, only the common module will ever be updated. The stub
load module containing your options table and stub module will not need
to change unless you choose to implement a newly introduced feature that
uses a new macro parameter.

Note also that any exits that were supported in earlier releases will
continue to be supported in release 18. Such exits will be linked with
your stub load module. We are considering the possibility of
introducing new exits for a few of the interfaces used with the macros
below. This would be done to accommodate those sites that have actually
modified the executable code in one of these macros to provide
additional functionality beyond that provided by the CA-supplied macros.

A few of you have already responded that you do modify executable code
in these macros. We will be contacting you directly to try to determine
how best to meet your business needs. If you do not hear from us in the
next week and are still concerned that your site may be adversely
affected, please contact John or myself directly at
or .