Direct links to fixes
8.6.0-TIV-TWS-WINDOWS-FP0004
8.6.0-TIV-TWS-WINDOWS_X86_64-FP0004
8.6.0-TIV-TWS-SOLARIS-FP0004
8.6.0-TIV-TWS-SOLARIS_I386-FP0004
8.6.0-TIV-TWS-LINUX_X86_64-FP0004
8.6.0-TIV-TWS-LINUX_S390-FP0004
8.6.0-TIV-TWS-LINUX_PPC-FP0004
8.6.0-TIV-TWS-LINUX_I386-FP0004
8.6.0-TIV-TWS-IBM_I-Fp0004
8.6.0-TIV-TWS-HPUX-FP0004
8.6.0-TIV-TWS-HPIA64-FP0004
8.6.0-TIV-TWS-AIX-FP0004
9.1.0-TIV-TWS-WINDOWS_X86_64_AGENT-FP0002
9.1.0-TIV-TWS-WINDOWS_X86_64_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-DWC-README-FP0002
9.1.0-TIV-TWS-WINDOWS_AGENT-FP0002
9.1.0-TIV-TWS-WINDOWS_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-SOLARIS-FP0002
9.1.0-TIV-TWS-SOLARIS_I386-FP0002
9.1.0-TIV-TWS-SOLARIS_I386_AGENT-FP0002
9.1.0-TIV-TWS-SOLARIS_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUXPPC-FP0002
9.1.0-TIV-TWS-SOLARIS_I386_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-SOLARIS_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_X86_64-FP0002
9.1.0-TIV-TWS-LINUX_X86_64_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_X86_64_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUX_S390_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_S390_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUX_PPC_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_PPC_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUX_I386_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_I386_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUX390-FP0002
9.1.0-TIV-TWS-IBM_I_AGENT-FP0002
9.1.0-TIV-TWS-IBM_I_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-HPIA64-FP0002
9.1.0-TIV-TWS-HPIA64_AGENT-FP0002
9.1.0-TIV-TWS-HPIA64_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-AIX-FP0002
9.1.0-TIV-TWS-AIX_AGENT-FP0002
9.1.0-TIV-TWS-AIX_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-WINDOWS_X86_64-FP0002
APAR status
Closed as program error.
Error description
Joblog shows following error and fails: <LogText><![CDATA[AWSITA082E The agent got an error response while sending the resource information to the server. The error code is "DISPLAY_NAME_ALREADY_EXISTS" and the error message is "AWKRRP084E A resource already exists with display name "<NFS mount path>"and type"FileSystem".".]]></LogText> It is caused by the NFS file system unmounted at a random rate and still some legacy data in the FSR table.
Local fix
If the analysis is correct, removing the row in the FSR table, related to the NFS filesystem and for the specific agent: delete from DWB.FSR_FILESYSTEM_RESOURCES where FSR_NAME='<agent ID>/<NFS mount path>'
Problem summary
All SAP jobs scheduled on a specific dynamic pool workstation go to the READY state when their dependencies are resolved in the plan
Problem conclusion
TAJ_TWS_AGENT_JOBS table is not correctly handled removing not running r3 jobs
Temporary fix
Comments
APAR Information
APAR number
IV67024
Reported component name
TIV WKLD SCHDL
Reported component ID
5698WKB84
Reported release
9A1
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-18
Closed date
2014-12-29
Last modified date
2015-04-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TIV WKLD SCHDL
Fixed component ID
5698WKB91
Applicable component levels
R9A1 PSY
UP
Document Information
Modified date:
14 April 2015