More options in policy selection

Thank you for this RFE.

Unfortunately there was not enough information to allow us to effectively assess this requirement. In a previous comment we requested the information that would help us clarify key points, but this information has not been provided.

Regreably this means that we cannot effectively assess this requirement and so our only option is to declined it at this point. You are free to re-raise this requirement with the detail requested if you still want it to be considered.

Thank you for your response.

Unfortunately, it is still not clear why these use case could not be satisfied with the technology in the product today by using a default connection to a program that would process either:
a) no value - process as normal
b) invalid value - error response

The header value can be mapped to a field for the CICS program to process. The program in the default region would know if any work flowed to it with a value set that it must be an invalid value. Alternatively it could check if the value was valid and if not respond with an error.

So the use cases you described would work as follows:
- no value entered, this is a valid situation and we want it routed to a default CICS
Policy would not match and so the default connection would be used. The CICS program would see an empty value and so process as usual
- a specific and valid CICS, we want it routed to this specific CICS
Policy would match and so the specific connection would be used.
- a specific and invalid CICS, we want a way to send back an "error" message
Policy would not match and so the default connection would be used. The CICS program would see an invalid value and so produce an error response

If you could explain what specifically is missing from this solution that would help us to further evaluate this RFE

We would like to be able to address ALL the following cases :

- no value entered, this is a valid situation and we want it routed to a default CICS
- a specific and valid CICS, we want it routed to this specific CICS
- a specific and invalid CICS, we want a way to send back an "error" message

Thank you for this RFE.

Today we believe it is possible to achieve what you describe by specifying a policy rule with the list of valid values and then have the default value set either a dummy connection (which would implicitly fail) or a default connection to a CICS region with a program that would provide an error response. If you can tell us more about your use case, and specifically why the capability that is available in the product today is not sufficient, then we will be able to assess this RFE.