If you notice a high incidence of joblet failures on a vsphere discovery job, the cause might be a result of a lack of available resources on the Orchestration Agent. You need to increase the Orchestration Agent heap size beyond the default, which is 512 MB.
To address this issue for an Orchestration Agent running on a Windows computer, create the C:\Program Files (x86)\Novell\ZOS\Agent\bin\zosagent.vmoptions file with the following content:
-XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 -Xmx512m -Xms512m -XX:MaxPermSize=128m
This same content also exists in the /opt/novell/zenworks/zos/agent/bin/node file for an Orchestrate Agent running Linux.
You can adjust the values in these files as needed:
The -XMx parameter sets the maximum heap size.
The -XMs parameter sets the initial and minimum heap size.
The -XX:MaxPermSize parameter sets the PermGen memory size.
After you create the zosagent.vmoptions file for the Windows agent, make configuration changes and save it, you need to restart the Windows agent.
For a Linux agent, look for the JVMARGS= section of the /opt/novell/zenworks/zos/agent/bin/node file. Normally, you change values of the -XMx or the -XX:MaxPermSize parameters in the file. After you make such changes, you need to save the file and restart the Linux agent.
NOTE:If the agent is running low on PermGen memory, we suggest that you conservatively increase it by 128 MB increments until no errors occur.