× 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.



Message text written by INTERNET:MIDRANGE-L@midrange.com
>37 AM 10/10/97 -0400, Booth Martin wrote:

>on 10/10/97at 08, the Great and Grand  Wazir DennisLovelady@kemet.com

>(Dennis Lovelady) said:

>

>Since the

>possibility (however slight) exists that the record changed, I
personally

>prefer the "read into DS" option.

>

>Isn't the possibility far greater than slight?  Tim said this is a
heavily

>used file.  The idea of reading a record, testing it, and if chosen,

>rereading the record and updating it is a really quick way to read a
file. 

>The chances are very good that it will arrive at almost every single

>record that is already out on other workstations and read it.  This
could

>lead to a lot of conflicts I think.


This, IMO, really pushes me toward Walden's solution of using SQL. That's
a really nice use of the update statement. Tim, if you don't have the SQL
licensed product installed, you can still do this by creating a query
management (*QMQRY) and then execute STRQMQRY from a CL or whatever.
Here's how to do it so that you don't even have to hard-code the file and
field names:


<paraindent><param>out</param>1.        Create a source file called
QQMQRYSRC,
record length 91 (really!).


2.      Add a member to QQMQRYSRC, say UPPER.


3.      Put the following statement in the source member:


            update &file set &field = upper(&field) where &field <<>
upper(&field)


        This uses replacement variables <bold>&file</bold> and
<bold>&field</bold>. These are what takes away the hard-coding. Later
you'll execute STRQMQRY and specify values for these variables. Anything
you put there simply replaces the variable. Therefore, you can even put
in a qualified filename.


4.      Create the *QMQRY:


            CRTQMQRY QMQRY(<italic>somelib</italic>/UPPER)
SRCFILE(<italic>somelib</italic>/QQMQRYSRC) SRCMBR(UPPER)


5.      Assuming an appropriate library list, run the statement with


            STRQMQRY QMQRY(UPPER) SETVAR((FILE <italic>filename</italic>)
(FIELD
<italic>fieldname</italic>))


6.      You can use this in a CL, which could even be the command
processing
program for something like


            CVT2UPR FILE(<italic>filename</italic>)
FIELD(<italic>fieldname</italic>)
        In this case, the STRQMQRY command could be


<

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.