Re: RUNSQLSTM failure -- MIDRANGE-L

Subject: Re: RUNSQLSTM failure
From: Thomas Garvey <tgarvey@xxxxxxxxxx>
Date: Mon, 11 Nov 2019 12:22:43 -0600
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>

I'll check that. Thanks. But the fact that both the install process and a manual effort to execute the RUNSQLSTM command are both in the same interactive session makes me wonder.
Could there be a PTF problem on their v7r1? This hasn't happened on my v7r3 or v5r4 partitions.

Best Regards,

Thomas Garvey

On 11/11/2019 12:10 PM, Rob Berendt wrote:

Do you have the joblog?
Maybe they are using some weird TGTRLS that predates #INCLUDE.
Maybe they are using some other option which changes drastically, like NAMING(*SYS) vs NAMING(*SQL), or some environment variable.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: RUNSQLSTM failure , Rob Berendt

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.