-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running code pal for ABAP with user parameter SATC_CI_MODE set to "X". #242
Comments
I definitly miss some guidance what to use here. |
It basically changes the ATC mode from CHECKMAN to CODE INSPECTOR. For instance, if you call the
Unfortunately, we haven't found a way to run both simultaneously yet. :( Ps: If you are an SAP employee, you can use the SUT framework in the SAP systems to inspect the code. It allows you to set the ATC mode on each execution with no dependency on the user flag. |
Technically, it is the way that the ATC tool works. You can choose between CHECKMAN and CODE INSPECTOR. As code pal is a tool that uses the CODE INSPECTOR as its framework, it depends on this customizing. |
SATC_CI_MODE is a parameter that is only relevant in certain SAP-internal systems. As an open tool, this tool should not do anything specific for SAP-internal system - the internal systems need to use ATC in CI mode by default if they want to use this like everyone else. The "CHECKMAN" choice has never been delivered outside of SAP. |
@D072189 so step 4 of the how-to-install.md does not need to be done outside of SAP, right? Anything else which is different from the current how-to guides outside of SAP? |
Indeed, step 4 is not necessary in non-SAP systems (and really should never have been part of public-facing documentation). We'll have to review the rest of documentation for more things of this kind (tracked now in #557), but I haven't seen any at a first glance |
PROBLEM: (problem described by one of our users):
For Code Pal, we have to set user parameter SATC_CI_MODE to X. However, this seems to cause conflict when looking up ATC issues from our consolidations system. Is it a known issue? How should we deal with that so that both Code Pal and proper ATC issues show up in our dev system?
SOLUTION
Setting this user parameter SATC_CI_MODE = X means that the Code Inspector Mode is activated,
Furthermore, it means you have to use then "Code Inspector" and catching the results via ATC is no longer possible.
One has to decide: The parameter is a switch between working with CI or ATC (for getting the results).
Maybe we need do discuss all possible ways of executing the code pal:
The text was updated successfully, but these errors were encountered: