Previous Topic: Reviewing Processing Options

Next Topic: CA JARS Exits


Saving Dynamic Dictionaries

If the optional DD statement //CAIJSDCO is coded in the CA JARS JCL, CA JARS will always write the dictionary or dictionaries out at the end of run, in their final state.

CA recommends the input dictionary //CAIJSDCI be coded as a GDG. Then CA JARS will write only new or changed dictionaries to a new GDG generation.

CA JARS will use dynamic allocation to create a new GDG generation to which to write the changed dictionary, as illustrated in this flowchart:

A new generation will only be created if the in-storage dictionary has changed, or a new dictionary has been added. CA recommends the GDG-input, dynamically allocated output option as it is somewhat more efficient to only write output when changed.

Note: If the input CA JARS dictionary is on an SMS-controlled volume, CA JARS will allocate the output dictionary data set to the same STRCLASS. IF //CAIJSDCI is on a non-SMS volume, CA JARS will attempt to allocate //CAIJSDCO to the same volume: UNIT=3390,VOL=SER=(volser of CAIJSDCI).