A small suggestion for the code below would be to add a unique identifier to each WRITE Statement. It seems like every company I've implemented SMS in has constructs which are assigned at multiple points in the code.
If that were to be true in this case, it would be more difficult to determine at which point DSOMEDC was assigned. I've found it to be very helpful to add identifiers like WRITE 'DC000100 DATACLASS SET to ('&DATACLASS')' Each DC# is unique to that WRITE/EXIT combination. When debugging an issue, it can speed things up as your EXIT point is immediately identified. You can also add some of the WRITE variables to help you in debugging the issue like &DSN, &DD, &ANYVOL, etc. ////////////////////////////// IF &DATACLAS EQ '' THEN /* HONORING SPECIFIED STORAGE CLASSES*/ SELECT WHEN (&DSN EQ &WHATEVER) DO SET &DATACLAS EQ 'DCSOMEDC' WRITE 'DATACLASS IS SET TO ('&DATACLAS')' EXIT END WHEN (&DSN EQ &SOMETHING) DO SET &DATACLAS EQ 'DCOTHER' WRITE 'DATACLASS IS SET TO ('&DATACLAS')' EXIT END (repeat as needed) OTHERWISE SET &DATACLAS EQ '' END /* END SELECT */ ********************************************************************** This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN