On Thu, 8 May 2008 18:05:31 -0400, Rob Scott wrote: >Tom > >A very common usage of that field is store some info about the level of the z/OS system packs (eg "put level"). A site can add a simple jobstep to their sysres cloning/propagation JCL to update the field using a simple zap. Hi Rob,
Some sites certainly do that but certainly not all sites, nor is the format common by any reasonable definition. Some folks stick the date (in various formats) into the field, some plant the PUT or ESO level into the field, some use both. I've seen many combinations. I have seen sites use the field to identify different systems in a shop and (in much larger entities) to identify different shops throughout the corporation. I don't know whether outsourcers make use of the field in a manner similar to Todd's idea. Smaller sites tend not to be aware or be too burdened with other work to bother updating the field at all. To Wayne's point, there is no common, standard place in any IBM-standard data structure that holds such a Universal Customer-ID value. (I agree with Wayne.) The CPUID ought to be unique (at least until PSI is able to sell their hardware). I don't see any compelling reason why customers would want to have to maintain such a value. (Customers don't see other customers' dumps so they don't have the need.) Perhaps some ISVs use the license key values to accomplish Todd's goal? -- Tom Schmidt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
