After upgrading Date Simulator from release 2.0 to release 3.0, a date Simulator batch job fails with message WARP011I: SECURITY VIOLATION.
Z/OS
The site is using a custom security exit load module WARPSCTY. By default Date Simulator does not ship with a security exit. Custom security exits are the responsibility of the customer to create and maintain.
The security exit can be turned off by renaming load module WARPSCTY in the Date Simulator APF authorized load library HLQ.CTWAAUTH. For the changes to take effect, the Date Simulator started task WARPMAIN must be recycled.
The client updated the custom security exit WARPSCTY source code.
For additional information, please review the Date Simulator release 3.0 documentation. See topics Security Exits and Activate a Security Exit.