We are seeing CPU hog abends when loading CONFIG.NLM with the /ALL
parameter on our clustered NW65SP3 Servers. I didn't believe it on the first
server; so I did the same thing on a second..... and on a third.

If I load config /ALL just after the re-boot but before resources are moved
back to
the server, it works okay.

If it matters, we have also applied the CMDLLNLM, NW65OS3, NW65NSS3A,
65AFP239, XNFS3A, TSA5UP18, TCP659J and SYSCALLS patches.

Has anybody seen anything like this? If I open an incident, I know that
will want a dump..

Steve Druck
Weizmann Insititute of Science