Chris Mason has cleared up what you can and cannot do. The question what you should do is a different one.
I have a copy of a fairly recent version of the "technical recommendations" of a major consulting firm, one that was once associated with an international auditing firm but is now independent. It makes many recommendations, and they have a characteristic flavo[u]r: Null-eligible DB2 table columns are strongly discouraged because they are 'confusing' and make 'application programs too difficult to write and maintain'. Negative logic should be avoided because it is 'difficult for many programmers to understand'. Static routes should 'always be NOREPLACEABLE ones' because 'the behavior of REPLACEABLE ones is too complex'. It is clear that this firm believes that both its employees and its clients have very low confusion, complication, and difficulty thresholds. Specific difficulties are not described or treated. Notional complexity is the villain. My own view is different. It is that the use of NOREPLACEABLE pours concrete over the behavio[u]r of your network. John Gilmore, Ashland, MA 01721 - USA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
