IDMSBCF unlock

Discussion created by ca.portal.admin on Aug 6, 2010
Latest reply on Aug 6, 2010 by ca.portal.admin
I executed PGM=3DIDMSBCF - UNLOCK SEGMENT DSCC01T1 and received the
following error? =20


+IDMS DC329000 TMGR error 00: DBIO error                 RC=3D0BBB

+IDMS DC208001 IDMS job abending with abend code TMGR

+IDMS DC208001 #ABEND from Module IDMSTMGR at Location 18F3ED18 Offset
01424E =20

+IDMS DC208001 SYSTEM mode registers at entry to #ABEND  =20


Not sure what this means. Anyone have an idea?


Thanks, =20


Michael J. Barta

Mainframe Database || Infocrossing, a Wipro Company || 11707 Miracle
Hills Drive, Omaha NE, 68154|| ': 402.496.8564 ||7: 402.496.8676 || :: **Think Green - Please print


Confidentiality Note: This e-mail, including any attachment to it, may =
contain material that is confidential, proprietary, privileged and/or =
""Protected Health Information,"" within the meaning of the regulations =
under the Health Insurance Portability & Accountability Act as amended. =
If it is not clear that you are the intended recipient, you are hereby =
notified that you have received this transmittal in error, and any =
review, dissemination, distribution or copying of this e-mail, including =
any attachment to it, is strictly prohibited. If you have received this =
e-mail in error, please immediately return it to the sender and delete =
it from your system. Thank you.
IDMS 3rd-party providers forum


Re: IDMSBCF unlock
" The x'0BBB' translates to decimal 3003. As indicated in the CA-IDMS Messages
and Codes Reference, an ABND3003 indicates
""An attempt to validate the database page number has failed.""
This can only occur when a physical page in the dataset for his area does not
match the definition in the DMCL. There are only a few ways this can occur:
1- The page range in the physical area doesn't match the DMCL definition
2- The page size of the physical area doesn't match the DMCL definition
3- The JCL is pointing to the wrong dataset
4- The DMCL has the file mapped to the wrong buffer
To verify the pages size, page range, and DSN, use LOOK DMCL. In the out-
put, you should see lines that look similar to this display:

. Page Low High Page
. Area Name Group Page Page Size DDNAME
. --------------- ----- ---------- -------- ------ --------
. EMPDEMO.EMP-DEMO-REGION 0 75,001 75,050 4,276 EMPDEMO
.------- Data File -------- Mode Stat Pg-Size Fl-Type DD-Name

Verify that the DDname & DSN in your JCL match the ones for your file.
If it is correct, there are a few other things that you can try:
1- You can run a PRINT PAGE on the first page lised in the DMCL for this
area, to see if it also fails with the 3003.
2- If the Buffer page size in the DMCL isn't at least as large as the area
pagesize, you can update the DMCL to use a different buffer for this area,
regenerate the DMCL, then try the Unlock again.
3- If you havbe other CVs that mirror this one, check the DMCL definitions in
those CVs to see if the definition for this area is the same as in this
4- Verify that the Unlock is run with the same DMCL as the CV.
5- You could try restoring this area from a backup, if you have one.

If none of the above resolve the error, then you will need to open an
issue with CA and we would probably require a dump to find out what the
problem is.

Edward McKinney
CA Technologies
Sr Sustaining Engineer
Tel:  +1-508-628-8171
Fax: +1-508-628-8715