Which CA IPC VLS file can and cannot be shared?
Sharable and non Sharable VLS files
ADRTRC (not a VLS library) - Not sharable
ADROUT - Recommend separate ADROUTs with different SYSTEM and PREFIX names for each environment.
When ADROUT is shared, all outputs and defined printers are available to all of the environments. Also, there is a possibility of output contention (that is, users in two different environments cannot view the same output simultaneously). When ADROUT is not shared, different SYSTEM and PREFIX names must be defined in each environment. Refer to the article, "Things to Know About ADROUT Recovery", for complete details on changing the SYSTEM and PREFIX names in CA-Ideal.
ADRPNL - Not sharable if ADROUTs are unique (because PSS#OPTIONS resides in ADRPNL)
When ADRPNL is shared, the same site options are in effect for all of the environments. ADRPNL is not sharable if you have separate ADROUTs because the ADROUT options (member PSS#OPTIONS) reside in ADRPNL.
ADRLIB - Sharable (Note: Jobcards in effect for all CICS regions.)
When ADRLIB is shared, the same jobcards are in effect for all of the environments.
IDDAT - Sharable.
When IDDAT is shared, the same members are available in all of the environments.
IDDVW - Sharable ONLY in a shared dictionary environment.
DDOFILE and DDOFIL2 - Not sharable
DDOFILE and DDOFIL2 are DD work files and must be unique to each region. CICS could potentially be writing to the same member at the same time which could corrupt the VLS file.
MDUOLL is DDOL map panel file and can be shared.
- All Ideal environments that share the same dictionary and VLS source, object and panel libraries should have matching QCODES. (The QCODE parameter is maintained in SC00OPTS.)
- ADRPNL and ADROUT should be considered a SET -- the options for ADROUT are stored in ADRPNL. If you plan to have unique ADROUT data sets, be sure to maintain unique ADRPNL data sets.