The InsertSlashHack message is less than informative, but was intended
more for development use in diagnosing problems than end-user use. That is
essentially the case for any message that does not have a message number.
It is desirable that such messages be re-evaluated for their usefulness,
rewritten, or at least preceded with ANS9999E, but that is another issue
to be dealt with for another day.

Sometimes, including the case of ANS1304W, the root cause if often
non-deterministic from the client's perspective. At any rate, there are
times when it is appropriate to contact IBM technical support for further
assistance, and this might be one of those times. In fact, if you review
the current "user response" section for message ANS1304W (which was
updated in version 5.3), you will see that it includes the following text:

*  If the reason this message occurred can not be determined and the
   message occurs when the operation is tried again, then contact IBM
   support for further assistance. ...

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-06-07
06:36:02:

> Hi, Matthew -
>
> Another of those cases where the client programming fails to explain
> problems that it finds and could interpret, resulting in a lot of
> wasted customer time.
>
> I believe that this condition can occur where there is a conflict in
> file system object type. For example, the object was originally
> backed up and stored in TSM storage as a directory, but in the
> current backup the TSM client finds that object to be a file. The CLI
> output is not helpful in this case, except to verify existence, as
> the CLI remains exasperatingly primitive, even in TSM 5, failing to
> provide any way to report the object type. You could instead use the
> GUI, drilling down to that point in the filespace, to identify the
> object type; or do a more arduous Select in the BACKUPS table for
> TYPE. (In worse cases, there may be non-visible binary bytes in the
> name which throw things off, put there by the file's creator, or by
> file system corruption.)
>
> You'll have to poke around to ascertain what the story is, and
> possibly compensate by object renaming in the client file system.
>
>     Richard Sims
>
> On Jun 7, 2005, at 8:27 AM, Warren, Matthew (Retail) wrote:
>
> > 06/07/05   12:51:08 WARNING: InsertSlashHack missing dirDelimter,
> > continuing...
> > 06/07/05   12:51:08 ANS1228E Sending of object
> > '/prod/bsmsb01/app/generis/var/out/import/actioned' failed
> > 06/07/05   12:51:08 ANS1304W Active object not found
> >
> >
> > I cant see anything on IBM's site other than one InsertSlashHack
> > problem
> > that doesn't appear to be related, and various ANS1304W problems
> > that do
> > not appear to be related.
> >
> > A query backup of the offending directory shows an Active file exists
> >
> > Node Name: SKANE-0
> > Session established with server RUTLAND: AIX-RS/6000
> >   Server Version 5, Release 2, Level 2.0
> >   Server date/time: 06/07/05   13:03:10  Last access: 06/07/05
> > 12:50:04
> >
> > tsm> q ba /prod/bsmsb01/app/generis/var/out/import/actioned
> >              Size      Backup Date        Mgmt Class A/I File
> >              ----      -----------        ---------- --- ----
> >             96  B  06/04/05   04:20:04    MC_RMM_UNI  A
> > /prod/bsmsb01/app/generis/var/out/import/actioned