Pathmon error 1121 - Autorestart Disabled

Sanand

unread,

Jan 17, 2013, 1:02:49 AM1/17/13

to

Hi,

We found one of our COBOL server in production is not getting up because of pathmon error 1121 - Autorestart disabled. Error 1121 means pathmon already exceeded attemps trying to restart the server and now could not be started. The saveabned is not on for this server. Do you know how to overcome this situation. Is there any way to start the server without making any server config changes. i know one way is turn saveabend on so that if could see if any issue with processing. Any other thoughts on 1121 error.Thanks in advacne.

Regards,
Sanand.

Anupam Das

unread,

Jan 17, 2013, 2:02:17 AM1/17/13

to

Autorestart is disabled because the server is again and again abending continously and so there is no point for the Pathmon to keep it up for a very long duration unless the problem is fixed. Check for the HOMETERM parameter in the server config, open the HOMETERM and I am sure server must have thrown some error there. This may allow you to not to go turn on the SAVEABEND Setting etc if you are too much reluctant to debug etc :-). Even if you issue START server command as of now, this is not going to help unless the problem is solved. If my guessing is right, the server must be trying to open some file in the beginning itself and getting error 48 which is most common kind of error I have seen :-). But may be different as well.

Anupam Das

unread,

Jan 17, 2013, 2:09:07 AM1/17/13

to

By the way, if $NULL is set for HOMETERM then only resolution is to turn of SAVEABEND and capture the core-dump file.

Keith Dick

unread,

Jan 17, 2013, 2:58:06 AM1/17/13

to

Anupam Das wrote:
> By the way, if $NULL is set for HOMETERM then only resolution is to turn of SAVEABEND and capture the core-dump file.

Well, I think you meant to say turn ON the SAVEABEND attribute, but that is not the only thing he could do -- he could change the home terminal setting to some device or process which could accept and store or display the error messages, assuming the error messages are going to the home terminal. The server might write error messages to its OUT file, or to some other file that it opens to use as an error log, so he would have to look there, too. There are lots of possibilities, and he is going to have to look at the Pathway configuration of the serverclass and the source code of the server to see where the error messages might appear.

One fairly easy approach to debugging startup problems in a server is to run the server from a TACL prompt, after setting up the appropriate IN, OUT, ASSIGNs, PARAMs, and DEFINEs, as specified in the Pathway configuration of the serverclass, and see what it does, either just observing the output or running it with RUND to debug it. That isn't very helpful if the server has problems when it is processing requests, but for debugging startup problems, it is a handy approach.

Anupam Das

unread,

Jan 17, 2013, 5:41:49 AM1/17/13

to kd...@acm.org

>> Well, I think you meant to say turn ON the SAVEABEND attribute <<

Oh yes, sorry Keith. That was a typo :-).

>> that is not the only thing he could do -- he could change the home terminal setting to some device or process which could accept and store or display the error messages, assuming the error messages are going to the home terminal. <<

Couple of things here -

1. OP said he is not much keen on changing any Pathway configuration and so I assumed that he might not be interested to take that path.
2. It does not matter whether the error messages are going to the home terminal or elsewhere, because, the ABEND will definitely display a CRE Run-time Error message on the home terminal even if the program does not write anything in any log or console or in the home terminal.