RE: SQL error causes all batch jobs to fail -- MIDRANGE-L

Subject: RE: SQL error causes all batch jobs to fail
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Date: Thu, 18 Jun 2009 11:36:13 +0200
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

The problem seems to be caused by a migration from one job scheduler to another.

We are migrating from SYSAUTO to AUTOMATOR by AXSYS.

Automator saves the system, stops and restarts the subsytems then passes control to SYSAUTO which continues with the jobs that ended in error. Any use of SQL using !! instead of concat submitted by SYSAUTO will fail. If submitted manually, no problem.

What sytem value could be changed by AUTOMATOR so that !! is no longer recognised?

Thanks

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SQL error causes all batch jobs to fail , Simon Coulter

This mailing list archive is Copyright 1997-2025 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.