RE: ODBC/QZDASOINIT Messages

["Haase, Justin C." <justin.haase@xxxxxxxxxxxx>]

Or put all your jobs that would access that particular file/set of files
in a separate subsystem and just end/restart the subsystem.

Justin C. Haase
Solution Manager - Technical Services
Kingland Systems Corporation


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic
Sent: Monday, March 12, 2007 10:45 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: ODBC/QZDASOINIT Messages

Well then, just before you're ready to recreate the file(s), do:

- ENDHOSTSVR *DATABASE
- ENDPJ QUSRWRK QZDASOINIT OPTION(*IMMED)
- delay for time sufficient to bring all of your ODBC jobs down
- run your "recreate files" script
- STRHOSTSVR *DATABASE

It's too bad you have to resort to this kind of drastic action.  
In my humble opinion it reflects a need for application redesign in your
nightly batch jobs.

Elvis

Celebrating 10-Years of SQL Performance Excellence


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Monday, March 12, 2007 10:35 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ODBC/QZDASOINIT Messages


Hi Walden, if the file is left open it will cause abends in nightly
batch
jobs which are trying to recreate the file.  
Frank