ADSM-L

query event misses schedule

1996-06-27 15:10:29
Subject: query event misses schedule
From: Dave Cannon <dcannon AT VNET.IBM DOT COM>
Date: Thu, 27 Jun 1996 12:10:29 MST
My guess is that the PROD2 schedule was updated, so Query Event would not
display events prior to the the update.  Query Schedule F=D gives the date
of last update, so you can confirm this.  Another possibility is that
the Delete Event command was executed.  The Admin Reference describes
conditions that must be met for events to be displayed using the Query Event
command.

Dave Cannon
ADSM Server Development
------------------------------- Referenced Note ---------------------------
I am running five production ADSM servers on MVS 2.1.02.  Each is a clone, same
I am running five production ADSM servers on MVS 2.1.02.  Each is a clone, same
domains, same policies, just different nodes.  Yesterday I noticed that a Unix
shell script that I wrote to check that all backups had completed was only
reporting on the first event and not the second, and this only happened in one
server.

adsm> q sched

Domain       * Schedule Name    Action Start Date/Time      Duration Period Day
------------ - ---------------- ------ -------------------- -------- ------ ---
HD_DOMAIN      PROD             Inc Bk 12/30/1995 22:00:00      4 H    1 D  Any
HD_DOMAIN      PROD             Inc Bk 12/30/1995 22:00:00      4 H    1 D  Any
HD_DOMAIN      PROD2            Inc Bk 12/30/1995 02:00:00      4 H    1 D  Any

adsm>  q event hd_domain prod*

Scheduled Start      Actual Start         Schedule Name Node Name     Status
-------------------- -------------------- ------------- ------------- ---------
06/26/1996 22:00:00                       PROD          CPHPHLP1      Future
06/26/1996 22:00:00                       PROD          CPHPHLP1      Future
06/26/1996 22:00:00                       PROD          CPFSAT2A4     Future
06/26/1996 22:00:00                       PROD          THDHUB        Future
06/26/1996 22:00:00                       PROD          CPHPDEV1.HOM- Future
                                                         EDEPOT.COM
06/26/1996 22:00:00                       PROD          CPFSPCLS      Future
06/26/1996 22:00:00                       PROD          GW3270        Future
06/26/1996 22:00:00                       PROD          CPHPHOT1      Future

Today The same command returns:

adsm> q event hd_domain prod*

Scheduled Start      Actual Start         Schedule Name Node Name     Status
-------------------- -------------------- ------------- ------------- ---------
06/27/1996 02:00:00  06/27/1996 02:21:40  PROD2         CPFSAT2A2     Completed
06/27/1996 02:00:00  06/27/1996 02:21:40  PROD2         CPFSAT2A2     Completed
06/27/1996 02:00:00  06/27/1996 02:00:25  PROD2         CPFSAT1A3     Completed
06/27/1996 02:00:00  06/27/1996 02:17:21  PROD2         ACM           Completed
06/27/1996 02:00:00  06/27/1996 02:02:26  PROD2         CPHPSQA1      Completed
06/27/1996 02:00:00  06/27/1996 02:01:53  PROD2         CPHPHLP2      Completed
06/27/1996 02:00:00  06/27/1996 03:17:49  PROD2         CPHPACM2      Completed
06/27/1996 02:00:00  06/27/1996 02:50:19  PROD2         CPHPIS02      Completed
06/27/1996 22:00:00                       PROD          CPHPHLP1      Future
06/27/1996 22:00:00                       PROD          CPFSAT2A4     Future
06/27/1996 22:00:00                       PROD          THDHUB        Future
06/27/1996 22:00:00                       PROD          CPHPDEV1.HOM- Future
                                                         EDEPOT.COM
06/27/1996 22:00:00                       PROD          CPFSPCLS      Future
06/27/1996 22:00:00                       PROD          GW3270        Future
06/27/1996 22:00:00                       PROD          CPHPHOT1      Future

I talked to my MVS counterpart yesterday and thought he had fixed it, but
apparently he did not.  It just went away.  Anyone seen anything like this?

Dazed and confused....
<Prev in Thread] Current Thread [Next in Thread>