I had the same issue when defining an IODF for a z990 ... I just numbered them sequentially (and cleaned up a few old ones no longer used). I believe the rationale is so that each esoteric will have a constant token (assuming you don't change it later) whereas without the token a catalog entry pointed to an entry in an esoteric table which could easily change when adding/deleting esoterics.
There is a job in SYS1.SAMPLIB(IEFESO) and (IEFESOJL) which scans a catalog for datasets cataloged with esoterics. I found a couple in my shop as well as a bunch cataloged to 3480's and reels which we couldn't read anyway. Ken Porowski AVP Systems Software CIT Group Email: [EMAIL PROTECTED] -----Original Message----- McKown, John > -----Original Message----- > Michael Schmutzok > > Question 1: Am I in big doo-doo if I continue to leave the > token field blank as I have before? > > Question 2: If so, what is my rationale/logic for determining > what to put in as values for each of the esoteric names? > > TIA, > > Mike Schmutzok I just had the same problem when upgrading to a z890 from a z800. Well, the problem was due to PTFs that I put on z/OS 1.4 to support the z890. Anyway, I just starting assigning token numbers from 1 to "n" in the EDT. So far, no problems with anything. That was about 3 months ago. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology ---------------------------------------------------------------------- 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
