ACF2/IMS interface no messages produced for OTMA and APPC transaction violations
search cancel

ACF2/IMS interface no messages produced for OTMA and APPC transaction violations

book

Article ID: 252645

calendar_today

Updated On:

Products

ACF2 - z/OS ACF2 ACF2 - MISC

Issue/Introduction

The documentation states that the internal IMS SAF interface is used for transactions generated from APPC and OTMA sessions

When a transaction authorization violation occurs there is no message sent to joblog/syslog as there is with the 3270 interface.

How to produce these messages to the Joblog and the Syslog?

 

Environment

ACF2 Release : 16.0

IMS Release : 15.2

Resolution

For violations to go through the ACF2 IMS interface for the validation:

  • Set OTMASE=N and APPCSE=N so that only the ACF2/IMS interface will validate the resources. This should then allow for violation messages to be issued.

  • Add a network record for APPC and for OTMA for the ACF2/IMS network records to allow messages to be returned.

  • Have both the SAF and the network related calls as referenced in technical documents OTMA Security and APPC Security

If there are any exits defined to perform site defined processing for IMS AUTH calls, verify that the site code is not impacting the message output.