Hi,
  Here is a code fragment I use to make the console ring for each mount
request:

                clear
                echo Starting ADSM console...
#
#                some tricky stuff here to get beeping messages
#
                mknod .piper.$$ p
                dsmadmc -id=$ID -password=$PASSWORD -consolemode  >
.piper.$$ &
                awk -F'|' '{
        f = 0
        b = 0
        l = length( $1 );
        for( i = 1; i <= l ; ++i ){
                if( substr( $1, i, 8 ) == "ANR8319I" ||  substr( $1, i,
8) == "ANR8308I" ){
                        b = 1;
                }
                if( substr( $1, i, 25 ) == "started for administrator"
){
                        f = 1;
                }
                if( substr( $1, i, 23 ) == "ended for administrator" ){
                        f = 1;
                }
        }
        if( f == 1 ){
                continue;
        }
        if( b == 1 ){
                printf " %s", $1 ;
        } else {
                printf "%s", $1 ;
        }
        for( i = l; i < 80; ++i ){
                printf " ";
        }
        printf "\n";
}' < .piper.$$
        rm .piper.$$

The script also does some filtering to reduce the number of messages
that the operators see.  Note that I use -consolemode rather than
-mountmode (though it would probably work there as well).
This is part of a series of wrapper scripts I wrote to allow us to
This is part of a series of wrapper scripts I wrote to allow us to
perform daily operations with relatively unskilled help.  In addition to
providing an operator interface for daily operations, the scripts also
manage backup of primary pools to secondary pools, tape reclaimation,
and database, device configuration file, and volhistory file backups,
limiting the number of tape drives and time consumed by these
operations.  Given enough
( number_of_tape-based_storage_pools + 2 + network_factor * [[
dsm_factor * dsm_clients * users/dsm_client * storage/dsm_client *
delta_storage/dsm_client ] + [ hsm_factor * hsm_clients *
users/hsm_client * storage/hsm_client * delta_storage/hsm_client ]] )
tape drives  we could use the ADSM administrative scheduler for some of
these operations, but...

Jim
> ----------
> From:         Peter Zutenis[SMTP:pzutenis AT IBM DOT NET]
> Sent:         Wednesday, June 25, 1997 10:17PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: remote console support and wnt adsm servers
>
> Leonard,
>
> I had a similar problem here. I am running the adsm server on AIX and
> I did have an aix client running in -MOUNT mode for   the operators,
> but the console was silent (no beeps etc). Operators would often miss
> a message to mount a tape causing havoc.
>
> I solved the problem by using our existing MVS automation packakge
> called AUTOM8XC (from Legent, now Computer Associates). This product
> runs on an OS/2 PC and is the central message router for
> MVS,VM,VSE,VMS,VTAM,CICS etc here. I just run a telnet on this pc, the
> Ops analyst define what messages to pick up and now mount messages for
> ADSM ring merrily on the autom8xc console - annoying the operators
> into action and making them mount tapes !.
>
> Hope this helps you a little.
>
> Best Regards,
>
> Peter Zutenis.
> Philip Morris Information Services Ltd
> Moorabbin, Australia
> E-Mail : pzutenis AT ibm DOT net
>
>
>       -----Original Message-----
>       From:   Leonard Boyle [SMTP:SNOLEN AT VM.SAS DOT COM]
>       Sent:   Thursday, 26 June 1997 09:35
>       To:     ADSM-L AT VM.MARIST DOT EDU
>       Subject:        remote console support and wnt adsm servers
>
>       We are learning a little about working with an adsm windows NT
> server.
>
>       One of the questions that have come up is what is the best way
> to automate the
>       console messages  for operator support.  Most of the  time there
> should  be no
>       operator support required, but once in a while there can be an
> exception.
>
>       For now  we can  place an  adsm admin client  with the  console
> option  in the
>       operator area.  But we really do  not want to  add consoles that
> they  have to
>       eyeball every few minutes for possible work.
>
>       We would like to  have something that will in real time  scan
> the messages and
>       send the important  ones to a central console (most  likely
> another platform).
>       (With our vm adsm server we use the vm:operator product for
> this).
>
>       For example  a request to check  on a dlt tape  drive i/o error
> could  be send
>       over to an  hpux window, or an  vm:operator screen or a mvs
> console. Then the
>       operator could go to the wnt box to handle the problem/request.
>
>       Before we reinvent  the wheel, Is someone else doing  something
> like this with
>       adsm servers. A perl script on AIX? A NT resource kit tool?
> Other?
>
>       Thanks len
>
>
> ----------------------------------------------------------------------
> ---
>       Leonard Boyle, Mainframe support            snolen AT vm.sas DOT com
>       SAS Institute Inc.                          ussas4hs@ibmmail
>       Room E206                                   (919) 677-8000 ext
> 6241
>       203 SAS Campus Drive
>       Cary NC 27513
>
>