RE: QZDASOINIT and Persistent Programs

Jim,

Your suggestion is worth a try.  Several host server processes resolve
program pointers when QSERVER is started not at run time.  Its possible
Mike may have to 1) ENDHOSTSVR *ALL, 2) ENDSBS QSERVER, 3) STRSBS
QSERVER and 4) STRHOSTSVR *ALL.  This process will not affect any Host
Server pre-start jobs running QSYSWRK or QUSRWRK.  These pre-start jobs
have to be ended manually after QSERVER has been bounced.  QSYSWRK or
QUSRWRK will automatially start new pre-start jobs when the originals
have been ended with ENDJOB.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
jlowary@xxxxxxxxxxxxx
Sent: Friday, September 10, 2004 12:41 PM
To: midrange-l@xxxxxxxxxxxx
Subject: QZDASOINIT and Persistent Programs 


Mike,

It's not automatic but when you make a change you could do an ENDHOSTSVR

*DATABASE  (or as soon as possible there after)

This will end the QZDASOINIT  jobs and then do a STRHOSTSVR *DATABASE to

restart.  This would keep functions like what you are doing and and
Client 
Abcess - File Transfers from being able to run (actually anything that 
would need the *DB server), but lot better and faster than an IPL/REBOOT

or taking down the subsystem.


-- Jim
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.