× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hey, dumb question here.

In my last test I ended/started subsystem QHTTPSVR. I just did a WRKACTJOB
and none of the HTTP server instances are running.

I mistakenly assumed that starting that subsystem would start the http
servers configured to autostart. I did some digging and it seems STRTCP is
what starts those http servers. I'm not ending TCP so therefore I'm not
starting it either.

Evidently I have to do a STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) as well as
a STRTCPSVR for each instance I want started? That seems odd. There has
to be a better way such that, with one command, I start the http server
instances configured to autostart..



On Wed, Jan 23, 2013 at 3:18 PM, <rob@xxxxxxxxx> wrote:

Just remember, if you do ever save in a fully restricted state you can use
OMITS(*IGNORE) on the STRBKUBRM.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/23/2013 03:04 PM
Subject: Re: BRMS - full save with least amount of restricted time
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I tried another test of saving the IFS today (while active) in BRMS.

Control group:

10 *EXIT ENDSBS SBS(QHTTPSVR) DELAY(60) ENDSBSOPT(*NOJOBLOG)
20 *LINK *ALLAVL FFFFFFF *YES *YES BACKUPS *NONE
30 *EXIT STRSBS SBSD(QHTTPSVR/QHTTPSVR)

These are my *OMITS as defined in QLNKOMT:

/Bytware/StandGuard/AV/logs
/FAXD01/RCVFAX
/QIBM/UserData/HTTPA/admin/logs (probably unneeded as I'm stopping
QHTTPSVR)
/QIBM/UserData/OS400/MGTC/QIWIRELESS/logs
/easy400apc/logs
/QIBM/UserData/OS400/MGTC/service

It worked, so to speak. What I mean is 1 object was not saved
(/QIBM/UserData/OS400/MGTC/config/McEPConfig.properties) as it said the
object was in use. This particular object was not an issue prior to this
test. However, I was messing around with Management Central during this
control group execution and I'm thinking I may have caused the issue. I
kept my hands off Management Central after that.

A test of this control group again tomorrow morning to prove it, then I'm
ready for a final test Saturday morning of the entire system.




On Wed, Jan 23, 2013 at 9:43 AM, Jeff Crosby
<jlcrosby@xxxxxxxxxxxxxxxx>wrote:

No jury duty today. Trial cancelled. Woo hoo!

On Mon, Jan 21, 2013 at 11:47 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:


OSGI, I don't have so I can't see into the directory but if they are
log
files or flight recorders, again not needed for a recovery


Found this IBM document:




http://www-01.ibm.com/support/docview.wss?uid=nas1631d7869f4c9bfa586257738005de266


Which tells me how to avoid the object locked messages for directory
/QIBM/UserData/OS/OSGi/LWISysInst, which is the bulk of them. ENDSBS
SBS(QHTTPSVR) and STRSBS SBS(QHTTPSVR)

I can just add a couple of *EXIT statements surrounding the *LINK save
to
handle that.


--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.




--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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.


--
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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.