RE: Backing up and not taking TCP/IP down

Yes, keep QSYSWRK subsystem up, and if you're doing a SAVLIB *IBM see my
reply re library QIWS and the 7 program objects locked by host server
jobs.



Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: Gary Lehman [SMTP:Gary_Lehman@mail.mchcp.org]
> Sent: Wednesday, July 29, 1998 8:35 AM
> To:   'MIDRANGE-L@midrange.com'
> Cc:   Neil Palmer
> Subject:      RE: Backing up and not taking TCP/IP down
> 
> To tell you the truth we're not specifying the library QIWS on our
> SAVLIB
> command.  We're specifying certain libraries to backup.  We are doing
> a
> ENDSBS on the subsystem QSYSWRK and that's where the TCP/IP jobs are.
> I'm
> not really sure why QSYSWRK is ended, but that's the way the job was
> set up
> by the previous programmer.  So is it true I need to keep QSYSWRK up
> in
> order to keep TCP/IP active?
> 
> Gary Lehman
> Programmer Analyst
> Missouri Consolidated Health Care Plan
> 
>               -----Original Message-----
>               From:   Neil Palmer [mailto:npalmer@NxTrend.com]
>               Sent:   Tuesday, July 28, 1998 5:58 PM
>               To:     'MIDRANGE-L@midrange.com'
>               Cc:     'Gary_Lehman@mail.mchcp.org'
>               Subject:        RE: Backing up and not taking TCP/IP
> down
> 
>               If you mean when you do a complete backup (GO SAVE #21
> or
> equivalent)
>               then the answer is no.  In a restricted state you can't
> have
> TCP/IP
>               active.
> 
>               If you mean in your regular backup program you are
> ending
> TCP/IP, then
>               the question would be why do you do that ?
> 
>               If you do a SAVLIB *IBM in your nightly backup and want
> to
> get
>               everything saved you must ENDHOSTSVR before saving
> library
> QIWS (I run
>               ENDHOSTSVR *ALL - then SAVLIB QIWS separately, then
> STRHOSTSVR *ALL,
>               then OMIT QIWS when I SAVLIB *IBM) to free locks on the
> following 7
>               programs:
>               QNPSERVD, QZDASRVSD, QZHQSRVD, QZRCSRVSD, QZSCSRVSD,
> QZSOSGND,
>               QZSOSMAPD.         
> 
>               Note - doing ENDHOSTSVR *ALL will not kill any active
> TN5250
> sessions to
>               the 400 etc., but it will prevent new sessions from
> being
> able to
>               connect for the approx 10 minutes when they are down.
> 
>               Neil Palmer           
> 
> 
>               > -----Original Message-----
>               > From: Gary Lehman [SMTP:Gary_Lehman@mail.mchcp.org]
>               > Sent: Tuesday, July 28, 1998 5:07 PM
>               > To:   'midrange-l@midrange.com'
>               > Subject:      Backing up and not taking TCP/IP down
>               > 
>               > Hello,
>               > 
>               > Got a question for the system/TCP/IP gurus.  Is there
> a
> way to keep
>               > TCP/IP
>               > up and running when backing up an AS/400?  When we
> backup
> our AS/400
>               > the
>               > subsystem that has TCP/IP running on it is taken down.
> How do we get
>               > around
>               > this?
>               > Thanks,
>               > 
>               > Gary Lehman
>               > Programmer Analyst
>               > Missouri Consolidated Health Care Plan
>               > 
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---