Behavior of BuildUtilities.isCICS (and others) method

[mhardin18]

I came across an issue today with a client where the LogicalFile.isCICS() method is correctly returning true based on what I know it to scan for. However, this client needed the member to not be recognized as a CICS program which this flag drives the behavior of in zApp.
(Don't ask me the specifics of why this needed to happen, I'm not a CICS programmer)

So my first thought was to just use the file property override setting isCICS to false. But this does not work.

Looking at the code
`

• isCICS - tests to see if the program is a CICS program. If the logical file is false, then

• check to see if there is a file property.
  */
  def isCICS(LogicalFile logicalFile) {
  boolean isCICS = logicalFile.isCICS()
  if (!isCICS) {
  String cicsFlag = props.getFileProperty('isCICS', logicalFile.getFile())
  if (cicsFlag)
  isCICS = cicsFlag.toBoolean()
  }

  return isCICS
  }
  `

This method is only one directional. You can only override the property isCICS to be true if the LogicalFile returns false.

Why is this and the other is??? methods only one directional and not bidirectional?

[mhardin18]

My short term solution was to rewrite the method to allow for bidirectional property override.
I could have probably solved the issue with a language definition as well, setting whatever needed to be done for the compile. But overriding the property is much simpler and in this case, seems warranted.

However, depending on the answer to this, I may change my approach.

@dennis-behm
@M-DLB