Description
This health check monitors number of concurrent active internal Transformer subtasks, AFP Transformers subtasks, and text wrapper subtasks to warn if the maximum number of Transformer subtasks is being reached.
Files being transformed externally by the Java Transformers do not count toward the maximum number of Transformer subtasks.
This condition is checked periodically every five minutes, and reports a medium severity health check exception if the threshold is exceeded.
Best Practice
Set X2YY MAXFILES to from 5 through 10. A number higher than 10 does not increase throughput, but only increases the virtual storage usage below the 16 Mb-line.
Note: For more information, see X2YY MAXFILES Check.
To allow for concurrent transformations remove TRANSFRM option R, which causes a transformation report to be produced for each transformation.
Specify the AFP transformer parameter CacheSize. If CacheSize is set to, for example, “CacheSize=10M” up to 10Mb of AFP resources are stored in memory to avoid reading the same resource members from the AFP resource libraries repeatedly. This dramatically reduces the I/O and CPU usage.
Use BUFSIZE=27998 to reduce I/O and CPU overhead to read transformer input files and write corresponding transformer output files.
Specify TRANSFRM option B to have multiple PCL, PostScript, and PDF commands buffered into output records to reduce CPU usage.
Specifies the threshold queue percentage. nn is a number from 0 through 100, inclusive.
Default: Taken from the CA Spool initialization parameter TGWARN.
No
No
For more information, see the Operations and Commands, Messages, and Customization guides.
Normal: ESFH041I
Exception: ESFH042E
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|