Author: "Martin, Jon R." <jrmartin AT KNS DOT COM>
Date: Tue, 12 Jun 2001 09:04:36 -0400
Good Morning, I am running TSM on AIX 4.3. Most of the suggestions I have seen for correcting a recovery log issue involve having access to TSM. Unfortunately I don't have any access. Does anyone hav
Jon - Contact your TSM administrator to have that person address it. And contact them ASAP, as the situation you detected is impairing all TSM processing. Richard Sims, BU
Author: "Lambelet,Rene,VEVEY,FC-SIL/INF." <Rene.Lambelet AT NESTLE DOT COM>
Date: Tue, 12 Jun 2001 15:38:35 +0200
Hello, on OS/390 we can run the server in batch mode to extend the log. You should be able to do the same under AIX: start it with a special parameter to indicate extension of the log, René Lambelet
Hi Joe, your Recocery log is full, you cannot make any action, I have the same problem a few weeks ago. Stop TSM server and restart it and recovery log becomes empty. Then you should set recocery log
Create a logical volume ... small is ok cd /usr/lpp/adsmserv/bin dsmserv extend log /dev/rlog-d35f3-ext 100 the /dev/rlog-d35f3-ext is the logical volume name Jeff Bach Home Office Open Systems Engin
Julie...when in NORMAL mode, the recovery log keeps copies of all 'inflight' transactions....thus the log will grow based on current backup activity and/or other database update activity. When a tran