ADASAV RESTORE FILE function

, , ,
1

Hello,

Restore prod file, 55 to ADA225 using ADASAV RESTORE FILE function.
With your help I had done similar job. I used RESTORE FMOVE function.

But now I had to accomplished this task by using ADASAV RESTORE FILE utility.

I had done following prior to any thing:

  1. Backup ADA225 (target)
  2. Analyzed ADREP161 & ADREP225.(reports for source and target)
  3. Diagnose “Physical Layout of the Database” &“File Space Allocations” in ADREP161 (source) for file 55.
  4. Check the following figure for File 55 (TP-CERTEXCA-ADA )
  5. Check ADREP225 to confirm file already is not existed.

Please see the attached file for the detail.
I have noticed 1141755 RABN is not exits in target.

Do I need to assigned it first prior to use ADASAV RESTORE FILE utility?
Do I need to allocate space prior to use ADASAV RESTORE FILE utility?

Thank You

ASS0326.doc (159 KB)

2

Dawar,

I am not following what you are trying to do here.

ADASAV RESTORE FILES=
and
ADASAV RESTORE FMOVE=

are the same exact utility. The only difference is that FILES= requires that the files be stored into the same original RABNs utilized by the file that it occupied when it was saved to tape. FMOVE= restores the files to any RABNs.

The only way you are going to have FILES= work is if you ensure file 55 is occupying the RABN range that the file occupied on your backup tape. If possible, you can save the file from db 225, delete it and then restore it specifying the file go to the blocks that you need it to occupy as identical to your source database backup. Then and only then will an ADASAV RESTORE FILES= work, though I don’t know why you would want to do that.

The other catch… your production environment (db 161) is larger, and the associator parts are all in RABNs higher than 1141755. Your maximum ASSO block in db 225 is 314986. It is IMPOSSIBLE to use RESTORE FILES= when db 161’s block ranges for file 55 is higher than your max ASSO block for db 225 unless you now go add space to db 225 so that your RABN range includes those that file 55 allocates on your source db.

Why is it important to you to use FILES= instead of FMOVE=? Didn’t you successfully restore file 55 from db 161’s backup to db 225 using FMOVE? What are you trying to accomplish that you didn’t already?

3

I think my team wants something similar to do this:
They want me to add space.

The other catch… your production environment (db 161) is larger, and the associator parts are all in RABNs higher than 1141755. Your maximum ASSO block in db 225 is 314986. It is IMPOSSIBLE to use RESTORE FILES= when db 161’s block ranges for file 55 is higher than your max ASSO block for db 225 unless you now go add space to db 225 so that your RABN range includes those that file 55 allocates on your source db.

4

Why do you have to guess what is expected from you ???

There are multiple options re. how to add space

http://techcommunity.softwareag.com/ecosystem/documentation/adabas/ada824mfr/adamf/util/adadbs-INCREASE.htm
http://techcommunity.softwareag.com/ecosystem/documentation/adabas/ada824mfr/adamf/util/adadbs-ADD.htm

Neither of this would I recommend to be used by someone who needs two weeks or more
to vaguely understand ADASAV RESTORE …

5

They insisted on using ADASAV RESTORE FILE function not ADASAV RESTORE FMOVE function.

But on other hand they also agreed FMOVE approach was correct. May be they want me to handle both situation. thanks

6

OK… so this is for you to learn.

Please look at the ADAFRM utility and ADADBS INCREASE utilities for this.

http://techcommunity.softwareag.com/ecosystem/documentation/adabas/ada824mfr/adamf/util/_utilover.htm

Please also backup your complete db before you start and adhere to any standards your shop has. We use full-pack allocations for our databases to remove some of the complexity, but here is a sample of JCL we use at our shop (edited for generic consumption):

