CA Tuesday Tip: (CA IDMS) List of RHDCOPTF optional bit settings

[Edward Gorga]

CA IDMS Tuesday Tip by Edward Gorga, Principal Support Engineer for August 21, 2014

 

 

For a few releases now, most optional APARs are permanently coded into the CA IDMS software and are activated by use of a bit setting in the RHDCOPTF module. Say for example you want to activate  optional bit setting 47. You activate it by coding the following in the RHDCOPTF module:

 

       #DEFOPTF OPT00047

 

The whole module would look like this:

         TITLE 'RHDCOPTF - Optional APAR Bitmap Table'

         #DEFOPTF OPT00047

         #DEFOPTF TYPE=GENERATE

         END

 

The RHDCOPTF source is in the CUSTOM.SRCLIB library in member RHDCOPTF.

Sample JCL to assemble and link RHDCOPTF is in the CAGJSAMP library in member RHDCOPTF.

 

The optional bit settings are documented in the following informational PTFs.

 

For release 18.5 see  RI70658.

For release 18.0 see  RI29610.

For release 17.0 see  RI08751.

For release 16.0 see  QI53099.

[Chris Hoelscher]

I hope the following statements are tru concerning the bit table:

 

A given option # never changes between releases (in other words – for a given functionality, it should never be #81 in 18 and #116 in 18.5)

Obsolete option #s are never reused; new options are given new numbers at the end of the list

Including an obsolete option # would force an error (to help remind the technician that it IS obsolete and should be removed) – unless leaving an obsolete bit ON will have no adverse effect to the system ….

 

Chris hoelscher

Technology Architect | Database Infrastructure Services

Technology Solution Services

 

123 East Main Street |Louisville, KY 40202

[e-mail]

Humana.com

[phone] – office

[phone] - blackberry

Keeping CAS and Metavance safe for all HUMANAty

[Brian Brendlinger]

Chris,

  A given OPTnnnnn should never change.

  There are many bit numbers that show in the list as * NOT USED *, typically because a different method of specifying the option has been introduced, so it certainly appears we do not re-use numbers.

  You will not get an assembly error if you specify an obsolete OPTnnnnn.  It is a simple setting of a bit number that results from the #DEFOPTF macro assembly.  However, if it is listed as   * NOT USED * it means the check for this bit has been removed from the code so it should not have any adverse affect.

  You should review all Optional settings at least when you upgrade if not at some regular interval.

[Edward Gorga]

Thanks for the clarification Brian.