Is there a practical limit to the number of dynamic LNKLST sets created? I find myself in a position to deploy two products upgrades, both requiring new data sets in LNKLST (either new names, or under-sizing issues). To accommodate implementation and back out processes, I would like to come up with a naming convention for the LNKLST sets that includes a numeric suffix, such that if product "A" is introduced first, the new set name is LNKLST01. When product "B" is introduced, set name LNKLST02 is defined. If product "A" requires back out, LNKLST03 is defined. If product "B" requires back out, LNKLST04 is defined, etc, etc, rinse, repeat. I honestly doubt there would ever be need to extend past "LNKLST99", or even "LNKLST09", but knowing a limitation (if one exists) will help shape a standard. Is hex representation acceptable, allowing from 01-FF sets? Does decimal representation, allowing from 01-99 sets exceed a limit?
If the maximum number of LNKLST sets is defined somewhere, my apologies for not seeing it! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
