Same problem occurs on V3 for Windows NT


Peter Zutenis wrote:
>
> Dwight,
>
> Hmmm, I have installed the aix adsm client v 3.1.0.1 on my test aix box and 
> have found the same result.
> Thanks for spotting this - I have heaps of scripts that use this method of 
> finding out information from ADSM.
>
> I Think my production systems will stay on AIX V2 clients and Server for a 
> while before I go to ADSM V3!
>
> Best Regards,
>
> Peter Zutenis
> Principal Systems Programmer
> Philip Morris Information Services Ltd
> Moorabbin, Australia.
>
> Phone +61-3-9556-1851
> Internet: pzutenis AT ibm DOT net
>
> -----Original Message-----
> From:   Dwight Cook [SMTP:decook AT AMOCO DOT COM]
> Sent:   Tuesday, 20 January 1998 01:37
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        ADSM Output quirk ! ! ! !  ? ? ? ? ?
>
>      Jerry, have you noticed that... and I'm guessing that it is in the
>      client code, AND all I have on my test box is straight off the CD...
>      THAT v3r1m0 with a "dsmadmc -id=xxx -pass=yyy q node | grep blah" you
>      either have to route in /dev/null (ie "dsmadmc -id=xxx -pass=yyy q
>      node < /dev/null") or hit enter to get it to run... it doesn't detect
>      that it is running in the middle of a process stream and sits and
>      waits on the "press enter to continue".
>      Now I've tried a few different commands that produce enough output to
>      fill multiple pages and it does it for all of them.
>
>      Oh, but are you only MVS Jerry ?
>
>      Folks on the list, I'm in summary mode on the list so unless you
>      include me specifically I won't see your reply until tomorrow...
>
>      later,
>            Dwight
>
>     ---------------------------------------------------------------
>
>                 Part 1.2       Type: application/ms-tnef
>                            Encoding: base64