Avoid printing of SYS$ANNOUNCE ? - VMS

This is a discussion on Avoid printing of SYS$ANNOUNCE ? - VMS ; I used the SYSMAN ALF feature to set up a hardwired terminal line to automatically log into a captive account (no Username: prompt) that automatically runs an application when someone presses return on the terminal. There are UAF flags to ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: Avoid printing of SYS$ANNOUNCE ?

  1. Avoid printing of SYS$ANNOUNCE ?

    I used the SYSMAN ALF feature to set up a hardwired terminal line to
    automatically log into a captive account (no Username: prompt) that
    automatically runs an application when someone presses return on the
    terminal. There are UAF flags to do things like disable the SYS$WELCOME
    message, but none for disabling SYS$ANNOUNCE. (Since SYS$ANNOUNCE
    normally gets displayed before the Username: prompt, it makes sense
    that there can't be a NOANNOUNCE flag).

    Does anyone know of a way to disable the display of SYS$ANNOUNCE on a
    terminal-by-terminal basis?

    Related question: Is there a way to disable the "logged out" message at
    the end when a process is logged out? Actually I know an answer to this,
    $ STOP/ID=0. But that seems so crude, is there _another_ way to do that?

  2. Re: Avoid printing of SYS$ANNOUNCE ?

    On Thu, 14 Aug 2008 22:23:26 +0000 (UTC),
    moroney@world.std.spaamtrap.com (Michael Moroney) wrote:

    >
    >Related question: Is there a way to disable the "logged out" message at
    >the end when a process is logged out? Actually I know an answer to this,
    >$ STOP/ID=0. But that seems so crude, is there _another_ way to do that?


    For your second question, EOJ works as well as stop/id=0.

  3. Re: Avoid printing of SYS$ANNOUNCE ?

    none writes:

    >On Thu, 14 Aug 2008 22:23:26 +0000 (UTC),
    >moroney@world.std.spaamtrap.com (Michael Moroney) wrote:


    >>
    >>Related question: Is there a way to disable the "logged out" message at
    >>the end when a process is logged out? Actually I know an answer to this,
    >>$ STOP/ID=0. But that seems so crude, is there _another_ way to do that?


    >For your second question, EOJ works as well as stop/id=0.


    I get the usual logout message from $ EOJ.

  4. Re: Avoid printing of SYS$ANNOUNCE ?

    On Aug 14, 6:23 pm, moro...@world.std.spaamtrap.com (Michael Moroney)
    wrote:
    > I used the SYSMAN ALF feature to set up a hardwired terminal line to
    > automatically log into a captive account (no Username: prompt) that
    > automatically runs an application when someone presses return on the
    > terminal. There are UAF flags to do things like disable the SYS$WELCOME
    > message, but none for disabling SYS$ANNOUNCE. (Since SYS$ANNOUNCE
    > normally gets displayed before the Username: prompt, it makes sense
    > that there can't be a NOANNOUNCE flag).
    >
    > Does anyone know of a way to disable the display of SYS$ANNOUNCE on a
    > terminal-by-terminal basis?
    >
    > Related question: Is there a way to disable the "logged out" message at
    > the end when a process is logged out? Actually I know an answer to this,
    > $ STOP/ID=0. But that seems so crude, is there _another_ way to do that?


    Buy another system and form a VMScluster with your existing system.
    Connect the hard-wired terminals to one system and set it up so that
    everyone else connects to the other. Set up different SYS$ANNOUNCE's
    on each system.

    I don't know how to solve your logout problem. I think you're stuck
    with STOP/ID=0.

    AEF

  5. Re: Avoid printing of SYS$ANNOUNCE ?

    AEF writes:

    >Buy another system and form a VMScluster with your existing system.
    >Connect the hard-wired terminals to one system and set it up so that
    >everyone else connects to the other. Set up different SYS$ANNOUNCE's
    >on each system.


    Not really possible. This isn't a real high priority, it's just that I
    want things to look better.

    I want to log terminal sessions. I have a captive account that does
    the equivalent to SET HOST/LOG 0 to log the terminal session. (I don't
    actually use SET HOST/LOG since I want the log file to be sharable but
    that's another story). Right now the users see SYS$ANNOUNCE twice, once
    for the captive account and once for the logged session. On logout you
    see a logout message twice, once for the logged session and oncec for
    the captive account. Not a big deal, it just looks funny.

    >I don't know how to solve your logout problem. I think you're stuck
    >with STOP/ID=0.



  6. Re: Avoid printing of SYS$ANNOUNCE ?

    On Aug 16, 10:26 am, moro...@world.std.spaamtrap.com (Michael Moroney)
    wrote:
    > AEF writes:
    > >Buy another system and form a VMScluster with your existing system.
    > >Connect the hard-wired terminals to one system and set it up so that
    > >everyone else connects to the other. Set up different SYS$ANNOUNCE's
    > >on each system.

    >
    > Not really possible. This isn't a real high priority, it's just that I
    > want things to look better.
    >
    > I want to log terminal sessions. I have a captive account that does
    > the equivalent to SET HOST/LOG 0 to log the terminal session. (I don't
    > actually use SET HOST/LOG since I want the log file to be sharable but
    > that's another story). Right now the users see SYS$ANNOUNCE twice, once
    > for the captive account and once for the logged session. On logout you
    > see a logout message twice, once for the logged session and oncec for
    > the captive account. Not a big deal, it just looks funny.


    Can you leave the captive account logged in?

    More details might increase the odds of getting a useful answer. E.g.,
    how do you make a shareable log of a new terminal session?

    [...]

    AEF

  7. Re: Avoid printing of SYS$ANNOUNCE ?

    AEF writes:

    >Can you leave the captive account logged in?


    I suppose I could do that.

    >More details might increase the odds of getting a useful answer. E.g.,
    >how do you make a shareable log of a new terminal session?


    I'm using a modified version of SYS$EXAMPLES:ALPHA_LOGGER.C. Biggest
    change is creating a detached interactive process instead of a
    subprocess.


  8. RE: Avoid printing of SYS$ANNOUNCE ?


    In article , moroney@world.std.spaamtrap.com
    (Michael Moroney) writes:

    >I used the SYSMAN ALF feature to set up a hardwired terminal line to
    >automatically log into a captive account (no Username: prompt) that
    >automatically runs an application when someone presses return on the
    >terminal. There are UAF flags to do things like disable the SYS$WELCOME
    >message, but none for disabling SYS$ANNOUNCE. (Since SYS$ANNOUNCE
    >normally gets displayed before the Username: prompt, it makes sense
    >that there can't be a NOANNOUNCE flag).
    >
    >Does anyone know of a way to disable the display of SYS$ANNOUNCE on a
    >terminal-by-terminal basis?
    >
    >Related question: Is there a way to disable the "logged out" message at
    >the end when a process is logged out? Actually I know an answer to this,
    >$ STOP/ID=0. But that seems so crude, is there _another_ way to do that?


    ...Not sure how to deal with your LOGOUT/EOJ issue. As far as
    suppressing SYS$WELCOME goes, though, the common way to handle this is to
    rig up a dynamic message. Do a Google search for "SYS$WELCOME" and "mailbox"
    against the comp.os.vms newsgroup and you should find references to this.

    Regards,
    Mike
    --
    | Systems Specialist: CBE,MSE
    Michael T. Davis (Mike) | Departmental Networking/Computing
    http://www.ecr6.ohio-state.edu/~davism/ | The Ohio State University
    | 197 Watts, (614) 292-6928

+ Reply to Thread