>I don't know what that means ( main platform schedule vs platform schedule).
My bad, typo. The individual product schedules do not all regularly fall on the zOS platform schedule. Base elements usually are on the zOS platform but products like OSA, SMP/E, NFS, ICKDSF, etc don't necessarily have to be. Certainly the languages (PL/I, COBOL) may not completely match the platform schedule. >Well I could if the .des files were kept up to date, but evidently >that's not happening. Which is exactly where we came in 29 posts ago. >If the .des files were up to date - in this particular case so that >the z/OS V1.13 file contained COBOL V5R1 as well as older COBOLs - >Charles would have had no cause to complain. There is surely no reason >to tie the .des file content to some now obsolete CD collections. The collection level .des file gets updated every time the deliverable gets produced and put in (usually) the root directory of the collection. At least at this level, IBM is keeping the collection-level .des file current. If you never intend, to download another collection kit, I am not certain that you will get a "new" suite of .des files. You might consider downloading at least new "versions" as they usually involve a complete change of order-number/material ID. That "should" work even against individual products. I have seen it successfully update r13 docs that did not make the initial electronic-deliverable drop. Have you tried using one of the "newer" .des files? Kevin Minerley ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
