Database save
Joe Bloggs
I am using Local mode IDMS database Release 14.1. It has 5 areas. I use 5
physical files. As a normal procedure before taking the database save I am
using the program IDMSBCF to unlock the database.
Last time while doing I got the following results.
UNLOCK AREA SEGANLP.AREA100;
Status = 1 SQLSTATE = 01610 Messages follow:
DB002367 C1M353: Area SEGANLP.AREA100 was not locked.
UNLOCK AREA SEGANLP.AREA200;
Status = 1 SQLSTATE = 01610 Messages follow:
DB002367 C1M353: Area SEGANLP.AREA200 was not locked.
UNLOCK AREA SEGANLP.AREA300;
Status = 1 SQLSTATE = 01610 Messages follow:
DB002367 C1M353: Area SEGANLP.AREA300 was not locked.
UNLOCK AREA SEGANLP.AREA400;
Status = 1 SQLSTATE = 01610 Messages follow:
DB002367 C1M353: Area SEGANLP.AREA400 was not locked.
UNLOCK AREA SEGANLP.AREA500;
Status = -4 SQLSTATE = 60002 Messages follow:
DB002300 C-4M353: DBIO Error:3005 Function:18 Page:540001
Only for the FILE500 I got the error message as above. But when I re-run the
job It was successful.
Does anyone help in this regard? And also could you please give some more
information about the IDMSBCF program?
Thanks in anticipation,
Chandru
Jayaraman Karunakaran
The UNLOCK utility is used to remove an external lock against a database
area. The database areas may remain with an external lock in cases such as
if any earlier job that has locked the database areas has aborted in between
before issuing a FINISH command.
To save a database segments/areas, you can use the IDMSBCF utility BACKUP.
This has to be on local mode and the database segments/areas that is to be
saved has to be on retrieval mode. This will prevent other users from
changing the contents of the area during the save. To vary the database to
retrieval you can use DCMT V SEG "segment-name" RET or DCMT V AREA
"area-name" RET.
If the database physical files have to be saved, the simplest way is to use
the IDCAMS REPRO to backup the physical file. For doing this you can vary
the database segments to retrieval and take the back up.
For information regarding IDMSBCF (CA-IDMS batch command facilities) and the
various utility statements that can be used, you can refer the IDMS MANUALS
: CA-IDMS UTILITIES.
Regards,
Karunakaran (Karan)
CSS Development Database Administrator
* Karuna...@bt.com
cdBritish Telecom,
Angel Centre, 403 St. John Street,
London
EC1V 4PL
* 020 7843 7461
* 020 7843 7393
Chris Hoelscher
*** I am using Local mode IDMS database Release 14.1. It has 5 areas. I use
5
*** physical files. As a normal procedure before taking the database save I
am
*** using the program IDMSBCF to unlock the database.
*** Last time while doing I got the following results.
It concerns me GREATLY that you are running an UNLOCK as "normal procedure"
. An unlock does not SOLVE a PROBLEM, it "heals" a SYMPTOM. By UNLOCKING a
LOCKED area without understanding why, you are opening yourself to data
corruption (both Physical and logical, and who is to say which is worse?).
I would recommend removing the UNLOCK from "normal procedures" and instead
concentrate on why the area is locked in the first place.
but to answer you immediate question:
ABND3005 3005
Reason: An attempt to open a database file has failed. Check the JCL for a
missing or invalid DD (MVS), ASSGN statement (VSE), or for a mismatch
between the DMCL page size and the disk dataset block size. For VSAM files,
check that the cluster has been properly defined using the IBM IDCAMS
utility and that the buffer in the DMCL being used is large enough to hold
the control interval (not just the page size). Also the database page must
be at least 8 bytes smaller than the control interval. Under VSAM, this
error can also occur if insufficient storage exists for the required VSAM
control blocks in the storage pool (DC/UCF) or in the partition (local
mode). Other possible reasons: An attempt to open an unallocated file.
chris hoelscher