//jobname JOB (VS00200,NSNS),'DBA',REGION=4096K,TIME=1440,           
//  MSGCLASS=T,CLASS=N,NOTIFY=&SYSUID                                 
//* RESTART=STEP3                                                     
//*================================================================== 
//*    CATALOG A SECOND EXTENT OF ASSO ON A DIFFERENT VOLUME          
//*   1.  NO FREE SPACE CAN EXIST ON ANY OF THE PREVIOUS VOLUMES      
//*   2.  UNCATALOG THE DATASET ( DO NOT DELETE )                     
//*   3.  FORMAT AND RE-CATALOG THE DATASET DISP=(MOD,CATLG,CATLG),   
//*                                         VOL=SER=(VOL1, VOL2,...)  
//*   4.  ADADBS - INCREASE THE DATA                                  
//*   5.  ADAREP - MAKE SURE THERE ARE NO '******' IN VOLSER COLUMN   
//* !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
//* !!! THE ADAREP MUST NOT RUN IN THE SAME JOB AS THE INCREASE AND   
//* !!! FORMAT. IT WOULD GIVE ERRONEOUS RESULTS. RUN THE JOB DPREP    
//* !!! AFTER THIS JOB.                                               
//* !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
//*================================================================== 
//*================================================================== 
//*    IEFBR14 : UNCATALOG ASSOR1 (DO NOT DELETE THE DATASET)         
//*================================================================== 
//STEP1   EXEC  PGM=IEFBR14                                           
//FL1    DD  DSN=hlq.ASSOR1,DISP=(OLD,UNCATLG),UNIT=3390         
//*                                                                    
//*==================================================================  
//*    ADAFRM : ALLOCATE AND FORMAT THE DATABASE COMPONENTS            
//*                                                                    
//*    TO CALULATE SIZE, MULTIPLY THE # VOLUMES BY 3338.               
//*    EXAMPLE: WE ARE ADDING 3 VOLUMES TO hlq.ASSOR1.                    
//*    IN THIS CASE, SIZE = (3338 * 3) = 10014.                        
//*                                                                    
//*    TACK VOLUMES ADAxxx, ADAyyy, AND ADAzzz AFTER ADAmmm.           
//*                                                                    
//*                                                                    
//*==================================================================  
//STEP2     EXEC PGM=ADARUN,COND=(0,NE)                                
//STEPLIB   DD   DISP=SHR,DSN=hlq.ADABAS.LOAD                    
//DDASSOR1 DD   DISP=(MOD,CATLG,CATLG),DSN=hlq.ASSOR1,           
//         SPACE=(CYL,(0,3338)),UNIT=3390,                             
//  VOL=SER=(ADAaaa,ADAbbb,ADAccc,ADAddd,ADAeee,ADAfff,ADAqqq,ADAhhh,  
//           ADAiii,ADAjjj,ADAkkk,ADAlll,ADAmmm,ADAxxx,ADAyyy,ADAzzz)  
//SYSUDUMP  DD   SYSOUT=X                                              
//DDDRUCK   DD   SYSOUT=X                                              
//DDPRINT   DD   SYSOUT=X                                              
ADARUN PROG=ADAFRM,
ADARUN SVC=249   
ADARUN DEVICE=8391
ADARUN DBID=225   
ADARUN DSF=YES    
ADARUN MODE=SINGLE,PLOGRQ=NO
/*
//DDKARTE   DD   *                                                    
ADAFRM ASSOFRM SIZE=10014,NUMBER=1,DEVICE=8391                         
/*                                                                    
//*================================================================== 
//*     ADADBS : INCREASE THE ASSO                                    
//*                                                                   
//*     INCREASE THE SAME AMOUNT AS THE FORMAT STEP ABOVE             
//*================================================================== 
//STEP3     EXEC PGM=ADARUN,COND=(0,NE)                               
//STEPLIB   DD   DISP=SHR,DSN=hlq.ADABAS.LOAD                   
//DDASSOR1  DD  DSN=hlq.ASSOR1,DISP=SHR                         
//DDDATAR1  DD  DSN=hlq.DATAR1,DISP=OLD                         
//DDTEMPR1  DD  DSN=hlq.TEMPR1,DISP=OLD                         
//DDSORTR1  DD  DSN=hlq.SORTR1,DISP=OLD                         
//DDWORKR1  DD  DSN=hlq.WORKR1,DISP=OLD                         
//SYSUDUMP  DD   SYSOUT=X                                             
//DDDRUCK   DD   SYSOUT=X                                             
//DDPRINT   DD   SYSOUT=X                                             
//DDCARD    *
ADARUN PROG=ADADBS,
ADARUN SVC=249   
ADARUN DEVICE=8391
ADARUN DBID=225   
ADARUN DSF=YES    
ADARUN MODE=SINGLE,PLOGRQ=NO
/*
//DDKARTE   DD *                                                      
ADADBS INCREASE ASSOSIZE=10014                                         
/*                                                                    
//*  
//

Please adapt to your own shop standards. This sample only increases ASSO, but you can follow the same logic for increasing DATA. Please also run an ADAREP when you have completed to be sure your volumes are allocated and your block ranges aren’t assigned to ******.

7

Wolfgang,

I think Dawar is coming to us to mentor him when L.A. County is giving him exercises to perform on their test database to give him experience.

It makes more sense now. They wanted him to figure out what he needed to do to make the FILES= work. I kinda provided the answer, though he still has work to do to make it all work in his shop.

We need to keep this in mind with our future responses.

8

Understood, Brian,

and although I should have been more elaborate I stick to my response:

Hands off INCREASE or ADD without having sound understanding of how
to do a full database backup (as you suggested), a database restore,
AND how to (re)create a database from scratch, simply because
chances are VERY high one will end up with a database in a state
that requires it to be rebuilt.

9

Absolutely. My guess is if Dawar gets himself into that kind of mess, his next task will be to fix it. I also guess that db 225 here can be blown away and re-created by his team mates if he gets in over his head, but he should heed your advice. Read all about these utilities, take a full db backup, and know how you will restore it or re-create it if you have to.

I went apoplectic over “power tools” in the other discussion thread, and I have to believe this is by design and that this is how they are teaching him.

10

Thanks for concerns.

I have done many good stuff so far, includes restore DB etc.

But still new in this arena but as u see I am hard worker and keen to learn always.

thanks

11

ADA225 is using VOL=SER=(ADA60C,ADA60D)
Both are 99% used.

can not add more space?

what to do?

12

Why can’t you add space using the utilities we explained will do that?

13

When these volumes are full you will need to talk to your site’s storage
administrators for a free volume (assuming one is enough, check ADAREP
first to see how much space is actually allocated to the source database),
we really can’t guess that from here …

14

Why can’t you add space using the utilities we explained will do that?

Do I need to add volume or space in this situation?
Volumes are 99% full.

I think I need to do as Wolfgang said. I had sent email to them yesterday.

thanks

15

Yes, you need to ask for volumes to be clipped if you need to add space to your database.

Just a side note: after you format and add these to your database, from the “outside” they will appear to be fully utilized. ADAREP shows you what is used “internally”.

16

Where should I see in adrep?

17

The physical layout section lists the volume names, there is no “volume overview” however.

18

I wrote the JCL, actually most of the stuff I took from the existing one.

I have explain step by step comments. (blue highligted)

Can you pl. confirm?

I did define following as:

ADADBS INCREASE ASSOSIZE=833 – 833 cylinders are to be added to an Associator on the associator’s existing device type [u]

But confused confused in that

ADAFRM ASSOFRM SIZE=833,DEVICE=8390

I am trying to understand each step.

thanks
FORfRM.rtf (6.37 KB)

19

you are formatting the increase area only. You don’t want to format the whole ASSO area as that will wipe out data needlessly.

20

I need to setup a job to increase the number of ISN by 12000. ISN is stored in AC.
The utility to be used is ADADBS. Which utility function to use?

how many RABN will be required to increase number of ISN by 12000?

Please find attached file contains some figures from report and JCL

thanks
ForForumQuickAna4Vol.pdf (255 KB)