RE: Cognos & iSeries -- MIDRANGE-L

Subject: RE: Cognos & iSeries
From: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 7 Apr 2009 16:08:09 -0500
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>

ENDHOSTSVR *DATABASE
ENDPJ QUSRWRK QZDASOINIT *IMMED

Then after the backup completes:

STRHOSTSVR *DATABASE

Hth, Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com

-----Original Message-----
Subject: Cognos & iSeries

We have a few Cognos 8 user who create reports using our (still) V5R3
iSeries files. I am finding multiple ODBC jobs that are persistent for
several hours. These jobs hold file locks. Short of ending QUSRWRK
before the backup, is there anything from the As/400 side that can be
done to programmatically end these jobs?

And THANK YOU to the authors of WRKODBCJOB!

Thank you,
Bonnie Lokenvitz

As an Amazon Associate we earn from qualifying purchases.

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.