Re: firmware robot magstar3575L32

[Coyle, Jack]

Michelle,

Per my trusty Maintenance Information manual for our 3575-L32 library, the
following part numbers may be what you are looking for:

Part Number Description
08L6658 EPROMs v2.17 (Model L12 only)
08L6659 EPROMs v2.17 (Model L18 only)
08L6660 EPROMs v2.17 (Model L24 only)
08L6661 EPROMs v2.17 (Model L32 only)

Note: I suspect that this part number is probably "supped" (my CE's term,
not mine) to a different number as v2.17 is no longer the latest microcode
level for the machine. (We are running v2.19 in our 3575-L32s.)

Regards,
Jack Coyle
Rex Healthcare

> --
> From: Michelle Wiedeman[SMTP:[EMAIL PROTECTED]
> Reply To: ADSM: Dist Stor Manager
> Sent: Friday, March 14, 2003 10:26 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: firmware robot magstar3575L32
>
> thnx eric!
> thats more info than I've ever gotten from bellmicro (where we got the
> lib)
> theyre claiming its a file...
> won't  have the part-no. available do you?
>
> -Original Message-
> From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2003 4:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: firmware robot magstar3575L32
>
>
> Hi Michelle!
> You will not find it anywhere. The library microcode is on a chip on the
> control board inside your library. The only way to have your library
> microcode upgraded is by placing a service call at IBM. They will come and
> place a new chip in your library. I have had it done here, it takes about
> 30
> minutes.
> But you stated that IBM doesn't have it? Was that a service engineer?
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
>
> -Original Message-
> From: Michelle Wiedeman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 13, 2003 16:39
> To: [EMAIL PROTECTED]
> Subject: firmware robot magstar3575L32
>
>
> hi all,
> Does anybopdy have a clue to where I can find firmware for the library
> robot?
> Our robot doesnt read barcodes. Now our supplier claims we ned fmr
> 3575-2007, but says IBM doesnt have it.
> I'm sure I can get it somewhere!
> so I turn to you all!!
> does anyone have it (or a later version which includes this) or know where
> to download/get it???
>
> thnx,
> /\/\ichelle
>
> "Plaats hier een Engelse quote die duidelijk maakt dat je een miskende
> intellectueel bent met een boeiende en diepgaande gedachtengang"
>
>
> **
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential
> and privileged material intended for the addressee only. If you are not
> the
> addressee, you are notified that no part of the e-mail or any attachment
> may
> be disclosed, copied or distributed, and that any other action related to
> this e-mail or attachment is strictly prohibited, and may be unlawful. If
> you have received this e-mail by error, please notify the sender
> immediately
> by return e-mail, and delete this message. Koninklijke Luchtvaart
> Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be
> liable for the incorrect or incomplete transmission of this e-mail or any
> attachments, nor responsible for any delay in receipt.
> **
>

Re: problem with a su script

[Coyle, Jack]

I thought the syntax to have a specific command executed required the "-c"
option, i.e.

su - oracle -c /home/oracle/scripts/backup/db_backup.sh

Jack Coyle
Rex Healthcare

