ADSM-L

MVS ADSM and TSO admin client in batch

1999-07-16 10:25:37
Subject: MVS ADSM and TSO admin client in batch
From: François Le Maner <flemaner AT LORICAM DOT FR>
Date: Fri, 16 Jul 1999 16:25:37 +0200
Hello , my problem is solved , it was a bug (see apar PQ21866) in ADSM

1) IBM support center give me the following LINK EDIT :

>>
>> Cust uses TCP/IP from INTERLINK.
>> He need to RELINK the TSO Admin:
>>
>> //SYSLMOD DD DSN=ADSM.V3.LINKLIB,DISP=SHR
>> //SYSLIB       DD  DSN=INTELINK.CILIB,DISP=SHR
>> //                      DD  DSN=CEE.SCEELKED,DISP=SHR
>> //SMPLTS    DD  DSN=SMPE.MVS.SMPLTS,DISP=SHR
>> //SYSLIN      DD *
>>  INCLUDE SMPLTS(ANSADM)
>>  INCLUDE SYSLIB(A0PERR)
>>  INCLUDE SYSLIB(STRERROR)
>>  INCLUDE SYSLMOD(ANSADM)
>>  ALIAS   DSMADMC
>>  MODE    AMODE(31),RMODE(ANY)
>>  SETCODE AC(0)
>>  ENTRY   SVMSTART
>>  NAME    ANSADM(R)
>> /*
>> ***********************************************************
>
2) ADSM lose the TCPPORT number
description 'APAR PQ21866
>>
>>Hello,
>>your first problem, the tso admin client getting the rc -59 matches
>>apar PQ21866. A brief desciption of the apar follows :
>>--------
>>IF THE TCPPORT OPTION IS PLACED BEFORE THE ICSSNAME OPTION IN
>>THE OPTIONS FILE, THE TCPPORT . WILL BE INTERPRETED AS ZEROS.
>>---------
>>PROBLEM SUMMARY:
>>****************************************************************
>>* USERS AFFECTED:                                              *
>>All users if the Version 3 TSO Admin Client.
>>****************************************************************
>>* PROBLEM DESCRIPTION:                                         *
>>The TSO Admin Client is unable to connect to the server using
>>the Interlink support because the port number is invalid.
>>Even tho the port number is specified in the TCPPORT statement
>>correctly, it is not valid when it is used.
>>PROBLEM CONCLUSION:
>>The TCPPORT number was being overlayed with blanks when the
>>ICSSNAME value was placed in a control block.  The code
>>assumed the ICSSNAME value to have a length of 8 instead of
>>4.  Code was change so that the correct length is used.
>>With this change, the order of the TCPPORT and ICSSNAME
>>option statements is not relevant.
>>
>>Bonne réception, et bon wek end
>>Bruno  DUVAL
>>
>>
>
<Prev in Thread] Current Thread [Next in Thread>