New journal files have been redefined and formatted larger than the files currently in operation. Following a ARCHIVE JOURNAL ALL, the new journal files were assigned to DD statements and the IDMS CV started and went into WARMSTART. The following errors were produced:
DC016109 XTIOT disabled for dynamic allocation
DC390009 V101 STARTING IDMS-CV/DC INITIALIZATION - R19.0 SP 4
DC391511 V101 Lock Manager for Warmstart initialization Complete
DC202001 V101 Starting WARMSTART
DC205007 V101 READ ERROR on File J1JRNL
DC205007 V101 CURRBN=000024E6 CURBMA=2C4DB3C8 CURFCB=2A511550 FDBK=00000000
DC205019 V101 IOSTATUS=3016 VERB=021 ERRSW=041 MOD=033 IOP=007F4C48
DC202010 V101 3016 = DBIO STATUS
DC202021 V101 J1JRNL FILE in ERROR
DC202036 V101 IDMSWARM ERRSWX= 018 MODNO= 049
DC202022 V101 RECOVERY did NOT START - See ERROR MESSAGE
DC202014 V101 ** IOP Address 807F4C48 ** Work area address 007F52C8
DC391008 V101 WARMSTART Failure - IOSTATUS=3009
Release : 19.0
Component : CA IDMS/DB
The 3016 error means the file doesn't match the size defined in the DMCL, see the documentation section ABND3016:
3016 Requested RBN beyond the range of the file.
A read or write was requested for a block that is beyond the defined size of the file.
To change the size of the disk journals you have to use a procedure similar to Changing the Page Size of a Disk Journal, perform the following steps:
The 3016 error means IDMS tried to read beyond the end of the journal file dataset. This indicates the CV is using the updated DMCL with the larger number of blocks for each disk journal file but may be accessing the old datasets that have fewer blocks.
Check the disk journal DDs in the startup JCL are pointing to the new formatted journal file datasets.