A basic question on concatenation sets:
My inventory has COBOL subroutines that are shared across applications.
Hence, to avoid duplications, these subroutines were added to a concatenation set.
1. Scanning of the inventory was successful.
2. But, the subroutines are not listed under 'Programs', when this was done.
(When they were added as a part of the source library, we were able to see this.)
3. Also, Impact analysis was not able to identify sub-routines in concatenation set.
(When sub-routines were added as a part of source library, the IA was able to identify impact to sub-routines.)
Q1. What type of components should go into concatenation sets & what should not?
Q2. How different are the objects in concatenation sets treated by RAA - as opposed to the source library (COBOL, JCL) components? Will this impact the count of programs , procs, jcls shown by RAA?
Q3. What other alternatives would you suggest - to scan subroutines while also avoiding duplicate files \ PROGRAM-ID issues?
Pl advise. Thanks in advance.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2012-12-21T10:51:41Z by SystemAdmin
Pinned topic Subroutines - candidates for concatenation sets?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-21T10:51:41Z at 2012-12-21T10:51:41Z by SystemAdmin
jcdelmo 0600012HN8343 PostsACCEPTED ANSWER
Re: Subroutines - candidates for concatenation sets?2012-12-18T15:38:42Z in response to SystemAdminIt appears, to me, that there is a misunderstanding of what a concatenation set is. They are used to simulate SYSLIB (for z/OS) or INCLUDE paths on workstation. They have nothing to do with finding COBOL subroutines (ie CALL, XCTL, LINK, resolution).
Q1) The only components that can go into a concatenation set are container names (ie, where to look for COPY, SQL INCLUDE, ++INCLUDE, -INC members)
Q2) The concatenation sets are only used by the COBOL/PLI scanners to resolve include members, they do not affect counts.
Q3) I do not understand the question. The CALL resolution is done after scanning and resolves subroutines within the same SITE.
Can describe the issue you are having with subroutines?
SystemAdmin 110000D4XK849 PostsACCEPTED ANSWER
Re: Subroutines - candidates for concatenation sets?2012-12-21T10:51:41Z in response to jcdelmoThank you, jcdelmo.
On Q3, a single instance of the subroutines can be loaded (one instance per site), and calls to this routines by programs under multiple applications (within the same site) will be resolved without any missing component errors. Is that what you were saying?