ADADBS ALLOCATE FILE= 55
ACSIZE = 11B
DEVICE= 8390
is it correct?
It won’t like the spaces, so that will have to be
ADADBS ALLOCATE FILE=55
ACSIZE=11B
DEVICE=8390and DEVICE is optional, it is only required when you have multiple ASSOs with
different device types and you want to force ADADBS to allocate that new
extent on a particular device (=block size), if you have just one ASSO it will
make no difference, and it will make no difference when you have multiple
ASSOs of the same device type.
I fact that will have to be either
ADADBS ALLOCATE FILE=55,ACSIZE=11B,DEVICE=8390or
ADADBS ALLOCATE FILE=55
ADADBS ACSIZE=11B
ADADBS DEVICE=8390Please note: my assignment was as below:
Device: 8390–Trks/Cyl: 15–ASSO: 3440:14–DATA: 6518:8–Work:10706:5–PLOG/RLOG:10706:5—CLOG: 8904:6–
TEMP/SORT/DSIM:8904:6–Notes: 1
Setup a job to increase the number of ISN by 12000.
The utility to be used is ADADBS. Read the manual to find out which utility function to use.
Use the information provided to calculate how many RABN will be required to increase number of ISN by 12000. Each ISN takes 3 byte.
Previously we had calculate for asso
3440/3 = 1146
12000/1146=10.47
So I need 11 RABNs for 12000 ISN
Do I need to do same with Data too? Or do not need it.
This is probably very silly question.
thanks
As Mogens tried to explain, there is absolutely no need to do that manually
at all, when extents (no matter if ASSO or DATA) for a file run full Adabas will
automatically create a new one, based on a defined formula, when you
want to override that automatism and create additional extents of a certain
size before the current last one runs full you are free to do so.
When what you are doing is all about training yourself on how to use ADADBS ALLOCATE
than just go ahead and try whatever you like, but there’s no magic, what you do for
ACSIZE will work just the same way for DSSIZE et al, but if you want to see what it
does and where you find the new extents in your ADAREP just go ahead 
Here is a JOB
//STEP01 EXEC PGM=ADARUN,REGION=4096K
//STEPLIB DD DSN=ADABAST.COMMON.LOADLIB,DISP=SHR
//SYSUDUMP DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//DDDRUCK DD SYSOUT=*
//DDASSOR1 DD DSN=ADABASDB.ADA225.ASSO,DISP=SHR
//DDDATAR1 DD DSN=ADABASDB.ADA225.DATA,DISP=SHR
//DDCARD DD DSN=ADABAST.COMMON.CNTRL(DBS225S),DISP=SHR
—Adabas common cntrl library member DBS225S…
(ADARUN PROG=ADADBS,PLOGRQ=NO,MODE=SINGLE,DEVICE=8390,SVC=233,DBID=225 ADARUN UEX3=USEREX3 USER EXIT 3 PHONETIC EXIT)
//DDKARTE DD *
ADADBS ALLOCATE FILE=55,ACSIZE=11B,DEVICE=8390
/*
//DDWORKR1 DD DSN=ADABASDB.ADA225.WORK,DISP=OLD
//*
//STEP02 EXEC PGM=IEFBR14
//D1 DD DSN=ADABASDB.ADA225.ASSO,
// DISP=(OLD,UNCATLG,UNCATLG)
//*
is it ok?
Dawar said:
Please note: my assignment was as below: I feel like it’s unfair you are asking us to spoon-feed you the answers, some of which is more like force-feeding because you don’t accept the help easily. I am sure there are points to be had for being resourceful and tapping the community for information as that is a key to success on the job. That said, I believe if L.A. County has given you these assignments as a training course and to test your knowledge and capacity to do the job, if you are successful because we told you what to do and not because you understand it, it’s not fair to anyone and doesn’t prove a thing.
Why don’t you just try it, if it abends it wasn’t then go back and investigate the cause.
This is what I would call a “boolean job”, it will either give you a “yes, works” or “no, does not work”,
if it were potentially dangerous like INCREASE I would have told you.
The worst thing that can happen is that you may have to get rid of an utility DIB entry,
but I guess you’ve been down that road before.
The only thing I question is - why do you run this in mode=single ?
I had done JCL Scan as
//STEP01 EXEC PGM=ADARUN,REGION=4096K
//STEPLIB DD DSN=ADABAST.COMMON.LOADLIB,DISP=SHR
//SYSUDUMP DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//DDDRUCK DD SYSOUT=*
//DDASSOR1 DD DSN=ADABASDB.ADA225.ASSO,DISP=SHR
//DDDATAR1 DD DSN=ADABASDB.ADA225.DATA,DISP=SHR
//DDCARD DD DSN=ADABAST.COMMON.CNTRL(DBS225S),DISP=SHR
//DDKARTE DD *
ADADBS ALLOCATE FILE=55,ACSIZE=11B,DEVICE=8390
/*
//DDWORKR1 DD DSN=ADABASDB.ADA225.WORK,DISP=OLD
//*
//STEP02 EXEC PGM=IEFBR14
//D1 DD DSN=ADABASDB.ADA225.ASSO,
// DISP=(OLD,UNCATLG,UNCATLG)
//*
!JCK on above JCL
NO JCL error
I am confused on DISP=(OLD,UNCATLG,UNCATLG)
It does not make sense to me either, but again, we here can not guess
what whoever wrote this had in mind, so it might be a better idea asking
your technical leads if there is a reason we just don’t see.
We do not need step 2.
I have run job as:
//STEP01 EXEC PGM=ADARUN,REGION=4096K
//STEPLIB DD DSN=ADABAST.COMMON.LOADLIB,DISP=SHR
//SYSUDUMP DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//DDDRUCK DD SYSOUT=*
//DDASSOR1 DD DSN=ADABASDB.ADA225.ASSO,DISP=SHR
//DDDATAR1 DD DSN=ADABASDB.ADA225.DATA,DISP=SHR
//DDCARD DD DSN=ADABAST.COMMON.CNTRL(DBS225S),DISP=SHR
//DDKARTE DD *
ADADBS ALLOCATE FILE=55,ACSIZE=11B,DEVICE=8390
//DDWORKR1 DD DSN=ADABASDB.ADA225.WORK,DISP=OLD
//*
But from 2 hour job is running and I can see following message in log
JOB15746 IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE TO INCS
JOB15746 IEF863I DSN = ADABASDB.ADA225.WORK INCSIZE RC = 04
JOB15746 *IEF099I JOB INCSIZE WAITING FOR DATA SETS
thanks
is it ok to stop job while is running?
Of course, the job is not even running, as the message says it is WAITING,
which is to be expected when DISP=OLD is specified while the nucleus is active.
I cancel the job.
I check as
n.sd.st
prefix ADA*
and see that DB is running.
I ran job again. But not succesful few times. I had made soem changes like I remove //DDWORKR1 DD DSN=ADABASDB.ADA225.WORK,DISP=OLD from the job.
I stop the server and restart get the message is done. I did not catch the time.
It was in single mode, what is different btw single and multiple mode?
I think one of mode requires DB down.
MODE=SINGLE requires the db to be down
that was the reason of hanging job.
Many thanks
hang on I am running same job with multi mode. DB is up
Job is not done yet but getting similar message in log
IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE TO INCS
IEF863I DSN = ADABASDB.ADA225.WORK INCSIZE RC = 04
*IEF099I JOB INCSIZE WAITING FOR DATA SETS
do you think DISP=old causing the issue
I know it is, that’s why I pointed you to it