Hi :) ,
How can bshell messages be trapped thro AFS?

Is there a specific error that you are getting that you want to trap? I do not think there is a way to trap bshell messages.

It can be any message that the bshell generates..for e.g a session timeout error or some message send by administrators or message generated by license server and so on...

You can search the board - I know it has been discussed before, but as far as I know there is nothing that can trap these errors.

Hi Bindu,

AFS is not built to trap those errors I think.

Regards

Did you try to use any bshell tracing flags or debug bshell ?

Explaining what are you looking for helps others to think in the right direction than shooting an arrow in the dark ?

We have faced this very peculiar problem of one particular session using AFS getting hung whenever our license server restarts. The message "no license server" (even though the license server has restarted) pops up and the processing stops there. Please note that all other sessions are working fine during this time.
Hence I wanted to know is there any functionality in AFS to trap such bshell triggered messages .