Defined two new database Files and Areas.
The new DMCL was compiled with new areas but the new database files were defined with the parameter EXTENDED..
Here are the messages when abended :
IEC143I 213-B8,IFG0194D,IDMST0,IDMST0,VSDF229,423F,PBST82, 121
+CCSR010E RHDCOS00 S213 at 00026B48 LMOD IDMSTAG8 CSECT RHDCOMOC +0026D0 IDMST0 N/A IDMST0
+CCSR021I OWNER = CA IDMS R19.0
+CCSR022I MODULE = RHDCOMOC FMID = CAGJJ00 RMID = CAGJJ00
+CCSR061I PSW: 07541000 80000000 00000000 00E42456
+CCSR062I ILC: 02 INTERRUPT CODE: 0D
+CCSR067I COMPLETION CODE S213 REASON CODE 000000B8
Extended Format files (DSNTYPE=EXTREQ or EXTPREF) are not supported as Database or Journal files. Attempts to open such files with IDMS software will result in System abend 213 reason code B8.
Support for DSNTYPE=LARGE database files was added in release 17.0. Still must be a single volume. IDMS does not support multi-volume files
CA IDMS Release Summary r17 SP1
Support for Large and Extended Format Files
CA IDMS now supports large format single volume files in z/OS for database
and journal files and both large and extended format for work files
dynamically created by the REORG utility. Both large and extended format
files can have more than 65,535 tracks on a single volume.
For more information about large and extended format files, see the
This feature requires z/OS version 1.7 or later.
Large Format Database and Journal Files
The ability to allocate large format database and journal files means that fewer files need to be defined, referenced, and managed leading to a reduction in the administrative effort associated with large database environments.
To use this feature, define a database or journal file whose size in tracks exceeds 65,535. When creating the file, specify DSNTYPE=LARGE in your JCL and be sure to allocate the file on a single volume.