Hello:

Here are some of the issues that I ran into while getting the TSO ADMIN
client working with the ADSM MVS server using APPC as the commmethod.

Start with the information on pages 190-194 of SH26-4043-00 Installing the
Server and Adminisrative Client.

1 - Make sure the ACBNAME in the APPCPMxx member of SYS1.PARMLIB matches
    the ACBNAME (or APPL name if ACBNAME is not coded) that you created
    for the TSO ADMIN client.

2 - Make sure you create the TP profile data set that is pointed to by
    the LUADD stanze in the APPCPMxx member of SYS1.PARMLIB.  Although
    no TP profile needs to get created if the profile data set does not
    exist APPC will abend on start-up and ADSM will get a CPIC return code
    CM_PRODUCT_SPECIFIC_ERROR.

3 - Make sure the value specified for the SYMBOLICDESTINATION in the client
    options file matches the DESTNAME option in the side information record
    and the name in the client options file is in UPPER CASE.  If either
    the name is not in upper case or the name does not match then you will
    get CM_PROGRAM_PARAMATER_CHECK.

4 - Make sure the APPL statement contains a MODETAB entry if the modename
    specified in the side information record does not exist in the default
    mode table.

5 - Make sure to start APPC and ASCH.  You might need to use
    S APPC,SUB=MSTR,APPC=xx to specify which APPCPMxx member you want out of
    SYS1.PARMLIB.

6 - Although ASCH needs to be started there does not need to be an ASCHxx
    member in SYS1.PARMLIB.  If it does not exist you will get some warning
    messages at start-up of ASCH but they can be ignored.

7 - If ASCH is not started you will get an error that indicates the
    conversation can not be allocated.

Hope this helps - David Bohm, ADSM technical support.