[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1222.0. "PCM Truncates Console Data on port without LF" by 60600::BROOKS () Fri Mar 01 1996 00:00

    Hi,
    
    	The SPD states that Console Manager can handle any systems/devices
    of any platform type that sends ASCII data over RS232C direct, TELNET
    or LAT[TM] connections which support XON /XOFF and I/O buffering.
    
    
    	A customer has a RS232 port off a AirCond management port that
    outputs ASCII data, but terminates the line with a <CR> an NOT a
    <CRLF> as like most DEC systems/Devices. PCM truncated the data after
    132 character. Therefore if you use CONSOLE EXTRACT <system> you will
    only see 132 characters and the rest appears to be lost.
    
    	Can Console Manager handle this type of system? or should we
    modify the SPD to say that the output must be terminated by a <CRLF>
    and should be less that 132 characters in lenght.
    
    Thanks,
    Niguel Brooks
    CSC Sydney Aust
    	 
T.RTitleUserPersonal
Name
DateLines
1222.1CSC32::BUTTERWORTHGun Control is a steady hand.Fri Mar 01 1996 14:5113
    Since the SPD is a legally binding document and this system meets the
    requirements stated in the SPD then PCM is required to support it.
    The CR should have terminated the read properly. You mentioned
    truncation at 132 chars which really shouldn't have happened. When you
    did the extract, was your terminal set to NOWRAP? Try doing the EXTRACT
    after issuing the following command:
    
    $ set term/wrap/wid=132
    
    and let us know what happens.
    
    Regards,
       Dan
1222.2more info60600::BROOKSMon Mar 04 1996 03:4167
    
    Dan,
    
    	I checked my terminal setting and it was set to WRAP. I also Dumped
    out the output file from the Extract and the file does not contain any
    data past 132 characters.
    
    Dump of file USER$TSC:[BROOKS]X.X;10 on  4-MAR-1996 14:42:42.38
    File ID (6860,4,0)   End of file block 1 / Allocated 4
    
    Virtual block number 1 (00000001), 512 (0200) bytes
    
     33323D70 6D655420 30303A30 32200086 .. 20:00 Temp=23 000000
     2D202025 33343D79 74696469 6D754820  Humidity=43%  - 000010
     706D6554 2030303A 30302D2D 2D2D2D2D ------00:00 Temp 000020
     2533343D 79746964 696D7548 2033323D =23 Humidity=43% 000030
     54203030 3A34302D 2D2D2D2D 2D2D2020   -------04:00 T 000040
     3D797469 64696D75 48203232 3D706D65 emp=22 Humidity= 000050
     303A3830 2D2D2D2D 2D2D2D20 20253334 43%  -------08:0 000060
     6964696D 75482032 323D706D 65542030 0 Temp=22 Humidi 000070
     00000000 0000FFFF 0D202533 343D7974 ty=43% ......... 000080
     00000000 00000000 00000000 00000000 ................ 000090
     00000000 00000000 00000000 00000000 ................ 0000A0
    
    Heres a dump of the .LOG
    
    Dump of file CONSOLE$ROOT:[LOG]SENTINEL_SITEB.LOG;1 on  4-MAR-1996
    19:53:25.02
    File ID (310,11,0)   End of file block 6 / Allocated 6
    
    Virtual block number 1 (00000001), 512 (0200) bytes
    
     2033323D 706D6554 2030303A 30320AF8 x.20:00 Temp=23  000000
     2D2D2020 2533343D 79746964 696D7548 Humidity=43%  -- 000010
     706D6554 2030303A 30300D2D 2D2D2D2D -----.00:00 Temp 000020
     2533343D 79746964 696D7548 2033323D =23 Humidity=43% 000030
     2030303A 34300D2D 2D2D2D2D 2D2D2020   -------.04:00  000040
     79746964 696D7548 2032323D 706D6554 Temp=22 Humidity 000050
     38300D2D 2D2D2D2D 2D2D2020 2533343D =43%  -------.08 000060
     696D7548 2032323D 706D6554 2030303A :00 Temp=22 Humi 000070
     2D2D2D2D 2D2D2020 2533343D 79746964 dity=43%  ------ 000080
     2032323D 706D6554 2030303A 32310D2D -.12:00 Temp=22  000090
     2D2D2020 2533343D 79746964 696D7548 Humidity=43%  -- 0000A0
     706D6554 2030303A 36310D2D 2D2D2D2D -----.16:00 Temp 0000B0
     2533343D 79746964 696D7548 2032323D =22 Humidity=43% 0000C0
     2030303A 30320D2D 2D2D2D2D 2D2D2020   -------.20:00  0000D0
     79746964 696D7548 2032323D 706D6554 Temp=22 Humidity 0000E0
     30300D2D 2D2D2D2D 2D2D2020 2535343D =45%  -------.00 0000F0
     696D7548 2032323D 706D6554 2030303A :00 Temp=22 Humi 000100
     2D2D2D2D 2D2D2020 2535343D 79746964 dity=45%  ------ 000110
     2032323D 706D6554 2030303A 34300D2D -.04:00 Temp=22  000120
     2D2D2020 2534343D 79746964 696D7548 Humidity=44%  -- 000130
     706D6554 2031353A 37300D2D 2D2D2D2D -----.07:51 Temp 000140
     2536343D 79746964 696D7548 2032323D =22 Humidity=46% 000150
     20747570 6E490D2D 362D2D2D 2D2D2020   -----6-.Input  000160
     6D655420 31353A37 300D076D 72616C41 Alarm..07:51 Tem 000170
     36343D79 74696469 6D754820 32323D70 p=22 Humidity=46 000180
     7475706E 490D2D2D 2D2D2D2D 2D202025 %  -------.Input 000190
     54203030 3A38300D 64657261 656C4320  Cleared.08:00 T 0001A0
     3D797469 64696D75 48203232 3D706D65 emp=22 Humidity= 0001B0
     3A32310D 2D2D2D2D 2D2D2D20 20253434 44%  -------.12: 0001C0
     64696D75 48203232 3D706D65 54203030 00 Temp=22 Humid 0001D0
     2D2D2D2D 2D2D2D20 20253534 3D797469 ity=45%  ------- 0001E0
     48203232 3D706D65 54203030 3A36310D .16:00 Temp=22 H 0001F0
                
    Regards,
    Niguel                                                                   
1222.3CSC32::BUTTERWORTHGun Control is a steady hand.Mon Mar 04 1996 13:0214
    Well you certainly haven't lost any data as the console log file
    contains all the text from the console but I'm surprised it's treating
    it like one big record since there are CR characters being xmitted.
    This same thing occurs on systems that do not send even A CR character
    (e.g., the LPS20's use direct cursor positionining sequence thus the
    logfile is one giant record). I'll have to check the code and see why
    the CR is not doing what we expect. Do a DIR/FULL of the console
    logfile and also do a SET TERM/WID=255/WRAP before doing an EXTRACT
    command and post your findings. If the longer width lets you look at
    more of the record via EXTRACT then at least you can use that for
    the time being.
    
    Regards,
       Dan
1222.4more information60600::BROOKSTue Mar 05 1996 00:0277
    
    Hi Dan,
    
    	Here's the information you requested.
    
    Regards,
    Niguel
    
    
    Directory CONSOLE$ROOT:[LOG]
    
    SENTINEL_SITEB.LOG;1                      File ID:  (310,11,0)
    Size:            6/6          Owner:    [USERS,BROOKS]
    Created:   29-FEB-1996 13:27:15.38
    Revised:   29-FEB-1996 13:28:02.02 (2)
    Expires:   <None specified>
    Backup:    <No backup recorded>
    Effective: <None specified>
    Recording: <None specified>
    File organization:  Sequential
    Shelved state:      Online
    File attributes:    Allocation: 6, Extend: 0, Global buffer count: 0
                        No version limit
    Record format:      Variable length, maximum 2808 bytes
    Record attributes:  Carriage return carriage control
    RMS attributes:     None
    Journaling enabled: None
    File protection:    System:RWED, Owner:RWED, Group:R, World:R
    Access Cntrl List:  None
    
    Total of 1 file, 6/6 blocks.
    
    $ sh term
    Terminal: _RTA1:      Device_Type: VT300_Series  Owner: BROOKS
    Remote Port Info: GIDDAY::BROOKS
    
       Input:    9600     LFfill:  0      Width: 255      Parity: None
       Output:   9600     CRfill:  0      Page:   24
    
    Terminal Characteristics:
       Interactive        Echo               Type_ahead         No Escape
       Hostsync           TTsync             Lowercase          Tab
       Wrap               Scope              No Remote          Eightbit
       Broadcast          No Readsync        No Form            Fulldup
       No Modem           No Local_echo      No Autobaud        Hangup
       Brdcstmbx          No DMA             Altypeahd          Set_speed
       No Commsync        Line Editing       Insert editing     No Fallback
       No Dialup          No Secure server   No Disconnect      No Pasthru
       No Syspassword     SIXEL Graphics     No Soft Characters Printerport
       Numeric Keypad     ANSI_CRT           Regis              NoBlock_mode
       Advanced_video     Edit_mode          DEC_CRT            DEC_CRT2
       DEC_CRT3           No DEC_CRT4        No DEC_CRT5        Ansi_Color
       VMS Style Input
    
    $ console extract/out=1.1 SENTINEL_SITEB
    POLYCENTER Console Manager
    Extract facility Version V1.6-111
    Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
    
    
    Working ... done.
    
    $ dump 1.1
    
    Dump of file USER$TSC:[BROOKS]1.1;2 on  5-MAR-1996 16:13:59.52
    File ID (7132,32,0)   End of file block 1 / Allocated 4
    
    Virtual block number 1 (00000001), 512 (0200) bytes
    
     2D2D2D20 20253334 3D797469 64696D75 48203332 3D706D65 54203030 3A303220  20:00 Temp=23 Humidity=43%  --- 000000
     20202533 343D7974 6964696D 75482033 323D706D 65542030 303A3030 2D2D2D2D ----00:00 Temp=23 Humidity=43%   000020
     33343D79 74696469 6D754820 32323D70 6D655420 30303A34 302D2D2D 2D2D2D2D -------04:00 Temp=22 Humidity=43 000040
     79746964 696D7548 2032323D 706D6554 2030303A 38302D2D 2D2D2D2D 2D202025 %  -------08:00 Temp=22 Humidity 000060
     00000000 00000000 00000000 00000000 00000000 00000000 000A0D20 2533343D =43% ........................... 000080
     00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ................................ 0000A0
     00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ................................ 0000C0
    
1222.5Any more Info ?GIDDAY::BROOKSWed Apr 24 1996 02:528
    Hi Dan,
    
    	Is there any advancement on this problem. Last time I posted a
    DIR/FULL of the console logfile. Do you require the logfiles at
    all.
    
    Regards,
    Niguel CSC Sydney 
1222.6Answer foundGIDDAY::BROOKSWed May 15 1996 02:1486
    
    Hi
    
    	After thinking about the situation, I realize that it would
    be hard for PCM to handle this situation and other type of
    variations. The real issue was hoe to get this output from
    CR to CRLF. I thought of re-directing the output to a 
    dedicated port and having a program do QIO's to the port and
    insert a LF after each CR detected. But I remembered that the
    DECSERVER 90tl has a TELNET server settings that could modify
    output like this.
    
    	So I grabbed a DS 90TL and setup a PCM telnet console and
    took off NEWLINE from the terminal setup features to reproduce
    the problem. 
    	
    	Then I modified the TELNET server setting for the port to 
    the following and I was able to get the Telnet server to 
    assert the LF required for PCM.
    
    	Here are the port settings if anyone else requires them;
    
    local> show telnet list 2008
    
    Listener TCP-port:  2008
    Identification:      PCM TORCO
    Ports:              8
    Connections:        Enabled
    
    local> show port 8
    Port  8:                               Server: PELTS1
    
    Character Size:            8           Input Speed:               9600
    Flow Control:            XON           Output Speed:              9600
    Parity:                 None           Signal Control:        Disabled
    Stop Bits:           Dynamic
    
    Access:               Remote           Local Switch:              None
    Backwards Switch:       None           Name:                    NIGUEL
    Break:              Disabled           Session Limit:                4
    Forwards Switch:        None           Type:                      Soft
    Default Protocol:        LAT
    
    Preferred Service: None
    
    Authorized Groups:   1,  5, 57
    (Current)  Groups:   1,  5, 57
    
    Enabled Characteristics:
    Input Flow Control,  Output Flow Control
    
    
    local>show port 8 telnet server
    
    
    	Port  8
    
    Xmit Char Size:                8    Newline From Term:        <CRLF>
    Rcv Char Size:                 8    Newline From Host:          <CR>
    IP:                         None    Newline To Term:          <CRLF>
    AYT:                        None    Newline To Host:          <CRLF>
    AO:                         None    EC:                         None
    EOR:                        None    EL:                         None
    NOP:                        None
    BRK:                        None
    
    
    Keep in mind that The TELNET CLIENT settings are
    used when the port is in LOCAL MODE, and the TELNET SERVER settings are
    used when in REMOTE MODE.
    
    There is also another distinct difference between the two displays.
    When  reviewing the "Newline" portion of the display, it is important 
    to understand:
    
    on a TELNET CLIENT session (LOCAL MODE):
    The "Term:" or Terminal is the device attached to the DECserver port.
    The "Host:" is the Host the user is connected to accross TELNET, such
    as a UNIX host or TELNET LISTENER port.
    
    
    on a TELNET SERVER or LISTENER session (REMOTE MODE):
    The "Host:" is the device attached to the DECserver port.
    The "Term:" or Terminal is the Host using the resource on this
    DECserver port.
    
1222.7CSC32::BUTTERWORTHGun Control is a steady hand.Wed May 15 1996 14:398
    Good work! I've had to modify the telnet server chars to solve other
    problems. I never thought to ask you if you were using TELNET. Just
    curious but were you using TELNET all along or at one time were you
    using LAT? I ask because the behavior will change between the two
    protocols.
    
    Regards,
       dan