× 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 Dave,
Just a quick suggestion to your TCP/IP issue.  There
are probably more elaborate procedures, but just
simply place a program to restart to your TCP/IP on
the job schedular and have it set to kick off about 30
minutes after the SWA would normally bring it back up.


Don

--- daparnin@xxxxxxxxxxxxxxxxxx wrote:

> 
> 
> 
> 
> Jeff,
> 
> I've implemented SWA here.  There's nothing special
> about using QCTL vs.
> another subsystem as long as all user jobs have
> ended.  I submit the
> monitor job to a subsystem that we already had set
> up for I.T. jobs.  The
> program doing the SWA just runs in the user jobq
> under the QBATCH subsytem.
> We get to a "semi-restricted" state by individually
> ending just about all
> other subsytems and ending TCP/IP to kill any ODBC,
> FTP, and 5250
> connections.
> 
> I am reconsidering restarting TCP/IP before the
> checkpoint has been
> achieved.  We had a glitch a month or so ago where
> there was an error with
> the tape drive and there was a QSYSOPR message with
> no way to answer it
> except to drive in (which I did at midnight).  If I
> had TCP/IP running I
> could have used a QCTL session that I've got to get
> in remotely and answer
> it.  That hardware issue was the only problem that
> we've had, which wasn't
> really a problem with SWA.
> 
> Dave Parnin
> Nishikawa Standard Company
> Topeka, IN  46571
> daparnin@xxxxxxxxxxxxxxxxxx
> 
> 
> 
> 
>                                                     
>                                                     
>        
>                       Jeff Crosby                   
>                                                     
>        
>                       <jlcrosby@dilgardfoo       
> To:       Midrange Systems Technical Discussion     
>           
>                       ds.com>                     
> <midrange-l@xxxxxxxxxxxx>@SMTP@CTB                  
>          
>                       Sent by:                   
> cc:       (bcc: David A Parnin/Topeka/NISCO/SPCO)   
>           
>                       midrange-l-bounces@m       
> Subject:  RE: Save while active (SWA)  question     
>           
>                       idrange.com                   
>                                                     
>        
>                                                     
>                                                     
>        
>                                                     
>                                                     
>        
>                       10/21/2004 07:04 AM           
>                                                     
>        
>                       Please respond to             
>                                                     
>        
>                       Midrange Systems              
>                                                     
>        
>                       Technical Discussion          
>                                                     
>        
>                       <midrange-l@midrange          
>                                                     
>        
>                       .com>                         
>                                                     
>        
>                                                     
>                                                     
>        
>                                                     
>                                                     
>        
> 
> 
> 
> Evan wrote:
> 
> > Why wouldn't you do them both in batch ? (just
> curious)
> 
> Up to now I've not used SWA so it had to be
> interactive.  I did an ENDSYS
> for the *ALLUSR backup.  Though I'm not starting
> with the *ALLUSR backup, I
> wanted to keep them all "the same" in style.
> 
> > I don't really have a recommendation either way,
> or more
> > exactly a good reason for why I'd probably go with
> Option 1.
> 
> I was thinking that way yesterday also.  But today
> I'm leaning a little
> more
> toward #2.  Batch has more CPW so it seems, at least
> on the surface, to do
> the heavier lifting there.
> 
> > Whichever way you go, build a timeout into
> > your restart job to make sure it doesn't wait
> forever for the
> > SWA checkpoint when the inevitable error comes
> along.
> 
> Good idea.  I had not thought of that.
> 
> --
> Jeff Crosby
> Dilgard Frozen Foods, Inc.
> P.O. Box 13369
> Ft. Wayne, IN 46868-3369
> 260-422-7531
> 
> 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 ...

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.