IDMS

Got this error on a new copy of my global DMCL, has not been regenned since release 16.4 on z/OS 1.13, running 17.1 now. Had to recycle CV's, luckily I have my CV's recycled daily in production. Anyone else seen this?

[color=#1704c1] V DMCL NC
Error Auditing/Building the new DMCL. BLDR returned a status of 04. See Log.
Release Number or OPSYS ID. changed between current DMCL and New DMCL.
V11 ENTER NEXT TASK CODE: CA IDMS release 17.0 tape GJH01M node TCV1 [color]

Log message

[color=#1704c1]11:08 IDMS DB347015 V11 T1 Error detected in DMCL AUDIT routine [color]

Message:

[color=#1704c1]DB347015
<<<<<<<< snip >>>>>>>
MESSAGE TEXT Error detected in DMCL AUDIT routine

DEFINITION DB347015 Error detected in DMCL AUDIT routine
While validating a DMCL VARY NEW COPY an internal
error was detected in the DMCL AUDIT routine.
The detailed reason for the error is displayed on the
terminal.
COMMENTS Module(s) = IDMSBLDR
V11 ENTER NEXT TASK CODE: CA IDMS release 17.0 tape GJH01M node TCV1 [color]

Thanks,
Steve Harmeson

Hi Steve,

This is par for the course. I had the same issue going from rel.15 to rel.17. You have to relink the DMCL. Then recycle CV. Then you can relink the DMCL again and vary new copy. The error will go again. This is also true going from rel. 17 to rel. 18 which I am going through the process now.

John N. Baloga

Thanks John, with add to my plans from here on out, 18.0 is next for me too.

Steve Harmeson

This happened to me in V17->V18 as well!

Chris hoelscher

I'm an IDMS newbie. Would anyone have sample JCL to relink the DMCL?

Mike Barta

Hi Mike, what is your OS and release of IDMS?

Steve Harmeson

z/os 1.11 and I'm upgrading from v16 sp7 to v17 sp1

Mike Barta

Yes we had to regenerate all our DMCLs when we went to 17 as the release number changed in the control block. Once we did and cycled all the CVs we had no problem after that with new copies.

Kirk Miller