ADSM-L

[no subject]

2015-10-04 18:08:48
     I believe I see two different things below... I think this will answer
     most of your questions...
     1) Scheduled client events may be commands (local operating system
     commands) Ex. we do our novell incrementals by a scheduled event that
     is a command "nightly.ncf" that fires up a seperate dsmc incremental
     against each logical drive, running them  concurrently.  Output from
     these DO NOT go into the sched.log but into the window of the
     associated dsmc (and then only if you don't use "quiet")

     2) Scheduled administrative commands, such as "backup db", "upd stg
     tapepool recl=80", "upd stg tapepool recl=100", "del volhist t=dbb
     tod=-7", etc... show up two ways: A) query event * type=admin
     B) in the activity log you will see where scheduled event BLAH
     initiates and finishes BUT that has nothing to do with the results of
     what the command is trying to do!  IE. scheduled event BACKUPDB
     initiated.... it issues a backup db t=f s=y ...   scheduled event
     BACKUPDB completed ...  THAT IS ONLY WHERE THE COMMAND WAS ISSUED,
     YOUR BACKUPDB COULD HAVE STILL FAILED 'CAUSE THERE WERE NO SCRATCH
     VOLUMES or the such...

     Now on a server scheduled client restore the sched.log on the client
     would contain all the specifics... but you would still need to get
     that sched.log where you could get to it.   There is also this neat
     little "postschedcmd" that lets you do any client opsys native
     command, such as transfer (ftp, mail, xmit, whatever) the sched.log to
     a central point.

     It is all very slick!  I like it anyway, but I am kind'a twisted.
     Everything is available for a person to customize adsm (with a little
     local code writing) to run itself and page you if it thinks it is
     having problems... (that is with a (different than adsm) system you
     can send pages from)

     Hey, a simple one if you have an aix machine around is

     dsmadmc -console -serv=mvsserver -id=blah -pass=blah |&
     loop doing "read -p consoleln" and assemble the complete message then
     cat $consoleln | grep ^AN[R,S][0-9][0-9][0-9][0-9][E,S,D,C] |
     pagehelp $consoleln
     continue looping...

     AND IF IBM WOULD BE CONSISTANT AND END ALL THEIR MESSAGES WITH A "."
     LIFE WOULD BE EASIER! (sorry IBM, had to throw that one in...)

     I'd give you my code but it is probably some big corporate secret...
     and I'd hate to find out the hard way.
     later
          Dwight



______________________________ Reply Separator _________________________________
Subject: Does scheduled command information get written to a log?
Author:  ADSM-L (ADSM-L AT VM.MARIST DOT EDU) at unix,mime
Date:    4/15/97 7:21 PM


We are currently running ADSM Server V1 for MVS and are upgrading to V2
shortly.  I understand that you can schedule Admin commands, including
restores with V2.

Do the results of these commands get logged to the DSMSCHED.LOG?

Specifically, would I know how many files were restored, how many failed
and how long it took from a scheduled restore?

Dianne Sharp
Operations Analyst
ISS CUSTOMER SUPPORT
Ext 4208

--MimeMultipartBoundary--
=========================================================================
<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=