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



Yes the command distinguishes between an interactive and a batch job in 
that subsystem.

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




"David A Parnin" <daparnin@xxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/17/2003 09:49 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Fax to

Subject
Re: Save-while-active questions / concerns







Would the issue of "current environment" be because you are trying to do 
it
from a workstation in QINTER instead of the console in QCTL?  If you 
submit
a job to QCTL wouldn't that environment be acceptable?  Does the command
distinguish between an interactive and a batch job in that subsystem?

Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx





  
                      rob@xxxxxxxxx  
                                               To:       Midrange Systems 
Technical Discussion 
                      12/17/2003 09:36 <midrange-l@xxxxxxxxxxxx>@SMTP@CTB  
 
                      AM                       cc:   
                      Please respond to        Subject:  Re: 
Save-while-active questions / concerns 
                      Midrange Systems  
                      Technical  
                      Discussion  
                      <midrange-l@midra  
                      nge.com>  
  
  



I think that step 1 will never execute.  I prompted ENDSBS, went to the
top and hit F1, scrolled down to the list of monitorable messages and...
CPF1052     ENDSBS *ALL not allowed in current environment.
Cause . . . . . :   ENDSBS *ALL is allowed only from an interactive job
that
  is started from a *SIGNON workstation entry in the controlling
subsystem.
  ENDSBS *ALL is not allowed from a target pass-through job.

Rob Berendt
--
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




"David A Parnin" <daparnin@xxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/17/2003 09:23 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Fax to

Subject
Re: Save-while-active questions / concerns







Thanks to everybody who replied.  I think I've got a better handle on the
concepts that I was missing.  Al makes a good case for the TAA Tool
SAVxxxACT commands which handles a lot of the details.  I may still
implement it with SAVLIB but we'll see.

The steps (as I understand them) are:
1.  Submit a job to QCTL to do a ENDSBS *ALL *IMMED.
2.  When a restricted state has been achieved start another subsystem.
3.  Starting that subsystem will also start the QSYSWRK subsystem so do a
ENDSBS QSYSWRK *IMMED
4.  Submit a job to the newly activated subsystem to monitor a message
queue for the message that the checkpoint has been established.
5.  Issue the SAVLIB command from the QCTL job with SAVACT(*SYNCLIB)
PRECHK
(*YES) SAVACTWAIT(0) and a SAVACTMSGQ specified.
6.  When the job in the new job queue gets the checkpoint message then run
the job specified by the QSTRUPPGM to make the system available for use.

Feel free to correct me if I missed something or got something wrong.
Thanks again everybody.


Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx


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




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