Re: ADSM Problems

I am in the process of testing V3 on OS390 also.
1.  I did not allocate a new database volume, but I did create a new
storage pool volume with the following JCL:
//*
//*********************************************************************
//* ADSM-B:  ALLOCATE BACKUPPOOL STORAGE GROUP VOLUME                 *
//*                                                                   *
//ALLOC    EXEC PGM=IEFBR14
//STGBK01   DD DSN=SYST.ADSM.STORAGE.POOL003,
//             DISP=(NEW,CATLG,DELETE),
//             RECORG=LS,AVGREC=M,SPACE=(100,(1)),UNIT=SYSALLDA,

//             VOL=SER=TLH101
//*
//*********************************************************************
//* ADSM-B:  FORMAT BACKUPPOOL STORAGE GROUP VOLUME                   *
//*                                                                   *
//FORMAT1  EXEC PGM=DSMFMT,TIME=1440,DYNAMNBR=300,COND=(0,NE,ALLOC),
//             PARM='/SYST.ADSM.STORAGE.POOL003'
//SYSPRINT  DD SYSOUT=*
//SYSTERM   DD SYSOUT=*
//DSMAMENG  DD DSN=SYST.ADSM.SANRMSG(ANRMENU),DISP=SHR
//*
This allocated the volume with no expiration date.  (It is SMS managed)

         SYST.ADSM.STORAGE.POOL001.DATA
THL101
  6840   ?   1 3390     VS   ?         ?     ? 1993/10/22 1999/12/31
1998/01/06
---------------------------------------------------------------------------
----
----
         SYST.ADSM.STORAGE.POOL002
         SYST.ADSM.STORAGE.POOL002
*VSAM*
                        VS

---------------------------------------------------------------------------
----
----
         SYST.ADSM.STORAGE.POOL002.DATA
         SYST.ADSM.STORAGE.POOL002.DATA
THL101
  2145   ?   1 3390     VS   ?         ?     ? 1993/10/22 1999/12/31
1998/01/06
---------------------------------------------------------------------------
----
----
         SYST.ADSM.STORAGE.POOL003
         SYST.ADSM.STORAGE.POOL003
*VSAM*
                        VS

---------------------------------------------------------------------------
----
----
         SYST.ADSM.STORAGE.POOL003.DATA
         SYST.ADSM.STORAGE.POOL003.DATA
TSMS23
  2145   ?   1 3390     VS   ?         ?     ? 1998/01/07 ***None***
1998/01/07
---------------------------------------------------------------------------
----
----
I did notice my old volumes have an expiration date. (Not SMS managed.)
I did notice my old volumes have an expiration date. (Not SMS managed.)





smithrr AT MARITZ DOT COM on 01/08/98 11:14:00

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Claudia Masters/Texas Utilities)
Subject:  ADSM Problems




        I have a couple of questions:
1. When we setup new volumes for either the database or recovery log, it
puts an expiration date of 12-31-99 on each dataset.  Why??
2. I am testing version 3.  We are on an MVS/OS390 server, and the
workstation is a windows '95 machine.  The problem is that I can not get
the schedule to run, without bouncing the scheduler right at the time
the schedule should start.  This doesn't even work all the time, any
clues??
Rick Smith
Maritz, Inc.
Storage & Security Administration
smithrr AT maritz DOT com
(314) 827-1584