Running SQL "Script" using RUNSQLSTM -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




We are going to start creating/changing files (tables) using SQL "scripts" using
the RUNSQLSTM command.
If anyone has experience doing this sort of thing.  I would like to hear about
the "Got-ya's" ahead of time.
We are going to use commit and rollback.  However, I'm not sure at what severity
level we should be using 0-40 ?
What level of commitment control  *CHG,  *ALL,  *CS,  *NONE,  *RR , *UR, *RS,
*NC ? Etc ....
If you have any advice on what or what not to do I'd appreciate it.

Thanks,
Brian Ellis.





+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.