BAD BIND ON AREA
Run IDMSBCF with the following input:
UNLOCK AREA SYSTEM.DDLDCLOG;
At one site I worked at – they ALWAYS placed an unlock before the archive log
For many years this caused a rc=4 if the area wasn’t locked (which this same site considered an error)
Trying to unlock a not-locked area may or may not still result in a rc=4 – my memory is fading …..
Technology Architect, Database Infrastructure Services
Technology Solution Services
123 East Main Street
Louisville, KY 40202
(502) 476-2538 or 407-7266
Yes it will still get RC=0004 and 4 is a warning, not an error. My ARCHIVE LOG job has always contained the Unlock as well.
IDMSBCF 19.0 CA IDMS Batch Command UNLOCK SYSLOG.DDLDCLOG; Status = 1 SQLSTATE = 01610 Messages follow: DB002367 C1M353: Area SYSLOG.DDLDCLOG was not locked. ARCHIVE LOG; CA IDMS DB/DC Print Log Utility CA IDMS DB/DC is a ProprieGJJ04I Release 19.0 Licensed from
*** PAGE 000030002 STATUS 0000 080918 04.29.58 6 S *** PAGE 000032000 STATUS 0000 081318 07.49.59 6 L
Retrieving data ...