@SYS$MANAGER:UTC$TIME_SETUP SHOW : no output using sysman - VMS

This is a discussion on @SYS$MANAGER:UTC$TIME_SETUP SHOW : no output using sysman - VMS ; If I do the command locally, it works on each of my non-clustered systems: $ @sys$manager:utc$time_setup show AUTO_DLIGHT_SAV is set to "1". OpenVMS will automatically change to/from Daylight Saving Time. (in time zones that use Daylight Saving Time) LOCAL TIME ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: @SYS$MANAGER:UTC$TIME_SETUP SHOW : no output using sysman

  1. @SYS$MANAGER:UTC$TIME_SETUP SHOW : no output using sysman

    If I do the command locally, it works on each of my
    non-clustered systems:

    $ @sys$manager:utc$time_setup show
    AUTO_DLIGHT_SAV is set to "1".
    OpenVMS will automatically change to/from Daylight Saving Time.
    (in time zones that use Daylight Saving Time)
    LOCAL TIME ZONE = US / CENTRAL -- STANDARD TIME
    LOCAL SYSTEM TIME = 5-NOV-2007 09:42:24.73 (CST)
    TIME DIFFERENTIAL FACTOR = -6:00
    TIME ZONE RULE = CST6CDT5,M3.2.0/02,M11.1.0/02
    Change CST to CDT on the Second Sunday of March (11-Mar-2007) at 02:00
    Change CDT to CST on the First Sunday of November (4-Nov-2007) at 02:00

    But if I do it using sysman to the systems,
    there's no output:

    $ mcr sysman
    SYSMAN> set env /nod=
    Remote Password:
    %SYSMAN-I-ENV, current command environment:
    Individual nodes:
    At least one node is not in local cluster
    Username will be used on nonlocal nodes
    SYSMAN> do @sys$manager:utc$time_setup show
    %SYSMAN-I-OUTPUT, command execution on node
    %SYSMAN-I-OUTPUT, command execution on node
    %SYSMAN-I-OUTPUT, command execution on node
    ....

    And, yes, the username being used is fully privileged and
    is the same one that works locally.

    Why doesn't it produce output?

    --
    Dale Dellutri (lose the Q's)

  2. Re: @SYS$MANAGER:UTC$TIME_SETUP SHOW : no output using sysman

    In article , Dale Dellutri writes:
    >If I do the command locally, it works on each of my
    >non-clustered systems:
    >[UTC$TIME_SETUP.COM]
    >But if I do it using sysman to the systems,
    >there's no output:
    >
    >Why doesn't it produce output?


    Because the UTC$TIME_SETUP.COM does a DEASSIGN SYS$OUTPUT and kills
    the logical the SMISERVER sets to get the output of the called procedure.

    Not the only bug of the SMISERVER...

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  3. Re: @SYS$MANAGER:UTC$TIME_SETUP SHOW : no output using sysman

    Peter 'EPLAN' LANGSTOeGER wrote:
    >
    > In article , Dale Dellutri writes:
    > >If I do the command locally, it works on each of my
    > >non-clustered systems:
    > >[UTC$TIME_SETUP.COM]
    > >But if I do it using sysman to the systems,
    > >there's no output:
    > >
    > >Why doesn't it produce output?

    >
    > Because the UTC$TIME_SETUP.COM does a DEASSIGN SYS$OUTPUT and kills
    > the logical the SMISERVER sets to get the output of the called procedure.
    >
    > Not the only bug of the SMISERVER...


    Dale,

    Try this:

    SYSMAN> do spawn @sys$manager:utc$time_setup show

    That produces output for me, with the usual SYSMAN distortion (blank
    lines are supressed, leading/trailing spaces may be trimmed).

    --
    David J Dachtera
    dba DJE Systems
    http://www.djesys.com/

    Unofficial OpenVMS Marketing Home Page
    http://www.djesys.com/vms/market/

    Unofficial Affordable OpenVMS Home Page:
    http://www.djesys.com/vms/soho/

    Unofficial OpenVMS-IA32 Home Page:
    http://www.djesys.com/vms/ia32/

    Unofficial OpenVMS Hobbyist Support Page:
    http://www.djesys.com/vms/support/

  4. Re: @SYS$MANAGER:UTC$TIME_SETUP SHOW : no output using sysman

    On Tue, 06 Nov 2007 19:49:53 -0600, David J Dachtera wrote:
    > Peter 'EPLAN' LANGSTOeGER wrote:
    > >
    > > In article , Dale Dellutri writes:
    > > >If I do the command locally, it works on each of my
    > > >non-clustered systems:
    > > >[UTC$TIME_SETUP.COM]
    > > >But if I do it using sysman to the systems,
    > > >there's no output:
    > > >
    > > >Why doesn't it produce output?

    > >
    > > Because the UTC$TIME_SETUP.COM does a DEASSIGN SYS$OUTPUT and kills
    > > the logical the SMISERVER sets to get the output of the called procedure.
    > >
    > > Not the only bug of the SMISERVER...


    > Dale,
    > Try this:
    > SYSMAN> do spawn @sys$manager:utc$time_setup show
    > That produces output for me, with the usual SYSMAN distortion (blank
    > lines are supressed, leading/trailing spaces may be trimmed).


    Yes, that worked. Thanks.

    --
    Dale Dellutri (lose the Q's)

+ Reply to Thread