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



I've never needed to do it, but I would try adding a "WITH NC" at the end of
the statement:
.... VARCHAR (28) NOT NULL WITH NC;
This changes the commit level to "no commit".

HTH,
Loyd

-----Original Message-----
From: McCallion, Martin [mailto:martin.mccallion@misys.com]
Sent: Tuesday, November 05, 2002 6:05 AM
To: 'midrange-l@midrange.com'
Subject: Ignoring messages in SQL scripts


Hi all.

I have written an SQL script which simply removes the null-capability from a
column.  The entirety of the code is this:

        ALTER TABLE DVMLINK.INCOMINGMESSAGES ALTER COLUMN MOR SET DATA TYPE
        VARCHAR ( 28) NOT NULL;

If I run this interactively in STRSQL, I get a program message which I can
respond to with an 'I' to ignore.  When I run it from OpsNav, it is
automatically answered with the cancel message.

I know I could change the system reply list to force the 'I' answer, but we
will be giving this to clients, and I'd like them just to be able to run the
script, without having to change the reply list first and then remember to
change it back afterwards.  Is there a way to tell the script to ignore the
message?

I can't find anything in the manuals, or on the web, except one exchange in
the archives, where David Gibbs asked how to do the same thing in RPG with
embedded SQL.  R. Bruce Hoffman, Jr. answered that he always did this in
scripts (see http://archive.midrange.com/rpg400-l/200109/msg00327.html).

So, David?  Bruce?  Anyone?

TIA.

Cheers,

Martin.


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.