Re: FW: ADSM problem

[Wim Feyants]

Jerry,
this is a know problem with the USS client. The reason is probably a memory
leak somewhere. Check with you local IBM support, as this has an apar
attached to it. If I'm correct, a start/stop of the schedule process should
fix it.


Wim Feyants

Re: FW: ADSM problem

[Richard Sims]

>ANS1149E 'No domain available

Sounds like the dsm.opt file got changed, and you want it to specify
a Domain of All-local.
  Richard

FW: ADSM problem

[JerryLawson]

Fellow list members

The guy we have handling ADSM and mainframe clients sent me the following problem.  As 
far as I know, they really haven't changed anything.  Backups stopped occurring last 
Thursday.  The messages are bordering on cryptic, and the manual isn't much better.  
The "No domain available" is confusing to me, because the node is assigned to the same 
domain it always has been, and shows up in the admin.  Or is it referring to a domain 
on the OpenEdition/Unix Systems Services address space?

Thanks in advance.

Jerry Lawson

 -Original Message-
From:   Leach, Michael C (OTSD, IT)
Sent:   Wednesday, October 04, 2000 1:52 PM
To: Lawson, Jerry W (OTSD, IT)
Cc: Annino, Robert D (OTSD, IT); Vechinsky, John M (OTSD, IT)
Subject:ADSM problem

Jerry,

I was hoping you could help us with a problem we are experiencing with an Open Edition 
client (MVS 2.8) who had been successfully backing up his environment with ADSM. He is 
now getting an ANS1149E 'No domain available for incremental backup' and a ANS1512E 
'Scheduled event failed' Return code = 1. We are running ADSM 3.1.6 and nothing has 
changed in the client or server environments that we are aware of. If you could shed 
any light on this problem it would be greatly appreciated.

Mike Leach
Storage Administrator
The Hartford