RE: CL Commands in SQL -- MIDRANGE-L

Subject: RE: CL Commands in SQL
From: dlclark@xxxxxxxxxxxxxxxx
Date: Mon, 4 Mar 2019 15:00:59 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 03/04/2019
02:54:00 PM:

I'm not sure what you mean, but AFAIK the Run SQL Scripts just

replaces

those CL: with a call to QCMDEXC, so I'm not sure how it would be any
different.

Apparently not. When I execute these CL command with the CL:
prefix their joblog output appears in my Run SQL Scripts display and in
View / Job Log. But when I run them through the QCMDEXC stored procedure
their joblog output does NOT appear in the Run SQL Scripts display nor in
View Job Log..

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: CL Commands in SQL , Tyler, Matt

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.