Hi all,
My thanks to those of you that responded to my request. We were
unfortunately unable to resolve our problem. Even IBM was unable to help.
So we had to bypass it instead.
In order to meet our deadline for upgrading the Mainframe operating system
software, we decided to upgrade the ADSM server to 3.1 lvl 2.0, without our
usual intensive testing. (I don't recommend this, but we were between a rock
and a hard place).
The ADSM server upgrade was done on 03/08/99, and ran without problems under
OS/390 v.1.2. The conversion of the ADSM database took less than 5 minutes.
On 07/08/99 the Mainframe operating system software was upgraded to OS/390
v.2.6. Everything went without a hitch.
WARNING
One warning I would make however, is in regards to the Quick Start manual
(for MVS). We utilise the TSO Admin client at our site, and the
instructions for setting this client up are non-existent in the manual. The
ANSADM module (with alias DSMADMC) needs to be re-linked out of the SMP LTS
pds library. We eventually found the required information within some
members in our SYS1.SAMPLIB pds library - ANRDDDEF and ANSDDDEF.
Documentation for running the CALLLIBS job (SMPE job that creates the he
linkedit job) was found in ADSM Program Directory document. The linkedit
job needs to be run to allow TCP/IP and Language Environment to be linked
into the ADSM TSO client module.
The version 2 ADSM manuals included covered this requirement, but the
version 3 ADSM manuals don't. Hopefully IBM will rectify this, and ensure
that manuals for future ADSM versions, include the setting up of this
client.
Hope this helps. Once again my thanks to those of you that endeavoured to
assist me in resolving our problem.
Gary Johnson
Operations Analyst (Emergency Planning)
IT Operations
CLEAR Communications Ltd
cnr Taharoto & Northcote Roads, Takapuna,
Auckland, 1309, New Zealand.
floorzone: 2101
phone: (64-9) 912-4200
DDI: (64-9) 912-4984
fax: (64-9) 912-4454
email: gary.johnson AT clear.co DOT nz
> -----Original Message-----
> From: Gary Johnson
> Sent: Wednesday, July 28, 1999 10:08 AM
> To: ADSM list (E-mail)
> Subject: ADSM v.2.1 MVS Server On OS/390 v.2.6
>
> Hi all,
> I hope you can help me. We are about to upgrade our Mainframe MVS
> operating system from OS/390 v.1.2 to OS/390 v.2.6. However, we don't
> want to upgrade ADSM at the same time, so we want to run the ADSM Server
> (v.2.1) under OS/390 v.2.6. However we are having several problems when
> testing this out.
> We are trying to use ADSM Version 2.1 lvl 18 in OS/390 v2.6. We assume it
> should work. After running the ZAP referred to in PQ19589 against the
> OS/390 2.6 version of DMSSVM5 the ADSM server started successfully. Now
> we are having problems connecting to ADSM from the Admin Client GUI.
> TCP/IP changed radically between OS/390 1.2 and OS/390 2.6 and with
> several products that we use, TCP/IP had to be reconfigured to use OE
> sockets. Does ADSM require any changes? When we try to connect the
> session just hangs. We can PING the HOST name OK but we can't telnet to
> port 1500. In the ADSM options file we have :
> TCPPORT 1500 and TCPNAME TCPIP
> Netstat sockets output show ADSM listening on port 1500
> The errors from the client end are as follows:
> ANS4017E Session rejected: TCP/IP connection failure
>
> ANS8002S Due to this error, processing cannot continue.
> This graphical user interface will shut down.
>
>
> We would appreciate any help that could point us in the right direction.
> We have raised an ETR with IBM for this problem. Unfortunately IBM has
> not been able to provide us with much assistance to date........their
> response is that they haven't seen this problem before..!!!!!!
>
> We suspect it is either a maint level issue with the ADSM server, or
> something to do with TCPIP.
>
> Regards,
> Gary Johnson
> Operations Analyst (Emergency Planning)
> IT Operations
> CLEAR Communications Ltd
> 12th floor, 49 Symonds Street, Auckland, 1001, New Zealand
> phone: (64-9) 912-4200
> DDI: (64-9) 912-4984
> fax: (64-9) 912-4454
> email: gary.johnson AT clear.co DOT nz
>
|
