Prevent errors during migration to a new zWS release by allocating files via EQQPCSxx jobs to have the same sizes and other characteristics as in the previous release

Currently the provided jobs (tailored by EQQJOBS) like EQQPCS01 and EQQPCS02 allocate tiny files with default characteristics.  However most customers make changes, like increasing the allocation of the files (more cylinders) or modifying the MAXRECL size of certain files (AD, JS, LT) or making the files extended or DSNTYPE=LARGE to support the million jobs feature (CPDATASPACE parameter). All these changes are lost when the allocation jobs are run for the new release, if the customer is not careful to manually copy over the changes made to the previous release.  Forgetting to make these changes can have disastrous consequences - long down times, loss of data, etc .  One way to fix this would be to have EQQJOBS gather information about the current file sizes and characteristics and use these in creating the EQQPCSxx JCL.  It could also be possible to provide a program to run before the migration job (EQQICNVS member in SEQQSAMP) to compare file sizes, MAXRECL, etc for the old release and new release.  For example if the old NCP was allocated as 500 cylinders and the new release NCP is allocated as 4 cylinders, this discrepancy could be flagged.  It would be better if this can be done proactively as it seems many customers just submit the JCL created by EQQJOBS without checking to see if the allocations are correct compared to their current zWS implementation.