IDMS JOB09 - What is SYSDIRL dictionary?
search cancel

IDMS JOB09 - What is SYSDIRL dictionary?


Article ID: 44833


Updated On:


IDMS IDMS - Database


IDMS configuration job JOB09 references the SYSDIRL dictionary. What is SYSDIRL and can it be shared across the CVs?




Release: All supported releases
Component: IDMS.


DIRLDML is the DDLDML dictionary area of the SYSDIRL dictionary. There should also be a SYSDIRL DDLDCLOD area, which usually resides in the segment SYSDIRL by default.
A DCMT D DBNAME on the SYSDIRL dbname entry shows:

        SEGMENT CATSYS                  0 BIND count
        SEGMENT SYSDIRL                 2 BIND count
        SEGMENT SYSMSG                  0 BIND count

SYSDIRL is an optional dictionary that is created and updated by default in installs and configurations. Some clients do not maintain a separate SYSDIRL dictionary and put the SYSDIRL contents into another existing dictionary. This is highly discouraged because subsequent upgrades will expect SYSDIRL to be present and problems will arise if it isn't.

Therefore, it is strongly recommended keeping SYSDIRL separate. 

JOB09 has the
same two IDMSDDDL steps that are used for all dictionaries, to add/update DLODDEFS and DLODPROT (common dictionary definitions and protocols for pre-processors).

The rest of the JOB09 SYSDIRL updates are to load the IDMS dictionary network schema source and all of the canned CULPRIT report source modules for all of the IDMS reports and the PERFMON report modules.

The network schema and the CULPRIT report modules take up a great deal of space so it makes sense to keep it in the separate SYSDIRL dictionary rather than clogging up the application dictionaries with the SYSDIRL content.

Since SYSDIRL only contains IDMS specific definitions, network schemas/subschemas and reports, this dictionary can be shared among CVs at the same release level.
Mixing release levels, meaning having a release 19.0 SYSDIRL in an 18.5 CV, could cause problems running reports that are not at the same release level. Some reports, specially the perfmon reports, are release specific so would report incorrect information if a different release report is used.