APAR status
Closed as program error.
Error description
When client sessions are disconnected abnormally, the dsapi_slave processes stay out there in a defunct state. The adeb shared memory segment stays out there with an nattch of 1 and the ISF memory map shared memory segment stays out there with an nattch of 0. The customer kills the dsapi_slave processes manually and the adeb segments get an nattch of 0 but still stay there
Local fix
Problem summary
On UNIX platforms at for IS 8.0.1, the ISF shared memory segment that is created for a DataStage client connection may not be removed if the dsapi_slave terminates abnormally. (This problem previously reported under ecase 119241.)
Problem conclusion
Added code to dsapi_slave for ensuring that the shared memory segment is removed when the normal shutdown code in the DataStage server isn't executed due to a broken network connection or an abnormal condition in processing.
Temporary fix
Remove unused shared memory segments manually if a job connection is broken.
Comments
APAR Information
APAR number
JR34724
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-02
Closed date
2011-05-04
Last modified date
2011-05-04
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
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R801 PSY
UP
R810 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 May 2011