Charles, This is a complex migration to a yet unknown. Look at the program (rexx) as a way to get multiple datasets attributes without accessing each of them to get the attributes.
The problem we try to solve is not the issue. I migrated clients data between platforms many times but this is not the problem we are trying to solve. ITschak *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: [email protected] **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* בתאריך שבת, 18 באוק׳ 2025 ב-1:03 מאת Charles Mills <[email protected]>: > I guess I don't understand the question. I fail to see how collecting data > set attributes solves an insufficiently sized CPU. > > I thought the problem was re-creating "PC" backed-up datasets with the > correct "mainframe" attributes (RECFM, LRECL, VB boundaries, etc.). > > DFSMSDSS restore does that. > > TERSE makes the records FB so they can survive to/from PC FTP. > > Charles > > On Fri, 17 Oct 2025 21:45:01 +0300, Itschak Mugzach < > [email protected]> wrote: > > >Migration it self is not an issue. The problem is the disk space and cpu > >sized that are insufficient. So we plan for click and set an environment > >that might not exist in next IPL (even on same day). > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
