Is there a best practice for sharing Language Definitions?
![]()
Posting on behalf of a customer. I am bit naive on the z side of things.
The team is trying to set up a Language Definition "Assembler" in their project area. They are receiving the following error -
"CRJZZ0212E Language Definition x in project area y already specifies the file extension z", it explains it as "The file extension you specified is already in use by another language definition in the repository." and suggests "Change or remove the file extension and try again. Alternatively, remove the file extension from the language definition in which it is already specified, then try your save again."
So it appears that someone else has already defined a language that uses the file extension ".asm" but the user is unable to see/list what language definitions are already defined.
|
Accepted answer
![]()
Hi Neil,
the System Definitions are repository wide, that's why you are seeing that collision. For the users to see these already existing definitions you have to make sure that the project area in which they reside is accessible from the project areas that will use them: read access to the project is granted. Generally speaking, if you define a project area as the one where System Defintions will be maintained, it will ease the administration. The rest of project areas will just make use of these definitions. You can see this approach in the RTCEE Build Admin Workshop. Hope this helps. Regards, Jorge. Neil Plantan selected this answer as the correct answer
Comments What if we do not want to share definition? How do we work around the problem? separate repositories? thank=you
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
How to share the Language definition in one project area to other project area in one RTC instance ?
In this case, this RTC instance is shared between two teams. One team has defined the PL/1 definition in their RTC project area. 2nd project area is created for the new team. This new team is not able to see the existing PL/1 definition and also not able to use the definition used by the existing team.
How to share the Language definitions among the project areas in a RTC instance ? or how each team can define their Language definitions without getting the error ""CRJZZ0212E Language Definition x in project area y already specifies the file extension z"