> I cannot get the ADSM 1.1 server to initialize on my VM/ESA 1.2.0
> system.  VM/ESA 1.2.0 is at slu 0 and I have C/370 version 2 release 1.0
> at slu 0.

Hm. SLU 0 for both products is probably not OK. There is
definitely some service required for DMSSVM beyond what's shipped
on the base tape, and 1.2.1.0 for the C libraries seems a bit
old. I remember having to apply service to the C libraries when
we first installed WDSF and subsequently ADSM.

> with the errors below.  Subsequent cp or cms commands yield more trace
> information from DSMSERV.  This seems to be related to the level of
> the C libraries but IBM assures me that my level is OK.  Anyone out
> there have any hints?  Thanks in advance for any comments.

>   At offset FFAC866A in Proc SVMCTXFR with EPA 0134B2B8 and DSA 015EA570
>    -------------- First 128 Bytes of DSA for Proc SVMCTXFR ---------------
>    015EA604 015EA0C8 015EA939 0134B4A0 013074C8 015EA368 015EA5D8 00DD0000
>    0130C248 0170CB18 015EA256 00000000 00000000 015EA570 015E7000 015EA0C8
>    0134B2B8 015E7000 015EA5F0 015EC000 01300BD8 015EA000 00000000 00000000
>    015EA470 00000000 815EA368 015EA361 015EA620 00000000 00024061 00000000
>
> >From offset 00000412 in Proc SVMCVBLD with EPA 01319B78 and DSA 015EA0C8
>    -------------- First 128 Bytes of DSA for Proc SVMCVBLD ---------------
>    00E04000 015EA050 015EA570 81319F8C 0134B2B8 000002E8 0131A430 00DD0000
>    0130C248 0170CB18 015EA256 00000000 015EA000 00DE55C8 00000002 01300BD8
>    81319B9C 015E7000 015EA570 015EC000 01300BD8 015EA000 00000000 00000000
>    015EA470 00000000 015EA258 00000100 815EA256 8131A444 80000000 0132AB88
> End of Calling Trace

Given the procedure names, I'd suspect the SVM multitasking
support in CMS. You may need some CMS service.