Accessing a native VSAM file in IDMS is failing and the following messages are observed in the CV joblog:
07.17.27 STC14372 IEC161I 066(002)-026,DF003,DF003,D7005F00,,MPC000,CRD.PRODV.CRDCIS, 778
778 IEC161I CRD.PRODV.CRDCIS.DATA,UCAT.PROD.ONLINE
07.17.27 STC14372 +IDMS DC016922 VSOPEN ERR=003 DDN=UNKNOWN
07.17.27 STC14372 +IDMS DC205006 V3 T176127 NVSAM ERR - CGPPIA29 FUNC=18 FDBK=168 R15=08 NVST=06 R0=000 NVERR=013
07.17.27 STC14372 +IDMS DC205006 V3 T176127 DDN=D7005F00 AREA=SGVSAM.AREA-7005 SET=
Release : All supported releases
Component : IDMS/DB
The IEC161I message with a return code of 066 means the application (which in this case is IDMS) looked for the VSAM dataset on a particular volume and did not find it.
The most likely cause of this error is that the native VSAM file was deleted and redefined on a different volume, while the CV was up, but it was not deallocated from the IDMS CV. IDMS is unaware that the file is on a different volume and attempts to address it on the original volume.
The native VSAM file must be deallocated from the IDMS CV while it is redefined. The correct sequence of commands is as follows:
DCMT VARY AREA segment.area OFFLINE
DCMT VARY AREA segment.area CLOSE
DCMT VARY FILE segment.file DEALLOCATE <== for all files related to the area
Then delete and re-create the VSAM file.
DCMT VARY FILE segment.file ALLOCATE <== for all files related to the area
DCMT VARY AREA segment.area OPEN
DCMT VARY AREA segment.area ONLINE
This situation is not possible with normal BDAM files because they cannot be deleted unless they are deallocated from the IDMS address space.