> --
> From: Conko, Steven[SMTP:[EMAIL PROTECTED]
> Reply To: ADSM: Dist Stor Manager
> Sent: Wednesday, April 02, 2003 8:25 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: problem with a su script
>
> > On all of our database servers we run an archive nightly but instead of
> a
> > regular "archive" we run a command instead:
> >
> > su - oracle /home/oracle/scripts/backup/db_backup.sh
> >
> > this script handles all the processing of the database and calls a dsmc
> > archive command. on 97% of the servers it works fine. however, on just a
> > few of them... that dont appear to be any different, the script
> > immediately dies with a return code of 1 (no, its not permissions)
> > however tsm reports it as completed (another problem). it doesnt appear
> > the script ever gets run because we use a debugging statement for the
> > first line that never gets called. nothing in the environment seems to
> be
> > a problem and on one system it just suddenly stopped working without any
> > changes being made.
> >
> > any ideas whats going on here? we're running aix 4.3.3, tsm client 5.1.5
> > and server  aix 4.3.3 tsm 4.2.2... even on the servers it works on.
> >
> > Steven A. Conko
> > Senior Unix Systems Administrator
> > ADT Security Services, Inc.
> >
>

Server Level 5.1.7.0 & APAR IC34754

[Coyle, Jack]

Like the rest of the group, our 5.1.x server suffered the "mashed" output
from a "query process" command. An append to this forum from Mr. Raibeck
indicated that this behavior was indeed anomalous and that APAR IC34754 had
been opened to address the problem. We have obtained level 5.1.7.0 recently
and the README.SRV file indicates that this level indeed contains the "fix"
for the subject APAR. However, after installing the level on our AIX 4.3.3
server, we are now seeing output from a "query process" command similar to
that shown below. Has anyone else observed "strange" output after applying
what was supposed to be a fix for strange output?

Regards,
Jack Coyle
Rex Healthcare
(919) 784-3792
[EMAIL PROTECTED]

tsm: SRV_01>q pro

 Process Process Description  Status

  Number
 
-
   1 Space ReclamationVolume 10202 (storage pool TAPEPOOL1), Moved

   Files: 5624, Moved Bytes: 3,212,860,540,

   Unreadable Files: 0, Unreadable Bytes: 0.

   Current Physical File (bytes):

   35,241,912
Current input volume: 10202.
Current
   output volume: 10042.


tsm: SRV_01>q pro

 Process Process Description  Status

  Number
 
-
   1 Space ReclamationVolume 10202 (storage pool TAPEPOOL1), Moved

   Files: 5635, Moved Bytes: 3,656,498,172,

   Unreadable Files: 0, Unreadable Bytes: 0.

   Current Physical File (bytes): 2,080,724
Current
   input volume: 10202.
Current output volume:
   10042.


tsm: SRV_01>q pro

 Process Process Description  Status

  Number
 
-
 234 Space ReclamationVolume 10053 (storage pool TAPEPOOL1), Moved

   Files: 4464, Moved Bytes: 1,263,379,404,

   Unreadable Files: 0, Unreadable Bytes: 0.

   Current Physical File (bytes): 754,580
Current
   input volume: 10053.
Current output
   volume: 10201.

Re: Help on select syntax

[Coyle, Jack]

Robert,

In place of your listed date computation, try

cast ((current_timestamp-date_time)hours as integer)<=24

Regards,
Jack Coyle
Rex Healthcare
(919) 784-3792
[EMAIL PROTECTED]


> --
> From: Robert Ouzen[SMTP:[EMAIL PROTECTED]
> Reply To: ADSM: Dist Stor Manager
> Sent: Monday, July 21, 2003 7:09 AM
> To:   [EMAIL PROTECTED]
> Subject:  Help on select syntax
>
> Hi to all
>
> Try to run a select query on the actlog table for certain msgno in certain
> period but got wrong result. Here my select command:
> select nodename , msgno , substr(message,44,14) as "Message"
> from actlog where (msgno=4961 or msgno=4964) and
> date_time=CURRENT_TIMESTAMP
> - 1 days
>
> Without the date_time parameter I got what I want but for the entire
> period
> I need to limit my query for the last 24 hours.
>
> Please advise if possible ..
>
> Regards Robert Ouzen
> E-mail: [EMAIL PROTECTED]
>

Re: Admin schedule to Backup DB does not start

[Coyle, Jack]

The issue here would seem to be the "wait=yes" option you have specified for
the backup command. Doing so causes the server to process the command in the
foreground. This, in turn, requires that you must wait for the command to
complete before performing any other tasks. Indeed, in such an environment,
you can only run one scheduled command at a time. Is there a compelling
reason why "wait=yes" is specified (other than the obvious one of not
wanting the database backup to occur before the backups of the storage pools
complete)?

Jack Coyle

> --
> From: Talafous, John G.[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Saturday, March 24, 2001 12:07 PM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Admin schedule to Backup DB does not start
>
> The ADMIN schedule that processing storage pools contained a "backup stg
> blahpool blahpool wait=yes".  When the wait completed, another backup stg
> command was issued and the ADMIN schedule ended. Then, the ADMIN schedule
> to
> do the database backup kicked off.
>
> Does this mean only one ADMIN schedule at a time?
> jt
>
> -Original Message-
> From: Cook, Dwight E [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 24, 2001 11:33 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Admin schedule to Backup DB does not start
>
>
> did they have the same start time ? ? ?
> That might cause that... but the actual scheduled event should initiate
> and
> be gone in seconds...
> For all admin activity that I can think of, tsm simply spawns off a
> process
> and the scheduled event is complete, unless it is something really short
> like an "update stg diskpool high=1 low=0" type thing...
> What was your other schedule that actually tied things up for a while...
> Like with the dbbackup schedule, it will start a process and then the
> schedule/event is complete...
>
> Dwight
>
> -Original Message-
> From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 24, 2001 9:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Admin schedule to Backup DB does not start
>
>
> Well what do you know?!?  Another ADMIN schedule to manage storage pools
> was
> running. When it finished, the BACKUP_DB admin schedule started. But, does
> this mean that only one (1) admin schedule can be active at any given
> time?
>
> TIA,
> John G. Talafous  IS Technical Principal
> The Timken CompanyGlobal Software Support
> P.O. Box 6927 Data Management
> 1835 Dueber Ave. S.W. Phone: (330)-471-3390
> Canton, Ohio USA  44706-0927  Fax  : (330)-471-4034
> [EMAIL PROTECTED]   http://www.timken.com
>

Re: Admin schedule to Backup DB does not start

[Coyle, Jack]

You can simulate having an EVENT driven scheduler by changing the database
backup event from a straight command to a script. See, for example, the
Tivoli-supplied script BKUP_STG_DB that is shipped with the product. In the
supplied sample, they show doing a storage pool backup, followed by a
database backup, with logic to defer the whole event if there is a node in
session with the server. A few deft modifications should suit your purposes.
For example, their script starts out with

select * from sessions where -
  upper(session_type)='NODE'
if (rc_ok) goto reschedule

The reschedule label then deletes a "temporary" schedule (if one exists) and
creates a onetime schedule that runs the script again, specifying a start
time of NOW+0:20. If you were to use this for "inspiration", you could
schedule the storage pool backup commands to run in the background, schedule
the database backup command / script to run at a reasonable time after they
normally complete and start the script out with something along the lines of
the following

select * from processes where -
  upper(process)='BACKUP STGPOOL'
if (rc_ok) goto reschedule

Then, at the reschedule label, play the same game with rescheduling the
database backup in a temporary schedule at "some point" in the future.
(Reader beware! The syntax may not be 100% accurate. I am assuming that the
process name that is returned will indeed match the command name executed to
back up the storage pool.) I believe this should work, but, as always, I
reserve the right to be wrong.

Jack Coyle

> --
> From: Talafous, John G.[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Saturday, March 24, 2001 4:39 PM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Admin schedule to Backup DB does not start
>
> Yes, the compelling reason is to have the backups of storage pools
> complete,
> hopefully, by 9:00AM. Then the scheduled launch of a database backup at
> 10:00AM would coincide nicely with DRM processing and the resultant
> ejection
> of tapes from an ATL.
>
> But, if clients send more data than anticipated. Oh my!  I run into
> the
> situation that the earlier ADMIN schedule does not complete soon enough.
> (I
> have changed the BACKUP_DB schedule to have an eight (8) hour startup
> window). This should help.
>
> Another reason is an attempt to keep the number of tape drives utilized by
> administrative schedules and migration tasks at an
> INSTALLATION_MAX_DRIVES-1
> to permit random client restores to have at least one drive available.
> (Note: INSTALLATION_MAX_DRIVES is a variable applicable to any situation.)
>
> Is the problem not having an EVENT driven scheduler available to TSM? (ie:
> When storage pool X drains to zero, why can't I launch a backup of storage
> pool x-tape to x-copy?) Or, can I?
>
> Thanks in advance,
> John G. Talafous  IS Technical Principal
> The Timken CompanyGlobal Software Support
> P.O. Box 6927 Data Management
> 1835 Dueber Ave. S.W. Phone: (330)-471-3390
> Canton, Ohio USA  44706-0927  Fax  : (330)-471-4034
> [EMAIL PROTECTED]   http://www.timken.com
>
>
>
>
>
>
>
> -Original Message-
> From: Coyle, Jack [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 24, 2001 12:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Admin schedule to Backup DB does not start
>
>
> The issue here would seem to be the "wait=yes" option you have specified
> for
> the backup command. Doing so causes the server to process the command in
> the
> foreground. This, in turn, requires that you must wait for the command to
> complete before performing any other tasks. Indeed, in such an
> environment,
> you can only run one scheduled command at a time. Is there a compelling
> reason why "wait=yes" is specified (other than the obvious one of not
> wanting the database backup to occur before the backups of the storage
> pools
> complete)?
>
> Jack Coyle
>
> > --
> > From: Talafous, John G.[SMTP:[EMAIL PROTECTED]]
> > Reply To: ADSM: Dist Stor Manager
> > Sent: Saturday, March 24, 2001 12:07 PM
> > To:   [EMAIL PROTECTED]
> > Subject:  Re: Admin schedule to Backup DB does not start
> >
> > The ADMIN schedule that processing storage pools contained a "backup stg
> > blahpool blahpool wait=yes".  When the wait completed, another backup
> stg
> > command was issued and the ADMIN schedule ended. Then, the ADMIN
> schedule
> > to
> > do the database backup kicked off.
> >
> > Does this mean only one ADMIN schedule at a time

Re: client schedule

[Coyle, Jack]

Arshad,

A couple of questions come to mind. Sorry, no insights yet.

1) When you start the scheduler on the client, do you see a set of messages
in the dsmsched.log that indicate the client is waiting to be contacted by
the server and lists the next scheduled backup time?

2) When the scheduled event kicks off on the TSM server, do you see any
messages in the activity log prior to the one indicating that the schedule
has been missed?

Jack Coyle

> --
> From: Arshad Sheikh[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Monday, March 26, 2001 6:15 PM
> To:   [EMAIL PROTECTED]
> Subject:  client schedule
>
> Hi there,
>
> I have schedule a backup of a domain which contains only single node. The
> problem am facing is that, if I start dsmc sched in the foreground when
> the
> scheduled job is showing pending status (q event *  * ) then it will
> backup
> the domain, else in actlog it always says that its missed. Even if I ran
> the
> dsmc sched in the background with nohup, it didn't catch request from
> server
> and actlog always says that its missed.
>
> Any insights?
>
> Arshad.
>
>
>
> _
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>

Re: Can't Get New MGMTCLASS to Work

[Coyle, Jack]

Did the NetWare folks recycle the scheduler on the Novell server after
making the requisite change to the dsm.opt file?

Jack Coyle

> --
> From: Louis Wiesemann[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Wednesday, March 28, 2001 12:41 PM
> To:   [EMAIL PROTECTED]
> Subject:  Can't Get New MGMTCLASS to Work
>
> We are running 3.7.3 server on OS/390.  On one of our NetWare servers
> running client level 4.1.1 we wanted to start collocating a filespace we
> were not collocating before.  I defined a new management class and backup
> copygroup for it.  I pointed the copygroup to new storage pools (a disk
> pool migrating to a tape pool).  I formatted and defined volumes for the
> disk pool.  I activated the policyset with the new management class.  I
> had the NetWare people update the backup to use an include naming the new
> management class.  But when the backup runs it does not use the new
> management class.  Nothing gets written to the new storage pools.  The
> logs for the backup don't show any problems that I can relate to this.  I
> have reviewed the documentation and the list archives but have not found
> anything additional I need to do.  Am I missing something?  Does anyone
> have suggestions for where to look.
>
> Thanks for any ideas.
>
> --
> --
>
> Louis J. Wiesemann
> 502-852-8952
>
> --
> --
>
> The "Daily Word For Reflection" is a free service and a non-discussion
> list intended primarily to allow personal reflection on the Word of God.
>
> SUBSCRIBE/UNSUBSCRIBE at:
>
>http://monica.cin.org:81/guest/RemoteListSummary/daily_word
> 
>

Re: Announce new node IP to Server

[Coyle, Jack]

Did you stop and restart the schedule process on the client after making the
changes to dsm.sys?

> --
> From: Block, Clemens[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Tuesday, April 10, 2001 8:23 AM
> To:   [EMAIL PROTECTED]
> Subject:  Announce new node IP to Server
>
> Hi all!
>
> I have a problem with server prompted schedules.
>
> We had to modify the IP Address of a client Node (IBM RS6000).
> It works really well for all standard appllikations running on the
> System.
>
> To make a backup possible I edit the dsm.sys file on the Node and
> replace the old TCPCLIENTAddress with the new one. Depending
> on the new network structure the Hostname of the TCPServeraddress
> also changed and I replaced these option too.
>
> Test to connect the Server from the client using dsmc work well. I can
> see sessions on the Server with the new IP Address. Backups are
> possible without any problem.
> Even if I execute "dsmc q schedule " I get the right Informations about
> the Server prompted schedule for this node
>
> Now the Problem:
> If the Server start to initiate a backup session caused by a Server
> prompted
> schedule I get the connection error:
>   ANR2716E Schedule prompter was not able to contact client MORITZ
>   using type 1 (192.168.66.226 1502)
> The Message is correct, because 192.168.66.226 is the old IP Address.
>
> So my question is:
> How can I notify the server, that the node has an new IP Address.
>
> Thanks in advance,
> Clemens
>

Re: AIX Question

[Coyle, Jack]

After making modification to /etc/inittab, issue the command "telinit q".

> --
> From: Gill, Geoffrey L.[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Monday, April 30, 2001 5:27 PM
> To:   [EMAIL PROTECTED]
> Subject:  AIX Question
>
> For all you AIX guru's out there,
>
> I haven't been able to find an answer to this in any of the books I have
> so
> I need to ask. I've been told that on other UNIX systems there is a way to
> "refresh" what's in inittab to the system. In AIX is there a way to have
> the
> inittab re-run to pick up any changes or processes that may have been
> stopped without restarting the computer?
>
> Thanks,
>
> Geoff Gill
> TSM Administrator
> NT Systems Support Engineer
> SAIC
> E-Mail:   [EMAIL PROTECTED]
> Phone:  (858) 826-4062
> Pager:   (888) 997-9614
>

Re: 3575lib

[Coyle, Jack]

Try "lscfg -vl rmtn", where n is replace by an appropriate numeric value. A
drive capable of supporting the desired tape should return (along with the
other information):

Machine Type and Model..03570C1A

If it returns

Machine Type and Model..03570B12

the drive does not support the C-format tape.

> --
> From: Gisbert Schneider[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Thursday, May 03, 2001 9:59 AM
> To:   [EMAIL PROTECTED]
> Subject:  3575lib
>
> Hello,
>
> can anyone tell me how to check whether my 3575 library tapedrives can
> use Magstar C-Format XL tapes?
>
>
>
> __
>
>
>Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden
>koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche
>Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer
> die
>Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von
>rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben
>unberuehrt.
>

Re: reclaim spoy stgpool volumes

[Coyle, Jack]

Per the Tivoli Storage Manager (for AIX) Administrator's Guide, "to enable
volume reclamation for a storage pool that has only one mount point (that
is, one drive), you can define a reclamation storage pool for the server to
use when reclaiming volumes. When the server reclaims volumes, the server
moves the data from volumes in the original storage pool to volumes in the
reclamation storage pool."

I realize I cited an AIX manual and you stipulated a Solaris environment,
but I rather doubt they are that different that the information wouldn't
apply.

JRC

> --
> From: Jon Milliren[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Friday, May 04, 2001 1:00 PM
> To:   [EMAIL PROTECTED]
> Subject:  reclaim spoy stgpool volumes
>
> Hi all,
>
> I have a copy storage pool with 8 offsite volumes. 3 of these
> volumes
> have reached over 40% reclaimable space, so I decided to run a reclaim.
> I did this by updating the copy storage pools reclamation threshold to
> 40.
>
> I expected reclaim to run, but nothing happened at all. The copy
> storage pool tape library is automated, with one drive. I am using TSM
> 3.7.3 for Solaris. Do I need to create a reclaim storage pool, or use
> the MOVE DATA command? Or is this me setting the reclaim threshold
> incorrectly?
>
> I didn't expect any problems becuase this was a copy pool, and
> reading
> the admin guide led me to believe that since I was reclaiming offsite
> volumes, lack of multiple mount points wouldn't affect reclaim.
>
> Thanks,
>
> Jon
> --
> Jon Milliren
> Systems Administrator
> University of Pittsburgh
> Office of Institutional Advancement
>
> [EMAIL PROTECTED]
> (412) 624-2727 office
> (412) 292-2070 mobile
>

Re: RMAN backup fails with this error !

[Coyle, Jack]

Amrhar,

>From an administrative client session of the TSM (ADSM) server, issue the
command

q node "node_name" f=d

where "node_name" is replaced by the name of the node giving you the error.
Observe the value returned for the line "Maximum Mount Points Allowed". This
is probably the parameter that is causing you problems. To increase the
value, issue the command

upd node "node_name" maxnummp="new_value"

where "new_value" is something "reasonably" larger than your current value.

Regards,
Jack Coyle
Rex Healthcare

> --
> From: AMRHAR Brahim[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Sunday, June 10, 2001 7:49 PM
> To:   [EMAIL PROTECTED]
> Subject:  Re: RMAN backup fails with this error !
> 
> I thak you,
> But do you have an idea about the place (file) where I can get and modify
> such parameter.
> On the ADSM Server , all I can manipulate is the
> /usr/Tivoli/tsm/server/bin/dsmserv.opt.
> 
>  -Message d'origine-
> De :Trevor Eastabrook [mailto:[EMAIL PROTECTED]] 
> Envoyé :  lundi 11 juin 2001 01:28
> À :   [EMAIL PROTECTED]
> Objet : Re: RMAN backup fails with this error !
> 
> ANS0326E Node has exceeded max tape mounts allowed.
> 
> Explanation: All the tape mount points for this node are in use.
> System Action: The system returns to the calling procedure.
> User Response: Increase the number of allowed tape mounts for this node on
> the server.
> 
> -Original Message-
> From: AMRHAR Brahim [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 11 June 2001 10:32
> To: [EMAIL PROTECTED]
> Subject: RMAN backup fails with this error !
> 
> 
> Hi all,
> Does anyone get this error message in sbtio.log file when trying to backup
> database via RMAN and TSM ?
> 
> 06/11/01   00:07:48 ANS4993E TDP Oracle AIX ANS0599 TDP for Oracle:
> (80102):
> 06/
> 11/2001:00:07:48 =>(enterprise2) sbtwrite():  ANS0326E (RC41)   Node has
> exceeded max tape mounts allowed.
> 
> Francly, I am newbe to backuping through TSM, but  I do understand nothing
> in 'node has exceeded blablabla...' it makes me crazy ?!.
> And even more , I don't find out the meaning of 'ANS0326E.
> So if you can help me to resolve this,..
> I thank you in advance and Best Regards.
> You can take the Horse to the water, But you can not make him drink.
> DISCLAIMER: "The information in this email and in any attachments is
> confidential and intended solely for the attention and use of the
> addressee(s). If this email is not intended for you, you must not use,
> read,
> distribute or copy it. If you have received this email by mistake please
> call the sender immediately on 64-9-2620772 and erase the email and any
> attachments, and any copies of the same. Internet communications are not
> secure and therefore Woolworths (NZ) Ltd does not accept legal
> responsibility for the contents of this message. Any views or opinions
> expressed are solely those of the author and do not necessarily represent
> those of Woolworths (NZ) Ltd unless specifically stated."
> 

Re: Recovery Log size

[Coyle, Jack]

Per the "Summary of Changes for Tivoli Storage Manager Version 4" section of
the "Quick Start" manual, the "Changes for Version 4 Release 2 - June 2001"
topic lists:

Maximum Size of the Recovery Log Increased
The maximum size of the recovery log is increased to 13GB.
Significantly
increasing the size of your recovery log could also
significantly increase the time
required to restart the server, to back up the database, and
to restore the database.

JRC

> --
> From: Paul Zarnowski[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Thursday, June 21, 2001 9:55 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Recovery Log size
>
> Yes, it made it to the list.  I've been anxiously awaiting a response from
> someone confirming this.  I am unaware of this "special fix", but we could
> certainly benefit from it.
>
> I have heard that some relief *may* be in a new release of TSM, perhaps
> 4.2, which I just received in the mail yesterday.  I haven't had a chance
> to check this.  Anyone else know if this is in 4.2?
>
> ..Paul
>
> At 06:31 AM 6/21/2001 -0700, you wrote:
> >I posted this 2 days ago but saw no responses. Did it make it to the
> list?
> >
> >Hello all,
> >
> >Last week I attended the 2 day DRM class in L.A.. In one the discussions
> we
> >had it was mentioned by the instructor that the size of the recovery log
> >could be over the 5.5gb current limit. I questioned him on this since
> there
> >has been much discussion on it here, quite recently in fact. According to
> >him anyone with this size problem could get a special fix from Tivoli.
> >
> >Has anyone else heard of this? Has anyone had this problem and got this
> >special fix?
> >
> >Geoff Gill
> >TSM Administrator
> >NT Systems Support Engineer
> >SAIC
> >E-Mail:   [EMAIL PROTECTED]
> >Phone:  (858) 826-4062
> >Pager:   (888) 997-9614
>

Re: Archive Question

[Coyle, Jack]

Do the statistics for the archive that are "low" indicate any failures? The
COPYGROUP that we have in place for our ARCHIVE management classes specify a
"copy serialization" of SHARED STATIC, implying that if files change during
the archive attempt, they should be skipped. (The number of attempts is
determined by the CHANGINGRETRIES client option.) If you see a nonzero value
for the number of failures, this may be the source of the discrepancy when
the total byte count is "lower".  Maybe it isn't the cause, but it is
something else to look for.

JRC

> --
> From: Bill Wheeler[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Monday, July 16, 2001 1:12 PM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Archive Question
>
> The information that we are archiving consists of two repositories, DB2
> backups and backup of our Pro/I information.
>
> The information should not change as much as it is.   The repositories
> grow
> daily, and the other backups are consistence on a nightly basis.  We do
> not
> use compression here, due to the information being backed up is not
> considerably large. Our archives average around 69 GB nightly.  I just
> find
> it hard how it can have a range of about 500 MB from the low end to the
> high
> end.  We use these archives as our disaster recovery, I am just perplexed
> on
> the range.  If it was a smaller amount, I would not be as concerned, but
> 500
> MB is a big difference.
>
> The information that use to determine how much was archived is taken from
> the Activity Log in TSM.   Should I look elsewhere to see if this
> information is incorrect?
>
> -Original Message-
> From: David Longo [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 16, 2001 11:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Archive Question
>
>
> What is it you are archiving?  Are you sure that the data would
> not be less on some days?  If there are not a lot of files, then
> look at dsmsched.log on the client and see what files and sizes
> were archived.  This may show why it is less some days, or point
> to files/directories where it is less.
>
> (Maybe you have less data on weekends).
>
> David Longo
>
> >>> [EMAIL PROTECTED] 07/16/01 10:57AM >>>
> Hello *SMers,
>
> I have a question for all those people out there that know more
> about TSM than I do.   Can someone explain to me why there would be a
> fluctuation in the amount of data backed up in an archive?   We run a
> nightly archive on our system, but the amount of GB backed up are
> different.
> I can understand if the information would just be growing but some days it
> is less than the day before.   Any explanation?
>
> We are running
>
> TSM4.1.2.0
> AIX  4.3.3
>
> Any information would be helpful.
>
>
> Thanks in advance,
>
> Bill Wheeler
> AIX Administrator
> La-Z-Boy Incorporated
> [EMAIL PROTECTED] 
>
>
>
> "MMS " made the following
>  annotations on 07/16/01 11:19:32
> --
> --
> --
> This message is for the named person's use only.  It may contain
> confidential, proprietary, or legally privileged information.  No
> confidentiality or privilege is waived or lost by any mistransmission.  If
> you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it, and notify
> the
> sender.  You must not, directly or indirectly, use, disclose, distribute,
> print, or copy any part of this message if you are not the intended
> recipient.  Health First reserves the right to monitor all e-mail
> communications through its networks.  Any views or opinions expressed in
> this message are solely those of the individual sender, except (1) where
> the
> message states such views or opinions are on behalf of a particular
> entity;
> and (2) the sender is authorized by the entity to give such views or
> opinions.
>
> ==
> ==
> ==
>

Re: TSM 4.1.4 - getting maintenance

[Coyle, Jack]

The way I got the maintenance was to stop one directory above the LATEST
directory and then issue the get against LATEST/TAM4140S_AIX.tar.


JRC

> --
> From: Tom Melton[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Tuesday, August 28, 2001 9:53 AM
> To:   [EMAIL PROTECTED]
> Subject:  TSM 4.1.4 - getting maintenance
>
> I am trying to get the latest TSM 4.1 maintenance, and the links on the
> Tivoli pages seem to not work.  I tried a regular ftp session, and get
> disconnected whenever I attempt to access the
> /storage/tivoli-storage-management/maintenance/server/v4r1/AIX/LATEST/
> directory.
>
> Can anyone get to the latest maintenance level for TSM 4.1?
>
>
> Thanks...
>
> Tom Melton
>

RE: Réf. : Re: Resolved: URGENT!! TSM client schedules notrunning (Guillaume Gilbert)

[Coyle, Jack]

Jacques,

The AIX command to change the Receive Pool Buffer size is:

chdev -l ent"x" -a rxbuf_pool_size=2048

where "x" is replace by the appropriate adapter number. However, it is not
as easy as just issuing this command. The adapter must be "offline" in order
for the change to take effect. This is sometimes a difficult state to
achieve. A possible circumvention, if you can arrange for a system recycle,
is to issue the command as:

chdev -l ent"x" -a rxbuf_pool_size=2048 -P

which says to update the ODM only. This can be done while the adapter is
active. You then perform your pre-arranged recycle of the system, and, when
it comes back up, the Receive Pool Buffer size will be set to the new value.
If that is not an option, then you will have to quiesce all traffic through
the adapter (don't forget sysinfod, if you happen to use that facility),
take the adapter down, issue the first listed command, and then put
everything back online. Clearly, I prefer the reboot option - far less
headaches.

Regards,

Jack Coyle
Rex Healthcare
(919) 784-3792
[EMAIL PROTECTED]


> --
> From: Jacques Butcher[SMTP:[EMAIL PROTECTED]
> Reply To: ADSM: Dist Stor Manager
> Sent: Friday, August 15, 2003 2:01 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Réf. : Re: Resolved: URGENT!! TSM client schedules
> notrunning (Guillaume Gilbert)
> 
> Hi Guillaume,
> 
> What command did you use to change the size of the "Receive
> Pool Buffer Size"?
> 
> On Thu, 14 Aug 2003 12:44:09 -0400
>  David E Ehresman <[EMAIL PROTECTED]> wrote:
> > If other people who are experiencing the problem also
> > have receive pool
> > buffer errors and increasing the size of the buffer pool
> > helps, maybe we
> > can get this added to the faq.
> >
> > David
> >
> > >>> [EMAIL PROTECTED] 08/14/03 11:50AM >>>
> > Hi David
> >
> > Thanks for the response. The "No receive pool buffer
> > errors" was at
> > 88934!!! I changed the Receive Pool Buffer Size to 2048
> > (it was at 384)
> > and am hoping everything will
> > be well for tonight. I am having the sysadmins bounce th
> > eschedulers on
> > all the servers that did not work last night just in
> > case...
> >
> >
> > Guillaume Gilbert
> > Conseiller - Gestion du stockage
> > CGI - Gestion intigri des technologies
> > TEL.:  (514) 415-3000 ext 5091
> > Pager:   (514) 957-2615
> > Email : [EMAIL PROTECTED]
> >
> 
> >
> >
> >
> >
> > David E Ehresman <[EMAIL PROTECTED]>@VM.MARIST.EDU>
> > on 2003-08-14
> > 11:04:49
> >
> > Veuillez ripondre ` "ADSM: Dist Stor Manager"
> > <[EMAIL PROTECTED]>
> >
> > Envoyi par :  "ADSM: Dist Stor Manager"
> > <[EMAIL PROTECTED]>
> >
> >
> > Pour : [EMAIL PROTECTED]
> > cc :
> > Objet : Re: Resolved: URGENT!! TSM client schedules
> > not running
> >
> > My problem was also with Prompted nodes only.  Polling
> > nodes ran ok as
> > did croned backups.
> >
> > The tcp setting was the size of the Receive Pool Buffer.
> >  IBM gave me
> > this query to determine if there was a problem:
> >   (echo "";date; netstat -v ent1 | grep "Receive Pool
> > Buffer" )
> >
> > The "No Receive Pool Buffer Errors" line should report
> > zero.  They had
> > me set the "Receive Pool Buffer Size" up to 2048 (AIX
> > 5.1).
> > Unfortunately, I don't remember the command to do that.
> >
> > David
> >
> > >>> [EMAIL PROTECTED] 08/14/03 10:29AM >>>
> > Ok you guys had to start talking about this and now it
> > has happened to
> > me. Nearly all my servers in prompt mode didn't take a
> > backup last
> > night. Nothing in  the activity
> > log and nothing in the dsmsched.logs. I'm running server
> > 5.1.6.4 on
> > AIX
> > 5.1 and clients range from 4.1.2.12 to 5.1.5.15, all
> > Windows (NT and
> > 2k). Most of these servers
> > had the MS patch installed for the blaster virus
> > yesterday. Is this
> > just a coincidence??. I know its not a network problem
> > because all my
> > UNIX clients where running
> > backups all night and those are not scheduled by TSM but
> > by crontabs.
> >
> > So David, what was the tcpip settings you had to change?
> >
> > Thanks
> >
> > Guillaume Gilbert
> > Conseiller - Gestion du stockage
> > CGI - Gestion intigri des technologies
> > TEL.:  (514) 415-3000 ext 5091
> > Pager:   (514) 957-2615
> > Email : [EMAIL PROTECTED]
> >
> 
> >
> > When I had the problem, I did open a PMR and they finally
> > tracked my
> > problem down to a tcp read buffer problem.  They had me
> > adjust the tcp
> > values and the problem has not reoccurred.
> >
> > David
> 
> Jacques Butcher
> TCM (Technology Corporate Management) Software Engineer
> Cell:  +27 (0)84 676 0329
> Tell:  +27 (0)11 483-2000
> Fax:   +27 (0)11 728-3656
> Nat. IT Diploma, MCSE, IBM Tivoli Storage Manager 5.1
> Certified, NetVault Certified, IPSTor Certified,
> IBM Certified Specialist - Enterprise Tape Solutions
> Version 2
> 
> ==
> Download ringtones, logo

Re: increasing mount points

[Coyle, Jack]

Geetha,

The first thing I would check is whether your drives are available for use
by the TSM server. It may be that the errors prior to your stopping the
server, manually unloading the drives and then restarting the server
resulted in the server marking the drives (or the known paths to the drives)
as unavailable. Try issuing the commands "query drive" and "query path" to
see what state the TSM server perceives the drives to be in. If the output
reports them as "unavailable", then either (or possibly both) the "upd
drive" or "upd path" commands can be used to make the drives available
again. HTH.

Regards,

Jack Coyle
Rex Healthcare
[EMAIL PROTECTED]


> --
> From: Geetha Thanu[SMTP:[EMAIL PROTECTED]
> Reply To: ADSM: Dist Stor Manager
> Sent: Friday, November 21, 2003 1:14 PM
> To:   [EMAIL PROTECTED]
> Subject:  increasing mount points
>
> Hi all,
>
> I had 2 problems in tivoli.
> 1.one the database was full
>  when the backup was going on.
> 2. the error insufficient mount points.
>
> I increasd the database size with all ur help.
> again when i stopped and started tivoli it gave these
> 2 errors
> ***
> ANR8872E No path is available for drive DRIVE01 - could not unload volume
> CDFD17 from drive.
> ANR8358E Audit operation is required for library AUTOLIB.
> ANR8470W Initialization failure on drive DRIVE01 in library AUTOLIB.
> ANR8872E No path is available for drive DRIVE02 - could not unload volume
> CDFD12 from drive.
> ANR8358E Audit operation is required for library AUTOLIB.
> ANR8470W Initialization failure on drive DRIVE02 in library AUTOLIB.
> ANR8439I SCSI library AUTOLIB is ready for operations.
> *
>
> when i gave dismount it was unable to dismount and said
> volume cdfd17 not available.so i stoped tivoli and manually
> unmounted the tape and restarted tivoli.these r the messages
> when i restarted it again.
> 
> ANR8470W Initialization failure on drive DRIVE01 in library AUTOLIB.
> ANR8470W Initialization failure on drive DRIVE02 in library AUTOLIB.
> ANR8439I SCSI library AUTOLIB is ready for operations.
> _ANR0812I Inventory file expiration process 1 completed: examined 43447
> objects, deleting 0 backup objects, 0 archive objects, 0 DB backup
> volumes,
> and 0
> recovery plan files. 0 errors were encountered.
> ANR0985I Process 1 for EXPIRATION running in the BACKGROUND completed with
> completion state SUCCESS at 10:27:35 AM.
> _
>
> The server is up and running.but when i take backup
> or restore it is giving the following error.
>
> ---
> ANR0567W Retrieve or restored failed for session 32 for node SUNSERVER
> (SUN SOLARIS) - insufficient mount points available to satisfy the
> request.
> ANR0403I Session 32 ended for node SUNSERVER (SUN SOLARIS).
>
> ANR0535W Transaction failed for session 43 for node SUNSERVER (SUN
> SOLARIS)
> - insufficient mount points available to satisfy the request.
> ---
>
> Pls guide me what to do.It is very urgent and i am a new bie
> pls help.waiting for reply
>
>
> Thanks
> Geetha Thanu
> Bioinformatics
> CDFD,Hyderabad.
>
>
>
>
>
>
>
>
>
> -
>
>

Re: increasing mount point

[Coyle, Jack]

Try the following two commands:

update path server1 drive01 srctype=server desttype=drive library=autolib
online=yes
update path server1 drive02 srctype=server desttype=drive library=autolib
online=yes

Assuming they execute without error, follow with a "query path" command to
see if the paths to the drives are now online.

HTH.

Regards,
Jack Coyle
Rex Healthcare
[EMAIL PROTECTED]


> --
> From: Geetha Thanu[SMTP:[EMAIL PROTECTED]
> Reply To: ADSM: Dist Stor Manager
> Sent: Friday, November 21, 2003 2:51 PM
> To:   [EMAIL PROTECTED]
> Subject:  Re: increasing mount point
>
> Coyle,
>
> Thank u Coyle for ur immediate reply.As u said I have given the query
> drive
> and query path and the results r as below
>
> Library Name Drive Name   Device Type On-Line
>   --- ---
> AUTOLIB  DRIVE01  DLT Yes
> AUTOLIB  DRIVE02  DLT Yes
>
>
>
>
> Source Name Source Type Destination Destination On-Line
> NameType
> --- --- --- --- ---
> SERVER1 SERVER  AUTOLIB  LIBRARYYes
> SERVER1 SERVER  DRIVE01  DRIVE  No
> SERVER1 SERVER  DRIVE02  DRIVE  No
>
> From the above result I feel the drives are online but
> the AUTOLIB library is not online.
> Now what I should do to put it on line and make the server
> work as normal as before.Pls guide me to proceed.
> Thanks to all who guide with my problems
>
> Thank u
> Geetha Thanu
>
>
>
>
>
>
>
>
>
>
> -
>
>

Re: increasing mount point

[Coyle, Jack]

You should not have to stop and start the server. From a drive / path
perspective, everything is as good as it is going to get. However, your
original append did show that the TSM server viewed the status of the
contents of your AUTOLIB library as inconsistent, The error message that you
listed

ANR8358E Audit operation is required for library AUTOLIB

indicates that, at a minimum, a library audit is in order before proceeding
further. Issue the command

audit library autolib

to allow the server to re-inventory the tapes that are in the library. If
that completes successfully, then you should be ready to use the library
again. If you would like to verify that before diving into a restore
operation, see if you can check one of your scratch tapes in that library
out and then back in. That should exercise both of the drives and verify
that they are, once again, operational. HTH.

Regards,
Jack Coyle
Rex Healthcare
[EMAIL PROTECTED]

> --
> From: Geetha Thanu[SMTP:[EMAIL PROTECTED]
> Reply To: ADSM: Dist Stor Manager
> Sent: Friday, November 21, 2003 4:10 PM
> To:   [EMAIL PROTECTED]
> Subject:  Re: increasing mount point
>
> Coyle,
>
> As u told i have given the commands and now query path gives
> the following result
>
> ANR1722I A path from SERVER1 to AUTOLIB DRIVE01 has been updated.
>
> ANR1722I A path from SERVER1 to AUTOLIB DRIVE02 has been updated.
>
> Source Name Source Type Destination Destination On-Line
> NameType
> --- --- --- --- ---
> SERVER1 SERVER AUTOLIB LIBRARY Yes
> SERVER1 SERVER DRIVE01 DRIVE Yes
> SERVER1 SERVER DRIVE02 DRIVE Yes
>
> Hope now evrything is fine.shld I have to start and stop the server
> can I try restoring things now.Pls reply.
>
> Thank u so much for helping.
> Geetha Thanu
> Bioinformatics
> CDFD,Hyderabad.
>
>
>
>
>
>
>
>
>
> -REPLY TO-
> Date:Fri Nov 21 15:51:09 CST 2003
> FROM: Coyle, Jack  <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: increasing mount point
> Try the following two commands:
>
> update path server1 drive01 srctype=server desttype=drive library=autolib
> online=yes
> update path server1 drive02 srctype=server desttype=drive library=autolib
> online=yes
>
> Assuming they execute without error, follow with a "query path" command
> to
> see if the paths to the drives are now online.
>
> HTH.
>
> Regards,
> Jack Coyle
> Rex Healthcare
> [EMAIL PROTECTED]
>
>
> > --
> > From: Geetha Thanu[SMTP:[EMAIL PROTECTED]
> > Reply To: ADSM: Dist Stor Manager
> > Sent: Friday, November 21, 2003 2:51 PM
> > To:   [EMAIL PROTECTED]
> > Subject:  Re: increasing mount point
> >
> > Coyle,
> >
> > Thank u Coyle for ur immediate reply.As u said I have given the query
> > drive
> > and query path and the results r as below
> >
> > Library Name Drive Name   Device Type On-Line
> >   --- ---
> > AUTOLIB  DRIVE01  DLT Yes
> > AUTOLIB  DRIVE02  DLT Yes
> >
> >
> >
> >
> > Source Name Source Type Destination Destination On-Line
> > NameType
> > --- --- --- --- ---
> > SERVER1 SERVER  AUTOLIB  LIBRARYYes
> > SERVER1 SERVER  DRIVE01  DRIVE  No
> > SERVER1 SERVER  DRIVE02  DRIVE  No
> >
> > From the above result I feel the drives are online but
> > the AUTOLIB library is not online.
> > Now what I should do to put it on line and make the server
> > work as normal as before.Pls guide me to proceed.
> > Thanks to all who guide with my problems
> >
> > Thank u
> > Geetha Thanu
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > -
> >
> >
>
> -
>
>

Re: NDS Backup error

[Coyle, Jack]

Bruce,

One of our W2K / NT / NetWare gurus researched this very problem at our
site. For completeness, I have included his entire report to our group on
the problem. The bottom line is that it is a Novell issue. Hope the attached
helps.

Regards,
Jack Coyle
Rex Healthcare
(919) 784-3792
[EMAIL PROTECTED]

 Our Resource's Findings
--

> After futile attempts to exclude the Scross object in the dsm.opt file on
> RexNDS, I found out the following:
>
> The error showing up in the dsmerror.log (shown below) is blamed (by
> Tivoli) on a bad Novell API that allows an invalid object to be created on
> TSM.
>
>   ANS1228E Sending of object '.[Root].O=REX.OU=Remote.OU=Scross'
> failed
>   ANS1304W Active object not found
>
> The object is interpreted as a file when it is an object or some variation
> thereof, further explained in the TSM document included below.  Once the
> problem occurs, the object is not recognized correctly so it will never
> match up.  They list a work around to get rid of the object causing the
> error, but say this could occur in the future without the API fix.  They
> post an incident number (2642846) to reference when calling Novell for the
> API fix.
>
> The steps are listed in red how to manually remove the object from the TSM
> filespace.  It appears the error arrived about the time the TSM
> maintenance and upgrade from 5.1.7 to 5.1.8 occurred.  For that reason, it
> may be best to remove the offending item at this time.  Novell does not
> list anything currently regarding this issue but I reported to Novell
> support our request for an API fix.  If you would prefer, I could open an
> incident to chase down an API fix immediately.
>
> To remove these objects from ITSM Server storage that will not be
> inactivated/deleted during incremental backups, either of the following
> can be done.
>
> 1. Rename the filespace on the ITSM server, and run a full backup from
> ITSM client to create a new filespace. Once a new clean filespace is
> created, customers can delete the old filespace.
>
> 2. Individual objects can be deleted with undocumented delete command
> specifying the specific High Level and Low Level identifiers for the
> object as it is stored in ITSM Server storage. Users would need to contact
> Support in determining the specific HL and LL qualifiers for these
> objects, as well as getting command syntax for delete command.
>
> I included the entire Tivoli document below.  I am awaiting a response
> from Novell, but wanted to provide this information in case you wanted to
> rectify the daily error populating the logs at present.  Given the pros
> and cons of renaming the filespace just to remove this error, let me know
> what you prefer.
>
>
> DCF Document ID: 468 - IBM Tivoli Storage Manager: ANS1228E ANS1304W
> "Active object not found" During Incremental Backup of NDS
> Problem Desc: "ANS1228E ANS1304W "Active Object Not Found"" error
> occurs. IBM Tivoli Storage Manager (ITSM) client fails NDS backup on
> Novell with this error message. Complete messaging is as follows: From
> dsmerror.log: ANS1228E Sending of object '.[Root].O=.OU=.CN='
> failed ANS1304W Active object not found
>
> Solution: ITSM displays these errors when it attempts to inactivate an
> object stored on the ITSM Server and is unable to. ITSM determines that an
> object has been deleted from the client NDS tree after building the
> directory tree as shown in the trace snippet below. (traceflags service)
>
> Built the following directory tree...
> dirtree.cpp (2254):
> dirtree.cpp (2254): .O=AMGruppe
> incrdrv.cpp (2730): Time to get query information: 0.06 sec.
> session.cpp (2777): Sess (xxx) FREELOCK lock action by thread (xxx):
> incrdrv.cpp (5864): PrivIncrFileSpace: Traversing: .[Root]
> .O=AMGruppe.OU=03.OU=K.OU=AO
> pstsa.cpp (1934): comparing target service AMGRUPPE to target
> service 'AMGRUPPE'.
> ntwfilio.cpp (3232): ntwSMSScan: resource
> (.OU=AO.OU=K.OU=03.O=AMGruppe.[Root])
> path(.OU=AO.OU=K.OU=03.O=AMGruppe.[Root]) connection 5 nameSpace 8
> ntwfilio.cpp (3308): NWSMTSGetNameSpaceTypeInfo (OPEN) : sms_rc = 0
> ntwfilio.cpp (3308): on connection 5 and sequence (OPEN) 0, (ATTRIB) 0
> ntwfilio.cpp (3338): NWSMPutOneName (OPEN) : sms_rc = 0
> ntwfilio.cpp (3338): on connection 5 and sequence (OPEN) 0, (ATTRIB) 0
> ntwfilio.cpp (3126): PRE-NWSMTSScanDataSetBegin (OPEN) : sms_rc = 0
> ntwfilio.cpp (3126): on connection 5 and sequence (OPEN) 0, (ATTRIB) 0
> ntwfilio.cpp (3138): NWSMTSScanDataSetBegin (OPEN) : sms_rc = 0
> ntwfilio.cpp (3138): on connection 5 and sequence (OPEN) 57DC2AF0,
> (ATTRIB) 0
> ntwfilio.cpp (3465): NWSMGetDataSetName: sms_rc = FFFBFFFC
> on connection 5 and sequence (OPEN) 57DC2AF0, (ATTRIB) 0
> ntwfilio.cpp (3465): (SMDR-1.0-24) An internal error has occurred.
> Either the list has no more entries or the specified name space type does
> not exist.
>
> ITSM compares what

Re: AIX Disk questions

[Coyle, Jack]

Try

for i in 18 19 20 21 22 23 24 33 ; do
chdev -l hdisk$i -a pv=yes
done

from the AIX command line when signed on as root (assumes ksh shell).

Jack Coyle
Rex Healthcare

> --
> From: Gill, Geoffrey L.[SMTP:[EMAIL PROTECTED]]
> Reply To: ADSM: Dist Stor Manager
> Sent: Wednesday, April 10, 2002 9:23 AM
> To:   [EMAIL PROTECTED]
> Subject:  AIX Disk questions
>
> This is an AIX question so may be off subject a little.
>
> I just had a second SSA drawer installed with 16 disks, only 7 of them
> seem
> to be missing depending on how you want to look at them. LSPV shows this
> for
> those disks. I've never seen this before so I'm not sure how to
> "initialize"
> if you will to get them to show up in Smitty, can't see them there. I'll
> be
> using these for my disk pools and DB and Log mirrors.
>
> hdisk18noneNone
> hdisk19noneNone
> hdisk20noneNone
> hdisk21noneNone
> hdisk22noneNone
> hdisk23noneNone
> hdisk24noneNone
> hdisk33noneNone
> Others show this:
>
> hdisk25000143405656e7baNone
> hdisk26000143405657922bNone
> hdisk27000143405657e7d1None
> hdisk2800014340565826e1None
>
> Thanks for the help. Oh, lsdev -Cc disk does show the disks.
>
>
> Geoff Gill
> TSM Administrator
> NT Systems Support Engineer
> SAIC
> E-Mail:   [EMAIL PROTECTED] 
> Phone:  (858) 826-4062
> Pager:   (877) 905-7154
>