RE : RE : Savsys in batch

Stephane

As far as I can tell BRMS runs a screen on the console that waits on a data
queue. It doesn't run in batch.

It does lock down the screen by requiring a password to be entered so there
is some security to be had using this method but you could easily add this
to Thomas' suggestion.

I would use a dataqueue instead of a message queue - it would be cleaner in
my opinion.

Regards
Evan Harris


>Thanks thomas for the tip.
>
>I know this way (with data queue).
>But you need to run the waiting pgm ONLINE on console, it cannot be batch.
>And this is my problem.(restricted state)
>Brms can run savsys batched.
>I don't know how.
>May be Leif knows.
>
>--
>Stephane
>
>
>-----Message d'origine-----
>De : thomas@inorbit.com [mailto:thomas@inorbit.com]
>Envoyé : vendredi, 8. février 2002 05:58
>À : midrange-l@midrange.com
>Objet : Re: RE : Savsys in batch
>
>Stephane:
>
>On Thu, 07 February 2002, "ISeries" wrote:
>
> > It seems Brms application do that.
> >
> > I ever checked archive and ... nothing good for me.
> >
> > Our customer don't want to Block the console (waiting time or on data
> queue), because many user have access to.
> > And don't want to save systeme on week-end.
>
>I have never needed to try this, but one possibility comes to mind.
>
>1. CRTMSGQ  qgpl/opsavsys
>
>2. Set authorities so that only restricted profiles can send messages to
>or receive messages from qgpl/opsavsys.
>
>3. Write a break-message handling program to receive messages from
>qgpl/opsavsys. The program can either take the message text and pass it
>directly into QCAPCMD or QCMDEXC or interpret the message text or message
>ID and decide how to start a SAVSYS. The program should be compiled *OWNER
>and have enough authority or call another program that does.
>
>4. CLRMSGQ  qgpl/opsavsys
>** You probably should always clear this *msgq before assigning the
>break-handler.
>
>5. CHGMSGQ  qgpl/opsavsys dlvry(*break) pgm(mylib/mybrkpgm *noalwrpy)
>** The CHGMSGQ command must be run at the console so that the
>break-handling program runs at the console. You can put the CLRMSGQ and
>CHGMSGQ commands into a CL program.
>
>6. Add a job scheduler entry to run a "SNDMSG 'SAVSYS' tomsgq(opsavsys)"
>command at the desired time. Send whatever message or message text that
>the break-handler is looking for. The entry should run under a profile
>that has authority.
>
>The break-handler should be smart enough to make sure that going to
>restricted state isn't going to disrupt whatever might be running at the
>time. Your guess is as good as mine on how to do that. Of course, after
>restricted state and the SAVSYS, STRSBS is needed for the controlling
>subsystem.
>
>Numerous details are missing, but it's reasonable.
>
>I'd test this out, but it's not something that's done on a whim. I suspect
>someone's done this somewhere.
>
>Good luck.
>
>Tom Liotta
>
>--
>Tom Liotta
>The PowerTech Group, Inc.
>19426 68th Avenue South
>Kent, WA 98032
>Phone  253-872-7788
>Fax  253-872-7904
>http://www.400Security.com
>
>
>___________________________________________________
>The ALL NEW CS2000 from CompuServe
>  Better!  Faster! More Powerful!
>  250 FREE hours! Sign-on Now!
>  http://www.compuserve.com/trycsrv/cs2000/webmail/
>
>
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>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@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.