And yes, a "defunct" process cannot be killed, because that already happened. "defunct" means that only the entry in the process list remains because the termination has not been picked up (through a wait() call) by the parent process. Sometimes, sending a kill -1 to the parent process works, but such a situation usually points to a code issue in the parent (e.g. the SAS object spawner). By killing/terminating the parent, the system init process takes over all its children and will remove them after receiving the -1 signal (kill -1 1). If that also fails, a system reboot is in order. Although I haven't seen that happening for a long time now (>10 years, not with AIX 6/7 and SAS 9.2 and above) ... View more

For the issue that has been mentioned, the first step is to check the logs. For an issue with web portals one can restart the web Application server . The script is given here. https://documentation.sas.com/doc/en/bicdc/9.4/bisag/n0mb6964vbfoeqn1hahrxyf89ugi.htm  The scripts given here also help us to check the status of the server. You can incorporate them into a batch Korn Shell or bash script to run them a periodic basic and get the status. If the issues with portal are recurrent then the appropriate approach is to contact SAS Tech Support. Going a sttep further you can consider using the deployment server batch utility as detailed here https://documentation.sas.com/doc/en/bicdc/9.4/bisag/n1uay2nibrxgxan1ranpr33gn8rt.htm . But this hould not be necessary ... View more

What do the object spawner logs say?  You can restart the object spawner using the script  Object spawner can be restarted using batch scripts as detailed here  https://documentation.sas.com/doc/en/bicdc/9.4/bisag/n0mb6964vbfoeqn1hahrxyf89ugi.htm  About monitoring You can use SAS Environment manager ... View more

Any time I need user related metadata I normally take the quick and easy way and use the SAS supplied macro %MDUEXTR. It probably gives you more than you need but it saves an awful lot of coding. Do it as a first step in a EG project and the rest will be clever joining, filtering and reporting on the resulting tables. In code: %MDUEXTR(LIBREF=WORK);   One of the resulting tables is EMAIL (all have obvious names) that can be joined with others, like PERSONS, for additional context.   Hope this helps, - Jan. ... View more