In days of yore, long, long ago, and far, far, away, it made sense to code at the step level.
OS/MVT used a contiguous storage algorithm and reserved that storage for the life of a job step.. If STEPB required more storage that STEPA, the possibility existed for significant execution delays until a contiguous block of real storage large enough for STEPB to execute became available. Great amounts of time and effort were spent determining actual real storage requirements and maintaining cascading region parameters to ensure that there was always enough contiguous real storage for the next job step. Potentially large amounts of real storage were "wasted" on small (real storage) steps executing before the large (real storage) step. All of the above went the way of the dodo when OS/MVS (specifically, virtual storage) became available. IMO, it no longer makes any sense to even worry about it. I do not believe any benefit (or not) would even be measureable. HTH, <snip> If there is a job with 200+ steps. Is it better to have region coded at the JOBCARD level or the STEP Level? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
