On the JOBLOG it can be seen that the LPAR is running with 2G of storage only. Any LPAR running with such a small amount of storage can encounter the problem. As documented on KB000006873
, the storage for the LPAR should be increase to at least 4G to avoid the problem even if not running under z/VM.
The problem seems to be related only to z/OS 2.2 where IBM made some significant changes that can result in this situation.