Do you know the resource consumption of your z/VSE workload ?
Ingolf24 120000DRN3 Visits (2501)
I accompanied many z/VSE migrations to new releases or new hardware over the last years. In some cases we were involved after the migration, because the system didn't meet the expectations. In nearly all of those cases performance data of the system prior to the migration was not available, such as CPU utilization or I/O rates.
Therefore I recommend to measure the resource consumption (CPU utilization, I/O rates, ...) regularly, Not just, if you plan a migration, but also to detect e.g. resource shortages, growing workloads and for future planning purposes. Always use days with comparable workloads.
In case of a migration please measure your workload before the migration and after each migration step. That is e.g. before a migration to new hardware (processor, disk, ...) and after that, before migration to a new z/VSE release and after that.
Please do not migrate to new hardware and a new z/VSE release in one step. My recommendation is to migrate to new hardware first with the current release, wait some weeks and then migrate to a new release.
To measure your workload you may use performance monitors from vendors or functions / tools that are included in z/VSE or that are available on our web pages for download.
E.g. to measure the CPU utilization / activity of your z/VSE system you may use the QUERY TD attention routine (AR) command, the IUI system activity dialog or the CPU monitor tool.
See the blog