Definitions have been added to the ESFPARM to allow transformations to go through the Java Transformers.
X2YYDEF D2EVISIO, PROC=ESFD2EE, MAXTASK=10, DEFAULT=NO
NODE MYA2PD, SMTP, TCPPRT=mydomain.com, TCPPORT=25, X2YY=D2EVISIO, TRANSFRM=A2PDKT
In the CA Spool Java Transformers Administration Guide , Chapter 1, it states "Actuate's Xenos d2e Vision is written fully in Java, so zAAP processors can be utilized."
However I cannot find a parameter to tell the Java Transformers to use zAAP processors.
There is no need for any parameter setting with the CA Spool Java Transformers to take advantage of the zAAP processors.
This is rather handled by the Java Virtual Machine (JVM) initiated when the CA Spool Java Transformers FSS executes Java code.
Whenever the JVM has found zAAP processors are defined in the environment it issues a request to z/OS to switch to zAAP.