I don't know why we consider IMS database, maybe I missed it is
information from OP.
However generally speaking it is important to know whether your dataset,
despite PS or VSAM, it "regular" dataset or "special" dataset.
Regular - I mean it is just like any other dataset with all the rules
and features.
Special - examples: DFSMShsm journal, RACF db, SMF SYS1.MANx, IODF, etc.
Each of them *looks like* PS or VSAM, but there are additional rules and
constraints which have to be followed.
I don't know IMS, but I vaguely remember that for Adabas moving "PS
files" from 3380 to 3390 or just from 3390-3 to 3390-9 required special
treatment. In other words it was not enough to copy it with IEBGENER.
So, it is important to know the application and check application's
documentation. Or ask someone.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 23.12.2025 o 23:05, Steve Thompson pisze:
Quickly, IMS is a Hierarchical DB, as opposed to relational.
Then IMS has various types of files (I've forgotten all the names and
acronyms). Of course I threw out all my IMS manuals during our
downsizing and moving (since I hadn't had anyone contact me that was
using IMS for 15+ years).
sigh.
Regards,
Steve Thompson
On 12/23/2025 2:30 PM, Jon Perryman wrote:
On Tue, 23 Dec 2025 08:19:18 +0400, Peter <[email protected]> wrote:
So allocating via ISPF 3.2 and using that IDCAMS repro is not correct ?
For IMS non-vsam databases, does IDCAMS REPRO work correctly? I only
mention this because why is there a utility to copy them? I suspect
getting 100,000 IMS transaction requires a database organization with
pointers of some sort. Maybe someone familiar with IMS knows. Ask
your IMS sysprog.
I'm not sure why someone recommended ALTER ADDVOLUMES instead of ISPF
3.2 since you were able to get it working.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
