|
Thanks, I have made the relevant changes to the ENDSBS job; the only reason I was issuing an EBDHOSTSVR and ENDTCPSVR was that I was unaware of a save while active on the SAVDLO. I will see if this works tonight. Thanks, Michael. ----- Original Message ----- From: "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> Date: Tue, 30 Sep 2003 08:51:20 -0500 To: "''midrange-l@xxxxxxxxxxxx''" <midrange-l@xxxxxxxxxxxx> Subject: RE: Access to DLO > N, QSNADS does not control access to the DLO's, they are in library QDOC (or > QDOC00xx if you have multiple ASP's). The most likely scenario is that you > are using Netserver to connect to the folders and that is being shut down by > the ENDTCPSRV *all. You could issue a STRTCPSVR SERVER(*NETSVR) immediately > after TCP ends to restart Netserver, but you might still have problems > writing to folders while the SAVDLO is running. > > You can minimize this window by using the SAVACT(*YES) parameter on your > SAVDLO, but be aware that any DLO's that might be locked will not be saved. > > Regards, > > Scott Ingvaldson > AS/400 System Administrator > GuideOne Insurance Group > > -----Original Message----- > date: Tue, 30 Sep 2003 08:25:49 -0500 > from: "michael kearns" <michaelkearns@xxxxxxxxx> > subject: Access to DLO > > Hello, > > Just wondering if anybody knows if QSNADS is the SBS controlling access to > DLO objects. The reason I ask is that a new server is trying to write to a > folder in the QDLS during the night, this is happening at the same time I am > running a SAVLIB and SAVDLO. Before the saves submit, another job runs to > shutdown selective SBS's, ENDHOSTSRV *all and ENDTCPSRV *all. I am not sure > if these shutdowns are restricting the Intel box from copying it's file into > the QDLS folder. > > Thanks, > > Michael. > > This message and accompanying documents are covered by the Electronic > Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information > intended for the specified individual(s) only. This information is > confidential. If you are not the intended recipient or an agent responsible > for delivering it to the intended recipient, you are hereby notified that > you have received this document in error and that any review, dissemination, > copying, or the taking of any action based on the contents of this > information is strictly prohibited. If you have received this communication > in error, please notify us immediately by e-mail, and delete the original > message. > > _______________________________________________ > 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. > -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers
As an Amazon Associate we earn from qualifying purchases.
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.